Jump to content
CCleaner Community Forums

Alan_B

Experienced Members
  • Content count

    4,274
  • Joined

  • Last visited

Everything posted by Alan_B

  1. Windows can create and use path lengths of up to 259 characters (excluding the terminating NULL character) Recuva aborts with a warning error for anything more than 257 characters when restoring (with folder structure) to the root of a drive, and obviously aborts upon a shorter length if restoring to folder other than root. W:\Drive_F_Long_Path_Bats>MakeLong Script W:\Drive_F_Long_Path_Bats\MakeLong.bat revised 13/07/2013 09:56 13/07/2013 09:57 18 AA--12-A.INI 13/07/2013 09:57 18 BB--24---------ZKZ-B.INI 13/07/2013 09:57 18 CC--25---------YLY--C.INI 13/07/2013 09:57 18 DD--26---------XMX---D.INI 13/07/2013 09:57 18 EE--27---------WNW----E.INI 13/07/2013 09:57 18 FF--28---------VPV-----F.INI 13/07/2013 09:57 18 GG--29---------UQU------G.INI 13/07/2013 09:57 18 XX--12-X.INI W:\## └───XYZ └───(1[---------------------FIFTY----------------------]1 └───2[---------------------FIFTY----------------------]2 └───3[---------------------FIFTY----------------------]3 └───4[---------------------FIFTY----------------------]4) └───#-5-# AA--12-A.INI BB--24---------ZKZ-B.INI CC--25---------YLY--C.INI DD--26---------XMX---D.INI EE--27---------WNW----E.INI FF--28---------VPV-----F.INI GG--29---------UQU------G.INI XX--12-X.INI Script W:\Drive_F_Long_Path_Bats\Header.Bat revised 12/07/2013 21:58 Delete contents of "\##\XYZ\*" ? D(elete) / N(o) :- n ....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'..S.;....'...M :- S(ort)=248 M(ax)=259 W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\BB--24---------ZKZ-B.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\CC--25---------YLY--C.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\DD--26---------XMX---D.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\EE--27---------WNW----E.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\FF--28---------VPV-----F.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\GG--29---------UQU------G.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\XX--12-X.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\AA--12-A.INI Script W:\Drive_F_Long_Path_Bats\Header.Bat revised 12/07/2013 21:58 ....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'.S..;....'...M :- S(ort)=247 M(ax)=259 W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\GG--29---------UQU------G.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\FF--28---------VPV-----F.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\EE--27---------WNW----E.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\DD--26---------XMX---D.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\CC--25---------YLY--C.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\BB--24---------ZKZ-B.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\XX--12-X.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\AA--12-A.INI Delete contents of "\##\XYZ\*" ? D(elete) / N(o) :- n "n" Retaining "\##\XYZ\*" W:\Drive_F_Long_Path_Bats> ================================================================================================== RECUVA TEST ON "Not Deleted" FILES :- Launched Recuva v1.47.498 (64bit) with "Wizard" bypassed. Options / Actions :- Ticked the boxes Scan for non-deleted ... Restore folderstructure all other action boxes unticked. Selected drive W:\ and clicked Scan Clicked on the "Path" header and all 8 of the ##\XYZ\* folders appeared near the top of the list I right clicked one of them and selected "Highlight Folder" and chose "W:\##\XYZ I right clicked the group and chose "Check Highlighted" I clicked "Recover" and chose E: and clicked OK and was told "Maximum path length exceeded" SOLUTION :- ================================================================================================== I launch SysExporter v1.62 and chose Title "Piriform Recover" Type "ListView" (If it does not appear you may need to tick "ListView" at the top of the list within Menu "Filter") This displayed what I could see in the Recuva window. Chose Menu "Items", Chose Columns", moved "Filename" below "Path", and unticked all other boxes, and clicked OK. Chose Menu "Items", chose "Copy selected items (Tab delimitted)% Launched Notepad and used Ctrl-V to paste the result which was Path Filename W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\ AA--12-A.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\ BB--24---------ZKZ-B.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\ CC--25---------YLY--C.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\ DD--26---------XMX---D.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\ EE--27---------WNW----E.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\ FF--28---------VPV-----F.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\ GG--29---------UQU------G.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\ XX--12-X.INI and saved this as "W:\Long-Paths\Report.txt" The FIlenames are preceeded by an ugly TAB that are dealt with by Header.Bat. Launched "W:\Long-Paths\Header.Bat" which produced Report.LST :- ....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'....;....'.S..;....'...M :- S(ort)=247 M(ax)=259 W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\GG--29---------UQU------G.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\FF--28---------VPV-----F.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\EE--27---------WNW----E.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\DD--26---------XMX---D.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\CC--25---------YLY--C.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\BB--24---------ZKZ-B.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\XX--12-X.INI W:\##\XYZ\(1[---------------------FIFTY----------------------]1\2[---------------------FIFTY----------------------]2\3[---------------------FIFTY----------------------]3\4[---------------------FIFTY----------------------]4)\#-5-#\AA--12-A.INI PathFilename ================================================================================================== File GG*.INI has a total path length of 259 characters I selected that file which removed highlights from the other files, and I unticked that file and tried again and was told "Maximum path length exceeded" I unticked FF*.ini and tried again and totally recovered 6 files I closed Recuva and SysExporter One instance of Windows Explorer shows all 8 files on drive W:\ and another instance shows only 6 files on E:\ I selected FF*.ini and GG*.ini and drag-drop copied to the some folder which Recuva aborted on. HashMyFiles (from Nirsoft) confirms that the files on W:\* have the same hash values as E:\* I renamed E:\##\* as E:\#0\* I deleted E:\##\* RECUVA TEST ON "Excellent" (i.e. DELETED) FILES :- Selected drive W:\ and clicked Scan Clicked on the "Path" header and all 8 of the ##\XYZ\* folders appeared near the top of the list I right clicked one of them and selected "Highlight Folder" and chose "W:\##\XYZ I right clicked the group and chose "Check Highlighted" I clicked "Recover" and chose E: and clicked OK and was told "Maximum path length exceeded" Unticked GG* and clicked Recover and again "Maximum path length exceeded" Unticked FF* and clicked Recover and totally recovered 6 files. Recuva Options / Actions and unchecked "Restore folder structure" and clicked OK Ticked FF* and FF* and clicked Recover and chose E:\##\XYZ\ as the destination and clicked OK and both files were recovered. Used Windows Explorer to drag-drop Move GG*.ini and FF*.ini from E:\##\XYZ\ to E:\##\XYZ\ ... \#-5-#\ HashMyFiles confirms that Recuva perfectly recovered from W:\ to E:## the deleted files which were preserved in long path that was renamed to become E:\#0. The only problem is that regardless of whether Recuva is dealing with a "Not Deleted" or "Excellent" file, it is unable to restore with a destination path and name that exceeds 257 characters, which is two short of the 259 limit for windows Explorer. Just for fun I selected BB*. CC*, and DD for recovery, creating a new destination E:\#0\ got the expected "Maximum path length exceeded" Unchecked DD* and successfully recovered BB* and CC*. Although recovery to the destination E:\#1\ has a path that 3 charaxters longer than E:\, only two of those characters appear to count - the end result is a destination length of 258 characters. The Test files AA*.ini through to GG*.ini were created by MakeLong.bat @ECHO OFF & setlocal EnableDelayedExpansion ECHO Script %~f0 revised %~t0 SET "Parent=\##" SET "BASE=%Parent%\XYZ" SET "Segment=[---------------------FIFTY----------------------]" SET "MY-PATH=%Base%\(1%Segment%1\2%Segment%2\3%Segment%3\4%Segment%4)\#-5-#" IF NOT EXIST "%MY-PATH%\" MD "%MY-PATH%" ECHO A %TIME% A > "%MY-PATH%\AA--12-A.INI" ECHO X %TIME% X > "%MY-PATH%\XX--12-X.INI" ECHO B %TIME% B > "%MY-PATH%\BB--24---------ZKZ-B.INI" ECHO C %TIME% C > "%MY-PATH%\CC--25---------YLY--C.INI" ECHO D %TIME% D > "%MY-PATH%\DD--26---------XMX---D.INI" ECHO E %TIME% E > "%MY-PATH%\EE--27---------WNW----E.INI" ECHO F %TIME% F > "%MY-PATH%\FF--28---------VPV-----F.INI" SET "BIG-NAME=GG--29---------UQU------G.INI" SET "LONG-NAME=HH--30---------TRT-------H.INI" ECHO G %TIME% G > "%MY-PATH%\%BIG-NAME%" ECHO H %TIME% H > "%MY-PATH%\%LONG-NAME%" > NUL IF NOT EXIST "%MY-PATH%\%BIG-NAME%" ECHO ERROR "%BIG-NAME%" IS TOO LONG IF EXIST "%MY-PATH%\%LONG-NAME%" ECHO ERROR "%LONG-NAME%" IS TOO SHORT DIR "%MY-PATH%"\*.INI | FIND "." TREE %PARENT% /F | FIND /V /I "VOLUME" DIR %PARENT%\*.INI /S /B > REPORT.TXT CALL HEADER 248 TYPE REPORT.LST ECHO( CALL HEADER TYPE REPORT.LST ECHO( SET ANS=N & SET /P ANS="Delete contents of "%Base%\*" ? D(elete) / N(o) :- " IF /I "!ANS!" EQU "D" (RD /S /Q %BASE%) ELSE (ECHO "!ANS!" Retaining "%BASE%\*") The above script creates the file REPORT.TXT and calls another script HEADER.BAT which produces REPORT.LST HEADER.BAT is in the same folder (I am usingW:\Drive_F_Long_Path_Bats\) as Makelong.Bat. Header.bat will take a file REPORT.TXT and remove extraneous TAB characters introduced by SysExporter, and then sort the list by any chosen value (such as 248 above), or by its default setting of 247 and everything that is shorter than the chosen length will appear after everything that reaches or exceeds the chosen length and then place a header which calibrates the length. This focusses attention upon the actual paths that are close to the maxium length allowed by Windows of 259 characters HEADER.BAT is :- @ECHO OFF & setlocal EnableDelayedExpansion ECHO Script %~f0 revised %~t0 SET /A SORT=247 SET /A MAX=259 IF "%1"=="" CALL :S %SORT% & GOTO :EOF :S SET "STR=" & FOR /L %%N IN (0,10,%MAX%) DO SET "STR=!STR!....'....;" SET /A NH=%1-1 SET /A NG=%MAX%-1 SET "STR=!STR:~0,%NH%!S!STR:~%1,%MAX%!" ECHO !STR:~0,%NG%!M :- S(ort)=%1 M(ax)=%MAX% > REPORT.LST MORE /T0 REPORT.TXT | sort /R /+%1 >> REPORT.LST
  2. Freeware Rebooted

    @login123 I do not blame you for the scare - It was entirely Burnaway's fault. @Andavari Congratulations on posting a message with single line spacing. The IPB forum software inserts unwanted blank lines when I attempt to place one line immediately after another.
  3. Freeware Rebooted

    When I received the Piriform notification of Willy's post I clicked and was brought into this sequence of topics. At that stage I think I was correctly taken to Willy.s topic BUT the preceding post from login appeared to take priority, and I saw the message that is present immediately above Willy's post, i.e. BURNAWAY Premium HAS BEEN downloaded, etc etc. I have not found any evidence that "Burnaware Premium has been downloaded", but it cost me time and effort to investigate because I had been explicitly told of a BurnAWay download which I had NOT initiated. Regards Alan
  4. Freeware Rebooted

    I have a MAJOR COMPLAINT AGAINST "BurnAWare" which DOWNLOADS AGAINST MY WILL. My only mistake was to click on Willy2's link for WizFile, and BEFORE I could read Willy's post my browser was SWAMPED with statements that BurnAware was already downloaded and ready to INSTALl. It does NOT tell me to WHERE it has buried this unwanted junk. My apologies to Willy2 for hijacking his post, BUT when I tried to complain on the BurnAware topic I just suffered more unsolicited "Downloads" Regards Alan
  5. Conversely you REALY do not have ANY CLUE about :- My knowledge of UAC as it was three years ago in the abysmal Windows 8.1 ; Nor of my PRESENT knowledge and experience of UAC in Windows 10 ; Nor of the fact that three years ago the prime purpose of CCleaner was to remove junk, and NOT to be a replacement for Windows inbuilt "program remover". Regards Alan
  6. Freeware Rebooted

    Thanks Hazel and Login123. Just downloaded Wiztree 2.01 Over a year ago I broke my left femur just below the Hip. After a month in bed with no access to my desktop P.C. I have spent more time walking in the local park instead of using the computer, hence I have only visited the forum when I get notification of updates to topics that I was involved in. Two months ago my desktop MOBO/CPU died and a friend gave my his old discarded P.C. I took out his Windows 7 HDD and swapped in my Windows 7 SSD and it worked better than I feared. My old P.C. had an AMD C.P.U so some Microsoft security updates were aimed at AMD, but my new P.C. has an Intel C.P.U. I have seen no compatibility conflicts so far, I now plan to replace the Windows 7 HDD, and then create all the shortcuts to my applications which are on my previous HDD. Then I plan full image backups of both the "Intel HDD" and the "AMD SSD" and then while Windows 10 is still free to try Windows 10 on both the HDD and the SSD. and create an image and restore that image to my SSD. Regards Alan
  7. Freeware Rebooted

    Thanks Waiting till tomorrow and hoping for 2.02
  8. Java allows Ask.com to hijack your pc

    In my particular case, which was probably 6 years ago, I subsequently discovered that in the Seconia small print the "latest" version of JAVA fixed a major Java defect, and that Seconia DEPENDED upon JAVA to facilitate their scan for all the OTHER software that might have been installed on my system. SECONIA REFUSED to scan my system with my existing version of JAVA, and deliberately chose to MODIFY MY SYSTEM REGARDLESS of my selection of INFORM ONLY. Seconia SHOULD HAVE WARNED ME and given me the opportunity to make a fresh partition image BEFORE they trashed my system.
  9. Java allows Ask.com to hijack your pc

    Secunia trashed my computer so badly that I had to restore it from a Partition Image backup. I DID NOT AUTHORIZE SECUNIA TO MAKE ANY CHANGES. I only allowed a preliminary scan to DISPLAY what was oui of date. Unfortunately Secunia took it upon themselves to FIRST WITHOUT ANY WARNING to update / install JAVA to facilitate their scan. I never allowed Secunia to have any contact with my computer after that fiasco.
  10. The Firefox/Mozilla Thread

    They chose to conceal their obstinate stupidity. Before the Windows 8 nightmare occurred, Palemoon supported both 32 bit and 64 bit versions of their browser. 32 bit machines had no choice - they could only use the 32 bit version. 64 bit machines could run either - BUT The code-base which was common to both Palemoon and Mozilla had incomplete 64 bit API support and EXTENSIONS which were common to both Palemoon and Mozilla needed 64 bit API's with 64 bit Browsers. As standard 64 bit Windows 7 included adequate 64 bit API's for some BUT NOT ALL extensions. Users that wanted extensions which needed missing 64 bit API's had to use the 32 bit browser. N.B. - I think that in those days Firefox only came as a 32 bit browser. I consider it most probable that the latest versions of Windows may include adequate 64 bit API support on 64 bit machines, in which case both Palemoon and Mozilla should have 64 bit browsers that support all the extensions that run on 32 bit browsers, BUT ONLY ON THE LATEST VERSIONS OF WINDOWS. My best guess is that if you are using 64 bit Vista or 64 bit Windows 7, then some BUT NOT ALL Extensions will run adequately with FF37. Not all Firefox users would be happy with such an outcome, but since when has Mozilla considered users happiness
  11. scan stuck, time to complete incrementing

    Welcome to forum. Sorry but you are wrong. Active File Recovery was not able to read more than 31.25 % of the capacity, Recuva appears a tad better at 33% In the past you could buy a 16 GB Flash Drive from eBay etc, and it may APPEAR to be 16 GB UNTIL you occupy the first few GB, because some crooks modify the drive to make it appear larger than it really is. I would guess that if you have a genuine 16 GB capacity, then accidental damage (e.g.. by unsafe removal) could have the opposite effect and fool windows into thinking it has a 5 GB capacity. Just possibly "Active File Recovery" was fooled into thinking that there was originally no more than 5 GB present, whilst Recuva has found an inconsistency between 16 GB expected and 5 GB scanned capacity, and is now spinning wheels whist trying to resolve issues.
  12. The Firefox/Mozilla Thread

    Try Pale Moon Spell Check always works for me in this forum OK The above looked like the following before I clicked each squiggled word and selected the relevant correction :- I jumped ship from Firefox after F.F. version 18 because it started to find different ways to go wrong each time I started up Windows.
  13. Firefox is in a constant state of flux. What can be cleaned on day may cause problems the next day. Firefox has abandoned us users to staify its developers, so I have now moved to Palemoon which is far more stable and uses the same Addons.
  14. Update version 5.02.5101

    Vitog, I am sorry you did not like any attitude that you may have perceived in my replies; but you commenced with an attitude of superiority over the CCleaner developers when you stated in post #8 that their "programming issues" were the cause of your problem, and that they had a duty to email you once they had fixed them; My first post #9 was a sincere effort to assist someone who claimed to have the skill to recognize a "programming issue", and I thought you needed technical information to understand the situation. I rather felt that you were acting superior to me by dismissing my response as "Jargon Filled". I would prefer to let this matter rest, and not continue to hijack this topic related to windows 7 and '' Error opening file for writing: C:\Programm Files\ CCleaner\ CCleaner64.exe'' Regards Alan
  15. No more Flash on YouTube

    Hackers would have no problem exploiting HTML5 - BUT ONLY IF HTML5 WAS AN ADOBE PRODUCT,
  16. Update version 5.02.5101

    What is the "jargon" that you fail to comprehend or understand ? I was responding to your post in which you FAILED to advise WHERE you obtained CCleaner. You now admit to having downloaded from Filehippo which I trusted in the past, but not now that it provides "extras" for the unwary and those that do not understand "jargon" So far as I am aware the NSIS installer is NOT part of the CCleaner application as created by Piriform, in which case it is YOUR fault to mistakenly demand :- N.B. If you have an NSIS installer on your computer, it may STAY there even after you uninstall CCleaner and replace CCleaner with a CLEAN download from Piriform so the problem may persist until you find and delete NSIS. If you need further help overcoming the problem I suggest you start your own topic, and not continue hijacking a topic that belongs to someone else with a different product "Professional Plus"and a different version of Windows.
  17. Update version 5.02.5101

    Sorry, BUT I really think this is your error. The ONLY TIME that I have suffered with NSIS was when using NON-PORTABLE applications that have been "Portablized" by PortabeApps which commonly used a NSIS launcher. I suffer much less grief from complications by using non-bodged applications that are from the outset deigned to be Portable. I notice that there are now individual users who are "rolling their own" versions of a semi-portable CCleaner :- http://portableapps.com/node/1390 I really doubt that you have encountered a PIRIFORM programming issue. There is no way they can fix software that they did not originate.
  18. The latest 162 KB WinApp2.ini causes a 4140 mSec assimilation delay before CCleaner is ready for action. Without WinApp2.ini then CCleaner needs only 350 mSec before being ready for action - but it is less comprehensive. A minimized 12 KB variant gives a mere 100 mSec Assimilation delay, and cleaning is just as good as the 162 KB variant. TRIM.BAT takes less than 3 seconds to produce the 12 KB variant, and is attached as TRIM.TXT to comply with attachment restrictions. UNFORTUNATELY it depends upon CCleaner.INI showing all the CCleaner.exe detections of applications, and that needs perhaps 1 minute of double clicking groups of CCleaner checkboxes to force needed information into CCleaner.ini. Please advise me If you know of a Windows GUI to text capture tool such as Nirsoft SysExp, but with command line options. If CCleaner /debug could be enhanced to show all detected applications, life would be much sweeter. Trim_Help.txt describes the actions needed to force needed information into CCleaner.ini. LaunchCC.BAT is attached as LaunchCC.txt and measures the duration of CCleaner(64).exe /AUTO and show how much faster a launch is using the reduced WinApp2.ini Trim_Log.txt was captured from the screen when using the above tools I FORGOT TO SAY - PLEASE NOTE :- THIS intended to run in a folder dedicated to the purpose of creating a minimized WinApp2.ini. It is intended also to demonstrate the speed of a "CCLEANER /AUTO " operation with all boxes unchecked so nothing is zapped. This has no effect upon the check-boxes / saved cookies / Includes / Excludes for your normal CCleaner configuration. Your "normal" CCleaner gains the benefit when you replace its standard WinApp2.ini with the minimized version. My "normal" CCleaner is Portable and held in partition H:\ with other Portable tools and applications, but the same MAXI Winapp2.ini works for both portable and installed versions of CCleaner, so the MINI version should be just as compatible. LaunchCC.txt Trim.txt Trim_HELP.txt Trim_Log.txt
  19. Here again is Trim_12.txt Simply download and change the name to Trim_12.BAT and you have the last version that I finalized Regards Alan. trim_12.txt
  20. Hi I am quite certain that I always posted the Trim*.bat variants as Trim*.txt variants because Piriform did not allow *.bat updates, with the instruction that after copying / downloading the name should be changed to Trim*.bat. I am absolutely certain my postings were in normal Windows ANSI standard with conventional CR/LF ( 0x0D,0x0A ) style line terminators, and not the horrible unreadable UNIX style variants ( omitting the 0x0D ) which subsequently appeared on the forum Windows powered up in stupid mode over a year ago and confused itself over which HDD possessed which Disk Identity, then automatically resolved the confusion by copying the Disk Identity of the MBR style 960 GB HDD to the GPT style 600 GB HDD, and because the 600 GB is always the first to be ready and becomes Drive 0, and it now had the signature of the 960 GB HDD, and then it saw the 960 GB HDD as DIsk 1 and immediately put Disk 1 OFFLINE due to Disk signature conflict - stupid imbecilic Windows. Windows then started C:\Windows on the 600 GB HDD - and fell flat on its back - legs in the air like a dead cockroach because there was no C:\Windows on that HDD. I had the proper C:\Windows running on the 960 GB HDD within half an hour. Stupid cantankerous Windows will NOT allow me to cancel its folly - it will not allow me to change back to GPT unless I first INIT the drive. All my primary partition image backups were held on the GPT disk - Windows now sees it all as RAW or UNALLOCATED. I always copied my primary backups to both an ESATA and USB connected external drives, so no serious data loss. Unfortunately all my adjustments to TRIM.BAT were created / tested on the 600 GB HDD, and the latest tweaks were not part of any image backup. I now have a superior data recovery tool which can access the "RAW / UNALLOCATED" files, and tomorrow I plan to dig out the the latest Trim bat file.
  21. This is NOT A RECUVA BUG. Obviously DELL Support is inadequate. It only provides you with X:\windows\system32\ That is obviously a microscopic scaled down pale shadow of an imitation version of Windows that is running in RAM - very probably a form of Windows PE, and this typically is less than 10% the size of normal Windows. Your Flash Drive with 64 bit Recuva SHOULD work if you plug it into a proper normally operating 64 bit Windows Computer. Your Flash Drive with 64 bit Recuva MAY FAIL to work if you plug it into a proper normally operating 32 bit Windows Computer. Your Flash Drive with 64 bit Recuva MIGHT work with Windows PE using X:\windows\system32\, BUT NOT a "bog standard" PE - you need to get or create a custom version using utilities which I have never attempted to master.
  22. CCleaner 5.0 beta GUI

    Can we please get this topic moved to the BUG REPORT FORUM so that the developers may take notice and fix v5. I understand that the SUGGESTIONS forum does not get their undivided attention.
  23. folder result by Dive wiper

    I do NOT recognize that as a valid command. Have you tried a more traditional command ? DEL F H:/todelete
  24. CCleaner 5.0 beta GUI

    They REALLY REALLY should have fixed that years ago, when I complained that AFTER I had carefully scrolled and selected a partition for complete FULL WIPE (not just a wipe FREE space), and when I then activated the WIPE the list scrolled back to the beginning, so that I had to exercise faith in Piriform that correct drive remained selected. Unfortunately my faith in Piriform was misplaced and a different partition with important files was wiped.
  25. 1) Windows by itself and for its own purposes is ALWAYS finding an excuse to re-write a file or in other ways write data to "FREE SPACE". 2) Security software is always observing everything that is happening and using Windows - giving Windows another excuse to write data to "FREE SPACE". Questions :- If Recuva is trying to examine the contents of a specific sector that is in "FREE SPACE", and at the same instant Windows is trying to write to the same sector, WHO WINS - OR DO THEY BOTH LOSE ? Is it possible that a potential "fatal embrace" is resolved by Windows / Recuva announcing to the user "Not enough Storage space" and then aborting.
×