rhinbc wrote: ↑
Tue Aug 28, 2018 8:53 am
BUGS in ChkUnin & PRIMO! Please Help Me!
Midas wrote: ↑
Tue Aug 28, 2018 2:56 pm
I've sent an email with almost the same content. So, decide yourself where to reply.
Hi Randy & community!
Before I start. Are you still working on PRIMO project? Or have you, unfortunately, abandoned this mega required tool?
First of all, I want to say you the huge THANK YOU for your effort put in PRIMO. That's a real deal against nasty software leftovers. TBH, your RegShot fork is the best compared to others (e.g. RegShot Unicode 2.0 (from one Russian man who have abandoned it), RegUndo (not a real fork but still...), etc.).
Now, sadly, I should notify you about huge bugs (drawbacks?) that I found in ChkUnin 7.1.0 & PRIMO 3.0.1 (x64 ANSI):
ChkUnin can't generate batch command(s) to delete existing files that are listed under [Files added:] section in the valid output TXT (EN) file/log and are NOT located in the newly-created folders that ChkUnin will mark with a RMDIR /S %_nop% delete command in a .bat file.
ChkUnin will successfully generate commands for folders removal but won't for files. It will leave set _nop= and _ok= without any path to file.
Generated batch script looks like that:
As you can see, there are no files paths in batch script. Files that were created between two PRIMO 3.0.1 (RegShot) snapshots are still located in "C:\Test Folder\" and aren't in any of COMODO directories.
Note: "C:\Test Folder\" wasn't created after the second snapshot. You can see this in the PRIMO output file (I've removed millions of noise data for better understanding):
Generally, there are no major issues with folders or registry keys/values processing. ChkUnin & PRIMO shine here, almost. Maybe not a bug but still dangerous...
ChkUnin with PRIMO along can't handle keys/values, folders/files renaming. PRIMO treats renaming as deleted/created and ChkUnin use PRIMO's output data to generate registry and file system clean up files (.reg, _mods.reg, .bat) that can brick the OS by deleting renamed folder instead of renaming it back.
For example: if any program will rename any key/value, folder or file that is necessary for the OS (I mean, it must at least exist, "no" matter what the name is), PRIMO will say that it/they was/were deleted & created like a new entries with a new name. Then, ChkUnin will generate "OS dealthful" .reg & .bat files. Well, that will be a mess, TBH.
I assume it's not a bug, it is more like a not filled gap in functionality that can cause a lot of issues.
As you may already know, ChkUnin also blocks files/folders until closed. I did a lot of investigations and can say that it does something weird with attributes/permissions, do not know why and how.
No Unicode support. Not a bug, more a missed feature. I saw a lot of feedback on RegShot SourceForge's official page and other forums from people who complain about RegShot 1.9.1 x64 Unicode doesn't work on Windows 10, but it works for me on Win 10 Enterprise LTSC 1809 (x64). I tried to take snapshots with the original RS 1.9.1, with different settings (reg, dirs, both, etc.) in different OS modes (safe/normal) and it works. With "Not Responding" message for 1-2 min but works!
So, would you consider rebuilding PRIMO/ChkUnin to fully support Unicode?
Minor bug. PRIMO (RegShot) wrongly increases information about [Total changed size:] in an output file every single time you click "Output". To know the exact size changes user should use Calc_size.vbs like a workaround.
That's all for bugs/drawbacks. But I also want to give you the recommendations to improve PRIMO. Here are my findings:
1. Reorganize the UI layout to be more compact and clear. Divide check boxes on different groups. I can make a graphical prototype later.
2. Add an option to scan only wanted registry hive keys, like it's already implemented with directories scan but with check boxes.
3. Add an option to NOT quit from RegShot after pressing any key to interrupt current scanning process. Just to pause/stop, not quit, because it's possible to lose 1st not saved snapshot while taking and breaking the 2nd one.
4. Will be soon...
Well. Are there any workarounds/future fixing plans to solve issues listed above?
Nevertheless, thank you, Randy, for a great utility! Take care and keep up the great project!
I've read whole PRIMO documentation and have checked almost every single file (along with code) from Primo.zip (downloaded from SourceForge.net). Haven't found any code gaps where it is possible to prevent ChkUnin from missing files deletion. Maybe I've missed something, let me know.
I use PRIMO on Win 10 Enterprise LTSC 1809 (x64).
My main Regshot.INI settings are:
Sorry for all the made typos and formatting issues.