|Windows 3.1 / 3.11 Menu||Slimming Down Windows 3.1/3.11||Full screen|
The new programs keep requiring more and more space. But many of the files are not necessary. All the files you may need for every possible computer the program may be installed and are cluttering up your hard drive. Windows 3.11 freshly installed with a network card takes up about 14mb. But the actual Windows runable is less than 2mb.
Because it is in ram memory, moving from window to window is quite fast. It move more like a 486x50. Time will tell how well other programs wil run on this "slow" computer.
|In the Windows Directory you need:|
|These files total: 180,155 bytes|
|In the Windows\system Directory you need:|
|These files total: 1,482,266|
|The total for Windows is: 1,662,421 bytes.|
|These two files will change depending on the Video driver you load:||vga.3gr||vga.drv|
|If you load Super VGA, they will be:||vddsvga.386||svga256.drv|
Now, of course it is void of any programs. So it is just there. So now you add the files you need for whatever programs the files are needed for. You can keep many files in reserve until they are needed. Help files you probably won't need once you have the Windows set up the way you want it. CPL files aren't needed unless you need to change something with the CONTROL PANEL.
|In the Windows Directory you need:|
|accessor.grp||8723||The Accessories Group||network.grp||6508||The Network Group|
|games.grp||42||The Games Group||startup.grp||44||The Startup Group|
|dosprmpt.pif||545||DOS Prompt PIF||_default.pif||545||Default PIF Source|
|control.exe||The Control Panel||control.ini||148592||Control Panel Information|
|cpwin386.cpl||111760||The Windows Setup Program||main.cpl||148592||The Drivers Setup Program|
|drivers.cpl||41440||The Drivers Setup Program||snd.cpl||8192||The Sound Drivers Setup Program|
|fax.cpl||2048||The Fax Program driver Setup|
|Additionally, these programs will need:|
|These files total: 1,020,251 bytes|
These files could be stored in a ZIP file or other location until needed.
|To operate only as a client (DOS or Windows):|
|net.exe||433829||The DOS Networking Program||net.msg||75697|
|protman.exe||13782||protocol.ini||528||Set Up by Windows|
|wfwsys.cfg||840||set up by Windows||de22x.dos||28832||Card driver from vendor|
|ipxodi.com||39748||Protocol driver from vendor|
The Network can be connected at DOS and will be available in Windows. However, Windows will not have the ability to change it or act as a server if it is connected at DOS.
|Options in the Windows directory are:|
From here you can add the sound card and any other accessories you may want. Many of them include the drivers they need and add them to Windows. I will have to experiment with that next.
To minimize the space required for the Windows (and any other added programs), any files I don't normally need (Help Files, Control Panel Files, Etc.) can be stored in separate ZIP files. When I need to make changes, I can add them while I make the changes. By keeping track of what files those are, I can delete them when the changes are complete. A Batch File would work for that.
This keeps the unpack time down when starting and minimizes the size of the Ramdisk required. Unzipping 14mb of 300 plus files takes much longer than unzipping 5mb of 90 files. You could, of course, load and run Windows from a ZIP disk (or a CDROM or Network), but that defeats the speed increase of running on a Ramdisk.
Run Windows 3.x from Floppys
First you need a boot disk using DOS 6.2 or 6.22.
Now you use DBLSPACE to compress the disk.
The COMMAND.COM should be the only file on A drive (now compressed). The other files should remain on the uncompressed drive (now R drive).
Copy the following files to the now compressed disk:
Make a windows and windows\system directory. Copy:
to the Windows directory. This may be the only file in these directories. There are 2 reasons for this.
1) EMM386.EXE needs to be loaded at boot. Windows will look for it in the same location when it starts. So this file must be on both disks.
2) If you are in the A:\windows\ directory and change disks and there is no a:\Windows\ directory on the new disk, the doublespace will unmount and you will crash.
Next create a CONFIG.SYS file with the following lines in it:
Save that to the A:\ drive (compressed).
Next create the AUTOEXEC.BAT with the following:
Save that to the A:\ drive (compressed). You can add other drivers such as a CDROM driver, ZIP Drive driver, and/or Network drivers. With the exception of the EMM386.EXE and the COMMAND.COM, none of these files will be needed after the boot. If you want flexibility, create a BOOT MENU. With that you can choose bare Windows, Networking, CDROM and/or ZIP Drive or a combination of these.
Next you prepare the second disk. This will contain the minimum Windows files listed above. You can add what other files you can fit on the disk. This disk will also be compressed. But the whole disk will be used for the compressed file. Start with a blank disk and select:
Now copy the windows files to the disk. You should also copy COMMAND.COM to the root of this disk.
Note: If you are copying Windows files from C drive, INI files and GRP files may be pointing to C drive. You must modify these for them to work on A drive.
The first disk is the Boot disk. This second disk is the Windows start disk. These should get you into Windows. But I suggest a third disk which you could call Windows Run. This could have other files to make Windows do what you want and other programs you want to run after Windows has started.
Once Windows is started, I find that it does not need most of its files. So you can insert a third disk with other files and programs you want to run that would not fit on the second disk. You could add such files to the first disk. But it may have little space left. You could probably create several compressed disks with files for what you want to run. You will have to experiment to see what files you can get along without on each disk and still run the Windows the way you want.
While this makes it possible to save work to a floppy disk, it is important that each floppy disk used is compressed and has the same file structure on it. If you put a standard (non compressed) floppy in the drive and try to read it or write to it, the Doublespace will unmount the disk and the system will crash.
I did this using Windows.3.11 WFW. Older computers such as a 286 cannot use Windows 3.11 as it has no Standard Mode. While this method will work for Windows 3.1, I don't know if Doublespace will work on a 286 computer.
|PoliTalk Technical Menu|
Comment to PoliTalk
And That's My|