View Single Post
Old 16 November 2005, 03:05   #7
Posts: n/a

Just in case you're still watching this thread. I got AmiTCP 3.0b2 working just fine, however, it hogs the cli window it starts in, (which is the one opened for startup-sequence) despite being 'run amitcp:amitcp' and whatnot. It's definitely the AmiTCP process itself that's doing it cause once I 'rx "address AMITCP; KILL;" the window closes by itself.

Searches don't give me conclisive information on what to do with this, (except one odd advice to run it from WBStartup with IconX, which I'd rather not use, since I'd rather not loadwb at all later on, this thing is meant for unattended startup anyway) neither do the docs.

Any clues?
Page generated in 0.03851 seconds with 10 queries