I was going to say, vscsi seems to work fine this side of the fence. I
recently tested it under XP SP2 on x86 and under Win2003 SP1 on x86, IA64
and AMD64, as part of our currency work. But if you have any problems, you
can email me or else our Frameworks support guy (at
xxxxx@compuware.com) and we’ll be glad to take it from there !
One thing I always do is, I only build it from a .dsp or solution that has
been generated by running src2dsp on the sources file.
I’ve been lobbying the powers that be to allow us to add a DriverStudio
Registry Scrubber to the product. That might go a long ways towards making
driver install and uninstall a bit more predictable !
Alberto.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Gary G. Little
Sent: Thursday, July 08, 2004 2:45 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Code 9 error when bus driver enumerates it’s ChildA
and ChildB drivers
as so often happens, shortly after I posted this I found the problem.
It seems ti’s more of an environmental than driver/code problem. I had been
installing and uninstalling the drivers for quite some time on that test
partition. As soon as I tried to install the suite on a fresh OS that had
never seen my driver suite installed … it worked. Crap! I hesitated to
Ghost the partition back to a fresh OS install because I have utilities and
tools installed which I use to test the driver. I have many times tiptoed
through the registry to “clean” it and consistently purged the oem files
from the INF directory, but there is a “sourdough” something that pollutes
an OS over a period of time requiring a fresh start.
That’s the wonderful world of driver writing folks! 
–
Gary G. Little
Seagate Technologies, LLC
“Gary G. Little” wrote in message news:…
> The test environment for this problem is a dual processr with 1/2 gig of
RAM
> and nearly a terabyte of Seagate SATA/PATA harddiscs under test and
booting
> from a Promise ATA controller. The OS is XP SP2/RC2. The drivers are
written
> using Compuwares DriverWorks with the bus driver based on the “vscsi”
> example, and uses the KPhysicalDevice and KBus classes for PDO/FDO
creation,
> enumeration , and management of child drivers.
>
> Once the bus driver has created it’s FDO in AddDevice, it starts the
thread
> that invalidates the bus to produce one PDO each for the child drivers,
ala
> vscsi. Thus far, having stepped through this numerous times this appears
to
> be working properly. The new DOs are indeed created and the calls to
> IRP_MN_QUERY_Xxxx IOCTLs handled properly. QUERY_ID generates proper
strings
> and returns them in IoStatus->Information with Status set to
STATUS_SUCCESS.
> The QUERY_RESOURCES IRPs are simply completed with Status unchanged.
>
> Once I’m at the desktop on a boot, the AddDeviceWizard does not run. When
I
> look at the Device Manager I see the parent driver and class has been
> created and the bus driver is functionioning properly. However, there is
an
> Unknown device and it has ChildA and ChildB defined under it. When I then
> attempt to install/update either child, it is moved under the proper
driver
> in Device Manager, but is yellow banged, telling me the driver failed
> because of Code 9, “The controlling firmware is reporting the resources
for
> the device incorrectly.” These child drivers have no resources.
>
> –
> Gary G. Little
> Seagate Technologies, LLC
>
>
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.
That “pollution” seems to have been the problem. The suite installs now,
except the driver that has genuine bug in it. A"scrubber" utility would be a
great tool.
–
Gary G. Little
Seagate Technologies, LLC
“Moreira, Alberto” wrote in message
news:xxxxx@ntdev…
> I was going to say, vscsi seems to work fine this side of the fence. I
> recently tested it under XP SP2 on x86 and under Win2003 SP1 on x86, IA64
> and AMD64, as part of our currency work. But if you have any problems, you
> can email me or else our Frameworks support guy (at
> xxxxx@compuware.com) and we’ll be glad to take it from there !
>
> One thing I always do is, I only build it from a .dsp or solution that has
> been generated by running src2dsp on the sources file.
>
> I’ve been lobbying the powers that be to allow us to add a DriverStudio
> Registry Scrubber to the product. That might go a long ways towards making
> driver install and uninstall a bit more predictable !
>
> Alberto.
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Gary G. Little
> Sent: Thursday, July 08, 2004 2:45 PM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Code 9 error when bus driver enumerates it’s ChildA
> and ChildB drivers
>
>
> as so often happens, shortly after I posted this I found the
problem.
>
> It seems ti’s more of an environmental than driver/code problem. I had
been
> installing and uninstalling the drivers for quite some time on that test
> partition. As soon as I tried to install the suite on a fresh OS that had
> never seen my driver suite installed … it worked. Crap! I hesitated to
> Ghost the partition back to a fresh OS install because I have utilities
and
> tools installed which I use to test the driver. I have many times tiptoed
> through the registry to “clean” it and consistently purged the oem files
> from the INF directory, but there is a “sourdough” something that pollutes
> an OS over a period of time requiring a fresh start.
>
> That’s the wonderful world of driver writing folks!
>
> –
> Gary G. Little
> Seagate Technologies, LLC
>
> “Gary G. Little” wrote in message news:…
> > The test environment for this problem is a dual processr with 1/2 gig of
> RAM
> > and nearly a terabyte of Seagate SATA/PATA harddiscs under test and
> booting
> > from a Promise ATA controller. The OS is XP SP2/RC2. The drivers are
> written
> > using Compuwares DriverWorks with the bus driver based on the “vscsi”
> > example, and uses the KPhysicalDevice and KBus classes for PDO/FDO
> creation,
> > enumeration , and management of child drivers.
> >
> > Once the bus driver has created it’s FDO in AddDevice, it starts the
> thread
> > that invalidates the bus to produce one PDO each for the child drivers,
> ala
> > vscsi. Thus far, having stepped through this numerous times this appears
> to
> > be working properly. The new DOs are indeed created and the calls to
> > IRP_MN_QUERY_Xxxx IOCTLs handled properly. QUERY_ID generates proper
> strings
> > and returns them in IoStatus->Information with Status set to
> STATUS_SUCCESS.
> > The QUERY_RESOURCES IRPs are simply completed with Status unchanged.
> >
> > Once I’m at the desktop on a boot, the AddDeviceWizard does not run.
When
> I
> > look at the Device Manager I see the parent driver and class has been
> > created and the bus driver is functionioning properly. However, there is
> an
> > Unknown device and it has ChildA and ChildB defined under it. When I
then
> > attempt to install/update either child, it is moved under the proper
> driver
> > in Device Manager, but is yellow banged, telling me the driver failed
> > because of Code 9, “The controlling firmware is reporting the resources
> for
> > the device incorrectly.” These child drivers have no resources.
> >
> > –
> > Gary G. Little
> > Seagate Technologies, LLC
> >
> >
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@compuware.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or
disclose
> it to anyone else. If you received it in error please notify us
immediately
> and then destroy it.
>
>
You do have a “scrubber” utility. It is called Ghost. Since they make USB
2.0 and 1394 hard drives nowadays, just make as many ghost images as you
need. It will take a while, but you can a good series. The only problem is
when you have more than what will fit into a single 2GB backup file.
Keeping the parts together can be more difficult, but you can put each
backup into a directory that has a descriptive name or a text file that
explains what is unique about it.
I finally had one installation of Windows XP that I didn’t have to replace
for almost a year. I have switched to another installation recently, but it
is getting better and I am not experimenting as much with my main system. I
use C: & D: as OS boot partitions and just modify the boot.ini as I need to.
I am waiting to restore the OS to C: until SP2 is out and seems stable. I
will then create a bootable XP with SP2 incorporated so I can get it as
clean as possible.
“Gary G. Little” wrote in message
news:xxxxx@ntdev…
> That “pollution” seems to have been the problem. The suite installs now,
> except the driver that has genuine bug in it. A"scrubber" utility would be
a
> great tool.
>
> –
> Gary G. Little
> Seagate Technologies, LLC
>
> “Moreira, Alberto” wrote in message
> news:xxxxx@ntdev…
> > I was going to say, vscsi seems to work fine this side of the fence. I
> > recently tested it under XP SP2 on x86 and under Win2003 SP1 on x86,
IA64
> > and AMD64, as part of our currency work. But if you have any problems,
you
> > can email me or else our Frameworks support guy (at
> > xxxxx@compuware.com) and we’ll be glad to take it from there !
> >
> > One thing I always do is, I only build it from a .dsp or solution that
has
> > been generated by running src2dsp on the sources file.
> >
> > I’ve been lobbying the powers that be to allow us to add a DriverStudio
> > Registry Scrubber to the product. That might go a long ways towards
making
> > driver install and uninstall a bit more predictable !
> >
> > Alberto.
> >
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of Gary G. Little
> > Sent: Thursday, July 08, 2004 2:45 PM
> > To: Windows System Software Devs Interest List
> > Subject: Re:[ntdev] Code 9 error when bus driver enumerates it’s ChildA
> > and ChildB drivers
> >
> >
> > as so often happens, shortly after I posted this I found the
> problem.
> >
> > It seems ti’s more of an environmental than driver/code problem. I had
> been
> > installing and uninstalling the drivers for quite some time on that test
> > partition. As soon as I tried to install the suite on a fresh OS that
had
> > never seen my driver suite installed … it worked. Crap! I hesitated to
> > Ghost the partition back to a fresh OS install because I have utilities
> and
> > tools installed which I use to test the driver. I have many times
tiptoed
> > through the registry to “clean” it and consistently purged the oem files
> > from the INF directory, but there is a “sourdough” something that
pollutes
> > an OS over a period of time requiring a fresh start.
> >
> > That’s the wonderful world of driver writing folks!
> >
> > –
> > Gary G. Little
> > Seagate Technologies, LLC
> >
> > “Gary G. Little” wrote in message news:…
> > > The test environment for this problem is a dual processr with 1/2 gig
of
> > RAM
> > > and nearly a terabyte of Seagate SATA/PATA harddiscs under test and
> > booting
> > > from a Promise ATA controller. The OS is XP SP2/RC2. The drivers are
> > written
> > > using Compuwares DriverWorks with the bus driver based on the “vscsi”
> > > example, and uses the KPhysicalDevice and KBus classes for PDO/FDO
> > creation,
> > > enumeration , and management of child drivers.
> > >
> > > Once the bus driver has created it’s FDO in AddDevice, it starts the
> > thread
> > > that invalidates the bus to produce one PDO each for the child
drivers,
> > ala
> > > vscsi. Thus far, having stepped through this numerous times this
appears
> > to
> > > be working properly. The new DOs are indeed created and the calls to
> > > IRP_MN_QUERY_Xxxx IOCTLs handled properly. QUERY_ID generates proper
> > strings
> > > and returns them in IoStatus->Information with Status set to
> > STATUS_SUCCESS.
> > > The QUERY_RESOURCES IRPs are simply completed with Status unchanged.
> > >
> > > Once I’m at the desktop on a boot, the AddDeviceWizard does not run.
> When
> > I
> > > look at the Device Manager I see the parent driver and class has been
> > > created and the bus driver is functionioning properly. However, there
is
> > an
> > > Unknown device and it has ChildA and ChildB defined under it. When I
> then
> > > attempt to install/update either child, it is moved under the proper
> > driver
> > > in Device Manager, but is yellow banged, telling me the driver failed
> > > because of Code 9, “The controlling firmware is reporting the
resources
> > for
> > > the device incorrectly.” These child drivers have no resources.
> > >
> > > –
> > > Gary G. Little
> > > Seagate Technologies, LLC
> > >
> > >
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@compuware.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
> >
> > The contents of this e-mail are intended for the named addressee only.
It
> > contains information that may be confidential. Unless you are the named
> > addressee or an authorized designee, you may not copy or use it, or
> disclose
> > it to anyone else. If you received it in error please notify us
> immediately
> > and then destroy it.
> >
> >
>
>
>
Yeah but … that’s a bit like killing a fly with sledge hammer though. In
this particular case I had utilities installed in an image I had NOT ghosted
yet. Yeah … dumb me … but I’m old … I forget to do things sometimes.
–
Gary G. Little
Seagate Technologies, LLC
“David J. Craig” wrote in message
news:xxxxx@ntdev…
> You do have a “scrubber” utility. It is called Ghost. Since they make
USB
> 2.0 and 1394 hard drives nowadays, just make as many ghost images as you
> need. It will take a while, but you can a good series. The only problem
is
> when you have more than what will fit into a single 2GB backup file.
> Keeping the parts together can be more difficult, but you can put each
> backup into a directory that has a descriptive name or a text file that
> explains what is unique about it.
>
> I finally had one installation of Windows XP that I didn’t have to replace
> for almost a year. I have switched to another installation recently, but
it
> is getting better and I am not experimenting as much with my main system.
I
> use C: & D: as OS boot partitions and just modify the boot.ini as I need
to.
> I am waiting to restore the OS to C: until SP2 is out and seems stable. I
> will then create a bootable XP with SP2 incorporated so I can get it as
> clean as possible.
>
> “Gary G. Little” wrote in message
> news:xxxxx@ntdev…
> > That “pollution” seems to have been the problem. The suite installs now,
> > except the driver that has genuine bug in it. A"scrubber" utility would
be
> a
> > great tool.
> >
> > –
> > Gary G. Little
> > Seagate Technologies, LLC
> >
> > “Moreira, Alberto” wrote in message
> > news:xxxxx@ntdev…
> > > I was going to say, vscsi seems to work fine this side of the fence. I
> > > recently tested it under XP SP2 on x86 and under Win2003 SP1 on x86,
> IA64
> > > and AMD64, as part of our currency work. But if you have any problems,
> you
> > > can email me or else our Frameworks support guy (at
> > > xxxxx@compuware.com) and we’ll be glad to take it from there
!
> > >
> > > One thing I always do is, I only build it from a .dsp or solution that
> has
> > > been generated by running src2dsp on the sources file.
> > >
> > > I’ve been lobbying the powers that be to allow us to add a
DriverStudio
> > > Registry Scrubber to the product. That might go a long ways towards
> making
> > > driver install and uninstall a bit more predictable !
> > >
> > > Alberto.
> > >
> > >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com
> > > [mailto:xxxxx@lists.osr.com]On Behalf Of Gary G. Little
> > > Sent: Thursday, July 08, 2004 2:45 PM
> > > To: Windows System Software Devs Interest List
> > > Subject: Re:[ntdev] Code 9 error when bus driver enumerates it’s
ChildA
> > > and ChildB drivers
> > >
> > >
> > > as so often happens, shortly after I posted this I found the
> > problem.
> > >
> > > It seems ti’s more of an environmental than driver/code problem. I had
> > been
> > > installing and uninstalling the drivers for quite some time on that
test
> > > partition. As soon as I tried to install the suite on a fresh OS that
> had
> > > never seen my driver suite installed … it worked. Crap! I hesitated
to
> > > Ghost the partition back to a fresh OS install because I have
utilities
> > and
> > > tools installed which I use to test the driver. I have many times
> tiptoed
> > > through the registry to “clean” it and consistently purged the oem
files
> > > from the INF directory, but there is a “sourdough” something that
> pollutes
> > > an OS over a period of time requiring a fresh start.
> > >
> > > That’s the wonderful world of driver writing folks!
> > >
> > > –
> > > Gary G. Little
> > > Seagate Technologies, LLC
> > >
> > > “Gary G. Little” wrote in message news:…
> > > > The test environment for this problem is a dual processr with 1/2 gi
g
> of
> > > RAM
> > > > and nearly a terabyte of Seagate SATA/PATA harddiscs under test and
> > > booting
> > > > from a Promise ATA controller. The OS is XP SP2/RC2. The drivers are
> > > written
> > > > using Compuwares DriverWorks with the bus driver based on the
“vscsi”
> > > > example, and uses the KPhysicalDevice and KBus classes for PDO/FDO
> > > creation,
> > > > enumeration , and management of child drivers.
> > > >
> > > > Once the bus driver has created it’s FDO in AddDevice, it starts the
> > > thread
> > > > that invalidates the bus to produce one PDO each for the child
> drivers,
> > > ala
> > > > vscsi. Thus far, having stepped through this numerous times this
> appears
> > > to
> > > > be working properly. The new DOs are indeed created and the calls to
> > > > IRP_MN_QUERY_Xxxx IOCTLs handled properly. QUERY_ID generates proper
> > > strings
> > > > and returns them in IoStatus->Information with Status set to
> > > STATUS_SUCCESS.
> > > > The QUERY_RESOURCES IRPs are simply completed with Status unchanged.
> > > >
> > > > Once I’m at the desktop on a boot, the AddDeviceWizard does not run.
> > When
> > > I
> > > > look at the Device Manager I see the parent driver and class has
been
> > > > created and the bus driver is functionioning properly. However,
there
> is
> > > an
> > > > Unknown device and it has ChildA and ChildB defined under it. When
I
> > then
> > > > attempt to install/update either child, it is moved under the proper
> > > driver
> > > > in Device Manager, but is yellow banged, telling me the driver
failed
> > > > because of Code 9, “The controlling firmware is reporting the
> resources
> > > for
> > > > the device incorrectly.” These child drivers have no resources.
> > > >
> > > > –
> > > > Gary G. Little
> > > > Seagate Technologies, LLC
> > > >
> > > >
> > >
> > >
> > >
> > > —
> > > Questions? First check the Kernel Driver FAQ at
> > > http://www.osronline.com/article.cfm?id=256
> > >
> > > You are currently subscribed to ntdev as:
xxxxx@compuware.com
> > > To unsubscribe send a blank email to xxxxx@lists.osr.com
> > >
> > >
> > >
> > > The contents of this e-mail are intended for the named addressee only.
> It
> > > contains information that may be confidential. Unless you are the
named
> > > addressee or an authorized designee, you may not copy or use it, or
> > disclose
> > > it to anyone else. If you received it in error please notify us
> > immediately
> > > and then destroy it.
> > >
> > >
> >
> >
> >
>
>
>