Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Michele31415 on November 03, 2021, 06:01:16 PM
-
I have my 2000 connected to my Sun with a serial cable. On the Amiga I can say "newcli aux:" and then on the Sun I can open a tip connection which gives me a shell. But it's just straight ASCII, so commands like "more" don't work right. I have TERM=VT100 set on the Sun end.
Is there some way to make the Amiga newcli on the aux: device emulate a VT100? Note that I'm not asking how to open a VT100 terminal window on the Amiga - there are several programs to do that.
-
Well, the Amiga doesn’t have a term database and doesn’t know much about vt100. The Amiga console is closer related to ANSI than to vt100, so it may help a little to use TERM=ansi. However, much of the software just assumes amiga console is used and will never work well over AUX:
-
No, setting TERM=ansi didn't help. "more" is still seriously confused. Ah well, at least it's good to know I can just forget about this one. Thanks!
-
If your Amiga had tcp stack, there is a better option…
https://github.com/alpine9000/squirt
It might be possible to alter it to work directly with serial perhaps, but at least I can say that it works great with PPP over serial :)
-
Hey that looks like the ticket! I'll give it a try tomorrow. Thanks :D
Oh, wait - I get that I can open a terminal window and talk to the Amigha but am I supposed to compile this project on my Sun or on the Amiga? They talk about running squirtd but there's only a C file named that there. And then where do the commands like squirt_cli come from?
-
Go to the Releases page, there you can download binaries.
https://github.com/alpine9000/squirt/releases
-
Oh duh, of course. I got the Amiga binaries and fortunately there are sources there too. I'm trying to build it for Solaris 11.4 SPARC now.
UPDATE:
OK, so it's now compiled for Solaris 11.4. I downloaded the Amiga binaries to the Amiga but I can't get it to run, either by following their example, or the simplest case:
3.FS3:Internet/Genesis> cd db
3.FS3:Internet/Genesis/db> run aux:squirtd work:incoming/
[CLI 4]
aux:squirtd: packet request type unknown
3.FS3:Internet/Genesis/db> aux:squirtd failed returncode 10
3.FS3:Internet/Genesis/db> cd ///
3.FS3:> cd squirt-amiga-v0.2
3.FS3:squirt-amiga-v0.2> dir
skill sps
squirtd ssum
3.FS3:squirt-amiga-v0.2> run aux:squirtd work:incoming/
[CLI 4]
aux:squirtd: packet request type unknown
3.FS3:squirt-amiga-v0.2> aux:squirtd failed returncode 10
3.FS3:squirt-amiga-v0.2> run squirtd
[CLI 4]
3.FS3:squirt-amiga-v0.2> status
Process 1: Loaded as command: AmiTCP:kernel/AmiTCP.020
Process 2: Loaded as command: Workbench
Process 3: Loaded as command: status
Process 5: Loaded as command: AmiTCP:bin/inetd
3.FS3:squirt-amiga-v0.2>
So whether "run squirtd" even worked is open to question. In any case, nothing happens on the Sun side either:
michele@hemlock:~/squirt-0.3/build$ squirt_cli 192.168.0.8
squirt_cli: failed to connect to server 192.168.0.8
michele@hemlock:~/squirt-0.3/build$ ping 192.168.0.8
192.168.0.8 is alive
michele@hemlock:~/squirt-0.3/build$
Any ideas?
-
Huh, why are you trying to run squirtd out of aux:???
-
Huh, why are you trying to run squirtd out of aux:???
It's mentioned in the github...
https://github.com/alpine9000/squirt
But it looks very wrong. It's almost like they have a volume or assign called aux.
-
Wow, yes, very wrong.
-
Huh, why are you trying to run squirtd out of aux:???
Because that''s what the directions said to do I can run squirtd with no arguments and it returns a prompt with no errors. But it also doesn't show up in status (though maybe it wouldn't). It should also be noted that the directions fail to mention you need port 6969 open so I added that to Internet/Genesis/db/inet.access, But it didn't help. A port scan of the Amiga's IP does not show port 6969. When I run squirt_cli on the Sun there are no mentions of any access attempt in the Genesis log.
Of course, this is version 0.2. Maybe I should just wait for 1.0 to come out.
-
I use squirtd 0.2 on all my Amiga systems without any problems, so I don’t know what problem you have. I use Roadshow though. Maybe SnoopDOS may reveal something.
-
I use squirtd 0.2 on all my Amiga systems without any problems, so I don’t know what problem you have. I use Roadshow though. Maybe SnoopDOS may reveal something.
Thanks - it's good to know that at least it does work for someone. So I installed SnoopDOS and started it. It opened a window that says "Monitoring system activity" but nothing appears in it when I type either "squirtd" or "run squirtd" (though other system activity does show up there). Also the WB free memory counter doesn't decrement when I start it. It's like a big no-op.
Maybe there's something wrong with the squirtd file. It's 5028 bytes long. Is that right? Am I starting it correctly? Just "squirtd"? Strange stuff.
-
OK, I figured it out. I recompiled squirtd with debugging turned on. Then when I ran it, it went "dest_folder". So I looked at the documentation and suddenly realized that the command is supposed to be
squirtd dirname/
not simply
squirtd
The dirname arg is NOT optional, and the "/" is also required. Once I created a directory named "incoming" and started squirtd with a that name (any name will do) it worked fine. I can now open a TCP shell from my Sun to the Amiga. I no longer need the serial port for that. It's still not a VT-100 but it is nonetheless pretty cool.