M
measekite
FRANKIE CRANKIE IS A TROLL AND HE IS A JERK.peterf said:
C
cvt
Effectively they are the identical thing, the onboards are accessed through
the PCI bus just as that card you have is. Onchips are similar aswell.
But when it comes to file/printer sharing this is done 100% in software, If
your printer prints locally it will not matter what its plugged into,
windows manages the sharing from a level above hardware and drivers.
--
C
cvt
The same devices that don't work properly on some onboards/onchips.
"windows explorer not recognise" wow.. I always thought windows explorer
was a gui file explorer, not a kernel, not driver management.
what you explained was driver issues, and your blaming hardware...
absolute pro you are..
you have no end to stupidity.
you've gone from amusing to plain annoying.
Killfiled.
--
C
cvt
I should add there are some devices that have issues with some cards,
namely NEC USB2 chipsets, but latelky there drivers have been better and
these issues are dissapearing, but that is not your issue since its
working locally.
--
P
peterf
Thanks for the clarification, I'm not quite sure what to try next... maybe
I'll boot the W2K partition, install the printer on it and see what happens
with that. I thought that maybe there was some sort of USB/sharing issue
originally but now I'm at a bit of a loss. Thanks again for all your help.
Peter
I'll boot the W2K partition, install the printer on it and see what happens
with that. I thought that maybe there was some sort of USB/sharing issue
originally but now I'm at a bit of a loss. Thanks again for all your help.
Peter
M
measekite
INCORRECT CIVET DA KATcvt said:
NOT TRUE ANIMAL. GO TO THE WESTERN DIGITAL SITE
YOU GOTTA BE A DUMB OLD FART
GOOD I AM TIRE OF YOU
T
Tony
peterf said:
Peter
I have watched this thread and did not respond because I had nothing to offer
at that time, but it seems you are now clutching at straws so I will provide a
few.
1. Are you using the built in XP networking functionality? Or are you using
Novell or similar?
2. At the beginning of the thread there was a debate about whether the drivers
should be installed on each PC or not, whilst I have no direct experience with
networking this printer I can emphatically advise that the generic answer is
"sometimes", it depends on the printer driver design. Some printers when
networked will load the drivers from the host PC and some will request the CD
with the drivers on, which one applies to your printer I do not know. What is
clear is that each PC can see the printer. If you go to control panel/printers
and right click on the printer icon (on a remote PC) is the printer reported as
either offline or paused? If either is so that is incorrect. In fact if the
icon is greyed out that is also incorrect. Sorry if this is basic but sometimes
the swamp hides the 'gators!
3. What cvt advised is technically correct but I have seen some very strange
phenomena with USB hubs and whilst you are not using a hub I wonder whether you
are right in suspecting the usb card. Is it easy to disable the card and use
the internal USB port just as a test? I have a scanner that works perfectly
with any internal usb port but will not work through 2 different makes of
powered USB hubs, I have also had a printer that works fine through a D-Link
hub but not a Belkin hub. So it is worth pursuing the usb direction I think.
4. When you install the printer on a remote PC, do you see any file transfer
activity from the host (loading drivers from the host) or altenatively do you
have to insert the CD? One of these should occur since your printer is not
natively supported by WinXP.
5. When you installed the printers on the remote PC's did you use add printer
and search for the networked printer or did you use some other method?
Out of ideas for now.
Good luck, please advise how you get on.
Tony
C
cvt
I'll add one thing..
If you want to see the file transfer, but not sure how, DUmeter is the
simplest way, and a nice little app to have, alternatively use task
manager.
I'll stick with my its not usb
your again talking local issues, whereas he is fine local, just not
remote, but one can always be proven wrong, thats my thesis on this
.Theres no harm in trying, but I don't beleive it to be the source of the
problem.
--
T
Tony
cvt said:I'll add one thing..
If you want to see the file transfer, but not sure how, DUmeter is the
simplest way, and a nice little app to have, alternatively use task
manager.
I'll stick with my its not usb
your again talking local issues, whereas he is fine local, just not
remote, but one can always be proven wrong, thats my thesis on this
Theres no harm in trying, but I don't beleive it to be the source of the
problem.
You are probably right - as I said I'm clutching at straws since the obvious
advice has not worked. I have been proven wrong more times than I care to
remember but if you are never wrong then you didn't try
Tony
P
peterf
Tony said:
XP native network using a Netgear FVS318v3
As a test, I did try it both ways. Both times the i9900 was seen/connected
to, but errored out on the actual print.
Well because of that "latchup" issue, I don't wish to risk it on this pc
(mine) but I might move the printer to another system and try it in reverse
Well, yes on both counts. When using the Printer Wizard/Networked Printer,
the drivers loaded and successfully installed according to the wizard. In
scenario 2, I installed the driver to the remote pc from the ini files on a
shared folder.\
Yes, networked printer (removed/reinstalled several times)
Thanks, I need much!
Peter
F
Frank
Are you able to try reversing your setup? Physically install the i9900peterf said:
on the computer that it won't network print from and try to network
print from the computer it is currently physically installed on?
Frank