The 630 can take up to a 128mb SIMM in a 32x32 configuration, I believe. The second simm slot, on boards that have it, can only take up to 64mb (I think you need to use the 128mb SIMM, and only 64 of that is visible). There's several threads about it, and trag has described the SIMMs to use...
Just because the Classic, LC, and IIsi were released together doesn't mean they share any architectural similarities.
The IIsi uses the MDU memory controller found in the Iici.
The Classic uses the BBU memory controller (well, calling it a memory controller is a stretch, it acks some bus...
The address map for the Classic puts ROM at the 4mb mark, so it's kinda stuck to 4mb. All the 68000 macs use this address arrangement, with the exception of the Portable. The Portable is the odd one here, where it maps ROM at the 9mb mark.
In the 68000 machines you can't really rearrange...
JFYI, with the 610 series, you can't interleave RAM SIMMs because of the way they arranged the banks. It has half the SIMM slots, and rather than just leaving off the top 2 SIMMs, they've split things up so every other bank will be empty, preventing any interleaving of the SIMM slots. 8mb...
The memory controller on the 605 supports interleaving, but the 4mb of onboard ram is not interleaved because it is just 4mb in a single bank.
The RAM SIMM will nearly always span banks and therefore be interleaved. Interleaving can give up to 10-15% speed improvement depending on how it is...
I don't have an LC, but I looked at the ROM disassembly a bit. There are definitely limitations in ROM, and from the ROM, it is likely the VISA memory decoder is limited to 10mb.
The LC entry in the table the ROM has to tell it about the machine, says there are 2 banks of RAM: one up to 8mb...
Isn't there solder points for a ROM SIMM socket underneath those DIP sockets? Desolder the DIPs and solder in a ROM SIMM socket, and use a dougg3 ROM SIMM! :)
To program them, you pretty much need a miniprog3, which is about $90. It's only used once in the initial programming, since mmcmaster has the software update via usb working. He's made it so any jtag or swd programming device should work, but I haven't found any software other than the...
That seems about right to me. Using the SCSI to CF setups, formatting a 4GB CF card on an SE/30 takes long enough that I just kick it off and go do something else for a while. Easily a couple hours. Those low level formats + verify takes a while.
Maybe time for a sanity check?
Ok, I've got a lot to say about these statements, some of which was covered by Gorgonops, but mostly I can't reconcile it with the later statement:
The initial argument is don't do software raid because of performance, then recommending USB 1.1?
Trash's initial...
Veering off topic here, but speaking of higher resolutions for older machines... The PCI ATI Radeon 7000 64MB can drive 1920x1200 over DVI. The PC version of the card can be had for cheap, but the EEPROM on the board is too small and needs to be swapped for a larger version. After that, it...
Awesome, thanks, that's what I needed. Sorry about the confusion there, I even looked at the schematic while assembling it, and it says "22". I just figured "22k" and went on my merry way.
I've got one fully working, the other one probably just needs some touchups.
Thanks again!
dougg3 had a similar thought. He found these chips have nonvolatile latches, but they don't seem relevant this particular problem, and from what I can tell, should be included in the hex files (which also encode the processor type and other metadata, not just the binary code).