• Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.

Has anyone ever seen a cleaner SE?

The drive isn't bad, it has no read/write issues with 1.44 disks.
Actually it obviously is bad because it doesn't behave reliably, but it might not be bad in a way that directly affects its ability to read disks. From your description of the behavior in which it initially refuses to acknowledge the 400/800k disk until it's been mounted in another drive *at which point it works* I would hazard a guess that there's something going on with particular drive that is breaking the usual "detect what kind of disk is inserted" routine that should happen when a disk is detected; when it's the only drive it's defaulting to 1.44 mode and giving up after that, but when you do the little detection dance it might be leaving the the SWIM in the correct mode so when you come back, viola, it works. What people are objecting to here is the contention that all drives with this model number normally behave this way; clearly this behavior is not normal and Apple never would have gotten away with selling a drive that behaved like this.

What *exactly* is broken with your individual drive is a good question; unlike normal floppy drives for PCs which are pretty "dumb" devices Macintosh drives have a rudimentary amount of stateful intelligence which is communicated via the PH0-PH3 lines. The motor behavior and head write current are completely different in the two modes of operation of the SuperDrive so there will be a register on it that needs to get flipped when it switches from one to the other; there might be documentation out there as to how exactly detection and mode switching works, reading that might clue you in on where the possible failure points lie. Off the top of my head I have no idea if SuperDrives *themselves* have enough intelligence on them to work out if there's a valid format of either type present, or if there's an elaborate dance that goes on between the SWIM and the drive every time a disk is inserted to figure it out. (It's almost certainly the latter.) It could be as simple as a bad connection on one of the PH* lines.

 
I'd like to see a couple other drives swapped in and see if the results are the same.  There is just something not right about what's happening there.

Besides, the argument that "it doesn't work now in 2019 thus it never worked and was not designed to" does not hold any water when it comes to floppies.  I have some that work perfectly in machines A, B, and C but not D, E or F and vice versa.  Other disks work fine on Tuesday but not Friday or every 3rd Monday.  Quite a bit of our hardware is FAR past its life expectancy by decades now and flaky, weird stuff is to be expected.  And that is the reason I have imaged hundeds of floppies and am not shocked when the originals or even new ones do weird stuff like this - I just dump the image onto another disk and move on.

 
Actually it obviously is bad because it doesn't behave reliably, but it might not be bad in a way that directly affects its ability to read disks. From your description of the behavior in which it initially refuses to acknowledge the 400/800k disk until it's been mounted in another drive *at which point it works* I would hazard a guess that there's something going on with particular drive that is breaking the usual "detect what kind of disk is inserted" routine that should happen when a disk is detected; when it's the only drive it's defaulting to 1.44 mode and giving up after that, but when you do the little detection dance it might be leaving the the SWIM in the correct mode so when you come back, viola, it works. What people are objecting to here is the contention that all drives with this model number normally behave this way; clearly this behavior is not normal and Apple never would have gotten away with selling a drive that behaved like this.

What *exactly* is broken with your individual drive is a good question; unlike normal floppy drives for PCs which are pretty "dumb" devices Macintosh drives have a rudimentary amount of stateful intelligence which is communicated via the PH0-PH3 lines. The motor behavior and head write current are completely different in the two modes of operation of the SuperDrive so there will be a register on it that needs to get flipped when it switches from one to the other; there might be documentation out there as to how exactly detection and mode switching works, reading that might clue you in on where the possible failure points lie. Off the top of my head I have no idea if SuperDrives *themselves* have enough intelligence on them to work out if there's a valid format of either type present, or if there's an elaborate dance that goes on between the SWIM and the drive every time a disk is inserted to figure it out. (It's almost certainly the latter.) It could be as simple as a bad connection on one of the PH* lines.
Thanks for clearing this up. That really did help. I agree with your conclusion. I am going to look into it more once I get my 40SC up and running.

 
Question...

i just got a 40sc. And the original 40mb quantum 5.25 drive was dead. It wouldn’t format in us sc or anything.

then I used lido 7, and it worked! Now, I was able to put system 6 on it and it seems to work fine.

is the drive still bad, or is it possible that it just corrupted the data and needed to be re-partitioned...

 
Back
Top