Jump to content

Augeas

Moderators
  • Posts

    4,542
  • Joined

Posts posted by Augeas

  1. So you cut/pasted or moved a file to a flash drive, the move failed and you deleted the original? Or did you create the file and save directly to the flash drive, and the save failed? And you didn't save the file anywhere else when the save to flash drive failed? Did you do the edit on your pc or on a shared pc at work or elsewhere?

     

    If it's your pc and the file existed on your hard drive then scan the drive with Recuva. You might find an edit autosave copy if you used Word or something similar. You will need to do a deep scan to find this. Look for files with a last accessed date of the date/time you did the fatal move. If you find anything recover it to a new flash drive. However using your pc to do anything, load Recuva, surf, signup here, post a message, etc will write files on your disk which increases the chance of overwriting deleted data and decreases the chances of finding anything useful.

     

    If it's your pc and you created and saved directly to the flash drive then you might find an edit autosave copy as above. If it's not your pc and you created and saved directly to the flash drive then the chances of getting anything back off the flash are minimal.

  2. If you're doing this to stop IE freezing then you're probably barking up the wrong tree. CC is more of a tidyer up of loose ends than a problem fixer. There's most likely a more fundamental reason why IE freezes.

     

    There's really no checklist that you can use to tick off what can be removed from the registry and what can't. It depends on many things including your software setup, what applications you have, how are they configured, etc. Nobody can guarantee that a specific item will not be trouble free if removed (except for some obvious ones such as invalid icons). I should do what's been advised in this thread, backup the registry, remove what seems like rubbish, reboot frequently to test, and leave those you aren't sure about alone. These entries aren't going to fill your disk or grind your pc to a halt so don't get too paranoid about them. Go and fix IE instead.

  3. I don't know what would cause the file renaming (O/S and method of deletion would be a help). Deleting via the recycler renames files but it doesn't seem likely that you deleted 2 drives via the recycler. I would say that it's not normal, some other application perhaps?

  4. I believe that CC wipe uses one pass of zeroes, no matter what you specify elsewhere. What would happen if you chose Normal Deletion?

     

    I'm not competent to answer the original question, and I don't think that anyone on the forum is either (excluding Piriform employees). How do we know what CC or Eraser is actually doing?

     

    Out of interest, if a large file is being allocated (the apparent method of choice for disk wiping) then doesn't it fill all the slack space (file tips) anyway?

  5. Can we guess that you were running Wipe Free Space? If you have not cancelled CC then try to let it run its course. It will take a long time, but should release the free space back to you when it's finished. If you have cancelled CC then look in the root directory (c drive) for a file with a random filename that is massively large and was created on the date/time when you ran CC. There may be more than one, I'm not sure. Shift/del it/them.

     

    Wipe free space is an absolute waste of time on a new pc (and some will say on an old one too). If you haven't run wfs, then post back.

  6. Afaik, windows WILL decrease the MFT zone as the disk is getting almost full, downto whatever size it takes to fit the new files on the disk.

    To be pedantic, when the non-mft zone area of the disk is full then Windows will place new files in the mft zone, which is not the same as reducing the mft zone size. When these files are deleted then the mft zone resumes it's size and function (that's an assumption). I would rather lean towards Defraggler not truly reporting the mft zone than the zone being reduced.

     

    Are you on XP? Do you have the default MFT zone size (12.5%) or is (was) your zone larger by a multiple of that?

     

    Oh yes, can you do something like allocating a file large enough to be seen, and then look in Defraggler to see whether it's been put in the mft zone or not?

  7. As I'm sure you know the 'standard' way of wiping free space is to fill up the disk with large files, and this includes the MFT zone. However the files are then deleted, leaving the disk with the same amount of free space as before, and the MFT zone as empty, or as full, as it was before.

     

    I don't really know how CC's wipe free space works, and I know even less about Defraggler. In XP it is not possible to reduce the MFT zone below 12.5% (according to M/S) so I wouldn't think that your zone has decreased in size. Do any other Defraggler users notice this? In Vista the MFT is treated differently (from what I remember), being allocated in not-necessarily-contiguous 200k blocks.

     

    This is assuming that the wipe free space option ran to completion and removed all filler files.

     

    I don't think that it is wise to write to clusters without going through Windows file allocation processes, otherwise you could be in deep youknowwhat.

  8. I was a long time user of AVG, from 6 upwards. However I was hit by a win32.virut virus which AVG didn't stop, and didn't detect when I scanned the infected files, so I switched to Avast (which did detect the virus). It's fine, no great drain on resources, but the interface is crappy compared to AVG's excellent offering. I was happy with AVG 8 and it's a shame to move, but once hit by a box rebuild you tend to get a little wary.

  9. JG, with a clean install of XP (don't know what you're on, and don't know about Vista) there are no startup entries. And it works fine, so fast and lean that you'll be reluctant to add any applications. Avast should give you two startup entries, and you can let them stay. Just Google the program names of the others to find out what they are. Then you can disable each one in turn with CC, and reboot, and see if there's any difference. Some entries might pop back in there after reboot, so you will have to stop the relevant service or whatever is causing it.

  10. Until someone comes along with the real answer, just cancel stage 2 of Recuva. I always do and it doesn't seem to make the slightest difference to the file state report, which isn't really important anyway, you can always look at the innards of any particular file you find.

  11. You can of course enter doc in the File/path box (but not .doc). In my experience Recuva will do a full scan and then show filtered results, no matter what you put in the File/Path box, so it won't make the scan any shorter. I don't think your chances are high, though.

     

    As you formatted the drive are you running a deep scan? (By the runtime and number of files found it sounds like it.)

  12. Don't know about number 1.

     

    Why would you want number 2? You can filter the rearch results in the file/path box if you so wish.

     

    Yes, it would be handy to pore over later. But for info only, as Recuva works on a moving base and the results later won't be the same.

  13. You actually need very few items at startup. I have two virus check components, which I think we can say are a must, and the Sigmatel Systray. I'm not sure why I keep the systray application running, there must be a reason but I can't remember what. So that's three startup items.

     

    You will have to plough through these items to see what each is, if it's not blindingly obvious, and do a lot of rebooting. But in the end it's nice to get rid of all that tat. It seems that every application is so important that it must be loaded ready for use at any time. You're the boss, shut them up!

  14. Or you could go to Dell's site, enter your service tag, and get a list of all drivers for your piece of kit (you'd have to be pretty dumb if you didn't go to Dell's site). Or you could enter find drivers on Google and trawl through the 27 million hits. Or you could run any of the countless driver finder applications already out there.

     

    There's really no reason why CC should do this, any more than a driver finder should clean up temporary files and fix the registry.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.