os2fan2 Posted July 24, 2009 Share Posted July 24, 2009 There are some useful things ye can do to the setup files, to allow for modern hardware.1. In SYSTEM.INI [386Enh], set "PageOverCommit=2". This prevents windows creating too big a page file. If you want to modify the source, the file to unpack is SYSTEM.SR_. 2. If ye have more than 20 MB, consider either having no paging file, or a very tiny one. The default is three times memory, which was fine when computers had 2M of ram, but it really does not need it these days. I never used a paging file on 20 MB ram, with no ill effects.3. Windows 3.x does not check files. You could pretty much add/subtract anything from setup.ini. I've been doing custom Windows since 1994. There is a file size limit of 64 KB on Setup.ini, so it's pretty much what ye can cull. 4. If ye have an upgrade version, the upgrade check is "does win.com exist?" 5. The auto-setup file is Setup.shh. This is the 'winnt.sif' kind of setup.6. You can use setup /a to unpack the files, and setup /n to create a minimal directory. Note here that the home directory will have just win.com and winver.exe, along with the .INI files. A neat trick here is that you can stick all of the .EXE files (like write, winhelp, &c into a different pathed directory, to stop them being over written. A program like DDEEXEC, take command/16 or Norton's group.exe (from NU8 or something), does quite nicely at creating and populating groups. One of my windows versions is a minimal one with just progman.exe, to which i use DOS batch files (with MAINTINI.EXE) and some Windows things to add not just the desktop, but all of the user apps as well. Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now