|
-
August 25th, 2003, 06:11 PM
#1
Registered User
-
August 25th, 2003, 08:25 PM
#2
Registered User
Have you tried the most recent drivers. Maybe search the HP site for simular things from other people. I found this thread. Maybe try some of what they are doing here:
http://forums.itrc.hp.com/cm/Questio...7a778c,00.html
-
August 25th, 2003, 10:42 PM
#3
MegaMod
You might also want to read up on Troubleshooting Shared Printing Issues in a Microsoft Windows 2000 or Windows XP Environment . It lists step-by-step procedures. One of the things it says is to disable bi-directional support...normally, you wouldn't want to do this.
Of course, you already checked HP's latest drivers for Win2K.
You might also want to read up on Alternate Printer Driver Choices. Lots of good basic info there.
One more: Manuals for your LJ5000.
Just a couple of suggestions...let us know how it all ends up.
-
August 26th, 2003, 09:31 AM
#4
Registered User
thanx for the tips...whats funny is we have another printer just like this working fine...
I have looked at the settings and drivers and there both the same no diffrence, tryed newer drivers but that one pinter is still giving us fuss. hummm might be a bad jetdirect card
-
August 26th, 2003, 11:46 PM
#5
MegaMod
Basic Troubleshooting Tips for your Expanded IO card.
BTW, do you have a model number for that JetDirect card? Is it J4135A? Go here for troubleshooting the J4136A. Notice the two links at the bottom for JetDirect software & firmware updates.
-
August 29th, 2003, 12:51 PM
#6
Registered User
FIXED: we tryed every driver from HP, but when we went to use the windows driver instead it works fine
-
August 29th, 2003, 01:05 PM
#7
Banned
Originally posted by +Daemon+
FIXED: we tryed every driver from HP, but when we went to use the windows driver instead it works fine
That is the absolute first time I have ever heard that as a resolution. Interesting predicament!
-
September 2nd, 2003, 09:44 AM
#8
Registered User
Originally posted by Ya_know
That is the absolute first time I have ever heard that as a resolution. Interesting predicament!
ya serrious it took us 1 1/2 weeks to fix this..oh and no user is ahving excel crashes now weird huh?
just shows how crappy and dependent M$ apps are
-
September 2nd, 2003, 09:53 AM
#9
Banned
Originally posted by +Daemon+
ya serrious it took us 1 1/2 weeks to fix this..oh and no user is ahving excel crashes now weird huh?
just shows how crappy and dependent M$ apps are
It also goes to show that drivers included with the MS OS's are typically so unreliable that in 1.5 weeks noone there or here for that matter even thought of it as a solution, even if just for grins...
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks