zefrenchtoon
Well-known member
Hi!
It was funky to read this quest just after viewing this video from dosdude1
It was funky to read this quest just after viewing this video from dosdude1
It would work if we put a longer script on a floppy disk...I'm not going to rule it out as a possibility, I just think someone better than me at making very compact forth would have to have a go![]()
It was me talking about itJust went around looking for this after someone mentioned it in a comment on my YouTube video about that combo card... Wouldn't it be possible to tokenize the patch into FCode (with some modification)? I'd assume that would decrease the size of it at least somewhat, and it can be executed from NVRAMRC... Or maybe it could be possible to add some sort of extra EEPROM containing said FCode, if space is still an issue after tokenizing?
Another idea I had was just to get rid of the PCI-PCI bridge altogether... Technically it shouldn't be necessary, as you can in theory just put all 3 devices (in this case SATA, FireWire and USB controller) all on the same PCI bus. That is if you don't end up reaching some sort of PCI device limitation on these machines.
... Wouldn't it be possible to tokenize the patch into FCode (with some modification)? I'd assume that would decrease the size of it at least somewhat, and it can be executed from NVRAMRC
Ah sorry, I misremembered - thanks for clarifying. Much appreciated.This would probably do it, if you can embed chunks of FCode in nvramrc. I didn't—and still don't—know how to do this, so I didn't. That would be the best way to expand it, though, definitely.
Ah, I've dealt with loading FCode from NVRAMRC before, and have a usable script that will do so. I'm currently working on converting your "NewTango2.0" Forth script to FCode, so we'll see how small it can be made once tokenized.This would probably do it, if you can embed chunks of FCode in nvramrc. I didn't—and still don't—know how to do this, so I didn't. That would be the best way to expand it, though, definitely.
Ah, I've dealt with loading FCode from NVRAMRC before, and have a usable script that will do so. I'm currently working on converting your "NewTango2.0" Forth script to FCode, so we'll see how small it can be made once tokenized.
I tried this originally with the Sonnet OEM patch and it behaved just like its cousin Tango 2.0 (the one with unpopulated ATA connectors.) USB and Firewire both worked, but ATA didn't.Managed to track down a Sonnet Tempo Trio (based on the early Tango 2.0). ATA-133, FW & USB in the TAM sounds like the dream. I'll give it a whirl and report back.
This seemingly won't be of any use to us, unfortunately, as it is larger than the original script (LOL).
Would this be of interest (especially for TAM users)?
Other possibility is use dead space in the rom or a bigger rom and jump to it / load it somewhere.
But all of these things are more difficult than getting one of these cards working in a small number of machines feels like it is worth.
Also forth is horrible.
2000 buffer: tb 0 tb 2000 8F6 & $X
Right. The reason you need to use a floppy is because Old World Macs can't read files from hard drives but can read files from a FAT (maybe HFS?) formatted floppy. I haven't tested FAT or HFS formatted partition - well, I guess every HFS+ partition with a HFS wrapper is HFS butIt would work if we put a longer script on a floppy disk...
But I'm not going to run my computer with a openfirmware boot script floppy disk forever
mac-files
is broken or doesn't work for HDs? I haven't looked into it." pci1/@F/@2/sd@0" 2dup find-device open-dev u.
2000 alloc-mem value buf
buf 2468 10 read-blocks 1 = if
buf 2000 evaluate
then
unselect-dev
It doesn't read HFS either sadly.Right. The reason you need to use a floppy is because Old World Macs can't read files from hard drives but can read files from a FAT (maybe HFS?) formatted floppy. I haven't tested FAT or HFS formatted partition - well, I guess every HFS+ partition with a HFS wrapper is HFS butmac-files
is broken or doesn't work for HDs? I haven't looked into it.