5_day_forecast on 14/1/2009 at 09:09

---

Simple process that got movies working for me in Vista.

First off, make sure the codecs are loaded. Run iv5play.exe (should be on the install CD.

Now, to make sure Vista registers the codecs. Vista has a nasty habit of NOT allowing some changes to occur unless you're "running the program as an administrator". This was, for me, the problem with the codecs registering. SO - go to the DOS prompt (should be in the start menu under Accessories) and RIGHT CLICK it, then select Run As Administrator.

If you don't do this, it won't work. You'll get that "registration did NOT succeed" error.

Okay then - first off, type this in the command prompt:
regsvr32 "c:\(WhereYouInstalledSShock2)\LGVID.AX" Hit Enter. If the codecs are installed, this will register 'em.

(don't remember if the prompt automatically closes. IF it does, re-open as an Admin again and continue)

Now, type this in:
regsvr32 ir50_32.dll Hit enter.

That's it. Start playing the game!

Ostriig on 18/1/2009 at 09:39

---

A lot of headaches with this Admin bullshit on Vista can be solved by disabling User Account Control. It's something that I recommend getting rid of as soon as you install Vista, along with Program Compatibility Assistant to save yourself some more headaches. Dumping DEP completely is also an option, but some people might prefer to keep it on.

At any rate, UAC might be relevant to your problem, here's how to ditch it: bring up the System Configuration window (Start -> Run -> msconfig), go to the Tools tab, and scroll down to the Disable UAC option, click Launch and then reboot. If, for God knows what reason, you later decide you want it back, the Enable UAC is just below it. Now, once that's done, I don't think you still need to select Run As Administrator, provided you are logged on an Admin account, but I don't know for sure so I gave it a try with the Run As Admin option and the CMD prompt started just fine. Give it a shot.

Oh, and... I mean no offense, and have no reason to bear you any ill will, but as per ZB's observation I can't wait for you and catbarf to disagree on something and start a pissing contest. Sorry. :p

AxTng1 on 18/1/2009 at 22:45

---

i hear all martians are gay never met one but thats what it said on fox

Anyway, DEP controls what areas of memory a program can write to. Older programs such as emulators that use very low level instructions can be defeated by this measure, as Windows (of ANY post-ME version) insists on its own memory management. I don't know if this affects the old indeo codec because I always turn it off during setup. If you don't want to go this far, shock2.exe (and lgvid.ax? or is it regsvr?) can be added to exceptions.

SS2 works perfectly on my Vista x64 thanks to Kolya's excellent (http://www.strangebedfellows.de/index.php/topic,392.0.html) patch. The only problem is ATI driver dithering, but that's not really Vista's fault.

catlord on 19/1/2009 at 00:04

---

Ah, okay.

Al_B on 21/1/2009 at 23:33

---

Yes - it's just an additional control over what you can do with a memory area. There are some very good reasons for being able to execute code from a data area but in most cases it means that either something's gone horribly wrong or it's a deliberate attempt to inject code.

In any case, if a program's well written then it can specify where code needs to run from a data segment so it shouldn't be a problem whether DEP is turned on or off.