Re: VersionNumber reg. key

[Jeff Smith]

My $0.02:
I say don't create, and dynamically 'lie' about it's value.
I'm sure it's easier said than done, but that's my thoughts, anyway.

-- Jeff S
> From: Ender 
> To: [e-mail]
> Subject: VersionNumber reg. key
> Date: Wed, 4 Sep 2002 21:28:32 -0500 (CDT)
> read the HKLM\Software\Microsoft\Windows\CurrentVersion\VersionNumber
> key. And of course, as this is a 'required' key in Windows, there was no
> code to cope with failure :)
> whether or not Wine should dynamically 'lie' about this registry key,
> depending what winver the current thread is running in.
> - Ender

_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

VersionNumber reg. key

[Bill Medland]

Question; is the "current version" a property of the client or the server; I
guess its the client.

I would suggest that when the registry is loaded the value is modified in
line with the current version.  Then we only need to check as we load the
registry; we don't need to keep watching for the question (especially
because it can be asked in so many different ways).

Bill
----- Original Message -----
From: "Jeff Smith" 
To: 
Sent: Thursday, September 05, 2002 7:19 AM
Subject: Re: VersionNumber reg. key
> My $0.02:
> I say don't create, and dynamically 'lie' about it's value.
> I'm sure it's easier said than done, but that's my thoughts, anyway.
>
> -- Jeff S
> > From: Ender 
> > To: [e-mail]
> > Subject: VersionNumber reg. key
> > Date: Wed, 4 Sep 2002 21:28:32 -0500 (CDT)
> > read the

HKLM\Software\Microsoft\Windows\CurrentVersion\VersionNumber
> > key. And of course, as this is a 'required' key in Windows, there was no
> > code to cope with failure :)
> > whether or not Wine should dynamically 'lie' about this registry key,
> > depending what winver the current thread is running in.
> > - Ender
>
> Chat with friends online, try MSN Messenger: http://messenger.msn.com

VersionNumber reg. key

[Andreas Mohr]

On Thu, Sep 05, 2002 at 09:40:30AM -0700, Bill Medland wrote:
> Question; is the "current version" a property of the client or the server; I
> guess its the client.

It's a property of the client.
However, the registry data is a property of the server.
This is a conflict, of course.
In this case I'm afraid we'll have to register the version value the
first wine instance has.

This method will break if you decide to run programs with *differing*
Windows version requirements within the same wineserver session,
of course. :-\
(as the first program's setting/requirement will be used for all wine
sessions)