Could not determine operating system. Exiting.

[Pavel Troller]

Hi!
  Congratulations for releasing wine-0.9!
  However, I still have a problem running a program. It's a NT4.0 only program
(at least its vendor is telling it) which I would like to run in wine. It's a
special software made by Siemens to support operation and maintenance of their
telephone exchanges.
  The installation starts, but after clicking the first "Next", just after the
initial information about the program, a small dialog saying "Could not
determine operating system. Exiting" pops up and the installation terminates.
  I've set the windows version in winecfg to NT4.0, as the program expects,
however I've tried another versions too and the program is ignoring it totally.
It's just clean CVS wine installation (no windows).
  Is there a possibility to find, which tricks is the program trying to
determine an OS it's running on ? I've tried WINEDEBUG=+relay, found the place
where the dialog was requested but I didn't find anything suspicious before.

                           With regards, Pavel Troller

[James Hawkins]

On 10/27/05, Pavel Troller <patrol(a)sinus.cz> wrote:
> Is there a possibility to find, which tricks is the program trying to
> determine an OS it's running on ? I've tried WINEDEBUG=+relay, found the place
> where the dialog was requested but I didn't find anything suspicious before.

I'm guessing the answer is no, but is there a free version of the
program or a demo that we can download?  It's hard to find this type
of bug without having the program to tinker with.  Assuming the answer
is no, can you provide the line where the dialog pops up and ~1000
lines before that point in a +version,+relay log?  Zip that up and
either send it back to the list (if the size isn't too large and the
mailing list lets it through) or post it on a website where we can
access the log.

Thanks,
James Hawkins

[Pavel Troller]

> I'm guessing the answer is no, but is there a free version of the
> program or a demo that we can download?  It's hard to find this type
> of bug without having the program to tinker with.  Assuming the answer
> is no, can you provide the line where the dialog pops up and ~1000
> lines before that point in a +version,+relay log?  Zip that up and
> either send it back to the list (if the size isn't too large and the
> mailing list lets it through) or post it on a website where we can
> access the log.
> Hi James!
>   Thanks for Your help, I made some progress in this issue.
>   I've looked once more to the +relay log (+version gives nothing). I've
> found that about 2000 lines before the dialog pops up there is a block
> reading all the NAMES of environment variables and comparing them with
> "OS". So I intuitively entered OS="Windows NT" before starting the program
> and now I'm getting another pop-up, saying that only NT is supported. So my
> "OS string" is wrong. I can find, where my name string retrieved from the
> envvar, but there isn't any comparison visible in the log (i.e. it's done
> internally in the program). 
>   So what I need now, is an exact string, which NT4.0 put to the OS envvar.
>   And I have a tip for wine improvement: maybe it would be good, that
> wine itself would set up such a variable according to the OS version it's
> emulating.
>                   With regards, Pavel Troller
> Thanks,
> James Hawkins

[Vitaliy Margolen]

Thursday, October 27, 2005, 11:41:02 AM, Pavel Troller wrote:
> > I'm guessing the answer is no, but is there a free version of the
> > program or a demo that we can download?  It's hard to find this type
> > of bug without having the program to tinker with.  Assuming the answer
> > is no, can you provide the line where the dialog pops up and ~1000
> > lines before that point in a +version,+relay log?  Zip that up and
> > either send it back to the list (if the size isn't too large and the
> > mailing list lets it through) or post it on a website where we can
> > access the log.
> > Hi James!
> >   Thanks for Your help, I made some progress in this issue.
> >   I've looked once more to the +relay log (+version gives nothing). I've
> > found that about 2000 lines before the dialog pops up there is a block
> > reading all the NAMES of environment variables and comparing them with
> > "OS". So I intuitively entered OS="Windows NT" before starting the program
> > and now I'm getting another pop-up, saying that only NT is supported. So my
> > "OS string" is wrong. I can find, where my name string retrieved from the
> > envvar, but there isn't any comparison visible in the log (i.e. it's done
> > internally in the program). 
> >   So what I need now, is an exact string, which NT4.0 put to the OS envvar.
> > You was really close: OS=Windows_NT

Vitaliy.

[Pavel Troller]

> > So what I need now, is an exact string, which NT4.0 put to the OS envvar.
> > You was really close: OS=Windows_NT

Hi!
  Thanks, it's really what the program was checking for!
  Now the installation proceeded and even succeeded without a glitch!
  However, the installed program doesn't run :-(.
  
  It requires to start the service first. The following occurs:

patrol(a)arcus:~/.wine/drive_c/SYSD$ wine Sysd.exe -1 -start

StartServiceCtrlDispatcher starting;
This will take several seconds or more.  Please wait. Use arg -help.
err:advapi:service_control_dispatcher failed to create pipe, error = 0
StartService: the StartService function failed. SYSD Service 1.
  File not found (0x2)
fixme:advapi:RegisterEventSourceA ((null),"SYSD"): stub
fixme:advapi:RegisterEventSourceW (L"",L"SYSD"): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000001,(nil),0x0001,0x00000000,0x7fc8fd14,(nil)): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000001,(nil),0x0001,0x00000000,0x7ff6c970,(nil)): stub
err:eventlog:ReportEventW L"CmdStartService: The StartService function failed."
fixme:advapi:CloseEventLog (0xcafe4242) stub
OpenService:
patrol(a)arcus:~/.wine/drive_c/SYSD$

  After the first err: from advapi (failed to create pipe), the program really
waits for about a minute and then writes the rest in a quick row.
  Is there a chance it will run in wine in a near future ? May using
native advapi for NT4.0 help ?

  I'm also answering one of the former questions: No, the program cannot
be downloaded from anywhere; it's a part of commercial software which is
bought together with an EWSD telephone exchange.

  Many thanks for Your support!
                           With regards, Pavel Troller

[Vitaliy Margolen]

Thursday, October 27, 2005, 1:06:01 PM, Pavel Troller wrote:
> > > So what I need now, is an exact string, which NT4.0 put to the OS envvar.
> > > You was really close: OS=Windows_NT
>
> Hi!
>   Thanks, it's really what the program was checking for!
>   Now the installation proceeded and even succeeded without a glitch!
>   However, the installed program doesn't run :-(.
>
> It requires to start the service first. The following occurs:
>
> patrol(a)arcus:~/.wine/drive_c/SYSD$ wine Sysd.exe -1 -start
> That does not work ATM on Wine. Wine can't handle any services because there is
> no infrastructure at all to support them.

Me and several other people working on this, but this will not be available for
some time. Also I'm not sure what that service does, but if that is some kind of
hardware driver - this will not work. As our goal to have only "self contained"
drivers working (those that for most part allow something that you normally can
not do on winNT from user space).

Vitaliy.

[Robert Shearman]

Vitaliy Margolen wrote:
> Thursday, October 27, 2005, 1:06:01 PM, Pavel Troller wrote:
> > > > So what I need now, is an exact string, which NT4.0 put to the OS envvar.
> > >
> > > You was really close: OS=Windows_NT
> >
> > Hi!
> >  Thanks, it's really what the program was checking for!
> >  Now the installation proceeded and even succeeded without a glitch!
> >  However, the installed program doesn't run :-(.
> >
> > It requires to start the service first. The following occurs:
> >
> > patrol(a)arcus:~/.wine/drive_c/SYSD$ wine Sysd.exe -1 -start
>
> That does not work ATM on Wine. Wine can't handle any services because there is
> no infrastructure at all to support them.

Services should work, even though the architecture is technically wrong.
> Me and several other people working on this, but this will not be available for
> some time. Also I'm not sure what that service does, but if that is some kind of
> hardware driver - this will not work. As our goal to have only "self contained"
> drivers working (those that for most part allow something that you normally can
> not do on winNT from user space).

That isn't what the above program is doing.

-- 
Rob Shearman

On Thu, 27 Oct 2005 19:55:38 +0200, Vitaliy Margolen  
<wine-devel(a)kievinfo.com> wrote:
> You was really close: OS=Windows_NT
> Vitaliy.

I was ; you were ;)

On 10/27/05, Pavel Troller <patrol(a)sinus.cz> wrote:
> > Is there a possibility to find, which tricks is the program trying to
> > determine an OS it's running on ? I've tried WINEDEBUG=+relay, found  
> > the place
> > where the dialog was requested but I didn't find anything suspicious  
> > before.

I suggest looking at the "reg" chanel , my bet is it will be looking for  
something like software/microsoft/windows/version ..... that would seem to  
be the most obvious check for a program to do and probably the officially  
correct way to do so.

look at your NT system to get the specific key then log all your  
WINEDEBUG= output to a text file and grep it for the key.

HTH.