>Did you ever get your FPD2.6 apps to print??? We support some FPW2.6 apps - which have been running relatively smoothly. Then within a matter of 2 weeks, 3 clients started receiving Spool32 errors when trying to print large documents. As always, they claim that they "changed nothing" and didn't add any new software or upgrades even though they were previously able to print the same reports (OH NO the dreaded Y2K-1 Bug!!!). I had them "turn off" spooling to the printer and it seemed to help for a while but now ITS BACk at the one site.
>
>Any thoughts would be appreciated..
>
>Rick Becker
>
>>p.s. This message was written on March 22nd, but couldn't connect in the meantime. I brought an OKI laser from office to do some testing (printing from FPD2.6 to a PCL printer while not touching any of the .frx files with embedded ESC/P2 escape sequences, and have it look as much the same as possible). It wouldn't print - spool32 permanently GPFed, or printed blank pages. Then I tried to reinstall everything, to no avail. Tried to install Memphis beta3, with the same result. Uninstalled it, but then it didn't want to keep my internet passwords, so I couldn't log in. Had to play for some ten days or more with it, and finally ended up deleting almost all the Windows files, starting with registry and ini files, including all the .dll files which I couldn't positively define as parts of some benign app. Finally I managed to connect. I've reinstalled Office, and yet have to reinstall VFP... had fun for two weeks. It still doesn't print.

The problem existed on my home machine only - I was using an obsolete cable which didn't have the two-way communication; my FPD apps still print almost anywhere. Sometimes they get stuck... or better, the spooler loses communication with the printer, doesn't complain, doesn't print. Yet, when they restart the machine which acts as a print server, all the jobs ARE queued and it offers to print them right away.

From DOS, I'm printing into a file (always), and then read that file low-level and send it to the printer using ?? commands. Back in DOS-only days, I've opened the printer with fopen() and sent them to the printer via fwrite() in 2K chunks, but that's not quite reliable now. I got it to work under Windows as well, but for text files only - it prints just garbage if I try to print the files for higher-level PCL.