FYI re: print problems

[tondi]

I have had crazy problems as have others who get
"FOXPROW" error box when attempting to print.

I have had several users 'upgrade' to various HP printers and often have problems. One not uncommon, frustrating scenario is 2 users running same app, same OS, same printer. One gets error and other does not.

I have been 'adding new printer' using HP550c as default
with positive results every time.

Tony

 

[rgbean]

Tony,
Your "answer" may be in

http://support.microsoft.com/default.aspx?scid=kb;en-us;183522

- "FIX: Divide by Zero Creates Err with Third-Party Print Drivers". But since FPW can't directly call 32-bit DLL's you'll need to use CALL32. The CALL32.ZIP file is on Rick Strahl's site at

http://www.west-wind.com/wwfp2pd.htm,

and includes the necessary files and some demo code. I've tried the following (which seems to work):

SET PROCEDURE TO CALL32
IF !("FOXTOOLS" $ SET("LIBRARY"))
   SET LIBRARY TO SYS(2004)+"FOXTOOLS.FLL" ADDITIVE
ENDIF
CLEAR

* Win32 usage
*
*       DECLARE _fpreset IN msvcrt20.dll
*       =_fpreset()

   lhcall32=reg32("_fpreset", "msvcrt20.dll", "")
   lh_fpreset=RegFP("", "L")
   ln_fpreset=callfn(lh_fpreset, lhcall32)

Note: Back when I was using this, I found that while CALL32 works for many 32-bit API calls, others can fail and "hang" the program / workstation - use only when necessary and test on all potential OS platforms.

Rick

 

[tondi]

Thanks Rick,
HP claims 550C and 560C can be used as 'generic'
deskjet drivers. Same is true of 4L for lasers.
Both have worked for my users every time I have found it necessary to try them. There seem to be new printers on the market every day so we can't possible test all of them with, not to mention the other variables which exist for our many users, most of whom are NOT computer literate.
Tony

 

[dbMark]

Talking about the HP 4L printer driver...

I wonder if the 4L had issues like the HP 5L or 6L desktop laser printers. A couple years back some clients had strange problems. Those printers absolutely would not print the very last line of text sent from a ? command in FoxPro for DOS. Even printing another line with "?" didn't force the prior line to print. Finally, after several days I ended up settling on a workaround, printing a space on the next line (? " &quot and that did it, although doing that would occasionally cause an extra formfeed sometimes if I was already on the last line. For some reason the printers (or the drivers) refused to print the last line containing characters from DOS. No help from HP.

 

[tondi]

The 'last line' and part of last line' issue is a foxpro
issue, not a printer issue. Both DOS and Win versions require data to be flushed with 'set printer to' command at end of print routine. On networks, this line of code needs to be repeated 2 or even 3 times. There have been several threads on this issue.
Tony

 

[dbMark]

Thanks! I'll keep that in mind. The only thing that made me think it was the printer at fault was that (1) no other printer models than the desktop "L" series ever demonstrated that behavior at several sites using hundreds of printers, (2) it was first noticed when it was connected locally, and (3) it was next to impossible to get any printer manual or command set specifications without buying a manual from HP (they used to come with every printer in the old days but since few used them I guess they decided to save a buck, in such cases I wish it would be free upon request). Instruction manuals today just tell you how to set it up, no command sets or anything. For that reason we reached the conclusion that the manufacturer must have reworked or twiddled with the "obsolete" DOS code, as it worked fine otherwise.

 

[ramani]

Hi
Just have a look in this also. Could be helpful.

Speed up your Printing under Win9x from FoxPro DOS
thread182-66171

ramani
(Subramanian.G),FoxAcc, ramani_g@yahoo.com