Windows Forum

Ask something
Discussion Locked

USB memory key reported as floppy

0 helpful
9 replies

by blackcurrant 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi

One of our users has a 128MB USB memory key. When inserted in their computer it is detected, but when My Computer is opened the device is listed as floppy drive B and is shown as comprising less than 1MB storage space. When the user attempts to save a file (a MS-Word doc of c. 20MB), to the memory key, Word reports that there is insufficient space available.

The OS is WinXP Pro, and is fully up to date.

When I place the same memory key in my computer (same OS), the memory key is allocated the next available drive letter (E), and the size is reported as 128MB.

Does anyone have any ideas how I can get the device to be accurately recognised?

9 replies

by blackcurrant

Hi Jen920, thanks for answering. The problem lay with the fact that the user had mapped a network drive to the next available drive letter (E:). Remapping the netowrk drive to Z: solved the issue.

by bouchie

What information do you see about the USB device in Computer Management? Right-click My Computer, and then click Manage. Under Computer Management, click Storage->Disk Management. In Disk Managment, a right-click on the drive provides the option to Change Drive Letter and Paths. Changing the drive letter *might* solve your problem. Also try Storage->Removable Storage->Media which has been a good source for getting the status on the device.

by blackcurrant

Hi Bouchie, thanks for answering. The problem lay with the fact that the user had mapped a network drive to the next available drive letter (E:). Remapping the netowrk drive to Z: solved the issue.

by blackcurrant

Hi sgt schultz, thanks for answering. The problem lay with the fact that the user had mapped a network drive to the next available drive letter (E:). Remapping the netowrk drive to Z: solved the issue.

by w2ktechman

Try going into disk management and assigning it a new drive letter manually. This should fix it.

by blackcurrant

Hi w2ktechman, thanks for answering. The problem lay with the fact that the user had mapped a network drive to the next available drive letter (E:). Remapping the netowrk drive to Z: solved the issue.

This discussion is closed to new replies.