ScanDisk

[bug]

06.02.21

In w98.2 if the puter locks up or otherwise crashes, running ScanDisk finds and fixes errors on hard drive....
? Is there a way to find out what specific errors it finds and how/ what it did to fix them. Some programs (norton systemworks) just delets stuff and terms it fixed.

In searching scandisk, i noticed others mentioning problems leading to forced safe mode booting and then problems with their mouse not being recognized, I have had similar problems with my usb logitech trackball, if you just plug in a normal ps2 ball mouse it will be recognized... (guess the usb-driver stuff is not accessed in safe mode.) This leads to an unrelated question, what is the technique using just keyboard to navigate desktop icon/programs and start/ect, like what are the keyboard shortcuts to access/activate as one would do with a mouse, but w/o a mouse all one can use is the keyboard.

Next unrelated question what program will destinguish a possible problem between the gpu vs monitor (so one can determine which is going bad [ in my case the 7 yr old monitor occasionally blacks out, needing to be turned off and them back on to see display.]) Dxdiag indicates DX9c is working ok in display, and still get same occasional black-screen problem with various gpu driver generations. Updating monitor (viewsonic gs-815) driver does not correct the black-outs.

[GaryRouth]

Hi bug

To find out what Scandisk does when it runs, from the ScanDisk startup screen, choose Advanced, and under the "Log File" option, select either "Append to log" or "Replace log" depending on whether you'd like each scan added to the log, or a new log overwriting the older each time. You'll find the file "ScanDisk.log" stored in the root directory of your hard drive - you can open it with NotePad to read it. For all the details on ScanDisk, see the Microsoft Knowledge Base article http://support.microsoft.com/default...b;en-us;186365

USB mice and keyboards often need to be enabled in your computer's Bios to be available in Windows 98's Safe Mode (the items are usually labeled "Legacy USB support"). Otherwise the USB support isn't available until Windows is booting in "normal" mode.

You certainly can use a keyboard to navigate in Windows - in just about any mode I can think of (provided your keyboard is recognised). Use the tab, arrow, and Enter keys for most moving around. The Windows key can be handy for opening up the Start menu. Various Windows 98 keyboard shortcuts are listed in this article http://support.microsoft.com/default...;en-us;q126449

If you either have trouble with the USB settings in the Bios, or just would rather not bother with the Bios at all, you could simply keep an inexpensive PS/2 keyboard around & plug it in when you wish to boot into Safe Mode (you'd unplug your USB keyboard when using the PS/2). Same is true for a PS/2 mouse. Plug PS/2 peripherals in only when the power is off.

The best test for diagnosing your video problem would be to borrow another monitor of the same type (that ViewSonic is a CRT, right?). If all is well with a different monitor, then it's time to replace the ViewSonic.

If the trouble continues, you could try different video drivers, but it'd be more likely time to replace the video card. If the computer is as old as the monitor, though, don't spend much on the replacement, and make sure to get an older card that matches the AGP/PCI slot on your motherboard.

Best of luck
. . . Gary

[bug]

06.02.26

... ! 14 MB of
The C:\WINDOWS\APPLIC~1\MOZILLA\PROFILES\DEFAUL~1\MOZ\NGUYFU4C.SLT\CHROME
folder could not be opened in MS-DOS mode because its complete short name
was longer than 66 characters.
Resolution: Ignore this error and continue
Results: Error was corrected as specified above.


Aparently there is a problem with extended > 66 character names.
Is there a work around so MS-DOS can recognize long file names, because nearly every time scandisk is doing nothing but ignoring aparent problems and claimes it found and fixed them.
I dont think i have ever used MS-DOS... in w98.2

Also the Advanced settings in Standard Scan: Display summary (Always)
Log file (Append to log)
Cross-linked files (make copies)
Lost file fragments (convert to files)
Check files for (Invalid file names, Invalid dates and times, Duplicate names)
Check host drive first
Report MS-DOS mode name length errors

... ? would there be better items to select for the Standard scan ?

And in Thourough Scan:

Areas of the disk to scan (Syatem area only) vs System and data areas
( ? Do not perform write-testing or Do not repair bad sectors in hidden and system files) what would be the merits in enabling either/both of these?

[glc]

There is nothing you can do about the filename length error except tell it not to report name length errors. This has no effect on system operation. Windows has no problem with long filenames, it's just the short name translation to be readable in DOS.

[skykissme]

Only way I can think of Bug is to rename your files on Windows, reduces all the white space, ie My Documents = MyDocuments, Windows will still recognise it. Otherwise, you will need ScanDisk Linux version, it doesn't care of how long your filename will be.

[glc]

Reducing white space does not change the short file name - it's still gonna be mydocu~1 either way. It's path depths that's getting it over 66 characters.