On Aug 26, 11:42 pm, schmidtd <schmi...@my-deja.com> wrote:
On Aug 26, 8:58 am, Polymorph <mike.a.steph...@gmail.com> wrote:> schmidtd wrote:
On Aug 26, 4:23 am, Polymorph <mike.a.steph...@gmail.com> wrote:
schmidtd wrote:
Thanks again for such a great program!
You're quite welcome.
However, I did discover that the format bug still appears to be there. I
formatted a blank 3.5" disk this morning using the 1.0.2 version and it
had the number of blocks set to 280 (instead of 1600) after the format
completed. It must think its a 5.25" disk or something?
Yes, it sounds that way. Famous last words: "I thought I fixed
that." If you format a second time, does it come out right?
No. I tried reformatting a 2nd time, but it didn't help.
Ok, I tried it here and formatting a previously unformatted disk came
out 1600 blocks. Two things I'd like to know about your setup:
1) if you put in another unformatted disk and ask for a (V)olume
display, what is the reported name and block count? I expect <I/O
ERROR> and 1600.
2) What 3.5" disk drive do you have? (Is it inside an IIc+?)
David, answering your questions:
1) I'll try this out when I get home tonight, but prior to formatting
the disk yesterday, I am nearly 100% sure that it displayed <I/O
ERROR> and 1600 *before* I formatted the disk. I'll try and confirm
this tonight with a different disk.
2) I have a Superdrive 3.5" drive connected to the standard IIgs drive
port (ie. *not* using a Superdrive card)
Another point of note is that I am formatting HD 3.5" disks - despite
people's warnings, I have had very little trouble using the HD disks
(I think I've had one disk fail out of a box of 25). But as I
mentioned, formatting the disk under System Utilities fixed the
problem (ie. after formatting in System Utilities the disk was
displayed as 1600).