AL wrote:
> Using hpnp.

Don't top-post. It makes for confusing conversations.

I suggest you try this with netcat and see if the problem still exists.


>
>
>
> "Tony Lawrence" <pcunix@gmail.com> wrote in message
news:<cgo3mf$41s@odah37.prod.google.com>...
> > AL wrote:
> >
> > > However, a new problem cropped up. For one of the printers (an HP
> > > laserjet 9000), whenever 2 or more large files are printed, the
last
> > > job is not released from the spooler, although all the jobs do
print.
> > > The spooler believes the last job is still printing and will stay
> > that
> > > way and not print anything else until that job is cancelled. It
only
> > > happens when printing files larger than 75,000 bytes, and only
when 2
> > > or more are sent in succession. And it only happens with that
> > printer.
> > > Printer prints fine from Windows.
> >
> >
> > Are you using Netcat (
> > http://aplawrence.com/SCOFAQ/FAQ_scotec7getnetcat.html ) or the
hpnp
> > stuff?

"Tony Lawrence" <pcunix@gmail.com> wrote in message news:<cgv7q6$s3q@odak26.prod.google.com>...
> AL wrote:
> > Using hpnp.
>
> Don't top-post. It makes for confusing conversations.
>
> I suggest you try this with netcat and see if the problem still exists.
>
>
> >
> >
> >
> > "Tony Lawrence" <pcunix@gmail.com> wrote in message
> news:<cgo3mf$41s@odah37.prod.google.com>...
> > > AL wrote:
> > >
> > > > However, a new problem cropped up. For one of the printers (an HP
> > > > laserjet 9000), whenever 2 or more large files are printed, the
> last
> > > > job is not released from the spooler, although all the jobs do
> print.
> > > > The spooler believes the last job is still printing and will stay
> that
> > > > way and not print anything else until that job is cancelled. It
> only
> > > > happens when printing files larger than 75,000 bytes, and only
> when 2
> > > > or more are sent in succession. And it only happens with that
> printer.
> > > > Printer prints fine from Windows.
> > >
> > >
> > > Are you using Netcat (
> > > http://aplawrence.com/SCOFAQ/FAQ_scotec7getnetcat.html ) or the
> hpnp
> > > stuff?

I am trying that today...

alb@opensystemscomputing.com (AL) wrote in message news:<5c4735f6.0408301039.2f301e9c@posting.google. com>...
> "Tony Lawrence" <pcunix@gmail.com> wrote in message news:<cgv7q6$s3q@odak26.prod.google.com>...
> > AL wrote:
> > > Using hpnp.
> >
> > Don't top-post. It makes for confusing conversations.
> >
> > I suggest you try this with netcat and see if the problem still exists.
> >
> >
> > >
> > >
> > >
> > > "Tony Lawrence" <pcunix@gmail.com> wrote in message
> news:<cgo3mf$41s@odah37.prod.google.com>...
> > > > AL wrote:
> > > >
> > > > > However, a new problem cropped up. For one of the printers (an HP
> > > > > laserjet 9000), whenever 2 or more large files are printed, the
> last
> > > > > job is not released from the spooler, although all the jobs do
> print.
> > > > > The spooler believes the last job is still printing and will stay
> that
> > > > > way and not print anything else until that job is cancelled. It
> only
> > > > > happens when printing files larger than 75,000 bytes, and only
> when 2
> > > > > or more are sent in succession. And it only happens with that
> printer.
> > > > > Printer prints fine from Windows.
> > > >
> > > >
> > > > Are you using Netcat (
> > > > http://aplawrence.com/SCOFAQ/FAQ_scotec7getnetcat.html ) or the
> hpnp
> > > > stuff?
>
> I am trying that today...


Well, I got netcat working, but unfortunately, it did not solve the
problem. Exact same symptoms. works fine for small files, but try to
print /etc/termcap 3 times and it hangs up. I would suspect the
printer, but it did all work fine and only stopped when the root
filesystem was copied from a "duplicate" server.

Anyone have any other ideas?

In article <5c4735f6.0409011304.275ad2a@posting.google.com> ,
AL <alb@opensystemscomputing.com> wrote:
>alb@opensystemscomputing.com (AL) wrote in message news:<5c4735f6.0408301039.2f301e9c@posting.google. com>...
>> "Tony Lawrence" <pcunix@gmail.com> wrote in message news:<cgv7q6$s3q@odak26.prod.google.com>...
>> > AL wrote:
>> > > Using hpnp.
>> >
>> > Don't top-post. It makes for confusing conversations.
>> >
>> > I suggest you try this with netcat and see if the problem still exists.
>> >
>> >
>> > >
>> > >
>> > >
>> > > "Tony Lawrence" <pcunix@gmail.com> wrote in message
>> news:<cgo3mf$41s@odah37.prod.google.com>...
>> > > > AL wrote:
>> > > >
>> > > > > However, a new problem cropped up. For one of the printers (an HP
>> > > > > laserjet 9000), whenever 2 or more large files are printed, the
>> last
>> > > > > job is not released from the spooler, although all the jobs do
>> print.
>> > > > > The spooler believes the last job is still printing and will stay
>> that
>> > > > > way and not print anything else until that job is cancelled. It
>> only
>> > > > > happens when printing files larger than 75,000 bytes, and only
>> when 2
>> > > > > or more are sent in succession. And it only happens with that
>> printer.
>> > > > > Printer prints fine from Windows.
>> > > >
>> > > >
>> > > > Are you using Netcat (
>> > > > http://aplawrence.com/SCOFAQ/FAQ_scotec7getnetcat.html ) or the
>> hpnp
>> > > > stuff?
>>
>> I am trying that today...

>Well, I got netcat working, but unfortunately, it did not solve the
>problem. Exact same symptoms. works fine for small files, but try to
>print /etc/termcap 3 times and it hangs up. I would suspect the
>printer, but it did all work fine and only stopped when the root
>filesystem was copied from a "duplicate" server.

Going back and reading your first post you say it only happens with
files over 75,000 bytes and if printed three times in succession.

That brings this question. Can you print ONE file that would be on
the order of 250,000 bytes. When testing remote printers
I built a huge file of alphabet and numbers [like the old
teletype test pages for those who remember those beasts], and
then ran it through pr to add line numbers.

When I could print a 100 page report on 8.5x14" paper on a system
150 miles away I considered it working.

See if you can determine it it is a size problem, or a problem
running multiple copies back to back.

Since you are running netcat and it fails that sounds like it is
pointing right to the printer spooler. Since you can have multiple
logins on an SCO machine, make a new login and change to the spool
directory and then watch when you start the multiple print jobs.

You might also look at the printer log files to see if there
is any hint there. Usually those just have job ID, time, and
printer name, but if you send three jobs and see it only twice [not
likely but you have to check everything] then it might give a hint.

If you can print a huge file, but just not many, I suspect there
may be permissions problems, or locking problems.

If you can print one big file, and then have it fail on printing
three files in succession, see if you can print four files in
succession.

Another question - on the last file that locks up - does any of it
print? If so perhaps the file is in the printer and just needs to
be flushed. Send a printer reset as the last part of the job
and see if that cures that.

Older printers used to hang, but the newer ones usually have a time
out and will flush any buffer after awhile.

Will the other system print to this same printer flawlessly.
There could be some internal setting on the printer that differs
from another if you have not tested this approach.

Bill

--
Bill Vermillion - bv @ wjv . com

bv@wjv.com (Bill Vermillion) wrote in message news:<I3E3uD.1s8M@wjv.com>...
> In article <5c4735f6.0409011304.275ad2a@posting.google.com> ,
> AL <alb@opensystemscomputing.com> wrote:
> >alb@opensystemscomputing.com (AL) wrote in message news:<5c4735f6.0408301039.2f301e9c@posting.google. com>...
> >> "Tony Lawrence" <pcunix@gmail.com> wrote in message news:<cgv7q6$s3q@odak26.prod.google.com>...
> >> > AL wrote:
> >> > > Using hpnp.
> >> >
> >> > Don't top-post. It makes for confusing conversations.
> >> >
> >> > I suggest you try this with netcat and see if the problem still exists.
> >> >
> >> >
> >> > >
> >> > >
> >> > >
> >> > > "Tony Lawrence" <pcunix@gmail.com> wrote in message
> news:<cgo3mf$41s@odah37.prod.google.com>...
> >> > > > AL wrote:
> >> > > >
> >> > > > > However, a new problem cropped up. For one of the printers (an HP
> >> > > > > laserjet 9000), whenever 2 or more large files are printed, the
> last
> >> > > > > job is not released from the spooler, although all the jobs do
> print.
> >> > > > > The spooler believes the last job is still printing and will stay
> that
> >> > > > > way and not print anything else until that job is cancelled. It
> only
> >> > > > > happens when printing files larger than 75,000 bytes, and only
> when 2
> >> > > > > or more are sent in succession. And it only happens with that
> printer.
> >> > > > > Printer prints fine from Windows.
> >> > > >
> >> > > >
> >> > > > Are you using Netcat (
> >> > > > http://aplawrence.com/SCOFAQ/FAQ_scotec7getnetcat.html ) or the
> hpnp
> >> > > > stuff?
> >>
> >> I am trying that today...
>
> >Well, I got netcat working, but unfortunately, it did not solve the
> >problem. Exact same symptoms. works fine for small files, but try to
> >print /etc/termcap 3 times and it hangs up. I would suspect the
> >printer, but it did all work fine and only stopped when the root
> >filesystem was copied from a "duplicate" server.
>
> Going back and reading your first post you say it only happens with
> files over 75,000 bytes and if printed three times in succession.
>
> That brings this question. Can you print ONE file that would be on
> the order of 250,000 bytes. When testing remote printers
> I built a huge file of alphabet and numbers [like the old
> teletype test pages for those who remember those beasts], and
> then ran it through pr to add line numbers.
>
> When I could print a 100 page report on 8.5x14" paper on a system
> 150 miles away I considered it working.
>
> See if you can determine it it is a size problem, or a problem
> running multiple copies back to back.
>
> Since you are running netcat and it fails that sounds like it is
> pointing right to the printer spooler. Since you can have multiple
> logins on an SCO machine, make a new login and change to the spool
> directory and then watch when you start the multiple print jobs.
>
> You might also look at the printer log files to see if there
> is any hint there. Usually those just have job ID, time, and
> printer name, but if you send three jobs and see it only twice [not
> likely but you have to check everything] then it might give a hint.
>
> If you can print a huge file, but just not many, I suspect there
> may be permissions problems, or locking problems.
>
> If you can print one big file, and then have it fail on printing
> three files in succession, see if you can print four files in
> succession.
>
> Another question - on the last file that locks up - does any of it
> print? If so perhaps the file is in the printer and just needs to
> be flushed. Send a printer reset as the last part of the job
> and see if that cures that.
>
> Older printers used to hang, but the newer ones usually have a time
> out and will flush any buffer after awhile.
>
> Will the other system print to this same printer flawlessly.
> There could be some internal setting on the printer that differs
> from another if you have not tested this approach.
>
> Bill


Thanks for all the suggestions - I will try them out soon. I agree I
need to determine if it is a size problem or a multiple copies problem
or a combination of both. I think it more size related or a
combination, since I can print many smaller files without a problem.

Some more info:

The printer is a newer model, a high-end Laserjet 9000. It was all
working fine until they restored the root filesystem from the
duplicate server, in effect bringing over the problem. I even tried
restoring all of the printing-related files from backup, but no help.
I removed and re-installed the printing modules, but no help.

All jobs sent to the queue print, even the last one, but the last one
is never cleared from the queue, so any jobs sent after just queue up
until someone cancels the job.

Finally a personal question - Did you used to do consulting work for
Seminole Community College in the 80's?

Thanks,

Al

AL wrote:
>
> alb@opensystemscomputing.com (AL) wrote in message news:<5c4735f6.0408301039.2f301e9c@posting.google. com>...
> > "Tony Lawrence" <pcunix@gmail.com> wrote in message news:<cgv7q6$s3q@odak26.prod.google.com>...
> > > AL wrote:
> > > > Using hpnp.
> > >
> > > Don't top-post. It makes for confusing conversations.
> > >
> > > I suggest you try this with netcat and see if the problem still exists.
> > >
> > >
> > > >
> > > >
> > > >
> > > > "Tony Lawrence" <pcunix@gmail.com> wrote in message
> > news:<cgo3mf$41s@odah37.prod.google.com>...
> > > > > AL wrote:
> > > > >
> > > > > > However, a new problem cropped up. For one of the printers (an HP
> > > > > > laserjet 9000), whenever 2 or more large files are printed, the
> > last
> > > > > > job is not released from the spooler, although all the jobs do
> > print.
> > > > > > The spooler believes the last job is still printing and will stay
> > that
> > > > > > way and not print anything else until that job is cancelled. It
> > only
> > > > > > happens when printing files larger than 75,000 bytes, and only
> > when 2
> > > > > > or more are sent in succession. And it only happens with that
> > printer.
> > > > > > Printer prints fine from Windows.
> > > > >
> > > > >
> > > > > Are you using Netcat (
> > > > > http://aplawrence.com/SCOFAQ/FAQ_scotec7getnetcat.html ) or the
> > hpnp
> > > > > stuff?
> >
> > I am trying that today...
>
> Well, I got netcat working, but unfortunately, it did not solve the
> problem. Exact same symptoms. works fine for small files, but try to
> print /etc/termcap 3 times and it hangs up. I would suspect the
> printer, but it did all work fine and only stopped when the root
> filesystem was copied from a "duplicate" server.

Al,

This sounds similar to a problem I had with Gesttner Copier/printers
at an office using Word Perfect 5.1. They purchased 3 new copier printers
to replace 2 old HP Lasers with built in Jet Direct cards.

I had set up the network printing using netcat to the HP's over a year ago
and they have been running without out problems. But when I set up the new
copier/printers, several jobs would print and then the printers would hang,
with jobs stacking up in the queue.

Powering the printers off/on would usually clear the stuck job, but not always.

I finally traced the problem to Word Perfect 5.1 port settings that I
had set up for the new printers. I failed to follow the settings I
had developed for the HP's and allowed wpport to modify the
printer interface scripts as it is want to do. WordPerfect jobs
to the printers would hang sometimes. you could copy the /usr/spool/temp
XXXXX-1 tmp file and send it to one of the other copier printers with
-oraw and it would print.

After a couple of days of tearing out my hair, I finally noticed the
difference in the wpport definition and modified the port settings
for the new copier/printers to specify "remote LP printer" for the
output type and "lp -s -oraw -c printername < <f>" for the "Adjust
spooler command" and since then there have been no more hung print jobs.

The long and short of the above is that the junk being sent by Word
Perfect would hang the printers. Once the port was defined as a remote
LP spooler, Word Perfect generated its print job in a different format
and used the specified lp -oraw to send it to the local spooler. My
Netcat interface respects the -oraw and just dumps the image without
adding printer control strings for font, page size, line endings,
etc.. Problem solved.

All the Windows machines (win98 and WinXP) print to the shared UNIX
print spooler via the VisionFS printer shares. None of the windows
printers print directly to the copier/printers.

>
> Anyone have any other ideas?

--

Steve Fabac
S.M. Fabac & Associates
816/765-1670

In article <5c4735f6.0409021214.168f2c95@posting.google.com >,
AL <alb@opensystemscomputing.com> wrote:
>bv@wjv.com (Bill Vermillion) wrote in message news:<I3E3uD.1s8M@wjv.com>...
>> In article <5c4735f6.0409011304.275ad2a@posting.google.com> ,
>> AL <alb@opensystemscomputing.com> wrote:
>> >alb@opensystemscomputing.com (AL) wrote in message news:<5c4735f6.0408301039.2f301e9c@posting.google. com>...
>> >> "Tony Lawrence" <pcunix@gmail.com> wrote in message news:<cgv7q6$s3q@odak26.prod.google.com>...
>> >> > AL wrote:
>> >> > > Using hpnp.
>> >> >
>> >> > Don't top-post. It makes for confusing conversations.
>> >> >
>> >> > I suggest you try this with netcat and see if the problem still exists.
>> >> >
>> >> >
>> >> > >
>> >> > >
>> >> > >
>> >> > > "Tony Lawrence" <pcunix@gmail.com> wrote in message
>> news:<cgo3mf$41s@odah37.prod.google.com>...
>> >> > > > AL wrote:
>> >> > > >
>> >> > > > > However, a new problem cropped up. For one of the printers (an HP
>> >> > > > > laserjet 9000), whenever 2 or more large files are printed, the
>> last
>> >> > > > > job is not released from the spooler, although all the jobs do
>> print.
>> >> > > > > The spooler believes the last job is still printing and will stay
>> that
>> >> > > > > way and not print anything else until that job is cancelled. It
>> only
>> >> > > > > happens when printing files larger than 75,000 bytes, and only
>> when 2
>> >> > > > > or more are sent in succession. And it only happens with that
>> printer.
>> >> > > > > Printer prints fine from Windows.
>> >> > > >
>> >> > > >
>> >> > > > Are you using Netcat (
>> >> > > > http://aplawrence.com/SCOFAQ/FAQ_scotec7getnetcat.html ) or the
>> hpnp
>> >> > > > stuff?
>> >>
>> >> I am trying that today...
>>
>> >Well, I got netcat working, but unfortunately, it did not solve the
>> >problem. Exact same symptoms. works fine for small files, but try to
>> >print /etc/termcap 3 times and it hangs up. I would suspect the
>> >printer, but it did all work fine and only stopped when the root
>> >filesystem was copied from a "duplicate" server.
>>
>> Going back and reading your first post you say it only happens with
>> files over 75,000 bytes and if printed three times in succession.
>>
>> That brings this question. Can you print ONE file that would be on
>> the order of 250,000 bytes. When testing remote printers
>> I built a huge file of alphabet and numbers [like the old
>> teletype test pages for those who remember those beasts], and
>> then ran it through pr to add line numbers.
>>
>> When I could print a 100 page report on 8.5x14" paper on a system
>> 150 miles away I considered it working.
>>
>> See if you can determine it it is a size problem, or a problem
>> running multiple copies back to back.
>>
>> Since you are running netcat and it fails that sounds like it is
>> pointing right to the printer spooler. Since you can have multiple
>> logins on an SCO machine, make a new login and change to the spool
>> directory and then watch when you start the multiple print jobs.
>>
>> You might also look at the printer log files to see if there
>> is any hint there. Usually those just have job ID, time, and
>> printer name, but if you send three jobs and see it only twice [not
>> likely but you have to check everything] then it might give a hint.
>>
>> If you can print a huge file, but just not many, I suspect there
>> may be permissions problems, or locking problems.
>>
>> If you can print one big file, and then have it fail on printing
>> three files in succession, see if you can print four files in
>> succession.
>>
>> Another question - on the last file that locks up - does any of it
>> print? If so perhaps the file is in the printer and just needs to
>> be flushed. Send a printer reset as the last part of the job
>> and see if that cures that.
>>
>> Older printers used to hang, but the newer ones usually have a time
>> out and will flush any buffer after awhile.
>>
>> Will the other system print to this same printer flawlessly.
>> There could be some internal setting on the printer that differs
>> from another if you have not tested this approach.

>Thanks for all the suggestions - I will try them out soon. I agree I
>need to determine if it is a size problem or a multiple copies problem
>or a combination of both. I think it more size related or a
>combination, since I can print many smaller files without a problem.

All I'll say is probably. But with computers you can never tell
:-)


>Some more info:

>The printer is a newer model, a high-end Laserjet 9000. It was all
>working fine until they restored the root filesystem from the
>duplicate server, in effect bringing over the problem. I even tried
>restoring all of the printing-related files from backup, but no help.
>I removed and re-installed the printing modules, but no help.

I guess the machines weren't exact duplicates then. Or the
restoration changed permissions. Did you have a SuperTar, or was
it just a tar or cpio. Not being careful with those can change
things.

>All jobs sent to the queue print, even the last one, but the last one
>is never cleared from the queue, so any jobs sent after just queue up
>until someone cancels the job.

>Finally a personal question - Did you used to do consulting work for
>Seminole Community College in the 80's?

Spent two 1/2 to 3/4 days a week for about 10 years. At first
taking care of 11 Xenix systems, and then as it migrated to Netware
almost exclusively working in filePro.

There were the occaisional things when the anti-Unix group realized
there were certain things they needed Unix for. So I resurected on
SCO machine and made it the internet email gateway which passed
the mail to their OS/2 mail handler, which passed to the Netware
users. Then when they realized their secure web servers needed
more than what MS offered, I had to get their Sun up and running
for them.

They were so happy to get rid of all the Xenix and thinking they'd
never need another Unix system ever - until they found that someone
had led them down the garden path as to capabilities.

I also watched them replace a $50K switch with another when someone
had not understood just what it was they wanted.

Bill

--
Bill Vermillion - bv @ wjv . com

"Steve M. Fabac, Jr." <smfabac@att.net> wrote in message news:<41379C03.C512BCC4@att.net>...
> AL wrote:
> >
> > alb@opensystemscomputing.com (AL) wrote in message news:<5c4735f6.0408301039.2f301e9c@posting.google. com>...
> > > "Tony Lawrence" <pcunix@gmail.com> wrote in message news:<cgv7q6$s3q@odak26.prod.google.com>...
> > > > AL wrote:
> > > > > Using hpnp.
> > > >
> > > > Don't top-post. It makes for confusing conversations.
> > > >
> > > > I suggest you try this with netcat and see if the problem still exists.
> > > >
> > > >
> > > > >
> > > > >
> > > > >
> > > > > "Tony Lawrence" <pcunix@gmail.com> wrote in message
> news:<cgo3mf$41s@odah37.prod.google.com>...
> > > > > > AL wrote:
> > > > > >
> > > > > > > However, a new problem cropped up. For one of the printers (an HP
> > > > > > > laserjet 9000), whenever 2 or more large files are printed, the
> last
> > > > > > > job is not released from the spooler, although all the jobs do
> print.
> > > > > > > The spooler believes the last job is still printing and will stay
> that
> > > > > > > way and not print anything else until that job is cancelled. It
> only
> > > > > > > happens when printing files larger than 75,000 bytes, and only
> when 2
> > > > > > > or more are sent in succession. And it only happens with that
> printer.
> > > > > > > Printer prints fine from Windows.
> > > > > >
> > > > > >
> > > > > > Are you using Netcat (
> > > > > > http://aplawrence.com/SCOFAQ/FAQ_scotec7getnetcat.html ) or the
> hpnp
> > > > > > stuff?
> > >
> > > I am trying that today...
> >
> > Well, I got netcat working, but unfortunately, it did not solve the
> > problem. Exact same symptoms. works fine for small files, but try to
> > print /etc/termcap 3 times and it hangs up. I would suspect the
> > printer, but it did all work fine and only stopped when the root
> > filesystem was copied from a "duplicate" server.
>
> Al,
>
> This sounds similar to a problem I had with Gesttner Copier/printers
> at an office using Word Perfect 5.1. They purchased 3 new copier printers
> to replace 2 old HP Lasers with built in Jet Direct cards.
>
> I had set up the network printing using netcat to the HP's over a year ago
> and they have been running without out problems. But when I set up the new
> copier/printers, several jobs would print and then the printers would hang,
> with jobs stacking up in the queue.
>
> Powering the printers off/on would usually clear the stuck job, but not always.
>
> I finally traced the problem to Word Perfect 5.1 port settings that I
> had set up for the new printers. I failed to follow the settings I
> had developed for the HP's and allowed wpport to modify the
> printer interface scripts as it is want to do. WordPerfect jobs
> to the printers would hang sometimes. you could copy the /usr/spool/temp
> XXXXX-1 tmp file and send it to one of the other copier printers with
> -oraw and it would print.
>
> After a couple of days of tearing out my hair, I finally noticed the
> difference in the wpport definition and modified the port settings
> for the new copier/printers to specify "remote LP printer" for the
> output type and "lp -s -oraw -c printername < <f>" for the "Adjust
> spooler command" and since then there have been no more hung print jobs.
>
> The long and short of the above is that the junk being sent by Word
> Perfect would hang the printers. Once the port was defined as a remote
> LP spooler, Word Perfect generated its print job in a different format
> and used the specified lp -oraw to send it to the local spooler. My
> Netcat interface respects the -oraw and just dumps the image without
> adding printer control strings for font, page size, line endings,
> etc.. Problem solved.
>
> All the Windows machines (win98 and WinXP) print to the shared UNIX
> print spooler via the VisionFS printer shares. None of the windows
> printers print directly to the copier/printers.
>
> >
> > Anyone have any other ideas?

They're not using WordPerfect, but perhaps I can apply some of the
same ideas. Thanks for the suggestions.

Al
Al

bv@wjv.com (Bill Vermillion) wrote in message news:<I3Fu1K.38G@wjv.com>...
> In article <5c4735f6.0409021214.168f2c95@posting.google.com >,
> AL <alb@opensystemscomputing.com> wrote:
> >bv@wjv.com (Bill Vermillion) wrote in message news:<I3E3uD.1s8M@wjv.com>...
> >> In article <5c4735f6.0409011304.275ad2a@posting.google.com> ,
> >> AL <alb@opensystemscomputing.com> wrote:
> >> >alb@opensystemscomputing.com (AL) wrote in message news:<5c4735f6.0408301039.2f301e9c@posting.google. com>...
> >> >> "Tony Lawrence" <pcunix@gmail.com> wrote in message news:<cgv7q6$s3q@odak26.prod.google.com>...
> >> >> > AL wrote:
> >> >> > > Using hpnp.
> >> >> >
> >> >> > Don't top-post. It makes for confusing conversations.
> >> >> >
> >> >> > I suggest you try this with netcat and see if the problem still exists.
> >> >> >
> >> >> >
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > > "Tony Lawrence" <pcunix@gmail.com> wrote in message
> news:<cgo3mf$41s@odah37.prod.google.com>...
> >> >> > > > AL wrote:
> >> >> > > >
> >> >> > > > > However, a new problem cropped up. For one of the printers (an HP
> >> >> > > > > laserjet 9000), whenever 2 or more large files are printed, the
> last
> >> >> > > > > job is not released from the spooler, although all the jobs do
> print.
> >> >> > > > > The spooler believes the last job is still printing and will stay
> that
> >> >> > > > > way and not print anything else until that job is cancelled. It
> only
> >> >> > > > > happens when printing files larger than 75,000 bytes, and only
> when 2
> >> >> > > > > or more are sent in succession. And it only happens with that
> printer.
> >> >> > > > > Printer prints fine from Windows.
> >> >> > > >
> >> >> > > >
> >> >> > > > Are you using Netcat (
> >> >> > > > http://aplawrence.com/SCOFAQ/FAQ_scotec7getnetcat.html ) or the
> hpnp
> >> >> > > > stuff?
> >> >>
> >> >> I am trying that today...
>
> >> >Well, I got netcat working, but unfortunately, it did not solve the
> >> >problem. Exact same symptoms. works fine for small files, but try to
> >> >print /etc/termcap 3 times and it hangs up. I would suspect the
> >> >printer, but it did all work fine and only stopped when the root
> >> >filesystem was copied from a "duplicate" server.
> >>
> >> Going back and reading your first post you say it only happens with
> >> files over 75,000 bytes and if printed three times in succession.
> >>
> >> That brings this question. Can you print ONE file that would be on
> >> the order of 250,000 bytes. When testing remote printers
> >> I built a huge file of alphabet and numbers [like the old
> >> teletype test pages for those who remember those beasts], and
> >> then ran it through pr to add line numbers.
> >>
> >> When I could print a 100 page report on 8.5x14" paper on a system
> >> 150 miles away I considered it working.
> >>
> >> See if you can determine it it is a size problem, or a problem
> >> running multiple copies back to back.
> >>
> >> Since you are running netcat and it fails that sounds like it is
> >> pointing right to the printer spooler. Since you can have multiple
> >> logins on an SCO machine, make a new login and change to the spool
> >> directory and then watch when you start the multiple print jobs.
> >>
> >> You might also look at the printer log files to see if there
> >> is any hint there. Usually those just have job ID, time, and
> >> printer name, but if you send three jobs and see it only twice [not
> >> likely but you have to check everything] then it might give a hint.
> >>
> >> If you can print a huge file, but just not many, I suspect there
> >> may be permissions problems, or locking problems.
> >>
> >> If you can print one big file, and then have it fail on printing
> >> three files in succession, see if you can print four files in
> >> succession.
> >>
> >> Another question - on the last file that locks up - does any of it
> >> print? If so perhaps the file is in the printer and just needs to
> >> be flushed. Send a printer reset as the last part of the job
> >> and see if that cures that.
> >>
> >> Older printers used to hang, but the newer ones usually have a time
> >> out and will flush any buffer after awhile.
> >>
> >> Will the other system print to this same printer flawlessly.
> >> There could be some internal setting on the printer that differs
> >> from another if you have not tested this approach.
>
> >Thanks for all the suggestions - I will try them out soon. I agree I
> >need to determine if it is a size problem or a multiple copies problem
> >or a combination of both. I think it more size related or a
> >combination, since I can print many smaller files without a problem.
>
> All I'll say is probably. But with computers you can never tell
> :-)
>
>
> >Some more info:
>
> >The printer is a newer model, a high-end Laserjet 9000. It was all
> >working fine until they restored the root filesystem from the
> >duplicate server, in effect bringing over the problem. I even tried
> >restoring all of the printing-related files from backup, but no help.
> >I removed and re-installed the printing modules, but no help.
>
> I guess the machines weren't exact duplicates then. Or the
> restoration changed permissions. Did you have a SuperTar, or was
> it just a tar or cpio. Not being careful with those can change
> things.
>
> >All jobs sent to the queue print, even the last one, but the last one
> >is never cleared from the queue, so any jobs sent after just queue up
> >until someone cancels the job.
>
> >Finally a personal question - Did you used to do consulting work for
> >Seminole Community College in the 80's?
>
> Spent two 1/2 to 3/4 days a week for about 10 years. At first
> taking care of 11 Xenix systems, and then as it migrated to Netware
> almost exclusively working in filePro.
>
> There were the occaisional things when the anti-Unix group realized
> there were certain things they needed Unix for. So I resurected on
> SCO machine and made it the internet email gateway which passed
> the mail to their OS/2 mail handler, which passed to the Netware
> users. Then when they realized their secure web servers needed
> more than what MS offered, I had to get their Sun up and running
> for them.
>
> They were so happy to get rid of all the Xenix and thinking they'd
> never need another Unix system ever - until they found that someone
> had led them down the garden path as to capabilities.
>
> I also watched them replace a $50K switch with another when someone
> had not understood just what it was they wanted.
>
> Bill


We met back in the late 80's when I came down to the College to do a
training class on the Lex Word processor. Do you remember that? It was
my first job in the computer industry after changing careers from
Chemistry. It was also my first training class, so I was pretty
nervous. Seems like ages ago...

Al

In article <5c4735f6.0409071314.7963520f@posting.google.com >,
AL <alb@opensystemscomputing.com> wrote:
>bv@wjv.com (Bill Vermillion) wrote in message news:<I3Fu1K.38G@wjv.com>...
>> In article <5c4735f6.0409021214.168f2c95@posting.google.com >,

[lots and lots deleted ..]


>> >Finally a personal question - Did you used to do consulting work for
>> >Seminole Community College in the 80's?

>> Spent two 1/2 to 3/4 days a week for about 10 years. At first
>> taking care of 11 Xenix systems, and then as it migrated to Netware
>> almost exclusively working in filePro.

.....

>We met back in the late 80's when I came down to the College to do a
>training class on the Lex Word processor. Do you remember that? It was
>my first job in the computer industry after changing careers from
>Chemistry. It was also my first training class, so I was pretty
>nervous. Seems like ages ago...

I remeber the WP, and I remember the classes for the users. I
don't remember 1/2 the faces that I saw regularly so you'll forgive
me if I can't put a face to your name, but I do remember the event.

They scheduled everyone who would be using it for 1 of 2 days of
training as I recall, and we had one room set up for a lot of users.
Nobody seems to do that anymore. But computers weren't as
ubiquitous then.

For those who aren't familiar with Lex, it was from Trajectory/ACE
and was the father or grandfather of the SCO Lyrix. ISTR it started
as a word processor on a PDP-11 ??. So it was a WP that was
tailored to a Unix system and that made it flexible.

We also took the CGA adaptors out of the PC's used as terminals
and put in the old MDA adaptors. That mean you could see bold
and underline just as they'd appear in a document. With the CGA
adaptors bold [as I recall] would have a reverse video background
of different colors.

That had to be the most configurable WP I've ever seen. If you had
a tech manual for a printer or terminal you could make it work.

And I kept the old tech manual after they decommisioned Lex as
it was quite interesting. It would totally confuse most who
who came into computers in the last few years.

I just grabbed it to look at - and going through the section on
setting up a test document to print all the characters, and then
going through to define the spacing on each character so you
could properly print with any proportional font you can find
is something that would make most people choose something else :-)

Things were really difficult to do in those days. Now it's just a
matter of buying some font sets and going with what you like.

'twas a good education though.

Bill

--
Bill Vermillion - bv @ wjv . com