Genesis Wizard Problem!

[Daniele]

I have installed the Internet software from OS 3.9 CD,
and I got in Devs:/Network the FastEthernet.device.

Now happens that when I go on Genesis Wizard then when I chose FastEthernet.device from the file requester and I go on it appears " unable to open device Devs/Networks/FastEthernet.device unit 0 "

What can I do to fix this ?

Many Thanks

[Dantron]

I am still having the same problem.  I am not using Genesis any more, I am now trying easynet, and their ethernet board, but it doesn't seem to matter what software I am using I can never seem to open the fastethernet.device
The latest advice I have been told is to install the medconfig program from elbox and see what it kicks out for clues.  I have to download the program from somewhere else and burn it to a cd to take to my amiga... so it's a little of a pain but that is my next step.
I will be reading your post answers in the hope I can glean the answer for myself too.
Good luck!
Dan

[pVC]

Try to config Genesis without Wizard? I haven't had any problems with fastethernet.device with it like that (Wizards are useless, so I haven't even bothered to try with it .

It might be that fastethernet.device doesn't fully cover all functions it should and that's why it fails on some queries or something It fails with executive's dashboard here too.. but when used directly from tcp/ip stack, it works just fine.

If that doesn't work.. are you sure that you have some mem from Voodoo reserved for network card? 10/100Mbps (fastethernet.device) cards need it, 10Mbps (mediatornet.device) won't. Check VoodooMem env-setting.

[Daniele]

the problem is not only  " unable to open device

Devs/Networks/FastEthernet.device unit 0 "

but when I try and run an internet application (or a

command fromAmiTCP), I get the error message "Cannot open

bsdsocket.library". How do Ifix this ?

[pVC]

You must have TCP/IP stack on-line before using any internet applications. bsdsocket.library is created on memory by tcp/ip stack then. So... you must figure out the problem with fastethernet.device before trying anything else.