Reference Issue / Question
MS-DOS Our main MS-DOS and Windows command line page.
MS-DOS The dictionary definition and related links on MS-DOS.
AC Additional help and information on autoexec.bat / config.sys
Batch file Additional help and information on MS-DOS batch files.
Boot disk Additional help and information on bootable diskettes.
CD-ROM Issues and help relating to CD-ROM drives.
Files Additional help and information with handling computer files.
Floppy Issues and help relating to the computer floppy drive.
Hard drive Issues and help relating to hard drive.
MODEM Issues and help relating to fax, modem or Internet.
Mouse Issues and help relating to the computer mouse.
Printer Issues and help relating to the computer printer.
Prompt How do I change the Prompt?
Sound card Issues and help relating to the sound card.
History The history of MS-DOS.
CHDOS How to get to a MS-DOS prompt.
CHMSDOS Basic Microsoft DOS troubleshooting.
CH000008 Location of QBasic in Windows 95 / Windows 98.
CH000009 How to hide a file in MS-DOS.
CH000010 Deleting files in MS-DOS without a prompt.
CH000011 What is an external / internal command?
CH000012 Receiving error "Missing command interpreter."
CH000013 Emm386 error #00
CH000014 How do I scroll in MS-DOS?
CH000015 Each time the computer boots I receive a prompt for the time and date.
CH000016 Missing 1MB of system memory.
CH000017 Ways of locating hardware and other system specifications.
CH000018 I have a C Drive and H drive, what is H?
CH000020 How to resize a full screen Windows command prompt (DOS) window.
CH000022 In DOS how to copy all files from one drive to another.
CH000140 Windows computer only starts in MS-DOS.
CH000175 Do you have additional information on FDISK /MBR?
CH000177 Can you type more than one command at one command prompt?
CH000209 Information on long file names.
CH000210 When the computer boots I see 'Bad Command or File name'.
CH000226 Partition shows up as a MS-DOS partition.
CH000229 Invalid System Disk error.
CH000257 Receive error 'Too many parameters'.
CH000309 How to find a file in MS-DOS.
CH000321 How to shut down / restart the computer with a batch file.
CH000323 How to quickly replace the file extensions of several files.
CH000325 Out of environment space.
CH000356 How to restart or shutdown the computer in DOS.
CH000361 MS-DOS issues with Windows ME.
CH000382 Stack overflow system halted.
CH000395 COMMAND.COM vs. CMD.EXE
CH000398 How to create a file in MS-DOS.
CH000440 How does MS-DOS interpret commands?
CH000481 Additional information about MS-DOS 7.0
CH000484 How to change the prompt.
CH000515 How do I change drives in MS-DOS?
CH000532 How to rename or label a disk drive.
CH000540 How to change the title of a MS-DOS Window.
CH000561 How to install a software program.
CH000562 Switching between MS-DOS Windows in Windows.
CH000598 How do I execute a file from MS-DOS.
CH000619 Command line vs. GUI.
CH000640 How can I obtain the file for an external MS-DOS command?
CH000671 Do I need to have MS-DOS on my computer?
CH000736 What is the MS-DOS command to get back into Windows?
CH000738 Preventing a MS-DOS window from automatically closing in Windows.
CH000742 How to create a directory / folder.
CH000743 How do I delete a file or folder?
CH000766 How do I copy files?
CH000769 How do I determine the size of a file?
CH000772 How do I print a listing of files in a directory?
CH000795 How do I change directories?
CH000797 Is MS-DOS case sensitive?
CH000805 How do I copy and paste in a MS-DOS window?
CH000838 How to copy a directory / folder.
CH000846 How do I change the name of a file or folder?
CH000866 How do I install MS-DOS?
CH000872 Information and help with the io.sys file.
CH000928 What is the MS-DOS path for the Windows desktop?
CH001005 How can I disable the Windows command prompt?
CH001038 How do I view the name or label of a drive?
FORUM If your question is not listed on this page please try our online forum.
Friday, September 19, 2008
Microsoft DOS History & TOP 10 COMMAND PAGES
Microsoft DOS HistoryYear Event
1981 MS-DOS 1.0 was released August, 1981.
1982 MS-DOS 1.25 was released August, 1982.
1983 MS-DOS 2.0 was released March, 1983.
1984 Microsoft introduces MS-DOS 3.0 for the IBM PC AT and MS-DOS 3.1 for networks.
1986 MS-DOS 3.2 was released April, 1986.
1987 MS-DOS 3.3 was released April, 1987.
1988 MS-DOS 4.0 was released July, 1988.
1988 MS-DOS 4.01 was released November, 1988.
1991 MS-DOS 5.0 was released June, 1991.
1993 MS-DOS 6.0 was released August, 1993.
1993 MS-DOS 6.2 was released November, 1993
1994 MS-DOS 6.21 was released March, 1994
1994 MS-DOS 6.22 was released April, 1994
MS-DOS top 10 commandsQuick links
DOS top 10 commands
DOS top 10 command pages
See all of Computer Hope's Top 10's
MS-DOS help page
DOS TOP 10 COMMANDS
Below is a listing of the top 10 MS-DOS commands most commonly used and that you will most likely use during a normal DOS session.
1. cd
2. dir
3. copy
4. del
5. edit
6. move
7. ren (rename)
8. deltree
9. cls
10. format
TOP 10 COMMAND PAGES
Below is a listing of the top 10 MS-DOS command pages by the amount of times they have been accessed on the Computer Hope server.
1. fdisk
2. format
3. copy
4. xcopy
5. dir
6. cd
7. deltree
8. net
9. Ansi
10. ping
1981 MS-DOS 1.0 was released August, 1981.
1982 MS-DOS 1.25 was released August, 1982.
1983 MS-DOS 2.0 was released March, 1983.
1984 Microsoft introduces MS-DOS 3.0 for the IBM PC AT and MS-DOS 3.1 for networks.
1986 MS-DOS 3.2 was released April, 1986.
1987 MS-DOS 3.3 was released April, 1987.
1988 MS-DOS 4.0 was released July, 1988.
1988 MS-DOS 4.01 was released November, 1988.
1991 MS-DOS 5.0 was released June, 1991.
1993 MS-DOS 6.0 was released August, 1993.
1993 MS-DOS 6.2 was released November, 1993
1994 MS-DOS 6.21 was released March, 1994
1994 MS-DOS 6.22 was released April, 1994
MS-DOS top 10 commandsQuick links
DOS top 10 commands
DOS top 10 command pages
See all of Computer Hope's Top 10's
MS-DOS help page
DOS TOP 10 COMMANDS
Below is a listing of the top 10 MS-DOS commands most commonly used and that you will most likely use during a normal DOS session.
1. cd
2. dir
3. copy
4. del
5. edit
6. move
7. ren (rename)
8. deltree
9. cls
10. format
TOP 10 COMMAND PAGES
Below is a listing of the top 10 MS-DOS command pages by the amount of times they have been accessed on the Computer Hope server.
1. fdisk
2. format
3. copy
4. xcopy
5. dir
6. cd
7. deltree
8. net
9. Ansi
10. ping
MS-DOS extended errors
DEC HEX Description
00 00h No error
01 01h Function number invalid
02 02h File not found
03 03h Path not found
04 04h Too many open tiles (no file handles available)
05 05h Access denied
06 06h Invalid handle
07 07h Memory control block destroyed
08 08h Insufficient memory
09 09h Memory block address invalid
10 0Ah Environment invalid (usually >32k in length)
11 0Bh Format invalid
12 0Ch Access code invalid
13 0Dh Data invalid
14 0Eh (reserved)
15 0Fh Invalid drive
16 10h Attempted to remove current directory
17 11h Not same device
18 12h No more tiles
19 13h Disk write-protected
20 14h Unknown unit
21 15h Drive not ready
22 16h Unknown command
23 17h Data error (CRC)
24 18h Bad request structure length
25 19h Seek error
26 1Ah Unknown media type (non-DOS disk)
27 1Bh Sector not found
28 1Ch Printer out of paper
29 1Dh Write fault
30 1Eh Read fault
31 1Fh General failure
32 20h Sharing violation
33 21h Lock violation
34 22h Disk change invalid
35 23h FCB unavailable
36 24h Sharing buffer invalid
37 25h (DOS 4+) code page mismatch
38 26h (DOS 4+) cannot complete file operation (out of input)
39 27h (DOS 4+) insufficient disk space
40 28h (reserved)
41 29h (reserved)
42 2Ah (reserved)
43 2Bh (reserved)
44 2Ch (reserved)
45 2Dh (reserved)
46 2Eh (reserved)
47 2Fh (reserved)
48 30h (reserved)
49 31h (reserved)
50 32h Network request not supported
51 33h Remote computer not listening
52 34h Duplicate name on network
53 35h Network name not found
54 36h Network busy
55 37h Network device no longer exists
56 38h Network BIOS command limit exceeded
57 39h Network adapter hardware error
58 3Ah Incorrect response from network
59 3Bh Unexpected network error
60 3Ch Incompatible remote adapter
61 3Dh Print queue full
62 3Eh Queue not full
63 3Fh Not enough space to print file
64 40h Network name was deleted
65 41h Network access denied
66 42h Network device type incorrect
67 43h Network name not found
68 44h Network name limit exceeded
69 45h Network BIOS session limit exceeded
70 46h Temporarily paused
71 47h Network request not accepted
72 48h Network print / disk redirection paused
73 49h (LANtastic) invalid network version
74 4Ah (LANtastic) account expired
75 4Bh (LANtastic) password expired
76 4Ch (LANtastic) login attempted invalid at this time
77 4Dh (LANtastic) disk limit exceed on network node
78 4Eh (LANtastic) not logged in to network node
79 4Fh (reserved)
80 50h File exists
81 51h (reserved)
82 52h Cannot make directory
83 53h Fail on INT 24h
84 54h (DOS 3.3+) too many redirections
85 55h (DOS 3.3+) duplicate redirection
86 56h (DOS 3.3+) invalid password
87 57h (DOS 3.3+) invalid parameter
88 58h (DOS 3.3+) network write fault
89 59h (DOS 4+) function not supported on network
90 5Ah (DOS 4+) required system component not installed
00 00h No error
01 01h Function number invalid
02 02h File not found
03 03h Path not found
04 04h Too many open tiles (no file handles available)
05 05h Access denied
06 06h Invalid handle
07 07h Memory control block destroyed
08 08h Insufficient memory
09 09h Memory block address invalid
10 0Ah Environment invalid (usually >32k in length)
11 0Bh Format invalid
12 0Ch Access code invalid
13 0Dh Data invalid
14 0Eh (reserved)
15 0Fh Invalid drive
16 10h Attempted to remove current directory
17 11h Not same device
18 12h No more tiles
19 13h Disk write-protected
20 14h Unknown unit
21 15h Drive not ready
22 16h Unknown command
23 17h Data error (CRC)
24 18h Bad request structure length
25 19h Seek error
26 1Ah Unknown media type (non-DOS disk)
27 1Bh Sector not found
28 1Ch Printer out of paper
29 1Dh Write fault
30 1Eh Read fault
31 1Fh General failure
32 20h Sharing violation
33 21h Lock violation
34 22h Disk change invalid
35 23h FCB unavailable
36 24h Sharing buffer invalid
37 25h (DOS 4+) code page mismatch
38 26h (DOS 4+) cannot complete file operation (out of input)
39 27h (DOS 4+) insufficient disk space
40 28h (reserved)
41 29h (reserved)
42 2Ah (reserved)
43 2Bh (reserved)
44 2Ch (reserved)
45 2Dh (reserved)
46 2Eh (reserved)
47 2Fh (reserved)
48 30h (reserved)
49 31h (reserved)
50 32h Network request not supported
51 33h Remote computer not listening
52 34h Duplicate name on network
53 35h Network name not found
54 36h Network busy
55 37h Network device no longer exists
56 38h Network BIOS command limit exceeded
57 39h Network adapter hardware error
58 3Ah Incorrect response from network
59 3Bh Unexpected network error
60 3Ch Incompatible remote adapter
61 3Dh Print queue full
62 3Eh Queue not full
63 3Fh Not enough space to print file
64 40h Network name was deleted
65 41h Network access denied
66 42h Network device type incorrect
67 43h Network name not found
68 44h Network name limit exceeded
69 45h Network BIOS session limit exceeded
70 46h Temporarily paused
71 47h Network request not accepted
72 48h Network print / disk redirection paused
73 49h (LANtastic) invalid network version
74 4Ah (LANtastic) account expired
75 4Bh (LANtastic) password expired
76 4Ch (LANtastic) login attempted invalid at this time
77 4Dh (LANtastic) disk limit exceed on network node
78 4Eh (LANtastic) not logged in to network node
79 4Fh (reserved)
80 50h File exists
81 51h (reserved)
82 52h Cannot make directory
83 53h Fail on INT 24h
84 54h (DOS 3.3+) too many redirections
85 55h (DOS 3.3+) duplicate redirection
86 56h (DOS 3.3+) invalid password
87 57h (DOS 3.3+) invalid parameter
88 58h (DOS 3.3+) network write fault
89 59h (DOS 4+) function not supported on network
90 5Ah (DOS 4+) required system component not installed
MS-DOS extended errors
DEC HEX Description
00 00h No error
01 01h Function number invalid
02 02h File not found
03 03h Path not found
04 04h Too many open tiles (no file handles available)
05 05h Access denied
06 06h Invalid handle
07 07h Memory control block destroyed
08 08h Insufficient memory
09 09h Memory block address invalid
10 0Ah Environment invalid (usually >32k in length)
11 0Bh Format invalid
12 0Ch Access code invalid
13 0Dh Data invalid
14 0Eh (reserved)
15 0Fh Invalid drive
16 10h Attempted to remove current directory
17 11h Not same device
18 12h No more tiles
19 13h Disk write-protected
20 14h Unknown unit
21 15h Drive not ready
22 16h Unknown command
23 17h Data error (CRC)
24 18h Bad request structure length
25 19h Seek error
26 1Ah Unknown media type (non-DOS disk)
27 1Bh Sector not found
28 1Ch Printer out of paper
29 1Dh Write fault
30 1Eh Read fault
31 1Fh General failure
32 20h Sharing violation
33 21h Lock violation
34 22h Disk change invalid
35 23h FCB unavailable
36 24h Sharing buffer invalid
37 25h (DOS 4+) code page mismatch
38 26h (DOS 4+) cannot complete file operation (out of input)
39 27h (DOS 4+) insufficient disk space
40 28h (reserved)
41 29h (reserved)
42 2Ah (reserved)
43 2Bh (reserved)
44 2Ch (reserved)
45 2Dh (reserved)
46 2Eh (reserved)
47 2Fh (reserved)
48 30h (reserved)
49 31h (reserved)
50 32h Network request not supported
51 33h Remote computer not listening
52 34h Duplicate name on network
53 35h Network name not found
54 36h Network busy
55 37h Network device no longer exists
56 38h Network BIOS command limit exceeded
57 39h Network adapter hardware error
58 3Ah Incorrect response from network
59 3Bh Unexpected network error
60 3Ch Incompatible remote adapter
61 3Dh Print queue full
62 3Eh Queue not full
63 3Fh Not enough space to print file
64 40h Network name was deleted
65 41h Network access denied
66 42h Network device type incorrect
67 43h Network name not found
68 44h Network name limit exceeded
69 45h Network BIOS session limit exceeded
70 46h Temporarily paused
71 47h Network request not accepted
72 48h Network print / disk redirection paused
73 49h (LANtastic) invalid network version
74 4Ah (LANtastic) account expired
75 4Bh (LANtastic) password expired
76 4Ch (LANtastic) login attempted invalid at this time
77 4Dh (LANtastic) disk limit exceed on network node
78 4Eh (LANtastic) not logged in to network node
79 4Fh (reserved)
80 50h File exists
81 51h (reserved)
82 52h Cannot make directory
83 53h Fail on INT 24h
84 54h (DOS 3.3+) too many redirections
85 55h (DOS 3.3+) duplicate redirection
86 56h (DOS 3.3+) invalid password
87 57h (DOS 3.3+) invalid parameter
88 58h (DOS 3.3+) network write fault
89 59h (DOS 4+) function not supported on network
90 5Ah (DOS 4+) required system component not installed
00 00h No error
01 01h Function number invalid
02 02h File not found
03 03h Path not found
04 04h Too many open tiles (no file handles available)
05 05h Access denied
06 06h Invalid handle
07 07h Memory control block destroyed
08 08h Insufficient memory
09 09h Memory block address invalid
10 0Ah Environment invalid (usually >32k in length)
11 0Bh Format invalid
12 0Ch Access code invalid
13 0Dh Data invalid
14 0Eh (reserved)
15 0Fh Invalid drive
16 10h Attempted to remove current directory
17 11h Not same device
18 12h No more tiles
19 13h Disk write-protected
20 14h Unknown unit
21 15h Drive not ready
22 16h Unknown command
23 17h Data error (CRC)
24 18h Bad request structure length
25 19h Seek error
26 1Ah Unknown media type (non-DOS disk)
27 1Bh Sector not found
28 1Ch Printer out of paper
29 1Dh Write fault
30 1Eh Read fault
31 1Fh General failure
32 20h Sharing violation
33 21h Lock violation
34 22h Disk change invalid
35 23h FCB unavailable
36 24h Sharing buffer invalid
37 25h (DOS 4+) code page mismatch
38 26h (DOS 4+) cannot complete file operation (out of input)
39 27h (DOS 4+) insufficient disk space
40 28h (reserved)
41 29h (reserved)
42 2Ah (reserved)
43 2Bh (reserved)
44 2Ch (reserved)
45 2Dh (reserved)
46 2Eh (reserved)
47 2Fh (reserved)
48 30h (reserved)
49 31h (reserved)
50 32h Network request not supported
51 33h Remote computer not listening
52 34h Duplicate name on network
53 35h Network name not found
54 36h Network busy
55 37h Network device no longer exists
56 38h Network BIOS command limit exceeded
57 39h Network adapter hardware error
58 3Ah Incorrect response from network
59 3Bh Unexpected network error
60 3Ch Incompatible remote adapter
61 3Dh Print queue full
62 3Eh Queue not full
63 3Fh Not enough space to print file
64 40h Network name was deleted
65 41h Network access denied
66 42h Network device type incorrect
67 43h Network name not found
68 44h Network name limit exceeded
69 45h Network BIOS session limit exceeded
70 46h Temporarily paused
71 47h Network request not accepted
72 48h Network print / disk redirection paused
73 49h (LANtastic) invalid network version
74 4Ah (LANtastic) account expired
75 4Bh (LANtastic) password expired
76 4Ch (LANtastic) login attempted invalid at this time
77 4Dh (LANtastic) disk limit exceed on network node
78 4Eh (LANtastic) not logged in to network node
79 4Fh (reserved)
80 50h File exists
81 51h (reserved)
82 52h Cannot make directory
83 53h Fail on INT 24h
84 54h (DOS 3.3+) too many redirections
85 55h (DOS 3.3+) duplicate redirection
86 56h (DOS 3.3+) invalid password
87 57h (DOS 3.3+) invalid parameter
88 58h (DOS 3.3+) network write fault
89 59h (DOS 4+) function not supported on network
90 5Ah (DOS 4+) required system component not installed
MS-DOS & Windows command line errors
MS-DOS & Windows command line errors
When attempting to rename a file, the file does not exist or there is already a file with that name. Verify no other file exists with the same name in the current directory and/or that you're typing the file you wish to rename correctly.
Abort, Retry, Fail?
This error is commonly encountered when attempting to read a diskette that is not readable or if no disk or disc in the drive trying to be read.
Additional information about problems reading floppy diskettes can be found on document CH000579.
Information about why a CD Disc, DVD or other type of disc is not working can be found on document CH000031.
Access denied
Often caused when the file or directory has read-only attributes, is being modified by another person or program on the computer, and/or other network permissions that prevent it from being deleted or modified.
See our attrib command for additional information about this command and options.
Bad command or file name
Commonly caused by a misspelling or error when typing a command and/or when the command attempting to be used is not a valid command for your version of MS-DOS or Windows.
Bad or missing command interpreter
The computer cannot locate the command.com, an important file that that enables the computer to boot into the operating system. See document CH000012 for additional information and help with this error message.
Cannot perform a cyclic copy
This error occurs when you're trying to copy or xcopy all directories and files and that directory also contains the directory you're copying all the files to. If this command were to be allowed it would get into a loop and would never stop copying the same files over and over. When using the xcopy command if you're copying all subdirectories you must copy those files and folders to a completely separate directory or drive.
Divide overflow
Program has attempted to divide something by zero. This error is often caused by an error in the program you're running on your computer. Verify there are no available patches or other updates for the software you're using on your computer.
Drive not ready error
Disk or disc in the drive is not readable.
Additional information about problems reading floppy diskettes can be found on document CH000579.
Information about why a CD Disc, DVD or other type of disc is not working can be found on document CH000031.
Duplicate file name or file not found
When attempting to rename a file, the file does not exist or there is already a file with that name. Verify no other file exists with the same name in the current directory and/or that you're typing the file you wish to rename correctly.
File cannot be copied onto itself
An attempt to copy a file could not be completed because the file already exists or same source and destination. Copy the file to an alternate drive or directory.
File creation error
Directory could be full because of the DOS limitation of files in one directory, the file already exist, and/or the file was not copied correctly. Try creating or copying the file in a different directory.
File not found
The file you attempted to list, copy, or edit does not exist in the directory you're in. Verify you're in the correct directory and that the file exists in that directory.
This error may also occur if you're using a back slash instead of a forward slash for switches on commands. For example, doing dir \p instead of the proper dir /p.
General Failure
An unknown error has occurred that is not known by MS-DOS. If this is given when trying to read the hard drive, you may need to format the hard drive as it could be failing or already bad.
Insufficient disk space
Disk is full or, if you are trying to copy am file to a disk, the file is too big to fit on the disk.
Additional information about determining available disk drive space can be found on document CH000369.
Internal stack overflow
The MS-DOS internal storage areas are full. You may need to go into your config.sys and increase the STACKS=0,0
Information about editing and viewing the config.sys can be found on our autoexec.bat and config.sys page.
Invalid directory
The directory or path you attempted to enter does not exist in the directory or drive you're currently in.
Invalid drive specification
The drive letter you're typing does not exist on the computer.
Invalid file name or file not found
This error occurs when attempting to rename, copy, or otherwise manipulate a file the file does not exist. Verify you're typing the file you wish to rename correctly.
Invalid media, track 0 bad or unusable
Format command cannot format the specified disk or the disk capacity is invalid, or bad disk.
Additional information about errors that occur while reading/writing a disk drive can be found on document CH000379.
Invalid number of parameters
When the command was typed, something was left out that DOS needed by the command, it was mistyped, or a space was placed where one was not needed.
This error commonly occurs when you're typing a directory in the MS-DOS or the Windows command line that has spaces in it. For example using the xcopy command to copy files in the Documents and Settings folder. When typing a directory with spaces in MS-DOS make sure to surround the path with quotes. For example, instead of typing c:\documents and settings type "c:\documents and settings".
Invalid parameter
Typed a command correctly but specified the incorrect parameter, such as format /z.
Invalid Switch
The wrong slash was typed, for example: cd/ instead of cd\.
Non-System disk or disk error
See document CH000229 for additional information and help with this error.
Not ready, reading drive X
The drive letter you're typing does not exist on the computer or there is no disk or disc in the drive.
Parse error
This error occurs when the command you're typing in has invalid syntax. For example, if you're surrounding your path in quotes and leave out the ending quotes.
The system cannot find the drive specified.
The drive letter you're typing does not exist on the computer.
The system cannot find the file specified.
This error occurs when attempting to rename, copy, or otherwise manipulate a file the file does not exist. Verify you're typing the file you wish to rename correctly.
The system cannot find the path specified.
The directory or path you attempted to enter does not exist in the directory or drive you're currently in.
Write fault error
Tried to reroute text to a device that is not connected, is not valid or not hooked up.
Write protect
Tried to write to a disk that is write protected.
When attempting to rename a file, the file does not exist or there is already a file with that name. Verify no other file exists with the same name in the current directory and/or that you're typing the file you wish to rename correctly.
Abort, Retry, Fail?
This error is commonly encountered when attempting to read a diskette that is not readable or if no disk or disc in the drive trying to be read.
Additional information about problems reading floppy diskettes can be found on document CH000579.
Information about why a CD Disc, DVD or other type of disc is not working can be found on document CH000031.
Access denied
Often caused when the file or directory has read-only attributes, is being modified by another person or program on the computer, and/or other network permissions that prevent it from being deleted or modified.
See our attrib command for additional information about this command and options.
Bad command or file name
Commonly caused by a misspelling or error when typing a command and/or when the command attempting to be used is not a valid command for your version of MS-DOS or Windows.
Bad or missing command interpreter
The computer cannot locate the command.com, an important file that that enables the computer to boot into the operating system. See document CH000012 for additional information and help with this error message.
Cannot perform a cyclic copy
This error occurs when you're trying to copy or xcopy all directories and files and that directory also contains the directory you're copying all the files to. If this command were to be allowed it would get into a loop and would never stop copying the same files over and over. When using the xcopy command if you're copying all subdirectories you must copy those files and folders to a completely separate directory or drive.
Divide overflow
Program has attempted to divide something by zero. This error is often caused by an error in the program you're running on your computer. Verify there are no available patches or other updates for the software you're using on your computer.
Drive not ready error
Disk or disc in the drive is not readable.
Additional information about problems reading floppy diskettes can be found on document CH000579.
Information about why a CD Disc, DVD or other type of disc is not working can be found on document CH000031.
Duplicate file name or file not found
When attempting to rename a file, the file does not exist or there is already a file with that name. Verify no other file exists with the same name in the current directory and/or that you're typing the file you wish to rename correctly.
File cannot be copied onto itself
An attempt to copy a file could not be completed because the file already exists or same source and destination. Copy the file to an alternate drive or directory.
File creation error
Directory could be full because of the DOS limitation of files in one directory, the file already exist, and/or the file was not copied correctly. Try creating or copying the file in a different directory.
File not found
The file you attempted to list, copy, or edit does not exist in the directory you're in. Verify you're in the correct directory and that the file exists in that directory.
This error may also occur if you're using a back slash instead of a forward slash for switches on commands. For example, doing dir \p instead of the proper dir /p.
General Failure
An unknown error has occurred that is not known by MS-DOS. If this is given when trying to read the hard drive, you may need to format the hard drive as it could be failing or already bad.
Insufficient disk space
Disk is full or, if you are trying to copy am file to a disk, the file is too big to fit on the disk.
Additional information about determining available disk drive space can be found on document CH000369.
Internal stack overflow
The MS-DOS internal storage areas are full. You may need to go into your config.sys and increase the STACKS=0,0
Information about editing and viewing the config.sys can be found on our autoexec.bat and config.sys page.
Invalid directory
The directory or path you attempted to enter does not exist in the directory or drive you're currently in.
Invalid drive specification
The drive letter you're typing does not exist on the computer.
Invalid file name or file not found
This error occurs when attempting to rename, copy, or otherwise manipulate a file the file does not exist. Verify you're typing the file you wish to rename correctly.
Invalid media, track 0 bad or unusable
Format command cannot format the specified disk or the disk capacity is invalid, or bad disk.
Additional information about errors that occur while reading/writing a disk drive can be found on document CH000379.
Invalid number of parameters
When the command was typed, something was left out that DOS needed by the command, it was mistyped, or a space was placed where one was not needed.
This error commonly occurs when you're typing a directory in the MS-DOS or the Windows command line that has spaces in it. For example using the xcopy command to copy files in the Documents and Settings folder. When typing a directory with spaces in MS-DOS make sure to surround the path with quotes. For example, instead of typing c:\documents and settings type "c:\documents and settings".
Invalid parameter
Typed a command correctly but specified the incorrect parameter, such as format /z.
Invalid Switch
The wrong slash was typed, for example: cd/ instead of cd\.
Non-System disk or disk error
See document CH000229 for additional information and help with this error.
Not ready, reading drive X
The drive letter you're typing does not exist on the computer or there is no disk or disc in the drive.
Parse error
This error occurs when the command you're typing in has invalid syntax. For example, if you're surrounding your path in quotes and leave out the ending quotes.
The system cannot find the drive specified.
The drive letter you're typing does not exist on the computer.
The system cannot find the file specified.
This error occurs when attempting to rename, copy, or otherwise manipulate a file the file does not exist. Verify you're typing the file you wish to rename correctly.
The system cannot find the path specified.
The directory or path you attempted to enter does not exist in the directory or drive you're currently in.
Write fault error
Tried to reroute text to a device that is not connected, is not valid or not hooked up.
Write protect
Tried to write to a disk that is write protected.
MS-DOS & Windows command line errors
MS-DOS & Windows command line errors
When attempting to rename a file, the file does not exist or there is already a file with that name. Verify no other file exists with the same name in the current directory and/or that you're typing the file you wish to rename correctly.
Abort, Retry, Fail?
This error is commonly encountered when attempting to read a diskette that is not readable or if no disk or disc in the drive trying to be read.
Additional information about problems reading floppy diskettes can be found on document CH000579.
Information about why a CD Disc, DVD or other type of disc is not working can be found on document CH000031.
Access denied
Often caused when the file or directory has read-only attributes, is being modified by another person or program on the computer, and/or other network permissions that prevent it from being deleted or modified.
See our attrib command for additional information about this command and options.
Bad command or file name
Commonly caused by a misspelling or error when typing a command and/or when the command attempting to be used is not a valid command for your version of MS-DOS or Windows.
Bad or missing command interpreter
The computer cannot locate the command.com, an important file that that enables the computer to boot into the operating system. See document CH000012 for additional information and help with this error message.
Cannot perform a cyclic copy
This error occurs when you're trying to copy or xcopy all directories and files and that directory also contains the directory you're copying all the files to. If this command were to be allowed it would get into a loop and would never stop copying the same files over and over. When using the xcopy command if you're copying all subdirectories you must copy those files and folders to a completely separate directory or drive.
Divide overflow
Program has attempted to divide something by zero. This error is often caused by an error in the program you're running on your computer. Verify there are no available patches or other updates for the software you're using on your computer.
Drive not ready error
Disk or disc in the drive is not readable.
Additional information about problems reading floppy diskettes can be found on document CH000579.
Information about why a CD Disc, DVD or other type of disc is not working can be found on document CH000031.
Duplicate file name or file not found
When attempting to rename a file, the file does not exist or there is already a file with that name. Verify no other file exists with the same name in the current directory and/or that you're typing the file you wish to rename correctly.
File cannot be copied onto itself
An attempt to copy a file could not be completed because the file already exists or same source and destination. Copy the file to an alternate drive or directory.
File creation error
Directory could be full because of the DOS limitation of files in one directory, the file already exist, and/or the file was not copied correctly. Try creating or copying the file in a different directory.
File not found
The file you attempted to list, copy, or edit does not exist in the directory you're in. Verify you're in the correct directory and that the file exists in that directory.
This error may also occur if you're using a back slash instead of a forward slash for switches on commands. For example, doing dir \p instead of the proper dir /p.
General Failure
An unknown error has occurred that is not known by MS-DOS. If this is given when trying to read the hard drive, you may need to format the hard drive as it could be failing or already bad.
Insufficient disk space
Disk is full or, if you are trying to copy am file to a disk, the file is too big to fit on the disk.
Additional information about determining available disk drive space can be found on document CH000369.
Internal stack overflow
The MS-DOS internal storage areas are full. You may need to go into your config.sys and increase the STACKS=0,0
Information about editing and viewing the config.sys can be found on our autoexec.bat and config.sys page.
Invalid directory
The directory or path you attempted to enter does not exist in the directory or drive you're currently in.
Invalid drive specification
The drive letter you're typing does not exist on the computer.
Invalid file name or file not found
This error occurs when attempting to rename, copy, or otherwise manipulate a file the file does not exist. Verify you're typing the file you wish to rename correctly.
Invalid media, track 0 bad or unusable
Format command cannot format the specified disk or the disk capacity is invalid, or bad disk.
Additional information about errors that occur while reading/writing a disk drive can be found on document CH000379.
Invalid number of parameters
When the command was typed, something was left out that DOS needed by the command, it was mistyped, or a space was placed where one was not needed.
This error commonly occurs when you're typing a directory in the MS-DOS or the Windows command line that has spaces in it. For example using the xcopy command to copy files in the Documents and Settings folder. When typing a directory with spaces in MS-DOS make sure to surround the path with quotes. For example, instead of typing c:\documents and settings type "c:\documents and settings".
Invalid parameter
Typed a command correctly but specified the incorrect parameter, such as format /z.
Invalid Switch
The wrong slash was typed, for example: cd/ instead of cd\.
Non-System disk or disk error
See document CH000229 for additional information and help with this error.
Not ready, reading drive X
The drive letter you're typing does not exist on the computer or there is no disk or disc in the drive.
Parse error
This error occurs when the command you're typing in has invalid syntax. For example, if you're surrounding your path in quotes and leave out the ending quotes.
The system cannot find the drive specified.
The drive letter you're typing does not exist on the computer.
The system cannot find the file specified.
This error occurs when attempting to rename, copy, or otherwise manipulate a file the file does not exist. Verify you're typing the file you wish to rename correctly.
The system cannot find the path specified.
The directory or path you attempted to enter does not exist in the directory or drive you're currently in.
Write fault error
Tried to reroute text to a device that is not connected, is not valid or not hooked up.
Write protect
Tried to write to a disk that is write protected.
When attempting to rename a file, the file does not exist or there is already a file with that name. Verify no other file exists with the same name in the current directory and/or that you're typing the file you wish to rename correctly.
Abort, Retry, Fail?
This error is commonly encountered when attempting to read a diskette that is not readable or if no disk or disc in the drive trying to be read.
Additional information about problems reading floppy diskettes can be found on document CH000579.
Information about why a CD Disc, DVD or other type of disc is not working can be found on document CH000031.
Access denied
Often caused when the file or directory has read-only attributes, is being modified by another person or program on the computer, and/or other network permissions that prevent it from being deleted or modified.
See our attrib command for additional information about this command and options.
Bad command or file name
Commonly caused by a misspelling or error when typing a command and/or when the command attempting to be used is not a valid command for your version of MS-DOS or Windows.
Bad or missing command interpreter
The computer cannot locate the command.com, an important file that that enables the computer to boot into the operating system. See document CH000012 for additional information and help with this error message.
Cannot perform a cyclic copy
This error occurs when you're trying to copy or xcopy all directories and files and that directory also contains the directory you're copying all the files to. If this command were to be allowed it would get into a loop and would never stop copying the same files over and over. When using the xcopy command if you're copying all subdirectories you must copy those files and folders to a completely separate directory or drive.
Divide overflow
Program has attempted to divide something by zero. This error is often caused by an error in the program you're running on your computer. Verify there are no available patches or other updates for the software you're using on your computer.
Drive not ready error
Disk or disc in the drive is not readable.
Additional information about problems reading floppy diskettes can be found on document CH000579.
Information about why a CD Disc, DVD or other type of disc is not working can be found on document CH000031.
Duplicate file name or file not found
When attempting to rename a file, the file does not exist or there is already a file with that name. Verify no other file exists with the same name in the current directory and/or that you're typing the file you wish to rename correctly.
File cannot be copied onto itself
An attempt to copy a file could not be completed because the file already exists or same source and destination. Copy the file to an alternate drive or directory.
File creation error
Directory could be full because of the DOS limitation of files in one directory, the file already exist, and/or the file was not copied correctly. Try creating or copying the file in a different directory.
File not found
The file you attempted to list, copy, or edit does not exist in the directory you're in. Verify you're in the correct directory and that the file exists in that directory.
This error may also occur if you're using a back slash instead of a forward slash for switches on commands. For example, doing dir \p instead of the proper dir /p.
General Failure
An unknown error has occurred that is not known by MS-DOS. If this is given when trying to read the hard drive, you may need to format the hard drive as it could be failing or already bad.
Insufficient disk space
Disk is full or, if you are trying to copy am file to a disk, the file is too big to fit on the disk.
Additional information about determining available disk drive space can be found on document CH000369.
Internal stack overflow
The MS-DOS internal storage areas are full. You may need to go into your config.sys and increase the STACKS=0,0
Information about editing and viewing the config.sys can be found on our autoexec.bat and config.sys page.
Invalid directory
The directory or path you attempted to enter does not exist in the directory or drive you're currently in.
Invalid drive specification
The drive letter you're typing does not exist on the computer.
Invalid file name or file not found
This error occurs when attempting to rename, copy, or otherwise manipulate a file the file does not exist. Verify you're typing the file you wish to rename correctly.
Invalid media, track 0 bad or unusable
Format command cannot format the specified disk or the disk capacity is invalid, or bad disk.
Additional information about errors that occur while reading/writing a disk drive can be found on document CH000379.
Invalid number of parameters
When the command was typed, something was left out that DOS needed by the command, it was mistyped, or a space was placed where one was not needed.
This error commonly occurs when you're typing a directory in the MS-DOS or the Windows command line that has spaces in it. For example using the xcopy command to copy files in the Documents and Settings folder. When typing a directory with spaces in MS-DOS make sure to surround the path with quotes. For example, instead of typing c:\documents and settings type "c:\documents and settings".
Invalid parameter
Typed a command correctly but specified the incorrect parameter, such as format /z.
Invalid Switch
The wrong slash was typed, for example: cd/ instead of cd\.
Non-System disk or disk error
See document CH000229 for additional information and help with this error.
Not ready, reading drive X
The drive letter you're typing does not exist on the computer or there is no disk or disc in the drive.
Parse error
This error occurs when the command you're typing in has invalid syntax. For example, if you're surrounding your path in quotes and leave out the ending quotes.
The system cannot find the drive specified.
The drive letter you're typing does not exist on the computer.
The system cannot find the file specified.
This error occurs when attempting to rename, copy, or otherwise manipulate a file the file does not exist. Verify you're typing the file you wish to rename correctly.
The system cannot find the path specified.
The directory or path you attempted to enter does not exist in the directory or drive you're currently in.
Write fault error
Tried to reroute text to a device that is not connected, is not valid or not hooked up.
Write protect
Tried to write to a disk that is write protected.
Autoexec.bat and Config.sys information
Autoexec.bat and Config.sys information
Quick links
About the autoexec / config
How to edit the files
Remarking information
Getting additional memory
Autoexec.bat layout
Config.sys layout
Information about batch files
Technical support
About the autoexec and config
The autoexec.bat and the config.sys were files created for MS-DOS and Windows 3.x as an easy solution of loading the files required for various devices as well as the operating system to properly run. These files are required for later revisions of MS-DOS and Windows 3.x to load. Because Microsoft is trying to steer away from MS-DOS, these files are not required for Windows 95, Windows 98, Windows NT, Windows ME, Windows 2000, Windows XP, or later operating systems. However, in some cases it may still be necessary for users to edit or configure these files.
How to edit the files
The auotexec.bat and the config.sys are most commonly edited by the MS-DOS command file Edit. To edit these files, type edit c:\autoexec.bat to edit the autoexec.bat file, or edit c:\config.sys to edit the config.sys file. If the mouse drivers are not loaded properly you will not have the capability of navigating the mouse.
If you have Windows 95, Windows 98, or later versions of Windows it is recommended that you use the sysedit command; to run this program, click Start / Run and type sysedit.
Remarking information
Remarking lines within the autoexec.bat or the config.sys allows you to temporarily or permanently prevent a line from loading each time you boot the computer. This is done by placing "REM " in front of the line you wish to skip.
If you are encountering issues with a line in the autoexec.bat it is highly recommended that you remark the line instead of removing it. This will prevent issues from arising if the line needs to be placed back into the autoexec.bat.
Getting additional memory
The below commands will help allow your computer to load programs into memory more efficiently allowing you to have more memory for MS-DOS programs / games.
Ensure you have the below three lines at the beginning of your config.sys file.
DEVICE=C:\Windows\HIMEM.SYS
DOS=HIGH,UMB
DEVICE=C:\Windows\EMM386.EXE NOEMS
By placing the DOS=HIGH,UMB on the second line, this can, in some cases, save memory because it is loading DOS into upper memory before loading the memory manager. Additionally, the first and third lines cannot be loaded into high memory because these lines are the memory managers.
Load all your devices in your config.sys and autoexec.bat into high memory.
Index
Category:
Hardware
Software
Companies:
None
Related Pages:
MS-DOS
Windows 3.x
Windows 95
Windows 98
Resolved
Were you able to locate the answer to your questions?
Yes
No
Autoexec.bat layout
Below is an example of what an autoexec may look like:
@echo off
SET SOUND=C:\PROGRA~1\CREATIVE\CTSND
SET BLASTER=A220 I5 D1 H5 P330 E620 T6
SET PATH=C:\Windows;C:\
LH C:\Windows\COMMAND\MSCDEX.EXE /D:123
SET PATH=C:\Windows;C:\
LH C:\Windows\COMMAND\MSCDEX.EXE /D:123
Command Explanation
@echo off Tells DOS to just read the lines but don't echo them back to the screen.
SET SOUND=C:\PROGRA~1\CREATIVE\CTSND This example is for the particular sound card that we have in one of the machines that we have. The set sound is telling the computer to send all sound events that the computer may run to that directory.
SET BLASTER=A220 I5 D1 H5 P330 E620 T6 Tells the computer to set the sound blaster settings. This is a good line for game players; if you have this line in your autoexec.bat you will know all settings players; if you have this line in your autoexec.bat you will know all settings for your sound card. A220 = port address "220", I5 = IRQ 5, D1 = DMA 1 usually being the settings you will need for any game out on the market.
SET PATH=C:\Windows;C:\ Sets the computer to look in the C:\windows directory or the root if a command used at the prompt is not found.
LH C:\Windows\COMMAND\MSCDEX.EXE /D:123 Line used for the CD-ROM. If you have Windows 95+, the MSCDEX will always be in the C:\Windows\COMMAND. In Windows 3.x or DOS, this will usually be either in C:\DOS or C:\Windows directory. The /D:123 is the name of the driver name that loads in upper memory; this can be anything, usually /D:MSCD0001. However, this is not an actual driver, this is just the name for the driver. Ensure if you change this line that you change it in the config.sys on your CD-ROM line. If the two are not the same, your CD-ROM drive will not load.
LH C:\MOUSE\MOUSE.EXE Loads the mouse driver into memory. However, not all mice use the same drivers. Although the mouse may use mouse.exe it could also be "mouse.com" or "mouse.sys", which is loaded in the config.sys.
C:\DOS\SMARTDRV.EXE /X Loads the smartdrive disk cache utility into memory. See our smartdrv command page for additional information about this utility.
DOSKEY Simple dos command to load DOSKEY into memory so when in DOS you can use it without having to load it.
CLS MS-DOS command to clear screen.
WIN Used for users using Windows 3.x, this line will load Windows automatically when booting the computer.
Config.sys layout
Below is an example of what the config.sys may look like:
DEVICE=C:\Windows\HIMEM.SYS
DOS=HIGH,UMB
DEVICE=C:\Windows\EMM386.EXE NOEMS
FILES=30
STACKS=0,0
BUFFERS=20
DEVICEHIGH=C:\Windows\COMMAND\ANSI.SYS
DEVICEHIGH=C:\MTMCDAI.SYS /D:123Command Explanation
DEVICE=C:\Windows\HIMEM.SYS The Himem.sys line is a very important line; this line will allow you to load drivers into high memory. If this line is not present, Windows 3.x will not load.
DOS=HIGH,UMB This line will load DOS into high memory in an upper memory block. Note the location usually best placed after the HIMEM.SYS.
DEVICE=C:\Windows\EMM386.EXE NOEMS The EMM386 line loads the extended memory manager. However, some older MS-DOS games have problems with extended memory and will not run without the NOEMS statement.
FILES=30 The files line allow Windows to load 30 files at the same time. Usually, however, going higher may decrease the computer's performance; 30 is found to work the best. Also ensure that this line is all as one line and that there is not a space between and after the =.
STACKS=0,0 The stacks line was first used in MS-DOS 3.2 and was used to swap the stack whenever an asynchronous hardware interrupt occurred. Later in MS-DOS 3.3 the line STACKS=0,0 was added into the config.sys. In special circumstances, this line was changed to STACKS=9,128.
The STACKS statement has a range of 8-64, 32-512. If a higher value is entered you will receive a FATAL : Internal Stack Failure, System Halted error message.
BUFFERS=20 Buffers line is to load buffers into memory allowing Windows to load memory.
DEVICEHIGH=C:\Windows\COMMAND\ANSI.SYS The ansi.sys line is a driver for DOS to allow you to have different colors / sizes and special characters at the DOS prompt.
DEVICEHIGH=C:\MTMCDAI.SYS /D:123 This line is the name of the CD-ROM driver on the particular system we are working on. The /D:123 represents the name of the driver, which in this case is named 123, however, can be named anything, usually MSCD0001. Note, however, that /D:123 must be exactly the same in config.sys and autoexec.bat; if they are different, the CD-ROM will not work in DOS.
LASTDRIVE= Allows you to specify the last drive installed on the computer. It is not recommended this line be used unless you are using Windows 3.11 or below. This line can cause issues with Windows 95 & 98 and will generally be remarked by Windows automatically.
FCBS= Line used to specify the number of file-control blocks for file sharing. This line should only be used when programs require it, and today, is generally not used or required. FCBS can utilize between 1 and 255.
TECHNICAL SUPPORT
Reference Issue / Question
MS-DOS Other questions and answers relating to MS-DOS.
CH000007 Getting the mouse to work in MS-DOS
CH000210 As the computer boots I receive bad command or file name.
CH000360 How to get sound in MS-DOS.
CH000361 MS-DOS issues with Windows ME.
CH000382 Stack overflow system halted.
CH000425 Himem.sys missing or corrupt.
FORUM If your question is not listed on this page, please try our online forum
Quick links
About the autoexec / config
How to edit the files
Remarking information
Getting additional memory
Autoexec.bat layout
Config.sys layout
Information about batch files
Technical support
About the autoexec and config
The autoexec.bat and the config.sys were files created for MS-DOS and Windows 3.x as an easy solution of loading the files required for various devices as well as the operating system to properly run. These files are required for later revisions of MS-DOS and Windows 3.x to load. Because Microsoft is trying to steer away from MS-DOS, these files are not required for Windows 95, Windows 98, Windows NT, Windows ME, Windows 2000, Windows XP, or later operating systems. However, in some cases it may still be necessary for users to edit or configure these files.
How to edit the files
The auotexec.bat and the config.sys are most commonly edited by the MS-DOS command file Edit. To edit these files, type edit c:\autoexec.bat to edit the autoexec.bat file, or edit c:\config.sys to edit the config.sys file. If the mouse drivers are not loaded properly you will not have the capability of navigating the mouse.
If you have Windows 95, Windows 98, or later versions of Windows it is recommended that you use the sysedit command; to run this program, click Start / Run and type sysedit.
Remarking information
Remarking lines within the autoexec.bat or the config.sys allows you to temporarily or permanently prevent a line from loading each time you boot the computer. This is done by placing "REM " in front of the line you wish to skip.
If you are encountering issues with a line in the autoexec.bat it is highly recommended that you remark the line instead of removing it. This will prevent issues from arising if the line needs to be placed back into the autoexec.bat.
Getting additional memory
The below commands will help allow your computer to load programs into memory more efficiently allowing you to have more memory for MS-DOS programs / games.
Ensure you have the below three lines at the beginning of your config.sys file.
DEVICE=C:\Windows\HIMEM.SYS
DOS=HIGH,UMB
DEVICE=C:\Windows\EMM386.EXE NOEMS
By placing the DOS=HIGH,UMB on the second line, this can, in some cases, save memory because it is loading DOS into upper memory before loading the memory manager. Additionally, the first and third lines cannot be loaded into high memory because these lines are the memory managers.
Load all your devices in your config.sys and autoexec.bat into high memory.
Index
Category:
Hardware
Software
Companies:
None
Related Pages:
MS-DOS
Windows 3.x
Windows 95
Windows 98
Resolved
Were you able to locate the answer to your questions?
Yes
No
Autoexec.bat layout
Below is an example of what an autoexec may look like:
@echo off
SET SOUND=C:\PROGRA~1\CREATIVE\CTSND
SET BLASTER=A220 I5 D1 H5 P330 E620 T6
SET PATH=C:\Windows;C:\
LH C:\Windows\COMMAND\MSCDEX.EXE /D:123
SET PATH=C:\Windows;C:\
LH C:\Windows\COMMAND\MSCDEX.EXE /D:123
Command Explanation
@echo off Tells DOS to just read the lines but don't echo them back to the screen.
SET SOUND=C:\PROGRA~1\CREATIVE\CTSND This example is for the particular sound card that we have in one of the machines that we have. The set sound is telling the computer to send all sound events that the computer may run to that directory.
SET BLASTER=A220 I5 D1 H5 P330 E620 T6 Tells the computer to set the sound blaster settings. This is a good line for game players; if you have this line in your autoexec.bat you will know all settings players; if you have this line in your autoexec.bat you will know all settings for your sound card. A220 = port address "220", I5 = IRQ 5, D1 = DMA 1 usually being the settings you will need for any game out on the market.
SET PATH=C:\Windows;C:\ Sets the computer to look in the C:\windows directory or the root if a command used at the prompt is not found.
LH C:\Windows\COMMAND\MSCDEX.EXE /D:123 Line used for the CD-ROM. If you have Windows 95+, the MSCDEX will always be in the C:\Windows\COMMAND. In Windows 3.x or DOS, this will usually be either in C:\DOS or C:\Windows directory. The /D:123 is the name of the driver name that loads in upper memory; this can be anything, usually /D:MSCD0001. However, this is not an actual driver, this is just the name for the driver. Ensure if you change this line that you change it in the config.sys on your CD-ROM line. If the two are not the same, your CD-ROM drive will not load.
LH C:\MOUSE\MOUSE.EXE Loads the mouse driver into memory. However, not all mice use the same drivers. Although the mouse may use mouse.exe it could also be "mouse.com" or "mouse.sys", which is loaded in the config.sys.
C:\DOS\SMARTDRV.EXE /X Loads the smartdrive disk cache utility into memory. See our smartdrv command page for additional information about this utility.
DOSKEY Simple dos command to load DOSKEY into memory so when in DOS you can use it without having to load it.
CLS MS-DOS command to clear screen.
WIN Used for users using Windows 3.x, this line will load Windows automatically when booting the computer.
Config.sys layout
Below is an example of what the config.sys may look like:
DEVICE=C:\Windows\HIMEM.SYS
DOS=HIGH,UMB
DEVICE=C:\Windows\EMM386.EXE NOEMS
FILES=30
STACKS=0,0
BUFFERS=20
DEVICEHIGH=C:\Windows\COMMAND\ANSI.SYS
DEVICEHIGH=C:\MTMCDAI.SYS /D:123Command Explanation
DEVICE=C:\Windows\HIMEM.SYS The Himem.sys line is a very important line; this line will allow you to load drivers into high memory. If this line is not present, Windows 3.x will not load.
DOS=HIGH,UMB This line will load DOS into high memory in an upper memory block. Note the location usually best placed after the HIMEM.SYS.
DEVICE=C:\Windows\EMM386.EXE NOEMS The EMM386 line loads the extended memory manager. However, some older MS-DOS games have problems with extended memory and will not run without the NOEMS statement.
FILES=30 The files line allow Windows to load 30 files at the same time. Usually, however, going higher may decrease the computer's performance; 30 is found to work the best. Also ensure that this line is all as one line and that there is not a space between and after the =.
STACKS=0,0 The stacks line was first used in MS-DOS 3.2 and was used to swap the stack whenever an asynchronous hardware interrupt occurred. Later in MS-DOS 3.3 the line STACKS=0,0 was added into the config.sys. In special circumstances, this line was changed to STACKS=9,128.
The STACKS statement has a range of 8-64, 32-512. If a higher value is entered you will receive a FATAL : Internal Stack Failure, System Halted error message.
BUFFERS=20 Buffers line is to load buffers into memory allowing Windows to load memory.
DEVICEHIGH=C:\Windows\COMMAND\ANSI.SYS The ansi.sys line is a driver for DOS to allow you to have different colors / sizes and special characters at the DOS prompt.
DEVICEHIGH=C:\MTMCDAI.SYS /D:123 This line is the name of the CD-ROM driver on the particular system we are working on. The /D:123 represents the name of the driver, which in this case is named 123, however, can be named anything, usually MSCD0001. Note, however, that /D:123 must be exactly the same in config.sys and autoexec.bat; if they are different, the CD-ROM will not work in DOS.
LASTDRIVE= Allows you to specify the last drive installed on the computer. It is not recommended this line be used unless you are using Windows 3.11 or below. This line can cause issues with Windows 95 & 98 and will generally be remarked by Windows automatically.
FCBS= Line used to specify the number of file-control blocks for file sharing. This line should only be used when programs require it, and today, is generally not used or required. FCBS can utilize between 1 and 255.
TECHNICAL SUPPORT
Reference Issue / Question
MS-DOS Other questions and answers relating to MS-DOS.
CH000007 Getting the mouse to work in MS-DOS
CH000210 As the computer boots I receive bad command or file name.
CH000360 How to get sound in MS-DOS.
CH000361 MS-DOS issues with Windows ME.
CH000382 Stack overflow system halted.
CH000425 Himem.sys missing or corrupt.
FORUM If your question is not listed on this page, please try our online forum
Subscribe to:
Posts (Atom)