View Single Post

   
  #7 (permalink)  
Old 02-15-2008, 11:50 AM
David P. Lurie
 
Posts: n/a
Default Re: Termlite Problem

Connect/Print Setup on my system gives a drop-down box with all available
Windows printers; an HP1220 on a JetDirect box also shows up as a shared
printer on the SCO box (via Samba) and as a shared printer from a few other
Windows boxes that mistakenly shared it on installation. All other network
printers show up as well. I can print to the HP1220 from TermLite without
problem.

The Network/Connect to Printer option at the lower left hand corner only
shows the two JetDirect Printers shared by Samba on the SCO box, likely
because no printers are directly connected to my PC.

Part or all of the problem may be related to adding/configuring the printer
for TermLite from within TermLite, rather than directly through Windows.
TermLite is an old 16 bit Windows 3.1 app, with internal configuration
restrictions as noted, but can access printers previously configured in
Windows XP .


"David Font" <comms@systime.co.nz> wrote in message
news:3f8c6362$1@news.iconz.co.nz...
> Yes, your problem is the printer destination is a remote network printer

and
> termlite doesnt print to a printer based on its UNC name.
> However you can around that by mapping a LPTx port number to the UNC name
> and making that LPTx the default printer for that Termlite user. Note:
> Termlite will only print to the PC's default printer.
>
> If that is impractical, you may have to consider replacing termlite with
> Netterm which is a satisfactory product.
>
> Regards
> Dave
> "Kevin F. Lane" <klane@lane-company.com> wrote in message
> news:veAhb.106909$qj6.3311022@news1.news.adelphia. net...
> > I am using Termlite 1.1 to access my SCO OSE 5.05 server over the

> internet.
> >
> > Transparent print works to a remote printer which is directly connected

to
> > the remote PC but not to a remote network printer.
> >
> > Any suggestions?
> >
> > --
> > ________________
> > Kevin F. lane
> > 978-281-5263
> > klane@lane-company.com
> >
> >

>
>



Reply With Quote