Yep, after the new patch this is still happening to me. It won't even start Vanguard launcher. I am running the same setup eaglepigjim is, win2000 pro.eaglepigjim wrote:I'm getting the same problem. Everything was working yesterday on my Windows 2000 pro sp4 box. Innerspace patched today and now I get the following 2 errors:
The application failed to initialize properly (0xc0000142). Click on OK to terminate the application.
The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "read". Click OK to terminate the program
Thanks[/img]
Vanguard Crash Issue
Moderators: Lavish Software Team, Moderators
sorry i didnt read this i just started a new thread with same problem i have restarted inner space and i still ahve the problem.. i have even disabled sound.. and still not working
Operating System: Windows 2000 Professional (5.0, Build 2195) Service Pack 4
Language: English (Regional Setting: English)
System Manufacturer: ECS
System Model: K8M890M-M
BIOS: Default System BIOS
Processor: AMD Athlon(tm) 64 Processor 3200+, ~2.0GHz
Memory: 1920MB RAM
Page File: 166MB used, 3646MB available
Card name: NVIDIA GeForce 7900 GT/GTO
Display Memory: 256.0 MB
Description: Realtek AC97 Audio
Operating System: Windows 2000 Professional (5.0, Build 2195) Service Pack 4
Language: English (Regional Setting: English)
System Manufacturer: ECS
System Model: K8M890M-M
BIOS: Default System BIOS
Processor: AMD Athlon(tm) 64 Processor 3200+, ~2.0GHz
Memory: 1920MB RAM
Page File: 166MB used, 3646MB available
Card name: NVIDIA GeForce 7900 GT/GTO
Display Memory: 256.0 MB
Description: Realtek AC97 Audio
My apologies, this would be fixed already but I was on the road and today I have a wedding reception to go to. Build 4501 is now up as a development build -- you can revert to it by checking the "Download development patches" box in the Inner Space patcher window, and restarting IS. I believe I have the newer crashes solved, but I can't test Vanguard from my laptop and I've only got a little bit of time before I have to leave for the day.
I crash with 4501 and have disabled the audio. But it's not an audio problem, it won't even run the launcher before crashing on the above stated error. It's exactly the same with 4505.Lax wrote:If you crash with build 4501, you need to disable audio. If you crash with 4505, it's for a completely different reason and you should switch to the development build (4501).
I will do what I can to take care of the issue today.
-
- Non-Subscriber
- Posts: 9
- Joined: Thu Apr 05, 2007 9:20 am
-
- Non-Subscriber
- Posts: 9
- Joined: Thu Apr 05, 2007 9:20 am