3.68 KBつ (NoCD EXE) CD-Check汎用 rev2.rar 2.78 KBつ (NoCD. 1.85 KBつ (NoCD Patch) Safedisc 2.90.40汎用 [SystemSoftAlpha,Unicorn-a,koei他].rar. SafeDisk 2 is one of the latest CD Protections to come from the Macrovision Corporation and works a lot more effectively than SafeDisc did. The SafeDisc 2 protection was first encountered on Red Alert 2.
Contents. History There have been several editions of SafeDisc over the years. Each one has the goals of making discs harder to copy. The current revision is marketed as SafeDisc Advanced.
The early versions of SafeDisc did not make the discs very difficult to copy. Recent versions 2.9+ could produce discs that are difficult to copy or reverse engineer, requiring specific burners capable of emulating the 'weak sectors' and odd data formats that are characteristic of SafeDisc. Circumvention Previous versions of SafeDisc were overcome by software such as. SafeDisc currently such software, meaning that those who want to use this method must install additional software to cloak the mounter; examples include and Another potential attack on SafeDisc is to pull the encrypted application out of the archive it is contained in. All SafeDisc encrypted discs contain an ICD file, an encrypted format used by SafeDisc to ensure that the original CD is loaded. UnSafeDisc circumvents and decrypts SafeDisc encrypted files by opening the ICD file format, decrypting it, and converting it to an EXE file.
However, each program requires a specific patch to enable full functionality. Operation SafeDisc adds a unique to the optical media at the time of replication. Each time a SafeDisc-protected program runs, the SafeDisc authenticator performs various security checks and verifies the SafeDisc signature on the optical media. The authentication process takes about 10 to 20 seconds. Once verification has been established, the sequence is complete and the program will start normally. The SafeDisc signature is designed to be difficult to copy or transfer from the original media.
(For example, it might change as a result of during the copying process.) Certain multimedia programs are designed to run from the PC's hard drive without accessing files from the program disc after the initial installation. SafeDisc will permit this as long as the consumer retains the original CD or DVD, which is required for authentication each time the program is launched. Failure to place the original disc in the drive when loading the program will prevent validation of the SafeDisc signature. Windows 10 Shortly after the release of Windows 10, Microsoft announced that games with SafeDisc DRM will not run on its new operating system, with them citing security concerns over the software due to the way in which it becomes 'deeply embedded' in the system, Microsoft said that supporting SafeDisc could have been a possible loophole for computer viruses to exploit. Version History SafeDisc (V1) (1998-2001) SafeDisk V1 protected CDs can be recognized by several files on the CD:.
00000001.TMP. CLCD16.DLL. CLCD32.DLL.
CLOKSPL.EXE. DPLAYERX.DLL And also by the existence of two files.EXE and.ICD (where is replaced with the actual game's name). The EXE executable is only a loader which decrypts and loads the protected game executable in the encrypted ICD file.
The initial version of SafeDisc was easy for home users and professional duplicators alike to copy, due to the fact that the ICD file can be decrypted and converted into an EXE file. SafeDisc (V2) (November 2000 - 2003) The following files should exist on every original CD:.
00000001.TMP. 00000002.TMP (not always present) The loader file (.EXE) is now integrated into the main executable, making the.ICD file obsolete. Also the CLOKSPL.EXE file, which was present in SafeDisc v1, no longer exists. The SD2 version can be found inside the.EXE file through its string: BoG.90.0&!! Yy, followed by three unsigned longs, these are the version, subversion and revision numbers (in hex).
When making a backup, read errors will be encountered between sectors 806-10663. The protection also has 'weak' sectors, introduced with this version, which causes synchronization problems with certain CD-Writers. Digital signatures are still present in this version. But this has no effect on disc images mounted in Daemon Tools or similar programs. In addition, SafeDisc Version 2.50 added detection making it impossible to use a copy in a burner unless software that masks this is used ( has the ability to do this.
) SafeDisc Versions 2.90 and above make burning copies more difficult requiring burners that are capable of burning the 'weak sectors'; these drives are uncommon. However, there are software solutions that eliminate the need for specialized hardware. SafeDisc (V3) (2003-2005) SafeDisc v3 uses a key to encrypt the main executable (EXE or DLL) and creates a corresponding digital signature which is added to the CD-ROM/DVD-ROM when they are replicated. The size of the digital signature varies from 3 to 20 MB depending how good the encryption must be. The authentication process takes about 10 to 20 seconds.
SafeDisc v3 is capable of encrypting multiple executables over one or more CDs/DVDs, as long as the executables are encrypted with the same key and the digital signature is added to each media. SafeDisc v3 supports Virtual Drives as long as the original CD/DVD is available. Once the CD has been authenticated the game should continue to run from the virtual drive, provided the virtual drive software has not been blacklisted. Is able to make copies of V3. SafeDisc (V4) (2005-2008) The final major SafeDisc version was Version 4, released in February 2005. It lost ground to over time, with the final build being version 4.90.010 in May 2008; with the product being discontinued on March 30, 2009. SafeDisc driver vulnerabilities On November 7, 2007; Microsoft stated that 'there is vulnerability in Macrovision SECDRV.SYS driver on Windows and it could allow elevation of privilege.
This vulnerability was patched by Microsoft on December 11, 2007 This vulnerability does not affect Windows Vista. The driver, secdrv.sys, is used by games which use Macrovision SafeDisc.
Without the driver, games with SafeDisc protection would be unable to play on Windows'. Ultimately, this would prove to be one of the factors that would lead to them to drop support for the program in 2015. See also. References.
Welcome to the Forums! Unfortunately, most of the sites that hosted No-CD/SafeDisc removal patches have disappeared, and many of them promoted software piracy. You may be able to find the patches on BitTorrent services, but that's not really a good idea - the risks of also downloading malware in the process are way too great. Some of the available Revelation electronic downloads might play on Win 10. For example, from Revelation uses SafeDisc 3 DRM.
Try doing a Google search for SafeDisc 3 DRM removal. See also: - -. If all of that isn't satisfying, take a look at the following: - - -. Thank you for replying. However, I'm not looking for unofficial or possibly illegal patches and cracks.
That fellow in the forum I linked to first provided a direct link to a ubisoft server for precisely the patch I need - supposedly, a fix that would remove SafeDisc from the game. He (or she) wasn't posting a link to a shady 3rd party site. I know you're a moderator, and maybe not a Ubisoft employee, but I would really appreciate it very much if you would send a message out to whomever you have contact with at Ubisoft from the old days (that post with the zip file URL is from 2004 - hard to believe!) and ask if that zip file is still around. Someone hopefully has it somewhere. I'd much rather have the official Safedisc removal method, safely from Ubisoft servers, then to try to 'hack' my system to remove safedisc, or more likely with Windows 10, deal with the fact that the game might be unplayable because Safedisc doesn't work. Or can you confirm for me that patch 1.03 removes Safedisc? My game file is still at the original DVD version; I tried it once yesterday, it crashed, so I came here.
I want to try the patches next, but if the patches don't remove SafeDisc then I still have a problem - I can't afford to play a game with a RootKit (which is what SafeDisc sounds like to me, similar to SecureROM) on my PC. I need to make sure the driver is removed. Thank you again for your time and for helping me out.
In general, - a. Install Revelation to your C: drive. If you have a very small C: that's reserved for system files only, install Revelation to D. Do NOT install the game to an external drive, either USB or E-SATA. Start Revelation from a fresh boot.
Disable all anti-virus/spyware/adware/pop-up programs running in the background. If you have only a software firewall (ZoneAlarm, for example), do NOT disable it! Do NOT run any other programs before starting Revelation. Do NOT boot up with a CD or DVD in any drive. If the Revelation disc autostarts when you insert it into the drive, cancel back to the Desktop. Start the game using the Revelation icon on the Desktop, NOT the menu item on the Revelation disc.
For the record, the moderators on these Forums are volunteers and are NOT Ubisoft employees. The Version 1.03 patch by itself does not remove Safedisc. It is, however, part of a process. If you open at the top of this Forum (and there's a very good reason for the title!), you'll find. The process is explained in the latter thread, and to the necessary files works.
The Revelation patches are available. I recommend applying the 1.02 patch and then the 1.03 patch. The 1.02 patch is 41.1 MB, while the 1.03 patch is only 15.4 MB, which may mean there's 'good stuff' included in 1.02 that isn't included in 1.03. Apply the patches as follows after re-installing Revelation: - a. Log into Windows with full Administrator privileges, and close all open applications.
Click on Start Run. Browse to myst4v1.00tov1.02pc.exe, and double-click on it to put it in the Open: box. Click on OK to start the install process.
Follow the Wizard's instructions, and accept the install defaults. Reboot when installation is complete. Log into Windows with full Administrator privileges, and close all open applications. Click on Start Run. Browse to myst4v1.0tov1.03pc.exe, and double-click on it to put it in the Open: box. Click on OK to start the install process. Follow the Wizard's instructions, and accept the install defaults.
Reboot when installation is complete. Start Revelation from a fresh boot as per steps b.
Under 'In general', above.