On 19/03/2008, Chris Teague <[EMAIL PROTECTED]> wrote:
> This is probably trivial, but I'm having a tough time figuring out the
> current version of Windows that Wine is mimicking. I have a situation
> where I need to behave differently if the version is NT (0x0500)
>
Chris Teague wrote:
> This is probably trivial, but I'm having a tough time figuring out the
> current version of Windows that Wine is mimicking. I have a situation
> where I need to behave differently if the version is NT (0x0500)
> versus when it is XP (0x0600). I see the WI
On Wed, Mar 19, 2008 at 2:02 AM, John Klehm <[EMAIL PROTECTED]> wrote:
>
> On Wed, Mar 19, 2008 at 1:31 AM, Chris Teague <[EMAIL PROTECTED]> wrote:
> > This is probably trivial, but I'm having a tough time figuring out the
> > current version of Window
On Wed, Mar 19, 2008 at 1:31 AM, Chris Teague <[EMAIL PROTECTED]> wrote:
> This is probably trivial, but I'm having a tough time figuring out the
> current version of Windows that Wine is mimicking. I have a situation
> where I need to behave differently if the version is N
This is probably trivial, but I'm having a tough time figuring out the
current version of Windows that Wine is mimicking. I have a situation
where I need to behave differently if the version is NT (0x0500)
versus when it is XP (0x0600). I see the WINVER #define, but that
doesn't seem r
"Mikolaj Zalewski" <[EMAIL PROTECTED]> writes:
> @@ -144,10 +144,18 @@ static int result_cp_949_mbctype[] = { 0
> static int result_cp_950_mbctype[] = { 0x0,65, 0x8,1, 0x18,26, 0x8,6,
> 0x28,26, 0x8,4,
>0x0,2, 0x4,32, 0xc,94, 0,1 };
>
> +/* these characters may differ on different Windows
