Stop a project transfer from accessing the floppy drive

Why does the floppy drive wake up when the transfer dialog opens?

Windows probes every removable drive when a dialog builds its drive list, and an empty internal floppy cannot answer until its seek and read timeout expires, so the drive wakes for about 2 seconds before the transfer dialog finishes opening.

My Computer builds the same list, which is why the drive also gives one brief spin when you open it. A drive with no disk in it cannot answer the media check immediately, so the operating system waits out the drive's seek and read timeout, then lists the drive as empty. That wait is the sound you hear, and it repeats for every window or dialog that builds a drive list.

Nothing in the transfer software controls this. The probe happens while the dialog is being drawn, before any data moves toward the panel, and no setting in the software changes the drive's timeout. The documented cause of a slow drive list is one or more drives that cannot answer, which is exactly what an empty floppy is.

How do I rule out the panel link first?

Rule out the panel link first: the transfer dialog must target the panel, not an external memory device, and the panel must appear under Universal Serial Bus Controllers in Device Manager on a known-good cable.

1. Open the transfer dialog and confirm the target is the panel. An external memory target reads and writes a drive letter, and drive access is expected in that mode.
2. With the panel attached over USB, open Device Manager and expand Universal Serial Bus Controllers. The panel must be listed there by name.
3. Disconnect any external USB floppy. If the light and noise stop, the problem was the external drive and you are done.

Then open My Computer once with the panel still attached. If the panel entry is present and the internal floppy spins on the My Computer click too, the link is good and the probe is confirmed as a Windows behavior.

A link that enumerates but crawls once the transfer starts is a different fault; an HMI panel project download that takes 2 minutes covers that case.

Which symptoms point at the floppy and which point elsewhere?

Two symptoms point at the floppy probe: a drive light and whirr for about 2 seconds at each dialog open, and the same sound when you open My Computer; a light that burns for minutes points at the drive cable instead.

• About 2 seconds of light and whirr when the transfer dialog opens, with the transfer completing: the Windows media check on the empty internal floppy.
• The same brief wake when you open My Computer or any file dialog: the probe belongs to Windows and the drive, and any program that builds a drive list triggers it.
• A drive light that burns for minutes, or that comes on at boot and stays on: the data cable is attached upside down at one end, at the drive or at the motherboard connector. Power down and reattach it the right way up.
• No entry for the panel under Universal Serial Bus Controllers while the panel is attached: a USB link fault. Fix the cable, port or driver first; the floppy is unrelated to it.
• Drive activity after you select an external memory target: expected, because that mode reads and writes a drive letter.

Will reinstalling the software or swapping cables fix it?

Reinstalling the transfer software, swapping USB cables and reflashing the panel do not touch this fault, because the panel never asks for the floppy; the PC's drive probe is the only thing at work, so those steps only cost production time.

The probe reproduces with the transfer software out of the picture: open My Computer and the drive wakes the same way, with nothing running but the file window. A reinstall cannot change a behavior Windows performs before the software talks to the panel, and a new cable or port changes a link the probe never uses.

Spend the saved time on the link instead, because a wrong target and a failed enumeration are the two genuine transfer faults. If the worry behind the reflash is a panel that forgets its project between power cycles, that fault has its own fix in an HMI panel that loses its project after a power cycle, and it is unrelated to this drive noise.

How do I disable the floppy drive in Device Manager?

Disable the drive in Device Manager: open it from System in Control Panel, expand Floppy disk drives, right-click the drive entry, choose Disable and confirm; the change takes effect at once and reverses in under a minute.

1. Open Control Panel, open System, and start Device Manager from there.
2. Expand Floppy disk drives. If the class is missing, switch on the option to show hidden devices.
3. Right-click the floppy drive entry and choose Disable. Confirm the prompt.
4. Close and reopen the transfer dialog.

Check the result in My Computer: A: either disappears from the drive list or stops polling, and the drive light stays dark when the transfer dialog opens. To undo the change, return to the same entry and choose Enable. Try this fix first, because no reboot into BIOS is needed and nothing else on the PC depends on the entry.

How do I disable the diskette drive in BIOS permanently?

Set the diskette drive to disabled in BIOS setup for a permanent repair: a drive disabled in BIOS never reaches Windows, so no drive list can probe it; enter setup with the key the POST screen shows, save, and exit.

1. Reboot the PC and enter BIOS setup with the key the POST screen shows.
2. Find the drive configuration page and the diskette entry. Labels vary by BIOS; look for the floppy or diskette drive setting.
3. Set it to disabled, save, and exit.
4. Boot Windows and confirm A: no longer appears in My Computer.

One condition applies: if this PC still boots from a floppy or reads driver and firmware disks from one, leave the drive enabled or undo this change, because a drive disabled in BIOS cannot be read by anything in Windows. Write the change into the machine's maintenance notes so nobody reverses it by accident during later troubleshooting.

If the only job left for the drive is the probe, take it out of the machine's drive list. A standard 3.5-inch HD diskette stores 1.44 MB, and data retention limits of 3.5-inch diskettes are the reason legacy media is a poor home for anything you still need.

Recommendation: start with the Device Manager disable when you want a change you can reverse in a minute, and move to the BIOS diskette setting once nothing on the PC reads floppy media; write the BIOS change into the maintenance notes either way.

What does the 2-second delay cost in a worked example?

On a line that opens the transfer dialog 10 times per shift across 3 shifts and 250 production days, the 2-second probe wastes 15,000 seconds a year, about 4.2 hours of pure drive spin, and the Device Manager disable removes all of it.

The scenario: one engineering PC serves a packaging line. After every changeover the technician pushes a project update to the panel, which means opening the transfer dialog 10 times per shift. Three shifts run each day over 250 production days.

• Per shift: 10 opens × 2 seconds = 20 seconds of drive spin.
• Per day: 20 × 3 = 60 seconds.
• Per year: 60 × 250 = 15,000 seconds = 250 minutes, about 4.2 hours.

The only variable is the number of dialog opens per shift; the probe length is set by the drive's timeout, so 20 opens per shift doubles the loss to about 8.3 hours a year. The Device Manager disable removes the whole amount in one change, and it also stops the wear each spin puts on an aging drive.

How do I prove the fix holds after a reboot?

Prove the fix with three checks: the dialog opens with the drive light off, the panel still appears under Universal Serial Bus Controllers, and a full transfer completes and runs on the panel; then reboot and repeat all three to confirm the change persisted.

1. Open the transfer dialog and confirm the drive light stays off and no whirr comes from the drive.
2. Open Device Manager, expand Universal Serial Bus Controllers and confirm the panel is still listed.
3. Run a full transfer to the panel and confirm the project loads and runs.
4. Reboot the PC and repeat steps 1 to 3.

If the Device Manager disable reverts after a reboot, or the light still comes on, move to the BIOS change; a drive disabled there sits outside every drive list Windows builds. The fix holds when the dialog opens silently, the transfer completes, and the result survives a reboot.

Questions