PMFJI, I use a 4000T & jetdirect. I found that it didn't "play nice" as long as I tried to use the PCL drivers. When I switched everyone to Postscript, everything worked better. I used to get stack over flow errors on the printer and would have client machines lock up when they tried to print. Postscript drivers seem to be the key to fixing the problem.

>Thanks for your replies Ed & Craig,
>
>I guess it was a bit much to expect.. Re the printer issues, the major inconvenience is when a new 4000T printer is installed with the default driver and I get to hear about it when the user gets weird messages on the printer, or the computer locks up, or the printer won't print. That's when I have to explain about using an older printer driver (user: howcome it works just fine for Word?0. :(
>
>
>>No, and no. You need DCOM to be installed properly; while the specific instance of C5 that is noted in the FAQ and MSKB article may have been worked around, there are things fixed by DCOM that really are important to Win9x as a whole, and possibly to your app. Blind installation of DCOM isn't a good move, either; you need to check the OS version, and the registry key, to see if DCOM has been previously installed on the system. Putting an older copy of DCOM in place by force on Win9x can be as troublesome as not putting it on when its needed.
>>
>>As to the printer issue, SP3 addresses at least some of the invalid FP state issues, but I wouldn't count on it fixing everything.
>>
>>IOW, if you have fixes that are working, unless you're losing something by using the HP4 drivers, I'd leave them in place.