FirstBusScanTimeInMs

[KachiWachi]

Anybody know how the value for this is determined?

I have a situation that I wish to discuss if someone here
is knowledgable about this registry value, how it is
detected, etc...

Thanks for your input.

 

[Heelen Diyond]

Is this value under [HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0]
?
I think it is related to SCSI drive.

Search Google for more info.

 

[KachiWachi]

Yes it is, but in Windows terms, all drive-type devices
are refered to as SCSI in this location.

Google searching has not provided any technical
information on how this item is derived.

Anyone...???

 

[Mark V]

Yes it is, but in Windows terms, all drive-type devices
are refered to as SCSI in this location.

Google searching has not provided any technical
information on how this item is derived.

Anyone...???

Not from knowledge I possess or can locate.

But I ran a regmon.exe "Log Boot" here on W2K, SP4 with a Promise
IDE controller that is treated as SCSI device. There is also a
IDE/ATAPI CD-RW device present and this is the device and bus which
contains the FirstBusScanTimeInMs (3004 ms). I can see that it is
definitely the System and during the boot (fairly early). From this
and the valuename I might guess that it is a record of how long the
first scan of the Bus took. Possibly used later to determine when a
Time-Out error should be triggered. This valuname only appears for the
CD (SCSI Port 0) and not for the IDE controller (Port 1). So I would
conclude that the system bus scanning process is simply recording a
value that is determined during the boot process for "slow" devices like
CD/DVD. The DEVICEMAP location I believe supports this theory. The
value does not appear to be accessed in normal (post-boot) operation.
*** This interpretation is pure speculation on my part. ***
Should you locate more complete and thorough information, please post it.

(partial regmon.log):

1792: System:8 CloseKey HKLM\System\CurrentControlSet\Services\atapi\Parameters SUCCESS
1793: System:8 CreateKey HKLM\Hardware\DeviceMap\Scsi SUCCESS Access: 0x2001F
1794: System:8 CreateKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0 SUCCESS Access: 0x2001F
1795: System:8 CloseKey HKLM\Hardware\DeviceMap\Scsi SUCCESS

1796: System:8 SetValue HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\FirstBusScanTimeInMs SUCCESS 0xBBC

1797: System:8 SetValue HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\DMAEnabled SUCCESS 0x1
1798: System:8 SetValue HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Driver SUCCESS "atapi"
1799: System:8 CreateKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0 SUCCESS Access: 0x2001F
1800: System:8 CreateKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Initiator Id 255 SUCCESS Access: 0x2001F
1801: System:8 CloseKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Initiator Id 255 SUCCESS
1802: System:8 CreateKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0 SUCCESS Access: 0x2001F
1803: System:8 CreateKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0\Logical Unit Id 0 SUCCESS Access: 0x2001F
1804: System:8 SetValue HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0\Logical Unit Id 0\Identifier SUCCESS "IDE-CD R/RW 4x4x24"
1805: System:8 SetValue HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0\Logical Unit Id 0\Type SUCCESS "CdRomPeripheral"
1806: System:8 CloseKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0\Logical Unit Id 0 SUCCESS
1807: System:8 CloseKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0 SUCCESS
1808: System:8 CloseKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0 SUCCESS
1809: System:8 CloseKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0 SUCCESS
1810: System:8 OpenKey HKLM\System\CurrentControlSet SUCCESS Access: 0x20019
....
60034: SERVICES.EXE:220 CloseKey *** Invalid Name **** SUCCESS
60035: System:8 CreateKey HKLM\Hardware\DeviceMap\Scsi SUCCESS Access: 0x2001F
60036: System:8 CreateKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0 SUCCESS Access: 0x2001F
60037: System:8 CloseKey HKLM\Hardware\DeviceMap\Scsi SUCCESS

60038: System:8 SetValue HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\FirstBusScanTimeInMs SUCCESS 0xBBC

