Results 1 to 5 of 5
  1. #1
    5 Star Lounger
    Join Date
    Jul 2001
    Location
    Terneuzen, Netherlands
    Posts
    895
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Device installation & INF-files

    Have a problem installing an USB-device in Win98. This is a modem but first should be 'recognized' as CAPI-device. For this I use the original floppy, which -and here it comes- worked flawlessy several times in the past but now refuses to recognize a driver...
    (the device itself is OK as it works fine under XP: I'm using a dual-boot setup)


    My question is specific but also generic: what does Win(98) do when it recognizes a new device, asks for a 'source' and I 'give' it the floppy below??? How are the files processed? What makes Windows tell me it cannot find a right driver?
    Again: this is the original floppy so it MUST work; I guess there's something on my system/in the registry that prevents positive recognition and thus subsequent installation.


    Anybody who can advise here (and tell me what I could do/check?)???

    Thanks,

    Erik Jan

    =========

    Here's the files on the floppy:

    22,528 capi2032.dll
    9,552 capi20.dll
    102,720 eehusbcp.sys
    1,004 elinkusb.inf
    897 svoxusb.inf
    27,136 capi2log.exe



    And here's the 'svoxsb.inf' file (which I believe should be 'the one' but is not recognized anymore)

    ; Windows USB Setup File
    ; Manufacturer: KPN Telecom
    ; Date: 27.10.98
    ; Comment: driver version 1.1.1

    [Version]
    Signature="$CHICAGO$"
    Class=USB
    provider=

  2. #2
    Silver Lounger
    Join Date
    Apr 2001
    Location
    New York, New York, USA
    Posts
    2,328
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Device installation & INF-files

    For detailed answer to your questions, see
    Microsoft Windows 98 Resource Kit ISBN: 1-57231-644-6

    In brief:

    1. what does Win(98) do when it recognizes a new device ?
    Answer: Looks for .inf file with the line
    Signature="$CHICAGO$"
    that matches device's PNP data in %Windir%INF folder. If such file is not found, it prompts user for this file.

    2. asks for a 'source'
    Answer: it looks for specific files listed in .inf file. In your case, they are:
    EehUsbCP.sys
    Capi2032.dll
    Capi2Log.exe
    and suppose to be in the same folder where .inf file is.

    3. How are the files processed?
    Answer: They are copied to %Windir%system folder.

    4. What makes Windows tell me it cannot find a right driver?
    Answer: These files are corrupted or not present in the same folder where .inf file is.

    5. this is the original floppy so it MUST work
    Answer: Your floppy may be corrupted, damaged or erased. Use Scandisk to check it. If so, try to download a new driver from Internet.

    6. tell me what I could do/check?
    Answer: Boot computer to the Safe Mode (F5 during bootup); open Device Manager and delete all instances of your modem and "smartvox Basic USB with CAPI2.0 for Win98". Then reboot to Normal mode and run Found New Hardware wizard once again.

  3. #3
    5 Star Lounger
    Join Date
    Jul 2001
    Location
    Terneuzen, Netherlands
    Posts
    895
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Device installation & INF-files

    Thanks! I'll try this out. Any change I can find this more detailed info also electronically somewhere (e.g. on TechNet?)

    Erik Jan

  4. #4
    Silver Lounger
    Join Date
    Apr 2001
    Location
    New York, New York, USA
    Posts
    2,328
    Thanks
    0
    Thanked 1 Time in 1 Post

  5. #5
    5 Star Lounger
    Join Date
    Jul 2001
    Location
    Terneuzen, Netherlands
    Posts
    895
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Device installation & INF-files

    All, I tried your suggestions and read articles you referred to. Nothing seemed to help but one-way or another it still helped me to find NEWER drivers somewhere hidden away on a site which seemed unrelated in another country... Anyway; I installed the drivers and everything works flawlessly now... Problem solved

    But... I still don't grasp what made Windows say it couldn't find the right drivers (my 'old' set files were OK -meaning: not damaged- and had worked on a previous system).
    There seems to be an ID attached to the (USB)device which should match one mentioned in the INF-file... that's what I more-or-less got... What governs this device ID and how one can read it and/or set it remains a mystery to me...

    Anyway, as said, my problem is solved! Thanks all, this is a great board eeehhh lounge <img src=/S/clapping.gif border=0 alt=clapping width=19 height=23>

    Erik Jan

Posting Permissions

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