Rairii
Rairii
try holding down Z for zipdisk as that's what that IDE device was intended to be used for
ok, so maybe it's some hardware issue with the ssd and the ide controller, i've known that to be an issue. for example my lombard has an ssd in it...
I really need to look into this. Until I figure this one out, known workarounds include: - booting manually from the open firmware prompt with `boot cd:,\\:tbxi` - plugging in...
Here's a test build, does this help? [nt_arcfw_grackle_fwonly_test20240717_2133.zip](https://github.com/user-attachments/files/16274485/nt_arcfw_grackle_fwonly_test20240717_2133.zip)
I had a sudden insight, this test build might fix the issue: [nt_arcfw_grackle_fwonly_test20240718_2222.zip](https://github.com/user-attachments/files/16289396/nt_arcfw_grackle_fwonly_test20240718_2222.zip)
hmm, so for some keyboards, the issue with sticky keys remains? is a valid workaround to press the last key that worked?
Is the cd drive showing up in the device list?
Does the same error show up every time you try to load the ramdisk? (by which I mean, try to load the ramdisk twice in a row without rebooting) What...
The invalid device name error would be consistent with the IDE/ATAPI driver failing to open the drive (so test unit ready/start unit/read capacity commands failing)... maybe I should look at...
OK, so when working on the uni-north port I found a slight issue with the ide driver, specifically the atapi side, on every access it sends test unit ready +...