ried
Well-known member
Edit: Trying MacZip.
Edit 2: Holy cow! It works!
Last edited:
Yeah, sorry, I didn't have an appropriate version of Drop Stuff on the machine to .sit it and preserve the resource fork.How does one execute this on Mac OS 9? It expands as a document / text file, with an XtraStuf.mac folder beside it.
Edit: Trying MacZip.
Corrected, and thank you allNot me, all cheesestraws, dosdude1 and joevt
Yes, this should rectify this issue with any PCI card that utilizes a PCI-PCI bridge.A nice early Christmas gift - thanks all for putting your minds to this. Does this mean I can try my luck with other FW/USB combo cards (eg Keyspan, SiiG) as opposed to the oversized Tango 2.0 in my TAM that blocks airflow venting out the top? Great stuff.
It's wonderful that this is the case. It was encouraging enough when cheesestraws was able to prove additional cases could be added via the old patch method, but obviously this was the dream solution, now realized Probably worth a "final" necro on this thread: https://68kmla.org/bb/index.php?threads/usb-firewire-cards-or-chipsets-that-work-in-the-tam.5760/ since it's still a top hit for people searching for why their card isn't working.this should rectify this issue with any PCI card that utilizes a PCI-PCI bridge.
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 my GitHub, if you want to make one yourself.Many thanks to all who have their time in this! This is really brilliant work; I've been switching between trying to understand all of these leaps and actually testing it on my TAM throughout the day.
It's wonderful that this is the case. It was encouraging enough when cheesestraws was able to prove additional cases could be added via the old patch method, but obviously this was the dream solution, now realized Probably worth a "final" necro on this thread: https://68kmla.org/bb/index.php?threads/usb-firewire-cards-or-chipsets-that-work-in-the-tam.5760/ since it's still a top hit for people searching for why their card isn't working.
In my own case, a rough and dirty test of this works without a single flaw. I can boot from the 30GB ATA drive and press cancel on the dialogue to format my 500GB osx Firewire drive with my USB mouse. Excellent.
View attachment 50450
If I switch them in place though, I get weird delays, conditional bus errors on boot, and no mountable volumes on the CF card. Assuming it's a simple issue between the CF/adapter and the Trio (removing the CF card from the ATA adapter resolves everyting, regardless of the 30GB being present on the onboard,) I presume a different ATA-CF solution (cable select mode?) might be the fix, but a different SSD will also work. Too bad, it was about to look pretty.
View attachment 50451
I'll make it perfect laterish...
I think I posted an old version of lspci for OpenFirmware. Can you try this newer version? It will probe the BARs to detect their sizes. I would like to know if the `assigned-addresses` and `reg` properties match the BAR sizes.Finally got to grab my PowerMac 6500, I have now gotten the information you have requested, using your LSPCI script. Output is attached.
Done, got the output both with your NVRAMRC patch and without.I think I posted an old version of lspci for OpenFirmware. Can you try this newer version? It will probe the BARs to detect their sizes. I would like to know if the `assigned-addresses` and `reg` properties match the BAR sizes.
Thanks. Looks likeDone, got the output both with your NVRAMRC patch and without.
ohare
has a 512K BAR but reserves 1MB in its fcode.The product / manufacturer id changes between different realtek cards with the same chipset (depending on the board manufacturer) - compare the two driver versions I sent you a while back and make changes at the points I did to match the ids of you card... might be all thats needed.Can confirm your patch works with all the combo cards I have here. Good stuff!
Ethernet on the three-way card doesn't work, but it's detected, and I'm apt to put that down to Realtek weirdness rather than Gazelle weirdness.
The product / manufacturer id changes between different realtek cards with the same chipset (depending on the board manufacturer) - compare the two driver versions I sent you a while back and make changes at the points I did to match the ids of you card... might be all thats needed.
Ah, curses.No, I did that: the interface was detected and came up but according to the switch was just sending gibberish: byte count kept going up, but 0 valid frames.