Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Error Messages

Feb 29, 2004 11:02PM PST

I am being asked to run Scandisk and at about 70+% completion, a message appears indicating that an "invalid long filename entry" was found and defrag is required. Defrag then indicates a bad cluster. Now whenever the computer is in use and I click or hit "enter" I receive the blue screen and the error of disk write error - unable to write to disk.

Can anyone point me in the direction of a solving this short of a reformat?

Discussion is locked

- Collapse -
Re:Error Messages
Feb 29, 2004 11:14PM PST
- Collapse -
Re:Error Messages
Mar 1, 2004 4:38AM PST

My problem same as posted , being asked to run Scandisk and with about 70% of and a message to free the disk appears when I do, I get the blue screen and by clicking any key it gets ok,
I use windows 98 second version with Pentium 3
hard disk 10gb, it happens mostly when I am running internet explorer,
Please help me with a solution
Thanks & regards

- Collapse -
If a solution is posted, would you use it?
Mar 1, 2004 6:28AM PST

I offered one, but your post seems to indicate you either didn't read it or it didn't apply.

Tell more.

Bob

- Collapse -
Re:If a solution is posted, would you use it?
Mar 2, 2004 2:09AM PST

Bob this person also indicated running internet explorer, which you should not have anything running when scandisking! You may have to perform a thorough scandisk to see the actual error, if bad data, or unsupported long file name, or bad sector. Long file names are not errors and you can ignore them. By running any program, you are writing data to your disk and it will change constantly, and the scandisk procedure will become a time consuming process, you can use ctl-alt-del keystroke to end tasks, with the only tasks needed to remain open are explorer, and systray. Once you complete this procedure you can indicate the actual error you are receiving.

- Collapse -
The first words are "My problem same as posted ,"
Mar 2, 2004 2:23AM PST

Since they lead off with this, then it becomes a simpler issue they need to find the invalid file name.

If they flubbed their post and "My problem same as posted ,", then they need to get back in here and work the issue.

Bob

- Collapse -
Re:The first words are
Mar 2, 2004 2:31AM PST

Hi - I am the guy with the original problem. I am still stuck perhaps you can help. I ran thru both Norton Virus detector and Norton Disk Doctor - all tests can out fine. After that I hit "restart" and the machine rebooted and came up with the statement "one or more drives may have developed bad sectors...run ScanDisk". It then automatically ran and although it did not indicate any problems, it did go immediately into Defrag. I walked away and came back later to find the machine had completed the task and then was loading the desktop when it then displayed the blue screen with "unable to write to disk - hit any key" I did and now it is running - but I am sure it will do the same thing when I reboot

- Collapse -
Scandisk may not report errors on boot.
Mar 2, 2004 2:40AM PST

That feature is one you see when you run it manually. On boot, MS (right or wrong) decided not to bother telling the user any news about the results.

The issue can be any number of items from a missing/corrupt motherboard driver, an IDE cable, motherboard issue or a failing hard disk.

Nothing in your posts gives any weight to which item it could be.

If this was my machine, I'd first fit a shiny new 80 conductor IDE CABLE and retest. Next I'd find the drive makers DRIVE FITNESS TEST to see what it things. Motherboard BIOS and drivers are never out of date on my machines and I already would have run SFG to see if the OS thinks its ok.

Bob

- Collapse -
(NT) TYPO. "SFG" s/b "SFC
Mar 2, 2004 2:45AM PST

.

- Collapse -
BIOS, Motherboard drivers noted at...
Mar 2, 2004 2:44AM PST