[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ADTPro with fast Disk II reads released

Polymorph wrote:

On Aug 27, 11:42 am, "Michael J. Mahon" <mjma...@aol.com> wrote:


Polymorph wrote:


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).


There have been several reports of weird formatting problems with
the Superdrive.  I always attributed them to the combination of
Superdrive and Superdrive controller, but maybe the drive itself
is the problem.

The usual symptom is a faulty format after attempting to read a
non-standard disk--like, perhaps, an unformatted one...

-michael

NadaPong: Network game demo for Apple II computers!
Home page:  http://members.aol.com/MJMahon/

"The wastebasket is our most important design
tool--and it's seriously underused."- Hide quoted text -

- Show quoted text -



Michael, thanks for the info - I was unaware of that. But there still
seems to be the issue of why formatting the disk using the System
Utilities "fixed" the problem. This would imply that the System
Utilities is formatting the disk differently than ADTPro would it not?


I'm guessing that it is caused by an incomplete initialization of
the drive, so that residual state from a previous use somehow
affects the subsequent format operation.

So any program that, accidentally or by design, clobbers the drive's
residual state will work fine.


If no one else is having this problem then maybe it is something to do
with the Superdrive. And I thought I was lucky having one of these
drives.  :-)


The problem seems to be specific to Superdrives.  So far, it has
never been enough of a problem for me that I cared.  ;-)


I also have a ROM01 IIgs with a regular 3.5" drive attached that I can
also test. I'll perform some more testing tonight and post back with
results.


I'm guessing that you'll find no problems.

-michael

NadaPong: Network game demo for Apple II computers!
Home page:  http://members.aol.com/MJMahon/

"The wastebasket is our most important design
tool--and it's seriously underused."