| I think the answer to a) is that it should work, although some
applications, notably Exchange don't work properly with that. So if
somebody sends you an Exchange message that it s a PostScript file, you
can't print directly from Exchange. I think you need to specify how
the customer is printing and where it doesn't work.
The answer to b) is that you don't need to use the Wizard to add the
queues in order to boot them. In fact, I recommend against it. There
is a limit to how many queues can be created, and then it becomes
difficult to manage the queues even from normal menus.
Just go into
Printers, Your Printer name, Properties, Ports, Configure Port,
Options, Configure
There you will see the place to add the Hardware Address, etc. If
Printserver 17/600 does not work, try the regular Printserver 17 driver
and reboot the printer. There are other notes in this conference about
what version of firmware you need to use the 17/600 driver, but I'm not
sure that it matters very much.
Having said that, I would recommend not booting from NT. There are
several limitations. You have no way to determine if the printer boots
unless you connect to it, and you cannot do the equivalent of NCP
TRIGGER. If it doesn't work, you are in the dark. You try stopping
and restarting the spooler, and then you find a VAX and turn on
service on the circuit to see if the MOP requests are reaching the
computer room. It works, but it is a lot more trouble than using VMS
for booting.
Ben
|
| a) The only way that I can think of that you would get autosensing was
if the customer was actually printing through a PATHWORKS queue to
a OpenVMS/DCPS system that was set up for Autosensing. Windows NT
3.51 printer queues do not autosense by themselves. Neither do
Windows NT 4.0 printer queues.
b) This request doesn't make sense. You can't create a new printer
queue with exactly the same name as an existing printer queue.
If you could, how would you or the system ever reliably distinguish
between the two? I don't think you can edit existing printer queues
with the Wizard.
I'm not sure if the Wizard lets you set up booting for a PrintServer
without creating a printer queue. If the purpose is to simply set up
booting from Windows NT and keep the existing queue, I think the
easiest way to do it is to create a dummy printer queue during the
process, then delete the dummy and redirect the existing queue if
necessary.
|