|
|
|
re: Question about 'Prevent file corruption problems'
Tuesday, November 4, 2003 at 11:24 pm
Windows XP Annoyances Discussion Forum
Posted by Grant
(1 messages posted)
All I can say is "what better way for a man to alleviate a multi-billion dollar
lawsuit than to make a crappy product that you will probably try to fix or replace
with another of his crappy products?" It's like I have the worst case of schizophrenia
in the world and I've been posting on this sight in my sleep for 2 yrs. I finally
got tired of not being able to burn anything more than 15kb before my PC/RW spit
out the cdr. This, I finally decided, was due to MS inability to supply a driver
that supports all the features for a number of different makes/models of CD-DVDROM
drives. Being one of the ecstatic millions of unlucky recipient's of the famed "oem
scam" systems I didn't get a whole lot of help from the PC distributor or the company
that made the CD-DVDROM drive either. By accident I found myself on Western Digital's
website looking for an overhaul kit for what sounds like a 1975 shovel- head firing
up where my hardrive used to reboot and came across the .ZIP file that is suppose
to fix the problem with our pal Williams' XP drivers. So I nabbed it, unzipped it,
read the install txt file and installed it along with the CONFIG.SYS\AUTOEXEC.BAT
file edits they said had to be done to make 'em run and support UDMA. So, needless
to say, if I've learned anything at all from using anything MS provides is to back
it up 5 times and hide another copy under you mattress. I reverse edited the config/auto
files to there original pristine disfunctional condition and rebooted. Got the chkdsk
prompt and it went off without a hitch. In, fact I've never seen chkdsk works so
fast. I tried to find what caused the chkdsk to even run as I didn't schedule it.
Got another prompt from windows' "found hardware" program. Upon investigation a Sony
memory stick got hooked up to my system and it was needing a driver and so was all
of my removable media and storage devices. Well to make an epic saga into a low-buck
paperback I back-peddalled a well executed restore point, ran another sector/recovery
scan, ad-aware scan, virus scan, McCafee quickclean, thouroughly checked the MMC
console and firewall logs and even did a completely unnecessary check back at Ole'
at the Windows' up-chuck site, rebooted, called a psychiatrist, swore off chemical
substance abuse (side effect Mr. G's technology), and went to bed. Next morning my
pc still still needed some time to reboot, only 3 of 5 processes completed and a
prompt "deleting index entry bootex.log in index $I30 of file 5/the file system was
corrupt and unreadable. Another 2 hrs, later it finally started after it tried and
did another chkdsk while I was gone. Now, upon 2clicking any file, search assistant
starts up because Search has become the default action in all my sub-menus, half
my background services won't run, my cable modem can't acquire an IP address, my
sound-card is staticy even during windows default sound scheme's, but, you can hear
a spider fart over my hard drive it's so quiet and evidently Western Digital makes
the M1A1-ABRAHMS tank of HDD's after a diagnostic scan mine is rating good to healthy
ratings in every test after 4 yrs. of family PC abuse and 4 OS. Just to put a twist
on this broadway show. I switched to XP Pro after my 2000 Pro had reduced me to a
slobbering idiot(again thank's to Bill's snake oil security patches). As if any of
you people are still reading, here I sit watching my system lose it's hardware/software
systems one at a time. I think when I get done printing these pdfs of MAC PC's and
Redhat Linux 9.0 I'll do one more chkdsk on the ol' girl and skip to ma loo with
my little plastic fortune to my local pc dealer. By the way NTFS here too and I think
I remember reading something at western digital or rarlab about a DDO device driver
for high volume harddrive's. Something about exceeding BIOS limits and instead just
recognizing 80 GB when you have 139 GB. In fact, I remember a couple of you mention
a 20% loss in accounting your HD space and according to them this appeared on harddrives
over 138GB. Anyway, keep posting guys I need ideas on how to make this thing really
run bad. Sorry for the 17 ton vent session. THANX!
n Friday, October 4, 2002 at 10:02 pm, Paul wrote:
>I have a question about Prevent
>file corruption problems:
>
>I have tried running the "new" CHKDSK under Windows XP using both the Error Checking
>tool in "My Computer/File/Properties" and from the command line.
>
>When I used the Error Checking tool (without selecting the Automatic fix of file
>system errors or the scan for bad sectors) XP displayed a dialogue with a sequence
>of messages, telling me that the Error Checker was performing phase 1 of its check,
>then phases 2 and 3 and finally a new dialogue appeared telling me that the check
>had been completed - and nothing more.
>
>When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the
output
>was more informative:
>
>"The type of the file system is NTFS.
>
>WARNING! F parameter not specified.
>Running CHKDSK in read-only mode.
>
>CHKDSK is verifying files (stage 1 of 3)...
>File verification completed.
>CHKDSK is verifying indexes (stage 2 of 3)...
>Index verification completed.
>Detected minor inconsistencies on the drive.
>CHKDSK is verifying security descriptors (stage 3 of 3)
>Cleaning up 33 unused index entries from index
>Cleaning up 33 unused index entries from index
>Cleaning up 33 unused security descriptors.
>Security descriptor verification completed.
>CHKDSK is verifying Usn Journal...
>Usn Journal verification completed.
>Correcting errors in the Volume Bitmap.
>Windows found problems with the file system.
>Run CHKDSK with the /F (fix) option to correct"
>
>My question is, which should I trust - the Error Checking tool (which I assume invokes
>CHKDSK in the background) or the command line? Or perhaps a third party program?
|
All messages in this thread [show all]
 |  | re: Question about 'Prevent file corruption problems' (Grant: Tue, Nov 4, 2003, 11:24 pm) |
|  | | Sins of NTFS (Down For The Count: Thu, Jan 22, 2004, 8:22 pm) |
|  | re: (Tong Narak: Tue, Jan 25, 2005, 6:43 pm) |
| |
| |
