[comp.unix.xenix.misc] Need help with two Xenix Problems

smm@milton.u.washington.edu (Stephen Milton) (12/03/90)

First problem:
  So far the only comm utility that I can get  to work on my Xenix/286 machine
is cu.  But how do you use sz or rz (zmodem) commands from within cu?  I've
tried many different methods, but none seem to work.  

Second Problem:
  I tried to get pcomm to work on my system and when it compiles it always 
ends up with a passle of unresolved externals that I haven't been able 
resolve.  i.e. why are they unresolved, and how do i fix them.

Many thanks to anyone who can give me any guidance on these, I'm sure, simple
questions.

Stephen M. Milton         University of Washington, Seattle

caf@omen.UUCP (Chuck Forsberg WA7KGX) (12/04/90)

In article <12181@milton.u.washington.edu> smm@milton.u.washington.edu (Stephen Milton) writes:
-First problem:
-  So far the only comm utility that I can get  to work on my Xenix/286 machine
-is cu.  But how do you use sz or rz (zmodem) commands from within cu?  I've
-tried many different methods, but none seem to work.  

Rz and sz are not written to be used from within cu.  Professional-YAM is
designed for dial-out applications.

jpr@jpradley.jpr.com (Jean-Pierre Radley) (12/04/90)

In article <12181@milton.u.washington.edu> smm@milton.u.washington.edu (Stephen Milton) writes:
>First problem:
>  So far the only comm utility that I can get  to work on my Xenix/286 machine
>is cu.  But how do you use sz or rz (zmodem) commands from within cu?  I've
>tried many different methods, but none seem to work.  

Cu can't do this. Xcmalt can. You can pick it up from slug/camco in Seattle.
If it compiles on 286, let me know, please.

>Second Problem:
>  I tried to get pcomm to work on my system and when it compiles it always 
>ends up with a passle of unresolved externals that I haven't been able 
>resolve.  i.e. why are they unresolved, and how do i fix them.

I never got it to work either.
-- 

 Jean-Pierre Radley	NYC Public Access	jpr@jpr.com	CIS: 72160,1341

paul@actrix.gen.nz (Paul Gillingwater) (12/04/90)

In article <19@omen.UUCP> caf@omen.UUCP (Chuck Forsberg WA7KGX) writes:
> -  So far the only comm utility that I can get  to work on my Xenix/286 machine
> -is cu.  But how do you use sz or rz (zmodem) commands from within cu?  I've
> -tried many different methods, but none seem to work.  
 
> Rz and sz are not written to be used from within cu.  Professional-YAM is
> designed for dial-out applications.

Yam is good, but the manual is very confusing.  I have used rz and
sz quite happily from within Kermit, which is widely available for
Xenix.
-- 
Paul Gillingwater, paul@actrix.gen.nz

jay@gdx.UUCP (Jay A. Snyder) (12/05/90)

Stephen Milton (smm@milton.u.washington.edu) writes:

->First problem:
->  So far the only comm utility that I can get  to work on my Xenix/286 machine
->is cu.  But how do you use sz or rz (zmodem) commands from within cu?  I've
->tried many different methods, but none seem to work.  

To use rz and sz from cu:  (ttyxx is the port you are dialed out on)
To upload a file:

type at host prompt:
rz
then type:
~$ sz foo.bar </dev/ttyxx

To download a file:

type at host prompt:
sz foo.bar
then type:
~$ rz </dev/ttyxx

->Second Problem:
->  I tried to get pcomm to work on my system and when it compiles it always 
->ends up with a passle of unresolved externals that I haven't been able 
->resolve.  i.e. why are they unresolved, and how do i fix them.

to compile pcomm on xenix (excerpts from Makefile):

#for SCO Xenix
CFLAGS = -Od -DM_TERMINFO -M3e -LARGE
LDFLAGS = -M3e
CURSES = -ltinfo -lx
TERMLIB = -ltinfo -lx
BSD =
TTY = tty_att.o

aris@tabbs.UUCP (Aris Stathakis) (12/07/90)

In <12181@milton.u.washington.edu> smm@milton.u.washington.edu (Stephen Milton) writes:

>First problem:
>  So far the only comm utility that I can get  to work on my Xenix/286 machine
>is cu.  But how do you use sz or rz (zmodem) commands from within cu?  I've
>tried many different methods, but none seem to work.  

Try ECU - a public domain comms program with X/Y/Zmodem (plust more).
It's available from the uunet archives.

It's really nice, and is specifically made for SCO XENIX/UNIX unlike
pcomm which is generic.

Aris

-- 
 Aris Stathakis | Bang: ..!uunet!ddsw1!olsa99!tabbs!aris or aris@tabbs.UUCP
        - First time, it's a KLUDGE - The second, a trick. -  
            - Later, it's a well-established technique! -
                               -- Mike Broido, Intermetrics

wht@n4hgf.Mt-Park.GA.US (Warren Tucker) (12/07/90)

In article <75@gdx.UUCP> jay@gdx.UUCP (Jay A. Snyder) writes:
>Stephen Milton (smm@milton.u.washington.edu) writes:
>
>->First problem:
>->  So far the only comm utility that I can get  to work on my Xenix/286 machine
>->is cu.

Tru ECU :-) available from comp.sources.misc archives
(new version Real Soon Now).

>type at host prompt:
>rz
>then type:
>~$ sz foo.bar </dev/ttyxx

The problem with standard cu is that it does not kill it's
receiver process when it forks with ~$, thus cu's rcvr swallows
some/much of the protocol traffic from the remote host.

