SingularLabs > Forums > Bug found

Support Forum

Registration is not required to ask a question. If you're a Pro Club member, please use our Priority Support page for a faster response.

Bug found

Home › Forums › System Ninja Support › Bug found

Viewing 10 posts - 71 through 80 (of 85 total)
1 2 3 … 7 8 9
  • Author
    Posts
  • July 25, 2015 at 10:48 pm #10821
    Phobos
    Moderator

    The Old Chrome Directory is not delete from the context menu, only using button the Delete Files.

    July 26, 2015 at 1:54 am #10822
    Dennis Ekelund
    Guest

    Hi

    On launching System Ninja or CCEnhancer my windows 10 build 10240, I get this error # 0xc00ce556, any help would be appreciated.

    I have used both in windows 10 earlier builds without errors.

    July 26, 2015 at 2:08 am #10823
    Shane Gowland
    Keymaster

    On launching System Ninja or CCEnhancer my windows 10 build 10240, I get this error # 0xc00ce556, any help would be appreciated.

    Windows 10 issues will not be addressed until the release build is finalized.

    August 1, 2015 at 6:16 pm #10967
    Shane Gowland
    Keymaster

    The Old Chrome Directory is not delete from the context menu, only using button the Delete Files.

    Thanks for reporting this. Fixed.

    August 5, 2015 at 2:42 am #11006
    Anonymous
    Inactive

    New System Ninja 3.1 portable doesn’t open on win 10

    Mysteriously last old portable version worked fine  until I went to new 3.1 today.

    June 3, 2016 at 7:33 am #11650
    Howard Pearce
    Guest

    System Ninja falsely reports  folder junctions  (linked data/folders/files) as belonging to the Recycle Bin and deletes them.

    June 3, 2016 at 1:11 pm #11651
    Shane Gowland
    Keymaster

    [quote quote=11650]System Ninja falsely reports folder junctions (linked data/folders/files) as belonging to the Recycle Bin and deletes them.
    [/quote]

    Could you please post the paths of some of these erroneous detections?

    June 4, 2016 at 1:02 am #11654
    Howard Pearce
    Guest

    Some lines reported by Ninja 3.1.4 results  — followed by actual path to junction folder STANDALONE on Drive D

    COPY PATH reports the files as from Drive C – perhaps leading to the problem ?

     

    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\desktop.ini  {0.13KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\Config.xml  {10.85KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\CrushLinx V1.2.exe  {284.50KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\desktop.ini  {0.14KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\dview-config.txt  {30.13KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\dview.exe  {2,296.00KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\EmptyFolderNuker.exe  {340.00KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\FolderMenu.exe  {273.26KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\launcher64.dll  {40.50KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\7-ZipPortable.exe  {213.52KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\help.html  {5.92KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\App\readme.txt  {0.17KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\App\7-Zip\7-zip.chm  {88.89KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\App\7-Zip\7-zip.dll  {54.50KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\App\7-Zip\7z.dll  {437.00KiB}
    D:\$RECYCLE.BIN\S-1-5-21-350654301-2681636980-4242219839-1002\$R8R6P8R\7-ZipPortable\App\7-Zip\7z.exe  {72.00KiB}

     

     

    D:\Install\Standalone\7-ZipPortable\App\7-Zip

     

     

    C:\Standalone\7-ZipPortable\App\7-Zip\7-zip.chm
    C:\Standalone\7-ZipPortable\App\7-Zip\7-zip.dll
    C:\Standalone\7-ZipPortable\App\7-Zip\7z.dll
    C:\Standalone\7-ZipPortable\App\7-Zip\7z.exe
    C:\Standalone\7-ZipPortable\App\7-Zip\7z.sfx
    C:\Standalone\7-ZipPortable\App\7-Zip\7zCon.sfx
    C:\Standalone\7-ZipPortable\App\7-Zip\7zFM.exe
    C:\Standalone\7-ZipPortable\App\7-Zip\7zG.exe
    C:\Standalone\7-ZipPortable\App\7-Zip\descript.ion
    C:\Standalone\7-ZipPortable\App\7-Zip\History.txt
    C:\Standalone\7-ZipPortable\App\7-Zip\License.txt
    C:\Standalone\7-ZipPortable\App\7-Zip\readme.txt

    June 4, 2016 at 9:03 pm #11655
    Shane Gowland
    Keymaster

    So if you delete a file in D:\$RECYCLE.BIN\ does it also delete the corresponding file in C:\Standalone\?

    To my eyes, it looks like when a junction was created between C:\ and D:\, the files already extant in D:\ were simply moved to the recycle bin and replaced with symlinks. That should mean that the files in D:\$RECYCLE.BIN should be safe to delete. If files are in D:\$RECYCLE.BIN, they’re probably going to be deleted next time you empty the recycle bin, since the bin is really just a GUI for that folder anyway.

    June 5, 2016 at 10:42 pm #11656
    Howard Pearce
    Guest

    Yes, it seems to. Deleted the actual file than just the link.

    I’ve had to restore that C:\Standalone library folder from my weekly True Image image backup.

  • Author
    Posts
Viewing 10 posts - 71 through 80 (of 85 total)
1 2 3 … 7 8 9
  • You must be logged in to reply to this topic.