PDA

View Full Version : Securom 7 errors explained


renhoekNL
02-12-2005, 20:13
I've been messing about with Star Wars - Battlefield II to try and get my backup to run. Previously I've run into a lot of problem trying to get F.E.A.R. to run too, so I'll share my experiences with you, so you might have less trouble then me at first.

When you start a Securom 7 game backup, most likely you will run into error messages. However, these can help you to figure out what goes wrong so that you take the next step to correct the problem.

Always create an image file with the latest version of Alcohol 120%. Be sure to create an .mds file during copying. Image at the lowest speed. This might be enough to get the game running without having to download additional .mds files or mini/maxi images.

When you start the game and get an error, look here:


Security module could not be loaded
The program is detecting your CD drive emulation software. Be sure to run a program to hide your virtual drive. Example: SR7 stop.


Please insert the original disc in drive X:
You still have a real CD drive available to the game. It will prefer ATA drives over the SCSI drive that for example Daemon tools is emulating. Run a program like Starforce Nightmare to 'disable CD' and with that hide the real drive from the game.


Please insert an original disc instead of a backup disc
Your game image is invalid. Please get another .mds file for gamecopyworld. Note that it's sometimes not clear if a .mds file on the site is from a CD or DVD image. Download them all and experiment with them.



If you have any additional info or if I made mistakes, please post corrections here. :)

Papio
03-12-2005, 03:31
Thanks renhoekNL, your post if more useful to me that you could possibly imagine.

DABhand
03-12-2005, 06:09
Security module error can also be due to it detecting programs like Sr7Stop also.

GLH
03-12-2005, 06:42
I've been messing about with Star Wars - Battlefield II to try and get my backup to run. Previously I've run into a lot of problem...I searched and searched, but I wasn't able to find anything about a game named "Star Wars - Battlefield 2". Only "Star Wars - Battlefront 2" i found... :D:D:cool:

Grumpy
03-12-2005, 06:57
@GLH
I wasn't able to find anything about a game named "Star Wars - Battlefield 2
Well noticed! I didnt pick that one up! I should have had a Good Look Here. :D Eagle Eye GLH. :D ;)

Papio
03-12-2005, 15:01
After your post I got to thinking, why oh why would I get a security module error since I’m using DT4 and SR7.Stop 1.2

The answer: Gamejacks inability to uninstall its down damn virtual drive and after many many attempts to get rid of this virtual parasite I finally reinstalled the program, found the MSI file that installs the universal Scsi controller, right clicked on it and selected uninstall.

Now I can play Stubbs from a HDD backup. YAY :)

TippeX
03-12-2005, 16:58
i thought the messages only happen if you try and launch the game using an image/virtual drive, at least for me using the original disk didnt cause a problem, backup/mounting got me the dreaded messages though ;(

hyakkii
03-12-2005, 17:41
security module error can be caused from a number of things mostly if anything is running application hooks (ie hypersnap dx will make the game get security module error ) or debug applications.

This is actully a bug and running in windows 2000 compat mode will fix alot of the errors but its not full proof.

DABhand
03-12-2005, 17:55
Why run in 2000 compatibility, you wont get great performance from it.

hyakkii
03-12-2005, 18:29
Why run in 2000 compatibility, you wont get great performance from it.
Ask the protection company this is/was listed as an "official fix" and is also on all the major game support and knowlagebase support pages.

it also seems for most people the major contributation to this security module error is getright (again it could be any program that has hooks :)

Aristarchus
04-12-2005, 03:27
Hi! In the last months i have come to realise that the achohol 120% and fake image way spreads as a solution to the backing-up games problem while the traditional no-cd(dvd) fixed exe is fading out. That makes me wonder... why do people want to make their lives harder with all that images, programs that work only in MS windows systems and stuff? Have all the crackers like deviance died or been been arrested or something? I guess not because recently they released a crack for quake 4 (old traditional fixed *.exe) which by the way has the same protection system like civ 4 (for which a crack hasn' t been released but that bloody image stuff again). Someone would say that new systems are tougher and perhaps unbreakable(but i dont think so as i explained above). I invite a cracker to state his opinion about his matter here(or in another post if he thinks suitable) and/or explain why the this systems are so tough to be cracked, the differences with older systems and the exaxt spot that he/she finds difficulties, even post related assembly code. Some of us would listen and undestand or even be able to help. But i think thats just not the case. Imo, the case is that most people are confortable with that new way since they just want their games to play in their personal computer at home and they dont care furthermore. Am I correct? Someone with knowledge in the matter answer me plz.

Papio
04-12-2005, 03:51
Not a cracker but I know at least one reason why images/mini images are better

Patch-ability, take your example "Civ 4" was so riddled with bugs at pre-patch a huge amount of players experienced a CTD at least once an hour. (if they could play at all)

renhoekNL
05-12-2005, 00:42
why do people want to make their lives harder with all that images, programs that work only in MS windows systems and stuff? Have all the crackers like deviance died or been been arrested or something?

1) fixing images is easier then cracking exe's
2) patchability as previous poster pointed out

And it should not be too hard to fix up mount's loopback code to include .mds functionality if you're trying to run games under linux. Ofcourse the 'security module' might trip on linux itself instead of only the dvd encryption bit.