July 14th 03, 09:48 PM
Update:
The breakdown appears to be between the spooler and the
rendering engine (hpeng07.exe). In the failed situation
the rendering doesn't start. IN the working mode (admin)
it kicks off and runs for a bit and then the page pumps
out.
Anyone got a clue as to why this would be the case?
Note - disable spooling and we work fine but painfully
slow.
DF
>-----Original Message-----
>Windows XP Home Edition
>When printing to an HP2210 from and ADMIN class account
>all is well. Demote a user to Limited for security
>purposes. (IE kids stay out of Dad's stuff) The Limited
>user sees the printer status (queue) window and sees
>their job drop in. It immediately dissapears as if
>printed. Sadly the printer doesn't seem to have seen a
>thing. This is a USB printer by the way.
>
>A look at the EventViewer shows:
>Source: Print EventID: 61
>Win32 error code 5 (0x5)
>
>Anybody have a clue?
>
>Does some spool directory or hardware registry entry
have
>to be made public or some such thing.
>Can't find any info on it by error number.
>
>.
>
The breakdown appears to be between the spooler and the
rendering engine (hpeng07.exe). In the failed situation
the rendering doesn't start. IN the working mode (admin)
it kicks off and runs for a bit and then the page pumps
out.
Anyone got a clue as to why this would be the case?
Note - disable spooling and we work fine but painfully
slow.
DF
>-----Original Message-----
>Windows XP Home Edition
>When printing to an HP2210 from and ADMIN class account
>all is well. Demote a user to Limited for security
>purposes. (IE kids stay out of Dad's stuff) The Limited
>user sees the printer status (queue) window and sees
>their job drop in. It immediately dissapears as if
>printed. Sadly the printer doesn't seem to have seen a
>thing. This is a USB printer by the way.
>
>A look at the EventViewer shows:
>Source: Print EventID: 61
>Win32 error code 5 (0x5)
>
>Anybody have a clue?
>
>Does some spool directory or hardware registry entry
have
>to be made public or some such thing.
>Can't find any info on it by error number.
>
>.
>