Would you please kindly elaborate? I hadn't heard of using OS/2 files in Win up to now.
You could fix up most of the bugs in Windows by using the Win-OS/2 files, but i wasn't all that game in replacing things like winoldap.mod, etc.
Most of what's in \OS2\MDOS\WINOS2 is an IBM compile of Microsoft's Windows 3.10 code. It has a handful of DOS files in it, and some icon changes (including winoldap).
It's pretty easy to work out the hacked files, since OS/2 for Windows
adds such files to a Windows 3.1 setup. These have different names, and use different functions to the standard DOS features. There are proggies that can add files from MS-Windows to Win-OS/2 to have the same effect.
Some of the files, like write.exe are identical. Others like progman and calc.exe, are different (the OS/2 version does not have the bugs). Winfile works quite well under both, i suppose. The help about dialog lives in 'shell.dll', so when you call this up, you get 'win-os/2 3.11' under my Windoze soup.
After 1994/01/01 the IBM/Msft joint agreement went into another stage, and Wfw 3.11 was brought out with some modification that adds incompatibilities to OS/2 for Windows. IBM did fix this up, in a later release. In any case, you can run Wfw 3.11 under standard mode, (since wfw 3.10 does), but you have to lift some files from win 3.11 or 3.10 to do it. On the other hand, setup in wfw 3.11 does not handle standard mode things, even though space exists for it. You have to manage these adjustments manually.
Still, nearly all of the utilities from OS/2 i have used under DOS, Winfile and Printman comes from Wfw and other files lifted elsewhere. If you put shell.dll and the two ole*.dll files, Windows will tell you that it's win-os2.
Note in the picture it says 'win-os2 version 3.11'. It's running under DOS, there never was a win-os2 3.11.
Edited by os2fan2, 18 April 2012 - 04:43 AM.