Hi,
I'm trying to run Seti Queue 1.0 under the latest debian wine package
0.0.20010326-3. However, when I try to run
wine --winver win98 setiqueue
I get the following log output:
fixme:win32:GetUserObjectInformationA (0x1 1 0x40566c14 12
0x40566c20),stub!
err:advapi:StartServiceCtrlDispatcherA Couldn't find wait semaphore
err:advapi:StartServiceCtrlDispatcherA perhaps you need to start
services using StartService
err:ntdll:RtlpWaitForCriticalSection Critical section 0x409c41d0 wait
timed out, retrying (60 sec) fs=0237
err:ntdll:RtlpWaitForCriticalSection Critical section 0x4065c090 wait
timed out, retrying (60 sec) fs=0237
err:seh:EXC_DefaultHandling Unhandled exception code c0000194 flags 0
addr 0x40059670
And when I run:
wine --winver win95 --debugmsg +advapi setiqueue.exe
I get the following:
trace:advapi:OpenSCManagerW ((null),(null),0x000f003f)
trace:advapi:OpenSCManagerW returning c0
trace:advapi:OpenServiceA Request for service SetiQueue
trace:advapi:OpenServiceW (192,0x40366460,983551)
trace:advapi:OpenServiceW Opening reg key
L"System\\CurrentControlSet\\Services\\SetiQueue"
trace:advapi:OpenServiceA Request for service SetiQueue
trace:advapi:OpenServiceW (192,0x40366460,4)
trace:advapi:OpenServiceW Opening reg key
L"System\\CurrentControlSet\\Services\\SetiQueue"
fixme:win:GetProcessWindowStation (void): stub
fixme:win32:GetUserObjectInformationA (0x1 1 0x40566c14 12
0x40566c20),stub!
trace:advapi:StartServiceCtrlDispatcherA (0x4b02b8)
err:advapi:StartServiceCtrlDispatcherA Couldn't find wait semaphore
err:advapi:StartServiceCtrlDispatcherA perhaps you need to start
services using StartService
My question is, why is it trying to get to the Services branch of the
Registry Tree?? This app does
run under WinME, and when I look in my WinME Registry, this
Services\\SetiQueue
branch does not exist? So, why is it trying to look for it??
Any comments/questions gratefully accepted...
