I have a cdrom, for DOS and Windows setup, from which i run also Windows from the CD.
I am aware of Weinneger's version of Windows 3.1 and 95, and i have started to fix the 95 version up.
I really can't see the point of his 3.1, though, since you don't have to run Windows 3.1 binaries from the RAMDISK. The thing works quite well in diskless workstations, with a shared system directory, and separate user directories.
I really can't see the point of patching the files after Windows is set up: you can quite easily set the thing up under subst, because windows 3.1 does not look through subst.
Correspondingly, the Windows network %windir% is well under 480 kb, which means it fits quite well onto a floppy. Don't forget, that Windows 3.1 was intended to run on diskless networked workstations with 8MB ram or less.
The idea here is that the network drive is shared between users, as say, s:\ and the user home is h:\ So the h:\win directory has *only* the ini files, win.com, and winver.exe, The s:\win31 directory has the network install. Nothing about what drive windows is installed on is in s:\win31. On the server, this might be e:\apps\win31, where e:\apps is shared out as s:\ to the users.
What it means is that you can boot Windows on a very tiny footprint.
The relevance of the Weinneger effort is that when Windows is completely in the ramdrive, you can remove the floppy disk. Even here, though, Windows affords lots of room in "thining out the product" without loss of functionality (ie use vga etc) and kill of drivers, etc. It also does not loose any kind of functionality.
One could, without loss of generality, copy icons of your apps into a copy of moreicons.dll, and point all your group icons at that DLL, and index number. So when you create an icon with "write.exe" as the exe line, and "myicons.dll,17" as the DLL, where that DLL is in the r:\win directory, it *doesn't matter* whether windows is in the r:\ drive or the s:\drive, write.exe will always be found by a path search.
On the other hand, the icon that progman shows *does* need to be in a stable path, which is why you might consider dragging the icons out of the apps into a single file, which is part of the user directory.
I have always multibooted, but in these cases, i have *always* put Win9x into its own partition, but its boot block is off the c-drive. This is because, some virii look for c\windows, (i never use that directory name).
Also note that the c:\ drive is now pretty much limited to under 500 MB, largely because some proggies will make it fat32 if it's over that size.
PC-DOS 7
------------
Most of the utilities of PC-DOS 7.0 have been defanged, and run quite happily under any DOS. I ran, for example, DOS 7 subst under MS-DOS 5, All kinds of DOS 6, Windows 95, Windows 98 SE.
If you multiboot under a commercial bootmanager, you can feed most of the DOS utilities through the PC-DOS stuff, with just a minimal native DOS.
Windows 9x
--------------
I very rarely install Windows 9x into the c:\ drive. This is left for "real" DOS.
The DOS Patch
------------------
I did patch a version of DOS 7.10.2222 (ie the one from Windows 98SE), and ran it from both Win98 and Win31 in the same sessions. None the same, the two sources of patch DOS versions *do not work* as designed, so i found
http://www.oldstuff.myagora.net/powerload/...oad/3xStart.exe http://www.oldstuff.myagora.net/powerload/...isk/msd710s.zipas the basis of my DOS. You still have to patch the MS-DOS in msd710 with 3xStart.exe, but it works like a dream elsewise.
The links don't work as designed, but google for 3xStart.exe and msd710s.zip and you should find current links to them.
The DOS in Weinneger's set is 7.10.1999, it is based around codepage 936, whereas the msd710s.zip version is 7.10.2222 based around the English cp 437 one.
In any case, you *can* run Win31 under two different DOS versions under the same time. You can also multiboot Windows 95 and Windows 98, by doing a couple of tricks.
I am thinking one day of thinning out a lot of the old legacy stuff out of Windows 3.1, mainly old dot-matrix print drivers network drivers, etc, to reduce the size of source. It, knowing my skill, should work like a dream.
W