Amiga.org
The "Not Quite Amiga but still computer related category" => Amiga Emulation => Topic started by: Brunty on January 04, 2007, 11:52:51 AM
-
I'm sure this must be possible!
Last night I had a proper play with the new WinUAE and really liked it - strange I thought as I've never been fond of emulation!
I have OS3.9 installed and working well with Picasso96, so decent full screen and lots of colours. What I really need now is an internet connection.
Is there a how-to somewhere? Or just a device that I can use with Genesis?
Cheers,
Brunty
-
On the misc screen, tick the bsd.socket emulation.
My question is, what about some software that needs inetd: or other tcp stack assigns ?
-
bsdsocket.library emulation option in WinUAE/Misc settings works fine. I do not have any tcp/ip stack installed on Amiga side.
My question is, what about some software that needs inetd: or other tcp stack assigns ?
I am using AmiTCP: assign pointing to IBrowse directory even though there's no AmiTCP installed at all and I've never experienced any problem.
-
@mgerics
My question is, what about some software that needs inetd: or other tcp stack assigns ?
What is the inetd: assign anyway? Never heard about that one before.
Anyway, the only apps using AmiTCP: are the ones that want to access the files within it. The only ones I can think of are actually the apps that are provided with AmiTCP.
-
Fantastic, thanks!
That option was greyed out before when I considered it. But I guess I was running UAE at the time...
Cheers,
Brunty
-
Related issue: thought I'd ty out the getvideo program from Aminet.
I have all the required proggies, but when I run it in WINUAE, it keeps asking for the TCP: assign. Any ideas ? Thomas ?
-
You need AmiTCP:l/inet-handler and AmiTCP:devs/inet-mountlist. You can find them from AmiTCP-bin-30b2.lha (http://www.funet.fi/pub/amiga/gnu/tcpip/AmiTCP-bin-30b2.lha) for example.
If you take them as-is, you need to put them somewhere and point AmiTCP: assign to this dir.
Or you can copy AmiTCP:l/inet-handler to L: and edit AmiTCP:devs/inet-mountlist accordingly and put it to DEVS:
Anyway, once done, put this to s:user-startup
mount TCP: from AmiTCP:devs/inet-mountlist
If you edited the mountlist and put the files to L: and DEVS: then add:
mount TCP: from DEVS:inet-mountlist
WARNING: inet-handler adds a slight security hole to the system. To open the system for remote access, malicious application would only need to do something like this: newshell TCP:6666
Attacker can then connect to the system remotely via telnet or netcat, and give arbitrary shell commands.