Problem with USB Mass Storage Devices

Hello,

I have a WinCE 4.20 image with USB Mass Storage device support. Attaching
and Deattaching USB Sticks works well, but when I attach an USB HD the
device is not listed in Windows Explorer and not recognized.
See below for the Debug Port output of attaching an 2,5" HD and an 3,5" HD
to the USB Port. Both are not working.
Thanks in advance.
Gunnar



I get the following output on the Debug Port when I attach a 2,5" HD:

0x8765c800: CHub(Root tier 0)::HubStatusChangeThread - port 2, change =
0x0001, status = 0x0101

0x8765c800: CHub(Root tier 0)::HubStatusChangeThread - device attached on
port 2

0x8765c800: +CHub(Root tier 0)::AttachDevice - port = 2, fIsLowSpeed = 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_USING_ADDRESS0, failures = 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS, failures = 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_LEAVE_ADDRESS0, failures = 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_DEVICE_DESCRIPTOR, failures

= 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR, failures = 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SETUP_CONFIGURATION_DESCRIPTOR_ARRAY, failures = 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_CONFIG_DESCRIPTOR, failures

= 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_CONFIG_DESCRIPTOR, failures = 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE, failures = 0

0x8765c800: WARNING!!!! Auto-selecting config #1 for new device.

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_SET_CONFIG, failures = 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_CREATE_NEW_FUNCTION, failures = 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_INSERT_NEW_DEVICE_INTO_UPSTREAM_HUB_PORT_ARRAY, fai

lures = 0

0x8765c800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SIGNAL_NEW_DEVICE_ENTER_OPERATIONAL_STATE, failures

= 0

0x8765c800: +USBD:OpenPipe, EP: 129, MaxPkt: 64, Type: Bulk

0x8765c800: -USBD:OpenPipe success, hPipe = 523E20

0x8765c800: +USBD:OpenPipe, EP: 2, MaxPkt: 64, Type: Bulk

0x8765c800: -USBD:OpenPipe success, hPipe = 523F30

0x8765c800:
DEVICE!ActivateDeviceEx(Drivers\USB\ClientDrivers\Mass_Storage_Class\6)
entered

0x8765c800: BOT_DataTransfer warning(6.7.2.3, RequestLength:512
TransferLength:63 Err:0 UsbErr:0x0, dwTimeout:5000)

0x8765e800: CQueuedPipe(Bulk)::CheckForDoneTransfers - failure on TD
0x4958c0, address = 1, endpoint = 1, errorCounter = 3, sta

tus field = 0x20

0x8765c800: BOT_DataTransfer warning(6.7.x.3, RequestLength:449
TransferLength:0 Err:31 UsbErr:0x4, dwTimeout:4968)

0x8765c800: +USBD:ResetPipe

0x8765c800: ScsiGetSenseData - SenseKey:0x0 ASC:0x0 ASCQ:0x0

0x8765c800: ScsiModeSense ERROR:0

0x8765c800: Not loading a UpperDriver since partition manager
exists0x8765c800: PNP interface class {A4E7EDDA-E575-4252-9D6B-41

95D48BB865} (DSK3:) ATTACH

0x8765c800: -CHub(Root tier 0)::AttachDevice - port = 2, fIsLowSpeed = 0,
address = 1

0x801b8e20: Unsupported IOCTL:0x71c24

0x801b8e20: DSK_IOControl error: 50

0x801b8e20: Loading partition driver mspart.dll hModule=80175A68

0x801b8e20: Driver mspart.dll loaded

0x80165800: NOTIFICATION::XCeEventHasOccurred

0x80165800: NOTIFICATION::HandleSystemEvent 7 /ADD DSK3:

0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
\\.\Notifications\NamedEvents\DSTTimeChange

0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
\\.\Notifications\NamedEvents\DSTTzChange

0x801b8e20: Opened the store hStore=0009B5E0

0x801b8e20: NumSec=78140160 BytesPerSec=512 FreeSec=0 BiggestCreatable=0

0x801b8e20: Partition Part00 NumSectors=78140097

0x801b8e20: MSPART!PD_OpenPartition: dwStoreId=0009B5E0, PartName=Part00

0x80165800: NOTIFICATION::XCeEventHasOccurred

0x80165800: NOTIFICATION::HandleSystemEvent 7 /ADD DSK3:

0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
\\.\Notifications\NamedEvents\DSTTimeChange

0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
\\.\Notifications\NamedEvents\DSTTzChange





Attaching another 3,5" HD causes the following output:

