Search results

Make sure you have a red-striped floppy drive cable, and not the yellow-striped.

I have seen that behavior on a 512K Mac when the desktop file became infected with a vintage virus (CDEF?) which produces this error ONLY on 128K & 512K macs. So you should probably run Virex or Disinfectant on these floppies in your Plus to see if it finds something.

@marcelv, thanks for confirming.

Interesting that you agree. I can’t find any authoritative source for which goes where. If swapping them solves the problem, or not, I hope you’ll let us know.

@macintosh2002, did you ever get your Classic II rev. B logic board working? I’m having similar problems with that same board, and just now found your thread. Looking at your pix, I wondered if your ROMs have been installed correctly? On mine (see attachment) and in the few images of this board...

I spoke too broadly. CDEF, which I just encountered, seems to have been less troublesome at the time than MDEF & other viruses — according to lowendmac, anyway.

I let my guard down, thinking old Mac viruses were no threat anymore. I understand these old viruses weren’t terribly malicious, as viruses go, on the Mac II-era systems they were targeting. This obscure effect on older systems like my 512k was way more annoying.

For the record: I found the problem! The desktop folder on the HD20 was infected with CDEF, a “classic” computer virus. Evidently CDEF, like it’s predecessor MDEF, can cause 128K & 512K macs to crash. https://lowendmac.com/2015/classic-mac-os-viruses/ Disinfectant 2.1 found it. It also found...

Thanks for the suggestions! The floppies I’m using are absolutely 400k; and I’m fairly certain they’re MFS. But the Mac 512K boots fine from these floppies So they’d have to be 400K MFS, wouldn’t they? If they weren’t, I’d get the Sad Mac and 0F0064 or whatever, right? After booting...

I’ve got an unmodified 512K logic board that boots up fine, but when I double-click (or use File > Open) on an internal or external 400k floppy, it gives me “the bomb” with System Error ID = 02. Seems odd that it can read a disk to boot, but can’t view the disk content from the desktop. It...