Jump to content

Augeas

Moderators
  • Posts

    4,542
  • Joined

Posts posted by Augeas

  1. You could try (swiped from M/S webpage)

     

    1. Click Start, click Run, type eventvwr.msc /s in the Open box, and then press Enter.

    2. Click the System category.

    3. Click the Source tab to sort by name, and then look for "sr" or "srservice." Double-click each of these services, and then evaluate the event description for any indication of the cause of the problem.

     

    Let us know what you find.

  2. Some info here.. http://forum.piriform.com/lofiversion/index.php/t6021.html

     

    It appears that this is a rare but not unknown problem, with a rare and (so far) unknown solution. Possible other software interference?

     

    The "suspended because of not enough disk space" error message is a little worrying. Are you sure you have enough space in sys restore? Each restore point will take around 50 mb and I use 1 gb to hold 20 points. I'm not sure whether Windows will delete all restore points except the latest if it hits space problems, I think yes. This does not fit with the latest test though, when you had only two points to play with.

  3. Do as little as possible on the drive that held the files, preferrably nothing. Open Recuva and run a scan on the correct drive, which may well be the c drive if you only have one. Look for the files you want to recover. You can sort the scan results by name or path etc. Files deleted from the recycler may be renamed to Dcxx.ext in XP and to $Rxxxxx.ext in Vista. If you find anything recover it to another drive, a flash drive will do.

     

    If you have deleted a lot of stuff then it will take several hours to find and recover it, if it can be found. There isn't any guarantee that you will find or be able to recover anything.

     

    Good sound advice would be to take a backup occasionally, but that was only valid up to yesterday.

  4. DD, this does not make sense. Clicking on Start>My Documents opens a folder showing real live files. They are not links, or shortcuts, or anything but real live files. Even if there were some way of not displaying these files, what would be the point? You may as well just close your eyes. Needless to say CC will not do what you apparently want.

     

    You could, by right clicking on Start>My Documents and selecting properties, change the folder that is referenced, and get it to point to another folder with no files in it. This would not show any files in My Documents, and would be beyond my comprehension.

     

    I think there must be some great misunderstanding here.

  5. Clicking Start > My Documents opens the My Documents folder. The list shown, if you're using that viewing option, is the only index to your personal files. I think there's some confusion about what you actually want to delete. Not the files held in the My Documents folder, surely?

     

    If you do want to do this then open the folder, click on the first file, hold the shift key down, and click on the last file. Then press delete. But no, you don't want to do this. You can't want to do this. Don't do it. You really don't want to do this.

  6. One orange and one red so they won't recover.

    I wouldn't put too much faith in these indicators, that's all they are. The proof is in the actual recovery.

     

    Perhaps in the case of Orange both the old deleted text file and the newly deleted test file occupy the same location on the flash drive, but you would have thought that Recuva could have recognised that the new file was indeed the newest: or maybe not.

     

    Flash drives are peculiar that they use what I think is called levelling, where the data is written to all areas of the drive to spread wear equally. Are files moved as a background task? Disk drives are as bad, all sorts of things going off when you're not looking. This stuff is too clever for it's own good.

  7. I'm not disputing anything anyone says, info is the intention, not assumptions. We didn't know how many disks you had, their size, what amount is allocated to sys restore, or what was being deleted.

     

    Do you run disk cleanup? If so, do you have the remove sys restore points option selected?

     

    When you run the CC reg cleanup, what options do you have ticked? Do you clean the registry frequently, and do you like to keep a clean registry by fixing all issues?

     

    I would first check the value in the sys restore point life registry entry, in HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\SystemRestore\RPLifeInterval, is set to decimal 7776000. (Keep sys rest points 90 days.)

     

    The next step would be to

     

    1) Check that there is more than one sys restore point available

    2) If not, create a sys restore point, redo step 1

    3) Run CC reg analysis

    4) Save the issues list to a text file

    5) Run CC reg fix issues

    6) Check how many restore points are available

    7) Post here with possibly the text file from step 4

     

    This assumes that there are some issues in CC reg to clean.

     

    I have never checked whether CC removes my sys restore points or not, but I can't see any option in it that would do such a thing. I would think that it would be quite difficult, seeing how XP protects the sys restore files.

  8. Free disk space is not really the issue, it's how much space is free in the allocated system restore amount, but as the default is 12% of drive space, and NTDS compresses sys restore data, it's unlikely to be an issue either, but is worth checking.

     

    Restore points are supposed to be kept for 90 days (surprisingly I only have 16 days saved with 2 gb of restore space - do they take up that much space?). Are all restore points being deleted or just a selection?

     

    Sys restore points are deleted if you run out of disk space on the system drive or on any one of the available non-system drives, which means that if you have a multiple-partition computer with a drive that has almost no free space, this drive may cause System Restore to stop responding all across the system and to delete restore points. There are other reasons, running disk cleanup with the right (or wrong) settings, and general space issues which haven't been reported here.

     

    If CC reg cleaner removes restore points, which option in reg cleaner does this, or seems to do this?

  9. Yes, I shall try to run without installing any software I never knew I wanted. And yes again, I never try to print photos myself, get a pro job for a few pence at any photo outlet. I even know how to use the machines myself!

  10. We unfortumately bought a Canon Pixma 110 (I think) all-in-one after it had rave reviews in a pc mag. It was terrible. Ink is cheap but the cartidges are so small (7 ml or so) that you never know if any problems are caused by low ink or something else. And as it's not used every day the print heads dried up, and despite running cleaner fluid through them it never returned to anything but a faded grey print. A waste of the best part of ?100.

     

    Now my old HP950C just keeps going after years of moderate use. I do tend to buy HP cartridges which are expensive, but I have had frustration with rebuilt carts, and there's nothing more frustrating than driving into town to get a catr, driving home, and the thingh doesn't work so you have to go all the way back into town again.

     

    We're thinking of replacing the rubbish Canon with an HP all-in-one, they're almost cheaper than the cost of the cartidges, but the important thing is that they work.

  11. Well, I think it would need exceptional circumstances for Recuva, or any application that uses Windows APIs, to cause disk errors that are fixed by chkdsk. FAT32 is still around for removable media of course, and possibly small devices with smallish drives or partitions. The max FAT32 filesize is I believe 4 gb - 1 byte.

  12. i think that the user means that CC secure deletion of the recycler contents doesn't rename all of the files, not that he or she wants to rename them whilst they're in the recycler.

     

    I don't know what actions CC takes when it securely deletes the recycler contents (and I don't think that Piriform are going to tell me), whether it can access and modify the recycler contents directly, or whether it has to do something entirely more messy. How does it manipulate Info2? A puzzle indeed.

  13. NTFS clusters should be at least 4k, but the size of the file is irrelevant. Recuva will see, but has the sense not to recover, files of zero byte size.

     

    There have been other reports of newly deleted files not being found. Whether this is due to the file record slot in the MFT being immediately overwritten by some other Windows process or not I don't know. In any event all deleted files are newly deleted at the start of their life (or should I say at the start of their limbo). I dunno, somebody should come up with a theory we can all bash.

  14. Assuming (ah, what misery has been caused in your name) that you found and recovered the files under their correct filename, and not just picked a ZZZZZ.ZZZ file by mere chance, are you sure that the files are not copies made by edit or some other process, and the originals have indeed been securely deleted?

  15. In XP files deleted to the recycle bin are renamed to Dcxx.ext, where xx is an ascending number. You could look for the file under that name, there's no need to run a deep scan. Or sort the path name and then look in c:\recycler.

×
×
  • Create New...

Important Information

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