CompuServe Messages

I too looked at your startup files and thought they looked like redundant city. Seemed like a file cabinet full with no folders. Here's a technique I use to create the most efficient setup for different operating sessions. 1. Create a dir called startup 2. Create another DIR called batch. 3. Do NOT list these in your path. 4. The last two lines in each autoexec.bat will be: CD\batch Type Menu.txt 5. an optional third line can state the startup mode eg: Echo System started for WFW and scanner drivers 6. Create an optimized config.sys and autoexec.bat file pair for each of your session modes. Locate them in the \startup dir. but name them with different ext to denote the mode eg. config.scn for scanner and autoexec.scn as well. 7. In the \batch dir create a menu.txt as follows with any text editor. STARTUP MODES: 1) WFW and scanner drivers 2) Lantastic Network 3) Clean boot no drivers 4) 3DS and targa+ drivers w/ QEMM 5) 3DS and targa+ drivers w/o QEMM LAUNCH SOFTWARE: 10) 3ds with RDPADI renderer 11) 3ds with RCPADI renderer 12) 3ds with RDPADI & Diaquest VTR 20) Launch WFW with targa+ 21) Launch WFW with SVGA TC 22) Launch WFW with SVGA 1024×768 256color etc. get creative here because this will be your low level screen in dos 8. Create a batch file for each of the entries as follows: @echo off echo echo echo Copying startup files to root directory. echo for reboot to Windows for Workgroups. copy c:\startup\config.wfw c:\config.sys copy c:\startup\autoexec.wfw c:\autoexec.bat echo echo echo Hit CTRL-ALT-DELETE now to reboot! Note: I wrote a small file called boot.com in debug that I put in instead of the three finger command. It is listed as follows: echo echo Machine will reboot pause boot.com Name the file 1.bat. 9. The launch files are done somewhat differently, might be simple or might be complex as in 3DS + Diaquest launch: d: cd\3ds set RCPADI=D:\3ds\drivers\RCPVESA.exp set RDPADI=D:\3ds\drivers\RDPTPLUS.exp set targa=248 rem load tconfig batch call c:\targa\51248632.bat call DQ50P copy 3dsset.dq5 3ds.set copy 3daditar.cfg 3dadi.cfg 3dshell c: cd\batch cls type menu.txt Name this file 12.bat 10. Use the above examples to customize your entire system and optimize a most efficient startup for each work session. The smaller the startup files the better. You can even loadhi the stuff in the launch files although this can be a bit tricky due to the permutations involved. To additionally maximize efficiency I have a number of 3DS.set and 3dadi files that I switch for 3DS. I also have several win.ini and system.ini files although managing the windows ini files gets cumbersom during new software installation. I haven't figured a slick way to handle this yet other than manually copy and paste