xxx[SIZE=2][SIZE=2]xxx[/SIZE][/SIZE] OilMan6
11 November 2005.
1733 Hrs. Central U.S. time.

SUBJECT: Operating system won't read new floppy disk drives.

Operating system being used: Windows XP Professional with SP#2.

I bought two new Imation floppy disk drives.

I installed them into both my computers.

Problem: The operating system won't read them.

Details of the problem:

When a blank floppy disk is in the drive, I get the following message.
"The volume does not contain a recognized file system.
Please make sure that all required file system drivers
are loaded and that the volume is not corrupted."

When a disk (with something on it) is in the drive,
I get the following message.
"No ID address mark was found on the floppy disk."

I wrote the Imation support E-address.
They told me ...
"Being that you are using WIN. XP Pro. with SP#2,
you don't need a driver.

Question: Well, what do I do in order
to get these two floppy drives to work properly?

Thank You.

Awaiting your response.

OilMan6.

Curlyben

ARe they enabled in the BIOS settings of your machines ?
Do they show up under 'My computer' ?

Worth a look.

StuMegu

Test the drives before the OS gets hold of them. Using another pc with working floppy drive, download the mem tester from microsoft and install to a blank floppy. Then boot from this floppy on the machines in question. This will tell you whether the drives work. From there you can work on the operating system errors.



http://oca.microsoft.com/en/windiag.asp

fredg

Hi,
This may or may not solve the issue, but if you haven't tried it, here are steps:

1. Right-click My Computer, and then click Manage.
2. Under Computer Management (Local), click Disk Management.
3. In the list of drives in the right pane, right-click the new drive and then click Change Drive Letter and Path(s).
4. Click Change, and in the drop-down box, select a drive letter for the new drive that is not assigned to a mapped network drive.
5. Click OK, and then click OK again.

The above is from Microsoft, dealing with mapped network drives, which can cause an issue similar to yours.