Results 1 to 8 of 8
  1. #1
    Lounger
    Join Date
    Jan 2001
    Posts
    34
    Thanks
    0
    Thanked 0 Times in 0 Posts

    A few days ago I posted about

    A few days ago I posted about my difficulty getting my WinXP upgrade to recognize my HP ScanJet 5100c scanner. The info posted on hp.com did not work for me. I decided to try to install with the W2KPro drivers. This worked the first time, it brought up the drivers boundled with WinXP and everything was beautiful. However, the next time I rebooted, it "forgot" and I need to refind the hardware. This occurred several times and then I ran into a brick wall. Upon startup, the plug and play would find a scsi controller, then the scanner and then abruptly crash the whole process.

    I've cleaned out the Registry of any reference to ScanJet (however, several keys relating to scsi controller would not allow deletion). Still crashes. Anybody have any idea about how to clean up things so I can continue to troubleshoot this thing?

    Thanks, David

  2. #2
    Gold Lounger Rebel's Avatar
    Join Date
    Jul 2001
    Location
    Canada
    Posts
    3,024
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: A few days ago I posted about

    Had the same problem with my 5200C. The new drivers do work, but after a lot of experimenting.
    Do a System Restore to a prior time Before you installed the scanjet. Then, unplug the scanner from the computer. Install the scanning software from the CD that came with the 5100 (HP Precision Scan, etc.) and DO NOT reboot. I assume you have already downloaded the WinXP update from HP (if not, do this before you start this whole procedure). After installing from the CD and before rebooting, run the XP patch. Then shut down, reconnect the scanner, and reboot. Hope this procedure works for you - I had a lot of "blue screens" and system restores before I finally figured out to apply the patch before rebooting. HP's lack of instructions on this seem to be typically HP - no wonder they stopped hosting newsgroups - too much legitimate HP bashing.
    John
    A Child's Mind, Once Stretched by Imagination...
    Never Regains Its Original Dimensions

  3. #3
    Lounger
    Join Date
    Jan 2001
    Posts
    34
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: A few days ago I posted about

    Unfortunately, this does not work for me. I had tried it before but I tried it again since I had cleaned out the registry. No go. I can manually get xp to see the scanner if I change the settings on the printer port in Device Manager. It is good for only until the next time I reboot as then it seems to "forget" and the scanner does not show up in the device manager.

  4. #4
    Gold Lounger Rebel's Avatar
    Join Date
    Jul 2001
    Location
    Canada
    Posts
    3,024
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: A few days ago I posted about

    Too bad. Maybe the 5200C is different than the 5300C. With the 5300C and a parallel port connection, the HP software CD actually installs a pseudo SCSI driver (provided by Shuttle Technologies). It is through this driver that the scanning software actually communicates with the scanner. In device manager, I actually see a SCSI/Raid Host Controller and I think that it was this device that was causing the problems prior to applying the XP Patch. Even after applying the patch, I still had to disable (through Msconfig) the HP Parallel Port Test (hpppt.exe). Once I did this, no more blue screens and the scanner and the scanner software are working as they did in Win ME.
    John
    A Child's Mind, Once Stretched by Imagination...
    Never Regains Its Original Dimensions

  5. #5
    Bronze Lounger
    Join Date
    Feb 2001
    Location
    England
    Posts
    1,306
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: A few days ago I posted about

    A passing thought, which may have no relevance at all, but : in the BIOS check the settings for LPT1 (or whatever it may be called - perhaps Printer Port or Parallel Port - and make sure they're set to ECP. If no joy, try EPP and so on down the list. saving, rebooting and testing each time.

    Rgds

  6. #6
    Lounger
    Join Date
    Jan 2001
    Posts
    34
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: A few days ago I posted about

    I'll look into that when I have some time. But you make a point-- this does seem to have something to do with the printer port.

    Why is it that all it takes to recognize the scanner is that I go into the device manager and change the setting ECP Printer Port (LPT1) / Port Settings / Filter Resource Method to any of the other choices other than what is selected, i.e. Try Not to use as an interrupt, Never use an interrupt or Use any interrupt assigned to the port? Just changing the setting of the Filter Resource Method causes it to see the scanner and install the device driver. Then, no matter the setting, it forgets the next time I reboot.

    Anybody know anything about how all this stuff works?


    Thanks, David

  7. #7
    Bronze Lounger
    Join Date
    Feb 2001
    Location
    England
    Posts
    1,306
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: A few days ago I posted about

    erm...., XP doesn't want interrupts : set Never use an Interrupt.

    Rgds

  8. #8
    Lounger
    Join Date
    Jan 2001
    Posts
    34
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: A few days ago I posted about

    This Worked! I changed from ECP to EPP and now my scanner is recognized!

    Thanks so much!

    David

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •