Am 17.04.2011 19:26, schrieb Alexandre Julliard:
> André Hentschel writes:
>
>> in 64-bit processor mode you can't use vm86 for 16-bit apps, so you need to
>> use dosbox on Windows an Wine does that automaticly (but needs some more
>> love).
>> So 16-bit vs. kernel-versoin on 64-bit is no probl
André Hentschel writes:
> in 64-bit processor mode you can't use vm86 for 16-bit apps, so you need to
> use dosbox on Windows an Wine does that automaticly (but needs some more
> love).
> So 16-bit vs. kernel-versoin on 64-bit is no problem.
16-bit code doesn't need vm86.
--
Alexandre Jullia
Am 15.04.2011 16:07, schrieb Ken Sharp:
> The only problem then is people wanting to run 32-bit apps with 16-bit code
> on a 64-bit system in XP mode might have all kinds of problems if the app
> first checks which kernel is in use - MS in their obvious wisdom have removed
> the 16-bit VM from X
Yep. That makes more sense. It's certainly beyond my capability.
The only problem then is people wanting to run 32-bit apps with 16-bit
code on a 64-bit system in XP mode might have all kinds of problems if
the app first checks which kernel is in use - MS in their obvious wisdom
have removed
Ken Sharp writes:
> Windows XP x64 has an updated kernel to XP, so just setting XP in
> winecfg will still cause apps to fail. IE8 for XP x64 is an example.
This should most likely be done automatically on 64-bit.
--
Alexandre Julliard
julli...@winehq.org
