🚀 go-pugleaf

kusumoto@chsun1.uchicago.edu (Bob Kusumoto) writes:
 
> You can compile [Transcript] to create the proper files so that
> one of the two serial ports in the back of the sparc will be
> able to talk to the printer without any fuss about using tip or
> kermit or any other communications product.
 
What I meant was that to get the connection going in the first
place, one needs to know the proper port settings.  The easiest
way to establish this is to use tip while editing /etc/remote
to find the framing and handshake settings that work.  These can
then be copied into the ms field in the printcap file.  Perhaps
Transcript has some intelligence that allows it to dynamically
fiddle with the port settings until it finds the correct one,
but this is a pretty sophisticated thing to do programmatically.
Do you know where Transcript has this capability, Bob, or is it
necessary to figure this out manually and tell Transcript the
values with a config file?
 
> Those MS-DOS diskettes are only useful if you are at an MS-DOS
> machine connected directly to the printer (either its serial
> port or over a PC network like Novell Netware or Bayan Vines). 
> It's almost useless if the printer is connected to the sparc
> and you're printing from the sparc
 
I use the MS-DOS version of Adobe fonts on my 386i.  Once I had
the files in a Unix directory, using DOS Windows to copy the
files from the MS-DOS diskettes, I then unwrapped the font
files, which were in the compressed binary format, into a
downloadable text format using the program I posted a couple of
weeks ago.
 
The AFM files were then fed into another of my programs to
generate width data for Borland Sprint (a DOS program).
 
Ken (shiva@well.sf.ca.us)