MS-DOS Shell Fails to Start (77624)
The information in this article applies to:
• Microsoft MS-DOS operating system 5.0
This article was previously published under Q77624
SYMPTOMS
MS-DOS Shell won't start after you type dosshell at the MS-DOS command prompt. Or, you cannot switch
between another program and MS-DOS Shell.
CAUSE
This problem can be caused by any of the following:
• Incorrect video files for a monochrome monitor
• A conflict with memory-resident drivers or programs
• Incorrect or corrupted MS-DOS Shell files
Read the Workaround section of this article, and try the procedures
that apply to your computer. If, after performing these steps, you
still have problems with MS-DOS Shell, contact Microsoft Product
Support Services.
NOTE: If you are a network administrator and you have local computers
running MS-DOS Shell files from a network DOS directory, contact
Microsoft Product Support Services.
WORKAROUND
Incorrect Video Files for a Monochrome Monitor
Sometimes Setup improperly identifies monochrome monitors and expands
incorrect video files. If your computer has a monochrome monitor and
you can't start MS-DOS Shell, expand the correct video files as
follows:
• Delete the DOSSHELL.VID file. For example, if the file is in the
DOS subdirectory, type the following at the MS-DOS command prompt:
• Preserve the DOSSHELL.INI file by renaming it with a different
extension, such as .OLD or .BAK. For example, if this file is
located in your DOS subdirectory, type the following command at
the MS-DOS command prompt:
ren c:\dos\dosshell.ini c:\dos\dosshell.old
• Use the following syntax to expand and copy the new files to your
DOS directory:
expand [drive1:][path1]mono.in_ [drive2:][path2]dosshell.ini
expand [drive1:][path1]mono.gr_ [drive2:][path2]dosshell.grb
This syntax renames the files as they are expanded and copied.
The [drive1:][path1] parameter specifies the location of the
compressed file you want to expand. The [drive2:][path2] parameter
specifies the location of the expanded file. The MONO.IN_ and
MONO.GR_ files are on Disk 3 (5.25-inch disks) or Disk 2 (3.5-inch
disks).
For example, if the MONO.IN_ file is on a disk in drive A, and you
want to expand the file to the DOS directory on drive C, type the
following at the MS-DOS command prompt:
expand a:\mono.in_ c:\dos\dosshell.ini
If DOS Shell works now, you have solved the problem.
Removing Memory-Resident Programs and Drivers
MS-DOS Shell might not work properly if a memory-resident program or
driver is running. If you are having problems with MS-DOS Shell, try
starting your computer without running memory-resident programs and
drivers.
To start your computer without running memory-resident programs or
drivers:
• Create a system disk by inserting a formatted disk into drive A
and typing the following:
• Make sure the system disk is in drive A and restart your computer
by pressing CTRL+ALT+DEL.
• To determine whether your CONFIG.SYS and AUTOEXEC.BAT files are
causing problems, type the following at the MS-DOS command prompt:
If MS-DOS Shell starts, one or both of these files are probably
causing problems. If MS-DOS Shell doesn't start, these files might
not be causing problems, in which case you should skip to the next
procedure, "Incorrect or Corrupt MS-DOS Shell Files."
• Remove the system disk from drive A and restart your computer by
pressing CTRL+ALT+DEL.
• To determine whether your AUTOEXEC.BAT file is causing problems,
rename your CONFIG.SYS file by typing the following at the MS-DOS
command prompt:
ren config.sys config.bac
• Restart your computer by pressing CTRL+ALT+DEL and type the
following at the MS-DOS command prompt:
If MS-DOS Shell doesn't start, your AUTOEXEC.BAT file is causing
problems; proceed to step 7.
If MS-DOS Shell starts, the problem is probably with your
CONFIG.SYS file, not your AUTOEXEC.BAT file; skip to step 11.
• Use a text editor, such as MS-DOS Editor, to open the AUTOEXEC.BAT
file. If you want to use MS-DOS Editor, type the following
command:
• Insert the REM command in front of every command in your
AUTOEXEC.BAT file except the @ECHO OFF, PROMPT, and PATH commands.
For example, your AUTOEXEC.BAT might look like the following:
rem dos\share
@echo off
prompt $p$g
path c:\dos
rem temp=c:\temp
rem tmp=c:\temp
rem init=c:\init
rem start workstation
rem logon joeblow
rem netime time
rem net use l: \\john\doe
rem net use lpt1: \\john\doe
rem mode spe=high
rem cd \qs
rem quickshr - - - y \qs
rem cd \
• Save your AUTOEXEC.BAT file. If you're using MS-DOS Editor, choose
Save from the File menu.
• To determine which command is causing a problem, remove the first
REM command from the first command line. Save your AUTOEXEC.BAT
file, restart your computer by pressing CTRL+ALT+DEL, and try to
start MS-DOS Shell by typing dosshell at the MS-DOS command prompt.
Repeat these steps until MS-DOS Shell does not start. When it
doesn't start, you have identified a command that conflicts with
MS-DOS Shell.
• Restart your computer by typing CTRL+ALT+DEL. Then rename your
CONFIG.SYS file by typing the following at the MS-DOS command
prompt:
ren config.bac config.sys
• To determine whether your CONFIG.SYS file is causing problems,
rename your AUTOEXEC.BAT file by typing the following at the
MS-DOS command prompt:
ren autoexec.bat autoexec.bac
• Restart your computer by pressing CTRL+ALT+DEL and type the
following at the MS-DOS command prompt:
If MS-DOS Shell doesn't start, your CONFIG.SYS file is causing
problems; proceed to step 14.
If MS-DOS Shell starts, there is probably no problem with your
CONFIG.SYS file; skip to step 20.
• Use a text editor, such as MS-DOS Editor, to open your CONFIG.SYS
file. If you are using MS-DOS Editor, type the following at the
MS-DOS command prompt:
c:\dos\edit c:\config.sys
• Insert the REM command in front of every command in your
CONFIG.SYS file except lines with device drivers that are needed
to run computer hardware, such as a disk drive, monitor, or
keyboard, and lines with FILES and BUFFERS commands. Make sure to
type the REM command in front of the mouse driver command, if any.
• Change the FILES and BUFFERS commands to the following:
If your CONFIG.SYS file does not have these commands, add them.
• Save your CONFIG.SYS file.If you're using MS-DOS Editor, choose
Save from the File menu.
• To determine which driver is causing a problem, remove the first
occurrence of the REM command from a command line. Save your
CONFIG.SYS file, restart your computer by pressing CTRL+ALT+DEL,
and try starting MS-DOS Shell by typing c:\dos\dosshell at the MS-DOS command prompt. Repeat these steps
until MS-DOS Shell does not start. When it doesn't start, you have
identified a command that conflicts with MS-DOS Shell.
• Rename your AUTOEXEC.BAT file by typing the following at the
MS-DOS command prompt:
ren c:\autoexec.bac c:\autoexec.bat
• When you have identified the commands that are causing problems,
insert the REM command in front of the same commands in the
AUTOEXEC.BAT and/or CONFIG.SYS files on drive C. Then restart your
computer and try using MS-DOS Shell. If the MS-DOS Shell still
doesn't start, you might have more than one command in one or both
files that are causing problems. In this case, repeat steps 5
through 19 as applicable.
When you have identified the drivers and/or programs that are
causing problems, you have two options:
• If the drivers and/or programs are not essential, you can disable
them with the REM command, as described earlier in this procedure.
• You can contact the manufacturers of the drivers and/or programs for
further assistance.
Incorrect or Corrupt MS-DOS Shell Files
Sometimes Setup identifies your monitor incorrectly and copies the
wrong video files to your system. Also, sometimes video or MS-DOS
Shell files become corrupted during or after setup. MS-DOS Shell won't
work properly if the following files are incorrect or corrupted:
DOSSHELL.EXE
DOSSHELL.GRB
DOSSHELL.INI
DOSSWAP.EXE
DOSSHELL.COM
DOSSHELL.VID
If you are having problems with MS-DOS Shell, try manually expanding
these files from your Setup disks, as follows:
• Preserve DOSSHELL.INI by backing it up with the COPY command. For
example, if this file is in the DOS directory, change to the DOS
directory by typing cd \dos at the
MS-DOS command prompt. Then type the following command:
copy dosshell.ini dosshell.old
• Use the following syntax to expand and copy the following files to
your DOS directory:
expand [drive1:][path1]dosshell.ex_ [drive2:][path2]dosshell.exe
expand [drive1:][path1]dosshell.co_ [drive2:][path2]dosshell.com
expand [drive1:][path1]dosswap.ex_ [drive2:][path2]dosswap.exe
The [drive1:][path1] parameter specifies the location of the
compressed file you want to expand. The [drive2:][path2] parameter
specifies the location of the expanded file. These files are on
Disk 3 (5.25-inch disks) or Disk 2 (3.5-inch disks).
For example, if the DOSSHELL.EX_ file is on a disk in drive A, and
you want to expand the file to the \DOS directory on drive C, type
the following at the MS-DOS command prompt:
expand a:\dosshell.ex_ c:\dos\dosshell.exe
• Find your monitor type below, and expand and rename the files by
typing the specified commands. The files are on Disk 3 (5.25-inch
disks) or Disk 2 (3.5-inch disks).
Monochrome
----------
expand a:\mono.gr_ c:\dos\dosshell.grb
expand a:\mono.in_ c:\dos\dosshell.ini
Note that a monochrome monitor does not require a .VID file.
CGA
---
expand a:\cga.gr_ c:\dos\dosshell.grb
expand a:\cga.in_ c:\dos\dosshell.ini
expand a:\cga.vi_ c:\dos\dosshell.vid
EGA
---
expand a:\ega.gr_ c:\dos\dosshell.grb
expand a:\ega.in_ c:\dos\dosshell.ini
expand a:\ega.vi_ c:\dos\dosshell.vid
EGA Monochrome
--------------
expand a:\egamono.gr_ c:\dos\dosshell.grb
expand a:\mono.in_ c:\dos\dosshell.ini
expand a:\ega.vi_ c:\dos\dosshell.vid
VGA (Super VGA, XGA, and other high-resolution monitors)
--------------------------------------------------------
expand a:\vga.gr_ c:\dos\dosshell.grb
expand a:\ega.in_ c:\dos\dosshell.ini
expand a:\vga.vi_ c:\dos\dosshell.vid
8514 Color
----------
expand a:\vga.gr_ c:\dos\dosshell.grb
expand a:\ega.in_ c:\dos\dosshell.ini
expand a:\ega.vi_ c:\dos\dosshell.vid
VGA Monochrome (VGA, Super VGA,
XGA, and other high-resolution monitors)
----------------------------------------
expand a:\vgamono.gr_ c:\dos\dosshell.grb
expand a:\mono.in_ c:\dos\dosshell.ini
expand a:\vga.vi_ c:\dos\dosshell.vid
8514 Monochrome
---------------
expand a:\vgamono.gr_ c:\dos\dosshell.grb
expand a:\mono.in_ c:\dos\dosshell.ini
expand a:\cga.vi_ c:\dos\dosshell.vid
Hercules
--------
expand a:\herc.gr_ c:\dos\dosshell.grb
expand a:\mono.in_ c:\dos\dosshell.ini
expand a:\herc.vi_ c:\dos\dosshell.vid
| Modification Type: |
Major |
Last Reviewed: |
11/22/1999 |
| Keywords: |
KB77624 |
|