serial file XFR to PC 3

[Walimay]

Hi,
I'm in a trouble.
I have to tranfer large tar.Z files froma a SCO server to a pc.
It could be done easily via FTP but unfortunately the server has only a Specialix multiserial connecterd to the clients and printers.

I use a trminal emulation program to connect, I have root access to the system.

While trying to transfer data using the "request files" option of the client teminal emulator the dest file is created but it remains at 0 Kb. I've tried also with small data files but nothing arrives.

Any suggestion?

Tnx. Walimay

 

[edfair]

I've used basic to capture stuff dumped from a serial port. But all of mine have been raw data.
Have also used a parallel/serial converter to take it from the parallel port into a serial port under basic.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[jfrantz]

You could uuencode the file and redirect the output to the appropriate serial port, capture it on the PC to a file, then uudecode the file on the PC.

-Jeff

 

[Annihilannic]

A serial file transfer protocol like Kermit or Zmodem perhaps? I can't remember whether these are available by default under SCO since I don't have a box to check...

Annihilannic.

 

[Walimay]

replying to jfrantz

the files I need are ascii export from an accounting sw. I used tar -cvf to collate em into a unique file and the I've compressed tars with compress.

Using TinyTerm as terminal emulator I can use the transfer funcion "request file(s)". I can choose the protocol Xmodem, Zmodem, Ymodem).

Using Xmodem the process seems to start correctly, a file on local pc is created but its size keeps to 0 bytes and after a while i get an "handshake timeout" error.

Have I to do something on the server?

I can post screenshots if needed.

tnx.

Waly

 

[Annihilannic]

Yes, you need to start sending the file from the server. For Zmodem the binary was sz (send Zmodem), so there might be an sx? Or I think you can also use kermit to send the file in a variety of protocols.

Annihilannic.

 

[Walimay]

i've looked for in / and /bin but neither sz, sx or kermit were found.
are there in a specific folder ?

Maybe it were not installed on this system?

How many troubles and time I need to put it in a TCP network?

(install NIC, and configure the system)

tnx. Waly

 

[motoslide]

Regarding installation of TCP:
What version of SCO? Try this:
# uname -X

If it's 5.0.X, then TCP should be fairly easy to implement. There's a version of 5.0.X (Host Edition) which didn't include TCP/IP, however.

Regarding serial transfer:
I think I've got the rz/sz binaries laying around here somewhere. Those would work for your Z-modem transfer. Kermit was included in Lone-Tar (backup software). If you happen to have that, look in the /usr/lone-tar directory.

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[Walimay]

I've looked for that files, neither sz, sx or lone-tar were in the system.

this is the result of uname -X :

System = SCO_SV
Node = xxxxxxx
Release = 3.2v5.0.6
KernelID = 2000-07-27
Machine = PentIII
BusType = ISA
Serial = 0000000
Users = 5-user
OEM# = 0
Origin# = 1
NumCPU = 1

hope will help.

tnx. Waly

 

[motoslide]

I couldn't find my RZ/SZ binaries, but a google search found this location. While you are there, check out their Anzio Lite terminal emulator. It's a great product, and (similar to TinyTERM) has some file transfer options.

http://www.anzio.com/pub/zmodem/

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[motoslide]

There is also a great "How To" on using Anzio and SZ/RZ:

http://www.anzio.com/support/kb/Anzio_kb/Using Zmodem in Anzio.htm

"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[Walimay]

it seems that i'm near the solution. Unfortunately the remote system is now unreachable. I'll try to connect tomorrow.

Steps I'll do:

Make a floppy with sz and rz executables.
copy 'em from floppy to /bin
launch sz to tranfer files from Host to PC
receive files to PC.

I think that's all .

pls correct if i'm wrong

tnx. Waly

 

[Annihilannic]

Sounds good to me.

Annihilannic.

 

[Walimay]

Ladies and Gentleman....

IT WORKS !!!

Tnx to all who contribute to this post, and special tnx to Motoslide and Annihilannic for the most useful help.

I run sz <filename> from host and then receive files on PC.
Unfortunately the tranfer is very very very slow, due to the serial connection at 38400 Kbs.

1% of the first file in 40 minutes !

well, i'll wait the end.

tnx. Waly

 

[Walimay]

Here again:

te client sw report a baud rate of 1400 / 38400 Kbs

is there any option to improve speed ?

I've tried with -bkrv

b = forces binary
K = sends 1024 bytes packet
r = resume interrupted files
v = verbose

so this ws the command: sz -bkrv myfile

tnx Waly

 

[motoslide]

I think Specialix had a couple of "fastbaud" options, where you specified one speed, and the driver automatically kicked it up to 57,600 or 115,200. When you stated "1400/38400", did you mean that your true throughput was 1400, even though the BAUD rate was set to 38400? Part of this could be on the PC end. The old COM1/COM2 ports were never meant to receive large hunks of data at high speed. They (physically) had to be serviced directly by the CPU via IRQ lines.
Cabling and flow-control could also play a part. Serial Transfer was never pleasant.



"Proof that there is intelligent life in Oregon. Well, Life anyway.

 

[Walimay]

Yes, the client tells me that i'm transferring at 1400 baud instead of a full capacity of 38400.

it seems that the serial connection is not so good, because of the latency of the response on screen. Added to the general performance of the "server"...

thanks anyway four your support...

Waly

 

[edfair]

What kind of handshaking? You might try xon/xoff if it isn't the current type.
You should be able to run it as a 3 wire cable.
And double check the setup on the PC end. If I recall there are 2 places that have to be set for high speed comms. The defaults are 9600.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[Walimay]

Well guys,
all works fine now. tnx ti Edfair that reminden me to double check the port config. (it was setted up at 9600 !!)

Now i'm transferring data at almost 38k, fine enough for my purpose.

tnx a lot to all who contribute to this post.

Now I can say: SOLVED !

Walimay