Hi,
I'm trying to run WFW 3.11 under DOS 7.10. I have Windows 98 SE and WFW 3.11 (in separate directories) on my C: drive, which is FAT16. Several times I've exited WFW and then tried to start it again and got the message "FAT allocation table bad, drive C." If I turn off the computer completely, then boot up into Win98 and run Scandisk, no errors are reported.
My system:
Transmonde Vivante SE laptop
300 MHz Pentium II
64 MB RAM
My Autoexec.bat:
====================
goto %config%
:Windows98
c:\maestro.com
C:\WINDOWS\win
goto end
:DOS-CD
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\DOSfiles
C:\DOSfiles\Drivers\Mouse.com
PROMPT $p$g
goto end
:DOS&CD
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\DOSfiles
C:\CD-ROM\MSCDEX.EXE /D:MSCD001 /V
C:\DOSfiles\Drivers\Mouse.com
PROMPT $p$g
goto end
:Test
PATH=C:\WINDOWS;C:\DOSfiles
LH C:\CD-ROM\MSCDEX /D:MSCD001 /V
LH C:\WINDOWS\SMARTDRV.EXE
LH c:\maestro.com
PROMPT $p$g
goto end
:end
My Config.sys:
====================
[menu]
menuitem=Windows98, Windows 98 configuration
menuitem=Dos-CD, Start up DOS without CD-ROM support.
menuitem=Dos&CD, Start up DOS with CD-ROM support.
menuitem=Test, Start up using test configuration.
menudefault=Windows98,10
menucolor=7,0
[Windows98]
DEVICE=C:\aecu.sys /s:00011111
[Dos-CD]
DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:OFF /Q
; DEVICE=C:\WINDOWS\EMM386.EXE RAM
DOS=HIGH,UMB
FILES=60
[Dos&CD]
DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:OFF /Q
DOS=HIGH,UMB
DEVICE=C:\CD-ROM\VIDE-CDD.SYS /D:MSCD001 /P:1F0,14 /P:170,15 /P:1E8,12 /P:168,10
LASTDRIVE=H
FILES=60
[Test]
DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:OFF /Q
DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
DOS=HIGH,UMB
DEVICEHIGH=C:\CD-ROM\VIDE-CDD.SYS /D:MSCD001 /P:1F0,14 /P:170,15 /P:1E8,12 /P:168,10
DEVICEHIGH=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER
DEVICEHIGH=C:\WFW311\IFSHLP.SYS
DEVICEHIGH=C:\aecu.sys /s:00011111
LASTDRIVE=H
FILES=60
STACKS=9,256
As you see, I am using a multi-configuration setup. I did this to minimize the chances of a conflict occurring. The "Test" configuration is the one I am using for WFW 3.11.
Any ideas what might be causing this strange error message?
-Phil