EtherY driver + oflas

(please forgive the forum alias rather than real name as requested; I think more people RISC OS-associated know me by this name than by my real name, so it seemed probably more actually identifying…)

I’m running RISC OS 3.7 on an SA RiscPC, fresh install of !Boot from the ROOL hard disc image + !System updates + NIC driver softloads on a completely blank disc. The machine has a Castle 10/100 card in it that uses the EtherY module. The version in ROM is 0.43. I set up the card in Configure, enabled TCP/IP, assigned IP address, usual goodness. Softloaded EtherY module seems to load OK. On reset, no interface was apparently created at least as far as the IP stack is concerned (an error about ‘no such interface’ at boot and ifconfig shows nothing), and the card-specific output from EYInfo is full of oflas.

Any suggestions for next troubleshooting steps? Am I doing anything obviously stupid?

The machine has a Castle 10/100 card in it that uses the EtherY module.

Don’t those have a flashable component that contains (or can contain) a copy of the SharedC?
If so that may not match the other stuff you’re bringing in during the disc boot.

Don’t those have a flashable component that contains (or can contain) a copy of the SharedC?
If so that may not match the other stuff you’re bringing in during the disc boot.

I think so, yes, but this still happens I’ve unplugged all the ROM modules coming from the card (which is just EtherY and apparently something called Notes, which I don’t know what it does…).

I’m slightly loathe to flash the new drivers to the card if I can’t get them softloading, because I don’t have any way to flash the card back.

I think so, yes, but this still happens I’ve unplugged all the ROM modules coming from the card (which is just EtherY and apparently something called Notes, which I don’t know what it does…).

I was thinking more of taking any modern components out of the equation. Considering you might sharedC from both the NIC and the disc boot.

I believe the correct rebuild of the disc side for use on pre-RO5 machines is to use the ROL derived Universal boot and then apply !System (if required) rather than taking the current HD4 (which is complete in itself and does not require !System on top).

So, try the HD4 without the !System if you want, but I’d suggest the RO3.7/4.02 Uni. boot initially.

Unfortunately, it does it also with ROOL NIC drivers + the original 3.7 boot on the old hard disc. Exactly the same symptoms. It works with the on-card drivers, but those seem to have … quirks, which is why I was hoping to try out some different ones :-).

original 3.7 boot on the old hard disc

+ !System possibly.