60039: System:8 SetValue HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\DMAEnabled SUCCESS 0x1
60040: System:8 SetValue HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Driver SUCCESS "atapi"
60041: System:8 CreateKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0 SUCCESS Access: 0x2001F
60042: System:8 CreateKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Initiator Id 255 SUCCESS Access: 0x2001F
60043: System:8 CloseKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Initiator Id 255 SUCCESS
60044: System:8 CreateKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0 SUCCESS Access: 0x2001F
60045: System:8 CreateKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0\Logical Unit Id 0 SUCCESS Access: 0x2001F
60046: System:8 SetValue HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0\Logical Unit Id 0\Identifier SUCCESS "IDE-CD R/RW 4x4x24"
60047: System:8 SetValue HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0\Logical Unit Id 0\Type SUCCESS "CdRomPeripheral"
60048: System:8 CloseKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0\Logical Unit Id 0 SUCCESS
60049: System:8 CloseKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0 SUCCESS
60050: System:8 CloseKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 0 SUCCESS
60051: System:8 CloseKey HKLM\Hardware\DeviceMap\Scsi\Scsi Port 0 SUCCESS
60052: System:8 OpenKey HKLM\System\CurrentControlSet SUCCESS Access: 0x20019

 

[KachiWachi]

Mark V -

Thank you for your reply.

In my situation, I also get 3004 (decimal), but for my HD,
which is on the Primary IDE Port. My CD-ROM reads 10
(decimal), and is on the Secondary IDE Port. Both devices
are alone on their respective ports.

The funny thing is that I have another, different PC with
the exact same HD installed, and it reads 10 (decimal)!!

Are you saying that this value is (might be) calculated
each time you boot up, or just on the first boot?

I could not find the 3004 value in the text you provided.

 

[Mark V]

Mark V -

Thank you for your reply.

In my situation, I also get 3004 (decimal), but for my HD,
which is on the Primary IDE Port. My CD-ROM reads 10
(decimal), and is on the Secondary IDE Port. Both devices
are alone on their respective ports.

At the moment I have one (slow) device on the MoBo supplied IDE
controller and it is on the first port as master. Nothing else on
that controller (while waiting for a replacement DVD drive)

The two HDDs here run off the add-in IDE controller (one device on
each of two ports as "master").

The funny thing is that I have another, different PC with
the exact same HD installed, and it reads 10 (decimal)!!

It may be that the value is bus-specific or perhaps device-specific?
Does it seems this value is only calculated for the first "SCSI"
controller in the system? I suspect that is the case.

Are you saying that this value is (might be) calculated
each time you boot up, or just on the first boot?

Without any hard facts or authoritative explanations yet available, I
draw on what I can observe (value written during every boot process)
and extrapolate from there. It's no more than a theory. Still
hoping someone who actually knows the answers will drop in an
enlighten us.

I could not find the 3004 value in the text you provided.

Sorry, I should have written "3004(decimal), BBC(hex)"

My post is atypical for me, as I usually deal with "facts" and "best
practices", but you insisted,
"Anyone...???" <G>
So I used a tool to find that this value is determined and recorded
during the boot process. That is really the only "fact" that I have
at this time. This is not much beyond what is indicated by the
location (\HARDWARE\...).

So I would say I know _when_ (during hardware discovery early in the
bootup) it is determined and by who (the system), but not _why_ or
how it is used or what the value really means. It may be the result
of a driver's query of the system or device perhaps that returns a
value which is recorded. My (pure guess here) is that this is
utilized later (maybe) during normal operations to calculate if a
time-out error should be posted or not.

Perhaps one of the regular visitors here has the resources and
contacts to pry something loose from Microsoft on this topic...

Another avenue might be device driver writers. Programmers with DDK
information regarding Windows actions with regards to hardware
determination during OS startup. I've been known to dig deep, but
not that deep.

I presume this is just for curiosity's sake. I do that myself. On
the off-chance that you are having actual problems with a SCSI
device, the answer would not be with this section of the registry
directly (in my best opinion).

 

[KachiWachi]

Thanks again for your response Mark V.

Oops...I really didn't read your regmon.log...just
searched it. I now see the bbch text.

I am having some problems, that's why I'm looking into
this.

The device is an ATA-5 Maxtor DiamondPlus VL 40GB drive
running on a i430VX chipset, which limits the drive to PIO-
4/MWDMA-2 speeds. I know W2K has a "feature" that steps
down the drive speed when it encounters "errors" as noted
here -

http://support.microsoft.com/default.aspx?scid=kb;en-
us;817472

Early on in the life of this OS install, and once I
learned more about it, I found that the drive had stepped
down to PIO-2, with DMA turned off!! (Scsi Port 0 sub-
key.) I've since restored the system back to full speed,
and have a grasp on what the other drive settings are (for
the most part), but this one haunts me, since on another
machine with the same drive (though an ATA-4 capable
controller), the setting is different.

I wish I could get the "fix" for this, because I'm pretty
sure that just putting in the registry key will do nothing
unless I have the updated atapi.sys file.

