Floppy light comes on for no apparent reason

Status
Not open for further replies.

barebear

Posts: 64   +0
I'm running Xp SP2 fully updated on a system w/ no malware issues of any sort (anti-virus, antispyware (including rootkit protections) is in place and fully updated).

The sytem configuration has been in place for at least 2 years and is configured is as follows:

Primary IDE master = C:

Primary IDE slave = E: ( Plextor 708A DVD-RW )

Secondary IDE master = F: ( TDK 48x CD-RW )

Secondary IDE slave = D: ( an 80GB 7200 rpm 8MB cache Western Digital, exactly identical to C: )

I don't use " My Documents" on C: so as to preclude losing everything if the drive should die. I accordingly created "My Documents" on D: and every night that folder is backed up to an external USB HD identical to C: and D:

My issue:

In the last week or so I am noticing that sometimes ( but not always) when I access D: either through "My Computer" or a shortcut to D:\ (file/folder) that is on my desktop, I hear a click and the light on my floppy drive comes on. When it occurs,this event repeats once or twice and then stops until I again access something on the drive.
This event also, but not always, occurs when I am not knowingly accessing D: at all---such as while I'm writing this in Notepad to be able to copy/paste into the message box of the forum I'm contacting.

There doesn't appear to be any negative impact on the functioning of the system in terms of any performance issue,
but it is an irritation that I want to correct.

I have so far tried all of the following:

I do not have any *.lnk references to A: that are not "Send To" or similar "shortcuts".

I have, without success, so far gone to Start>Properties>Customize>Advanced>Recent Documents>Clear List. and re " may be a reappearance of the NTFS bug on showing color. Explorer, Tools, Folder Options, View uncheck
"Show encrypted or compressed NTFS folders in color", have also done that

I also have done Right click the My Computer icon/Manage. Services and Applications/Services/Shell Hardware Detection and set it to Automatic. ----it was already "Automatic" when I checked the setting.

I then tried Start/Run/gpedit.msc/User Configuration/Administrative Templates/Windows Components/Windows Explorer. In the right pane double click Hide these specific drives from my computer. Enable then use the drop box.
This seemed to have worked till I unhid the drive, but is not a viable solution because I use floppies for small data files that I'd otherwise be wasting a CD on; there also are occasions when I need to see what is on a particular floppy.

Since there are occasions when I want to boot from a floppy (testing rescue disks, etc), I don't want to change the boot order in the bios or disable "floppy drive seek at boot".

The floppy works just fine--I can read, write, and format with no problem.

Summary: Given all of the preceding, please advise possible causes and cures for the floppy light coming on
 
Interesting...

I imagine you've already explored these options, but the only plausable reason I can think of is there's a program responsible. Maybe your virus scanner is doing this?

Other than that, I don't have much of an idea. :\
 
Hi Rick,

Thanks for responding! I run V-Com System Suite Pro 7.0 and use its anti-virus feature.

I've been running it for months before the floppy light issue arose ( maybe 10 days ago? )

I believe its Trend Micro's stuff; might there be a specific significance that you're aware of there?

Best, Peter
 
I think I found the answer !?

Hi Rick,

I believe I may have discovered a way to stop the floppy light.

It starts with something I found on the internet:

Click Start/Run/gpedit.msc/User Configuration/Administrative Templates/Windows Components/Windows Explorer. In the right pane double click Hide these specific drives from my computer. Enable then use the drop box.

The refinement is that instead of enabling and then using the drop down box to exclude A:, you simply click on the "Disabled" box and leave it at that.

Since taking that action, I do not get floppy light activity anymore when going into D: . Time will tell whether or not I get it at other times---will keep you advised.

I haven't rebooted since doing "disable"; hopefully nothing changes when I do---will also advise
 
Hi Rick,

Guess it was too much to hope for---rebooted this am and it started again.
Guess I'm just going to have to put up with it?

Any ideas ?
 
A total 'shot in the dark' idea...

