mirror of
https://github.com/SabreTools/MPF.git
synced 2026-02-08 13:49:48 +00:00
Scan for protection: Path could not be scanned! #147
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MichaelDavidHarry on GitHub (Oct 27, 2019).
Originally assigned to: @mnadareski on GitHub.
I get the 'Path could not be scanned!' message every time I try to use the Scan for protection feature.
Here is what the log output says:
My drive is a PLEXTOR CD-R PX-W4824A over a USB adaptor. I get this same error when I try with any of my other drives as well. I'm trying to test this with a copy of the original The Sims which should have some kind of SafeDisc on it.
I did some fiddling around with the DICUI project in Visual Studio and the exception seems to be coming from the ProtectionFind.Scan(path); code on line 925 of Validators.cs.
I had some issues building the project from source, and I had to bring in the BurnOutSharp, libmspack4n, and LessIO libraries as projects to get this to build. I'm using Visual Studio Community 2019. Any tips on getting it to build from what is in the git repository would be appreciated.
Thanks for this program!
@mnadareski commented on GitHub (Oct 27, 2019):
This has already been fixed in some of the recent BurnOutSharp and DICUI builds. Please try them out and report back if it's still failing.
@mnadareski commented on GitHub (Oct 27, 2019):
If you want it to build, you need to Nuget restore and it will bring in the required stuff. Otherwise, just use the AppVeyor builds linked on the main page. Linked here for convenience: https://ci.appveyor.com/project/mnadareski/dicui/build/artifacts
@MichaelDavidHarry commented on GitHub (Oct 27, 2019):
Thanks! This build (https://ci.appveyor.com/project/mnadareski/dicui/builds/28395164/artifacts) seems to work OK for me.
I think my build issues were caused by some issues with COM objects that couldn't be found, I think this got resolved when I installed the Windows Driver Kit. (At least I think that fixed it, but I'm not totally sure. I installed a couple of other things as well.)
Thanks again!