• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Command Prompt

There actually wasn't a autoexec.nt in system32, found it in repair folder mind you so i've copied it in and it now works (don't know how that happened anyways) ta

Electronic Punk

Staff member
Political User
Here are the contents of mine anyway, may be default... (should be), may not be :)

@echo off

REM AUTOEXEC.BAT is not used to initialize the MS-DOS environment.
REM AUTOEXEC.NT is used to initialize the MS-DOS environment unless a
REM different startup file is specified in an application's PIF.

REM Install CD ROM extensions
lh %SystemRoot%\system32\mscdexnt.exe

REM Install network redirector (load before dosx.exe)
lh %SystemRoot%\system32\redir

REM Install DPMI support
lh %SystemRoot%\system32\dosx

REM The following line enables Sound Blaster 2.0 support on NTVDM.
REM The command for setting the BLASTER environment is as follows:
REM    SET BLASTER=A220 I5 D1 P330
REM    where:
REM        A    specifies the sound blaster's base I/O port
REM        I    specifies the interrupt request line
REM        D    specifies the 8-bit DMA channel
REM        P    specifies the MPU-401 base I/O port
REM        T    specifies the type of sound blaster card
REM                 1 - Sound Blaster 1.5
REM                 2 - Sound Blaster Pro I
REM                 3 - Sound Blaster 2.0
REM                 4 - Sound Blaster Pro II
REM                 6 - SOund Blaster 16/AWE 32/32/64
REM    The default value is A220 I5 D1 T3 and P330.  If any of the switches is
REM    left unspecified, the default value will be used. (NOTE, since all the
REM    ports are virtualized, the information provided here does not have to
REM    match the real hardware setting.)  NTVDM supports Sound Blaster 2.0 only.
REM    The T switch must be set to 3, if specified.
SET BLASTER=A220 I5 D1 P330 T3

REM To disable the sound blaster 2.0 support on NTVDM, specify an invalid
REM SB base I/O port address.  For example:


OSNN Senior Addict
Moonwraith said:
Has anyone seen this error before?
I can't access command prompt at all :wow: Anyone know the cause?
As mentioned in another answer I made,the autoexec and / or config.nt files are sometimes accidently deleted in some SP2 upgrades, depending on your system... but as you found, the "repair" folder in Windows keeps copies.
This will throw up 16 or 32 bit application run error messages
I'm still on XP home from the box, haven't bothered upgrading (didn't like sp2 when i had it) and i've formatted since then. Hmm, not a clue what would have deleted it

Members online

No members online now.

Latest posts

Latest profile posts

Hello, is there anybody in there? Just nod if you can hear me ...
What a long strange trip it's been. =)

Forum statistics

Latest member