SabreTools/MPF
1
0
Fork 0
mirror of https://github.com/SabreTools/MPF.git synced 2026-02-03 21:29:27 +00:00
Code Issues 392 Packages Projects Releases 20 Wiki Activity

[Request] Remove drive letters from !protectionInfo.txt #488

New Issue
Closed
opened 2026-01-29 16:17:16 +00:00 by claunia · 11 comments
claunia commented 2026-01-29 16:17:16 +00:00
Owner
Copy Link

Originally created by @JohnVeness on GitHub (Jan 16, 2023).

Originally assigned to: @mnadareski on GitHub.

Is your feature request related to a problem? Please describe.
I usually dump with two different drives and like to diff the !submissionInfo.txt and !protectionInfo.txt files afterwards to check they dumped the same. The !submissionInfo.txt files will differ a little at the end because of the different disc drive models, but that's fine and manageable.

However, what is annoying is that every line in !protectionInfo.txt will differ between the two dumps because the drive letter will be different.

Describe the solution you'd like
Please can you remove (or normalise) the drive letter from !protectionInfo.txt? E.g. a file like:

F:\DrvMgt.dll: SafeDisc 4.00.002+
F:\SECDRV.SYS: SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000
F:\00000001.TMP: SafeDisc 3+ (DVD)
F:\RomeTW-BI.exe: SafeCast/SafeDisc 4.00.003
F:\engine32.cab\ISBEW64.exe: Denuvo (Unknown x64 Version)
F:\RomeTW.exe: SafeCast/SafeDisc 4.00.003
F:\: SafeDisc 1.06.000+, SafeDisc 3+ (DVD), SafeDisc 4.00.002+, SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000

could change to:

\DrvMgt.dll: SafeDisc 4.00.002+
\SECDRV.SYS: SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000
\00000001.TMP: SafeDisc 3+ (DVD)
\RomeTW-BI.exe: SafeCast/SafeDisc 4.00.003
\engine32.cab\ISBEW64.exe: Denuvo (Unknown x64 Version)
\RomeTW.exe: SafeCast/SafeDisc 4.00.003
\: SafeDisc 1.06.000+, SafeDisc 3+ (DVD), SafeDisc 4.00.002+, SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000

or to (where it always uses x whatever the actual drive letter is):

x:\DrvMgt.dll: SafeDisc 4.00.002+
x:\SECDRV.SYS: SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000
x:\00000001.TMP: SafeDisc 3+ (DVD)
x:\RomeTW-BI.exe: SafeCast/SafeDisc 4.00.003
x:\engine32.cab\ISBEW64.exe: Denuvo (Unknown x64 Version)
x:\RomeTW.exe: SafeCast/SafeDisc 4.00.003
x:\: SafeDisc 1.06.000+, SafeDisc 3+ (DVD), SafeDisc 4.00.002+, SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000
Originally created by @JohnVeness on GitHub (Jan 16, 2023). Originally assigned to: @mnadareski on GitHub. **Is your feature request related to a problem? Please describe.** I usually dump with two different drives and like to diff the !submissionInfo.txt and !protectionInfo.txt files afterwards to check they dumped the same. The !submissionInfo.txt files will differ a little at the end because of the different disc drive models, but that's fine and manageable. However, what is annoying is that every line in !protectionInfo.txt will differ between the two dumps because the drive letter will be different. **Describe the solution you'd like** Please can you remove (or normalise) the drive letter from !protectionInfo.txt? E.g. a file like: ``` F:\DrvMgt.dll: SafeDisc 4.00.002+ F:\SECDRV.SYS: SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000 F:\00000001.TMP: SafeDisc 3+ (DVD) F:\RomeTW-BI.exe: SafeCast/SafeDisc 4.00.003 F:\engine32.cab\ISBEW64.exe: Denuvo (Unknown x64 Version) F:\RomeTW.exe: SafeCast/SafeDisc 4.00.003 F:\: SafeDisc 1.06.000+, SafeDisc 3+ (DVD), SafeDisc 4.00.002+, SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000 ``` could change to: ``` \DrvMgt.dll: SafeDisc 4.00.002+ \SECDRV.SYS: SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000 \00000001.TMP: SafeDisc 3+ (DVD) \RomeTW-BI.exe: SafeCast/SafeDisc 4.00.003 \engine32.cab\ISBEW64.exe: Denuvo (Unknown x64 Version) \RomeTW.exe: SafeCast/SafeDisc 4.00.003 \: SafeDisc 1.06.000+, SafeDisc 3+ (DVD), SafeDisc 4.00.002+, SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000 ``` or to (where it always uses x whatever the actual drive letter is): ``` x:\DrvMgt.dll: SafeDisc 4.00.002+ x:\SECDRV.SYS: SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000 x:\00000001.TMP: SafeDisc 3+ (DVD) x:\RomeTW-BI.exe: SafeCast/SafeDisc 4.00.003 x:\engine32.cab\ISBEW64.exe: Denuvo (Unknown x64 Version) x:\RomeTW.exe: SafeCast/SafeDisc 4.00.003 x:\: SafeDisc 1.06.000+, SafeDisc 3+ (DVD), SafeDisc 4.00.002+, SafeDisc Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000 ```
claunia added the enhancement label 2026-01-29 16:17:16 +00:00
claunia commented 2026-01-29 16:17:17 +00:00
Author
Owner
Copy Link

@mnadareski commented on GitHub (Jan 16, 2023):

The protection info file is just there to provide more complete information than what is included in the submission info. It is intentionally full-pathed as a result.

@mnadareski commented on GitHub (Jan 16, 2023): The protection info file is just there to provide more complete information than what is included in the submission info. It is intentionally full-pathed as a result.
claunia commented 2026-01-29 16:17:18 +00:00
Author
Owner
Copy Link

@Deterous commented on GitHub (Oct 12, 2023):

Removing the drive letter is not something I would personally want MPF to do.
If it helps, there are a few ways for you to automate this:
Regex: replace ^.. with (nothing). E.g. in notepad++, replace ^..(.*) with $1
Python: https://gist.github.com/Deterous/2e15bd7caa11eb115290594d491e2282

@Deterous commented on GitHub (Oct 12, 2023): Removing the drive letter is not something I would personally want MPF to do. If it helps, there are a few ways for you to automate this: Regex: replace `^..` with ` ` (nothing). E.g. in notepad++, replace `^..(.*)` with `$1` Python: https://gist.github.com/Deterous/2e15bd7caa11eb115290594d491e2282
claunia commented 2026-01-29 16:17:18 +00:00
Author
Owner
Copy Link

@JohnVeness commented on GitHub (Oct 12, 2023):

Thanks for the script @Deterous :)

I've noticed that, for some reason, the order of the lines in !protectionInfo.txt is not consistent from one dump to another, so diffing them is annoying even if the drive letter is omitted! I guess I could run the file through sort.

Overall, although in an ideal world I'd prefer !protectionInfo.txt to be identical between two different dumps of the same disc, if it's not easy or desirable for MPF to achieve this, I don't mind this being closed.

@JohnVeness commented on GitHub (Oct 12, 2023): Thanks for the script @Deterous :) I've noticed that, for some reason, the order of the lines in !protectionInfo.txt is not consistent from one dump to another, so diffing them is annoying even if the drive letter is omitted! I guess I could run the file through ``sort``. Overall, although in an ideal world I'd prefer !protectionInfo.txt to be identical between two different dumps of the same disc, if it's not easy or desirable for MPF to achieve this, I don't mind this being closed.
claunia commented 2026-01-29 16:17:18 +00:00
Author
Owner
Copy Link

@mnadareski commented on GitHub (Oct 18, 2023):

This doesn't apply to Linux paths, so approaching this in a reasonable way is a bit difficult from within the code.

@mnadareski commented on GitHub (Oct 18, 2023): This doesn't apply to Linux paths, so approaching this in a reasonable way is a bit difficult from within the code.
claunia commented 2026-01-29 16:17:19 +00:00
Author
Owner
Copy Link

@Deterous commented on GitHub (Jan 6, 2024):

@JohnVeness I gave this change a go with this commit: 6f8f43d4f0
If you can help test it (MPF UI vs MPF.Check, Windows vs Mac vs Linux, Different discs), the builds with the change are here: https://ci.appveyor.com/project/Deterous/mpf/builds/48894181/artifacts

@Deterous commented on GitHub (Jan 6, 2024): @JohnVeness I gave this change a go with this commit: https://github.com/Deterous/MPF/commit/6f8f43d4f0359105142d6d6692e23bc3f9e1bd48 If you can help test it (MPF UI vs MPF.Check, Windows vs Mac vs Linux, Different discs), the builds with the change are here: https://ci.appveyor.com/project/Deterous/mpf/builds/48894181/artifacts
claunia commented 2026-01-29 16:17:19 +00:00
Author
Owner
Copy Link

@JohnVeness commented on GitHub (Jan 6, 2024):

@Deterous Many thanks. I've done some testing, MPF UI in Windows, MPF.Check in Windows, MPF.Check in Linux (all on the same PC and drive, dual-booting), with two discs I had to hand, The Movies and Rome: Total War: Gold Edition.

For The Movies:

MPF UI in Windows:

\Setup\Data\Movies.exe: Macrovision Protected Application, SafeDisc 4.60.000
\Setup\rsrc\ereg.exe: Executable-Based Online Registration 1.0.0.1
\SECDRV.SYS: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000
\00000001.TMP: SafeDisc 3+ (DVD)
\DrvMgt.dll: SafeDisc 4.00.002+
\: SafeDisc 3+ (DVD)

MPF.Check in Windows:

\DrvMgt.dll: SafeDisc 4.00.002+
\00000001.TMP: SafeDisc 3+ (DVD)
\SECDRV.SYS: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000
\Setup\Data\Movies.exe: Macrovision Protected Application, SafeDisc 4.60.000
\Setup\rsrc\ereg.exe: Executable-Based Online Registration 1.0.0.1
\: SafeDisc 3+ (DVD)

MPF.Check in Linux:

/run/media/john/MOVIES/SECDRV.SYS: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000
/run/media/john/MOVIES/Setup/Data/Movies.exe: Macrovision Protected Application, SafeDisc 4.60.000
/run/media/john/MOVIES/00000001.TMP: SafeDisc 3+ (DVD)
/run/media/john/MOVIES/Setup/rsrc/ereg.exe: Executable-Based Online Registration 1.0.0.1
/run/media/john/MOVIES/: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc 3+ (DVD), SafeDisc 4.00.002+
/run/media/john/MOVIES/DrvMgt.dll: SafeDisc 4.00.002+

For Rome: Total War: Gold Edition:

MPF UI in Windows:

\DrvMgt.dll: SafeDisc 4.00.002+
\RomeTW.exe: Macrovision Protected Application, SafeDisc 4.00.003
\RomeTW-BI.exe: Macrovision Protected Application, SafeDisc 4.00.003
\00000001.TMP: SafeDisc 3+ (DVD)
\: SafeDisc 3+ (DVD)
\SECDRV.SYS: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000

MPF.Check in Windows:

\RomeTW-BI.exe: Macrovision Protected Application, SafeDisc 4.00.003
\: SafeDisc 3+ (DVD)
\RomeTW.exe: Macrovision Protected Application, SafeDisc 4.00.003
\DrvMgt.dll: SafeDisc 4.00.002+
\SECDRV.SYS: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000
\00000001.TMP: SafeDisc 3+ (DVD)

MPF.Check in Linux:

/run/media/john/ROMETWGOLD/DrvMgt.dll: SafeDisc 4.00.002+
/run/media/john/ROMETWGOLD/RomeTW-BI.exe: Macrovision Protected Application, SafeDisc 4.00.003
/run/media/john/ROMETWGOLD/SECDRV.SYS: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000
/run/media/john/ROMETWGOLD/00000001.TMP: SafeDisc 3+ (DVD)
/run/media/john/ROMETWGOLD/RomeTW.exe: Macrovision Protected Application, SafeDisc 4.00.003
/run/media/john/ROMETWGOLD/: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc 1.06.000+, SafeDisc 3+ (DVD), SafeDisc 4.00.002+

You see that the outputs for MPF UI and MPF.Check in Windows have successfully had the drive letter removed. The lines come out in a different order, though, which is a problem I've noticed before, which makes "diff" annoying! Maybe the lines can be sorted alphabetically before output?

The output for MPF.Check in Linux is of the same form as version 3.0.3, namely that it doesn't have a drive letter and so doesn't have a drive letter that can be removed! Given that the command-line for MPF.Check includes "-p /run/media/john/MOVIES" or "-p /run/media/john/ROMETWGOLD" you could maybe use that to remove that text from the beginning of each line? Although watch out for people typing "-p /run/media/john/MOVIES/" or "-p /run/media/john/ROMETWGOLD/", i.e. including the end slash, especially as autocomplete on the command-line will include the last slash by default.

The Linux output is also in a different line order. And of course it uses forward-slashes instead of back-slashes in Windows so a diff between the two would show every line as changed. You might want to consider changing the Linux output to match the Windows, or vice versa.

I don't have a Mac to hand, but that would also use forward-slash directory separators.

Hope this helps!

@JohnVeness commented on GitHub (Jan 6, 2024): @Deterous Many thanks. I've done some testing, MPF UI in Windows, MPF.Check in Windows, MPF.Check in Linux (all on the same PC and drive, dual-booting), with two discs I had to hand, [The Movies](http://redump.org/disc/101524) and [Rome: Total War: Gold Edition](http://redump.org/disc/47189). For The Movies: MPF UI in Windows: ``` \Setup\Data\Movies.exe: Macrovision Protected Application, SafeDisc 4.60.000 \Setup\rsrc\ereg.exe: Executable-Based Online Registration 1.0.0.1 \SECDRV.SYS: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000 \00000001.TMP: SafeDisc 3+ (DVD) \DrvMgt.dll: SafeDisc 4.00.002+ \: SafeDisc 3+ (DVD) ``` MPF.Check in Windows: ``` \DrvMgt.dll: SafeDisc 4.00.002+ \00000001.TMP: SafeDisc 3+ (DVD) \SECDRV.SYS: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000 \Setup\Data\Movies.exe: Macrovision Protected Application, SafeDisc 4.60.000 \Setup\rsrc\ereg.exe: Executable-Based Online Registration 1.0.0.1 \: SafeDisc 3+ (DVD) ``` MPF.Check in Linux: ``` /run/media/john/MOVIES/SECDRV.SYS: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000 /run/media/john/MOVIES/Setup/Data/Movies.exe: Macrovision Protected Application, SafeDisc 4.60.000 /run/media/john/MOVIES/00000001.TMP: SafeDisc 3+ (DVD) /run/media/john/MOVIES/Setup/rsrc/ereg.exe: Executable-Based Online Registration 1.0.0.1 /run/media/john/MOVIES/: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc 3+ (DVD), SafeDisc 4.00.002+ /run/media/john/MOVIES/DrvMgt.dll: SafeDisc 4.00.002+ ``` For Rome: Total War: Gold Edition: MPF UI in Windows: ``` \DrvMgt.dll: SafeDisc 4.00.002+ \RomeTW.exe: Macrovision Protected Application, SafeDisc 4.00.003 \RomeTW-BI.exe: Macrovision Protected Application, SafeDisc 4.00.003 \00000001.TMP: SafeDisc 3+ (DVD) \: SafeDisc 3+ (DVD) \SECDRV.SYS: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000 ``` MPF.Check in Windows: ``` \RomeTW-BI.exe: Macrovision Protected Application, SafeDisc 4.00.003 \: SafeDisc 3+ (DVD) \RomeTW.exe: Macrovision Protected Application, SafeDisc 4.00.003 \DrvMgt.dll: SafeDisc 4.00.002+ \SECDRV.SYS: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000 \00000001.TMP: SafeDisc 3+ (DVD) ``` MPF.Check in Linux: ``` /run/media/john/ROMETWGOLD/DrvMgt.dll: SafeDisc 4.00.002+ /run/media/john/ROMETWGOLD/RomeTW-BI.exe: Macrovision Protected Application, SafeDisc 4.00.003 /run/media/john/ROMETWGOLD/SECDRV.SYS: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000 /run/media/john/ROMETWGOLD/00000001.TMP: SafeDisc 3+ (DVD) /run/media/john/ROMETWGOLD/RomeTW.exe: Macrovision Protected Application, SafeDisc 4.00.003 /run/media/john/ROMETWGOLD/: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc 1.06.000+, SafeDisc 3+ (DVD), SafeDisc 4.00.002+ ``` You see that the outputs for MPF UI and MPF.Check in Windows have successfully had the drive letter removed. The lines come out in a different order, though, which is a problem I've noticed before, which makes "diff" annoying! Maybe the lines can be sorted alphabetically before output? The output for MPF.Check in Linux is of the same form as version 3.0.3, namely that it doesn't have a drive letter and so doesn't have a drive letter that can be removed! Given that the command-line for MPF.Check includes "-p /run/media/john/MOVIES" or "-p /run/media/john/ROMETWGOLD" you could maybe use that to remove that text from the beginning of each line? Although watch out for people typing "-p /run/media/john/MOVIES/" or "-p /run/media/john/ROMETWGOLD/", i.e. including the end slash, especially as autocomplete on the command-line will include the last slash by default. The Linux output is also in a different line order. And of course it uses forward-slashes instead of back-slashes in Windows so a diff between the two would show every line as changed. You might want to consider changing the Linux output to match the Windows, or vice versa. I don't have a Mac to hand, but that would also use forward-slash directory separators. Hope this helps!
claunia commented 2026-01-29 16:17:19 +00:00
Author
Owner
Copy Link

@Deterous commented on GitHub (Jan 6, 2024):

Perfect, that is the expected output. As mnadareski said above, this doesn't apply to Linux paths, so this change only benefits Windows users (Linux output is unchanged as desired). I see how removing the full Linux "drive path" would make it cleaner, but that would require larger code changes outside of this function. Another approach would be changing how BOS works, that's not in scope.

As for the order in which things are printed, MPF is printing them in dictionary order as it receives from BOS. The keys themselves can be ordered alphabetically before printing to file, as I have done here: f9f854e70b
You can test it with this build: https://ci.appveyor.com/project/Deterous/mpf/builds/48895411/artifacts
Although I'll ask @mnadareski if this is a desirable change before making a PR. Alphabetical order might not be preferred, but instead by "folder". This could be done by BOS outputting a SortedDictionary instead.

@Deterous commented on GitHub (Jan 6, 2024): Perfect, that is the expected output. As mnadareski said above, this doesn't apply to Linux paths, so this change only benefits Windows users (Linux output is unchanged as desired). I see how removing the full Linux "drive path" would make it cleaner, but that would require larger code changes outside of this function. Another approach would be changing how BOS works, that's not in scope. As for the order in which things are printed, MPF is printing them in dictionary order as it receives from BOS. The keys themselves can be ordered alphabetically before printing to file, as I have done here: https://github.com/SabreTools/MPF/commit/f9f854e70b9ec3c1feb38c24cdcd05736208cce8 You can test it with this build: https://ci.appveyor.com/project/Deterous/mpf/builds/48895411/artifacts Although I'll ask @mnadareski if this is a desirable change before making a PR. Alphabetical order might not be preferred, but instead by "folder". This could be done by BOS outputting a SortedDictionary instead.
claunia commented 2026-01-29 16:17:20 +00:00
Author
Owner
Copy Link

@JohnVeness commented on GitHub (Jan 8, 2024):

@Deterous Thanks, sorting seems to work with that version, so the output from MPF UI and MPF.Check on Windows are the same. This will make comparisons between different dumps on that platform much easier, which was my original issue :)

Output is also sorted on the Linux version too, although obviously differs from the Windows output as expected.

I notice one more thing (tell me if I should open this as a new issue), which you can see in the outputs in https://github.com/SabreTools/MPF/issues/448#issuecomment-1879789151 - for some reason I notice that the Linux version of MPF.Check, when outputting the line for the root folder of the disc, shows more details than the Windows versions of MPF UI and MPF.Check. E.g. Linux will output "/run/media/john/ROMETWGOLD/: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc 1.06.000+, SafeDisc 3+ (DVD), SafeDisc 4.00.002+" compared to Windows ": SafeDisc 3+ (DVD)". It looks like the Linux version is showing all the protections found in all the files below root, and the Windows version only one. Any ideas?

