IOS Drive Letter assignment on Windows 98

NTDEV
1

Hi,

We have a system having Windows 98 on which there is a drive that is not formatted. On this system we are trying to install device with storage support (memory stick). We observe that when our storage virtual port driver is being loaded on this type of system, the drive letter being assigned to our device is the same as the last drive letter already existing on the system. Ideally it should be a new drive letter incrementally following the last drive letter already existing on the system. The drive letter is being notified to us through the AEP_CREATE_VRP callback function part of the Asynchronous Event routine registered in the IOS Driver registration packet at the time of initialization. We also observe that if there is no unformatted drive, or if we format the drive when the device is installed, we get the right drive letter upon reboot.

We are suspecting that the windows IOS service Routine is not taking into account the possibility Of an unformatted drive existing on the system at the time of enumerating and assigning a new drive letter.

Has anybody come across such a problem or has any workarounds, please share the information.

Thanks

-Shail.

2

Hi,

We have a system having Windows 98 on which there is a drive that is not formatted. On this system we are trying to install device with storage support (memory stick). We observe that when our storage virtual port driver is being loaded on this type of system, the drive letter being assigned to our device is the same as the last drive letter already existing on the system. Ideally it should be a new drive letter incrementally following the last drive letter already existing on the system. The drive letter is being notified to us through the AEP_CREATE_VRP callback function part of the Asynchronous Event routine registered in the IOS Driver registration packet at the time of initialization. We also observe that if there is no unformatted drive, or if we format the drive when the device is installed, we get the right drive letter upon reboot.

We are suspecting that the windows IOS service Routine is not taking into account the possibility Of an unformatted drive existing on the system at the time of enumerating and assigning a new drive letter.

Has anybody come across such a problem or has any workarounds, please share the information.

Thanks

-Shail.