Indeed, as the man page says, ~$ sends the OUTPUT of the forked
process to the line, but it, er, forks up your INPUT.
 
----------------------------------------------------------------------------
Warren Tucker                     emory!n4hgf!wht or wht@n4hgf.Mt-Park.GA.US
"I was 35 years old before I knew a pie was meant to be eaten." - Moe Howard

scotto@ipars.UUCP (Scott O'Connell) (12/07/90)

In article <1990Dec4.080740.4252@actrix.gen.nz> paul@actrix.gen.nz (Paul Gillingwater) writes:
>In article <19@omen.UUCP> caf@omen.UUCP (Chuck Forsberg WA7KGX) writes:
>> -  So far the only comm utility that I can get  to work on my Xenix/286 machine
>> -is cu.  But how do you use sz or rz (zmodem) commands from within cu?  I've
>> -tried many different methods, but none seem to work.  
> 
>> Rz and sz are not written to be used from within cu.  Professional-YAM is
>> designed for dial-out applications.
>
>Yam is good, but the manual is very confusing.  I have used rz and
>sz quite happily from within Kermit, which is widely available for
>Xenix.

Yam is GREAT, but the manual is very confusing and the support sucks.

I've tried to get a Wyse 60 terminal to work with Yam for several weeks.  I 
have tried to use Chuck's GEnie account for support, but he only answers
some of my questions.  When I ask why specific questions weren't answered
he tells me to use voice support.  I don't want to run up a $20 phone call
to the NW when e-mail is available.

I don't know what I've done to warrant such treatment, but I'm tired of 
the problems in trying to deal with Omen Tech.

Does anyone have a Wyse 60 terminal working with Pro-YAM?  Here's my
configuration and the problems encountered:

Compaq 386/20, 8M
SCO Xenix 386 2.3.3 (the real 2.3.3 via xnx155b)
Equinox MegaPort 24 w/2.0.0 drivers
Wyse 60 terminal with ASCII Keyboard

Pro-YAM as installed works fine on the SCO console.  When I try to run
from the Wyse 60 terminal, the program comes up normally and all looks
fine, including the reverse video message "Hit F10 for help".  I 
should note that this terminal/serial port combination works fine with 
other application programs and to the modem with cu.

Pressing F10 on the Wyse keyboard does bring up the help screen, but
it's control codes aren't correct.  It comes across as a bunch of
garbage.

The biggest problem is that when in terminal mode I loose complete 
control of the program.  I can't get back to command mode, I can't
talk to the modem, and I get random IOCTL error messages.  THIS NEVER
HAPPENS AT THE CONSOLE.

At CAF's request, I verified that "echo $TERM" from within Pro-YAM
returns "wy60" in reverse video.  I have also asked for an explanation
of the following:

My Pro-YAM was purchased roughly 2 years ago.  When purchased, the 
printed manual pages were Version 17.50 TurboDial 2.33.  I was told
to download the latest version of Yam which provided me with a "xman"
file which says it's Version 17.66 TurboDial 2.33.  When I actually
press F10 while in the latest Yam (1.2), it says Version 17.47 TurboDial
2.33.

SPECIFIC QUESTIONS:

1.	What's the relation between Pro-YAM 1.2 and help/xman 
	versions 17.47, 17.50 and 17.66?

2.	What could *I* be doing wrong that would work fine at
	the console and not at the terminal?


Thanks in advance to anyone who can help.

jpr@jpradley.jpr.com (Jean-Pierre Radley) (12/08/90)

In article <266@n4hgf.Mt-Park.GA.US> wht@n4hgf.Mt-Park.GA.US (Warren Tucker) writes:
>In article <75@gdx.UUCP> jay@gdx.UUCP (Jay A. Snyder) writes:
>>Stephen Milton (smm@milton.u.washington.edu) writes:
>>->  So far the only comm utility that I can get  to work on my Xenix/286 machine
>>->is cu.
>
>Tru ECU :-) available from comp.sources.misc archives
>(new version Real Soon Now).


I've used XCMALT to invoke rz/sz...
-- 

 Jean-Pierre Radley	    NYC Public Unix	jpr@jpr.com	CIS: 72160,1341

mce@sdcc10.ucsd.edu (Mark Edwards) (12/10/90)

In article <19@omen.UUCP> caf@omen.UUCP (Chuck Forsberg WA7KGX) writes:
#In article <12181@milton.u.washington.edu> smm@milton.u.washington.edu (Stephen Milton) writes:
#-First problem:
#-  So far the only comm utility that I can get  to work on my Xenix/286 machine
#-is cu.  But how do you use sz or rz (zmodem) commands from within cu?  I've
#-tried many different methods, but none seem to work.  
#
#Rz and sz are not written to be used from within cu.  Professional-YAM is
#designed for dial-out applications.

	I used rz and sz very successfully under C-Kermit for a few months.
The technique requires that you use kermit in "command" mode.  Go online to
the modem, and dial your connection.  To download, type "sz filename", then
escape back to kermit.  Run "rz </dev/ttyXX >/dev/ttyXX" as a subshell.
The technique is similar for uploading.  I did this until I could afford to
by Pro-YAM from Chuck. The Pro-YAM product is a much better way to go.  I use
it daily.  So do most of my office mates.  It is definitely $$ well spent.


-- 
Mark C. Edwards             voice:      619/586-2204
Associate Systems Analyst   unix:       mce@pbsdts.pacbell.com
Matt 3:16-17,Acts 7:55-56,*John 8:17-18,*John 14:28,*Mark 13:32,
*John 20:17,*Matt 12:31-32,*John 17:20-23 (* Red letters)