Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.
bad file allocation table
Name: Rich Dennis Date: November 11, 2003 at 10:59:14 Pacific OS: DOS 7.10/Win3.1 CPU/Ram: 200Mhz w/128 Mb
Comment:
After installing DOS 7.10/Win 3.11 for Workgroups, I consistently get "File allocation table bad on Drive C:\" error messages, whenever I try to boot Windows. When I return to the root directory, there are no difficulties. Don't exactly know where to start diagnosing the problem. Thanks.
Name: Rich Dennis Date: November 11, 2003 at 11:14:47 Pacific
Reply:
Is it a conflict between memory managers? DOS 7.10's HIMEM.SYS vs. Windows'? No idea. Thanks for any help anyone's willing to offer a newbie.
R.Dennis
0
Response Number 2
Name: yulin Date: November 11, 2003 at 13:00:41 Pacific
Reply:
"Don't panic, this isn't true. As a workaround, make sure that you start or quit Windows 3.x from the root directory of drive, e.g. C:\"
0
Response Number 3
Name: Wengier Date: November 11, 2003 at 14:51:07 Pacific
Reply:
This message is totally a false message, which is caused by a problem in WIN386.EXE(in 386 enhanced mode) in some environment. However, the false message "file allocation table bad" will only appear on some FAT16 drives, not on FAT32 drives. Just starting or quitting Windows 3.x from the root directory of drive(like C:\) solves the problem.
0
Response Number 4
Name: Rich Dennis Date: November 11, 2003 at 20:32:45 Pacific
Reply:
Tried that. Switched to root directory;typed win;got the splash screen, and then......nothing. No dice. No good w/ DOS 7.1 and Windows 3.11fW. Any other ideas?
0
Response Number 5
Name: Wengier Date: November 11, 2003 at 20:43:47 Pacific
Reply:
Still IFSHLP.SYS problem???!!!
More information about this, please look at the following thread!!
Name: Wengier Date: November 11, 2003 at 21:40:44 Pacific
Reply:
Or, there is even an easiler way: simply change "LASTDRIVE=32" to "LASTDRIVE=26" (or "LASTDRIVE=Z") in C:\CONFIG.SYS! The reason is that WFW 3.11 IFSHLP.SYS has problems reading the drive letters past Z!
0
Response Number 7
Name: Wengier Date: November 12, 2003 at 06:17:51 Pacific
Reply:
Now I have changed the default value of LASTDRIVE from 32 to 26(that is, Drive Z:)in MS-DOS 7.10 CONFIG.SYS, so this IFSHLP.SYS problem is solved forever.
Summary: Yes, I'm using a temporary swap file. I don't really see the need for a permanent one. Besides, having read what a permanent swap file can do to a FAT32 partition, I'd rather not press my luck. It ...
Summary: As a matter of fact you can. a normal DOS format just overwrites the File Allocation Table, it does not even delete the files, just hides them for you. If you have marked bad sectors on your harddrive...
Summary: Was getting bored with all this bullshit so here yar are NO ROM BIOS Bios Chip corrupted - replace Hard Drive faulty - replace Motherboard faulty - replace or technician repair DISK BOOT FAILURE, IN...
0 
windows 3.0 Boot Disk
