Copy Protection Scan #55

New Issue

Closed

opened 2026-01-29 16:08:30 +00:00 by claunia · 1 comment

claunia commented 2026-01-29 16:08:30 +00:00

Owner

Copy Link

Originally created by @mnadareski on GitHub (Jun 29, 2018).

Originally assigned to: @mnadareski on GitHub.

Currently, the best course of action for people to get the copy protection field for their discs is to run ProtectionID. This is good, but it is not scriptable. It would be better if we had internal checking for copy protection that can slowly add more over time.

Possibly look at BurnOut, since that's OSS and EOL;

Originally created by @mnadareski on GitHub (Jun 29, 2018). Originally assigned to: @mnadareski on GitHub. Currently, the best course of action for people to get the copy protection field for their discs is to run ProtectionID. This is good, but it is not scriptable. It would be better if we had internal checking for copy protection that can slowly add more over time. Possibly look at BurnOut, since that's OSS and EOL;

claunia added the enhancement label 2026-01-29 16:08:30 +00:00

claunia closed this issue 2026-01-29 16:08:31 +00:00

claunia commented 2026-01-29 16:08:32 +00:00

Author

Owner

Copy Link

@mnadareski commented on GitHub (Jul 4, 2018):

Update to the original issue: In the linked PR, it was easier to take the BurnOut code and convert it from VB to C# than I would have thought. This means that every protection technically supported by BurnOut will also be technically supported by DICUI after this. Some enhancements were made for the PR but there is another issue, #83 that is tracking anything that needs to be added on top of that.

@mnadareski commented on GitHub (Jul 4, 2018): Update to the original issue: In the linked PR, it was easier to take the BurnOut code and convert it from VB to C# than I would have thought. This means that every protection technically supported by BurnOut will also be technically supported by DICUI after this. Some enhancements were made for the PR but there is another issue, #83 that is tracking anything that needs to be added on top of that.

claunia referenced this issue 2026-01-29 16:24:35 +00:00

[PR #101] [MERGED] Goodbye drive speed finders #970

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

master

rolling

3.6.0

3.5.0

3.4.2

3.4.1

3.4.0

3.3.3

3.3.2

3.3.1

3.3.0

3.2.4

3.2.3

3.2.2

3.2.1

3.2.0

3.1.9

3.1.8

3.1.7

3.1.6

3.1.5

3.1.4

3.1.3

3.1.2

check-rolling

ui-rolling

3.1.1

3.1.0

3.0.3

3.0.2

3.0.1

3.0.0

2.7.5

2.7.4

2.7.3

2.7.2

2.7.1

2.7.0

2.6.6

2.6.5

2.6.4

2.6.3

2.6.2

2.6.1

2.6

2.5

2.4

2.3

2.2

2.1

2.0

1.18

1.17.1

1.17

1.16.1

1.16

1.15

1.14

1.13

1.12.2

1.12.1

1.12

1.11

1.10

1.07

1.06

1.05.1

1.05

1.04b

1.04a

1.04

1.03

1.02b

1.02

1.01d

1.01c

1.01b

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

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SabreTools/MPF#55