Help to install drivers

[meb]

On 06/22/2009 06:44 AM, 1Adata wrote:
> I have uninstalled the USBXpress development kit (which is highly
> inconvenient application and seems does not support win 98 though they claim
> it does). I removed all drivers which USBXpress has left in C:\WINDOWS\INF
> and C:\WINDOWS\SYSTEM directory (though correct uninstaller must delete
> these files during uninstall, but it does not).
> But nothing has changed, windows does not show "Add new hardware wizard"
> when connect device to usb.
>
> ---------------

Your continued resistance to follow the readme, suggestions here, and
address the device's own support forums seems certain to cause a failure.

1. *IF you had the device attached* [as required] when installing the
software there would not necessarily be any "Add New Hardware" wizard.
It may only appear under the USD/B in Device Manager per prior advise
and readme.

1a. *IF* it required a re-boot to change or add system files or modify
registry and you failed to do so, you will NOT have a correct installation.

2. *IF* you did NOT have the device attached when attempting the driver
installation it will not properly install the drivers per prior advise
and readme.

3. *IF* you also did not set the PID, then you will not have a correct
installation per prior advise and readme.

You apparently keep expecting it to follow what YOU want it to do,
rather than what needs to be done.
YOU don't control device installations, the OS and installer do. This
is partially WHY the newer MS OSs have made these activities either
unnecessary [universal drivers - PNP] or have demanded the manufacturers
COMPLETELY CONTROL installation taking away user interaction [users can
not be relied upon to understand the most basic requirements, or
understand manuals and readmes].

Try the support forums for the device, perhaps you can find someone
who speaks your native language...

