HaloMods "Classic" Read-only Archive

So i've been trying to do some modding on my girlfriends PC but this seems to happen when I want to open a specific program I have for Halo1.



I can click "ok" and it opens the program as normal but when I go to open the actual .map it gives me an error and quits. It's not a problem with vista. I've updated the directx. I've even updated her graphics card. This seems to be a problem spanning either from "Presario/Compaq" products or it's the intel graphics chipset installed. When I right click on her desktop it gives me the option for graphics options. That button brings me to Intel Graphics Media Accelerator window. Where I can go into the 3d settings and mess around with the OpenGL stuff.

My idea is that it's probably the OpenGL API. I have no idea if you can switch your computer to use Directx API's or if that's not possible. I don't know nitty gritty about graphics stuff.

Note* This happened awhile ago with her older computer which ran Windows XP but also had a Intel Chipset for the display adapter. Can anybody please help me fix this. I'd appreciate it highly.

DirectX and OpenGL are both supported by Intel.. also there's no need to do any 'switching'; the computer will know which renderer to use. As for why your getting the error.. That error message is rather crap and doesn't really give any clues..

It's possible that the application may have been badly coded, and so it doesn't work well with todays' hardware. That's my only guess unless you can get a more detailed error message :\

There is another error message after opening the .map. So I guess that could work.

I don't think it has anything to do with today's computer and such. I have an up to date computer with an ATI graphics card and the program works for my computer...it just seems to be my girlfriends computer's. As I said before though, they are both compaq presario's...which is weird. I'll get the error later.

Maybe its a compatibility issue in whichcase i suggest going into properties and choose "run as winxp sp2"

Dalek wrote:Maybe its a compatibility issue in whichcase i suggest going into properties and choose "run as winxp sp2"

Already tried that. It doesn't work.