Amiga.org
Amiga computer related discussion => General chat about Amiga topics => Topic started by: haywirepc on July 21, 2010, 09:57:31 PM
-
I'm pretty sure this working fine on my last linux install...
I installed euae then copied my amiga forever directories to the linux computer. System boots all is fine but Aweb just hangs when looking for google or any other website.
I can't see anything in the euae config about networking. Anyone have any idea how I can fix this? Can't do much with my virtual amiga unless I can get on aminet...
Steven
-
In your ~/.uaerc file, add the following line if not present:
bsdsocket_emu=true
-
I'm not sure what file you mean, where should this file be located?
I take it thats a text config file for euae?
EDIT... I found the config file, the line was already there.
Still just hangs on looking for google, or it crashes to the guru black and red screen of death...
Steven
-
Reboot!
-
I'm not sure what file you mean, where should this file be located?
I take it thats a text config file for euae?
EDIT... I found the config file, the line was already there.
Still just hangs on looking for google, or it crashes to the guru black and red screen of death...
Steven
~/ is the short cut to /home//
Anyway, when e-uae starts, it reads the contents of this file (if it exists). E-UAE's GUI only supports fairly basic configuration settings, the rest are only configurable in the file.
Assuming the setting was already enabled, then the problem exists elsewhere. Could be in your emulated system, even.
-
Its pretty much a straight new amiga forever system and work directory, unless I borked something on my windows box playing with it...
I'm going to try installing amikit on this linux box. Amikit is very nice and most often works great but I really prefer the original 3.x kind of wb though.
Steven
-
You can actually run WinUAE under WINE if you like, but I found that the interface can be flaky. Depending on your version of the latter, your mileage may vary - hopefully better. On my system, for instance, if you use F12 to bring up the WinUAE interface, it can refuse to close again as if the keypress event wasn't consumed. Opening it from the windows systray (under gnome, it puts this icon in your notification area) works fine though.