>
>
>
> "MEB"<MEB-not-here@hotmail.com> wrote in message
> news:uC8%23Smt8JHA.1252@TK2MSFTNGP04.phx.gbl...
>> On 06/21/2009 08:15 PM, 1Adata wrote:
>>> Problem is now when connect device, windows does not show "Add new
> hardware
>>> dialog" anymore. I tried install driver via 'Add new hardware wizard' in
>>> Control panel manually> Update driver, but it can no find driver after
> I
>>> specified the folder where it located.
>>>
>>> ------
>> Because its not an INF installation [that came from the NT ONLY
>> attempted installation], its from the *executable installer*....
>> A present the device doesn't exist, nor will anything be shown [except
>> unknown driver or can not find driver]. You *DON'T* use "Add New
>> Hardware", and close it if automatically opened when booting [but not if
>> opened *BY the installer* {including after a re-boot after installation}].
>>
>> The only potential MANUAL way is to expand [if possible] the
>> installation exe file.
>> *** That however, is *NOT* what you need to use for installation as the
>> device MAY require other changes, that the *installer* will determine
>> *DURING* installation...
>>
>> THAT is what the first few lines of the readme were trying to explain
>> to you...
>> >>>>>- Install the device as instructed in your CP210x Evaluation Kit
>> >>>>> along with the Virtual Serial Port Drivers.
>> >>>>>- Run PreInstaller.exe included in this USBXpress package. Click
>> >>>>> 'Continue Anyway' if prompted.
>>
>> IF and only *IF* the installer just expands the file into an
>> installation folder/directory THEN direct the hardware wizard to that
>> folder, otherwise that should be automatically taken care of by the
>> installer.
>>
>> THIS IS the standard operating procedure [SOP] for NORMAL installation
>> of devices... when confronting an executable either check for expansion
>> capabilities [zip or otherwise] OR RUN the executable.
>>
>>>
>>> "MEB"<MEB-not-here@hotmail.com> wrote in message
>>> news:O6HYeyr8JHA.4172@TK2MSFTNGP02.phx.gbl...
>>>> On 06/21/2009 09:56 AM, 1Adata wrote:
>>>>> I find two files related to CP210x:
>>>>> Silicon Laboratoriesslabbus.inf in C:\WINDOWS\INF\Other
>>>>> and
>>>>> Drvidx.bin in C:\WINDOWS\INF, this file contains info about installed
>>> device
>>>>> at the end of file.
>>>>> I find also one registry key
>>>>> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\USB\0017]
>>>>> I removed just .inf file and registry key.
>>>>>
>>>>> The device is simple RFID Reader, I already installed it on win XP,
> now
>>> just
>>>>> want install on win 98SE.
>>>>> The Reader is USB bridge to COM way. Installing the driver will create
> a
>>>>> virtual COM port. There are no additional instructions how to install
>>> driver
>>>>> for win 98. In manufacturer's website specified that device support
>>> Windows
>>>>> 98\2000\XP\NT\ME\Vista, but they only have CP210x Windows Driver v4.40
>>> for
>>>>> NT systems available for download on website.
>>>>> I read the USBXpress Development Kit v2.42 Readme, but they
> instructions
>>> so
>>>>> vague, it's difficult to understand how to install that driver.
>>>>>
>>>>> --------
>>>>
> https://www.silabs.com/support/knowledg ... dgeBase%3E
> https://www.silabs.com/support/forums/P ... CForums%3E
>>>> https://www.silabs.com/products/mcu/Pag ... Notes.aspx
>>>>
>>>> Obviously I can't supply much more unless I purchase the device,
> which
>>>> is beyond the intent of this forum... try the actual support forums and
>>>> information links...
>>>>
>>>>
>>>>
>>>>>
>>>>> "MEB"<MEB-not-here@hotmail.com> wrote in message
>>>>> news:%23hhMv1h8JHA.5704@TK2MSFTNGP03.phx.gbl...
>>>>>> On 06/20/2009 05:10 PM, 1Adata wrote:
>>>>>>> well, I find no drivers installed in windows system directory.
>>>>>> The directory/folder to check is/was the {drive}:\%windir%\INF
> which
>>>>>> is a hidden folder, you must have "Show all files" and "Do not hide
>>>>>> known file extensions" set [folder/View Options] to see the folder.
>>>>>> Use Search/Find "CP210*" within the folder to check for any
> previous
>>>>>> installation attempts.
>>>>>> I previously explained HOW to remove any left over installed
> files
>>> and
>>>>>> other from previous installation attempts.
>>>>>> The REASON to check for improper INF files is to avoid doubled
>>> drivers
>>>>>> and/or information which may conflict or be invalid.
>>>>>>
>>>>>>> I installed the USBXpress development kit, it place all files in
>>>>>>> C:\SiLabs\MCU\USBXpress, without placing any shortcuts.
>>>>>>> So its not fully clear how to install drivers? Some steps in Readme
>>> file
>>>>> is
>>>>>>> not clear: what meant step 2 - should I first attach USB device,
> then
>>>>> run
>>>>>>> PreInstaller.exe(step 3)? Step 4 not clear: where to change this PID
>>> to
>>>>>>> 0xEA61 ??
>>>>>>>
>>>>>>> --------
>>>>>>> Installing the Driver [Relevant Devices: CP2101/2/3]:
>>>>>> This presumes you actually have a 1, 2, or 3 version...
>>>>>>
>>>>>>> Operating Systems: Windows 98SE/2000/XP
>>>>>>>
>>>>>>> - This procedure assumes that you have a CP210x device with
> factory
>>>>>>> VID (0x10C4) and PID (0xEA60).
>>>>>> This is the referenced PID and VID. You only need to follow the
>>> below
>>>>>> unless you are programming {etc.} using this device, see the manual
> for
>>>>>> full information..
>>>>>> Device needs to be hooked-up {per below}, *HOWEVER* I highly
>>> recommend
>>>>>> downloading the manual and reading first.
>>>>>>
>>>>>>> - Install the device as instructed in your CP210x Evaluation Kit
>>>>>>> along with the Virtual Serial Port Drivers.
>>>>>>> - Run PreInstaller.exe included in this USBXpress package. Click
>>>>>>> 'Continue Anyway' if prompted.
>>>>>> This is the driver prep package. Note any information shown...
>>>>>>
>>>>>>> - Use the CP210xSetIDs.exe program to change the PID to 0xEA61.
>>>>>> This program is used to manually set/check the actual PID for the
>>>>>> device.. look at the supplied *manual* [available from the same link
> if
>>>>>> not included]...
>>>>>>
>>>>>>> - When Windows brings up the the "New Hardware" wizard, choose
>>>>>>> the default option marked "Recommended" and click 'Next'.
>>>>>>> - Click 'Continue Anyway' if prompted. Click 'Finish' to
> complete
>>>>>>> the installation.
>>>>>>> - To verify, check in "Device Manager" under 'Universal Serial
> Bus
>>>>>>> Controllers'. There should be an entry for 'USBXpress Device'.
>>>>>>> --------------
>>>>>> This describes the normal pop-up device installation window, a
>>>>>> potential question and the answer "continue anyway", and verifies
>>>>>> installation using Control Panel> Device Manager> Universal
> Serial
>>>>>> Devices> > HUB/Controller> sub-entry = USBExpress Device - on
> one of
>>>>>> the branches.
>>>>>>
>>>>>> Check the identifier and for the device [using the above CP>
> DM>
>>>>>> USD/B>] and use the cp210xsetids again if necessary AFTER a re-boot.
> IF
>>>>>> changed, RUN "scanreg" to save the registry modification; re-boot;
> and
>>>>>> check again.
>>>>>>
>>>>>> HOPEFULLY you will not find you have a driver conflict due to the
>>>>>> prior installation attempts. IF SO and you didn't follow the advise
> to
>>>>>> check for prior failed installation files, un-install the new driver,
>>>>>> and use the prior manual check for files and removals which I
>>> previously
>>>>>> outlined...
>>>>>>
>>>>>> What are you going to use this device for???
>>>>>>
>>>>>>> "MEB"<MEB-not-here@hotmail.com> wrote in message
>>>>>>> news:eeeF2Pc8JHA.4608@TK2MSFTNGP05.phx.gbl...
>>>>>>>> On 06/20/2009 12:19 PM, 1Adata wrote:
>>>>>>>>> I managed to install drivers via "Add new hardware Wizard", but
>>> device
>>>>>>>>> status not working properly:
>>>>>>>>>
>>>>>>>>> http://img170.imageshack.us/img170/2553/device.jpg
>>>>>>>>> http://img170.imageshack.us/img170/569/device2.jpg
>>>>>>>>> http://img170.imageshack.us/img170/9016/device3.jpg
>>>>>>>>>
>>>>>>>>> I tried re-install via Update Driver button, but not help.
>>>>>>>>>
>>>>>>>> The "drivers" you are attempting to install are for NT based
>>>>> systems,
>>>>>>>> you need the development kit which also apparently includes a 9X
>>>>> driver,
>>>>>>>> which I previously linked to.
>>>>>>>>
>>>>>>>> *IF* you were familiar with modifications of existing NT
> drivers
>>> for
>>>>>>>> 9X usage you MIGHT be able to force a usage though likely not, as
>>> they
>>>>>>>> are designed to work in conjunction with HAL and other aspects of
> the
>>>>> NT
>>>>>>>> environment...
>>>>>>>>
>>>>>>>> MEB
>>>> MEB
>>>>
>> MEB
>


