Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Printing to USB Printer???
Message
From
25/08/2000 17:39:19
 
 
To
25/08/2000 15:49:38
Calvin Smith
Wayne Reaves Computer Systems
Macon, Georgia, United States
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Miscellaneous
Thread ID:
00409410
Message ID:
00409464
Views:
33
>I have just discovered that if a user attempts to print to a USB port printer the program crashes. I am using the 'Set printer to name (printer name string)'. The printer is on port 'USB/Deskjet 950C/US9BH1K0B7JM'. The crash is as follows 1. Printer not ready error box 2. An error has occured... To keep working... with Close/Ignore buttons. Clicking Ignore more than twice makes the program go away and triggers a GPF.
>
>Can anyone tell me the proper procedure to print to a USB port printer? Thanks

Is this Win9x or NT/2K? On Win9x, you might try referencing the pritner by it's port name; my ME box is much happier when I refer to the printer as EPUSB1: than as "Epson Stylus 740 on USB Port"; the 2K boxes are happy as clams referencing it across the LAN by UNC or arbitrary names. I tend to map a logical DOS device to a printer using the WSH if no permanent mapping exists. I also am careful not to put spaces and special characters in my fully qualified UNCs, which has been problematic for me with Win95 boxes.

I'd try renaming the printer UNC with _ rather than / at a minimum to make the parser a little less uncomfortable. No guarentees, but short and sweet and simple generally avoids issues. It may be seeing the / as a folder delimiter...

Ed (with the unimaginitive printer names Epson740 and HPLJ4P)
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform