Device Manager - Disable->Enable = (Code 39)

I have a SCSI MiniPort that was working fine on WinXP SP2 although
when I updated SP2 with the latest critical patches I started seeing
this problem.

In the device manager I can see my SCSI Controller and one disk
which is hanging off it. If I disable the SCSI controller in device
manager the disk goes away as expected. Although if I re-enable the
SCSI adapter the disk returns but with a bang and Code 39. (Rebooting
the system once in this state resolves the problem. Also rebooting in
between the disable and enable works around the issue. Tracing the
driver its running fine. No errors.)

I ran across a couple kb article which looks like an exact match
although it only seems to apply to CD/DVDs. And there workarounds
don't match up for a disk device.

Has anyone encountered this and do you know of solutions /
workarounds?

Gary
Thu Dec 06 11:00:04 PST 2007

Have you stepped into your miniport to see what is happening? Is it failing
in DriverEntry or in the HW callback functions?

--
The personal opinion of
Gary G. Little

"Dave" <david@weibeltech.com> wrote in message
news:baf6e9ff-0d71-4087-af10-7ef7053fbe70@y43g2000hsy.googlegroups.com...
>I have a SCSI MiniPort that was working fine on WinXP SP2 although
> when I updated SP2 with the latest critical patches I started seeing
> this problem.
>
> In the device manager I can see my SCSI Controller and one disk
> which is hanging off it. If I disable the SCSI controller in device
> manager the disk goes away as expected. Although if I re-enable the
> SCSI adapter the disk returns but with a bang and Code 39. (Rebooting
> the system once in this state resolves the problem. Also rebooting in
> between the disable and enable works around the issue. Tracing the
> driver its running fine. No errors.)
>
> I ran across a couple kb article which looks like an exact match
> although it only seems to apply to CD/DVDs. And there workarounds
> don't match up for a disk device.
>
> Has anyone encountered this and do you know of solutions /
> workarounds?

Dave
Mon Dec 10 08:24:56 PST 2007

On Dec 6, 12:00 pm, "Gary G. Little" <gary.g.lit...@seagate.com>
wrote:
> Have you stepped into your miniport to see what is happening? Is it failing
> in DriverEntry or in the HW callback functions?

DeviceEntry(), FindAdapters(), and Initilize all seem to be working
and returning successfully. It seems like this is more an issue of
the Device Managers configuration database. Although I'm not sure
where to look in that respect.