--
~
--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Diagnostics, Security, Networking
http://peoplescounsel.org
The *REAL WORLD* of Law, Justice, and Government
_______

[1adata]

Ok, I got drivers for Windows 98 and managed to install it, device works
properly now.
Since "Add new hardware wizard" was not shown after attaching device, I went
to System Properties, Device manager, found this device and use Update
driver button, this launched Add new hardware wizard, then specified path to
drivers. But device still not worked. So I rebooted PC, and after rebooting
system popup this 'Add new hardware wizard ', so i went through the same
steps still twice - so total it required three times to install. This point
not fully clear, since there was specified that process(Add new hardware
dialog) repeats twice.
The bad thing is I forgot to run first InCtrl5 utility to make system
snapshot, so next time i need search for location of all this drivers when I
want to remove it.

Thank you.

----------


> ---------------
>
>
>
> "MEB" <MEB-not-here@hotmail.com> wrote in message
> news:uC8%23Smt8JHA.1252@TK2MSFTNGP04.phx.gbl...
> > On 06/21/2009 08:15 PM, 1Adata wrote:
> > > Problem is now when connect device, windows does not show "Add new
> hardware
> > > dialog" anymore. I tried install driver via 'Add new hardware wizard'
in
> > > Control panel manually> Update driver, but it can no find driver
after
> I
> > > specified the folder where it located.
> > >
> > > ------
> >
> > Because its not an INF installation [that came from the NT ONLY
> > attempted installation], its from the *executable installer*....
> > A present the device doesn't exist, nor will anything be shown [except
> > unknown driver or can not find driver]. You *DON'T* use "Add New
> > Hardware", and close it if automatically opened when booting [but not if
> > opened *BY the installer* {including after a re-boot after
installation}].
> >
> > The only potential MANUAL way is to expand [if possible] the
> > installation exe file.
> > *** That however, is *NOT* what you need to use for installation as the
> > device MAY require other changes, that the *installer* will determine
> > *DURING* installation...
> >
> > THAT is what the first few lines of the readme were trying to explain
> > to you...
> > >>>>>- Install the device as instructed in your CP210x Evaluation Kit
> > >>>>> along with the Virtual Serial Port Drivers.
> > >>>>>- Run PreInstaller.exe included in this USBXpress package. Click
> > >>>>> 'Continue Anyway' if prompted.
> >
> > IF and only *IF* the installer just expands the file into an
> > installation folder/directory THEN direct the hardware wizard to that
> > folder, otherwise that should be automatically taken care of by the
> > installer.
> >
> > THIS IS the standard operating procedure [SOP] for NORMAL installation
> > of devices... when confronting an executable either check for expansion
> > capabilities [zip or otherwise] OR RUN the executable.
> >
> > >
> > >
> > > "MEB"<MEB-not-here@hotmail.com> wrote in message
> > > news:O6HYeyr8JHA.4172@TK2MSFTNGP02.phx.gbl...
> > >> On 06/21/2009 09:56 AM, 1Adata wrote:
> > >>> I find two files related to CP210x:
> > >>> Silicon Laboratoriesslabbus.inf in C:\WINDOWS\INF\Other
> > >>> and
> > >>> Drvidx.bin in C:\WINDOWS\INF, this file contains info about
installed
> > > device
> > >>> at the end of file.
> > >>> I find also one registry key
> > >>>
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\USB\0017]
> > >>> I removed just .inf file and registry key.
> > >>>
> > >>> The device is simple RFID Reader, I already installed it on win XP,
> now
> > > just
> > >>> want install on win 98SE.
> > >>> The Reader is USB bridge to COM way. Installing the driver will
create
> a
> > >>> virtual COM port. There are no additional instructions how to
install
> > > driver
> > >>> for win 98. In manufacturer's website specified that device support
> > > Windows
> > >>> 98\2000\XP\NT\ME\Vista, but they only have CP210x Windows Driver
v4.40
> > > for
> > >>> NT systems available for download on website.
> > >>> I read the USBXpress Development Kit v2.42 Readme, but they
> instructions
> > > so
> > >>> vague, it's difficult to understand how to install that driver.
> > >>>
> > >>> --------
> > >>
> > >>
> > >
>
https://www.silabs.com/support/knowledg ... dgeBase%3E
> > >>
> > >
>
https://www.silabs.com/support/forums/P ... CForums%3E
> > >> https://www.silabs.com/products/mcu/Pag ... Notes.aspx
> > >>
> > >> Obviously I can't supply much more unless I purchase the device,
> which
> > >> is beyond the intent of this forum... try the actual support forums
and
> > >> information links...
> > >>
> > >>
> > >>
> > >>>
> > >>>
> > >>> "MEB"<MEB-not-here@hotmail.com> wrote in message
> > >>> news:%23hhMv1h8JHA.5704@TK2MSFTNGP03.phx.gbl...
> > >>>> On 06/20/2009 05:10 PM, 1Adata wrote:
> > >>>>> well, I find no drivers installed in windows system directory.
> > >>>> The directory/folder to check is/was the {drive}:\%windir%\INF
> which
> > >>>> is a hidden folder, you must have "Show all files" and "Do not hide
> > >>>> known file extensions" set [folder/View Options] to see the folder.
> > >>>> Use Search/Find "CP210*" within the folder to check for any
> previous
> > >>>> installation attempts.
> > >>>> I previously explained HOW to remove any left over installed
> files
> > > and
> > >>>> other from previous installation attempts.
> > >>>> The REASON to check for improper INF files is to avoid doubled
> > > drivers
> > >>>> and/or information which may conflict or be invalid.
> > >>>>
> > >>>>> I installed the USBXpress development kit, it place all files in
> > >>>>> C:\SiLabs\MCU\USBXpress, without placing any shortcuts.
> > >>>>> So its not fully clear how to install drivers? Some steps in
Readme
> > > file
> > >>> is
> > >>>>> not clear: what meant step 2 - should I first attach USB device,
> then
> > >>> run
> > >>>>> PreInstaller.exe(step 3)? Step 4 not clear: where to change this P
ID
> > > to
> > >>>>> 0xEA61 ??
> > >>>>>
> > >>>>> --------
> > >>>>> Installing the Driver [Relevant Devices: CP2101/2/3]:
> > >>>> This presumes you actually have a 1, 2, or 3 version...
> > >>>>
> > >>>>> Operating Systems: Windows 98SE/2000/XP
> > >>>>>
> > >>>>> - This procedure assumes that you have a CP210x device with
> factory
> > >>>>> VID (0x10C4) and PID (0xEA60).
> > >>>> This is the referenced PID and VID. You only need to follow the
> > > below
> > >>>> unless you are programming {etc.} using this device, see the manual
> for
> > >>>> full information..
> > >>>> Device needs to be hooked-up {per below}, *HOWEVER* I highly
> > > recommend
> > >>>> downloading the manual and reading first.
> > >>>>
> > >>>>> - Install the device as instructed in your CP210x Evaluation
Kit
> > >>>>> along with the Virtual Serial Port Drivers.
> > >>>>> - Run PreInstaller.exe included in this USBXpress package.
Click
> > >>>>> 'Continue Anyway' if prompted.
> > >>>> This is the driver prep package. Note any information shown...
> > >>>>
> > >>>>> - Use the CP210xSetIDs.exe program to change the PID to
0xEA61.
> > >>>> This program is used to manually set/check the actual PID for
the
> > >>>> device.. look at the supplied *manual* [available from the same
link
> if
> > >>>> not included]...
> > >>>>
> > >>>>> - When Windows brings up the the "New Hardware" wizard, choose
> > >>>>> the default option marked "Recommended" and click 'Next'.
> > >>>>> - Click 'Continue Anyway' if prompted. Click 'Finish' to
> complete
> > >>>>> the installation.
> > >>>>> - To verify, check in "Device Manager" under 'Universal Serial
> Bus
> > >>>>> Controllers'. There should be an entry for 'USBXpress Device'.
> > >>>>> --------------
> > >>>> This describes the normal pop-up device installation window, a
> > >>>> potential question and the answer "continue anyway", and verifies
> > >>>> installation using Control Panel> Device Manager> Universal
> Serial
> > >>>> Devices> > HUB/Controller> sub-entry = USBExpress Device - on
> one of
> > >>>> the branches.
> > >>>>
> > >>>> Check the identifier and for the device [using the above CP>
> DM>
> > >>>> USD/B>] and use the cp210xsetids again if necessary AFTER a
re-boot.
> IF
> > >>>> changed, RUN "scanreg" to save the registry modification; re-boot;
> and
> > >>>> check again.
> > >>>>
> > >>>> HOPEFULLY you will not find you have a driver conflict due to
the
> > >>>> prior installation attempts. IF SO and you didn't follow the advise
> to
> > >>>> check for prior failed installation files, un-install the new
driver,
> > >>>> and use the prior manual check for files and removals which I
> > > previously
> > >>>> outlined...
> > >>>>
> > >>>> What are you going to use this device for???
> > >>>>
> > >>>>> "MEB"<MEB-not-here@hotmail.com> wrote in message
> > >>>>> news:eeeF2Pc8JHA.4608@TK2MSFTNGP05.phx.gbl...
> > >>>>>> On 06/20/2009 12:19 PM, 1Adata wrote:
> > >>>>>>> I managed to install drivers via "Add new hardware Wizard", but
> > > device
> > >>>>>>> status not working properly:
> > >>>>>>>
> > >>>>>>> http://img170.imageshack.us/img170/2553/device.jpg
> > >>>>>>> http://img170.imageshack.us/img170/569/device2.jpg
> > >>>>>>> http://img170.imageshack.us/img170/9016/device3.jpg
> > >>>>>>>
> > >>>>>>> I tried re-install via Update Driver button, but not help.
> > >>>>>>>
> > >>>>>> The "drivers" you are attempting to install are for NT based
> > >>> systems,
> > >>>>>> you need the development kit which also apparently includes a 9X
> > >>> driver,
> > >>>>>> which I previously linked to.
> > >>>>>>
> > >>>>>> *IF* you were familiar with modifications of existing NT
> drivers
> > > for
> > >>>>>> 9X usage you MIGHT be able to force a usage though likely not, as
> > > they
> > >>>>>> are designed to work in conjunction with HAL and other aspects of
> the
> > >>> NT
> > >>>>>> environment...
> > >>>>>>
> > >>>>>> --
> > >>>>>> ~
> > >>>>>> --
> > >>>>>> MEB
> > >> MEB
> > >>
> > >
> >
> >
> > --
> > ~
> > --
> > MEB
> > http://peoplescounsel.org/ref/windows-main.htm
> > Windows Diagnostics, Security, Networking
> > http://peoplescounsel.org
> > The *REAL WORLD* of Law, Justice, and Government
> > _______
> >
> >
>

