In theory should this work: to package a Windows 95 program (currently runnng on XP) to run on W2008r2 64b - or is the
technology gap just too wide. (It didn't work at first attempt - is it worth persevering ?)
In theory should this work: to package a Windows 95 program (currently runnng on XP) to run on W2008r2 64b - or is the
technology gap just too wide. (It didn't work at first attempt - is it worth persevering ?)


From http://stealthpuppy.com/appv-faqs/...
App-V is not a compatibility solution. App-V does not provide any additional layers that applications can use when executing on different versions of Windows. (Source)

My bad, I thought it had some, just not the stuff to go from 16/32 to 64 at any rate it looks like your looking at a full VM to run it then.
Thanks - that is the conclusion I was kinda expecting (ie Virtualbox)

Ive managed to get some 16 bit apps working on 64 bit but i find it very hit and miss usually miss

By some 16-bit apps, do you mean just their installers?
No 16-bit code can run, except for recognized InstallShield and Acme installers (these are hard-coded in Wow64 to allow them to work). (Source)


I thought it was impossible to run 16-bit apps on 64-bit Windows without resorting to VMs (or DOSBox)?
What makes it all worse is that 64-bit Windows has all the same limits even though 64-bit Windows can't run 16-bit applications at all. When operating in 64-bit mode, x86-64 processors can't switch to 16-bit compatible mode. They can switch to 32-bit compatible mode, enabling the use of 32-bit software in a 64-bit operating system, and obviously they can use a 64-bit mode, but there's no 16-bit mode. This means that 64-bit Windows can't run DOS or 16-bit Windows software. If this is something that you really must do, you will have to use a virtual machine. (Source)
There are currently 1 users browsing this thread. (0 members and 1 guests)