If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#31
|
|||
|
|||
"Buffalo" wrote in message
news:%boqd.110131$5K2.55239@attbi_s03... "glee" wrote in message ... Why are you loading DOS drivers for the CD-ROM drive, for use in Windows? Unless your CD-ROM drive is ancient, you should let Windows load its protected mode driver. Loading real mode drivers is likely putting the CD drive in DOS compatibility mode, reducing its performance in Windows. -- Glen Ventura, MS MVP W95/98 Systems http://dts-l.org/goodpost.htm I guess I am a little confused. If I restart in DOS ('command prompt only' from the Startup Menu) I cannot access my cd drive if I don't have that entry in my autoexec.bat. When in Windows, there is no indication that the cd-rom drive is using DOS compatibility mode drivers. I know I am missing something, but perhaps you can explain it further. Also, any idea why my path statement suddenly stopped giving me the 'too many parameters' error? SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;"C:\Program Files\NortonSystemWorks\Norton Ghost\";C:\PROGRA~1\ATITEC~1\ATICON~1 Perhaps I should just set msconfig not to process the autoexec.bat and the config.sys. Why do you need access to the CD drive from Command Prompt Only on the Startup Menu (boot menu)? If you want to boot to DOS Mode with CD-ROM support, you should use the Restart in MS-DOS Mode option on the StartShutdown menu in Windows, and either load the drivers in Config.sys and Dosstart.bat, OR use 'Specify a new configuration' in the Exit To DOS.PIF and create custom startup files within the ..pif (Alternately you can boot with a boot floppy with CDROM support). Loading all those DOS drivers just for use in Command Prompt Only from the boot menu is a waste of memory, among other things, and for no good reason. BTW, Windows will likely bypass those DOS drivers during startup so that you are not in compatibility mode. I have not seen documentation of it but I have seen it happen in practice. SFB's suggestion of creating a menu using your autoexec.bat and config.sys is a good idea if you insist on having CD access from Command Prompt Only. You should be able to create a menu that will bypass drivers in a boot to windows, but will give you the option to load the DOS drivers if you go to Command Prompt Only. Are you sure the "Too many parameters' error was due to the Path statement, and not some other line? -- Glen Ventura, MS MVP W95/98 Systems http://dts-l.org/goodpost.htm |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Autoexec.bat | Javad | General | 4 | November 22nd 04 11:49 PM |
Autoexec.bat | Dave | Improving Performance | 4 | October 8th 04 12:30 AM |
Reading Autoexec.bat | Dingus | Software & Applications | 12 | August 25th 04 08:35 PM |
Major errors in config.sys & Autoexec.bat | Kim | Setup & Installation | 4 | August 2nd 04 02:23 AM |
UNC Path bug ? | Skybuck Flying | Networking | 2 | June 23rd 04 10:42 AM |