DjLizard

If you don't have enough memory (less than 256MB) then turning off the page file to do that above routine is going to be a bad idea. Just use PageDefrag as Andavari said.

If it's case sensitive I am going to die laughing and never come back!

%USERPROFILE% is an environment variable that points to: C:\Documents and Settings\USERNAME All 2k/XP machines use it. %TEMP% is set to "%USERPROFILE%\Local Settings\Temp" (instead of a real path) so that it can be dynamic - each user's %TEMP% will get filled in with the proper value. You don't usually get to see that, unless you are in System Properties and edit your global %TEMP% variable. When %TEMP% is fully expanded, it ends up pointing to C:\Documents and Settings\USERNAME\Local Settings\Temp. However, when *you* query %TEMP%, it will show you the fully expanded value instead of the one containing %USERPROFILE%. Hope that clarifies it.

For all who didn't know: Windows 9x (all versions from 95 to Me) makes 1 registry backup per day during the first successful boot of that day. You can type 'scanreg /restore' in MS-DOS mode (tap F8 before the Windows logo appears > Command prompt only) to invoke scanreg's backup system. It will show you a list of .cab files which work not unlike Windows XP's System Restore. It restores win.ini, system.ini, system.dat, and user.dat to whatever date you select in scanreg. Also, within Windows, you can do: Start > Run > scanreg ...and it will allow you to make another backup, even if it had already made one for that day.

LOL: from 181 to 183. If you have 64, 128, or 256 MB of system RAM, you should set the min and max of your swap file size to 1024/1024. If you have 512 MB of RAM, 512/512. If you have 1024MB of RAM, 256/256 or completely off (unless you play big 3D games like WoW, Battlefield, etc, in which case it should be 1024/1024)

%TEMP% is %USERPROFILE%\Local Settings\Temp. Each user gets their own temp folder. It's created by Windows and all 32-bit programs that check for %TEMP% will get pointed there. C:\Windows\temp hasn't been used since Win9x and it is there for compatibility purposes. edit: beaten

I would like to know too, but it seems to be fairly common lately, so something is going on. Sometimes, users or programs unknowingly set the TEMP location to somewhere that it really shouldn't be, like C:\WINDOWS. Oh yeah, every time I clean the TEMP folders, I want C:\WINDOWS to be deleted. Hooray! At any rate, when you are in System Properties changing your TEMP and TMP variables, you need to use the environment variable, instead of the path it expands to. So, use "%USERPROFILE%\Local Settings\Temp", NOT "C:\Documents and Settings\Username\Local Settings\Temp" (or what-have-you). When you do echo %TEMP% at the command prompt, it should expand %USERPROFILE% and show you the entire path (C:\Documents... etc) I'm not sure what causes the variable to get screwed up, and how not having %TEMP% set could lead to data loss, but I know that if %TEMP% is set to a folder containing important files, CCleaner will happily empty it for you. Dial-a-fix 0.58 is going to thoroughly check %TEMP% against all other important variables and make a best guess as to what is going on, and inform the user. It will also check for blank variables. When either of these conditions are detected, Dial-a-fix will not allow you to install any of its support files or empty the temp folders from within DAF.

The problem is, if you continue to use your computer (especially to install recovery software) you will overwrite bits of your data. You essentially have to stop using your computer and perform the recovery on the drive from another machine. At my shop, I usually use Ontrack EasyRecovery Pro. None of my recovery software is free, though, and it always requires hooking up the drive to another machine as a slave. Any data you change on this drive will make it that much harder to recover your documents.

This is usually caused by Disk Cleanup's compression algorithm. To fix it, disable compression. Save the following as disablediskcleanupcompression.reg and then double click to import it: Windows Registry Editor Version 5.00[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches\Compress old files]

CCleaner will not actually show itself on startup; it runs in the background silently/hidden and exits.

There's a bug in DAF's display of your %TEMP% variable - it's not blank, it most likely matches %USERPROFILE%. This is fixed in v0.58 which will be out in a week or two. Try this: Start > Run > cmd.exe echo %TEMP% echo %USERPROFILE% See if they match. If they do, that's why CCleaner deleted your files. Right-click My Computer > Properties > Advanced tab > Environment Variables > and change the TEMP and/or TMP paths listed there to: %USERPROFILE%\Local Settings\Temp <- change them to exactly what is written here.

