The FW/USB/SATA cards that work in this application are probably a better solution. But the Trio is neat. Found mine on Buyee.jp in case you use that site.
-
Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.
The Great Gazelle PCI Hack Thread, Part 2
- Thread starter cheesestraws
- Start date
Yeah I have some of those I’ve just always wanted a trio neat bit of history that one. This whole thread is amazing though. I’ve yet to try out the latest hack here but I’m super excited to try it when I unbury those systems again.
Bumping this as I think it got missed in the excitement!
Are the issues with the S900 at all related or similar to the Gazelle's issues?
The solution at #232 doesn't explain the real problem. It's a workaround which postpones the problem by probing the ATI fcode last after all the other PCI slots/bridges are handled.
Does the S900 have an ATI chip? If not, then it's probably a different problem.
Are there any posts that describing the S900 issue?
A patch depends on the version of Open Firmware and the type of machine. A rom dump is required to create a patch.
Wow! I hunted down several 5500/6500 boards over the years and was so disappointed when my pair of Trios proved incompatible with them. Playtime commences! Only have my 6360 and one 6400 board but their resolution limitations have kept the Trio itch at bay to date.
Fabulous work gang!
Fabulous work gang!
What???
Got a list of those cards to look out for? Just USB/SATA trumps Trio in my book.The only FW device I have is a Zip Drive. If there's not a FW interfaced NIC -> fast Ethernet available, I can't think of much use for it these days given SATA? If there's none available, such might make a really neat project?
What???
The only FW device I have is a Zip Drive. If there's not a FW interfaced NIC -> fast Ethernet available, I can't think of much use for it these days given SATA? If there's none available, such might make a really neat project?
The Great Gazelle PCI Hack Thread, Part 2
Hi! It was funky to read this quest just after viewing this video from dosdude1 :D
68kmla.org
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 probably try to stick with the dimensions of the SIIG card I’ve worked with before, unless someone can let me know what the absolute maximum dimensions of a card could be that would still fit in a TAM.
For the TAM you can make the card taller than standard PCI, at least up until it might conflict with the G3 card.
edit: If you can constrain it to fit within the space of the CSII NIC, I've got a project here somewhere around here where I developed the spec for a TwinSlot PCI riser to allow for a great VidCard to be installed in the primary slot and second PCI card in the NIC/Riser combo cubic. Besides, isn't a USB NIC a bit faster than the available CSII NIC? I've got a cardboard/connector prototype, but not up to board design/fab at this point in my quest.
edit: If you can constrain it to fit within the space of the CSII NIC, I've got a project here somewhere around here where I developed the spec for a TwinSlot PCI riser to allow for a great VidCard to be installed in the primary slot and second PCI card in the NIC/Riser combo cubic. Besides, isn't a USB NIC a bit faster than the available CSII NIC? I've got a cardboard/connector prototype, but not up to board design/fab at this point in my quest.
Last edited:
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.
What about a small daughter card that would probably not really add to the thickness but give you more PCB real estate. Seems an appropropriate solution given the vintage nature of our stuff as well, lots of our old cards did it that way to get extra room.
@cheesestraws
Would it be feasible to combine your force32 with the nvramrc patcher program? An extension that on boot checks the state of nvramrc, and if it isn't patched, write the patch and reboot?
Would it be feasible to combine your force32 with the nvramrc patcher program? An extension that on boot checks the state of nvramrc, and if it isn't patched, write the patch and reboot?
@cheesestraws was saying that booting from FDD was something he'd like to avoid. Was wondering if a purpose dedicated, tremendously simplified, read only version of BMOW's FloppyEMU setup would be a possible solution?
For TAM it doesn't matter, but for any other Gazelle machine it would be nice if they supported two FDDs for such purposes. I'm guessing not and hoping a bog simple EMU implementation might be scripted to eject/unmount itself to free up use of the single FDD available after it does the dirty?
Sorry if it's moot, haven't had a chance to re-read the project or even be able towrap my head around the goings on when/if I can make the time for review.
For TAM it doesn't matter, but for any other Gazelle machine it would be nice if they supported two FDDs for such purposes. I'm guessing not and hoping a bog simple EMU implementation might be scripted to eject/unmount itself to free up use of the single FDD available after it does the dirty?
Sorry if it's moot, haven't had a chance to re-read the project or even be able towrap my head around the goings on when/if I can make the time for review.
Hey @Trash80toHP_Mini, it's probably worth catching up with the thread. The issues have been completely solved by joevt's script and it 'sticks' as long as you have a battery and don't nuke the nvramrc, just like the sonnet patch, but better and universally for all similar 'bridge' cards.
Don't mind my question to cheesestraws, it is just me thinking out loud, with me not having a battery in my 6500. I'm not sure that anything floppy related is needed at the moment and think you have in mind when we were talking about running a longer script from a floppy disk as a possible answer. Joevt's script is way shorter, so this doesn't matter.
Does that make sense, or did I misunderstand what you meant?
Is a battery required if you have AC connected? I guess it will be annoying when you get a power outage.
No time and little understanding here, sorry
I tend to think in terms of simple hardware hardware solutions that avoid problematic battery/power outage resets of systems.
Good to know there is a workaround for needing boot media of any sort to set things up to run properly at startup. My machines tend to sit around for long periods while I play with others or work out theoretical flights of fancy.
I think you got it, does my reply make sense to you?
Sadly I think it resets with every cold start, but not having a battery is really my problem, not the computer's
The only full solution would be new ROMs and I wouldn't bother replacing them "just in case" even if there was a new fixed version. I don't mind re-applying at the start of the day.
My though tagging cheesestraws was if I fit a small IDE DOM to the IDE port, and install an OS with the patch as an extension that loads early in boot, it can check if the patch is applied, run it if not, restart and you're away.
Best thing is if the SATA is your boot drive it should double boot (initially partially from the DOM up to the point the check/patch extension loaded), but when you get to the desktop it will be your SATA drive, even if you didn't have the patch when you first powered on. You'd potentially only lose a few seconds on first boot.
You of course could still boot from the DOM if you selected it as your startup device.
Other than the fact that I created the patch application, not @Phipli ... it would be nice if people's work was accurately credited in youtube videos, although I know the youtube crowd is not fond of me. A correction would be nice, @omgmonsters
At least the screenshot of my post on the screen had my attributions to you and joevt!
I felt quite guilty just resedit hacking the patch together from other people's work that I didn't even understand. All I did was 10 seconds of copy pasting a text field.
Similar threads
