S
SortaNortth
In the last few days I used the windowsupdate to update my Windows XP.
Since that upgrade I have been unable to print from most of my applications.
The only applications that will allow printing are Adobe Acrobat and MS
Access. If I convert my documents to Adobe Acrobat format, they will print
from Acrobat 6.0. Otherwise, besides MS Access nothing else prints. I get
one of two things that happens when I try to print
1. I get a printer error:
ERROR: syntaxerror
OFFENDING COMMAND: ==image (or nostringval or PScript_WinNT_Inc)
2. Nothing happens. The file goes to the printer, but nothing happens.
So, did the latest XP Security update screw up my printing? My Windows 2000
Server and my Macintosh OSX 10.1 both still print to the same network
printer without skipping a beat.
Setup:
OS: Windows XP Pro with all latest updates
Office 2002 Pro(10.xxxx.3501)
Acrobat Pro 6.0
Printer:HP Laserjet 6MP with latest drivers
printing through an HP JetDirect EXPlus box.
Any ideas of how I might cure this problem? Anyone else reporting the same
problem?
Thanks for any information.
Dick Marcum
(e-mail address removed)
Since that upgrade I have been unable to print from most of my applications.
The only applications that will allow printing are Adobe Acrobat and MS
Access. If I convert my documents to Adobe Acrobat format, they will print
from Acrobat 6.0. Otherwise, besides MS Access nothing else prints. I get
one of two things that happens when I try to print
1. I get a printer error:
ERROR: syntaxerror
OFFENDING COMMAND: ==image (or nostringval or PScript_WinNT_Inc)
2. Nothing happens. The file goes to the printer, but nothing happens.
So, did the latest XP Security update screw up my printing? My Windows 2000
Server and my Macintosh OSX 10.1 both still print to the same network
printer without skipping a beat.
Setup:
OS: Windows XP Pro with all latest updates
Office 2002 Pro(10.xxxx.3501)
Acrobat Pro 6.0
Printer:HP Laserjet 6MP with latest drivers
printing through an HP JetDirect EXPlus box.
Any ideas of how I might cure this problem? Anyone else reporting the same
problem?
Thanks for any information.
Dick Marcum
(e-mail address removed)