I'm afraid I don't know. I suspect that there's nothing terribly special about a Windows Service, AFAIK it's a regular PE-format executable. Obviously it must be fully self-contained and not interactive in any way (so not accessing the keyboard or screen, for example). There's some relevant information here.What would be required to run a compiled bb4w program as a Windows' service, and not as a regular application?
So that that would allow automatic restarts, status notifications, easy reports and logging.
One concern I would have is that there is no way to stop a BB4W executable creating a window; it will always do that (even when compiled as a Console application). So if Windows objects to a service creating a window, it may fail. I think that's relatively unlikely, but the only way to find out is probably to try it.
A Google search finds this reference which hopefully tells you everything you need to know about accessing an Event Log. Although I've not tried it myself, it looks perfectly straightforward on a quick glance.And related to that, is there a bb4w library that allows (an easy) access to (esp. writing) Windows Event Log?