82
the drive G, which is currently enabled, will be disabled.
This problem arises from the fact that the hardware conditions established by initialization with
CARDID.EXE are lost since access to the drive F was executed by means of specific codes
included in the BIOS. To avoid this problem, these specific codes in BIOS should be disabled.
ENDATA.COM is used to do this. If ENDATA.COM is executed with the two drives mentioned
above enabled, the specific codes (program) in BIOS are disabled, and the drive G can be retained
as the only valid card drive. Below are example CONFIG.SYS and AUTOEXEC.BAT scripts
used to boot a card.
Example of CONFIG.SYS
FILES=30
BUFFERS=20
DOS=HIGH,NOUMB
DEVICE=C:
SYSDRV.SYS
DEVICE=C:
HIMEM.SYS /M:2
DEVICE=C:
POWER.EXE
DEVICE=C:
TIME.SYS
DEVICE=C:
EMM386.EXE FRAME=C800 X=C000-C7FF X=D800-DFFF I=C800-D7FF
SHELL=C:
COMMAND.COM C:
/P /E:1024
DEVICE=C:
CARDSOFT
SS365SL.EXE /SKT=1
DEVICE=C:
CARDSOFT
CS.EXE /POLL:1
DEVICE=C:
CARDSOFT
CSALLOC.EXE
DEVICE=C:
CARDSOFT
ATADRV.EXE /S:1
DEVICE=C:
CARDSOFT
MTSRAM.EXE
DEVICE=C:
CARDSOFT
MTDDRV.EXE
DEVICE=C:
CARDSOFT
MTDAPM.SYS
Example of AUTOEXEC.BAT
@ECHO OFF
C:
CD
C:
CARDSOFT
CARDID.EXE
C:
ENDATA.COM
C:
CARDSOFT
CS_APM.EXE
PROMPT $p$g
PATH C:
C:
CASIOAPM.COM
For the moment concentrate on the positions of CARDID.EXE and ENDATA.COM. CARDID.EXE
can be registered as a device driver. In fact, this CARDID.EXE is registered as a device driver in
