>Ed,
>
>No, we haven't been able to figure out how to make the IBM (using XP Professional) capture LPT1. I guess, that's where the problem really is. When running the app on the Dell (using Win2k), it prints fine, but Win2k allows us to capture LPT1.
>
>So is MAP USE our answer on the IBM Laptop? I'll look into it this morning... I'm headed out to that site to do some more troubleshooting.
>
NET USE on Microsoft Client networks, and CAPTURE on Novell, or calls to the WSH Wscript.Network AddprinterConnection or AddWindowsPrinterConnection methods, or the WNet API all would work.
In my Win2K login script, I assign the queue laserplain on the DC WEATHERSVR to LPT1: with the following:
NET USE LPT2 /D
REM this deleted the pre-existing mapping of a device to LPT2 if it was there
NET USE LPT2 \\WEATHERSVR\LASERPLAIN /yes /persistent:yes
REM this assigned the LASERPLAIN queue to my LPT2 device
>
>>>I am trying to bet a printout in Foxpro 2.6 for DOS in Windows XP Professional... however, the complete application locks up as soon as the print job is issued. The server is a new Dell running Win2k and the printer is a Lexmark Laser shared. The workstatiion that is locking up is a new IBM thinkpad with the default printer the Lexmark on the Dell.
>>>
>>>Does anyone have any experience with this?
>>
>>Have you use MAP USE to assign the Lexmark to a printer port so that a DOS app can see it? FPDOS can't figure out Windows Printer names without assigning them to a DOS device name like LPT1...
