On 2012-11-09 19:42 (GMT+0100) Eric Auer composed: >>> I was going to install FreeDOS 1.1 on a USB drive within qemu 1.1.1 on >>> Opensuse 12.2 32 bit. After selecting the language in the FreeDOS >>> installer, my notebook was busy during the next hour with thousands of >>> thousands of messages like "Run chkdsk: Bad FAT I/O: 0x...".
> The kernel produces that message when "getblock" fails. Bernd, > the message is printed by "clusterMessage" and "getblock" is a > macro for "getblk" (x, y, FALSE) which apparently is, more or > less, a wrapper for "dskxfer" to let BUFFERS do their work... > Probably something tried to access the drive as if it already > was formatted while it was not, maybe failed to set a flag to > mark the drive as unformatted in some internal processing... The Bad FAT I/O: 0x000000x topic has appeared on the DFSee mailing list several times without leading to any solution, e.g.: http://tech.groups.yahoo.com/group/dfsee-support/message/10101 http://tech.groups.yahoo.com/group/dfsee-support/message/12917 http://tech.groups.yahoo.com/group/dfsee-support/message/13536 http://tech.groups.yahoo.com/group/dfsee-support/message/14049 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
