UPDATED (2x): OpenSauce and Halo CE Crashing *PLEASE TEST FOR FEEDBACK*

[English Mobster]

Huh. I'm still not getting any text, but I had no memory leaks this time. No clue why it stopped.

May as well throw in my ninja last-second-edit I made on the bottom of the last page:
I did some research, and I found one other person who was using a program VERY similar to OS for Halo PC, who had encountered the same "missing text" problem.

Unfortunately, he fixed it by getting a new video card/reformatting.
All my efforts to reinstall DirectX have failed. Every time, DirectX gives me a message saying that there is a newer or equivalent copy of DirectX installed. While that IS true, there is an equivalent copy installed, it's one which possibly has some broken files. DirectX eradicator thinks I'm running Vista when I'm really running XP with some modifications made to some system files (Something called Vistamizer), so I can't uninstall DirectX.

I think I've found what the hell I did to cause it, as well.
I was one of the first to jump onto the OS thread with this computer, before people explained I needed to put the d3d9.dll into my CE folder. Well, actually, I did put it into my CE folder, but the init.txt caused it to exception. But I didn't know that was what caused it, so I moved the d3d9 into my system32 folder, backing up the original and replacing it.
Now, Windows isn't letting me overwrite it with the backup, even though it was totally fine with me fucking it up in the first place. So I need to be able to delete that d3d9, overriding Windows' "protection" of the DirectX files, so I could reinstall the backup.

[jcap]

Did you try installing DirectX from that link I posted? You don't need to uninstall it - it just installs over the current installation. Doing that should overwrite the dll that you overwrote.

Try booting into safe mode to delete the dll, then replace it. You shouldn't need to take ownership of any kind, like you do in Vista and W7. The actual file protection is caused by the dllcache Windows XP has which monitors the files in the system32 folder for any changes and then replaces them with the backup in system32\dllcache if it notices a change. The copy in dllcache is an original (possibly even old), so you shouldn't touch anything in there.

[supersniper]

... take ownership of the file.
Or log onto the True administrator account.
XP just boot up safemode and it's their.
For vista you need to google how to activate it. (un hide it)

[Kornman00]

If the memory leaks still happen even when OS is NOT loaded, then its not OS...

...

[English Mobster]

Did you try installing DirectX from that link I posted? You don't need to uninstall it - it just installs over the current installation. Doing that should overwrite the dll that you overwrote.

Try booting into safe mode to delete the dll, then replace it. You shouldn't need to take ownership of any kind, like you do in Vista and W7. The actual file protection is caused by the dllcache Windows XP has which monitors the files in the system32 folder for any changes and then replaces them with the backup in system32\dllcache if it notices a change. The copy in dllcache is an original (possibly even old), so you shouldn't touch anything in there.

Yes, straight from your link. It simply tells me that I have a newer or equivalent version of DirectX installed.

... take ownership of the file.
Or log onto the True administrator account.
XP just boot up safemode and it's their.
For vista you need to google how to activate it. (un hide it)

I've tried. =/

...

But I'm not the only one reporting these leaks after using OS. OS is the only common factor here, and both of us only started to get these problems once we installed OS.

[Kornman00]

OS is the only common factor here

Thats a bold claim to make. I wouldn't start jumping to conclusions until we know what else you're both running (as far as applications) while running halo.

See what happens when you run halo pc...

[English Mobster]

No leaks at all with PC. Only CE has an issue.

[Warsaw]

OS works fine for me, using motion blur and faux HDR shaders by FireScythe. Halo CE 1.08, init.txt removed, etc. Even having DXTweaker and XFire running over it didn't cause any issues.

------------------
System Information
------------------
Time of this report: 7/14/2009, 19:31:52
       Machine name: GENSEVEN
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.090206-1234)
           Language: English (Regional Setting: English)
System Manufacturer: NVIDIA
       System Model: AWRDACPI
               BIOS: )Phoenix - Award WorkstationBIOS v6.00PG
          Processor: AMD Athlon(tm) 64 Processor 3200+,  MMX,  3DNow, ~2.2GHz
             Memory: 2048MB RAM
          Page File: 587MB used, 3353MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.2600.5512 32bit Unicode

[jcap]

Even having DXTweaker and XFire running over it didn't cause any issues.

WHAT!?

[supersniper]

OS works fine for me, using motion blur and faux HDR shaders by FireScythe. Halo CE 1.08, init.txt removed, etc. Even having DXTweaker and XFire running over it didn't cause any issues.

WHAT!?

Was it in the root folder or did you inject the .dll file?