0x87667df0: CHub(Root tier 0)::HubStatusChangeThread - port 2, change =
0x0001, status = 0x0101

0x87667df0: CHub(Root tier 0)::HubStatusChangeThread - device attached on
port 2

0x87667df0: +CHub(Root tier 0)::AttachDevice - port = 2, fIsLowSpeed = 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_USING_ADDRESS0, failures = 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS, failures = 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_LEAVE_ADDRESS0, failures = 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_DEVICE_DESCRIPTOR, failures

= 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR, failures = 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SETUP_CONFIGURATION_DESCRIPTOR_ARRAY, failures = 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_CONFIG_DESCRIPTOR, failures

= 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_CONFIG_DESCRIPTOR, failures = 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE, failures = 0

0x87667df0: WARNING!!!! Auto-selecting config #1 for new device.

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_SET_CONFIG, failures = 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_CREATE_NEW_FUNCTION, failures = 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_INSERT_NEW_DEVICE_INTO_UPSTREAM_HUB_PORT_ARRAY, fai

lures = 0

0x87667df0: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SIGNAL_NEW_DEVICE_ENTER_OPERATIONAL_STATE, failures

= 0

0x87667df0: +USBD:OpenPipe, EP: 129, MaxPkt: 64, Type: Bulk

0x87667df0: -USBD:OpenPipe success, hPipe = 522EE0

0x87667df0: +USBD:OpenPipe, EP: 2, MaxPkt: 64, Type: Bulk

0x87667df0: -USBD:OpenPipe success, hPipe = 522FF0

0x87667df0:
DEVICE!ActivateDeviceEx(Drivers\USB\ClientDrivers\Mass_Storage_Class\6)
entered

0x87667df0: BOT_DataTransfer warning(6.7.2.3, RequestLength:512
TransferLength:0 Err:1460 UsbErr:0x0, dwTimeout:5000)

0x87667df0: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
dwTimeout:4000)

0x87667df0: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)

0x87667df0: Retry BOT_MassStorageReset

0x87667df0: BOT_DataTransfer warning(6.7.2.3, RequestLength:18
TransferLength:0 Err:1460 UsbErr:0x0, dwTimeout:5000)

0x87667df0: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
dwTimeout:4000)

0x87667df0: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)

0x87667df0: Retry BOT_MassStorageReset

0x87667df0: ScsiGetSenseData error:1460

0x87667df0: ScsiModeSense ERROR:1460

0x87667df0: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
dwTimeout:4000)

0x87667df0: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)

0x87667df0: Retry BOT_MassStorageReset

0x87667df0: BOT_DataTransfer error(5.3.1, 1460, 0x0, 0, 31, 4000)

0x87667df0: Retry BOT_MassStorageReset

0x87667df0: ScsiGetSenseData error:1460

0x87667df0: ScsiTestUnitReady ERROR:1460

0x87667df0: ScsiUnitAttention:1460

0x87667df0: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
dwTimeout:4000)

0x87667df0: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)

0x87667df0: Retry BOT_MassStorageReset

0x87667df0: BOT_DataTransfer error(5.3.1, 1460, 0x0, 0, 31, 4000)

0x87667df0: Retry BOT_MassStorageReset

0x87667df0: ScsiGetSenseData error:1460

0x87667df0: ScsiStartStopUnit ERROR:1460

0x87667df0: BOT_DataTransfer warning(6.7.2.3, RequestLength:18
TransferLength:0 Err:1460 UsbErr:0x0, dwTimeout:5000)

0x87667df0: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
dwTimeout:4000)

0x87667df0: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)

0x87667df0: Retry BOT_MassStorageReset

Gunnar
Fri Feb 10 10:49:56 CST 2006

Hello,
I cut the relevant information out of the Debug output. Does anyone has an
idea why attaching an USB Flash Drive and USB Mouse is working fine and
attaching an USB Hard Disk failed with the debug output listed below?
Gunnar


########################
Attaching USB Flash Drive:
########################