Well, if you really want to know, CCleaner's "Issues" scan targets invalid "InProcServer" (and more) entries in the registry... removing these entries is akin to unregistering the objects that the entries belonged to. Therefore, if CCleaner erroneously removed entries or the entries were damaged in the registry, the objects are considered not registered. Dial-a-fix will solve this by re-registering many, many DLLs. This puts things back to Windows installation defaults. Here's just a few files that are registerable via Dial-a-fix that have relation to MSOE (this is a dependency log of Outlook Express 6 from my own system, truncated to list only those objects that are covered in Dial-a-fix) : c:\windows\system32\WINTRUST.DLL c:\windows\system32\RPCRT4.DLL c:\windows\system32\ATL.DLL c:\windows\system32\OLE32.DLL c:\windows\system32\OLEAUT32.DLL c:\windows\system32\OLEACC.DLL c:\windows\system32\NETPLWIZ.DLL c:\windows\system32\URLMON.DLL c:\windows\system32\SHELL32.DLL c:\windows\system32\DEVMGR.DLL c:\windows\system32\SHDOCVW.DLL c:\windows\system32\MSRATING.DLL c:\windows\system32\MSHTML.DLL c:\windows\system32\HLINK.DLL c:\windows\system32\IMGUTIL.DLL c:\windows\system32\MLANG.DLL c:\windows\system32\INETCOMM.DLL c:\windows\system32\BROWSEUI.DLL c:\windows\system32\OLEPRO32.DLL c:\windows\system32\CDFVIEW.DLL c:\windows\system32\NETMAN.DLL c:\windows\system32\WINHTTP.DLL c:\windows\system32\NETCFGX.DLL c:\windows\system32\MOBSYNC.DLL c:\windows\system32\HNETCFG.DLL c:\windows\system32\NETSHELL.DLL Here's a couple more that aren't directly dependencies (but belong to MSOE and are covered by Dial-a-fix) : msoe.dll, msoeacct.dll Because of this thread, I just learned a bunch of new DLLs I can add to Dial-a-fix that are dependencies of MSOE (among other programs). The following currently are NOT covered by Dial-a-fix but DO need to be registered: RPCRT4.DLL, ACTIVEDS.DLL, OLEACC.DLL, CREDUI.DLL, CRYPTUI.DLL, MSSIGN32.DLL, CERTCLI.DLL, SCECLI.DLL, USERENV.DLL, MSI.DLL, SHSVCS.DLL, OLEPRO32.DLL, QUERY.DLL They will be added to the next version of DAF (If you wish to register these DLLs in an attempt to fix your issue, click Start > Run > and type: regsvr32 filename.dll with each of the above files). For USERENV.DLL and SHSVCS.DLL, also do regsvr32 /i filename.dll

It's a binary file; it has to be uploaded somewhere. Start > Run > iexplore ftp://ftp.DjLizard.net/incoming/ After a few minutes, it will open up a blank window. Drag the file into that window. You will not be able to see the file after it's uploaded (I'm pretty sure) so don't let that alarm you. After that's done, let me know via PM or post here and I'll examine it. If you're not able to upload it there for whatever reason, try uploading it here: http://upload2.net/ After the file is uploaded there, post the "File download link" it gives you.

If you're getting a blue screen of death, running more software is usually not going to fix it. First, disable automatic restarting: 1) Start > Run > sysdm.cpl 2) Advanced tab > Startup and Recovery section > Settings button 3) *Un*check "Automatically restart" under "System failure" if it isn't already 4) Under "Write debugging information", set it to Small memory dump (64 KB) 5) Hit OK to all of these dialogs. 6a) If there is anything in C:\Windows\minidump\, find the most recently dated file and post it somewhere so I can look at it. 6b) If nothing is in there, wait for or cause a blue screen of death. 7) Write down the STOP error code (looks like 0x0000STUFF) and the words and numbers next to it in the same line, if any. Write down any filenames listed, if any. Once I know what it is, I can tell you what to do. I suspect registry damage. Do *not* do a System Restore at this time.

