Vanguard Crash Issue

Post by **Lax** » Thu Aug 16, 2007 8:51 am

Well, IS build 4508 is up as a development build, I'm waiting on hearing if it solves the crash issues or not. If anyone can test it and let me know that'd be great.

craf · Post by **craf** » Thu Aug 16, 2007 7:40 pm

no go lax, still broke

eaglepigjim · Post by **eaglepigjim** » Thu Aug 16, 2007 8:22 pm

Hi Lax,

I tried the development patch but got 4513 instead of 4508 and I still get the same 2 errors as before. The Vanguard patcher does not launch at all.
Windows 2000 SP4 here.

Thanks for tryign to fix this.
J

craf · Post by **craf** » Thu Aug 16, 2007 10:18 pm

let us roll back, was perfectly happy before the update. You do have an older rev we can get to?

Spritzen · Post by **Spritzen** » Fri Aug 17, 2007 5:25 am

Boo Hoo, was hoping this would have been fixed or rolled back to a working version before GU2 came in

Any news Lax?

Spritzen · Post by **Spritzen** » Fri Aug 17, 2007 5:59 pm

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

Still Happening on win 2000 for 1.09 Build 4526

Post by **Lax** » Sat Aug 18, 2007 9:48 am

Looks like everyone is fixed except for Windows 2000 users. I'll see what I can do, but seriously, Windows 2000?

smushi · Post by **smushi** » Sat Aug 18, 2007 10:39 am

yea still cant use it kind of sucks...

Spritzen · Post by **Spritzen** » Sat Aug 18, 2007 4:41 pm

Still Happening on win 2000 for 1.09 Build 4527

Win2000 has served me well

I appreciate your efforts, trying to hunt this down Lax.

eaglepigjim · Post by **eaglepigjim** » Sat Aug 18, 2007 6:51 pm

Hi Lax,

I run Windows 2000 on all my secondary machines, if you can't get it fixed, can you just check for the OS and let us windows 2000 users use the last patch that worked for us and we dont get any ongoing fixes?

I really dotn want to have to go and spend $ upgrading all my older PCs OSs, they can all handle Vanguard at minimum settings just fine.

Thanks
J

craf · Post by **craf** » Sun Aug 19, 2007 9:41 am

Why Win2k?
I have laptop on XP that runs fine but hey it's a laptop and a older Win2k workstation that still works fine with VG but broke with Innerspace. I am going to get a new screamer someday with Vista but not for a while. I really don't want to pay for XP for my old comp. I also agree that I would be just fine with no furthur updates to have a rolled back version that works.

Post by **Lax** » Sun Aug 19, 2007 10:19 am

You might think that'd be a good idea, but what will happen is something you use will start to require newer updates or it wont work at all. For example, as soon as ISXDK updates to version 31, the current version of Inner Space will not work with new releases of ISXVG, and you won't be able to use it at all.

I'm not asking anyone to switch to a different version of Windows, just frustrated that the one version of Windows that I don't own is the one causing problems, and I don't have anyone to try potential fixes with a short response time. If any of you have the ability to get debug output from the crash, that would help since it's not giving the Lavish Crash Reporter.

Post by **Lax** » Sun Aug 19, 2007 11:11 am

Build 4528 is up now, and may fix the problem. Please let me know

craf · Post by **craf** » Sun Aug 19, 2007 1:07 pm

Build 4528 no help. The failure is immediate. Here is the error.

-Vanguard.exe-
The application failed to initalize properly (0xc0000142).
Click ok to terminate the application.

Afetr clicking ok--

-Vanguard.exe-
The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "read".
Click on OK to terminate program.

Thats all I can get, nothing in console. I have no idea if this is pertainant but heres Innerspace.dat

-snip-
1:LavishPatcher.exe:143360:497026181
2:Lavish.dll:114688:-1113685008
4:LavishCrashMobile.exe:61440:-529288043
3:InnerSpace.txt:118820:689135674
10:InnerSpace.exe:319488:-63608362
11:InnerSpace.dll:266240:-1453245966
12:IS-D3D8.dll:397312:-610912
13:IS-D3D9.dll:126976:8898389
18:IS-OpenGL.dll:90112:233108358
21:ISUI.dll:1306624:-1761986066
22:Interface\WindowControls.png:704:26555294
24:Interface\Button.png:1021:-1534730266
25:Interface\CheckBox.png:969:-78638273
26:Interface\DefaultUI.xml:4161:486810057
27:Interface\Slider.png:1031:-642872903
28:Interface\Gauge.png:780:-174299653
29:Interface\ScrollBar.png:801:-1735937465
30:Interface\DefaultSkin.xml:31861:1817490020
31:Interface\TabControl.png:996:-25695653
32:Interface\ComboBox.png:683:1821855244
34:GameDetection.XML:18779:-895216540
37:Scripts\DefaultStartup.iss:4439:1768281148
38:Scripts\DefaultPreStartup.iss:772:55187406
39:IS-Kernel.dll:1257472:-580034108
40:Interface\DefaultUplinkUI.xml:70398:-1178047476
41:IS-D3D9Engine.dll:114688:1144500808
43:IS-VirtualInput.dll:151552:-387841104
44:LavishScript Modules\Targz.dll:155648:1473235943
45:Lavish.InnerSpace.dll:61440:907160235
46:Lavish.LavishVMRuntime.dll:20480:178677524
47:Lavish.LavishNav.dll:36864:830010985
48:Lavish.InnerSpace.xml:72249:-754376941
49:Lavish.LavishNav.xml:38724:-1005728974
50:.NET Programs\IS-DotNetScript.exe:20480:-1874585317

craf · Post by **craf** » Sun Aug 19, 2007 1:09 pm

I am available today to try out any new patches you throw up. It's pouring down rain , I am bored and will love to help fix this.