0x8764a800: CHub(Root tier 0)::HubStatusChangeThread - port 2, change =
0x0001, status = 0x0101
0x8764a800: CHub(Root tier 0)::HubStatusChangeThread - device attached on
port 2
0x8764a800: +CHub(Root tier 0)::AttachDevice - port = 2, fIsLowSpeed = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_USING_ADDRESS0, failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS, failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_LEAVE_ADDRESS0, failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_DEVICE_DESCRIPTOR, failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR, failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SETUP_CONFIGURATION_DESCRIPTOR_ARRAY, failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_CONFIG_DESCRIPTOR, failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_CONFIG_DESCRIPTOR, failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE, failures = 0
0x8764a800: WARNING!!!! Auto-selecting config #1 for new device.
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_SET_CONFIG, failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_CREATE_NEW_FUNCTION, failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_INSERT_NEW_DEVICE_INTO_UPSTREAM_HUB_PORT_ARRAY,
failures = 0
0x8764a800: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SIGNAL_NEW_DEVICE_ENTER_OPERATIONAL_STATE, failures = 0
0x8764a800: +USBD:OpenPipe, EP: 129, MaxPkt: 64, Type: Bulk
0x8764a800: -USBD:OpenPipe success, hPipe = 24C760
0x8764a800: +USBD:OpenPipe, EP: 2, MaxPkt: 64, Type: Bulk
0x8764a800: -USBD:OpenPipe success, hPipe = 5377A0
0x8764a800: +USBD:OpenPipe, EP: 131, MaxPkt: 2, Type: Interrupt
0x8764a800: -USBD:OpenPipe success, hPipe = 5378B0
0x8764a800: Command Block Status: Command Failed
0x8764a800: ScsiGetSenseData - SenseKey:0x6 ASC:0x28 ASCQ:0x0
0x8764a800: SENSE_UNIT_ATTENTION : ASC_MEDIA_CHANGED
0x8764a800: ScsiTestUnitReady ERROR:20
0x8764a800: ScsiUnitAttention:20
0x8764a800:
DEVICE!ActivateDeviceEx(Drivers\USB\ClientDrivers\Mass_Storage_Class\6)
entered
0x8764a800: Command Block Status: Command Failed
0x8764a800: ScsiGetSenseData - SenseKey:0x5 ASC:0x24 ASCQ:0x0
0x8764a800: SENSE_ILLEGAL_REQUEST
0x8764a800: ScsiModeSense ERROR:87
0x8764a800: Not loading a UpperDriver since partition manager
exists0x8764a800: PNP interface class {A4E7EDDA-E575-4252-9D6B-41
95D48BB865} (DSK3:) ATTACH
0x8764a800: -CHub(Root tier 0)::AttachDevice - port = 2, fIsLowSpeed = 0,
address = 1
0x80175e54: Unsupported IOCTL:0x71c24
0x80175e54: DSK_IOControl error: 50
0x80175e54: Loading partition driver mspart.dll hModule=8014FD68
0x80175e54: Driver mspart.dll loaded
0x80165800: NOTIFICATION::XCeEventHasOccurred
0x80165800: NOTIFICATION::HandleSystemEvent 7 /ADD DSK3:
0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
\\.\Notifications\NamedEvents\DSTTimeChange
0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
\\.\Notifications\NamedEvents\DSTTzChange
0x80175e54: Opened the store hStore=0009C850
0x80175e54: NumSec=255488 BytesPerSec=512 FreeSec=0 BiggestCreatable=0
0x80175e54: Partition Part00 NumSectors=255425
0x80175e54: MSPART!PD_OpenPartition: dwStoreId=0009C850, PartName=Part00
0x80175e54: FSD_MountDisk: mounting volumes for hDsk=0009DA70
0x80175e54: FATFS!MountDisk: BPB_HiddenSectors(63) != 0
0x80175e54: FATFS!OpenVolume: access time updates disabled
0x80175e54: FATFS!OpenVolume: event logging enabled
0x80175e54: FATFS!OpenVolume: automatic scanning disabled
0x80175e54: FATFS!OpenVolume: write verify disabled
0x80175e54: FATFS!OpenVolume: extra FAT on format disabled
0x80175e54: FATFS!OpenVolume: force write through enabled
0x80175e54: FATFS!OpenVolume: Codepage = 1
0x80175e54: FATFS: Sec/FAT = 249!!!
0x80175e54: FATFS: CacheSize = 128!!!
0x80165800: NOTIFICATION::XCeEventHasOccurred
0x80165800: NOTIFICATION::HandleSystemEvent 7 /ADD \Hard Disk
0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
\\.\Notifications\NamedEvents\DSTTimeChange
0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
\\.\Notifications\NamedEvents\DSTTzChange
0x80165800: NOTIFICATION::XCeEventHasOccurred
0x80165800: NOTIFICATION::HandleSystemEvent 7 /ADD DSK3:
0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
\\.\Notifications\NamedEvents\DSTTimeChange
0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
\\.\Notifications\NamedEvents\DSTTzChange
0x8777d000: FATFS!FAT_GetFileAttributesW(\desktop.ini) returned 0xffffffff
(2)
0x8777d000: FATFS!FAT_CreateFileW(\desktop.ini) returned 0x0 (2)

###########################



########################
Attaching USB HD Drive:
########################

0x87658ce4: CHub(Root tier 0)::HubStatusChangeThread - port 2, change =
0x0001, status = 0x0101
0x87658ce4: CHub(Root tier 0)::HubStatusChangeThread - device attached on
port 2
0x87658ce4: +CHub(Root tier 0)::AttachDevice - port = 2, fIsLowSpeed = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_USING_ADDRESS0, failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS, failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_LEAVE_ADDRESS0, failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_DEVICE_DESCRIPTOR, failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR, failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SETUP_CONFIGURATION_DESCRIPTOR_ARRAY, failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_CONFIG_DESCRIPTOR, failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_CONFIG_DESCRIPTOR, failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE, failures = 0
0x87658ce4: WARNING!!!! Auto-selecting config #1 for new device.
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_SET_CONFIG, failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_CREATE_NEW_FUNCTION, failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_INSERT_NEW_DEVICE_INTO_UPSTREAM_HUB_PORT_ARRAY,
failures = 0
0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SIGNAL_NEW_DEVICE_ENTER_OPERATIONAL_STATE, failures = 0
0x87658ce4: +USBD:OpenPipe, EP: 129, MaxPkt: 64, Type: Bulk
0x87658ce4: -USBD:OpenPipe success, hPipe = 536B70
0x87658ce4: +USBD:OpenPipe, EP: 2, MaxPkt: 64, Type: Bulk
0x87658ce4: -USBD:OpenPipe success, hPipe = 5396E0
0x87658ce4:
DEVICE!ActivateDeviceEx(Drivers\USB\ClientDrivers\Mass_Storage_Class\6)
entered
0x87658ce4: BOT_DataTransfer warning(6.7.2.3, RequestLength:512
TransferLength:0 Err:1460 UsbErr:0x0, dwTimeout:5000)
0x87658ce4: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
dwTimeout:4000)
0x87658ce4: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)
0x87658ce4: Retry BOT_MassStorageReset

########################

SergeiR
Fri Feb 10 11:45:30 CST 2006

Hello,

from your debug output messages, I could only see that

1) regarding 1st case, you did get DSK3: and \Hard Disk being added
correctly, so it looks like it almost worked. Perhaps disk is not a simple
FAT format or is too large in size or maybe it is FAT32 ?

2) regarding 2nd case, you didn't get DSK#: and there was BOT message. Maybe
many of them showing up continiously ... ? That one looks like usb
peripheral gets not enough power supply. I.e. are you using external power
supply to provide power to your usb peripheral disk ? If not, please try
that maybe it would help.

SergeiR

"Gunnar Frenzel" <Gunnar_Frenzel@web.de> wrote in message
news:uJU1HImLGHA.2696@TK2MSFTNGP14.phx.gbl...
> Hello,
> I cut the relevant information out of the Debug output. Does anyone has an
> idea why attaching an USB Flash Drive and USB Mouse is working fine and
> attaching an USB Hard Disk failed with the debug output listed below?
> Gunnar
>
>
> ########################
> Attaching USB Flash Drive:
> ########################
>
> 0x8764a800: CHub(Root tier 0)::HubStatusChangeThread - port 2, change =
> 0x0001, status = 0x0101
> 0x8764a800: CHub(Root tier 0)::HubStatusChangeThread - device attached on
> port 2
> 0x8764a800: +CHub(Root tier 0)::AttachDevice - port = 2, fIsLowSpeed = 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_USING_ADDRESS0, failures = 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS, failures = 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_LEAVE_ADDRESS0, failures = 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_DEVICE_DESCRIPTOR, failures =
> 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR, failures = 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SETUP_CONFIGURATION_DESCRIPTOR_ARRAY, failures = 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_CONFIG_DESCRIPTOR, failures =
> 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SCHEDULING_GET_CONFIG_DESCRIPTOR, failures = 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE, failures = 0
> 0x8764a800: WARNING!!!! Auto-selecting config #1 for new device.
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SCHEDULING_SET_CONFIG, failures = 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_CREATE_NEW_FUNCTION, failures = 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_INSERT_NEW_DEVICE_INTO_UPSTREAM_HUB_PORT_ARRAY,
> failures = 0
> 0x8764a800: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SIGNAL_NEW_DEVICE_ENTER_OPERATIONAL_STATE, failures =
> 0
> 0x8764a800: +USBD:OpenPipe, EP: 129, MaxPkt: 64, Type: Bulk
> 0x8764a800: -USBD:OpenPipe success, hPipe = 24C760
> 0x8764a800: +USBD:OpenPipe, EP: 2, MaxPkt: 64, Type: Bulk
> 0x8764a800: -USBD:OpenPipe success, hPipe = 5377A0
> 0x8764a800: +USBD:OpenPipe, EP: 131, MaxPkt: 2, Type: Interrupt
> 0x8764a800: -USBD:OpenPipe success, hPipe = 5378B0
> 0x8764a800: Command Block Status: Command Failed
> 0x8764a800: ScsiGetSenseData - SenseKey:0x6 ASC:0x28 ASCQ:0x0
> 0x8764a800: SENSE_UNIT_ATTENTION : ASC_MEDIA_CHANGED
> 0x8764a800: ScsiTestUnitReady ERROR:20
> 0x8764a800: ScsiUnitAttention:20
> 0x8764a800:
> DEVICE!ActivateDeviceEx(Drivers\USB\ClientDrivers\Mass_Storage_Class\6)
> entered
> 0x8764a800: Command Block Status: Command Failed
> 0x8764a800: ScsiGetSenseData - SenseKey:0x5 ASC:0x24 ASCQ:0x0
> 0x8764a800: SENSE_ILLEGAL_REQUEST
> 0x8764a800: ScsiModeSense ERROR:87
> 0x8764a800: Not loading a UpperDriver since partition manager
> exists0x8764a800: PNP interface class {A4E7EDDA-E575-4252-9D6B-41
> 95D48BB865} (DSK3:) ATTACH
> 0x8764a800: -CHub(Root tier 0)::AttachDevice - port = 2, fIsLowSpeed = 0,
> address = 1
> 0x80175e54: Unsupported IOCTL:0x71c24
> 0x80175e54: DSK_IOControl error: 50
> 0x80175e54: Loading partition driver mspart.dll hModule=8014FD68
> 0x80175e54: Driver mspart.dll loaded
> 0x80165800: NOTIFICATION::XCeEventHasOccurred
> 0x80165800: NOTIFICATION::HandleSystemEvent 7 /ADD DSK3:
> 0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
> \\.\Notifications\NamedEvents\DSTTimeChange
> 0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
> \\.\Notifications\NamedEvents\DSTTzChange
> 0x80175e54: Opened the store hStore=0009C850
> 0x80175e54: NumSec=255488 BytesPerSec=512 FreeSec=0 BiggestCreatable=0
> 0x80175e54: Partition Part00 NumSectors=255425
> 0x80175e54: MSPART!PD_OpenPartition: dwStoreId=0009C850, PartName=Part00
> 0x80175e54: FSD_MountDisk: mounting volumes for hDsk=0009DA70
> 0x80175e54: FATFS!MountDisk: BPB_HiddenSectors(63) != 0
> 0x80175e54: FATFS!OpenVolume: access time updates disabled
> 0x80175e54: FATFS!OpenVolume: event logging enabled
> 0x80175e54: FATFS!OpenVolume: automatic scanning disabled
> 0x80175e54: FATFS!OpenVolume: write verify disabled
> 0x80175e54: FATFS!OpenVolume: extra FAT on format disabled
> 0x80175e54: FATFS!OpenVolume: force write through enabled
> 0x80175e54: FATFS!OpenVolume: Codepage = 1
> 0x80175e54: FATFS: Sec/FAT = 249!!!
> 0x80175e54: FATFS: CacheSize = 128!!!
> 0x80165800: NOTIFICATION::XCeEventHasOccurred
> 0x80165800: NOTIFICATION::HandleSystemEvent 7 /ADD \Hard Disk
> 0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
> \\.\Notifications\NamedEvents\DSTTimeChange
> 0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
> \\.\Notifications\NamedEvents\DSTTzChange
> 0x80165800: NOTIFICATION::XCeEventHasOccurred
> 0x80165800: NOTIFICATION::HandleSystemEvent 7 /ADD DSK3:
> 0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
> \\.\Notifications\NamedEvents\DSTTimeChange
> 0x80165800: NOTIFICATION::HandleSystemEvent::Don't want
> \\.\Notifications\NamedEvents\DSTTzChange
> 0x8777d000: FATFS!FAT_GetFileAttributesW(\desktop.ini) returned 0xffffffff
> (2)
> 0x8777d000: FATFS!FAT_CreateFileW(\desktop.ini) returned 0x0 (2)
>
> ###########################
>
>
>
> ########################
> Attaching USB HD Drive:
> ########################
>
> 0x87658ce4: CHub(Root tier 0)::HubStatusChangeThread - port 2, change =
> 0x0001, status = 0x0101
> 0x87658ce4: CHub(Root tier 0)::HubStatusChangeThread - device attached on
> port 2
> 0x87658ce4: +CHub(Root tier 0)::AttachDevice - port = 2, fIsLowSpeed = 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_USING_ADDRESS0, failures = 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS, failures = 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_LEAVE_ADDRESS0, failures = 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_DEVICE_DESCRIPTOR, failures =
> 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR, failures = 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SETUP_CONFIGURATION_DESCRIPTOR_ARRAY, failures = 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_CONFIG_DESCRIPTOR, failures =
> 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SCHEDULING_GET_CONFIG_DESCRIPTOR, failures = 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE, failures = 0
> 0x87658ce4: WARNING!!!! Auto-selecting config #1 for new device.
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SCHEDULING_SET_CONFIG, failures = 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_CREATE_NEW_FUNCTION, failures = 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_INSERT_NEW_DEVICE_INTO_UPSTREAM_HUB_PORT_ARRAY,
> failures = 0
> 0x87658ce4: CHub(Root tier 0)::AttachDevice - status =
> DEVICE_CONFIG_STATUS_SIGNAL_NEW_DEVICE_ENTER_OPERATIONAL_STATE, failures =
> 0
> 0x87658ce4: +USBD:OpenPipe, EP: 129, MaxPkt: 64, Type: Bulk
> 0x87658ce4: -USBD:OpenPipe success, hPipe = 536B70
> 0x87658ce4: +USBD:OpenPipe, EP: 2, MaxPkt: 64, Type: Bulk
> 0x87658ce4: -USBD:OpenPipe success, hPipe = 5396E0
> 0x87658ce4:
> DEVICE!ActivateDeviceEx(Drivers\USB\ClientDrivers\Mass_Storage_Class\6)
> entered
> 0x87658ce4: BOT_DataTransfer warning(6.7.2.3, RequestLength:512
> TransferLength:0 Err:1460 UsbErr:0x0, dwTimeout:5000)
> 0x87658ce4: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
> dwTimeout:4000)
> 0x87658ce4: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)
> 0x87658ce4: Retry BOT_MassStorageReset
>
> ########################
>
>

