Memory Allocation Error Cannot Load Command System Halted Dos
Cooling Fetish CPU & Motherboard Technologia Mobile Computing Outpost Networking Matrix Other Hardware Agora Classifieds Ars DIY Forum (Name TBD!) Operating Systems & Software Battlefront Microsoft OS & Software Colloquium Linux Kung Fu Windows Technical Mojo Distributed Computing Arcana Macintoshian Achaia Programmer's Symposium The Server Room Ars Lykaion Gaming, Extra Strength Caplets The Lounge The Soap Box The Boardroom The Observatory Ars Help & Feedback Ars Subscription Member Areas Image Galleries HELP!!! Memory Allocation Error!!! HELP!!! 11 posts Marrek Wise, Aged Ars Veteran Registered: Mar 13, 2000Posts: 127 Posted: Mon Aug 20, 2001 5:18 pm System:AST Ascentia M Series laptop64mb ram(now 128)swapable cdrom/disk drive4gb ibm travelstar hard driveThe other day I tried to upgrade to win2k on my laptop, but after the initial setup restarted the laptop to continue setup on the hard drive I got an invalid disk error like the hard drive still had nothing on it, but when i looked through dos there was a BOOTEX and 2 FOUND dir on the hard drive. So I tried to put win98se back on and to my suprise I would get an "Out of Memory" error in a little grey box during the initial scandisk that 98se runs, then it says "There are still errors on drive C." on a blue screen. When I went to the view log option it put me at a screen that read:"Out of memory. Disable unnecessary memory-resident programs and try again.Memory allocation errorCannot load COMMAND, system halted"These are some trouble shooting things I have tried already:1. Win98se and Win2k cd both work in other computers2. Copied win98 folder from cd to hard drive in dos and tried to install it from the hard drive....it would lock as soon as I hit enter for c:\win98>setup3. I took the cdrom out and booted to dos using the win98se boot disk. Then I ran
error: MESSAGE Memory Allocation Error. Cannot load COMMAND.COM. System Halted Troubleshooting The error occurred using a DOS SET command in the login script. Cause http://arstechnica.com/civis/viewtopic.php?t=938366 1.1 There was not enough space available to set the variable. Solutions 1.1 Increased the DOS environment from 512 to 1024 using the shell command in the CONFIG.SYS file and the http://support.novell.com/docs/Tids/InfoDocument/3083.html problem disappeared. document Document Title: "Memory Allocation Error. Cannot load ..." Document ID: 3083 Creation Date: 23May1991 Modified Date: 01Jul1995 Revision: 1 Novell Product Class:NetWare disclaimer The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
The PC Guide Tip Jar. Visa/MC/Paypal accepted. View over 750 of my fine art photos any time for free at DesktopScenes.com! [ The PC Guide | http://www.pcguide.com/ts/x/sys/operrCommandCom-c.html Troubleshooting and Repair Guide | The Troubleshooting Expert | Troubleshooting The System Overall | Troubleshooting Run-Time Error Messages ] Cannot load COMMAND.COM, system halted
Explanation: When you boot up DOS, you are placed at what is commonly called the "C: prompt", where you can type commands or run programs. The part of DOS that reads what you type and executes commands is called the command memory allocation interpreter, which is stored in the file "COMMAND.COM". This interpreter is loaded when you start the system or when you start an MS-DOS session under Windows 95, and is also reloaded in some cases when you finish running a program. In this case, the system was unable to find COMMAND.COM and therefore halted the system. Diagnosis: Part of COMMAND.COM resides in conventional memory under normal memory allocation error circumstances. It uses memory that might be needed by DOS programs. To make sure that these programs can use as much conventional memory as possible, COMMAND.COM allows the memory it uses to be overwritten by a DOS program that needs it, and then reloads itself when the program completes. The error message occurs when the COMMAND.COM file cannot be found to reload. The most common cause of this problem is renaming or moving COMMAND.COM on the hard disk, and then forgetting to reboot the system. It can also be caused in some cases by booting from a floppy disk and then removing the disk from the system after running a program. When the program completes the system will try to go back to the floppy disk to find COMMAND.COM, see an empty drive, and hang up. Recommendation: Make sure that COMMAND.COM is in the C:\ root directory, or if it somewhere else, that there is a line in AUTOEXEC.BAT that reads "COMSPEC=X:\PATH" where "X:\PATH" is wherever COMMAND.COM resides. Edit the PATH command in your AUTOEXEC.BAT file, if you are trying to run a command in another directory that should be accessible from anywhere. Hom