In Thu, 27 Feb 2014 08:06:06 +0800, Eric Auer <[email protected]> wrote:
> > Hi Roy, > >> Forwarded from sourceforge bug tracker: >> https://sourceforge.net/p/freedos/bugs/115/ >> >> Boot FAT32 kernel (ex. ke2041_86f32) from A: and "format b: /u", then an >> error occurs. > > Does this only happen with the FAT32 kernel? > > Does this only happen with a FreeDOS kernel? > > Are your A: and B: actually 2 distinct physical drives? > > Does this only happen with /U or also with other modes? > Can you add the /D option to get more verbose messages? > >> A:>format b: /u >> Insert new diskette for drive B: >> Press ENTER when the right disk is in drive... >> Using drive default: 1440k (Cyl=80 Head=2 Sec=18) >> Please enter volume label (max. 11 chars): >> No label, disk will have no creation timestamp. >> Full Formatting (wiping all data) >> 100 percent completed. >> Preparing FAT area... >> Drive_IO(WRITE 1, count 1 ) [FAT12/16] [drive B*] >> >> Critical error during DOS disk access >> DOS driver error (hex): 01 >> Description: unknown unit for driver >> Program terminated. >> [Error 129] >> >> Format uses INT26, and this error occurs in kernel. >> When "dir b:" before format, then this error does not occur. > > If you only have 1 drive, this might be a DJ mechanism > issue, where A: and B: are actually the same hardware > and DOS has to keep track whether you name it A: or B: > at the current moment. Can you try with other FORMAT > tools? If the problem is really with the DJ mechanism > then I think other FORMAT tools could be able to try > harder to switch - both from A: to B: and back again. > > If you do DIR B: before format, what will happen? Is > the disk already formatted before you format it? > > Lots of questions but also an interesting problem :-) > > Regards, Eric > Reply from 7shi in tracker: I reply to the answer on the mailing list. https://sourceforge.net/p/freedos/mailman/message/32031925/ > Does this only happen with the FAT32 kernel? Yes. > Does this only happen with a FreeDOS kernel? > Does it mean other DOS, for example, MS-DOS? I've tested only with FreeDOS. > Are your A: and B: actually 2 distinct physical drives? Yes, but not with a real machine. I've tested in QEMU. I've created a boot floppy "fd1.img" with ke2041_86f32. $ dd if=/dev/zero of=fd2.img bs=512 count=2880 $ qemu -fda fd1.img -fdb fd2.img Starting SeaBIOS ... (snip) FreeCom version 0.82 pl 3 [Dec 10 2003 06:54:37] A:\>format b: /u > Does this only happen with /U or also with other modes? Without /U, only in first (unformatted) the error occurs. With /U, always the error occurs. > Can you try with other FORMAT tools? No, I don't know other FORMAT tools for FreeDOS. > If you do DIR B: before format, what will happen? > Is the disk already formatted before you format it? [Unformatted] A:\>dir b: Volume in drive B has no label Volume Serial Number is EF27-3654 File not found. [Formatted] A:\>dir b: Volume in drive B has no label Volume Serial Number is 3970-18E7 File not found. > Can you add the /D option to get more verbose messages? I've attached the log. http://sourceforge.net/p/freedos/bugs/_discuss/thread/f4b953f8/d8f0/attachment/log.txt ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