Gunnar
Mon Feb 13 02:28:00 CST 2006

Hello,
the 1st case is working. Attaching the USB flash drive works fine, the
problem is with the second case. I've tried both a USB HD with external
Power Supply and one without external power supply and two USB connectors.
Both are not working. The output in 2nd case is from the one with external
power supply. The BOT messages are indead showing up continuously:

0x8764a800:
DEVICE!ActivateDeviceEx(Drivers\USB\ClientDrivers\Mass_Storage_Class\6)
entered
0x8764a800: BOT_DataTransfer warning(6.7.2.3, RequestLength:512
TransferLength:0 Err:1460 UsbErr:0x0, dwTimeout:5000)
0x8764a800: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
dwTimeout:4000)
0x8764a800: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)
0x8764a800: Retry BOT_MassStorageReset
0x8764a800: BOT_DataTransfer warning(6.7.2.3, RequestLength:18
TransferLength:0 Err:1460 UsbErr:0x0, dwTimeout:5000)
0x8764a800: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
dwTimeout:4000)
0x8764a800: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)
0x8764a800: Retry BOT_MassStorageReset
0x8764a800: ScsiGetSenseData error:1460
0x8764a800: ScsiModeSense ERROR:1460
0x8764a800: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
dwTimeout:4000)
0x8764a800: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)
0x8764a800: Retry BOT_MassStorageReset
0x8764a800: BOT_DataTransfer error(5.3.1, 1460, 0x0, 0, 31, 4000)

So what causes these BOT messages? Looks like the SCSIGetSenseData call
fails. Because this HD has an external power supply, this doesn't seem to
cause the problem here. Any idea what's going wrong?

Gunnar





"SergeiR" <sergeir@termos.ru> wrote in message
news:%23lU1KnmLGHA.500@TK2MSFTNGP15.phx.gbl...
> Hello,
>
> from your debug output messages, I could only see that
>
> 1) regarding 1st case, you did get DSK3: and \Hard Disk being added
> correctly, so it looks like it almost worked. Perhaps disk is not a simple
> FAT format or is too large in size or maybe it is FAT32 ?
>
> 2) regarding 2nd case, you didn't get DSK#: and there was BOT message.
> Maybe many of them showing up continiously ... ? That one looks like usb
> peripheral gets not enough power supply. I.e. are you using external power
> supply to provide power to your usb peripheral disk ? If not, please try
> that maybe it would help.
>
> SergeiR
>

