naides
November 8th, 2009, 10:10
Quote:
[Originally Posted by Worf;83616]Hi.
Does anyone know how to patch Win7\Vista files so that they will work in Win xp? I know it can be done. . . |
I somewhat doubt it . . .
Windows OS are well know to have a design phylosophy of back-compatibility, to allow new products to be introduced in the market without every one having to buy all new hardware and new software from scratch with every update.
Forward compatibility? Meaning that the designers of XP somehow previewed, in their crystal balls, the future internal workings of Vista/win7 and made arrangements to accomodate their yet unkown functions???? What would be the point of new, improved OS architecture then?
If the win7 specific code contains system calls and API's that only exist in Win7, tough shit. Either you emulate them in Win XP, ie invent the wheel, or upgrade your OS to Win 7, which IMHO is the sanest choice.
If the snag is a simple OS check, then isolating the check and bypassing it is the way to go. inside .inf files you find lines of the form
oslist=501,600,600.64,601,601.64
Which translate: if the OS is
501 (Windows XP)
501.64 (Windows XP 64) (Sucks)
600 (Vista)
600.64 (Vista 64)
601 (Windows 7)
601.64 (Windows 7 64)
Then install and/or run, otherwise not.
Also there is the GetVersion API's called near the begining of regular code. . .
Remeber that these guards are there for a reason, to adjust the code to the OS, or to prevent the code from running and crashing, if it is in the wrong environment. . .
You bypass them at your own peril.
A workaround solution would be install a VM host in XP tah is able to run Win 7 as a guest (VMWARE 7.0) then run you Win 7 specific program inside the VM, using it as an adaptor. In any case, you need a version of Win 7 installed in your computer, virtually or otherwise.