@JohnVeness commented on GitHub (Jan 8, 2024): @Deterous Thanks, sorting seems to work with that version, so the output from MPF UI and MPF.Check on Windows are the same. This will make comparisons between different dumps on that platform much easier, which was my original issue :) Output is also sorted on the Linux version too, although obviously differs from the Windows output as expected. I notice one more thing (tell me if I should open this as a new issue), which you can see in the outputs in https://github.com/SabreTools/MPF/issues/448#issuecomment-1879789151 - for some reason I notice that the Linux version of MPF.Check, when outputting the line for the root folder of the disc, shows more details than the Windows versions of MPF UI and MPF.Check. E.g. Linux will output "/run/media/john/ROMETWGOLD/: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc 1.06.000+, SafeDisc 3+ (DVD), SafeDisc 4.00.002+" compared to Windows "\: SafeDisc 3+ (DVD)". It looks like the Linux version is showing all the protections found in all the files below root, and the Windows version only one. Any ideas?
claunia commented 2026-01-29 16:17:20 +00:00
Author
Owner
Copy Link

@Deterous commented on GitHub (Jan 8, 2024):

I notice one more thing (tell me if I should open this as a new issue), which you can see in the outputs in #448 (comment) - for some reason I notice that the Linux version of MPF.Check, when outputting the line for the root folder of the disc, shows more details than the Windows versions of MPF UI and MPF.Check. E.g. Linux will output "/run/media/john/ROMETWGOLD/: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc 1.06.000+, SafeDisc 3+ (DVD), SafeDisc 4.00.002+" compared to Windows ": SafeDisc 3+ (DVD)". It looks like the Linux version is showing all the protections found in all the files below root, and the Windows version only one. Any ideas?

That could potentially be due to how BOS treats Windows vs Linux paths as files vs directories. Please open an issue with BOS, I may test that out another day. For now, I will try get these changes merged and close this particular issue.

@Deterous commented on GitHub (Jan 8, 2024): > I notice one more thing (tell me if I should open this as a new issue), which you can see in the outputs in [#448 (comment)](https://github.com/SabreTools/MPF/issues/448#issuecomment-1879789151) - for some reason I notice that the Linux version of MPF.Check, when outputting the line for the root folder of the disc, shows more details than the Windows versions of MPF UI and MPF.Check. E.g. Linux will output "/run/media/john/ROMETWGOLD/: Macrovision Security Driver 4.00.060 / SafeDisc 4.00.000-4.70.000, SafeDisc 1.06.000+, SafeDisc 3+ (DVD), SafeDisc 4.00.002+" compared to Windows ": SafeDisc 3+ (DVD)". It looks like the Linux version is showing all the protections found in all the files below root, and the Windows version only one. Any ideas? That could potentially be due to how BOS treats Windows vs Linux paths as files vs directories. Please open an issue with BOS, I may test that out another day. For now, I will try get these changes merged and close this particular issue.
claunia commented 2026-01-29 16:17:20 +00:00
Author
Owner
Copy Link

@JohnVeness commented on GitHub (Jan 8, 2024):

Thanks for all your help :)

@JohnVeness commented on GitHub (Jan 8, 2024): Thanks for all your help :)
claunia commented 2026-01-29 16:17:20 +00:00
Author
Owner
Copy Link

@Deterous commented on GitHub (Jan 9, 2024):

Removing drive letters will not be done by default, but it will be an option within both MPF and MPF.Check
The alphabetical sorting will be done by default, though

@Deterous commented on GitHub (Jan 9, 2024): Removing drive letters will not be done by default, but it will be an option within both MPF and MPF.Check The alphabetical sorting will be done by default, though
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
duplicate
enhancement
good first issue
help wanted
invalid
pull-request
Mirrored from GitHub Pull Request
 question
regression
wontfix
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SabreTools/MPF#488
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?