Insert a blank floppy disk.

Scroll down to the bottom of this page, download and run the utility. http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx

In the "Volumes" menu, click "No Volumes". Open the menu again and click "Volume A: Removeable"

Let the program run and the next time your floppy light comes on, see if File Monitor displays any details. If it does, it will show you what program is attempting to read/write to your floppy drive (I'm assuming this is the reason behind the light coming).
 
Hi Rick,

Have done as you instructed; in top box "network' was checked--I left it alone.
In bottom I first clicked "no volumes" and then "A". There now are checks next to "network" and "A"; I've left the program open w/ the main screen showing.

I have accessed my D: several times but the floppy light hasn't come on?! I will keep you posted re what goes on--

A question--should I reboot, leave a blank floppy in the drive,, open Filemon again making sure that only "network" and "A" are checked, and see what happens, or is it better that I just use the system for a while w/o rebooting,etc.?

Reason I ask is of course that I got rid of the light per an earlier post, but it came back after rebooting.

Will await your further instructions and report any odd developments in the meantime.

Best, Peter
 
Hi Rick,

YIKES! I finished posting and closed my browser, then went to open my D; and the light came on along w/ a bunch of entries in Filemon relating to Executive Diskeeper trying to access A:?! I've copy/pasted everything, will wait to hear your comments. ( I've had Diskeeper running for several months w/o the floppy light coming on, so am quite concerned as to implications and what to do?!)

1 5:05:25 PM DkService.exe:652 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
2 5:05:26 PM DkService.exe:652 QUERY INFORMATION A:\ SUCCESS FileNameInformation
3 5:05:26 PM DkService.exe:652 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
4 5:05:26 PM DkService.exe:652 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
5 5:05:26 PM DkService.exe:652 CLOSE A:\ SUCCESS
6 5:10:31 PM DkService.exe:652 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
7 5:10:32 PM DkService.exe:652 QUERY INFORMATION A:\ SUCCESS FileNameInformation
8 5:10:32 PM DkService.exe:652 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
9 5:10:32 PM DkService.exe:652 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
10 5:10:32 PM DkService.exe:652 CLOSE A:\ SUCCESS
11 5:10:36 PM DkService.exe:652 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
12 5:10:37 PM DkService.exe:652 QUERY INFORMATION A:\ SUCCESS FileNameInformation
13 5:10:37 PM DkService.exe:652 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
14 5:10:37 PM DkService.exe:652 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
15 5:10:37 PM DkService.exe:652 CLOSE A:\ SUCCESS
 
Hi Rick,

I'm a beta tester for Diskeeper--called the co.---they're aware of a problem w/ Diskeeper trying to access A:, working on a new build due out in a few days.

They claim no system stability issue involved.

Please let me know you got this and prior post w/ Filemon data--I will keep you informed of dvelopments w/ Diskeeper,etc

Wait to hear from you, best, Peter
 
An interesting lead!

Some quick searching on Google reinforces DK as a possible culprit:

twl845 @ wilderssecurity.com said:
lodore @ wilderssecurity.com said:

The Diskeeper manual states:
By default, the summary file is written to your floppy drive (A:). This dialog box can be edited to specify another volume, directory path, and filename. However, the summary file cannot be written to the volume upon which you are running Boot-Time Defragmentation. Also note that the filename should not contain any spaces.
Even though this shouldn't be the cause (for boot-time defrag only), try disabling this option if it is checked, "Produce a summary log file". This is the only related option I see in DK, so its worth a shot.

Also, I don't know if such a thing could happen, but make sure DK isn't somehow trying to defrag your A:

LoL...
 
1 good reason

This has been hard to follow,but during bootup all drives are checked
and the lights flash.My floppy even grinds a bit.
This means their in working order.
So,Do you mean it flashes at other times,like opening D Drive ?
So if it's only at bootup,relax they all do it.Be glad it does.
 
Hi Rick and Zipperman,

Rick--that log file option had never been checked; I went and looked.

Zipperman--after a reboot with the usual flashing/click a couple of times, the first time I access my D: the light will come on and go off twice. Then it seems to be ok till the next reboot --at that point the whole cycle repeats, including the first time I access my D: the light will come on and go off twice.

I'm going to reboot a couple of more times and see if the pattern holds--will advise developments shortly----would have replied much sooner, but couldn't load the website--would just get a "done" w/ a blank screen.

I'm now going to do a 1 time boot defrag w/ nothing but the paging file and MFT options enabled, and then see how the floppy behaves after completion of reboot ( light coming on randomly or not), and then when I access D: for the first time after reboot.

Will advise results shortly; in the meanwhile any further comments/ideas?

Goalie--just saw your post; FYI in case it gives any light on the issue, I'm running DK 2007 Premier 11.0.693.0

Best, Peter

Yikes again--while I was writing this and bouncing back and forth between DK and here, Filemon came up w/ :

1 8:49:43 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001
2 8:50:18 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001
3 8:50:26 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001
4 8:59:55 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001
5 9:50:53 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001
6 9:50:58 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001


Comments/ideas?---What now?

Am going to do the reboot, boot defrag thing now and then report back
 
Zipperman, I hope that was meant to be funny. It sure wasn't informative.

Rick: Yes a defrag is possible. Of obvious limited effectiveness and speed, however.

