Now Reading
Slimming Down Home windows 3.1/3.11

Slimming Down Home windows 3.1/3.11

2024-02-24 01:04:46








Slimming Down Home windows 3.1/3.11





      The brand new applications preserve requiring an increasing number of house. However most of the recordsdata will not be crucial. All of the recordsdata you could want for each doable pc this system could also be put in and are cluttering up your arduous drive. Home windows 3.11 freshly put in with a community card takes up about 14mb. However the precise Home windows runable is lower than 2mb.


      You’ll be able to run Home windows from floppy disks. I’ve succeeded utilizing two 1.44mb floppys in a pc with no arduous drive. This technique can get you by on the minimal reminiscence wanted for Home windows 3.x, as little as 4mb. That is appropriate for older computer systems with little reminiscence, whether or not or not they’ve a tough drive. Utilizing DMF formatting, you could possibly run from a single disk.


      Since at this time’s computer systems are utilizing FAT 32 partitions which Home windows 3.1 cannot run on, I’ve been experimenting with Ramdisks. My Packard Bell 386 (20mhz) has solely 16mb of ram. If I create a 14mb Ramdisk to run it on, there’s not sufficient reminiscence left to run it. So I peared Home windows down to suit. At this level it’s about 5mb whole on a 9mb ramdisk. It has a 2mb swap file additionally on the ramdisk. So I’ve about 2mb extra space that I can fill and about 7mb of reminiscence left for applications to run on. Way over to 2 to 4 mb of RAM the pc had after I first used Home windows 3.1.



      As a result of it’s in ram reminiscence, shifting from window to window is kind of quick. It transfer extra like a 486×50. Time will inform how effectively different applications wil run on this “gradual” pc.


 

Beginning From Scratch



      The minimal recordsdata that Home windows will run from are:


Within the Home windows Listing you want:
 essential.grp 5120   progman.exe 115312   reg.dat 2825   win.com 50904 
 mouse.ini 24   progman.ini 238   system.ini 2452   win.ini 3464 
These recordsdata whole: 180,155 bytes
 
Within the Windowssystem Listing you want:
 comm.drv 5968   mmsound.drv 3440   person.exe 264096   vgasys.fon 7280 
 dosx.exe 32682   mmsystem.dll 61648   vga.3gr 16384   vtdapi.386 5245 
 gdi.exe 220800   mouse.drv 10672   vga.drv 73200   win386.exe 577557 
 keyboard.drv 7568   shell.dll 40944   vgafix.fon 5360   winoa386.mod 49248 
 krnl386.exe 76400   system.drv 2304   vgaoem.fon 5168   wswap.exe 16302 
These recordsdata whole: 1,482,266
The full for Home windows is: 1,662,421 bytes.
These two recordsdata will change relying on the Video driver you load:  vga.3gr  vga.drv
For those who load Tremendous VGA, they are going to be:  vddsvga.386  svga256.drv



      Now, in fact it’s void of any applications. So it’s simply there. So now you add the recordsdata you want for no matter applications the recordsdata are wanted for. You’ll be able to preserve many recordsdata in reserve till they’re wanted. Assist recordsdata you in all probability will not want after you have the Home windows arrange the way in which you need it. CPL recordsdata aren’t wanted except it is advisable to change one thing with the CONTROL PANEL.

The Menus Teams


      Lets begin with the Menus. These are the GRP extension recordsdata. Home windows 3.11 creates the next (Foremost.grp was skipped because it was included within the Required part):


Within the Home windows Listing you want:
 accessor.grp 8723  The Equipment Group  community.grp 6508  The Community Group
 video games.grp 42  The Video games Group  startup.grp 44  The Startup Group
 dosprmpt.pif 545  DOS Immediate PIF  _default.pif 545  Default PIF Supply

The Management Panel



      The management panel is simply required when it is advisable to modify settings. The recordsdata required by this are:


 management.exe   The Management Panel  management.ini 148592  Management Panel Info
 cpwin386.cpl 111760  The Home windows Setup Program  essential.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  
Moreover, these applications will want:
 lzexpand.dll 23712  All   ver.dll 9696  All 
 ncdw.dll 41264  All   wfwsetup.dll 337008  All 
 setup.inf 57701  All   commctrl.dll 48112  File supervisor 
 commdlg.dll 97936  A number of   community.inf 58618  Community Setup-Vendor  
 winnet.inf 14691  Community Setup-Vendor 
