Anonymous_User Absent Member.
Absent Member.
2004 views

Cannot capture to iPrint Printer

NW 6.5 SP5 print server with iPrint client on Windows 98. Old DOS program
prints using capture command.

Tried to do:

capture l=1 p=.iprintername.ou.o

and got the following error:

Capture ... is unable to find printer. .iprintername.ou.o.
in the directory. Make sure the printer name was typed correctly or use
PCONSOLE or the NetWare administrator utility to make sure that it exists.

How can I fix the problem? Create NDPS printer?

Thanks
Don
0 Likes
17 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

don@blackshoe.uk wrote:

>How can I fix the problem?


Use icapture:

http://www.novell.com/documentation/oes/iprint_nw/data/bu4tilz.html#bu4tin2

--
Marcel Cox (using XanaNews 1.18.1.6)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

icapture is not supported on Windows 98. Also nprint.exe does not work with
NW 6.5 pure IP environment.

How can I print from DOS on the Windows 98 to the NW 6.5 iPrint printer. I
know Windows 98 is old but we have old apps that only run in DOS.

Thanks
Don

> don@blackshoe.uk wrote:
>
> >How can I fix the problem?

>
> Use icapture:
>
> http://www.novell.com/documentation/oes/iprint_nw/data/bu4tilz.html#bu4tin2
>
> --
> Marcel Cox (using XanaNews 1.18.1.6)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

don@blackshoe.uk wrote:

>How can I print from DOS on the Windows 98 to the NW 6.5 iPrint printer. I
>know Windows 98 is old but we have old apps that only run in DOS.


Well, in that case, stick with NDPS. For any pritner you define as iPrint,
it is also automatically available as NDPS printer provided you have the
NDPS client installed on the workstation.

--
Marcel Cox (using XanaNews 1.18.1.6)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

On Mon, 15 Jan 2007 21:36:55 +0000, don wrote:

> icapture is not supported on Windows 98. Also nprint.exe does not work
> with NW 6.5 pure IP environment.
>
> How can I print from DOS on the Windows 98 to the NW 6.5 iPrint printer. I
> know Windows 98 is old but we have old apps that only run in DOS.


Keep in mind that with iPrint you can still define old print queues and
then configure the iPrint printer to services those queues. Then just
capture lpt1 to those print queues.

--
Joe Marton
Novell Support Forum SysOp
Novell does not officially monitor these forums!

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

So after I add the queue to iPrint Printer, I can delete the Print Server
and Printer objects then, right?

Thanks
Don

> On Mon, 15 Jan 2007 21:36:55 +0000, don wrote:
>
> > icapture is not supported on Windows 98. Also nprint.exe does not work
> > with NW 6.5 pure IP environment.
> >
> > How can I print from DOS on the Windows 98 to the NW 6.5 iPrint printer. I
> > know Windows 98 is old but we have old apps that only run in DOS.

>
> Keep in mind that with iPrint you can still define old print queues and
> then configure the iPrint printer to services those queues. Then just
> capture lpt1 to those print queues.
>
> --
> Joe Marton
> Novell Support Forum SysOp
> Novell does not officially monitor these forums!
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

On Tue, 16 Jan 2007 15:52:33 +0000, don wrote:

> So after I add the queue to iPrint Printer, I can delete the Print Server
> and Printer objects then, right?


Yes. All you need is the Manager, Broker, iPrint Printer, and Queue. You
don't need the old printer server or old printer objects.

--
Joe Marton
Novell Support Forum SysOp
Novell does not officially monitor these forums!

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

In addition to what Joe says, you don't even need IPX. Print queues work
fine over IP only. It's only old fashioned print servers that had
dependencies on IPX.

--
Marcel Cox (using XanaNews 1.18.1.6)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

On Tue, 16 Jan 2007 18:03:34 +0000, Marcel Cox wrote:

> In addition to what Joe says, you don't even need IPX. Print queues work
> fine over IP only. It's only old fashioned print servers that had
> dependencies on IPX.


