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

[VickJr]

WORKED-after downloading the d3dx9_37.dll

 
Time of this report: 5/27/2009, 17:33:21
       Machine name: DAN-910AAEB67EB
   Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.090206-1234)
           Language: English (Regional Setting: English)
System Manufacturer: AOPEN_
       System Model: AWRDACPI
               BIOS: Phoenix - AwardBIOS v6.00PG
          Processor: Intel(R) Celeron(R) CPU 2.70GHz
             Memory: 2048MB RAM
          Page File: 1129MB used, 2814MB 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

32 bit

I even tried it with xfire and it worked. (though I don't know if xfire worked. It Gave an unhandled system error in the background and took a while, but then continued and worked as normal.

I did NOT have a custom ui but I DID have ONLY custom maps being used (not default maps), so I can confirm that that is not a problem.

[Limited]

Try using this build. I compiled the dll that Jcap linked to in the main post, and apparently I compiled in a debug config which could fuck things up for some people. So anybody who has had a problem, try using this build.

Nah I tried that, same problem. I'll look into it tomorrow. Maybe compile my own version of OS.

[English Mobster]

Tried the default UI, same problem.

Tried ShadowSpartan's DLL, same problem.

[sdavis117]

I think you need to put Shadow's DLL into your system 32 folder, then run Halo CE in XP compatibility mode.

Maybe it is just me, but that DLL reminds me of one I had to use to get Dark Basic to work on W7, and that's how I got it working.

I may be wrong though.

[New101]

I got halo ce working fine yet when i go to run the default sapien It crashes.

Debug says :

05.28.09 00:10:02 Couldn't read map file './sapienbeta.map'
05.28.09 00:10:02 EAX: 0x00000000
05.28.09 00:10:02 EBX: 0x00000040
05.28.09 00:10:02 ECX: 0x00000000
05.28.09 00:10:02 EDX: 0x00000000
05.28.09 00:10:02 EDI: 0x0012EDE0
05.28.09 00:10:02 ESI: 0x0012F310
05.28.09 00:10:02 EBP: 0x0012F1BC
05.28.09 00:10:02 ESP: 0x0012EDC4
05.28.09 00:10:02 EIP: 0x00417E20, 8B 01 8B 96 ?????
05.28.09 00:10:02 7C817077 ?????
05.28.09 00:10:02 00751B18 ?????
05.28.09 00:10:02 004F8200 ?????
05.28.09 00:10:02 EXCEPTION_ACCESS_VIOLATION


I take the .dlls out of halo ce and sapien opens fine

[Advancebo]

Yeah, OS crashes my Sapien too. I fixed it by just removing the d3d9.dll file out of the halo custom edition folder.

[English Mobster]

I think you need to put Shadow's DLL into your system 32 folder, then run Halo CE in XP compatibility mode.

Maybe it is just me, but that DLL reminds me of one I had to use to get Dark Basic to work on W7, and that's how I got it working.

I may be wrong though.

System 32? Not your CE folder?

I'll try it...

E: OK. Halo's running, but I can't open the console. I hit ~ and nothing appears, plus I can still move, etc. I'm going to enable devmode and try it again.

EE: Console appeared, but the gravity command didn't work. Going to put d3d9 in CE folder, try again.

EEE: Exception. I'm going to try Windows 98 compatibility like I have to for Sapien. Also, Sapien doesn't work.

EEEE: Exception. Trying Safe Mode.

EEEEE: Exception.

[Skarma]

Sapien also relies on d3d9.dll. By default, a program searches the corresponding directory path for the dll files, so they are loaded first. If they are not found, the system directory is searched.

Sapien is loading OS because it needs to load the d3d9 library, when it was not programmed to work with Sapien. Something in the code is making it crash.

I can only hope my help is at least taken into consideration.

[Sel]

Yeah, the issue with the HEK programs is already known about, and will probably be fixed later.

[Skarma]

Yeah, the issue with the HEK programs is already known about, and will probably be fixed later.

Well, unless you wanna do a big hack job, the only logical way to fix it, is to not use a proxy dll for the Direct3D interface. This method for OS is irrational and should consider being changed for the better. There are no perks other than it being a noob-friendly drag into the Halo folder.