Search results

I have another absolutely MASSIVE update for you all... I was able to implement an LZSS decompression algorithm in the ROM, and use it to decompress a stored LZSS-compressed version of the OS9 NDRV. As such, the ROM has been reduced in size to UNDER 128K! This means that you can now flash it...

Unfortunately, all the available Mac ROMs are very much closed source, so there's not much that can be done with those outside of reverse-engineering. However with that said, I may some day write my own custom firmware for these cards, which of course I then would make open source.

These cards are top-notch, and won't exhibit any issues you normally get with IDE to SATA adapters (and also solve a compatibility issue with some G4 machines present in the cheap Chinese Sil3112 cards). The main issue with those adapters comes from the fact that they use the horrible JMicron...

Yes, only those 3 chips are compatible. I originally thought the AM29LV040 was not (as you can see by my testing picture), but looking at the code (control flow diagram of patched OS9 NDRV attached), you can see it checks for the ID of that chip (01 4F), as well as the IDs of the MX29LV040 (C2...

Yes, awesome! If you can, try it in OS X as well... The OS X patch is completely separate from the classic Mac OS one, and was significantly more difficult. If OS X can mount a drive connected with the SST39SF040 ROM installed, it is properly patched as I intended.

No option ROM is needed for a Windows machine (I believe). But if needed, you could always flash a standard Sil3112 PC option ROM.

I would still like to find the 5.0.7 version of this SeriTek ROM if possible, which apparently fits on a 128K EEPROM. That way I could patch this version as well, and it could be used on cards with 128K EEPROMs without having to swap the EEPROM.

I have a huge update for you all. After many hours of reverse engineering, I was able to SUCCESSFULLY PATCH that SeriTek 1S2 ROM for the SIl3112 cards, allowing it to work with ANY 512K EEPROM! It functions just as it would with a "supported" EEPROM, working with and booting both OS X and OS9...

I’d like to make it compatible with other machines, so height would have to remain standard. Another idea I had was to make a custom riser for the TAM specifically with a device or two on it.

I still intend to make my own custom version of a combo card... Just let me know what devices would be best to implement. I can have up to 4 devices on the card using the PLX PCI6150 PCI-PCI bridge. The biggest constraint to a design with a lot of devices is physical space on the card... I’d...

Well, another reason I bring this up is because there's this one ROM, for the "SeriTek 1S2" Sil3112-based card, that has some weird protection in it making it ONLY work with two specific EEPROM types, a PM39LV040 or MX29LV040. As such, some users may want to install one of these onto this card...

One thing I'd recommend is ditching the TSOP EEPROM in favor of a PLCC32 one (which can be socketed for even better ease of use). That way it can be more easily soldered and programmed externally if necessary. Also, the Sil3112 has two pins that can be used to configure RAID mode enable and BA5...

Done, got the output both with your NVRAMRC patch and without.

I’ve actually been working on my own custom 2.5” IDE SSD, of which the design and PCBs are already complete. All I need to do now is assemble the drives, which I’ll do in about a week or so after the holidays, and then I can start selling them. PCB design and schematic will also be available on...

Yes, this should rectify this issue with any PCI card that utilizes a PCI-PCI bridge.

It works great! I can’t believe the onboard video FCode was causing the issue the whole time...

No way, that seemed to have worked!!! Onboard video still working as well! Going to test further now. 0 > dev / ls FF828518: /PowerPC,603@0 FF828D90: /chosen@0 FF828F68: /memory@0 FF8290B0: /openprom@0 FF829170: /AAPL,ROM@FFC00000 FF829388: /options@0 FF8298E0: /aliases@0 FF829B78: /packages@0...

Finally got to grab my PowerMac 6500, I have now gotten the information you have requested, using your LSPCI script. Output is attached.

I've added what I believe should be able to access and execute the option ROM of the SATA portion of the card, though I don't think it will work at this time, as I don't think the script produces some of the necessary "reg" properties that are needed to load the option ROM (also it is probably...

Could you display the .properties of the SATA device in the device tree in the 6500?