Good point!

--
Joe Marton
Novell Support Forum SysOp
Novell does not officially monitor these forums!

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

I got the iPrint to support the queue now.

Now I run into another problem, the DOS app runs:

nprint m:\filename.txt

It prints to the right queue from one workstation properly. On another
Windows 98 machine, when I run the nprint command, I got the nprint help
screen. My question is if I don't specify a queue or printer name, what
does nprint.exe uses to print the output.

Is it on the registry setting or it is a network setting?

Thanks
Don

> On Tue, 16 Jan 2007 15:52:33 +0000, don wrote:
>
> > So after I add the queue to iPrint Printer, I can delete the Print Server
> > and Printer objects then, right?

>
> Yes. All you need is the Manager, Broker, iPrint Printer, and Queue. You
> don't need the old printer server or old printer objects.
>
> --
> Joe Marton
> Novell Support Forum SysOp
> Novell does not officially monitor these forums!
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

On Tue, 16 Jan 2007 18:31:40 +0000, don wrote:

> I got the iPrint to support the queue now.
>
> Now I run into another problem, the DOS app runs:
>
> nprint m:\filename.txt
>
> It prints to the right queue from one workstation properly. On another
> Windows 98 machine, when I run the nprint command, I got the nprint help
> screen. My question is if I don't specify a queue or printer name, what
> does nprint.exe uses to print the output.
>
> Is it on the registry setting or it is a network setting?


With iPrint servicing jobs from the queue, all you should have to do now
is run capture and capture lpt1 to your queue. Then just print to lpt1
normally. For example:

type m:\filename.txt > lpt1

--
Joe Marton
Novell Support Forum SysOp
Novell does not officially monitor these forums!

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

The capture command works for me.

However, the wired thing is an existing Windows 98 will print to a
particular queue by running "nprint m:\filename.txt" but "capture show" has
not queue is captured to any LPT ports.

I don't know where the machine knows which queue or printer to print to. I
assume it would be on some Windows registry key but searched the whole
registry and don't find any queuename.

The other way I can fix the problem is if I can change the queue volume to
a different server that I can use the same print queue name. The reason I
need to move to a different volume is because if I retire an old server
that is servicing the old print queue, then that queue won't work. I am not
sure what would happen if I delete the queue and recreate the same queue
name pointing to a new server's volume that's why I what to know how the
printing works.

Thanks again.
Don

> With iPrint servicing jobs from the queue, all you should have to do now
> is run capture and capture lpt1 to your queue. Then just print to lpt1
> normally. For example:
>
> type m:\filename.txt > lpt1
>
> --
> Joe Marton
> Novell Support Forum SysOp
> Novell does not officially monitor these forums!
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

On Tue, 16 Jan 2007 19:48:16 +0000, don wrote:

> The capture command works for me.
>
> However, the wired thing is an existing Windows 98 will print to a
> particular queue by running "nprint m:\filename.txt" but "capture show"
> has not queue is captured to any LPT ports.


That's because nprint is a NetWare-aware print utility that can print
directly to a queue. It doesn't require anything to be captured.
However, most DOS apps only know how to print to a hardware LPT port.
That's where capture comes into play.

> I don't know where the machine knows which queue or printer to print to. I
> assume it would be on some Windows registry key but searched the whole
> registry and don't find any queuename.


Honestly I can't recall since it's been ages since I've used nprint. You
might want to go to support.novell.com and do some searches for nprint,
making sure to select documentation as a place to search.

> The other way I can fix the problem is if I can change the queue volume to
> a different server that I can use the same print queue name. The reason I
> need to move to a different volume is because if I retire an old server
> that is servicing the old print queue, then that queue won't work. I am
> not sure what would happen if I delete the queue and recreate the same
> queue name pointing to a new server's volume that's why I what to know how
> the printing works.


