»

[Duce]

Aye, AmiTCP is pretty simple with all the guides out there, but maybe a little over this fellows head atm, which is why I recommended Miami.

[Sutty100]

Ok so I followed the guide and now I can't boot to workbench unless I comment out the AmiTCP stuff in the user startup.

I get an error openDevice: Device or unit failed to open

Any advice on that one!?

To use Miami will I need to remove AmiTCP? I believe classic workbench has the installer for miami already on it?

[Snoozy]

Easynet drove me up the wall!! yes i think you should remove amitcp and have a fresh start with miami

Here is a link to setting up Miami dx:

http://www.amibay.com/showthread.php?t=24984

(especially useful at the end with the pics)

[Sutty100]

No luck with Miami either! Could it be to do with my Indivison ACA Mk2 accelerator card? I inserted the line Run <>NUL: C:WirelessManager prism2.device

and then after this Miami has inserted assign Miami.


In my wireless Manager file I have
network={
key_mgmt=NONE
}

Which should search for an network which does not have security.

After the Amiga boots I run the Miami wizzard but it does not Detect the settings of the network and the wireless card just keeps blinking. It does not start blinking until Miami starts trying to detect settings.

Thinking of sending it back at the moment spent forever trying to get it working!

[amiman99]

Here are some files from my configuration.

Some lines like IP, name and key, you need to change.

Maybe if you send me your files, we can look them over.

[Sutty100]

Hi,

Thanks for your help I have attached my files. I don't have a netDB-myhosts where did you place that file? Is it other computers on your network?

I have commented out the AmiTCP statements now but when I did have them uncommented they were in the format they are now.

[amiman99]

In the interfaces file change the prism line to this:
prism dev=devs/networks/prism2.device

(I did it this way: prism dev=devs:networks/prism2.device and it did not work, I'm not sure why)
==============================
In the wireless.prefs do this:
network={
key_mgmt=NONE
}
==============================
In startnet (in my startnet example ignore the wep key stuff it was copy paste stuff mistake):
remove: AmiTCP:bin/login -f amiga_user

works fine w/o it in my setup.
==============================
Create the file netdb-myhost, its should be in the amitcp/db folder, you can open the example file and add your settings. (Nameserver is your DNS server):

; This host
HOST 192.168.1.12 amiga.something.com amiga
; Domain names

; Name servers
NAMESERVER 156.154.70.1
NAMESERVER 156.154.71.1

==============================
In the user-startup:
Remove AmiTCP:bin/startnet
==============================
when your amiga starts, make sure that the wireless card is plugged in. during the statup watch the power led turn on, this is when this command starts in user-startup: Run <>NIL: C:WirelessManager prism2.device
The active light should blink once in awhile.
I like to start the Amitcp by hand not automaticly, and it's good to start it manually for troubleshooting. You can do that from CLI, just type startnet before using internet.
Before you do startnet try to do this in CLI: ifconfig prism0 192.168.0.11 netmask 255.255.255.0
If there is no error then the rest should work.

[ncafferkey]

Originally Posted by Duce

";-)" is not a valid SSID, though manufacturers vary on it a bit.

Google acceptable SSID characters/limits and come up with something different, see if that works.

An excerpt from RFC:

Also: The following six characters are not allowed: ?, ", $, [, \, ],
and +. In addition, the following three characters cannot be the first
character: !, #, and ;.

Which RFC? The 802.11 standard says that an SSID can include any byte values, including unprintable ones. Any limitations on accepted characters are due to bugs. Having said that, such bugs definitely exist in various routers etc., so it's wise not to stress them by using odd characters.

[danbeaver]

I'm afraid that EastNet simplifies setting up AmiTCP v 3.0b; it does not help with the hardware all that much, in fact it took me 2 months to get online and only works on OS 3.x (they leave this out). After more than several emails I sent went unanswered by Amigakit's support staff (over a 2 moth period) I finally got some help. The next issue for me was connecting my 2 network printers so I could print; they never answered this one. I finally got all of MiamiDX downloaded and setup so 2.5 months after I started I could surf and print via my home network.

Here are a few hints: there is a downloadable key file for MiamiDX, if you have USB support, then a USB Ethernet dongle sets up easier than any other (for wireless, get a ZuniDigital wireless bridge -- Newegg on sale for not that much, I just bought another for 25 salad leaves US). Read through Amibay's help site for setups. If there is an area that doesn't work for you there are alot of folks out there to help.

[Sutty100]

Originally Posted by amiman99

In the interfaces file change the prism line to this:
prism dev=devs/networks/prism2.device

(I did it this way: prism dev=devs:networks/prism2.device and it did not work, I'm not sure why)
==============================
In the wireless.prefs do this:
network={
key_mgmt=NONE
}
==============================
In startnet (in my startnet example ignore the wep key stuff it was copy paste stuff mistake):
remove: AmiTCP:bin/login -f amiga_user

works fine w/o it in my setup.
==============================
Create the file netdb-myhost, its should be in the amitcp/db folder, you can open the example file and add your settings. (Nameserver is your DNS server):

; This host
HOST 192.168.1.12 amiga.something.com amiga
; Domain names

; Name servers
NAMESERVER 156.154.70.1
NAMESERVER 156.154.71.1

==============================
In the user-startup:
Remove AmiTCP:bin/startnet
==============================
when your amiga starts, make sure that the wireless card is plugged in. during the statup watch the power led turn on, this is when this command starts in user-startup: Run <>NIL: C:WirelessManager prism2.device
The active light should blink once in awhile.
I like to start the Amitcp by hand not automaticly, and it's good to start it manually for troubleshooting. You can do that from CLI, just type startnet before using internet.
Before you do startnet try to do this in CLI: ifconfig prism0 192.168.0.11 netmask 255.255.255.0
If there is no error then the rest should work.

Ok so I have changed those files so they are the same as yours except things like IP address. So now I can boot into workbench. But if I try startnet I get an error that this file is not executable.

And if I try the ifconfig I get AmiTCP/IP version 3 or later should be started first!

Also the LED on the wireless card remains solid!

Still at least workbench now starts!

Cheers for all your help so far though! :-)

[Sutty100]

Originally Posted by Sutty100

Ok so I have changed those files so they are the same as yours except things like IP address. So now I can boot into workbench. But if I try startnet I get an error that this file is not executable.

And if I try the ifconfig I get AmiTCP/IP version 3 or later should be started first!

Also the LED on the wireless card remains solid!

Still at least workbench now starts!

Cheers for all your help so far though! :-)

