1.5 And SecuROM
 

I've had the digital download version of the uboat addon for awhile, but I haven't been playing it for a bit. I did play it for awhile after I got it with no problems. I returned to SH4 recently, and am greeted with an error message about CmdLineExtInstallerExe.exe not being able to find WSOCK32.dll. I traced down the program and it is something that SecuROM installs. I was certain that SecuROM was essentially removed (and I did also remove it manually) after 1.3. However, after running the Sony provided removal util (which is the only thing I've found that's able to remove the license stuff in the registry as well), rebooting and all that, SecuROM installs itself again each time I run SH4. It's possible that SecuROM has been lingering since installing the uboat addon all those months ago and just never showed a problem until now. It's also possible that the autopathcer (if it even works...) did something to add it back. Has anyone else encountered signs that 1.5 has put SecuROM back in? I'm going to try reinstalling the uboat addon, hopefully that will clear it up...

Dont get me started on SecureROM... I have issues with my machine now. Not from SH4 but another game.

To put it in a nut shell now all my apps take a coons age to launch.

Very aggrivatting.

Im considering reformatting.

Effin copy protection schemes all they do is punish the legimate users.

I downloaded but haven't installed the UBoat add on should I be worried? Does it include secureROM? Other than SH4 I am not a gamer and no nothing about this copy protection
stuff. does this have the potential to fubar my machine?

Urge

I wouldent worry too much, I am a 'gamer' and have alot of different games with various copy protection schemes installed / uninstalled / re-installed.

Sooner or later all that copy protection crap begins to conflict and it takes 10 minutes to read a disk ... sigh... :oops:

But if you only have a few games installed... probably no problems.

Look in my sigi.

I think the error is caused by the offending application looking for wsock32 in the wrong folder. Since the applications folder isn't in the windows/system32 folder like it would be on a 32 bit OS. The solution may be as simple as copying wsock to the folder the applications dll is stored in...

Wsock32.dll is a system file
 

It is the 32 bit application programming interface for networking and is a system file provided by Microsoft. It allows programs to access TCP/IP network communication. It should be in the System32 folder. The installer is trying to use it to gain internet access but can't find it on your system.

Even though it is conveniently located in the system32 folder... I think we may have foind a weakness in SecuROM... Just have to pin it down, and figure out how to exploit it...

You might try this..

http://www.securom.com/message.asp?m=analysis