Well as long as the queue had the same name and was in the same container,
it wouldn't matter that it was deleted and recreated. That's probably the
easiest way to "move" the queue to a new server.

For your DOS situation, assuming what you need is to simply have a DOS app
on a Win98 box print to a queue, here's what you should do.

- Create the queue on the appropriate server.
- Configure iPrint to service jobs from that queue.
- Use a batch file to launch the DOS app and have the batch file execute
capture.
- Configure the app to print to the LPT port captured in your capture
command.

You shouldn't otherwise need to use nprint.

--
Joe Marton
Novell Support Forum SysOp
Novell does not officially monitor these forums!

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

don@blackshoe.uk wrote:

>However, the wired thing is an existing Windows 98 will print to a
>particular queue by running "nprint m:\filename.txt" but "capture show" has
>not queue is captured to any LPT ports.


Well, if you are just printing a file, you can also print the same file
with the command like this:

copy m:\filename.txt \\servername\queuename

In other works, you can simply copy a file to print queues and the the
file will be pritned.

>I don't know where the machine knows which queue or printer to print to. I
>assume it would be on some Windows registry key but searched the whole
>registry and don't find any queuename.


If you use a command like capture or nprint without a print queue or
pritner name, then the tool will read the print job configuration
information from NDS. It will first check the user object to see if it has
print job configuration attributes set, and if not, it will continue with
the container object containing the user.


>The other way I can fix the problem is if I can change the queue volume to
>a different server that I can use the same print queue name. The reason I
> need to move to a different volume is because if I retire an old server
>that is servicing the old print queue, then that queue won't work. I am not
>sure what would happen if I delete the queue and recreate the same queue
>name pointing to a new server's volume that's why I what to know how the
>printing works.


There are tools like PQMOVE from JRButils ( http://www.jrbsoftware.com/ )
or Hostedit from Dreamlan ( http://www.dreamlan.com/hostedit.htm ) that
allow you to move queues.
If you delete the queue and create a new one, you will loose all
references to it and you will have to assiciate it again with the print
server (or NDPS printer) and you need to recreate your pritn job
configuration.

--
Marcel Cox
http://support.novell.com/forums
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot capture to iPrint Printer

Thanks everyone for the help. I agree, it was so long agao since I work
with nprint as well.

I will recreate the queue and see what happen next.

Cheer!
Don

> don@blackshoe.uk wrote:
>
> >However, the wired thing is an existing Windows 98 will print to a
> >particular queue by running "nprint m:\filename.txt" but "capture show" has
> >not queue is captured to any LPT ports.

>
> Well, if you are just printing a file, you can also print the same file
> with the command like this:
>
> copy m:\filename.txt \\servername\queuename
>
> In other works, you can simply copy a file to print queues and the the
> file will be pritned.
>
> >I don't know where the machine knows which queue or printer to print to. I
> >assume it would be on some Windows registry key but searched the whole
> >registry and don't find any queuename.

>
> If you use a command like capture or nprint without a print queue or
> pritner name, then the tool will read the print job configuration
> information from NDS. It will first check the user object to see if it has
> print job configuration attributes set, and if not, it will continue with
> the container object containing the user.
>
>
> >The other way I can fix the problem is if I can change the queue volume to
> >a different server that I can use the same print queue name. The reason I
> > need to move to a different volume is because if I retire an old server
> >that is servicing the old print queue, then that queue won't work. I am not
> >sure what would happen if I delete the queue and recreate the same queue
> >name pointing to a new server's volume that's why I what to know how the
> >printing works.

>
> There are tools like PQMOVE from JRButils ( http://www.jrbsoftware.com/ )
> or Hostedit from Dreamlan ( http://www.dreamlan.com/hostedit.htm ) that
> allow you to move queues.
> If you delete the queue and create a new one, you will loose all
> references to it and you will have to assiciate it again with the print
> server (or NDPS printer) and you need to recreate your pritn job
> configuration.
>
> --
> Marcel Cox
> http://support.novell.com/forums


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.