>Don,
>
>If the printer requires a special driver (IOW, one that isn't part of the standard XP >installation), then there's no way around having to install it on each machine, AFAIK.
>
>Once the driver was installed, I don't think that there will be a problem with >AddWindowsPrinterConnection().
>
>I assume from the text above that the error is occurring when you try to set the >printer as the default. Is this correct? If so, rather than using the WSH to set the >default printer, have you tried using SET PRINTER TO < name >?
>
>What line is causing the problem? This is occurring on WinXP, right? I ask
>the second question, because the syntax is different under Win98/ME.


Ah, I did forget that little piece...Yea, my development machine is an XP. Most of the users are/were running a combo of Win9x machines. All are being upgraded to XP and this is what led to the rewrite. I know in Win9X/ME you have to specify a driver and an optional printer port. Since that isn't an issue for them, I've been able to get away from that and just get straight to the queue.

I'll try the SET PRINTER TO and see what I get. The output is pretty much straight text (ASCII) since they are going directly onto preformatted paper. I've been told that they plan to only include a "generic" printer type in each user's Ghost, and I've tried to tell them that when XP attaches to the queue, it's going to bug them for drivers.

We'll see what happens.

--Don