Problems with DOS programs

[gjab13]

Hey. Recently I cannot open DOS programs in Windows 98. I receive an error message: "There are not enough system resources available to run this program. Quit one or more programs, and then try again." I can't even open a DOS window with "command" (it show the same error message). I have also noticed that when I select to view the Properties of a DOS program, it does not show all the tabs that it is supposed to; it only shows one tab (the "General" tab). Please help

[DELTREE]

gjab13- your PC is telling you the problem but, this will explain it.

http://www.windows-help.net/techfile...resources.html

Take Care

[gjab13]

Thanx for responding. I read the article and found some useful info.
But I think that the problem I have is different. I don't even think it's actually a resources problem. I closed every single program and checked the system resources and they were fine, but the error message keeps appearing when I try to open a DOS window or run a DOS program.
I recall of having a similar problem in the past, and that I resolved it by changing some values in the program's properties; in one of it's several tabs (remember, when you right click DOS programs and select Properties, the properties dialog box has several tabs, including "General", "Program", and others).
But as I said, now there are no tabs for the DOS programs' properties, just the "General" tab.
Something went wrong here and I can't figure it out.

[Train]

Looks like you will need to make a boot floppy to play that game. Or modify the autoexec.bat

your problem stems from the fact you are not using high memory that is called for by the program.

http://www.computerbits.com/archive/...00/qa9507.html

Perhaps your Windows resource pool is leaking. Think I'm kidding don't you? Well, I'm not! The "Out of Memory" error message is used to convey several types of out of memory conditions. The first (and most obvious) occurs when you try to load a program that takes more memory than you have in your computer. The second condition occurs when you don't have enough DOS memory available. DOS memory constitutes the first 640KB of RAM in your system. Available DOS memory is that which is still free after you boot DOS and load your device drivers and TSR's (basically all those statements in config.sys and autoexec.bat). If you only have 517KB of available DOS memory and you attempt to load a program that requires 518KB you'll get an Out of Memory error.

Not that like might be of help. Or tyou can try posting the Dos part in Windows 3.x and DOS

Just my thoughts on the problem.

[Eeyore]

I can't even open a DOS window with "command" (it show the same error message).

Gentlemen and ladies, this is not a DOS problem. It is a Windows problem. It is not about this particular program needing more memory than is available. gjab13 cannot open a DOS window period!

I don't know the solution. If it were Windows 95, I know what the minimum files needed to run are. But I have never isolated Windows 98 files (which are different).

This could be a damaged file. In Windows 95, dosapp.fon in the FONT folder could cause such a problem. Possibly an over installation could fix the problem. It could also be a bad registry key. Running SCANREG /FIX (at real DOS mode) might correct errors. SCANREG /RESTORE most likely won't repair it because the problem may have not been discovered unit all of the backups have been likewise contaminated.

If you haven't already, press Alt-CTRL-DEL to call up the Task Manager. End every program listed there except Explorer and Systray, then try to open a DOS prompt. Also run MSCONFIG and disable any programs listed under Startup. Reboot and try the DOS prompt again. If any of this gets the Prompt to run, you have another program interfering.

I would look at the possibility of a virus as well. Something caused a change. One virus I recently read about, W32.Swen.A@mm adds a key that prevents you from running the REGEDIT program. Kind of hard to edit the REGISTRY if the REGISTRY keeps the program from running. So there are lots of possibilities.


The solutions of running at DOS should get around the problem if the program is a DOS program. But there is still a problem in Windows.

------------------
My
Two Cents
Dennis
Visit Politalk