Canon MultiPass C3000 in Windows XP
I have a Canon MultiPass C3000 and Windows XP. I've found that there is no driver provided by Canon for Windows XP.
Somebody suggested using a BJC 610 or 620 driver but I haven't been successfull with that.
Does anybody have any ideas?
Thanks
~Rob
Somebody suggested using a BJC 610 or 620 driver but I haven't been successfull with that.
Does anybody have any ideas?
Thanks
~Rob
sirbounty
Typically windows 2000 drivers will work - have you tried that?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks!
Happy to help...:D
"Sirbounty" I thank you for your advice on the workaround for using the Canon Multipass C3000 as a printer attached to the XP OS. I did as you suggested and installed the BJC-4200 driver set and use the emulation mode to print. Sure saved money in not having to purchase a new printer (for now!)
Now, however, I am constantly having to cancel the insistent requests from the Automatic Hardware Detection s/w, which finds the C3000 each time I power up my system. Annoying, this set of 3 or 4 steps I have to cancel in order to continue with the boot-up process.
Is there a way of defeating, at least for the C3000 printer, this auto-detect of new hardware? ... I've done some google searches on the internet for 'disable hardware detection' and variants thereof, but to no avail.
My thought is that if I install the C3000 driver (or at least let the hardware detect process go to completion in finding the printer and doing whatever it needs to do to satisfy itself at least once), I can kill two birds with one stone.
That is, I will be able to continue to use the C3000 in emulation mode (having both drivers in the system pointing to the same printer, but going through the emulation mode set-up to print) while also having the OS finally be satisfied that it has found the C3000 and no longer needs to ask for installation of it over and over again.
I have not done the latter (allow auto-detect of and installation of the C3000) ... am waiting for comments/feedback from you and anyone else here in the community!
Thanks for your time!!!
sincerely,
Not_a_Bozo
Now, however, I am constantly having to cancel the insistent requests from the Automatic Hardware Detection s/w, which finds the C3000 each time I power up my system. Annoying, this set of 3 or 4 steps I have to cancel in order to continue with the boot-up process.
Is there a way of defeating, at least for the C3000 printer, this auto-detect of new hardware? ... I've done some google searches on the internet for 'disable hardware detection' and variants thereof, but to no avail.
My thought is that if I install the C3000 driver (or at least let the hardware detect process go to completion in finding the printer and doing whatever it needs to do to satisfy itself at least once), I can kill two birds with one stone.
That is, I will be able to continue to use the C3000 in emulation mode (having both drivers in the system pointing to the same printer, but going through the emulation mode set-up to print) while also having the OS finally be satisfied that it has found the C3000 and no longer needs to ask for installation of it over and over again.
I have not done the latter (allow auto-detect of and installation of the C3000) ... am waiting for comments/feedback from you and anyone else here in the community!
Thanks for your time!!!
sincerely,
Not_a_Bozo
ASKER
Have you tried installing the drive when prompted by the auto detection? I would suggest removing your existing printer driver, restarting, and then using the nagging wizard when it comes up, choose select the driver from a list, and use the Canon BJC 620 or BJC 4200 (they both seem to work).
It sounds like you may have bypassed that wizard and installed the driver yourself and the OS still thinks there is new hardware attached because the driver you installed doesn't match the hardware it's detecting. ?
It sounds like you may have bypassed that wizard and installed the driver yourself and the OS still thinks there is new hardware attached because the driver you installed doesn't match the hardware it's detecting. ?
I'll give this a try, rfiddler, and get back to you. Most likely on Monday or Tuesday. ... and, yes, I just may have bypassed the wizard and installed the driver myself.
Thanks again for your comments.
Not_a_Bozo
Thanks again for your comments.
Not_a_Bozo