Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DIC incorrectly recognized some Microsoft OS CDs as being SecuROM-protected. #223

Open
OldMadMan opened this issue Jul 19, 2023 · 4 comments

Comments

@OldMadMan
Copy link

Version
32 bit, AnsiBuild, 20230608T140750

Describe the bug
The DIC program incorrectly recognized some Microsoft OS CDs as being SecuROM-protected.

From my experience dumping a lot of Microsoft CDs, older Microsoft OS and software CDs are not protected by SecuROM. But I occasionally encounter DIC prompting that the disc being dumped is protected by SecuROM. My personal guess is that DIC may have detected some code in files on the disc and misidentified it.

There is one more information to add, all disks that are mistakenly considered to be protected by 1st gen. of SecuROM by DIC.
Screenshots
cd G NTWKS40DA.bin 72 /d8 /c2 1000 /q /ns /s 2

214547

Disc title
Microsoft Windows NT 4.0 Workstation

Disc ringcode
X05-34506

URL
Download here
Log file
Upload the created files except .bin .img .scm .iso

@saramibreak
Copy link
Owner

  1. When dumps LBA 40752, your drive returned incorrect subQ.
  2. Its incorrect subQ is checked by SecuROM-check routine.
	WORD reCalcCrc16 = (WORD)GetCrc16CCITT(10, &pDiscPerSector->subcode.current[12]);
	WORD reCalcXorCrc16 = (WORD)(reCalcCrc16 ^ 0x0080);
	if (pDiscPerSector->subcode.current[22] == HIBYTE(reCalcXorCrc16) &&
		pDiscPerSector->subcode.current[23] == LOBYTE(reCalcXorCrc16)) {
		// FIFA 99 (Europe) http://redump.org/disc/23791/
		OutputLog(standardOut | fileDisc
		, "Detected intentional subchannel in LBA %d => SecuROM 1st version (a.k.a. OLD)\n", nTmpLBA);
		pDisc->PROTECT.byExist = securomV1;
		break;
	}
  1. Results of calculations, incorrect subQ is recognized as SecuROM unfortunately.

From my experience dumping a lot of Microsoft CDs, older Microsoft OS and software CDs are not protected by SecuROM

Definitely yes. The way to solve this problem is not to use /ns. When dumps non-SecuROM disc, there is no point in using /ns.

@OldMadMan
Copy link
Author

I now find that this problem may be related to whether the disc is clean and the ability of the optical drive to read the disc.

In some cases, when I use detergent to clean the disc surface before reading the disc, or slow down the speed at which the disc is read, DIC does not consider the disc to be SecuROM protected. But in other cases, DIC will think that the disc is SecuROM protected even if I am reading a brand new disc that has just been opened.

Since the Plextor optical drives I use are products from more than ten years ago and the laser heads have aged, it is actually difficult for me to determine the root cause of the problem.

@thegawin
Copy link
Contributor

Can tell from experience that small amount of residue on disc can cause Securom (old).

Probably something like light layer of vegetable oil would reproduce this.

@malvarenga123
Copy link

@OldMadMan @mrpijey I think it's best to remove the /ns option from regular discs from the BA guide/batch file. As @saramibreak said, it's only useful for Securom discs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants