Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
System Hang
Message
From
24/01/2000 21:02:43
 
 
To
24/01/2000 20:19:48
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Title:
Miscellaneous
Thread ID:
00303157
Message ID:
00321978
Views:
34
>>I am also testing the HP Laserjet III driver. So far I'm not having any problem. But having a hard coded printer setup would cause problem if the user is not using a printer compatible to the selected driver.
>>
>>I mean what happens if the user is using an Epson or something else? I could not force them to buy a prefferred printer just for the application program. Maybe some fellows using the same brand of printer could assist us on this.
>
>I'm not sure what you mean by "hard coded". What I'm talking about is setting up a Windows printer (Start-Settings-Printers) to attach to the desired printer. If it's not an HP printer than you don't have the problem with the HP printer drivers. If it is an HP printer than under Properties specify the HP Laserjet III driver. You can also set up another Windows printer which connects to the same printer and uses the standard driver.
>

If you're looking for a least common denominator for lasers other than PostScript stuff, the MS-distributed HP LaserJet Series II drivers are about as solid as cast titanium, and are as close to "plain vanilla laser" as you can get. I've not seend anyone blame this driver for being non-standard, and any PCL-capable printer from HP or it's competitors will be able to survive using this driver, if at the expense of not taking full advantage of every conceivable feature on the printer.

>Make sure that the VFP program uses the printer connection with the Laserjet III driver. The simplest way of doing this is to select that printer as the default printer.
>

Rather than forcing your will on the rest of the environment for the user, ensure that the printer is installed with the HP LaserJet Series II driver as a distinct device, and then use something to set that as the default printer from within VFP - the Wscript.Network SetDefaultPrinter method is a good way to do so. users may not even realize that you're using the ancient driver this way.

>The downside to this is that you get 300 dpi resolution. If the user wants 600 dpi for use with another software product then they can select the other printer connection with the newer driver.
>

Not really the case if you're using fonts that are already resident on the printer in the first place - the horizontal vertical positioning of txt may be limited in this fashion, and emvbedded graphic images, but I doubt there'd be noticable degradation of native font output.

>>Is there a way of asking the HP guys how compatible is their printers with VFP6.0? Better ,yet, the VPF authorities themselves.
>

If you ask HP, they've never made a printer driver they didn't like....
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