A1260 PCMCIA Wifi worth it?

[patrik]

Originally Posted by Photon

Q: Where does plipbox.config go on the finished installed HDD, and how do I perform the plipbox0 step on the nonexistant nbddriver?

The nbddriver seems to be an ENV variable on the "Network Boot Disk for Amiga" disk cnvogelg is referring to. Is this what you are using?

I also have a similar experience with the NOBURST setting being a requirement for the PlipBox to work in most cases. To set it, you can do this in a shell:

8.Ram Disk:> makedir ENVARC:Sana2 
8.Ram Disk:> echo NOBURST >ENVARC:Sana2/plipbox.config

And then reboot and the startup-sequence executed at boot will automatically make sure it is copied from ENVARC: (ENV Archive) to ENV:.

Another option is to edit the file with a text editor of course.

[Sir_Lucas]

Originally Posted by Photon

GitHub instructions say that file is optional, grr. The 2 steps about plipbox0 and Sana2 I couldn't perform because there were no such files or folders. Where should the file go on WB3.1 hdd?

All I ended up doing was add the interface (I had to add UNIT=0 at the end as for the others) and then I could select it in Advanced settings in the Network program.

I'm going to try with the one from the original dev's blog and add NOBURST. And maybe add the right device to the tooltype as well.

Do you have your config file somewhere so I know what's supposed to be in it? The only one I've seen just had 1 line of text in it.

It's sketchy editing files like this. Is there some other floppy image with installer somewhere?

I didn't run the floppy image linked from Github because it will try to change settings for my existing AmiTCP4 and overwrite it with AmiTCP3. I could try it with some copy of existing WinUAE hdd directory to see what it does.

But OK, NOBURST is a lead.

Q: Where does plipbox.config go on the finished installed HDD, and how do I perform the plipbox0 step on the nonexistant nbddriver?

Which TCP/IP are you using? Is it AmiTCP? Have you tried Miami, MiamiDX or Roadshow as well?

[Photon]

I use AmiTCP. 3.0b is on the floppy and 4 is on the HDD. We can remove the HDD from discussion until I can ping the gateway.

I added plipbox.device to df0:devs/networks and initialized the disk according to the Github instructions.

Running from the floppy:

ifconfig plipbox0 returns UP and RUNNING.

ping <self i.e. amiga ip> works fine.

ping 192.168.1.1 (gateway) or a PC on the network doesn't work from the floppy.

netmask is standard 255.255.255.0.

So I'm stuck here and can do no more until this works.

[Photon]

OK, started from scratch and followed the guide exactly. The only thing I did differently was to use the 020 compiled plipbox.device.

Here is the disk image after the final reboot, if anyone can spot an error. If so, this error occurs from following the GitHub readme with the two downloads (networkbootdisk.adf and plipbox-0.6.zip).

(One thing worth noting is that if you follow the readme exactly, you will never select an interface (e.g. PlipBox, X-Surf, etc from the popup menu in the s-s on the floppy). So IDK why that popup is there. Nor are there instructions for what to do when the floppy is working and connecting, to make your CF card WB install able to connect.)

The result is the same. I can ping myself, but not the Gateway or a PC on the network. I can also ping the "broadcast" address, 192.168.1.255. I don't know if that means anything.

MiamiDX seems to have a proper program for configuring Ethernet. I have never used it, so I'm asking for tips like official website, which version to get, 68000 support etc.

[btp]

Concerning plipbox I made mine working with my A500 following the instructions provided in this video
[ Show youtube player ]

[Sir_Lucas]

Originally Posted by Photon

OK, started from scratch and followed the guide exactly. The only thing I did differently was to use the 020 compiled plipbox.device.

Here is the disk image after the final reboot, if anyone can spot an error. If so, this error occurs from following the GitHub readme with the two downloads (networkbootdisk.adf and plipbox-0.6.zip).

(One thing worth noting is that if you follow the readme exactly, you will never select an interface (e.g. PlipBox, X-Surf, etc from the popup menu in the s-s on the floppy). So IDK why that popup is there. Nor are there instructions for what to do when the floppy is working and connecting, to make your CF card WB install able to connect.)

The result is the same. I can ping myself, but not the Gateway or a PC on the network. I can also ping the "broadcast" address, 192.168.1.255. I don't know if that means anything.

MiamiDX seems to have a proper program for configuring Ethernet. I have never used it, so I'm asking for tips like official website, which version to get, 68000 support etc.

Here is a great website that explains everything regarding Miami, MiamiDX installation and configuration. Instead of cnet.device or prism2.device just use plipbox.device - experiment with different versions.
https://www.retro-commodore.eu/netwo...-on-the-amiga/

And a video for MiamiDX - just use plipbox.device instead of 3c589.device
[ Show youtube player ]

[Photon]

OK, now I've learned everything driver and hardware and networking software developers have to learn, and which software have bugs and which error messages mean what, so now I have working Ethernet on my Amiga.

It shouldn't be this way. It should be like AmiTCP. It was by far the easiest. Library and device, fill in a form, get a Network icon.

Plipbox is now inspected, looks fine but just - won't - work so marked broken. Probably not what I want to use either for speed reasons.

Next stack was MiamiDX which looks easy, can detect nothing but lets you fill in stuff and lets you run MiamiDX to start a default interface (but the big window stays open). It has MiamiSSL (if it works) which is the only way AWeb can surf to HTTPS. It also has a bunch of commands, several of which complain of missing library versions that are not installed with the package, e.g. MiamiPing(!)