From corporate experience, I can tell you Diskkeeper accesses drives pretty much anything at random and for fun until properly configured. As we have it configured by GPO (which I don't have access to view), I cannot tell you however how to get DK to quit that ____. My general recommendation is to seek another product, as I've seen many problems beyond this one caused by DK. When it works, it works OK, but much like Symantec when it goes bad it goes really really bad.
 
?!

Hi all,

Decided to insert the floppy and access D: one last time before reboot.
Here is what log file now looks like in case it helps?

1 8:49:43 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001
2 8:50:18 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001
3 8:50:26 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001
4 8:59:55 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001
5 9:50:53 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001
6 9:50:58 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001
7 9:56:40 PM DkService.exe:612 OPEN A:\ NO MEDIA Options: Open Directory Access: 00100001
8 9:56:56 PM DkService.exe:612 OPEN A:\ REPARSE Options: Open Directory Access: 00100001
9 9:56:57 PM DkService.exe:612 READ A: SUCCESS Offset: 0 Length: 4096
10 9:56:57 PM DkService.exe:612 READ A: SUCCESS Offset: 4096 Length: 4096
11 9:56:57 PM DkService.exe:612 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
12 9:56:57 PM DkService.exe:612 QUERY INFORMATION A:\ SUCCESS FileNameInformation
13 9:56:57 PM DkService.exe:612 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
14 9:56:57 PM DkService.exe:612 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
15 9:56:57 PM DkService.exe:612 CLOSE A:\ SUCCESS
16 9:56:59 PM DkService.exe:612 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
17 9:56:59 PM DkService.exe:612 QUERY INFORMATION A:\ SUCCESS FileNameInformation
18 9:56:59 PM DkService.exe:612 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
19 9:56:59 PM DkService.exe:612 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
20 9:56:59 PM DkService.exe:612 CLOSE A:\ SUCCESS


Best, Peter
 
Hi all,



Heres the log of what happened after the boot defrag/reboot process and the first time I accessed D:, and then a folder in D:


1 10:18:52 PM DkService.exe:624 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
2 10:18:52 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileNameInformation
3 10:18:52 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
4 10:18:52 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
5 10:18:52 PM DkService.exe:624 CLOSE A:\ SUCCESS
6 10:19:02 PM DkService.exe:624 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
7 10:19:03 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileNameInformation
8 10:19:03 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
9 10:19:03 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
10 10:19:03 PM DkService.exe:624 CLOSE A:\ SUCCESS
11 10:19:12 PM DkService.exe:624 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
12 10:19:13 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileNameInformation
13 10:19:13 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
14 10:19:13 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
15 10:19:13 PM DkService.exe:624 CLOSE A:\ SUCCESS
16 10:19:23 PM DkService.exe:624 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
17 10:19:24 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileNameInformation
18 10:19:24 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
19 10:19:24 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
20 10:19:24 PM DkService.exe:624 CLOSE A:\ SUCCESS
21 10:20:15 PM DkService.exe:624 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
22 10:20:16 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileNameInformation
23 10:20:16 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
24 10:20:16 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
25 10:20:16 PM DkService.exe:624 CLOSE A:\ SUCCESS
26 10:20:23 PM DkService.exe:624 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
27 10:20:24 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileNameInformation
28 10:20:24 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
29 10:20:24 PM DkService.exe:624 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
30 10:20:24 PM DkService.exe:624 CLOSE A:\ SUCCESS

The floppy light comes on the first 2 times I access D: after a reboot, and then seems to stop acting up till after the next reboot.

Wait to hear from you guys...
Best,Peter
 
Hi all,

More data (note the times re this data and that in previous posts)
that turned up with the same BLANK floppy in the drive?!
Note: Yesterday I had put in the floppy that refers to Barb Bear Book and opened it, then closed My Computer (where I'd accessed A: from), and then removed the floppy--it hasn't been put back in the drive since then. I did just finish making/sending an RAR file, but the floppy drive was in no way involved w/ doing that

1 10:59:01 PM DkService.exe:608 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
2 10:59:02 PM DkService.exe:608 QUERY INFORMATION A:\ SUCCESS FileNameInformation
3 10:59:02 PM DkService.exe:608 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
4 10:59:02 PM DkService.exe:608 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
5 10:59:02 PM DkService.exe:608 CLOSE A:\ SUCCESS
6 11:05:57 PM DkService.exe:608 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
7 11:05:59 PM DkService.exe:608 QUERY INFORMATION A:\ SUCCESS FileNameInformation
8 11:05:59 PM DkService.exe:608 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
9 11:05:59 PM DkService.exe:608 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
10 11:05:59 PM DkService.exe:608 CLOSE A:\ SUCCESS
11 11:06:05 PM DkService.exe:608 OPEN A:\ SUCCESS Options: Open Directory Access: 00100001
12 11:06:06 PM DkService.exe:608 QUERY INFORMATION A:\ SUCCESS FileNameInformation
13 11:06:06 PM DkService.exe:608 QUERY INFORMATION A:\ SUCCESS FileFsVolumeInformation
14 11:06:06 PM DkService.exe:608 QUERY INFORMATION A:\ SUCCESS FileFsAttributeInformation
15 11:06:06 PM DkService.exe:608 CLOSE A:\ SUCCESS
16 11:07:00 PM Winrar.exe:4000 OPEN A: SUCCESS Options: Open Access: 00100180
17 11:07:01 PM Winrar.exe:4000 QUERY INFORMATION A: SUCCESS FileFsVolumeInformation
18 11:07:02 PM svchost.exe:1092 OPEN A:\BARB BEAR BOOK.ZIP NOT FOUND Options: Open Access: Read-Attributes

omments, ideas? All this data has been/is being sent to Diskeeper

Can you say "buggy software" LOL ---this is a drag--never had trouble w/ DK before, and I mean at least 5 earlier versions over the last couple of years or so
 
Greetings all,

Goalie, DK may have bugs but they don't loaf--its 1245AM Fri PST and I just got an automatic update from them (being sent to all users).
I've installed it, haven't rebooted yet (no reboot required after DK update, and system doing scheduled maintenance), but when I access D:, or my Intel PC camera or my Fuji6800 digital camera (played a hunch and found out that DK attempted to write to A: when these 2 were opened, also when closed), no floppy light or click--at least so far.
Going to bed, will reboot in AM and advise details.

Best, Peter
 
Now we have 2 problems

Is D a HD partition or an Optical drive,or somwthing else.
This is an unusuall happening.
Can you read floppys with data ?
Why not start another post about your browser problem ?
=================
I am not trying to be funny.Are you ?
You don't defrag hardware (floppy drives),if thats what you suggested
 
Hi Zipperman, Hi Rick, Hi Goalie,

Zipperman ---- The sytem configuration has been in place for at least 2 years and is configured is as follows:

Primary IDE master = C:

Primary IDE slave = E: ( Plextor 708A DVD-RW )

Secondary IDE master = F: ( TDK 48x CD-RW )

Secondary IDE slave = D: ( an 80GB 7200 rpm 8MB cache Western Digital, exactly identical to C:)

I don't use " My Documents" on C: so as to preclude losing everything if the drive should die. I accordingly created "My Documents" on D: and every night that folder is backed up to an external USB HD identical to C: and D:

I never even thought of defrag re a floppy; per my original post > >The floppy works just fine--I can read, write, and format with no problem.

I don't have a browser problem?! The attachment is in your honor LOL.


Rick---I am delighted to tell you that the update which DK sent me last nite---see my previous post---works! The floppy light no longer comes on when accessing D:, my Intel PC camera, or my Fuji (all mentioned in my previous post. I consider the issue resolved since the system has run flawlessly all day long.

Best to all and thanks for the help!, Peter
 
Thanks for explaining

Haveing 2 topics in 1 post can be confuseing.I was mainly concerned with
your floppy problem.then along comes
My Documents problem.
Wasn't it originally on your Desktop ? Mine always has been.
It's an easy fix as my picture shows.I regularly move ant important files off of C: to various locations.If it's a picture it goes to "New Pics" folder on D:
I also use a rw disk for this situation.
I would like to stop them from going there as i don't send them there.
Glad to see your floppy is fixed as it's still a necessary hardware.
If you go Sata,you'll need it.
Heres some My Documents options.
 
Hi Zipperman,

Of course I have the My Documents on C: that is a part of Windows! I was just relating that to protect myself, I created another My Documents on D:, got rid of the C:\My Documents shortcut on the desktop, and replaced it w/ a shortcut to D:\My Documents, where I keep everything---that way everything is on the D: and if the C: should die, I haven't lost everything in C:\My Documents--that folder still exists, I just don't use it. Then, because I'm paranoid LOL, I back up D:\My Documents automatically every night to G: which is an external USB HD identical in all respects to C: and D:

Best , Peter
 
zipperman said:
This has been hard to follow,but during bootup all drives are checked
and the lights flash.My floppy even grinds a bit.
This means their in working order.
So,Do you mean it flashes at other times,like opening D Drive ?
So if it's only at bootup,relax they all do it.Be glad it does.
some motherboard BIOSes allow you to turn off check floppy at boot up.
if you're light stays on all the time, your cable is backwards.
 
Bare...
I am curious and not being critical, but I wonder why you have the ROM drives attached on the same IDE channel as your HDD's ? This could cause some issues for your machine .

Also, I may have missed it , but does DK offer an option in Preferences/Options to allow you to shut off Defragging/accessing the A:\ drive ?
 
Hi Liquidlen,

The TDK burner on secondary IDE has to be a master, therefore D: is slave--especially since I only use it as a data drive.

Both Plextor and TDK are internal units; to repeat myself from a prior post, I've run that configuration for several years w/ no noticeable ill effects

BUT

I am EXTREMELY interested in what and how this could cause issues for my machine per your comment!

Please be kind enough to respond in detail at your early convenience---I apologize for taking so long to respond, but was off to work when I first saw your post around 1030AM PST

As for DK--there never was an option to access A: in the first place--the floppy light issue came from an update from them at the end of January--it proved to be flaky and was superseded by an update 48 hrs ago that totally resolved the floppy light issue.

Wait to hear from you, best , Peter
 
Status
Not open for further replies.
Back