Not me! I don't know the answer Although there are several MSOE related DLL registrations in DAF, CCleaner would not have normally changed any of their registrations. You're welcome to try DAF light though, just in case. * http://djlizard.net/software/Dial-a-fix.exe Checkmark everything in box #5 and hit GO.

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

Thread.Close();

If your %TEMP% environment variable is set to your documents folder, then CCleaner will delete it without haste. Dial-a-fix tries to check for this kind of error and warn you about it, but as of v0.57.7 it is currently not 100% foolproof at figuring that out. Dial-a-fix v0.58 is going to be very good at detecting this kind of problem. CCleaner needs to start checking %TEMP% to make sure it does not match other environment variables and system folders.

I don't think it should include files that were recovered by chkdsk... deleting those would be considered data loss. Those files are not just frivolous creations of Windows; they are actual file chains recovered from filesystem errors. You are technically supposed to look through them to see what it has recovered (but in the old days, only a technician could have done this). If you are able to read the file header and can determine what kind of file it is, then giving it a proper file extension usually makes the .chk file accessible again. Starting with NTFS, most recovered files maintain their proper names and extensions. I'm assuming by the fact that your files are *.chk that you are using FAT32. If I'm correct in that assumption, that is a big mistake; you should switch to NTFS as soon as you can to avoid future data loss. If I'm incorrect and you are using NTFS, then good. NTFS maintains a journal of file changes and lost files and lost file chains are a lot more recoverable than when under a FAT32 filesystem. I also noticed that the latest version doesn't successfully clean Run MRU. I went into Start menu properties > Start Menu tab > Customize > Advanced tab > Clear list and that cleared it.

It's a managed language, so garbage collection and most memory functions are handled by the runtime rather than the developer. .NET seems to be for RAD (rapid application development) the way VB is, but with managed code (VB is unmanaged). C++ is unmanaged, and so is Delphi, etc. I would say CCleaner would not be better in .NET.

Can't click on the Tools section? Why's that? Well, you may or may not be able to install SP2. Anyway, if your system is running SP1 and your CD has SP1 in it, then there's no harm in using that if it's prompting you for files or something. But yeah, see if you can install SP2. If you can't, try the SSL checkmark in Dial-a-fix and hit GO.

Dial-a-fix is not keen on IE7 yet (don't worry though, it won't cause any harm), so I will add a check for iesetup.dll (note that nothing is wrong with your system, and that error is generated because Microsoft has changed that DLL to where it is no longer registerable). So basically, ignore that part. The rest will go on as normal. Continue forth. Try the IE Repair/reinstall tool now, or that VBS thing you were trying to do before.

Another note: is that a 2006 Norton/Symantec product? If so, Dial-a-fix > Tools > Repair permissions (just for good measure)

Download Dial-a-fix full (http://djlizard.net/software/Dial-a-fix-full.exe) extract it to a folder on your desktop. Double click Dial-a-fix.exe. Checkmark the first checkmark in box #1, and all 5 checkmarks in box #5 and then click GO. Then click the Tools button, choose Repair/reinstall IE, and click GO on that dialog. It will prompt you for files from your Windows installation CD (most are located in i386 on the CD). Some of the files may not be found in i386 on your XP CD, and it will prompt you for them. After successfully pointing the dialog to one file, it will most likely immediately ask you for another. You can find them in any of the following locations (just keep trying each location for each file until it continues and asks you for more files) : C:\Program Files\Common Files\Microsoft\TextConv C:\Program Files\Internet Explorer\SIGNUP C:\Program Files\Internet Explorer\MUI C:\Program Files\Common Files\Microsoft\MSInfo C:\Program Files\Internet Explorer

Haha, I know what you mean. I wrote Dial-a-fix in Delphi 7. Better than hiding the box itself is to use the included BeginUpdate and EndUpdate methods: ListBox1.BeginUpdate; <insert or delete stuff> ListBox1.EndUpdate; I hate VB (which is what CCleaner is written in) But not only that, most of the components on the form are non-standard even to VB (note all of the OCXs that get installed, ugh) I also hate the way HijackThis does smooth scrolling (long pause during the first vertical scroll, then it gets back to normal speed)