[meb]

On 06/22/2009 01:10 PM, 1Adata wrote:
> Ok, I got drivers for Windows 98 and managed to install it, device works
> properly now.
> Since "Add new hardware wizard" was not shown after attaching device, I went
> to System Properties, Device manager, found this device and use Update
> driver button, this launched Add new hardware wizard, then specified path to
> drivers. But device still not worked. So I rebooted PC, and after rebooting
> system popup this 'Add new hardware wizard ', so i went through the same
> steps still twice - so total it required three times to install. This point
> not fully clear, since there was specified that process(Add new hardware
> dialog) repeats twice.
> The bad thing is I forgot to run first InCtrl5 utility to make system
> snapshot, so next time i need search for location of all this drivers when I
> want to remove it.
>
> Thank you.
>
> ----------
>

Glad you got it installed and running properly. Thanks for posting back
with the results.

>
>> ---------------
>>
>>
>>
>> "MEB"<MEB-not-here@hotmail.com> wrote in message
>> news:uC8%23Smt8JHA.1252@TK2MSFTNGP04.phx.gbl...
>>> On 06/21/2009 08:15 PM, 1Adata wrote:
>>>> Problem is now when connect device, windows does not show "Add new
>> hardware
>>>> dialog" anymore. I tried install driver via 'Add new hardware wizard'
> in
>>>> Control panel manually> Update driver, but it can no find driver
> after
>> I
>>>> specified the folder where it located.
>>>>
>>>> ------
>>> Because its not an INF installation [that came from the NT ONLY
>>> attempted installation], its from the *executable installer*....
>>> A present the device doesn't exist, nor will anything be shown [except
>>> unknown driver or can not find driver]. You *DON'T* use "Add New
>>> Hardware", and close it if automatically opened when booting [but not if
>>> opened *BY the installer* {including after a re-boot after
> installation}].
>>> The only potential MANUAL way is to expand [if possible] the
>>> installation exe file.
>>> *** That however, is *NOT* what you need to use for installation as the
>>> device MAY require other changes, that the *installer* will determine
>>> *DURING* installation...
>>>
>>> THAT is what the first few lines of the readme were trying to explain
>>> to you...
>>> >>>>>- Install the device as instructed in your CP210x Evaluation Kit
>>> >>>>> along with the Virtual Serial Port Drivers.
>>> >>>>>- Run PreInstaller.exe included in this USBXpress package. Click
>>> >>>>> 'Continue Anyway' if prompted.
>>>
>>> IF and only *IF* the installer just expands the file into an
>>> installation folder/directory THEN direct the hardware wizard to that
>>> folder, otherwise that should be automatically taken care of by the
>>> installer.
>>>
>>> THIS IS the standard operating procedure [SOP] for NORMAL installation
>>> of devices... when confronting an executable either check for expansion
>>> capabilities [zip or otherwise] OR RUN the executable.
>>>
>>>>
>>>> "MEB"<MEB-not-here@hotmail.com> wrote in message
>>>> news:O6HYeyr8JHA.4172@TK2MSFTNGP02.phx.gbl...
>>>>> On 06/21/2009 09:56 AM, 1Adata wrote:
>>>>>> I find two files related to CP210x:
>>>>>> Silicon Laboratoriesslabbus.inf in C:\WINDOWS\INF\Other
>>>>>> and
>>>>>> Drvidx.bin in C:\WINDOWS\INF, this file contains info about
> installed
>>>> device
>>>>>> at the end of file.
>>>>>> I find also one registry key
>>>>>>
> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\USB\0017]
>>>>>> I removed just .inf file and registry key.
>>>>>>
>>>>>> The device is simple RFID Reader, I already installed it on win XP,
>> now
>>>> just
>>>>>> want install on win 98SE.
>>>>>> The Reader is USB bridge to COM way. Installing the driver will
> create
>> a
>>>>>> virtual COM port. There are no additional instructions how to
> install
>>>> driver
>>>>>> for win 98. In manufacturer's website specified that device support
>>>> Windows
>>>>>> 98\2000\XP\NT\ME\Vista, but they only have CP210x Windows Driver
> v4.40
>>>> for
>>>>>> NT systems available for download on website.
>>>>>> I read the USBXpress Development Kit v2.42 Readme, but they
>> instructions
>>>> so
>>>>>> vague, it's difficult to understand how to install that driver.
>>>>>>
>>>>>> --------
>>>>>
> https://www.silabs.com/support/knowledg ... dgeBase%3E
> https://www.silabs.com/support/forums/P ... CForums%3E
>>>>> https://www.silabs.com/products/mcu/Pag ... Notes.aspx
>>>>>
>>>>> Obviously I can't supply much more unless I purchase the device,
>> which
>>>>> is beyond the intent of this forum... try the actual support forums
> and
>>>>> information links...
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> "MEB"<MEB-not-here@hotmail.com> wrote in message
>>>>>> news:%23hhMv1h8JHA.5704@TK2MSFTNGP03.phx.gbl...
>>>>>>> On 06/20/2009 05:10 PM, 1Adata wrote:
>>>>>>>> well, I find no drivers installed in windows system directory.
>>>>>>> The directory/folder to check is/was the {drive}:\%windir%\INF
>> which
>>>>>>> is a hidden folder, you must have "Show all files" and "Do not hide
>>>>>>> known file extensions" set [folder/View Options] to see the folder.
>>>>>>> Use Search/Find "CP210*" within the folder to check for any
>> previous
>>>>>>> installation attempts.
>>>>>>> I previously explained HOW to remove any left over installed
>> files
>>>> and
>>>>>>> other from previous installation attempts.
>>>>>>> The REASON to check for improper INF files is to avoid doubled
>>>> drivers
>>>>>>> and/or information which may conflict or be invalid.
>>>>>>>
>>>>>>>> I installed the USBXpress development kit, it place all files in
>>>>>>>> C:\SiLabs\MCU\USBXpress, without placing any shortcuts.
>>>>>>>> So its not fully clear how to install drivers? Some steps in
> Readme
>>>> file
>>>>>> is
>>>>>>>> not clear: what meant step 2 - should I first attach USB device,
>> then
>>>>>> run
>>>>>>>> PreInstaller.exe(step 3)? Step 4 not clear: where to change this P
> ID
>>>> to
>>>>>>>> 0xEA61 ??
>>>>>>>>
>>>>>>>> --------
>>>>>>>> Installing the Driver [Relevant Devices: CP2101/2/3]:
>>>>>>> This presumes you actually have a 1, 2, or 3 version...
>>>>>>>
>>>>>>>> Operating Systems: Windows 98SE/2000/XP
>>>>>>>>
>>>>>>>> - This procedure assumes that you have a CP210x device with
>> factory
>>>>>>>> VID (0x10C4) and PID (0xEA60).
>>>>>>> This is the referenced PID and VID. You only need to follow the
>>>> below
>>>>>>> unless you are programming {etc.} using this device, see the manual
>> for
>>>>>>> full information..
>>>>>>> Device needs to be hooked-up {per below}, *HOWEVER* I highly
>>>> recommend
>>>>>>> downloading the manual and reading first.
>>>>>>>
>>>>>>>> - Install the device as instructed in your CP210x Evaluation
> Kit
>>>>>>>> along with the Virtual Serial Port Drivers.
>>>>>>>> - Run PreInstaller.exe included in this USBXpress package.
> Click
>>>>>>>> 'Continue Anyway' if prompted.
>>>>>>> This is the driver prep package. Note any information shown...
>>>>>>>
>>>>>>>> - Use the CP210xSetIDs.exe program to change the PID to
> 0xEA61.
>>>>>>> This program is used to manually set/check the actual PID for
> the
>>>>>>> device.. look at the supplied *manual* [available from the same
> link
>> if
>>>>>>> not included]...
>>>>>>>
>>>>>>>> - When Windows brings up the the "New Hardware" wizard, choose
>>>>>>>> the default option marked "Recommended" and click 'Next'.
>>>>>>>> - Click 'Continue Anyway' if prompted. Click 'Finish' to
>> complete
>>>>>>>> the installation.
>>>>>>>> - To verify, check in "Device Manager" under 'Universal Serial
>> Bus
>>>>>>>> Controllers'. There should be an entry for 'USBXpress Device'.
>>>>>>>> --------------
>>>>>>> This describes the normal pop-up device installation window, a
>>>>>>> potential question and the answer "continue anyway", and verifies
>>>>>>> installation using Control Panel> Device Manager> Universal
>> Serial
>>>>>>> Devices> > HUB/Controller> sub-entry = USBExpress Device - on
>> one of
>>>>>>> the branches.
>>>>>>>
>>>>>>> Check the identifier and for the device [using the above CP>
>> DM>
>>>>>>> USD/B>] and use the cp210xsetids again if necessary AFTER a
> re-boot.
>> IF
>>>>>>> changed, RUN "scanreg" to save the registry modification; re-boot;
>> and
>>>>>>> check again.
>>>>>>>
>>>>>>> HOPEFULLY you will not find you have a driver conflict due to
> the
>>>>>>> prior installation attempts. IF SO and you didn't follow the advise
>> to
>>>>>>> check for prior failed installation files, un-install the new
> driver,
>>>>>>> and use the prior manual check for files and removals which I
>>>> previously
>>>>>>> outlined...
>>>>>>>
>>>>>>> What are you going to use this device for???
>>>>>>>
>>>>>>>> "MEB"<MEB-not-here@hotmail.com> wrote in message
>>>>>>>> news:eeeF2Pc8JHA.4608@TK2MSFTNGP05.phx.gbl...
>>>>>>>>> On 06/20/2009 12:19 PM, 1Adata wrote:
>>>>>>>>>> I managed to install drivers via "Add new hardware Wizard", but
>>>> device
>>>>>>>>>> status not working properly:
>>>>>>>>>>
>>>>>>>>>> http://img170.imageshack.us/img170/2553/device.jpg
>>>>>>>>>> http://img170.imageshack.us/img170/569/device2.jpg
>>>>>>>>>> http://img170.imageshack.us/img170/9016/device3.jpg
>>>>>>>>>>
>>>>>>>>>> I tried re-install via Update Driver button, but not help.
>>>>>>>>>>
>>>>>>>>> The "drivers" you are attempting to install are for NT based
>>>>>> systems,
>>>>>>>>> you need the development kit which also apparently includes a 9X
>>>>>> driver,
>>>>>>>>> which I previously linked to.
>>>>>>>>>
>>>>>>>>> *IF* you were familiar with modifications of existing NT
>> drivers
>>>> for
>>>>>>>>> 9X usage you MIGHT be able to force a usage though likely not, as
>>>> they
>>>>>>>>> are designed to work in conjunction with HAL and other aspects of
>> the
>>>>>> NT
>>>>>>>>> environment...
>>>>>>>>>
>>>>>>>>> MEB
>>>>> MEB
>>>>>
>>>
>>> --
>>> ~
>>> --
>>> MEB


--
~
--
MEB
http://peoplescounsel.org/ref/windows-main.htm
Windows Diagnostics, Security, Networking
http://peoplescounsel.org
The *REAL WORLD* of Law, Justice, and Government
_______