| Click here to select a new forum. |
| 400k floppy drive glitchfest (flashing warning?) |
Posted by: cheesestraws on 2021-08-30 13:04:48
I have a 400k floppy drive that, when trying to boot a known good copy of System 2.0, does, erm, this:
Words fail me. Any ideas, other than turning it into an art piece? |
Posted by: Nixontheknight on 2021-08-30 13:06:19
Have you lubricated the drive rails and spiral gear? Are the heads clean? |
Posted by: cheesestraws on 2021-08-30 13:09:11
I have lubricated and cleaned it (though perhaps not as well as I should?) the heads are clean. Sony Test shows the stepper as correctly working. I wrote this disc on the machine itself and it verified OK. The machine boots fine from other floppy drives using this 2.0 image. |
Posted by: Nixontheknight on 2021-08-30 13:10:07
I have lubricated and cleaned it (though perhaps not as well as I should?) the heads are clean. Sony Test shows the stepper as correctly working. I wrote this disc on the machine itself and it verified OK. The machine boots fine from other floppy drives using this 2.0 image. Maybe the drive itself is dead. Do you have any other 400k internal drives you can swap in? |
Posted by: cheesestraws on 2021-08-30 13:11:32
I think going from the above, the drive may be undead. I do not, I will have to find one. |
Posted by: mg.man on 2021-08-31 01:31:03
I have a 400k floppy drive that, ... does, erm, this: Oooo... that *is* weird! I've PM'd on our chat... |
Posted by: monoxrom on 2021-08-31 04:33:56
I have the same problem on macintosh ED without floppy drive)
|
Posted by: cheesestraws on 2021-08-31 04:47:32
I have the same problem on macintosh ED without floppy drive)
That's extremely interesting; in my case it only happens when trying to boot off that one floppy drive. My other drive is fine.
Now, I thought it was reading garbled data from the floppy drive and the result was that, but perhaps it's actually reading code from a place where code isn't in the ROM (?) and the drive in my case is just kicking that off? |
Posted by: techknight on 2021-08-31 13:20:09
its acting like a memory out of bounds condition. like a pointer that got sent off into the weeds which just starts filling up memory with w/e, eventually hitting screen memory. So yeah, its not executing or reading the code properly. |
Posted by: ScutBoy on 2021-08-31 13:24:52
Agreed that seems more like a software problem than a hardware problem... unless there's some kind of glitch in the electronics of the drive itself... |
Posted by: cheesestraws on 2021-08-31 13:56:12
Well, it only happens with that one drive; other drives are OK, as is the Floppy Emu, so it's certainly something to do with that drive. It also doesn't always do precisely that, sometimes it wanders off into a different bit of memory, makes the Welcome To Macintosh spasm like that, then draw lines all over the screen and then ends up back at the 'not a system disc' icon. And very occasionally, and funniest of all, it plays loud farting noises for a while then does a good vapourwave visuals impression.
Theory time with cheesey [anyone want to write me a theme tune?]: This drive had issues stepping beyond certain tracks, and I have a feeling that something is off so that it isn't reading properly after a certain point on the disc; this will eventually prevent a function returning somewhere in the OS, because it will start running the function then be unable to read the bit that returns to caller, and thus ends up with execution wandering off into the depths of memory.
But it's funnier to claim that the drive is possessed. |
| 1 |