DjLizard

Well of course it's the font size... but that's not the user's fault, it's CCleaner's fault for not scaling the form and components to the DPI. It's easy to do in Delphi, but maybe not so easy in VB ... In Delphi, I simply turn auto-scaling off in the form properties, and use this code in every form: procedure TYourForm.FormCreate(Sender: TObject);begin if Screen.PixelsPerInch <> PixelsPerInch then ScaleBy(Screen.PixelsPerInch, PixelsPerInch); {...the rest of your FormCreate procedure...}end; And like magic, everything turns out perfectly.

OH SNAP

Start > Run > desk.cpl Screen Saver tab > 'On resume, display Welcome Screen' or 'password protect'. Uncheck that.

Give this man a cookie. On a lot of systems, there's more than one i386 folder. If it's the i386 folder that contains all of the XP installation files, then you should keep it if you don't have the XP CD or if your computer is made by a name brand (such as Dell, Gateway, Acer, Toshiba, IBM, Compaq, HP, Sony, etc).

Even when IE is broken because of the mshtml.dll registration bug, you can still direct download files via Start > Run, like: Start > Run > http://DjLizard.net/software/mshtml.dll (that's the working one) 1) Close all programs that use IE. 2) Save that to Windows\System32 and overwrite the old one. 3a) Register the one you downloaded: 3b) Start > Run > regsvr32 mshtml.dll /i

Universal Extractor http://www.legroom.net/modules.php?op=modl...&app=uniextract

kill CiSvc with fire. Context indexing in XP is really unstable in my experiences. Start > Run > sc config cisvc start= disabled (don't forget the space after "start=")

Sorry about your loss I can't remember the exact steps I used to fix my iPod when this exact thing happened, sorry :| PS: Want to get rid of that Nero Scout icon? regsvr32 /u "%commonprogramfiles%\Ahead\Lib\MediaLibraryNSE.dll"

Andy, Mshtml.dll - watch out for that! See here: http://djlizard.net/2006/03/14/139

Is there an i386 folder on your hard drive somewhere? Start > Run C:\path-to-i386-folder\winnt32.exe /cmdcons That should allow you to install recovery console as a boot-time option, so that you can hardcore manual repairs (with guidance from a tech, like me) without needing an install CD

You won't need those (because as you can see, it's already detected as a mass storage device). I had to do a repair install myself recently to repair a COM+ subsystem problem (don't ask) and I got the same result you are getting. I ended up having to do a double reset on the iPod, uninstall iTunes and Quicktime, and re-install the latest iPod updater (even though I had it installed already) and then reinstall iTunes and Quicktime. After launching the iPod updater, I connected my iPod, it saw it, and from then on, so did iTunes.

It seemed self-explanatory to me, but okay... it says that if you keep getting the same entries listed every time you scan for Issues in CCleaner, run DAF's Repair Permissions tool.

http://wiki.djlizard.net/Dial-a-fix_tips#CCleaner

krit86lr : send people to the medium version when it is just a permissions fix routine

For future reference, grayed-out display property items can sometimes be solved by Dial-a-fix's policies scanner (if a policy is indeed why it is grayed out).

Install this: http://www.microsoft.com/downloads/details...&displaylang=en

Oh, I missed that part. Anyway, since it can't be done (easily) in XP Home, why not just uncheck ZoneAlarm in CCleaner's Applications tab?

That option only exists in XP Professional, and it's a bad idea anyway, since the programs that created the logs wouldn't be able to write to them anymore, just as CCleaner wouldn't be able to delete them, so that would only create new problems. What is the name of the program?

You kick ass. I'll probably need to talk to you at some point. Please join my wiki http://wiki.DjLizard.net

Blue screens of death and data loss are not among the symtpoms, so you probably had a corrupt registry to begin with. Dial-a-fix can't cope with pre-existing critical problems just like most programs can't, but registering DLLs definitely will not cause blue screens of death. The problematic file was the new mshtml.dll that Microsoft just pushed out in the Optional section of Windows Update. But yeah, it won't cause your system to restart, so you had something much, much worse. The part about System Restore not working (was it just blank?) is part of the symptoms. However, if you had been able to get online from another computer, I could have shown you how to manually revert your registry to a previously working one, but you opted to format instead. Next time, just shoot me an email from whatever computer you can get to, and I'll give you the steps on how to do a manual system restore (which only requires that you have a Windows XP installation CD). Here's a tip for your new installation: disable automatic restart. Right-click My Computer > Properties > Advanced > Startup and Recovery Settings > uncheck "Automatically restart". Next time you get a blue screen of death (and you may soon, if you have an intermittent hardware defect) you'll be able to read the STOP error code so a technician can help you (instead of it auto-rebooting, which was dumb of Microsoft to put in there in the first place). If the error you had was similar to PAGE FAULT IN NONPAGEABLE AREA then it probably was pre-existing registry corruption, which you fixed by formatting/reinstalling. If it was an intermittent memory failure, then it may not crop back up again for a while (because hardware has the distinct ability to be "slightly defective" and very intermittent). I recommend doing a memory test now so that you know your new installation is safe too: www.memtest.org You can download a bootable CD or bootable floppy maker. Boot to memtest86+, and make sure it passes the test at least 5 times. Anyway, I suspect that it was just a corrupted registry hive and everything will be fine now.

Exactly how did Dial-a-fix "ruin" your C: drive?

To clarify, don't do the sfc /scannow bit in Safe Mode; it only works in normal mode.

wtf, that's the most annoying knowledge base article I've ever seen. Nowhere in there does it say what the problem is ;_; "This issue may occur if a Windows system file is missing or corrupted." It doesn't even tell you which file it is A sad day for DAF, thanks to Microsoft (meaning: I can't add this fix because they won't say what it is!)

krit86lr, who are you and why aren't you a moderator?

Whatever. Don't tell end-users to turn off the service. It only serves to hurt them.