I want to setup a squeak instance running seaside, and an RFB server. 
This way I can monitor/maintain/debug the server from anywhere on my 
VPN with a VNC client.

I've seen notes from others about installing squeak as an NT Service 
being an issue.  I tried a third party EXE NT service "Wrapper" with 
the best results so far.  But this didn't allow for the NT Services to 
find out when Squeak went down.

Several questions I have...

1) With respect to NT service Configuration.  Do I need to select the 
   option  "allow the service to interact with the desktop"?  It seems 
   like this may be necessary for low level GUI things to be present 
   for squeak in order for the VNC server to run/ I just don't know.  
   When I select this option Squeak fails to start because it cannot 
   find the image, it's looking for an image with a garbled name, not 
   the one I specifiy.

2) If I select this option (#1 above) I can't select the "This 
   Account" and specify a different account with permissions for 
   networking.  Do I need this so seaside and RFB support can create 
   server sockets?


--

I use several Squeak/Seaside/RFB services on WS2003. I'm trying it now on
virtual WinXP Prof. without problems. 

The structure of this service directory (C:\squeak) is:
Service.exe (renamed Squeak.exe)
Service.changes
Service.Image
SqueakV3.sources
Service.ini

The content of Service.ini is:

[Global]
DeferUpdate=1
ShowConsole=0
DynamicConsole=1
ReduceCPUUsage=1
ReduceCPUInBackground=0
3ButtonMouse=0
1ButtonMouse=0
UseDirectSound=1
PriorityBoost=1
B3DXUsesOpenGL=0

CaseSensitiveFileMode=0
ImageFile="C:\squeak\Service.image"

[Security]
UserDirectory="C:\squeak\"


I run this service using:

Service.exe -service: "SqueakService" "C:\squeak\Service.image"

The virtual machine finds image file correctly.

You don't have to change any other service settings like interacting with
the desktop. I run Squeak services under unprivileged account.

-- Pavel