Sysinternals Homepage
Forum Home Forum Home > Sysinternals Utilities > Filemon
  New Posts New Posts RSS Feed: Filemon vs TR:Legend’s SecuROM
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Filemon vs TR:Legend’s SecuROM

 Post Reply Post Reply
Author
Message Reverse Sort Order
molotov View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 October 2006
Online Status: Offline
Posts: 17492
Post Options Post Options   Quote molotov Quote  Post ReplyReply Direct Link To This Post Topic: Filemon vs TR:Legend’s SecuROM
    Posted: 30 November 2008 at 5:09pm
Hi Iain,

SecuROM does not seem to like it when specific drivers are resident.  Rebooting will unload the drivers.  So, you may need to note what you run before launching Football Manager, to attempt to determine which program SecuROM / Football Manager does not like, if  it does not tell you outright.  Or, you could consider contacting the developer of Football Manager - they may be able to tell you, or tell you how to find out.
Daily affirmation:
net helpmsg 4006
Back to Top
jenkins252 View Drop Down
Newbie
Newbie


Joined: 29 November 2008
Location: United Kingdom
Online Status: Offline
Posts: 1
Post Options Post Options   Quote jenkins252 Quote  Post ReplyReply Direct Link To This Post Posted: 29 November 2008 at 4:58pm
I've had a similar problem when trying to run Football Manager 2008 but I don't know enough about computers to get the thing to run, can anyone suggest how I can fix this SecuROM problem? I have no idea which process it might be that is stopping it working
Back to Top
Karlchen View Drop Down
Senior Member
Senior Member
Avatar

Joined: 18 June 2005
Location: Germany
Online Status: Offline
Posts: 5121
Post Options Post Options   Quote Karlchen Quote  Post ReplyReply Direct Link To This Post Posted: 25 December 2006 at 6:34pm
Filemon and Regmon, each use their kernel mode driver at runtime.
They load it and use it.
But Mark thinks it is unsafe to unload those drivers while Windows is running. (He wrote them, he should be able to judge. ) They will stay in memory till next reboot.
They will not be reloaded unless you launch Filemon / Regmon again.

Karl
Back to Top
mrfrazzlebottom View Drop Down
Newbie
Newbie


Joined: 28 February 2006
Location: Afghanistan
Online Status: Offline
Posts: 4
Post Options Post Options   Quote mrfrazzlebottom Quote  Post ReplyReply Direct Link To This Post Posted: 25 December 2006 at 5:59pm
Originally posted by MP_ART

Filemon and Regmod driver stay in memory after closing main application. SecuRom just detect it.


Anyway to terminate that "driver that stays in memory?"

Why would Filemon/Regmon do that anyway? SOP?
Back to Top
EP_X0FF View Drop Down
Senior Member
Senior Member
Avatar

Joined: 08 March 2006
Location: Russian Federation
Online Status: Offline
Posts: 4753
Post Options Post Options   Quote EP_X0FF Quote  Post ReplyReply Direct Link To This Post Posted: 17 May 2006 at 6:40am
For preventing FileMon/RegMon from shutdown read this thread

http://www.sysinternals.com/forum/forum_posts.asp?TID=4515&P N=1
Back to Top
MP_ART View Drop Down
Senior Member
Senior Member
Avatar

Joined: 08 March 2006
Location: Russian Federation
Online Status: Offline
Posts: 947
Post Options Post Options   Quote MP_ART Quote  Post ReplyReply Direct Link To This Post Posted: 17 May 2006 at 6:35am
Filemon and Regmod driver stay in memory after closing main application. SecuRom just detect it.
Back to Top
wingnutkj View Drop Down
Newbie
Newbie


Joined: 16 May 2006
Location: United Kingdom
Online Status: Offline
Posts: 1
Post Options Post Options   Quote wingnutkj Quote  Post ReplyReply Direct Link To This Post Posted: 17 May 2006 at 4:07am

I was doing some messing about with my PC last night, and had various Sysinternals goodies running, including Filemon.

After I'd finished messing, I decided to have a quick blast at Tomb Raider: Legend (reasonably good fun, disappointingly lacking the massively sprawling vaguely non-linear levels of the original). Except, when I went to run it, I got a not-terribly attractive message box telling me "A required security module cannot be activated. This program cannot be executed (5001).", with a link to here, which tells me "SecuROM™ has determined that some File Monitor or Registry Monitor program is running in the background. Please close this program before you start the application."

Hrm. After a check with Proces Explorer to see there was anything obvious still floating around, I started Filemon back up, just to see what kind of skullduggery was going on with this SecuROM software. Magically, Tomb Raider loaded!

So yeah - if you run filemon on your system, then quit it, Tomb Raider: Legend won't run unless you either reboot or restart filemon. Really fills me with confidence that it's doing its job.

I was tempted to send off a sarcastic email to them, but it'd only encourage them.

Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down