But, my systems can run boot-time defrag. He probably figures, what a bone-head.Īnyway, I do appreciate the quick response. I informed the tech of this, but haven't heard back. I was hoping to get an error.txt log to send to him. This had trashed my partition twice before. For the third time, I imaged my XP SP1 partition, installed Diskeeper 7.413, and ran boot-time defrag. No problems, but I'll be dern if I could see anything about reading past cylinder 1023.Ģ. To make a 15 minute conversation short, he sent me Maxtors diagnostic utility and I ran it. "Well it won't work if it doesn't" How do I find out? "A properly configured system can read past cylinder 1023, does yours?" Gee, I don't really know. "Do you know what that means?" I said maybe not, admitting my stupidity. Is your system properly configured?" I don't know. "We've tested boot-time defrag on hundreds of properly configured XP SP1 systems without a problem. The tech was a bit agitated and jumped over my head with his first sentence. They called me that same morning! Impressive!
#DISKKEEPER LITE 7.0 SOFTWARE#
I informed Executive Software of this potential problem via E-mail and gave them my phone number. OK, I have had two things happen since my original post:ġ. (Always sound advice, but with SP1, you'll use the backup.) IF YOU RUN DK BOOT-TIME DEFRAG ON XP SP1, BE SURE YOU HAVE A CURRENTīACKUP. I have downloaded a demo copy of Perfect Disk and plan to switch This is atīest unlikely since the problem only occurs with SP1 installed, and onlyĪffects boot-time and not online defrags. I've received has been that it might be errors on my HD. I have opened an incident with Executive SW. Partition (multiboot), chkdsk still finds no problems, but some systemįiles don't compare (eg, significantly different lengths) and have Looking that the destroyed system disk from another XP One time it was HAL.DLL that was clobbered, another time System, the problem is bad enough that the system refuses to boot, even Within a couple of hours, with normal activity on the Sign of trouble is that sigverif begins to report that some system filesĪre "unsigned" - actually it not just the signature, but the whole file Chkdsk (eg, /v/f) shows no problems eitherīefore or after the boot-time defrag. I have repeated this failure three timesįrom clean XP installs. With SP1 installed, online DK defrags seem fine, but runningīoot-time DK trashes the disk. SP1, I have run both online and boot-time DK degrags many times with no Running DK v7 with build 413, which is the latest version. One thing I HIGHLY RECOMMEND is to Ghost your system first.Īfter upgrading XP to SP1, I have observed that running Diskeeper'sīoot-time defragmentation on the C: disk reliably corrupts files. There was another reply saying that they did not have a problem with Diskeeper and XP SP1.
0 kommentar(er)
