Artine
asked on
Cannot scan under Windows 2000
I'm unable to use my CanoScan D660U under Windows 2000. I'm dualbooting 2k and Win98, and I'm able to scan just fine under Win98.
Something strange is that--and I don't know if this is normal, it might be--under Device Manager, there are two sets of the "USB Root Hub" and the "VIA USH Host Controller." One of them lists my scanner as a connected device and that there is one free port. The other says there are two free ports. I currently have only two free ports (although up until a while ago I had two additional ports connected to the mainboard, but I removed them suspecting that they were the culprits.) Before I reformatted and upgraded a few hardware components, I was able to use this scanner under Win2k as well as 98. I have an ABIT KT7A mainboard.
Any ideas at all?
Something strange is that--and I don't know if this is normal, it might be--under Device Manager, there are two sets of the "USB Root Hub" and the "VIA USH Host Controller." One of them lists my scanner as a connected device and that there is one free port. The other says there are two free ports. I currently have only two free ports (although up until a while ago I had two additional ports connected to the mainboard, but I removed them suspecting that they were the culprits.) Before I reformatted and upgraded a few hardware components, I was able to use this scanner under Win2k as well as 98. I have an ABIT KT7A mainboard.
Any ideas at all?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
pc_doc: I'm getting to download the service pack as I type and I will let you know how I fared as soon as it's done installing.
genguy: I'll try the BIOS update after the service pack, and let you know about that. And I had already tried your idea about deleting the drivers and letting Windows detect it; well, it detected two again.....
So I'll return in a while with more info.
genguy: I'll try the BIOS update after the service pack, and let you know about that. And I had already tried your idea about deleting the drivers and letting Windows detect it; well, it detected two again.....
So I'll return in a while with more info.
ASKER
Okay, I'm back after trying SP2. Windows now treats my scanner like it should and it passes the diagnostic test and I can begin scanning images. However, the scanner shuts itself off completely in the middle of scans and will not function properly again until being restarted.... It works just fine under 98, so I know it's not a hardware problem with the scanner itself. Odd, odd, odd.... If you've got any ideas about that, shoot 'em at me, and once I've got it all resolved, I'm giving the points to pc_doc.
The latest drivers for your scanner are here:
http://209.85.7.18/techsupport.php?p=csd660u&q=download&type=windows
They were updated to jan,2001. If yours are older, they may help.
I may have given some bad advice in my last comment. The southbridge of the via kt133a supports 4 usb ports (even though your motherboard only has 2), so 2 entries of the controller MAY be normal.
This seems very odd though, I would think that only 1 entry for the controller would be necessary, supporting all 4 possible ports. I will look for more info on this.
http://209.85.7.18/techsupport.php?p=csd660u&q=download&type=windows
They were updated to jan,2001. If yours are older, they may help.
I may have given some bad advice in my last comment. The southbridge of the via kt133a supports 4 usb ports (even though your motherboard only has 2), so 2 entries of the controller MAY be normal.
This seems very odd though, I would think that only 1 entry for the controller would be necessary, supporting all 4 possible ports. I will look for more info on this.
ASKER
I tried upgrading the drivers; no luck...
Although a strange new development; the scanner doesn't seem to be functioning under Windows 98 now either......... It worked perfectly under Win98 as recently as three days ago...... Too strange...
Although a strange new development; the scanner doesn't seem to be functioning under Windows 98 now either......... It worked perfectly under Win98 as recently as three days ago...... Too strange...
Did you do a virus check with an up-to-date program?
Is your hard drive full? (this could also be a symptom of a virus).
Is your hard drive full? (this could also be a symptom of a virus).
ASKER
I have done a virus scan and I'm clean. And no, my harddrive is not full; getting there, but nowhere near close enough to matter (1.6GB).
I think the problem may be with the device itself.
Can you try the scanner on another machine?
Can you try the scanner on another machine?
ASKER
genguy: Good idea; I'll have access to another machine later on today and I'll give that a try.
ASKER
Okay, I tested it out on another machine and it works absolutely perfectly. Not a single flaw in installation or operation. The other machine was also running Windows 2000..... This gets weirder by the minute...
Hmmm, this is getting tough.
I'm starting to run out of ideas, 99% of the time what we have tried so far cures the problem.
In Appendix C and D of the motherboard manual (follow link if you don't have yours) they describe a service pack and usb drivers (usb drivers will have to install under both win98 and win2000 I think)
ftp://66.40.22.130/download/manual/english/kt7a-raid.pdf
If you didn't install these when you re-loaded your system, then this is very likely the problem. They are on the Abit cd that came with your motherboard.
In the bios setup I found a few things that could affect this:
Please check these settings;
Under "Integrated Peripherals"
USB Controller = Enabled
USB Keyboard = OS
(if you have a usb keyboard and need support under dos, then set this to Bios)
Under "PnP/PCI Configurations"
PnP OS Installed = Yes
This setting allows windows to take control of the Plug and Pray assignments.
You can try setting this to No. It may cause windows to re-detect your hardware though. The bios may set up things differently to windows if there is a conflict between one of your cards and a motherboard device.
I'm starting to run out of ideas, 99% of the time what we have tried so far cures the problem.
In Appendix C and D of the motherboard manual (follow link if you don't have yours) they describe a service pack and usb drivers (usb drivers will have to install under both win98 and win2000 I think)
ftp://66.40.22.130/download/manual/english/kt7a-raid.pdf
If you didn't install these when you re-loaded your system, then this is very likely the problem. They are on the Abit cd that came with your motherboard.
In the bios setup I found a few things that could affect this:
Please check these settings;
Under "Integrated Peripherals"
USB Controller = Enabled
USB Keyboard = OS
(if you have a usb keyboard and need support under dos, then set this to Bios)
Under "PnP/PCI Configurations"
PnP OS Installed = Yes
This setting allows windows to take control of the Plug and Pray assignments.
You can try setting this to No. It may cause windows to re-detect your hardware though. The bios may set up things differently to windows if there is a conflict between one of your cards and a motherboard device.
ASKER
I did install the USB drivers when I first set up my system, and I've tried reinstalling them several times.
And your idea about the USB keyboard; I have a PS/2 keyboard.
And I'll see what happens with PnP OS installed in a few minutes.
Also, I should note that I eMailed Canon's tech support and they finally got stumped and gave up on me saying that they'd seen it one other time in a Win2k system that had ACPI enabled and that I should disable it in the system BIOS. Well, there's no way that I could see to disable it. So I eMailed ABIT's tech support and they said that I would have to reinstall the OS and install it as a Standard PC instead of an ACPI PC. Well, I didn't want to reinstall, so I changed the driver for my computer under Device Manager, which, of course, made Windows have to redetect all of my hardware and I had to reconfigure everything. (I never did get it to like my second NIC again, though, so I had to swap out my old ISA Etherlink 3c509b-TPO for a Linksys Ether16). But now it's supposedly a Standard PC with no ACPI support, and it doesn't work. (Although the Canon people said that I'd have to disable ACPI in the BIOS...)
And your idea about the USB keyboard; I have a PS/2 keyboard.
And I'll see what happens with PnP OS installed in a few minutes.
Also, I should note that I eMailed Canon's tech support and they finally got stumped and gave up on me saying that they'd seen it one other time in a Win2k system that had ACPI enabled and that I should disable it in the system BIOS. Well, there's no way that I could see to disable it. So I eMailed ABIT's tech support and they said that I would have to reinstall the OS and install it as a Standard PC instead of an ACPI PC. Well, I didn't want to reinstall, so I changed the driver for my computer under Device Manager, which, of course, made Windows have to redetect all of my hardware and I had to reconfigure everything. (I never did get it to like my second NIC again, though, so I had to swap out my old ISA Etherlink 3c509b-TPO for a Linksys Ether16). But now it's supposedly a Standard PC with no ACPI support, and it doesn't work. (Although the Canon people said that I'd have to disable ACPI in the BIOS...)
ASKER
Tee hee! I've figured something out; my computer hates me. But anyway... I tried updating the BIOS and now the scanner works just fine under Windows 98. Who knows what that means.... Maybe it's just a coincidence, i don't know. But I realized that, for some inexplicable reason, my LinkSys NIC didn't like connecting to the LAN under 2k (although it worked just fine under 98) so I put my 3COM NIC back in, and I've got the same problem as before--device can't start--and fiddling around with the NIC has led me to accidentally disable the CD-ROM drive so Win2k won't boot at this point (actually, all I need to do is jump into Safe mode, fiddle with the NIC's resources, and then reboot again; so it's not a big deal) so I haven't had a chance to test the scanner in 2k with the new BIOS yet, but I'm off to do that now. I'll report back shortly.
Also, I don't know if I mentioned this, but when I was testing the scanner out a bit a while ago (under 2k), it seemed to work okay for about 10-15 seconds, and then it just shut itself off and wouldn't come back on. That does sound like ACPI to me, but I don't know these things. I haven't yet sat in Win98 long enough for it to turn itself off to find out if it'll come back on, but when I've had a chance, I'll let you know......
Also, I don't know if I mentioned this, but when I was testing the scanner out a bit a while ago (under 2k), it seemed to work okay for about 10-15 seconds, and then it just shut itself off and wouldn't come back on. That does sound like ACPI to me, but I don't know these things. I haven't yet sat in Win98 long enough for it to turn itself off to find out if it'll come back on, but when I've had a chance, I'll let you know......
ASKER
Okay, I'm in Win2k now. It's pretending to work, I was able to make one full scan without any problems. But I still have no functioning NIC, and I wonder what will happen when I get my NIC to work again, whether or not it'll conflict with the USB... I'm gonna keep working with the NIC and see if I can get both it and the scanner to function... If you have any ideas for the NIC, let me know. (Device manager says "Device Cannot Start" with no reason. And the NIC's utility program crashes with a divide by 0 error, so I can't run it....
ASKER
Alright, I think everything's working now. I'm going to test everything more rigorously later on today, but I was able to scan on my first test and the NIC is working now. All I needed to do was set the computer back to ACPI, so, basically, genguy, if I had followed your advice in the first place and not putzed around, it would have worked a few days ago. :-) I'll award points to you this evening after testing thorougly to make sure the hardware's not lying to me like it was the other day.
Well I'm glad you've got it working. As far as the NIC's go it's the same deal, the drivers usually are the culprit.
However on page 3-42 of your Abit manual is text and a handy chart showing PCI slot IRQ sharing. Often just moving them to a different slot gets the card working, or the motherboard resource that it interfered with.
However on page 3-42 of your Abit manual is text and a handy chart showing PCI slot IRQ sharing. Often just moving them to a different slot gets the card working, or the motherboard resource that it interfered with.
ASKER
Thanks so much for helping me even though I didn't comply with your suggestions at first; I really, really appreciate it!
also see if you can get win2K drivers for the usb port as well as for the scanner