Windows Forum

Ask something
Discussion Locked

Out of memory

0 helpful
3 replies

by daveg 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Windows 98
My config.sys is as follows:
DEVICE=HIMEM.SYS /testmem:on
device=C:\windows\emm386.exe
DOS=HIGH,UMB
FILES=30
BUFFERS=20

DEVICE=cd1.SYS /D:banana /E

rem DEVICE=cd1.SYS /D:banana /P:1f0,14
rem DEVICE=cd1.SYS /D:banana /P:170,15
rem DEVICE=cd1.SYS /D:banana /P:170,10
rem DEVICE=cd1.SYS /D:banana /P:1e8,12
rem DEVICE=cd1.SYS /D:banana /P:1e8,11
rem DEVICE=cd1.SYS /D:banana /P:168,10
rem DEVICE=cd1.SYS /D:banana /P:168,9

LASTDRIVE=Z

Conventional Memory total=655,360
Conventional Memory used=137,968
Conventional Memory Free=517,392

Upper Memory total,used and free =0

reserved memory total=393,216
reserved memory used=393,216
reserved memory free=0

extended memory total=99,614,720
extended memory used=606,208
extended memory free=99,008,512

total EMS=32M
free EMS=32M

Largest executable = 505K
Largest free umb = 0
MS-DOS is resident in the high mem area.

Question:
Why do I run out of memory when I try to exract /a s:\win98\win98_22.cab *.fon /l c:\windows\fonts.

I am trying to avoid a re-install. Right now, the gdi.exe fails to load and windows fails to load because of missing fonts.

3 replies

by cruncher_1

Unless you are running many DOS programs, I would rename config.sys to config.old and reboot. If that doesn't work, I would start by removing all the cards from the motherboard except the video. I would also remove anything else that is not absolutely necessary to run the computer. You will need memory and video. Of course, if you have to access the CD or the floppy, you will have to plug them back in. You may not even need to extract the files. Then add the hardware back one at a time to see what happens.

I hope this helps.

Good Luck.

by daveg

Copied the cab files to the hard drive, booted with c:\ prompt only and extracted the files that way. Then the computer would boot into safe mode again, which is where i started. then i "rem"'d out the config.sys,system.ini,win.ini etc via the msconfig tool and eventually found that an entry in the system.ini file under the boot section was causing the problem, that being the computer would only boot into safe mode. It was a device driver for adobe print manager. the entry in the system.ini file was system.drv=atmsys.drv. When i changed it to system.drv=system-drv the fatal exception OD upon boot up went away.

This discussion is closed to new replies.