Sign in with
Sign up | Sign in
Your question

Diskette Drive A Error

Tags:
  • Floppy Disk
  • Cable
  • Components
Last response: in Components
Share
August 21, 2014 8:19:37 AM

I am having a problem with my computer. I am running Windows 95 on a Dell Dimension Socket 5 motherboard and I receive a 'Diskette Drive A error' when booting up. I am unable to access my Floppy Drive, CD-ROM and Zip Drive as a result of this.

I have tried the following:

1. Making sure the IDE cable is connected correctly (the IDE cable for the Floppy Drive only fits one way).

2. Made sure the IDE cable that connects to the CD-ROM and Zip Drive is connected correctly i.e. that the red dotted line matches with pin one on the connector.

3. Making sure the cables are connected tightly to the drives.

4. Tried connecting another IDE cable for the Floppy Drive to rule out a bad IDE cable.

5. Tried re-installing Windows 95.

6. Tried setting the Floppy Drive to 'Not Installed' in the BIOS.

7. Tried setting the Floppy Drive type from '3.5 inch 1.44mb' to '3.5 inch 720k' in the BIOS.

8. Tried replacing the CMOS battery.

9. Tried replacing the 3.5 inch Floppy Disk Drive.

10. Tried installing a Floppy Disk Controller Card and setting different jumper combinations.

11. Tried running the computer with the Zip Drive disconnected in an attempt to free up power.

11. Tried attaching a fan to the CPU and heatsink to help prevent the CPU from becoming too hot.

12. Made sure the Hard Disk Drive is set to 'Auto' in the BIOS.

13. Disabled the Floppy Disk Controller by right clicking on 'My Computer', selecting 'Properties', clicking the 'Device Manager' Tab, clicking the plus (+) symbol next to Floppy Disk Controllers, double clicking on 'Standard Floppy Disk Controller' and left clicking the white box next to 'Disable this in hardware profile', then clicking OK to save the changes.

14. Disconnected the Floppy Drive and disconnected the IDE cable that connects to the Floppy connector on the motherboard.

In 'Device Manger' there is a yellow exclamation mark next to CMD PCI-0690 PCI to IDE Controller. I have checked the registry by clicking 'Start', 'Run' typing regedit and going to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Service\VxD\IOS and checking for an instance of 'NOIDE' but there is no such instance.


Can anyone help?

Thanks so much!

More about : diskette drive error

August 21, 2014 8:27:58 AM

ooo windows 95. Lets see how good my memory is...Or i can just load it up real quick in a VM XD.

So the question is do you need the floppy? If not Try disabling the Floppy drive in the CMOS. Also since you can see that is there something going on with the drives do this. Not sure if its the same for Windows 95. I need you to get the Hardware ID of the so called IDE Controller. This is what will help us out in finding the drive for it. at least in XP and up when you double click on the Device with the Yellow ! it should bring up a properties window. in there is there a tab that says "Details"? If so click on that and there should be a drop down menu. one of them should say Hardware ID. All i need is the first ID in the list and then we can search for that ID on http://www.pcidatabase.com/ and see exactly what hardware it is and then we can start searching for a driver.
m
0
l
August 21, 2014 8:42:05 AM

But, if memory serves me correctly didn't floppy drives use a floppy cable and it was different from a standard IDE cable? If so, are you really using an IDE cable connected to a floppy? I seem to remember that the connectors were different sizes as well.
m
0
l
Related resources
August 21, 2014 8:49:24 AM

floppy cables are different(smaller) then IDE. Also I think disabling it in bios is the way to go.
m
0
l
August 21, 2014 9:02:51 AM

Hi Guys,

Yes the cable that connects to the Floppy is smaller than the IDE cables that connect to the Hard Disk & CD-ROM, I think it is a 34-pin cable. I thought they were both called IDE cables.

I have tried disabling the Floppy in the BIOS but I still get the error. I will try and locate the Hardware ID number and report back.
m
0
l
August 21, 2014 9:13:17 AM

The hardware version is 002 (that's all I can find in Windows 95 regarding an ID number). It says no drivers are required for this type of device and that there is a conflict. I have tried to resolve this conflict but I still continue to see the yellow symbol.
m
0
l
August 21, 2014 9:15:37 AM

what does it say the conflict is? and is it an add-in IDE Controller or is it the onboard controller? also whats the exact make of the dell.
m
0
l
August 21, 2014 11:04:06 AM

Hi,

CMD PCI-0640 PCI to IDE Controller conflicts with the following:

Input/Output Range 01F0 - 01F7 used by: Standard IDE/ESDI Hard Disk Controller
Input/Output Range 03F6 - 03F6 used by: Standard IDE/ESDI Hard Disk Controller

I believe it is the on board controller. I cannot modify the resource settings for the CMD Controller, only the Standard IDE Hard Disk Controllers.

The computer is a Dell Dimension P100 X-BIOS A05.
m
0
l
August 21, 2014 11:06:36 AM

Now when I boot up there are (I think) four beeps followed by three beeps that continue playing in a looped sequence.
m
0
l
August 21, 2014 11:35:50 AM

Ugh. The days of dealing with Resource Settings XD So glad we next to never have those issues anymore...unless you load up your PC with so much stuff it runs out haha.

ok for the Beep codes. are the two sets of beeps fast or slow?
m
0
l
August 21, 2014 11:48:11 AM

I would say both the first four (?) beeps and the three continuous beeps are fast.

..beep..beep..beep..beep.. followed by:

....beep....beep....beep.... which plays continuously.

I wish this thing would just blow up, then I'll know for sure that the motherboard is dead.
m
0
l
August 21, 2014 1:34:35 PM

XD HAHA yea i feel ya. So 4 really fast ones and then 3 after...hmmmmm...I can't seem to find anything with beeps like those but then we are working with something around 20 years old. Internet didn't really exist that much then so might be hard to find. I could just disconnect anything unneeded and reseat the memory and any other add-in cards.


Ok so my first question should have been "What in the world are you using a Pentium 1 bases PC for? HAHA
m
0
l
August 21, 2014 1:47:39 PM

I've listened to the beeps again. It actually sounds like 3-2-3, meaning three quick short beeps, followed by two quick short beeps, followed by three short beeps (last three not as quick).

I googled 'Phoenix BIOS beep codes' (I'm sure it was a Phoenix BIOS) and found a table where 3-2-3 means 'Reserved' and it doesn't tell me anything else! Here is the link: http://www.bioscentral.com/beepcodes/phoenixbeep.htm
m
0
l
August 21, 2014 4:47:21 PM

Hmmm...any way you can make a recording of the beeping?
m
0
l
August 21, 2014 5:16:25 PM

You must have read my mind mate. I don't know how to go about doing that.

After hours of testing I think I can safely say that it's not the RAM, CMOS Battery, Graphics Card or CPU. I don't think it's the PSU either as the lights come on when I boot up.
m
0
l
August 23, 2014 11:05:01 AM

Yea its just trying to find a proper cmos code for a almost 20 year old PC is kinda hard haha. I'm a bit at a loss
m
0
l
August 23, 2014 3:45:48 PM

That's interesting. When I put the RAM into SIMM banks 2 & 4, or 2 or 4 with one stick - the beeping stops. Putting them into 1 & 3, or 1 or 3 with one stick causes the machine to resume beeping.

I have purchased a POST diagnostic card. Maybe it might help. I have cleared the CMOS by switching the jumpers on the motherboard. Can't think of anything else to try at this time.
m
0
l
August 24, 2014 11:01:03 AM

Oh snaps XD SIMM. I love how people talk about how you shouldn't mix RAM. These days your PC will run fine with mixed RAM. back then Nope. Had to be the same make, model, and size and they had to be put in as pairs haha.

Now when its in 2/4 does the PC start up?
m
0
l
August 24, 2014 1:10:23 PM

If I put them into 2 & 4 the machine will power on but there's no display, just the beep codes. I recall clicking on the Start Menu when the machine suddenly locked up and then powered off for no obvious reason.

When I power on, the disk drives and the motherboard appear to receive power (the lights on the drives and board come on). Is it possible that the Power Supply may be faulty even though the components are receiving power? I am hoping the POST card can help with this, apparently if the 12v+/12v-, 5v+/5v- and 3.3v+/3.3v- bulbs do not light up on the card then there is a short circuit with the PSU.
m
0
l
August 24, 2014 10:04:03 PM

yea i'd say get a PSU tester but i don't think they make them for the 20 year old AT PSU's lol
m
0
l
August 25, 2014 3:16:46 AM

I'll report back when I acquire the error codes that are generated by the POST card.
m
0
l
August 30, 2014 9:12:25 AM

Well I received my POST card in the mail today and it just seems like a complete waste of time. The User Guide is written in bad English and it doesn't tell me HOW to fix the problem, just refers me to a table that vaguely describes what the issue is and where the source of the problem might be located.
m
0
l
August 30, 2014 9:55:23 PM

A series of codes are generated by the POST card, the final one to be generated is: EE EF. The manual says in the table under AMI for the code EE 'Looking for a floppy diskette in drive A: Reading the first sector of the diskette. Under Phoenix 4.0/Tandy 3000 it says 'Shadow Boot Block'.

For the EF code, under AMI it says 'A read error occurred while reading the floppy drive in drive A. Under Phoenix 4.0/Tandy 3000 it says 'system memory test'.

Does anyone know what this means?
m
0
l
August 30, 2014 11:48:18 PM

My bet is that the floppy disk controller is faulty and that the motherboard needs replacing.
m
0
l
August 31, 2014 12:32:45 AM

And if you need a new floppy drive just buy a USB external one...

I'm not 100% sure if your motherboard has USB slots though...
http://www.newegg.com/Product/Product.aspx?Item=9SIA1PU...

Really I'd say your solution is to just get a new computer. There's no good reason to still be using a windows 95 machine. Unless you like collecting viruses or something.
m
0
l
August 31, 2014 1:36:44 AM

My old motherboard doesn't have USB slots. Thanks for the feedback though.
m
0
l
August 31, 2014 11:27:31 AM

yea i got one of those PCI testers...Waste of money! If i had the PC right here in front of me then i would be able to check things out more.

do you have any other SIMM Ram or no?
m
0
l
October 17, 2014 4:56:00 AM

I've tried other simm ram but I still get the same problem.
m
0
l
!