I have a question about Do I still need CONFIG.SYS and AUTOEXEC.BAT?:

My Autoexecbat file in ME contains the folowing:- SET BLASTER=A220 I5 D1 T4 SET PATH=C:\PROGRA~1\COMMON~1\MICROS~1\MSInfo\;;C:\WINDOWS;C:\WINDOWS\COMMAND SET PROMPT=$p$g SET TEMP=C:\WINDOWS\TEMP SET TMP=C:\WINDOWS\TEMP SET COMSPEC=C:\WINDOWS\COMMAND.COM SET windir=C:\WINDOWS SET winbootdir=C:\WINDOWS I cannot get rid of these entries. I do not have any legacy hardware. Can anyone suggest what is loading these devices. I understand the blaster is the sound card loading a legacy driver for DOS but how can I stop it. Cheers Rod Gayford

[Reply or follow-up to this message]

I'm not 100% sure but if you run msconfig and click on the autoexec.bat tab, you can edit or uncheck them. I would like to know the answer because I have some of those starting on my system also.


On Sunday, November 24, 2002 at 4:24 am, Rod Gayford wrote:
>I have a question about Do
>I still need CONFIG.SYS and AUTOEXEC.BAT?:

>My Autoexecbat file in ME contains the folowing:-
>
>SET BLASTER=A220 I5 D1 T4
>SET PATH=C:\PROGRA~1\COMMON~1\MICROS~1\MSInfo\;;C:\WINDOWS;C:\WINDOWS\COMMAND
>SET PROMPT=$p$g
>SET TEMP=C:\WINDOWS\TEMP
>SET TMP=C:\WINDOWS\TEMP
>SET COMSPEC=C:\WINDOWS\COMMAND.COM
>SET windir=C:\WINDOWS
>SET winbootdir=C:\WINDOWS
>I cannot get rid of these entries. I do not have any legacy hardware. Can anyone
>suggest what is loading these devices. I understand the blaster is the sound card
>loading a legacy driver for DOS but how can I stop it.
>Cheers
>
>Rod Gayford
>
>

[Reply or follow-up to this message]

If you do not have legacy drivers (and judging from what's here, even if you do have legacy drivers), you don't need this stuff. The SET BLASTER part is telling Windows the DMA, IRQ, and other stuff for a Sound Blaster card. Most of the rest is about paths, that post Windows 3.11 is done internally. The Prompt $p$g is how the command prompt will look. The COMSPEC specifies what command interpreter you're using, which was useless even in the olden days. Get rid of it, leave it, frankly doesn't matter...


On Sunday, November 24, 2002 at 4:24 am, Rod Gayford wrote:
>I have a question about Do
>I still need CONFIG.SYS and AUTOEXEC.BAT?:

>My Autoexecbat file in ME contains the folowing:-
>
>SET BLASTER=A220 I5 D1 T4
>SET PATH=C:\PROGRA~1\COMMON~1\MICROS~1\MSInfo\;;C:\WINDOWS;C:\WINDOWS\COMMAND
>SET PROMPT=$p$g
>SET TEMP=C:\WINDOWS\TEMP
>SET TMP=C:\WINDOWS\TEMP
>SET COMSPEC=C:\WINDOWS\COMMAND.COM
>SET windir=C:\WINDOWS
>SET winbootdir=C:\WINDOWS
>I cannot get rid of these entries. I do not have any legacy hardware. Can anyone
>suggest what is loading these devices. I understand the blaster is the sound card
>loading a legacy driver for DOS but how can I stop it.
>Cheers
>
>Rod Gayford
>
>

[Reply or follow-up to this message]

Rod,

You're confusing device drivers with environment variables. All of the lines in the 
autoexec.bat you listed are environment variables. Your system needs most, if not 
all of them. The set blaster line is particularly useful if you play any games based 
in DOS, not Wndows, like older versions of Castle Wolfenstien, or DOOM, QUAKE, or 
other games of that type. If you remove it, you won't have any sound in your DOS 
based games.

You won't save any memory (to speak of) and you won't have any confllicts if you 
leave them alone.

If you had a device driver, your batch file lines would refer to them with a DOS 
filename ending with .COM  .EXE or even .SYS

Those you can stop from executing by adding REM to the first FOUR characters in the 
line involved. FOUR means to include the [SPACE] character after the REM, i.e. :

REM MOUSE.COM

would stop your system from loading the mouse driver.

I hope this helps!

Good luck!





On Sunday, November 24, 2002 at 4:24 am, Rod Gayford wrote:

>I have a question about Do 

>I still need CONFIG.SYS and AUTOEXEC.BAT?:


>My Autoexecbat file in ME contains the folowing:-

>

>SET BLASTER=A220 I5 D1 T4

>SET PATH=C:\PROGRA~1\COMMON~1\MICROS~1\MSInfo\;;C:\WINDOWS;C:\WINDOWS\COMMAND

>SET PROMPT=$p$g

>SET TEMP=C:\WINDOWS\TEMP

>SET TMP=C:\WINDOWS\TEMP

>SET COMSPEC=C:\WINDOWS\COMMAND.COM

>SET windir=C:\WINDOWS

>SET winbootdir=C:\WINDOWS

>I cannot get rid of these entries. I do not have any legacy hardware. Can anyone 

>suggest what is loading these devices. I understand the blaster is the sound card 

>loading a legacy driver for DOS but how can I stop it.

>Cheers

>

>Rod Gayford

>

>
 

[Reply or follow-up to this message]

Actually, the path information is still required by some programs, and everything 
is not done internally by Windows. Windows does load some things internally, but 
not everything. It's still there to allow for both current programs, and for legacy 
program compatibility.

The SET COMSPEC variable is also important to many systems, as it allows you to load 
an alternative operating system, and in some cases, a system file can be hidden to 
protect the file from being tampered with by someone with malicious intent.

Removing and/or changing your CONFIG.SYS and AUTOEXEC.BAT files can stop some programs, 
even Windows based ones from functioning properly.

Tinker if you like, but you might want to save copies of your files in a ZIP archive 
before you edit them and end up needing to restore them to their previous state. 

Good luck!








On Tuesday, March 18, 2003 at 9:30 am, John wrote:

>If you do not have legacy drivers (and judging from what's here, even if you do 
have 

>legacy drivers), you don't need this stuff.  The SET BLASTER part is telling Windows 

>the DMA, IRQ, and other stuff for a Sound Blaster card.

>

>Most of the rest is about paths, that post Windows 3.11 is done internally.  The 

>Prompt $p$g is how the command prompt will look.  The COMSPEC specifies what command 

>interpreter you're using, which was useless even in the olden days.

>

>Get rid of it, leave it, frankly doesn't matter...

>
 

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum