C:\DOS\MSCDEX.EXE /D:MSCD000 SET SOUND=C:\FORTE16 SET GALAXY=A220 I5 D1 K10 P530 T6 SET BLASTER=A220 I5 D1 T4 C:\FORTE16\UTILITY\EMUTSR.EXE SET IEPPP=C:\MSIE40 SET PCTCP=C:\MSIE40\PCTCP.SHV @ECHO OFF PROMPT $P$G C:\DOS\SMARTDRV.EXE 1024 256 /X SET DIRCMD=/0 SET TEMP=C:\PBTOOLS\WINTEMP SET WINTEMP=[WINDOWS] $P$G CD C:\WINDOWS WIN
REM TYPE C:\PBFRONT\TEXT\EXIT2.MSG
REM LSL REM EPROPKT 0X69 0XA 0X320 REM AON101.COM REM IPXODI.COM REM CD C:\WGSERV REM CALL WG GO
Can anyone give me tips on getting this fixed... Thanks
... this message appears in three cases: a) If there is not enough space in the resource heaps b) If the amount of RAM really is too small c) If there isn't enough memory below 1 MB available.
Possibly you may after all be low on conventional memory. A little more info might be helpful.
Drop the last year into the silent limbo of the past. Let it go, for it was imperfect, and thank God that it can go.
You only need TCP/IP protocol with WfW3.11, you appear to have at some time installed other protocols either in DOS or Windows. Therefore it may be a conflict of resources!
IPX is only required for Novell Knitware and NETBEUI is for older compatibility should not need, TCP/IP should be adequate.
.. which I guess is some kind of Windows prompt environment variable - maybe for 9x (?) - never quite seen that before.
Kinda seems like a little bit of everything - that many REM statements is counter productive, for sure. Shouldn't there be a 'net start' line for WfW too (as opposed to all the REM'd out DOS net drivers)?
Just as well he'd posted them after all, although some details regarding the error & running Win programs etc wouldn't hurt
Drop the last year into the silent limbo of the past. Let it go, for it was imperfect, and thank God that it can go.
No need to be formal - excessive values for files and buffers can increase the memory requirements for the DOS kernel and prevent it from loading into the HMA
Thanks for fleshing out the problem.
Drop the last year into the silent limbo of the past. Let it go, for it was imperfect, and thank God that it can go.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE