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 curacao_dejavu

rem these 3 lines.
DEVICE=HIMEM.SYS /testmem:on
device=C:\windows\emm386.exe

the first line referning to the cd rom.

win98 manage it's own memory, you should not need the memory manager in config.sys
unless win98 doesn't have drivers for your cdrom, it's not needed for windows, only if you go to dos and need cdrom support you will need that enabled in config.sys. copy the .cab file on the harddisk and extract it from the harddisk.

You can also try to boot to safe mode and then extract the file.

"rem" entries also from autoexec.bat.

success
Leopold

by daveg

Thanks, even though the computer still boots into safe mode only, its not worse off than when i started. It gives a fatal exception error at 2047:00000316 on normal bootup, which is what it was doing before. Success!....sort of.

This discussion is closed to new replies.