[REBOL] Re: Strange behavior
From: amicom:sonic at: 1-Oct-2008 9:24
Graham,
It appears it was partially 'call to blame (even though I also tried the
'run command from Autoit via REBOL's dll facilities with similar results).
However, the main problem seems to be running a REBOL executable as a
Windows service. Here are the service types:
Type is a type REG_DWORD that specifies what this object represents:
Value D e s c r i p t i o n
1 A kernel-mode device driver.
2 A file system driver.
4 A set of arguments for an adapter.
8 A file system driver service, such as a file system recognizer.
16 (0x10) A Win32 program that runs in a process by itself. This type
of Win32 service.can be started by the Service Controller.
32 (0x20 A Win32 program that shares a process. This type of Win32
service can be started by the Service Controller.
272 (0x110) A Win32 program that runs in a process by itself (like
Type16) and can interact with users.
288 (0x120) A Win32 program that shares a process and can interact
with users.
I've tried all these values with no success.
Unless anyone has any ideas, here is my conclusion:
REBOL executables running as a service are moderately to severely
sterilized
. Executables launched from a service-launched REBOL
executable generally cannot display their interface and interact with
the operating system in a normal manner.
-Bo
