Egan Ford

When writing to a diskette ADTPro gets stuck at 273 (of 280) and the
floppy drive is making a lot of noise. I've had this problem with
my //e and //c on and off ever since I started using ADTPro (versions
1.1.5 - 1.1.9). It's worse on the //e. It does not matter if the
diskette image is DOS 3.3, ProDOS, or CP/M. Same problem in the same
place (273). I've tried 3 different brands of diskette. Formatting
and reformatting.

Reading diskettes works 100% of the time.

Others seen this? Thanks.

Michael J. Mahon

Egan Ford <datajerk@gmail.com> wrote:
> When writing to a diskette ADTPro gets stuck at 273 (of 280) and the
> floppy drive is making a lot of noise. I've had this problem with
> my //e and //c on and off ever since I started using ADTPro (versions
> 1.1.5 - 1.1.9). It's worse on the //e. It does not matter if the
> diskette image is DOS 3.3, ProDOS, or CP/M. Same problem in the same
> place (273). I've tried 3 different brands of diskette. Formatting
> and reformatting.
>
> Reading diskettes works 100% of the time.
>
> Others seen this? Thanks.

Have you tried a different disk drive?

-michael - NadaNet 3.1 and AppleCrate II: http://home.comcast.net/~mjmahon

Kevin Dady

On Dec 29, 7:45*pm, Michael J. Mahon <mjma...@aol.com> wrote:
> Egan Ford <dataj...@gmail.com> wrote:
> > When writing to a diskette ADTPro gets stuck at 273 (of 280) and the
> > floppy drive is making a lot of noise. *I've had this problem with
> > my //e and //c on and off ever since I started using ADTPro (versions
> > 1.1.5 - 1.1.9). *It's worse on the //e. *It does not matter if the
> > diskette image is DOS 3.3, ProDOS, or CP/M. *Same problem in the same
> > place (273). *I've tried 3 different brands of diskette. *Formatting
> > and reformatting.
>
> > Reading diskettes works 100% of the time.
>
> > Others seen this? *Thanks.
>
> Have you tried a different disk drive?
>
> -michael - NadaNet 3.1 and AppleCrate II:http://home.comcast.net/~mjmahon

well since the op mentioned a //e and a //c I would assume so ....

what os is the host computer, have you tried other host computers, are
you using "real" serial ports or a usb thingie, and if your using
"real" serial ports are they -12+12 RS232, or the more recent eh 0-5
will cut it variety?

dunno, just shooting out idea's

Egan Ford

On Dec 29, 7:10*pm, Kevin Dady <ke...@hackaday.com> wrote:
> On Dec 29, 7:45*pm, Michael J. Mahon <mjma...@aol.com> wrote:
> well since the op mentioned a //e and a //c I would assume so ....

Correct.

> what os is the host computer, have you tried other host computers, are
> you using "real" serial ports or a usb thingie, and if your using
> "real" serial ports are they -12+12 RS232, or the more recent eh 0-5
> will cut it variety?

The data actually makes it to the //e, it's the writing to disk that
fails. I am assuming that there is some level of serial data
integrity checking and that the source of the problem is the client
writing to disk.

To answer your questions. I've tried two different MacBooks and two
different USB to Serial adapters and two different cables and some
permutations of the aforementioned. BTW, none of that was to
troubleshoot the problem. It is that my equipment has changed
overtime. Like I said I've had this problem since 1.1.5.