|
Faster BootingPart 1The biggest improvement I've found (about 25 seconds on my system) is dropping ndis2sup from the system startup. If you want to do this, use Boot Log Analyzer to check for load failures. If you see a line that says "Loadfailed =ndis2sup.vxd", your system is not equipped to use this file so it's safe to dump it. Follow these steps:
Recovery: If your system (particularly networking) misbehaves immediately after this, you can restore your original settings by:
I spent a full day testing and timing various configuration changes, registry hacks, and other tips and have found significant improvements in these two changes. Part 2Using the System Information utility, I disabled Scan Registry. (SYSINFO.EXE/Tools/System Configuration Utility/Startup) or more directly (MSCONFIG.EXE/Startup) This cut another 18 seconds off my startup time.
This change will prevent daily backups of the registry from being made (something the Win98 does in its default configuration). However, I manually force backups as part of my usual day-end shutdown, when I also optimize the registry (using RegClean and Norton's WinDoctor) and defrag the drive (using Norton's SpeedDisk). To make manual backups easy, you can create an shortcut for scanregw.exe, and using properties add "/backup" to the end of the command line. Clicking on this will cause your current registry to be backed up immediately. This is extremely useful just prior to making a major installation on the system. Click here to download a desktop shortcut that will back up your registry.
Faster System OperationYou can cut the amount of time dedicated to defragging way down by using Norton Speed Disk and setting it up with some consideration for keeping its workload down. First, fix your swapfile minimum size at 2-3 times the size of your RAM. (I have 128M RAM, and an 8GB drive formatted in a single partition, so I set my swapfile min and max both at 384MB.) Speed Disk moved this down to the bottom of the drive where it gets fast access when needed. Since the size is fixed, it never gets fragmented and, more importantly, never contributes to the fragmentation of other files on the drive. Second, configure Speed Disk to put the drivers and program files (*.exe, *.dll, *.386, *.sys, *.ocx, *.vxd) at the beginning of the drive for fast access, and since they change infrequently, they'll rarely become fragmented if they're stored together. Third, set parameters in Speed Disk to move the bulky, unchanging files on the system to the top of the drive. These files (*.hlp, *.zip, *.chm, *.cab, *.gid, \windows\help\*\*) include help files and compressed installation files that are not frequently accessed and rarely (if ever) changed. Since large portions of the drive no longer become fragmented, system performance stays high, and these areas don't require any attention during defrags, cutting down defrag time. All that's left is the middle section of the drive which contains the files that do get regularly updated, and they can be cleaned up quickly. After doing this to my own system, fragmentation is now such a low level issue that it needs to be done only every week or two, and it usually takes only 10 or 15 minutes. Works for me . . .
|