pax
Well-known member
I think the IIsi stock ROM does support HD20, while it’s missing from IIx, IIcx, IIfx and SE/30.On the subject of HD20 support, I don’t believe my ROM has this, since it’s not in the IIsi base ROM (right?)
I think the IIsi stock ROM does support HD20, while it’s missing from IIx, IIcx, IIfx and SE/30.On the subject of HD20 support, I don’t believe my ROM has this, since it’s not in the IIsi base ROM (right?)
Huh, I just checked on my SE/30 and you're right, the IIsi ROM does support HD20 booting. That's strange because it says in the Mac IIsi Developer Note that it's only supported with an INIT. Well that's good!I think the IIsi stock ROM does support HD20, while it’s missing from IIx, IIcx, IIfx and SE/30.
I'm not sure why BMOW used such a thin PCB in light of the fact that the IIsi and IIfx ROMs all fit perfectly in the SE/30 in terms of thickness, with no connectivity issues whatsoever. Meaning, if you make a ROM thick enough to fit an SE/30, it should fit those other Macs just fine too. Maybe there was another Mac model that required a thinned PCB, I don't know.Regarding the thickness, I was able to get a few quotes for 1.3mm boards. The best price was around $4 each, which is not bad if it solves the major issue with these ROM SIMMs.
It’s the imperial-to-metric transition that’s responsible. Original SIMMs are all nominally 0.05 inches thick, which is 1.27mm. Once upon a time, 0.05 in. was a common PCB thickness, and so was 0.06 in. (1.524mm). Now, however, metric dimensions are standard, and the commonly available thicknesses have been rounded to 1.2mm and 1.6mm. 1.6mm is way too thick, but 1.2mm is on the edge of the acceptable thickness. For example, one SIMM socket’s data sheet stated a minimum PCB thickness of 1.19mm. Depending on the type of socket used, which has some correlation with the model of Mac, as well as the thickness variation among boards, it works more or less reliably.I'm not sure why BMOW used such a thin PCB in light of the fact that the IIsi and IIfx ROMs all fit perfectly in the SE/30 in terms of thickness, with no connectivity issues whatsoever. Meaning, if you make a ROM thick enough to fit an SE/30, it should fit those other Macs just fine too. Maybe there was another Mac model that required a thinned PCB, I don't know.
Hmm, yes, this could certainly help. Both SIMMs have used 1oz copper thus far. 3oz is an unusual option but 2oz will at least make up half of the difference, if indeed the fabricator doesn't use a thinner core substrate to cancel it out. This will cost less than a 1.3mm board since the 2oz copper is a common option. I will try this in the future.If ROM thickness is 0.7mm too thin, why not up the copper?
I don't have an Apple CD-ROM to test and confirm if the extension would not only load under 7.1 but also control the drive too. Perhaps someone else can do that though.Thanks for the feedback! I'll install 7.1. Now about the CD extension, I generally use FWB CD Toolkit because I can set a massive driver cache size with it, but I think it would be more appropriate to include Apple's CD extension. Now, version 5.3.1 seems to be the right version to use, but this evidently shipped with System 7.6. Presumably this'll work with 7.1 (being that 7.5 and 7.6 are basically a bunch of extensions on 7 lol) but can anyone say otherwise?
Hmm, yes, this could certainly help. Both SIMMs have used 1oz copper thus far. 3oz is an unusual option but 2oz will at least make up half of the difference, if indeed the fabricator doesn't use a thinner core substrate to cancel it out. This will cost less than a 1.3mm board since the 2oz copper is a common option. I will try this in the future.
I’m going to throw the freeware CD Sunrise extension into the discussion here because that is small, universal and has been very reliable for me at least.Apple's CD extension
Very very very much this.Macsbug! Please please please include Macsbug.
There's another one called ADB Reset that I keep on my KVM'd Macs.“ADB Reset” seems to be ADB Renewer.
When switching back to a Mac from the KVM, sometimes the mouse fails to re-initialize. KBD never failed so I could hit TAB A and press enter to run ADB Reset the bus and bring the mouse back to life.I read the description of what it does, but I’ve actually never used it before. What is an example situation that crops up where this software solves the problem?
Same thing as mechanical KVM switching, but the KVM switching eliminates joggled insertion hotplugging, controller endangerment.The only time I had problems with ADB was in the distance past when I accidentally plugged in an ADB device while the Mac was powered, which is something you’re not supposed to do, as you could damage the hardware.