[FREE TOOL] Pincab Toolbox — scan your VPX/Popper install and find what's broken

[NoizePMP]

Most findings seem explainable. No criticals. I like the extra info in the details for certain triggers. In confirms what I allready expected.

Root causes:

-Only error is on the backglass. In the root folder you have the standard test tables like JP's rubber test, etc. They don't have a backglass. The finding is correct but not a real problem.

Warningstab:
-Hybrid frontend x64 and x32. That is correct I have a Hybrid install for VPX and the plugins.  I like the added probable cause in the details. 
-Again the backglass errors on the test tables.......

-Playlist error about a deleted playlist and the possible solution to resave the tables. Interesting one. Can't figure out what games are affected from. Can't find a detailed list in the export. I don't work with manual selected playlist but only active SQL. 
It is correct that a playlist was deleted but that was a small playlist and the games are in a new playlist now. Saving the playlist again did not fix this.
I am going to fiddle arround and post If I find something.

-more blocked file warnings. This is interesting. The files that are 'blocked'  are pupdesktoppunch.exe. It is a Nailbuster solution to fix missing screens/video. Since I work with a PC hybrid setup and 2 monitors,  I use this with Puppack tables like the Orbital games (Harry Potter and the goblet of fire),  MFdoom original, etc. You have to place the program in all the poppervideo folders. When I first opened the table, I would get the windows warning that is was downloaded, blah blah.
Picked the option to open it anyway. Problem with video's fixed and no more warnings.
It seems that you still need to manualy unblock them.  Opening the table again does not give the warning anymore but behind the scene it seems that windows is still marking it as a potential harm.
There is a thing bugging me. If it is 'really' blocked, it doesnt make sense that with the program in the puppack folder the problem is fixed and removing it, shows the video problems again. 
So even with a unticked unblock and the stream indentifier that it is from the web, it is allowed to run because of the choice to open it AFTER the windows warning. 
On the other hand....... better to be safe than sorry and unblock the file.

some notes:
- like an advice to place pinup popper video's on another drive. The folder structure is how Pinuppopper installs it. Pinup popper media config itself save playlist and table video's to these folders. I can understand that running
video's from another drive can be handy performance wise, put it feels like it goes against the way the file structure was intended?

Hope this helps.
 

[Flipsync]

This is the most useful report I have had so far, thank you for taking the time.

On the blocked files, your question is the right one and here is the answer. There are two separate mechanisms. The mark Windows attaches to a downloaded file stays on the file itself. Clicking "run anyway" does not remove it, it records a decision for that one executable. So a program you launch by hand goes through once you have made that choice, which is exactly what you observed with pupdesktoppunch. A library loaded by another program gets no such choice, it is simply refused, silently. That is why the scanner reads the mark on the file and not the Unblock checkbox in the properties window, the checkbox and the mark can disagree, and someone else confirmed that to me last week. So your instinct is correct, unblocking costs nothing and removes a real risk on the files that are loaded rather than launched.

On the test tables, you are right and I am wrong. The finding is accurate and useless. A rubber test table has no reason to own a backglass, flagging it adds noise to a report that should only show what actually hurts. I will look at how to tell a utility table from a real one without inventing a fragile rule.

On the playlist, that one bothers me more than it bothers you. A warning that cannot tell you which tables are involved is a warning you cannot act on, and that is my fault not yours. The export should list them. And the suggested fix clearly does not cover active SQL playlists, which is the setup you actually run. If you do find something while fiddling, I am very interested.

On moving media to a second drive, your objection is fair and it comes from something I failed to explain. The tool does not break the structure, it copies the folder to the drive you pick and leaves an NTFS junction at the original path, so Popper keeps writing exactly where it always did and never knows the difference. That should have been written on the screen, not left for you to guess.