These recordsdata whole: 1,020,251 bytes



      These recordsdata could possibly be saved in a ZIP file or different location till wanted.

The Community
DOS


      In case you are working a Community Card with Home windows For Workgroups 3.11, you’ll need the next recordsdata:


To function solely as a consumer (DOS or Home windows):
 ifshlp.sys 4548     ndishlp.sys 4464     
 web.exe 433829  The DOS Networking Program  web.msg 75697   
 neth.msg 122333     protman.dos 21940   
 protman.exe 13782     protocol.ini 528  Set Up by Home windows
 wfwsys.cfg 840  arrange by Home windows  de22x.dos 28832  Card driver from vendor
 ipxodi.com 39748  Protocol driver from vendor



      The Community might be linked at DOS and might be accessible in Home windows. Nevertheless, Home windows is not going to have the power to alter it or act as a server whether it is linked at DOS.

The Community
Home windows


      Internet Begin have to be run earlier than beginning Home windows. Nevertheless, the Community shouldn’t be Logged on to at DOS. To run the Community from Home windows, you want the next recordsdata within the SYSTEM listing:


 ifsmgr.386 65625   lpt.386 5917   ndis.386 27846   ndis2sup.386 23224 
 netbeui.386 37043   nwlink.386 33316   nwnblink.386 37988   serial.386 11112 
 vcache.386 9862   vcomm.386 5688   vnetsup.386 14647   vpmtd.386 5653 
 vredir.386 85746   vserver.386 101054   vshare.386 14925   wfwnet.drv 308864 
Choices within the Home windows listing are:
 logonoff.exe 8192   winmeter.exe 92992   winpopup.exe 28528   netwatch.exe 40448 
 msmail.exe 302502   rasstart.exe 13312       netwatch.exe 40448 



      From right here you may add the sound card and another equipment it’s your decision. A lot of them embrace the drivers they want and add them to Home windows. I must experiment with that subsequent.


 

Storage


      Since I run this on a Ramdisk, I’ve to repeat the recordsdata to the Ramdisk every time the pc is re-booted. I retailer them in a ZIP file created by PKware’s PKZIP program. This may be saved on a tough drive, a ZIP disk, Floppy disks, or a Community Drive. As I make modifications to Home windows, I need to replace the ZIP recordsdata.



      To attenuate the house required for the Home windows (and another added applications), any recordsdata I do not usually want (Assist Information, Management Panel Information, And so on.) might be saved in separate ZIP recordsdata. Once I have to make modifications, I can add them whereas I make the modifications. By holding observe of what recordsdata these are, I can delete them when the modifications are full. A Batch File would work for that.



      This retains the unpack time down when beginning and minimizes the dimensions of the Ramdisk required. Unzipping 14mb of 300 plus recordsdata takes for much longer than unzipping 5mb of 90 recordsdata. You may, in fact, load and run Home windows from a ZIP disk (or a CDROM or Community), however that defeats the pace enhance of working on a Ramdisk.


 


Run Home windows 3.x from Floppys


      Since a RAMDISK is utilizing reminiscence, on older machines which have little or no, say 3 or 4mb, when you load file to a Ramdisk, there will not be sufficient to run Home windows. Utilizing DOUBLE SPACE or DRIVE SPACE, you may match a working Home windows on a single 1.44 floppy disk. Nevertheless, the boot recordsdata wanted plus the Home windows recordsdata are slightly an excessive amount of for one disk. However there’s a approach. This Home windows, just like the Ramdisk Home windows might be run on a pc with no arduous drive.

See Also


      First you want a boot disk utilizing DOS 6.2 or 6.22.

The first step: Make a boot disk. Put a clean floppy disk in drive A. Get to the C:> immediate and sort:
sys a:
When it’s completed it is best to have:

IO.SYS

MSDOS.SYS

COMMAND.COM

DBLSPACE.BIN
on the disk (DRVSPACE.BIN if utilizing DOS 6.22). You’ll need so as to add:

DBLSPACE.INI
which you’ll create containing the strains:

AutoMount=1

FirstDrive=R

LastDrive=R

MaxRemovableDrives=1

MaxFileFragments=111

ActivateDrive=r,A0
Set the Attrib for this file to R,H,S.




Now you utilize DBLSPACE to compress the disk.

DBLSPACE /COMPRESS A:

will create a compressed file dblspace.000 on the floppy disk in drive A and Mount it. The precise Drive A will develop into Drive R (the letter I’ve specified within the dblspace.ini file).



The COMMAND.COM must be the one file on A drive (now compressed). The opposite recordsdata ought to stay on the uncompressed drive (now R drive).



Copy the next recordsdata to the now compressed disk:


command.com

dblspace.sys

himem.sys

mem.exe




Make a home windows and windowssystem listing. Copy:



to the Home windows listing. This can be the one file in these directories. There are 2 causes for this.

1) EMM386.EXE must be loaded at boot. Home windows will search for it in the identical location when it begins. So this file have to be on each disks.

2) In case you are within the A:home windows listing and alter disks and there’s no a:Home windows listing on the brand new disk, the doublespace will unmount and you’ll crash.



Subsequent create a CONFIG.SYS file with the next strains in it:

DEVICE=HIMEM.SYS /testmem:off

DEVICE=windowsEMM386.EXE noems

DOS=HIGH,UMB

recordsdata=40

buffers=40

STACKS=9,256

lastdrive=Z

shell=a:command.com /p

devicehigh=DBLSPACE.SYS /transfer




Save that to the A: drive (compressed).



Subsequent create the AUTOEXEC.BAT with the next:

echo off

path=a:;a:home windows

immediate=$p$g




Save that to the A: drive (compressed). You’ll be able to add different drivers corresponding to a CDROM driver, ZIP Drive driver, and/or Community drivers. Except for the EMM386.EXE and the COMMAND.COM, none of those recordsdata might be wanted after the boot. In order for you flexibility, create a BOOT MENU. With which you could select naked Home windows, Networking, CDROM and/or ZIP Drive or a mix of those.



Subsequent you put together the second disk. This can include the minimum Windows recordsdata listed above. You’ll be able to add what different recordsdata you may match on the disk. This disk may also be compressed. However the entire disk might be used for the compressed file. Begin with a clean disk and choose:



Now copy the home windows recordsdata to the disk. You also needs to copy COMMAND.COM to the foundation of this disk.


Be aware: In case you are copying Home windows recordsdata from C drive, INI recordsdata and GRP recordsdata could also be pointing to C drive. It’s essential to modify these for them to work on A drive.



The primary disk is the Boot disk. This second disk is the Home windows begin disk. These ought to get you into Home windows. However I recommend a 3rd disk which you might name Home windows Run. This might produce other recordsdata to make Home windows do what you need and different applications you need to run after Home windows has began.

THE OPERATION


      If you boot from the boot disk the compressed drive is mounted earlier than you see a DOS immediate. You may add directions within the autoexec.bat if you need telling you while you run the subsequent disk. When the boot stops, you may place the second disk with Home windows on it within the drive. Offered you don’t trigger the drive to be accessed whereas the disk is out, it ought to suppose it’s nonetheless on the identical compressed drive. Nevertheless, you now can kind WIN and begin Home windows. Chances are you’ll get an error that the DBLSPACE.BIN can’t be discovered. Nevertheless, Home windows appeared to work despite this. That file was on the boot disk. So it’s not accessible after you alter disks.


      As soon as Home windows is began, I discover that it doesn’t want most of its recordsdata. So you may insert a 3rd disk with different recordsdata and applications you need to run that might not match on the second disk. You may add such recordsdata to the primary disk. However it might have little house left. You may in all probability create a number of compressed disks with recordsdata for what you need to run. You’ll have to experiment to see what recordsdata you will get alongside with out on every disk and nonetheless run the Home windows the way in which you need.


      Whereas this makes it doable to save lots of work to a floppy disk, it’s important that every floppy disk used is compressed and has the identical file construction on it. For those who put an ordinary (non compressed) floppy within the drive and attempt to learn it or write to it, the Doublespace will unmount the disk and the system will crash.


      I did this utilizing Home windows.3.11 WFW. Older computer systems corresponding to a 286 can not use Home windows 3.11 because it has no Commonplace Mode. Whereas this technique will work for Home windows 3.1, I do not know if Doublespace will work on a 286 pc.










Up to date August 20, 2002





1

Source Link

What's Your Reaction?
Excited
0
Happy
0
In Love
0
Not Sure
0
Silly
0
View Comments (0)

Leave a Reply

Your email address will not be published.

2022 Blinking Robots.
WordPress by Doejo

Scroll To Top