Ok, so, I have plenty of free resources; 77% USER, 71% GDI, 72% LDT. Plenty of RAM available, swap file is barely in use. But for some reason, I can't start any console applications, 16 or 32-bit. I can't even start command.com (or cmd.exe). My current uptime is 5 days 13 hours, and I've been doing tons with batch files and console programs (both 16 and 32-bit), so I've exhausted some resource related to console use, but what?

Oh, and when I try and run a console application, it's the generic ''There is not enough memory available to run this program. Quit one or more programs, and then try again.'' message. I can open like 40 instances of Internet Explorer, but can't open a simple command prompt. I'm going to restart my computer to resolve the issue temporarily, but I'd love to know what is actually causing the problem.

Queue

Edit - When I run a 32-bit console application, the error message's title is ''Win32'' and the program actually runs (it's in the task list) but since a console window never spawns, I can't interact with t.

Edited June 26, 201016 yr by Queue

''There is not enough memory available to run this program. Quit one or more programs, and then try again.'' message. I can open like 40 instances of Internet Explorer, but can't open a simple command prompt. I'm going to restart my computer to resolve the issue temporarily, but I'd love to know what is actually causing the problem.

That's the classic symptom of exhausted System Arena memory. What have you been doing? Added any new hardware piece or more RAM lately? What's your machine's configuration?

I haven't done anything different lately, and the hardware has been the same for years. This isn't a new problem, but I'm also not sure what causes it; it's generally only after Windows has been running for days without a restart, and seemingly only if I've been doing a lot of command-line things.

The machine itself is a:

1.3 GHz Athlon

512 MB non-DDR RAM (133 MHz)

Radeon 9550

I'm just wondering why a problem crops up after a while when there isn't a problem after a reboot, and when all my other resources seem fine.

Queue

Try adding a [VCache] section to your system.ini and adding a MaxFileCache=393216 under it. It should solve your problem, or, at least, cause it to appear much later. BTW, have you been seeing BSODs in VXD VCOND(03), too? Or you've never seen them?

Try adding a [VCache] section to your system.ini and adding a MaxFileCache=393216 under it. It should solve your problem, or, at least, cause it to appear much later. BTW, have you been seeing BSODs in VXD VCOND(03), too? Or you've never seen them?

No, I've never seen that BSOD.

Actually, I can't think of the last time I saw a BSOD.

Anyhow, I'll give that a shot. I have a commented out vcache entry; I had last experimented with it in regards to Windows Explorer (as in, using it to browse folders) performance degrading over time. This problems tends to take days to crop up, so it'll be hard to get back to you to know if it helps.

Thanks.

Queue