I know bad form replying to myself but I did further tests. The answer is both. I tested MS format in freeDOS and got the same result that FD format gave me. FD format in MS-DOS worked. Ok, so I tested the command interpreter just to find out if the kernel really is involved in this. FD command.com under MS-DOS accessed the disks without a problem. MS command.com failed to access the disks under the freeDOS kernel. So the answer is both. Fdisk and xfdisk seem to do their own thing and fail to access the disks, and the kernel couldn't be bothered that int 13H is being routed by something else.
Question: Does the kernel handle int 13H itself without bothering to use BIOS functions? But if that was the case why can't loading the proper device driver remove control of int 13H from it. Charles ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
