cant run application in dos from bootup

D

dwight

I am trying to get a dos bootable Floppy to run F-Prot
with NTFS support from the boot up.

Every time I try to run it, it gives me the following
error:

"causeway error 12: not enough memory to load application"

I am loading Himem.sys and dos high with upper memroy
blocks.

Here is a copy of the batch program:

" @ECHO OFF

PATH=A:\;x:\fprot;x:\ntfs

LOADHIGH MSCDEX /D:MSCD001 /M:8 /L:X
@echo
@echo
@echo 1 for 9x 2 for XP/2k

choice /C:12 /n

IF ERRORLEVEL 2 GOTO 2k
IF ERRORLEVEL 1 GOTO 9x

:2k
LOADHIGH x:\ntfs\NTFSPRO.EXE /L:Z /V
MENUXP.BAT

:9x
MENU9X.BAT





REM cd\fprot
REM f-prot
rem SET DIRCMD=/OGNES
rem CTMOUSE
rem LOADHIGH SMARTDRV
rem LOADHIGH DOSKEY /INS"

Does anybody have any ideas as to why this won't allow it
to run??

Thanks in advance for any assistance!!

Dwight
 
G

Guest

Thanks for the info, but this is a CLEAN BOOT to a FLOPPY
disk being run on an 80 gb hd with min 40gb free. So I
don't see where that could be an issue!

Any other ideas??

Dwight
-----Original Message-----
12 - Not enough memory to load application.

Generated if CauseWay is unable to provide enough memory
Click to expand...
to load the application. Free additional memory and/or
disk space before running the application. Check for
CAUSEWAY=SWAP, TEMP and TMP environment variables that
point to a disk with little free space. If running under
an operating system that provides DPMI per application,
increase the application's DPMI allocation.
 
M

Malke

Thanks for the info, but this is a CLEAN BOOT to a FLOPPY
disk being run on an 80 gb hd with min 40gb free. So I
don't see where that could be an issue!

Any other ideas??

Dwight
Click to expand...
Try copying the F-Prot folder to the hard drive and then running
f-prot-exe from the hard drive, not the floppy.

Malke
 
A

Alex Nichol

dwight said:
I am trying to get a dos bootable Floppy to run F-Prot
with NTFS support from the boot up.

Every time I try to run it, it gives me the following
error:

"causeway error 12: not enough memory to load application"
Click to expand...

Two thoughts: One is remove the @ECHO OFF so as to see how far it gets
- and especially what happens from those embedded .BAT files. Then
after the failure, run
MEM /C /P
and see what has got loaded where, so as to see if anything could be
left out in Config.sys (I presume you are loading the oakcdrom.sys there
as the CD driver)
 
Top