Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Floppy drive problem

Featured Replies

I've got a problem that I hope [b:08e4fd0609]SOMEONE[/b:08e4fd0609] can help me with. My floppy drive under WinME was locking my system whenever I tried to access it. And I mean a total system lock, no mouse or anything. I was hoping that a fesh install of WinXP when I got it would fix the problem. Unfortunately, no go.

The reason I'm having trouble tracking down the problem is that when I try and access a disk:

  1. In a normal start, the system locks
  2. Using msconfig.exe and disabling everything in the selective start, the system locks
  3. In Safe Mode, it reads the drive fine
  4. Booting from a floppy, it accesses the disk just fine
    [/list=1]
    Does anyone have any ideas of what the problem could be? :confused
    Thanks in advance.

If you tried both fresh installs of WinME and WinXP, and you still get a complete system lock-up when accessing the floppy drive, then it sounds like a hardware problem. Bad IDE cable probably?

  • Author

That's a possibility I hadn't tried. Geez, you'd think after working with these buggers for over 20 years, I'd have thought of that. I'll give it a try.:bash

When you are getting frustrated out of your mind, then it is easy to forget stuff that is right in front of your face. LOL

Rick

Bad IDE cable on a floppy drive? Not unless he's got a SuperDisk or something.. It sounds like he may have a bad cable or the drive connected to the wrong connector. It has to be connected AFTER the twisted section for drive A:, unless you've got floppy swap enabled in the BIOS. The system would boot fine but Windows will look for A: in the wrong location. I suspect it would also give an error under Device Manager as well if it ever booted into Normal Mode. Get a new floppy cable and connect it AFTER the twist and see if it helps.

  • Author

I figured he probably meant floppy cable.Oddly enough, Windows reports the floppy drive as working just fine. It's only when you try to access a disk that the lock happens.I've tried a different floppy drive to no avail, but the cable had completely slipped my mind. Fortunately, I live in a house with 3 systems, so it's no problem... acquiring another cable. :)

Well hold on one min guys....When you go to acsess the drive do you get any light or activity on the drive while its locked up. If you do then this has nothin to do with the cable. As far as I have ever seen if you have tried two fresh OS installes and your getting activity on the drive when try to acsess it, then its the drive. They cost 15 bucks go get a new one. [b:48cad05970]Now-[/b:48cad05970] If your not getting any activaty and its locking up then I would have to refer to posted replys above.

-Chris

  • Author

I get the light, but it's not the drive. That was my first thought, but I've swapped the drive with another one in the house. If it were the drive, then the problem should have transferred over to the other system. But the drive that I know is working still locks up my system. The one that I was getting the lock ups on works fine in the other system.

Think u all are forgeting something.

The drive boots in dos + it works in safe mode!

So drive & cable are ok.

It's a windows problem. Wrong drivers or some conflict.

  • 6 years later...

My solution is yanking out the fdd cable and tell the BIOS to disable the drive totally. Most modern BIOS's boot to USB flash drive. The 256m or even 128m are dirt cheap. If you need a disc, make a bootable CD. FDD's are OLD and unreliable (both drives and disks), why fight it?

My 2 cents worth.

Sakui

Think u all are forgeting something.

The drive boots in dos + it works in safe mode!

So drive & cable are ok.

It's a windows problem. Wrong drivers or some conflict.

Agreed... check for Conflicts (IRQ, DMA, etc). New hardware added recently maybe? Check that BIOS and REAL hardware settings. Windows only uses what it's told to, ya know... One-by-one, you'll find the culprit. :thumbup
My solution is yanking out the fdd cable and tell the BIOS to disable the drive totally. Most modern BIOS's boot to USB flash drive. The 256m or even 128m are dirt cheap. If you need a disc, make a bootable CD. FDD's are OLD and unreliable (both drives and disks), why fight it?

My 2 cents worth.

Sakui

Ehm, this thread is over 6 years (!) old... :whistle::wacko:

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.