Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: garyg on December 22, 2013, 05:52:59 PM
-
First, please forgive the newbie question but I haven't connected to the Internet with an Amiga for almost four years because my ISP doesn't support dial-up.
Now I have my A4000/Mediator (with an Ariadne II card) working and an ethernet cable long enough to reach my router. However, when I start up iBrowse I can't connect. Some sites say "you have to start a TCP stack first". For some reason iBrowse doesn't automatically start Miami.
The last time I connected to the Internet using an Amiga was with my A4000 desktop. What am I doing wrong/forgetting?
Thanks in advance,
Gary
-
You have to run Miami first. It will not start automatically.
You can move it to WBStartup or run it from user-startup to get it started after boot.
-
You have to run Miami first. It will not start automatically.
You can move it to WBStartup or run it from user-startup to get it started after boot.
Suspecting that, I clicked on Miami and it said something like "configuring modem" but after nothing happened for a while I hit Cancel, afraid that I'd mess up the router somehow
Next time I'll be more patient, and follow your advice about moving it to WbStartup.
Thanks!
-
You should first configure Miami and test the connection before you let it start automatically.
Delete or rename the miami.defaults file, then run MiamiInit and configure your ethernet connection. Better read the manual before start.
-
I haven't used it personally, but have heard very good things in this forum and others about the new TCP/IP stack "Roadshow". You might want to consider ditching Miami and trying that out. Or try them both - you never know which might work better for you. ;) Good luck!
-
Thanks, that worked! Although IBrowse 2.3 gets hung up on javascripts on several websites. I need to install 2.4 in hopes that it'll help
-
Glad you got it working! IBrowse 2.4 is slightly better with JavaScript. The main improvement over 2.3 is that the status bar will tell you that it's working on processing a script and offer you the option to abort after a set amount of time (instead of just hanging with a busy pointer). The JavaScript engine itself was a considerable improvement by 2006 standards, but in 2013 it's effectively useless. I don't do much browsing beyond Aminet on my Amigas these days.
-
Yeah, even the IBrowse site used javascript in such a way that 2.3 couldn't process it!