@AmiBiL0:
Have you moved the VGAOnly file to Devs/Monitors/? It might very well result in a better positioned screen. If it is a VGA-monitor, it should have no problem with 31kHz btw, as that is what they are specified for.
You can also run the Prefs/Overscan program to adjust the position of the screen a bit.
You don't need to be able to contact the network in any way for AmiTCP to be able to add the default gateway. If you had a normal ethernet-card, that would work fine even if the card didnt have a network-cable attached for example. It is as you say - the reason it fails there is that it has failed to configure the interface.
You don't need to add any info like SSID etc. via S:User-Startup for the prism2-device load successfully and configure the interface, so that is not the issue... as long as you didn't supply any wrong info that actually made prism2.device fail. Though, if pccard.library is missing or CardReset isnt run before, as I said in the previous post it _will_ fail.
Remember that in AmiTCP 3.0b2, you can't have any numbers in the interface-name (found in the file AmiTCP:db/interfaces) as when you call the interface from the startnet file (AmiTCP:bin/startnet), you supply a number at the end which says which unit-number of the device for that interface you want to use.
This means that if you say have wrongly named the interface "prism2" in AmiTCP:db/interfaces and tries to call it with ifconfig from AmiTCP:bin/startnet by "ifconfig prism20 xxx.xxx.xxx.xxx....", ifconfig will then search for the interface-name "prism", which it ofcourse will not find in your interfaces file, as it is named "prism2". Also, if it found the interface "prism", it would make it try to open unit 20 of the specified device, which would be way wrong.
Personally I would recommend you go with AmiTCP because of much lower memory-usage, about double the speed and no time-limit.
/Patrik