Didn't realise I had to vavigate to the directory startnet was in and type Execute Startnet.

The output I get is as follows: ifconfig loctl (SIOCGIFFLAGS): no such interface
add host amiga.something.com: gateway locachost
add net default gateway 192.168.0.1 network is unreachable

I also get an AmiTCPIIP log that the device or unit failed to open

Is it a problem that I have AmiTCP installed on a different partition to where the prism2 driver is?

[danbeaver]

Most commonly AmiTCP does not store the location of you driver in its db/interfaces and, if using EasyNet, in the EasyNet.cfg file. Make sure they point directly to your NIC device (xxx.device) driver. It does care about much else if the dhcp is set properly. MiamiDX will set your IP address, mask and router IP address automatically; EasyNet doesn't do dhcp as easily.

[Sutty100]

Originally Posted by Sutty100

Didn't realise I had to vavigate to the directory startnet was in and type Execute Startnet.

The output I get is as follows: ifconfig loctl (SIOCGIFFLAGS): no such interface
add host amiga.something.com: gateway locachost
add net default gateway 192.168.0.1 network is unreachable

I also get an AmiTCPIIP log that the device or unit failed to open

Is it a problem that I have AmiTCP installed on a different partition to where the prism2 driver is?

Another update! The LED does now blink once at startup. When I go to execute startnet I no longer get the can't open device (I changed the interfaces file to look into the Workbench: partition. But the host is still unreachable and ifconfig loctl (SIOCGIFFLAGS): no such interface.

I feel I am getting closer! Maybe...

[amiman99]

You get this error: ifconfig loctl (SIOCGIFFLAGS): no such interface , because this command does not work: prism dev=devs/networks/prism2.device
I had exactly same problem. Maybe change the prism line to: prism dev=devs:networks/prism2.device
Check if the prism2.device is in Devs/Networks folder and play with the path.

Edit: When you get error when executing startnet, try this command: ifconfig prism0 192.168.0.11 netmask 255.255.255.0
When this one is not working: prism dev=devs:networks/prism2.device , this one will fail: ifconfig prism0 192.168.0.11 netmask 255.255.255.0

[Sutty100]

Originally Posted by amiman99

You get this error: ifconfig loctl (SIOCGIFFLAGS): no such interface , because this command does not work: prism dev=devs/networks/prism2.device
I had exactly same problem. Maybe change the prism line to: prism dev=devs:networks/prism2.device
Check if the prism2.device is in Devs/Networks folder and play with the path.

Edit: When you get error when executing startnet, try this command: ifconfig prism0 192.168.0.11 netmask 255.255.255.0
When this one is not working: prism dev=devs:networks/prism2.device , this one will fail: ifconfig prism0 192.168.0.11 netmask 255.255.255.0

I have tried all sorts of paths but it just wont find it I don't understand what the path could be! I have it located on a different partition to Amitcp Workbench:devs/networks/prism2.device Also the network card no longer flashes on startup!

Going backwards again now! Ah dear!