Hi everyone,
I just wanted to give folks an update on what we’ve been able to do, and
what we’re looking at doing. Also, I want to clearly say “THANK YOU” –
the thread was a major motivating factor in helping folks to understand
the user impact.
- The HWID USB\VID_04B4&PID_8613 in submission (<>) has been
marked for un-distribution from WU. It should be pulled out in the next
24 hours.
2) We are working to remove HWID USB\VID_04B4&PID_8613 from all other
submissions that have already been submitted for WU. We’ve already
found two additional cases, so (due to logistics, verification, etc.)
the problem may not be fully resolved for a number of weeks yet.
3) We are looking for info on any other similar “generic” PnP IDs. For
example, the following are being looked at as possible candidates:
- PCI\VEN_109E&DEV_036E&SUBSYS_00000000
- PCI\VEN_109E&DEV_036E&SUBSYS_FFFFFFFF
- PCI\VEN_109E&DEV_0878&SUBSYS_00000000
4) We are considering modifying the WHQL submission process to
automatically fail when one of these “generic” PnP IDs is provided as an
INF match.
Thanks for your patience during this process. BTW, if you have any
additional “development kit” PNP IDs that you think need to be excluded,
please send me the following info:
A) Link to the manufacturer’s product page / spec sheet
B) The PNP ID that they use for development boards
I can’t guarantee anything, but I can at least pass it on to the right
folks.
Thanks,
Henry Gabryjelski
Senior Software Development Engineer
US - Windows Device Experience
Microsoft Corporation
-----Original Message-----
From: Henry Gabryjelski
Sent: Thursday, March 22, 2007 9:17 AM
To: ‘Windows System Software Devs Interest List’
Subject: RE: Issue with Vista 64-bit recognizing Cypress CY7C68013A
(FX2LP) VID 0x04B4 PID 0x8613
Hi everyone,
I’ve raised this issue to the appropriate folks internally. They seem
to understand the problem (but hadn’t heard of it). I’ll let you know
if there is any additional news.
Thanks,
Henry Gabryjelski
Senior Software Development Engineer
US - Windows Device Experience
Microsoft Corporation
-----Original Message-----
From: John Matsumoto [mailto:xxxxx@surfaceoptics.com]
Sent: Wednesday, March 21, 2007 12:28 AM
Subject: RE: Issue with Vista 64-bit recognizing Cypress CY7C68013A
(FX2LP) VID 0x04B4 PID 0x8613
Hello Gianluca,
Thanks for the advice. Unfortunately, for whatever reason, my
development
hardware causes the KWorld firmware to connect, disconnect, connect…
Because of this, devcon reports back that it cannot find the targeted
hardware. That’s the reason why I don’t see the hardware in the device
manager. For now I’m generating a README outlining Michal’s advice
(editing
the Registry). My original README was to have end-users who were
unfortunate
enough to fall into this dilemma, muck with system files and
directories,
but I think that modifying the Registry is a bit more forward. Thanks to
everyone for all the help and support.
Motz
> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:bounce-281222-
> xxxxx@lists.osr.com] On Behalf Of Gianluca Varenni
> Sent: Tuesday, March 20, 2007 3:02 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Issue with Vista 64-bit recognizing Cypress
> CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
>
>
> ----- Original Message -----
> From: “Michal Vodicka”
> To: “Windows System Software Devs Interest List”
> Sent: Tuesday, March 20, 2007 2:52 PM
> Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> CY7C68013A
> (FX2LP) VID 0x04B4 PID 0x8613
>
>
> Will “devcon update” work if you need to replace WHQL signed driver
with
> non-signed one?
>
> --GV–
> I haven’t tested it with an unsigned driver. But I’d bet it works.
> --GV–
>
>
> Next problem is there are two VID/PID pairs involved and only
> uninteresting
> one is loaded. If #1 works, manual unplug/plug or board reset will be
> necessary.
>
> --GV–
> devcon disable HWID allows you to disable any device matching the
pattern
> in
> HWID, in the same way as you would disable a disable from device
manager.
> For PCI devices it works perfectly (it’s the way I update a PCI driver
> during development: put a new binary in system32\drivers, and then
> disable/enable the device itself).
>
> Have a nice day
> GV
>
> --GV–
>
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.com]
>
>
> > ----------
> > From:
> > xxxxx@lists.osr.com[SMTP:bounce-281217-
> xxxxx@lists.osr.com]
> > on behalf of Gianluca Varenni[SMTP:xxxxx@gmail.com]
> > Reply To: Windows System Software Devs Interest List
> > Sent: Tuesday, March 20, 2007 10:38 PM
> > To: Windows System Software Devs Interest List
> > Subject: Re: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
> >
> > Can’t you use devcon?
> >
> > This procedure works for PCI devices, it should work for USB too.
> >
> > 1. devcon update “USB\VID_XXXX&PID_YYYY”
> > 2. devcon disable “USB\VID_XXXX&PID_YYYY”
> > 3. devcon enable “USB\VID_XXXX&PID_YYYY”
> >
> > Have a nice day
> > GV
> >
> >
> >
> > ----- Original Message -----
> > From: “Michal Vodicka”
> > To: “Windows System Software Devs Interest List”
> > Sent: Tuesday, March 20, 2007 1:53 PM
> > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > CY7C68013A
> > (FX2LP) VID 0x04B4 PID 0x8613
> >
> >
> > > ----------
> > > From:
> > > xxxxx@lists.osr.com[SMTP:bounce-281159-
> xxxxx@lists.osr.com]
> > > on behalf of John Matsumoto[SMTP:xxxxx@surfaceoptics.com]
> > > Reply To: Windows System Software Devs Interest List
> > > Sent: Tuesday, March 20, 2007 10:04 AM
> > > To: Windows System Software Devs Interest List
> > > Subject: RE: [ntdev] Issue with Vista 64-bit recognizing Cypress
> > > CY7C68013A (FX2LP) VID 0x04B4 PID 0x8613
> > >
> > > 1. If this is truly a Microsoft signed driver (and not a virus)
that
> is
> > > in
> > > their driver compatibility list, where do I send a request to ask
if
> > > Microsoft would please consider removing this driver from its
update
> > > site?
> > >
> > I hope the WHQL signature was really coming from MS. Which, of
course,
> > doesn’t necessarily mean it isn’t a virus
> >
> > > Our product developers and manufacturing engineers, who know
nothing
> > > about system files or registry entries, will push the
“recommended”
> > > button
> > > and I can’t seem to come up with a really easy way to load our
driver
> > > once
> > > the “recommended” path is taken. Any suggestions would be greatly
> > > appreciated.
> > >
> > We did it following way:
> >
> > - identify the firmware loader driver entry in the registry
> > (HKLM\System\CCS\Services<fw_loader_name>
> > - unplug Cypress board(s)
> > - change fw loader Start value from 3 to 4
> > - plug the board back
> > - in the Device Manager, board is marked with question mark because
OS
> has
> > problem loading driver
> > - right click, Update driver and now it is possible to manually
select
> > something else than rogue fw loader
> > - it is necessary to repeat process for every port where it was
plugged
> >
> > You can make whole process a bit easier by creating .reg file which
> > changes
> > the Start value but beware about systems where rogue fw loader was
never
> > installed. For product developers above description should be
enough,
> for
> > manufacturing engineers add screenshots and for marketing persons
(if
> > involved) create Power Point presentation
> >
> > HTH
> >
> > Best regards,
> >
> > Michal Vodicka
> > UPEK, Inc.
> > [xxxxx@upek.com, http://www.upek.com]
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer</fw_loader_name>