My CD-ROM is also "faster" than the chipset can support,
so it is also stepped down to PIO-4/MWDMA-2...yet it reads
ah (10 decimal) in the "Scsi Port 1" sub-key. This is what
confuses me.

I do have a SCSI card in the machine for an external CD-RW
and ZIP (Scsi Port 3 sub-key), but the registry has
different information in the sub-key for that, and does
not apply.

I hear you on the facts (I'm the same way)...but sometimes
if a thread gets alot of attention, maybe the "experts"
will chime in...so keep posting!!

 

[Mark V]

Thanks again for your response Mark V.

[ all prior was snipped }

[ ]

I am having some problems, that's why I'm looking into
this.

The device is an ATA-5 Maxtor DiamondPlus VL 40GB drive
running on a i430VX chipset, which limits the drive to PIO-
4/MWDMA-2 speeds. I know W2K has a "feature" that steps
down the drive speed when it encounters "errors" as noted
here -

Jumping sideways momentarily. I too was limited by my MoBo VIA IDE
chipset with newer, more capable drives. My solution: Purchase a
Promise PCI/IDE controller for less than $30 US. Aside from finding
that I needed one driver version older than "current", it did the
trick and I now operate the ATA-5 drive at ATA-5. Have you ruled
this option out for cause?

Continuing with hardware. Are you using a newer 80-conductor cable
and has it been reseated? Have you run the Maxtor diagnostics to
rule out the drive itself. Not certain if Maxblast (?) does a check
for cabling errors though. HD problems or cabling errors might be an
underlying cause perhaps.

http://support.microsoft.com/default.aspx?scid=kb;en-
us;817472

Never seen such behavior myself. The KB article was of interest
however. Are you on SP4 now? I see the HotFix file is a later
version though.
In your case does this step-down occur in conjunction with a
"resume" event or any other "spin-up" event other than system power-
on? If not then I suggest that article is less appropriate and that
HD or cabling could be the true cause.

Early on in the life of this OS install, and once I
learned more about it, I found that the drive had stepped
down to PIO-2, with DMA turned off!! (Scsi Port 0 sub-
key.) I've since restored the system back to full speed,
and have a grasp on what the other drive settings are (for
the most part), but this one haunts me, since on another
machine with the same drive (though an ATA-4 capable
controller), the setting is different.

I *think* you are on a goose chase in the HARDWARE sub-key. Most of
that is both volatile and derived from boot-up processes (starting
with ntdetect IIRC). Unless you are hoping the value is dynamically
updated and significant as an indicator (as it appears you do). I
will look for such information when I can.

I wish I could get the "fix" for this, because I'm pretty
sure that just putting in the registry key will do nothing
unless I have the updated atapi.sys file.

Based on the article I would agree with that. (HKEY_LOCAL_MACHINE
\SYSTEM\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-
08002BE10318}\0001 add a key. Seems both the new key and the new
file are required to get the altered timings.

[ ]

I hear you on the facts (I'm the same way)...but sometimes
if a thread gets alot of attention, maybe the "experts"
will chime in...so keep posting!!

I will as time permits. Have you tried ms.public.*.hardware groups?

 

[Guest]

No room in the board for another PCI card (Video, NIC,
SCSI, and USB/Firewire...Sound and Modem are ISA). Plus,
the board is older...only 66MHz bus capable (officially),
even though I have the BIOS patched to run an AMD K6-2/+
(400MHz...6x66MHz). I'd jump to 6x75MHz, but I don't think
the SCSI card would like it timing-wise, from what I
understand.

An 80 conductor cable is not required at PIO-4/MWDMA-2
speeds, and I'm not sure adding one would do anything,
since there is no "fault correction" defined for the ATA-2
standard either. The drive tests fine using MaxBlast.

Yes I'm at SP4, and yes...the file is newer. The document
says you need W2K SP2, but was first fixed in XP SP2.

For me, I just think the system on the whole stalls at
certain times...which creates the issue. In the beginning,
I installed all the "MS Updates" in one shot, with the
exception of some of the biggies I had downloaded to CD.
Installing all these at once was probably CPU intensive,
so the HD did not get serviced in time.

I guess I'm thinking that somehow the key is wrong and
should say ah...like the other drive does in the other
machine. I was curious if I changed it manually, if it
would stay, restore itself, or...?? That was the purpose
in asking what the function/value of this key means.