I have posted this in the partner help forum for Vista - It was to technical for them so they sent me to MSDN . . . ;-)) First, I rather would not like to change the program code of this DOS program since the program is just too old, not my stuff and works perfect but just for this case. Frankly I strongly believe it's a Vista DOS Shell / Spooler issue. For all tests I did used administrator rights. I have a DOS application that prints to LPT1-4 using PCL3. This problem shows only in Vista (Business / SP0 / SP1). On a Vista PC with a physical LPT1 port I use net use LPT1 \\VistaPC\HPOfficeJetL7580 and the DOS application prints perfect. On a Vista notebook without a physical LPT Port no printing in this manner is possible. But !! In the regular cmd-shell âDir > LPT1 \\VistaPC\HPOfficeJetL7580â works! Even if I start my DOS application in this same cmd-shell it wonât print then to LPT1-4 from my DOS application. On the other hand if I connect my notebook over the network to any other PC (Win2000, WinXP, SBS2003) that serves as a print server, printing works fine again. So it looks to me as if the Vista Print Spooler is to blame for it. Or maybe the cmd-shell could be pep up with an additional command? Can anyone help?? Thanks Don
Hi, > I have a DOS application that prints to LPT1-4 using PCL3. > On a Vista PC with a physical LPT1 port I use > net use LPT1 \\VistaPC\HPOfficeJetL7580 > and the DOS application prints perfect. Is this UNC mapping actually pointing to a share on the same computer? DOS app and printer are both on same box? > On a Vista notebook without a physical LPT Port no printing in this manner > is possible. > But !! In the regular cmd-shell âDir > LPT1 \\VistaPC\HPOfficeJetL7580â > works! The notebook is not also called "VistaPC" so I assume this UNC path is pointing to your other PC (acting as a print server?) -- Gerry Hickman (London UK)
I don't recall the exact details, but I helped someone get a very old DOS program to print under Vista. Look in the properties on the printer - on one of the tabs, there should be something about "printer pooling". When you enable pooling, you can assign an LPT port to the printer. I did this and assigned LPT1 to the USB printer and the DOS program then had no problems printing to LPT1 as if that port really existed. "Don" <Don@community.nospam> wrote in message news:45A6D23A-A855-4B20-A3BD-14AEDE2595B1@microsoft.com... >I have posted this in the partner help forum for Vista - It was to >technical > for them so they sent me to MSDN . . . ;-)) > > First, I rather would not like to change the program code of this DOS > program since the program is just too old, not my stuff and works perfect > but > just for this case. > Frankly I strongly believe it's a Vista DOS Shell / Spooler issue. > For all tests I did used administrator rights. > > I have a DOS application that prints to LPT1-4 using PCL3. > This problem shows only in Vista (Business / SP0 / SP1). > > On a Vista PC with a physical LPT1 port I use > net use LPT1 \\VistaPC\HPOfficeJetL7580 > and the DOS application prints perfect. > > On a Vista notebook without a physical LPT Port no printing in this manner > is possible. > But !! In the regular cmd-shell "Dir > LPT1 > \\VistaPC\HPOfficeJetL7580" > works! > > Even if I start my DOS application in this same cmd-shell it won't print > then to LPT1-4 from my DOS application. > > On the other hand if I connect my notebook over the network to any other > PC > (Win2000, WinXP, SBS2003) that serves as a print server, printing works > fine > again. > > So it looks to me as if the Vista Print Spooler is to blame for it. > Or maybe the cmd-shell could be pep up with an additional command? > > Can anyone help?? > > Thanks Don >
JD wrote: > Look in the properties on the printer - on one of the tabs, there should be > something about "printer pooling". When you enable pooling, you can assign > an LPT port to the printer. Yup, this is useful for USB printers residing on the same box, wasn't sure if that was Don's situation. -- Gerry Hickman (London UK)
Thanks JD for your sugestion about 'printer pooling'. We use it already and it works fine a long as you have a PC (OS Vista) that has a physical LPT1 port. But if you have a notebook with no physical LPT1 port you will experince excactly the problem I discribed. But Thanks anyway Don "JD" wrote: > I don't recall the exact details, but I helped someone get a very old DOS > program to print under Vista. > > Look in the properties on the printer - on one of the tabs, there should be > something about "printer pooling". When you enable pooling, you can assign > an LPT port to the printer. > > I did this and assigned LPT1 to the USB printer and the DOS program then had > no problems printing to LPT1 as if that port really existed. > > > "Don" <Don@community.nospam> wrote in message > news:45A6D23A-A855-4B20-A3BD-14AEDE2595B1@microsoft.com... > >I have posted this in the partner help forum for Vista - It was to > >technical > > for them so they sent me to MSDN . . . ;-)) > > > > First, I rather would not like to change the program code of this DOS > > program since the program is just too old, not my stuff and works perfect > > but > > just for this case. > > Frankly I strongly believe it's a Vista DOS Shell / Spooler issue. > > For all tests I did used administrator rights. > > > > I have a DOS application that prints to LPT1-4 using PCL3. > > This problem shows only in Vista (Business / SP0 / SP1). > > > > On a Vista PC with a physical LPT1 port I use > > net use LPT1 \\VistaPC\HPOfficeJetL7580 > > and the DOS application prints perfect. > > > > On a Vista notebook without a physical LPT Port no printing in this manner > > is possible. > > But !! In the regular cmd-shell "Dir > LPT1 > > \\VistaPC\HPOfficeJetL7580" > > works! > > > > Even if I start my DOS application in this same cmd-shell it won't print > > then to LPT1-4 from my DOS application. > > > > On the other hand if I connect my notebook over the network to any other > > PC > > (Win2000, WinXP, SBS2003) that serves as a print server, printing works > > fine > > again. > > > > So it looks to me as if the Vista Print Spooler is to blame for it. > > Or maybe the cmd-shell could be pep up with an additional command? > > > > Can anyone help?? > > > > Thanks Don > > > > >
Hi Gerry > Is this UNC mapping actually pointing to a share on the same computer? Yes. The printer will be hocked up to the Vista-Notebook (no physical LPT1) by a patch kabel using the network port 10/100/1000. > DOS app and printer are both on same box? Yes. I opened a DOS Box shared the printer (net use LPT1....) Tested the funcionality (dir > lpt1 ... it works !! ) And you will see a print job in the print job window for a few seconds. I then startet the DOS Application (in this same DOS-Box) - no printing is possible and you won't even see a printjob in the print job window. > The notebook is not also called "VistaPC" so I assume this UNC path is > pointing to your other PC (acting as a print server?) Yes. The Vista-Notebook is it's own printserver. If an other not Vista-OS PC ist the printserver printing is absolutely perfect. -- Don (Switzerland) "Gerry Hickman" wrote: > Hi, > > > I have a DOS application that prints to LPT1-4 using PCL3. > > > On a Vista PC with a physical LPT1 port I use > > net use LPT1 \\VistaPC\HPOfficeJetL7580 > > and the DOS application prints perfect. > > Is this UNC mapping actually pointing to a share on the same computer? > DOS app and printer are both on same box? > > > On a Vista notebook without a physical LPT Port no printing in this manner > > is possible. > > But !! In the regular cmd-shell âDir > LPT1 \\VistaPC\HPOfficeJetL7580â > > works! > > The notebook is not also called "VistaPC" so I assume this UNC path is > pointing to your other PC (acting as a print server?) > > -- > Gerry Hickman (London UK) >