Chanced it on a Corega Ethernet card and was lucky (reported to 'the list' as verified). This and a borrowed Wifi card (WEP only, create WLAN in router) I tried with MiamiDX.

For these cards you will need CardReset and/or CardPatch.

Then I installed Roadshow and got faster speeds (2.25MB/s with AmigaExplorer, 4096B packet size). It has no network icon at all, you must make a script, make an icon and use tooltype C:IconX and give the full commandline. Default install causes a wait in s-s. It also has no place to enter the normal values IP etc, these are split into 3 files that you have to read walls of text to find the path to. Also no way to turn off or restart that I know.

So, now that I have all drivers and all stacks and all software installed I finally have a good solution.

I recommend:

1. X-Surf with driver or (Amiga verified) wired PCMCIA card with CNet.Device + CardReset/CardPatch.
2. Use AmiTCP4 install disk with bsdsocket.library, add device to interfaces. Put Network icon on the workbench.
3. AmigaExplorer and/or AWeb pointed to an online FTP.

That way you don't have to learn fine details and try stuff and look for stuff and waste hours and hours.

[Swe_Kryten2x4b]

Originally Posted by Photon

Next stack was MiamiDX which looks easy, can detect nothing but lets you fill in stuff and lets you run MiamiDX to start a default interface (but the big window stays open). It has MiamiSSL (if it works) which is the only way AWeb can surf to HTTPS. It also has a bunch of commands, several of which complain of missing library versions that are not installed with the package, e.g. MiamiPing(!)

You can configure Miami to not show the interface on startup. Not sure which library version it is complaing about on your setup, never had that problem.

As long as it's running the cli commands should be able to run. Everything needed should be AmigaOS (duh!), and MUI.

[indigolemon]

Originally Posted by Photon

Then I installed Roadshow and got faster speeds (2.25MB/s with AmigaExplorer, 4096B packet size). It has no network icon at all, you must make a script, make an icon and use tooltype C:IconX and give the full commandline. Default install causes a wait in s-s. It also has no place to enter the normal values IP etc, these are split into 3 files that you have to read walls of text to find the path to. Also no way to turn off or restart that I know.

I created this: https://aminet.net/package/comm/net/Roadie

Maybe it helps you live more easily with Roadshow? It is still the fastest stack, and the only one still actively maintained afaik.

[Photon]

Originally Posted by Swe_Kryten2x4b

You can configure Miami to not show the interface on startup. Not sure which library version it is complaing about on your setup, never had that problem.

As long as it's running the cli commands should be able to run. Everything needed should be AmigaOS (duh!), and MUI.

Seems you're right. Maybe it was during getting MiamiDX to work that I tested MiamiPing etc. The error message should read "MiamiDX is offline or not started", though, not "missing library version X". It's not so helpful when trying to figure out where in the mix of HW and SW the problem is.

Just tested AWeb with MiamiDX and it seems to work better with semi-legacy websites (that can have https links on them). Unless I can make RoadShow work with SSL, I would recommend MiamiDX if you do some surfing.

Originally Posted by indigolemon

I created this: https://aminet.net/package/comm/net/Roadie

Maybe it helps you live more easily with Roadshow? It is still the fastest stack, and the only one still actively maintained afaik.

Yeah, RoadShow seemed ~50% faster on A1260. I recognize some of the commands from the manual, maybe it does come with at least commands to turn off/restart. (Turning off is mostly for WHDLoad, which otherwise goes online and checks for newer versions of slaves, I wouldn't mind a check but on an optional button instead.)

Cheers for this, I might try it when I have some more time.

~

To answer the original question, yes wireless can be worth it, the extra fiddling consists of ensuring you have a router where you can set up an extra WLAN with an older protocol that your card speaks. It was not much extra work (for me it was the easy part). I noticed no slowdown on 060 using WEP, maybe on 030?

And I think don't worry about "only" 10Mbps cards or bad Wifi coverage, it will be fast enough for the Amiga end.

[Kin Hell]

Originally Posted by indigolemon

I created this: https://aminet.net/package/comm/net/Roadie

Maybe it helps you live more easily with Roadshow? It is still the fastest stack, and the only one still actively maintained afaik.

Always nice to meet the Author of such marvellous programs like Roadie!

Great program for a great Network Stack!

[ncafferkey]

Originally Posted by Photon

To answer the original question, yes wireless can be worth it, the extra fiddling consists of ensuring you have a router where you can set up an extra WLAN with an older protocol that your card speaks. It was not much extra work (for me it was the easy part). I noticed no slowdown on 060 using WEP, maybe on 030?

Using WEP should never cause a slowdown compared to unencrypted, as all supported cards have hardware accelerated WEP. Orinoco/Hermes-type cards also have hardware accelerated WPA/TKIP, so there shouldn't be a slowdown there either (well maybe just a little bit, because a small part of TKIP has to be done in software).

[Sir_Lucas]

Just tested AWeb with MiamiDX and it seems to work better with semi-legacy websites (that can have https links on them). Unless I can make RoadShow work with SSL, I would recommend MiamiDX if you do some surfing.

You should try IBrowse and AmiSSL. They both support the newest SSL. They are actively supported too.

https://www.ibrowse-dev.net/news.php?id=1703240103