Hello again! > Another suggestion might be to 'boot with no startup sequence' to > a command prompt, then assign ENV: to RAM: and then type 'loadwb' > to avoid any startup stuff at all (except maybe WBStartup - can't > remember whether those get called by loadwb or not) > and then you will be in WB. at this point, do you still have a > 'light'? Then fire up MiamiDX and test again. The light went off at the moment I put the interface for my LAN online in miami, so after I started Miami. But I discovered the problem :) The problem was a config-file in ENV: When I deleted that file the problem was gone! I tested this to be sure by temporarily putting the file back and it seems to be 100% reproducable. It was a 7 byte large ascii config-file called ENV:Sana2/ariadne_ii_0.config. The contents of this file was a string "10BASET" When such a file is present, putting an interface online 'does something' to the connection (for lack of a better explanation :-). From my (limited) findings this something can only be undone by resetting my Amiga. FYI, I am using the ariadne_ii.device in my setup. Anyway, thanks Kevin for your help, I would not have discovered the problem this quickly (if I would have discovered it at all) without your emails! And now I can maybe help somebody who is having the same or a similar problem in the future... Thanks! // Niels de Koning ____________________________________________________________________ Co-editor on 3DAddict's GFXZone http://gfxzone.planet-d.net -- To unsubscribe send "unsubscribe miami-talk-ml" to "[EMAIL PROTECTED]". For help on list commands send "help" to "[EMAIL PROTECTED]".
