unrecoverable error 5302: conventional memory exhausted
kleefarr iol.ie>
(touch wood) I get the following error-
unrecoverable error 5302: conventional memory exhausted
Press any key to continue.
Then boots into windows.
I have had a search and not come up with anything.
The machine has 256kb Memory.
Config.sys and Autoexec.bat are the same as the other machine.
"CONFIG.SYS"
dos=single
fileshigh=99
buffershigh=50
dos= high, umb
device= c:\windows\himem.sys
device= c:\windows\emm386.exe
"AUTOEXEC.BAT"
@ echo off
set tmp= c:\windows\temp
set temp= c:\windows\temp
The system is a bit too good for win 95, but I have ironed out the other
problems that I originally had with the other machine ie CPU speed fix etc.
Well all apart from finding a dialup adapter that doesn't cause an NDIS
error, but that's another story.
Would anybody have any ideas please?
Kevin
RobertVA
Only 256 KB of RAM and "too good for win 95"?!
I don't think you can run ANY version of Windows with less than a
Megabyte. Used to be a saying that Windows didn't "run" with only the
minimum RAM "requirement", it "crawled".
Maybe you mean 256 MB, but many DOS applications only use the first MB
and it has to be something pretty demanding to use anything past the
second MB. "Conventional memory" is limited to 640 KB of that first MB
and you are NOT going to avoid DOS and other necessities useing part of
that before your application even loads. Windows 95 and subsequient
command prompts allow multiple applications running unaware of each
other in duplicates of that structure. The DOS legacy applications don't
even know the other megabytes are there.
Despite documentation that Windows 9x could manage high, extended and
expanded memory with no config.sys or autoexec.bat files, I could make
more conventional memory available in command prompts if I used
himem.sys, emm386.exe ram v and dos=high,umb lines in a config.sys file
that executed before Windows 9x loaded.
What output are you getting from the MEM command? The reference material
I'm useing recommends using the /D and /P parameters.
"DOS=Single" I don't see a "single" parameter in the reference material
I'm useing. It lists high, low, umb and noumb.
Have you tried?:
* Relocate himem.sys and emm386.exe to top of config.sys
* Add RAM and V parameters to emm386.exe command
* If not required by you application, reduce buffer quantity. Each
buffer uses 532 bytes, so those 50 are soaking up over 25K of that
precious first conventional or high memory area. The high memory area is
only about 64 KB, and you've already loaded part of DOS there. Default
quantiy would be 15 buffers.
I've been useing Bantam's "DOS 6.0 Power Tools" by Goodman and Socha
kleefarr iol.ie>
"RobertVA" wrote:
Robert,
1) Yes, I meant 256MB.
2) Should I include the "emm386.exe ram v" command in CONFIG.SYS?
3) Output from MEM command ..
MEM /D
Conventional 655,360 52,672 602,688
Upper 0 0 0
Reserved 0 0 0
Extended (XMS) 67,043,328 ? 198,983,680
---------------- ----------- ----------- -----------
Total memory 67,698,688 ? 199,586,368
Total under 1 MB 655,360 52,672 602,688
Handle EMS Name Size
------- -------- ------
0 094000
Total Expanded (EMS) 67,108,864 (64M)
Free Expanded (EMS) 16,777,216 (16M)
Memory accessible using Int 15h 0 (0K)
Largest executable program size 602,672 (589K)
Largest free upper memory block 0 (0K)
MS-DOS is resident in the high memory area.
XMS version 3.00; driver version 3.95
EMS version 4.00
MEM /P
Memory Type Total Used Free
---------------- -------- -------- --------
Conventional 640K 51K 589K
Upper 0K 0K 0K
Reserved 0K 0K 0K
Extended (XMS) 65,472K ? 194,320K
---------------- -------- -------- --------
Total memory 66,112K ? 194,909K
Total under 1 MB 640K 51K 589K
Total Expanded (EMS) 64M (67,108,864 bytes)
Free Expanded (EMS) 16M (16,777,216 bytes)
Largest executable program size 589K (602,672 bytes)
Largest free upper memory block 0K (0 bytes)
MS-DOS is resident in the high memory area.
4) I only copied the original config.sys and autoexec.bat files from the
original
Win 95 PII 64MB machine. This had the dos=single line. Should I remove it?
RobertVA
"DOS 6.0 Power Tools" indicates the RAM parameter enables the use of any
available extended memory for Upper Memory Blocks (the unused addresses
within the 384k block of the first MB where the BIOS, the peripheral
ROMS and peripheral hardware like keyboard and drive interfaces are).
This allows portions of DOS to load into those UMB areas as well as in
the high memory area.
The v parameter enables verbose error messages in the event EMM386.exe
encounters a problem.
On my earlier computers I was getting about 589K conventional memory
available in Windows 9x command prompts when no CONFIG.SYS was present.
With a CONFIG.SYS containing EMM386.EXE with the above parameters and no
buffers line I was getting free memory in the 615K range. I had one
application that was insisting on at least 609K.
Sometimes I had to add similar lines to shortcuts in order to get DOS
applications to run in Windows 9x DOS mode.
As I said, I see no indication of what the parameter acomplishes. Try
the CONFIG.SYS with and without the line to see if it's makeing any
difference.
Jeff Richards
http://support.microsoft.com/?kbid=134399
How to Increase Conventional Memory for MS-DOS-Based Programs
--
Jeff Richards
MS MVP (Windows - Shell/User)
"kleefarr iol.ie>" <kleefarr<at> wrote in message
news:63AE6C33-3132-4A71...@microsoft.com...
kleefarr iol.ie>
I decided, after trying out the things you both suggested below, to format
and reinstall Win 95 again. Then when I got to running the program I simply
put
files=99
buffers=50
into config.sys, nothing else, just that and didn't touch autoexec.bat. Hey
Presto! Running fine.
Thanks again,
Kevin