中国DOS联盟

I don't understand debug. One day, driven by curiosity, I ran it, and forcefully exited without understanding the parameters. Then I found:
My hard disk doesn't support cloning anymore, and I can't run Ghost and so on. As soon as I run it, it prompts: the program too big to fit in memory. It's also no good to repartition. It prompts: emm386 is running. the memory limited 32mb. (The general idea is that the memory can't exceed 32MB). How to solve it. Please give instructions from the experts?

Oh, the program too big...........Generally, it's that the application is broken.

I don't know which program the original poster is running to get those prompts. If all programs have this prompt when run, it's because the machine didn't load a memory management software at startup, resulting in too little base memory.

Please change the boot disk and restart to try again. Remember to load the memory management software. (himem.sys and emm368.exe)

I made a new bootable disk today, and it turned out that it could clone. But I have two hard drives. Only the WD one works, the Samsung one doesn't. Here's the detail: Last October, I ran debug on the WD disk, shut down halfway and exited. When I booted up again, I couldn't run Ghost or install systems other than DOS. Whenever I tried to install, there was the above - mentioned prompt. I also changed the bootable disk, but it didn't work. It could be used as a slave disk. Then I used the Samsung hard drive as the master disk. In the past few days, to solve the problem, I made many attempts. Generally, when running U无忧's pq; fdiskgen; fdisk, etc., it prompts that emm386 is running, memory is limited to 32MB. Then it can't operate and exits automatically. If you run Ghost or install Windows, it prompts: "the program too big to fit in memory". Once I ran a partition software, and there was the following prompt: "emm386 has detected error #u^5 in an application at memory address 08cd:3e80. To minimize the chance of data loss, emm386 has halted your computer. For more information, consult your documentation." After trying around, the Samsung hard drive also had the same problem. I asked WD customer service, and they said that zeroing it would work. The day before yesterday, I booted with a floppy disk and ran fdisk, set the active partition, and then both disks could run Ghost. When I booted with the WD as the master disk, the Samsung disk disappeared, and all the data was gone. I zeroed the Samsung disk and partitioned it, but it was still the same prompt, and the WD couldn't run Ghost either. Until just now, after changing the bootable disk, the WD could run Ghost, but the Samsung disk was still not working, and there were the above - mentioned prompts. Whether the WD disk will have similar problems in the future is unknown. What is this problem? I'm looking forward to the guidance of all the experts!

Today I used Jiangmin Hard Disk Tool to test and got the following report:
"The total memory with DOS reports is 639KB.
The total memory I found is 655344 bytes.
The location where the user program is loaded (in hexadecimal) is 03A2H.
The available memory for the user program is 64064 bytes.
The memory used by DOS and memory-resident programs is 14880 bytes.
The current DOS version is MS.7.10
Number of serial ports 1
Number of parallel ports 1"
My memory is 128 megabytes. Why is the memory so little? How to increase it?

First of all, try the replacement method by changing a memory stick to eliminate whether it is a problem caused by the memory stick. If the problem still exists, please upload the contents of the AUTOEXEC.BAT and CONFIG.SYS files of the boot disk for everyone to analyze.

My memory is SDR, which is too hard to find. I'll try later. I really didn't expect that running debug would have such serious consequences.
Thank you all for your care and guidance!!!!!

Originally posted by liqi2002112 at 2007-2-26 13:36:
My memory is SDR, it's too hard to find, I'll try later. I really didn't expect that running debug would have such serious consequences.
Thanks to everyone's care and guidance!!!!!!

The poster can first release the contents of the CONFIG.SYS and AUTOEXEC.BAT files of the boot disk, and then explain the software environment when the software is running, so that everyone can jointly analyze the cause of this problem.

According to my speculation, the fault of the thread starter may have nothing to do with debug. The feasible solution steps are:
1. Clear the CMOS data and restore the default BIOS settings.
2. Perform a low-level format operation on the hard disk.
3. Detect whether there is any hardware damage.

I tried, without any memory management program, GHOST can also run.
When GHOST runs, it will read the partition table, the file allocation table of the FAT/FAT32 system, and the MFT table of NTFS. If something is written wrong somewhere, such a problem may occur. PQ may repair partition table errors, and disk scanning can repair FAT/MFT errors. It is suggested that the owner try it first. I think it is the place that should not be written when DEBUG exits, which causes the GHOST operation error. It is not a memory problem.
Now I want to know, what instruction did the owner run under DEBUG at that time?

I once ran an external application, and it prompted "SCAN THE DISK(Y/N)". I thought it was just scanning the computer hard drive, so I pressed Y. As a result, a good 80GB hard drive with four partitions, all containing useful materials (including a large amount of sorted DOS materials that took a long time to organize) was combined into one partition, and all the materials were gone. It was so heartbreaking. There was no way to recover them.

Last edited by xiaoguiping2003 on 2007-3-1 at 02:35 PM ]

I haven't been online for a day or two, and there are so many friends helping me figure out a way. Thank you.

The hard drive is okay. Now I hang it as a slave drive on another hard drive and can clone it. But after cloning, it works normally, but it can't be used as the master drive to install a large system or run Ghost.

I don't know how to extract the contents of the CONFIG.SYS and AUTOEXEC.BAT files of the boot disk. However, there is a download of this boot disk in the union. That is Shen Jie's pwin. Generally, I run option 2 or 3 after booting with it. Debug is run in 2. The debug I ran was by accident, and I can't remember what command it was.

Low-level formatting has been done, but it didn't work.

I don't know how to run the statement of building 10. As soon as I run it, there is: the program too big to fit in memory.

I haven't tried clearing the CMOS data and restoring the default BIOS settings. I don't know how to do it. Is there any danger?

Haven't tried clearing the CMOS data and restoring the default BIOS settings. I don't know how to do it. Is there any risk?

There's no real risk. Open the case, take out the coin cell battery, and touch the + and - poles with a metal object (commonly called discharging). Actually, there's a discharging interface next to the coin cell battery.
If that doesn't work, remove all PCI USB and other devices for debugging. If it still doesn't work, you'll have to reflash the BIOS (that's the risky part)

If there is no important data in the hard disk, you can use the system tool disk made by Shenshan Hongye for processing. The tools on this disk should be able to handle more than 99% of software and hardware problems.

I ran it once, and the result was all garbled. Later, I imported the backed-up.reg file to solve the problem.