SergeiR
Mon Feb 13 11:17:26 CST 2006

Hi,

please search this newsgroup for a discussion, about 1/2 year ago to 1 year
ago, where a developer of usb storage device driver was asking contributors
for their feedback, including debug messages, where, as far as I recall,
some messages were explained, and BOT was one of them. My impression was it
relates to power stuff, but aparently it looks incorrect in this case.

Sincerely
SergeiR

"Gunnar Frenzel" <Gunnar_Frenzel@web.de> wrote in message
news:u7EcpdHMGHA.3064@TK2MSFTNGP10.phx.gbl...
> Hello,
> the 1st case is working. Attaching the USB flash drive works fine, the
> problem is with the second case. I've tried both a USB HD with external
> Power Supply and one without external power supply and two USB connectors.
> Both are not working. The output in 2nd case is from the one with external
> power supply. The BOT messages are indead showing up continuously:
>
> 0x8764a800:
> DEVICE!ActivateDeviceEx(Drivers\USB\ClientDrivers\Mass_Storage_Class\6)
> entered
> 0x8764a800: BOT_DataTransfer warning(6.7.2.3, RequestLength:512
> TransferLength:0 Err:1460 UsbErr:0x0, dwTimeout:5000)
> 0x8764a800: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
> dwTimeout:4000)
> 0x8764a800: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)
> 0x8764a800: Retry BOT_MassStorageReset
> 0x8764a800: BOT_DataTransfer warning(6.7.2.3, RequestLength:18
> TransferLength:0 Err:1460 UsbErr:0x0, dwTimeout:5000)
> 0x8764a800: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
> dwTimeout:4000)
> 0x8764a800: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)
> 0x8764a800: Retry BOT_MassStorageReset
> 0x8764a800: ScsiGetSenseData error:1460
> 0x8764a800: ScsiModeSense ERROR:1460
> 0x8764a800: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
> dwTimeout:4000)
> 0x8764a800: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)
> 0x8764a800: Retry BOT_MassStorageReset
> 0x8764a800: BOT_DataTransfer error(5.3.1, 1460, 0x0, 0, 31, 4000)
>
> So what causes these BOT messages? Looks like the SCSIGetSenseData call
> fails. Because this HD has an external power supply, this doesn't seem to
> cause the problem here. Any idea what's going wrong?
>
> Gunnar
>
>
>
>
>
> "SergeiR" <sergeir@termos.ru> wrote in message
> news:%23lU1KnmLGHA.500@TK2MSFTNGP15.phx.gbl...
>> Hello,
>>
>> from your debug output messages, I could only see that
>>
>> 1) regarding 1st case, you did get DSK3: and \Hard Disk being added
>> correctly, so it looks like it almost worked. Perhaps disk is not a
>> simple FAT format or is too large in size or maybe it is FAT32 ?
>>
>> 2) regarding 2nd case, you didn't get DSK#: and there was BOT message.
>> Maybe many of them showing up continiously ... ? That one looks like usb
>> peripheral gets not enough power supply. I.e. are you using external
>> power supply to provide power to your usb peripheral disk ? If not,
>> please try that maybe it would help.
>>
>> SergeiR
>>
>
>

Andrew
Mon Feb 13 13:54:49 CST 2006

I'm looking into problems with mass storage devices at the moment also,
although the output I have is quite different to yours so I'm not sure
if I can help.

However, in response to discussion about these messages, the "BOT"
refers to Bulk Only Transport, and the first number after the brackets
is a reference to a section in the USB Mass Storage specification
document. The BOT_DataTransfer() function is a fairly low level one -
you probably need to set a breakpoint on the previous higher level
calling code and investigate what it was trying to do.

In my case I hit a dead end (currently discussing with the device
manufacturer) because the failure had dwUsbErr of 0x5, which maps to
USB_DEVICE_NOT_RESPONDING_ERROR - I beleive that means a failre to
respond at the OHCI hardware controller level.

In your case, there doesn't look to be any low level error (dwUsbErr is
0), but I imagine dwCswErr=1460 maps to the value from winerror.h of
ERROR_TIMEOUT, so I'd start by tweaking the various timeout parameters
in the registry for USB mass storage (see the online help). You can do
this on the fly while your USB mass storage device is removed (ie using
remote registry editor) and then plug it back in to see the new timeouts
in effect.

