Yes, that will cause complains by less experienced users for sure. Maybe installation script should ask basic network settings and apply it to configuration file in devs:. Doesn't need much, just little playing with scripts. And then you could reconfigure it by running installation script again. Pretty old fashioned, but would be better than nothing if you're not up to write full prefs program.
Picking the right configuration is hard. If you assume that DHCP ought to work, it would make the basic setup easier. But, trouble is, if DHCP does not work, then the boot process will stall until the failed negotiation times out. I don't have a good solution for this yet (yes, the OS4 version of Roadshow has exactly the same problem).
Specific configuration options which suit your local network are more often than not tough to get exactly right. I remember that when I used AmiTCP for the first time, back in 1994, I didn't understand exactly how IP-Adress, subnet mask and default gateway would play together. If I remember correctly, DNS servers were configured separately. Any small mistake would render the whole configuration useless, and not being an expert greatly increased the likelihood of making that small mistake
And btw. could you add preconfigured interface file for 3com driver too? And Hydra & X-surf too...
I'd be happy to. The current set of files represents only the hardware which I had access to and could test by myself. If you could point me to working configurations (e.g. what goes into the "device=" line of the respective Storage/NetInterfaces config file), I'll update the demo version and the release version archives.
