motorollin wrote:
I saw your thread about adding the ata3.driver to a ROM image and burning it an an EPROM. The code is not 'ROM-able' so it won't execute even if you insert it in to a ROM image. The same applies for the Kickflash I'm afraid.
The problem with the 4xEIDE.driver and ata3.driver is that they're normal executable files which create the driver in memory. They don't have a valid resident structure until they're created, so they aren't seen when exec scans the ROM for residents
It's not impossible though.. I've almost got my 4xEIDE working on my A1200 from a ROM, it just needs a little fettling and tweaking. It's showing up in Scout's resident list, but still needs a damn reboot to work properly!