> > entered
> > 0x8764a800: BOT_DataTransfer warning(6.7.2.3, RequestLength:512
> > TransferLength:0 Err:1460 UsbErr:0x0, dwTimeout:5000)
> > 0x8764a800: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
> > etc

Rob
Wed Feb 15 10:31:31 CST 2006

Hi,
What did you do to fix the first case ?
I have similar trouble with some of my usb-keys...

Greetings,
Rob.


"Gunnar Frenzel" wrote:

> Hello,
> the 1st case is working. Attaching the USB flash drive works fine, the
> problem is with the second case. I've tried both a USB HD with external
> Power Supply and one without external power supply and two USB connectors.
> Both are not working. The output in 2nd case is from the one with external
> power supply. The BOT messages are indead showing up continuously:
>
> 0x8764a800:
> DEVICE!ActivateDeviceEx(Drivers\USB\ClientDrivers\Mass_Storage_Class\6)
> entered
> 0x8764a800: BOT_DataTransfer warning(6.7.2.3, RequestLength:512
> TransferLength:0 Err:1460 UsbErr:0x0, dwTimeout:5000)
> 0x8764a800: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
> dwTimeout:4000)
> 0x8764a800: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)
> 0x8764a800: Retry BOT_MassStorageReset
> 0x8764a800: BOT_DataTransfer warning(6.7.2.3, RequestLength:18
> TransferLength:0 Err:1460 UsbErr:0x0, dwTimeout:5000)
> 0x8764a800: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
> dwTimeout:4000)
> 0x8764a800: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)
> 0x8764a800: Retry BOT_MassStorageReset
> 0x8764a800: ScsiGetSenseData error:1460
> 0x8764a800: ScsiModeSense ERROR:1460
> 0x8764a800: BOT_DataTransfer error(5.3.3, dwCswErr:1460, dwUsbErr:0x0,
> dwTimeout:4000)
> 0x8764a800: BOT_DataTransfer error(5.3.3, ResetErr:0x5b4 StallCount:0)
> 0x8764a800: Retry BOT_MassStorageReset
> 0x8764a800: BOT_DataTransfer error(5.3.1, 1460, 0x0, 0, 31, 4000)
>
> So what causes these BOT messages? Looks like the SCSIGetSenseData call
> fails. Because this HD has an external power supply, this doesn't seem to
> cause the problem here. Any idea what's going wrong?
>
> Gunnar
>
>
>
>
>
> "SergeiR" <sergeir@termos.ru> wrote in message
> news:%23lU1KnmLGHA.500@TK2MSFTNGP15.phx.gbl...
> > Hello,
> >
> > from your debug output messages, I could only see that
> >
> > 1) regarding 1st case, you did get DSK3: and \Hard Disk being added
> > correctly, so it looks like it almost worked. Perhaps disk is not a simple
> > FAT format or is too large in size or maybe it is FAT32 ?
> >
> > 2) regarding 2nd case, you didn't get DSK#: and there was BOT message.
> > Maybe many of them showing up continiously ... ? That one looks like usb
> > peripheral gets not enough power supply. I.e. are you using external power
> > supply to provide power to your usb peripheral disk ? If not, please try
> > that maybe it would help.
> >
> > SergeiR
> >
>
>
>

Gunnar
Wed Feb 15 10:45:22 CST 2006

Hello,
the first case has never been a problem. It always worked with the USB
Sticks I had here, just external Hard Drive didn't worked.
Meanwhile the hard drives are working, too - in a WinCE 5.0 image. In WinCE
4.2 I wasn't able to get it running. In the WinCE 5.0 image there was a
problem with the hive based registry. There were drivers with the
"Flags"=dword:1000 setting. I removed any driver from the HIVE BOOT SECTION
section and removed there "Flags" parameter except for the
drivers\builtin\atapi and drivers\builtin\atapi\device* drivers and now hive
based registry as well as external hard drives seem to work. It looks like
there's been a conflict with any of these settings.
I don't know what's wrong in the WinCE 4.2 image, where I got the messages
from my previous postings. (But the problem in WinCE 5.0 was similar).
Gunnar


"Rob" <Rob@discussions.microsoft.com> wrote in message
news:21B39FE6-AF81-4510-AD7F-E14515199A7E@microsoft.com...
> Hi,
> What did you do to fix the first case ?
> I have similar trouble with some of my usb-keys...
>
> Greetings,
> Rob.
>