P.S. new installation crashing

Post by **BackTrak** » Tue Oct 14, 2014 3:59 am

Hi fin,

A few things:

Ensure that you are running the launcher as admin.

You may need to reset your WMI. I don't see the WMI queries logged in your launcher file. I'm expecting to see lines like this:

Code: Select all

9/30/2014 4:59:41 AM UTC:     opened: HARDWARE\DEVICEMAP\Scsi
            
9/30/2014 4:59:41 AM UTC:     Scsi Port 0
            
9/30/2014 4:59:41 AM UTC:     Scsi Bus 0
            
9/30/2014 4:59:41 AM UTC:     Initiator Id 255
            
9/30/2014 4:59:41 AM UTC:     Target Id 0

If you are not seeing those lines, and you are running the launcher as admin, then you may need to perform these steps:
http://blogs.technet.com/b/csstwplatform/a...dows-7-wmi.aspx

My main suspect is this line, it should show an assembly length, like this, not -1:

9/30/2014 5:07:36 AM UTC: AssemblyLoader::ValidateEntryAssembly() - data length: 9216

Thanks,
-BT

finisher2 · Post by **finisher2** » Tue Oct 14, 2014 4:41 pm

Hey BT,

The respository came back consistent, but I tried resetting it anyways. The reset failed because "a stop contrl had been issued to a service other services were dependant on".

Gotta get back to work but I'll fiddle more when I get home.

BackTrak wrote:QUOTE (BackTrak @ Oct 13 2014, 11:59 PM) Hi fin,

A few things:

Ensure that you are running the launcher as admin.

You may need to reset your WMI. I don't see the WMI queries logged in your launcher file. I'm expecting to see lines like this:
Code: Select all
9/30/2014 4:59:41 AM UTC:     opened: HARDWARE\DEVICEMAP\Scsi
            
9/30/2014 4:59:41 AM UTC:     Scsi Port 0
            
9/30/2014 4:59:41 AM UTC:     Scsi Bus 0
            
9/30/2014 4:59:41 AM UTC:     Initiator Id 255
            
9/30/2014 4:59:41 AM UTC:     Target Id 0
If you are not seeing those lines, and you are running the launcher as admin, then you may need to perform these steps:
http://blogs.technet.com/b/csstwplatform/a...dows-7-wmi.aspx

My main suspect is this line, it should show an assembly length, like this, not -1:

9/30/2014 5:07:36 AM UTC: AssemblyLoader::ValidateEntryAssembly() - data length: 9216

Thanks,
-BT

finisher2 · Post by **finisher2** » Tue Oct 14, 2014 10:12 pm

Hey BT, here's the full log, I think it has a mix of what you're looking for and the other:

and by the way thanks to everyone for trying to help!

Code: Select all

-------------- Log Start 10/13/14 at 11:24 PM UTC --------------

13/10/2014 11:24:22 PM UTC:     Using: Software\Microsoft\Microsoft Games\Allegiance\ for registry root.
            
13/10/2014 11:24:49 PM UTC:     ServiceHandler::LauncherSignIn() - Data received for: chuckles, data length: 9216
            
13/10/2014 11:24:49 PM UTC:     AssemblyLoader::ValidateEntryAssembly() - data length: 9216
            
13/10/2014 11:24:51 PM UTC:     opened: HARDWARE\DEVICEMAP\Scsi
            
13/10/2014 11:24:51 PM UTC:     AssemblyLoader::ValidateEntryAssembly() loaded assembly: System.Reflection.Assembly
            
13/10/2014 11:24:51 PM UTC:     AssemblyLoader::ValidateEntryAssembly() machine info created.
            
13/10/2014 11:24:51 PM UTC:     AssemblyLoader::ValidateEntryAssembly() calling checkin.
            
13/10/2014 11:24:52 PM UTC:     AssemblyLoader::ValidateEntryAssembly() calling checkin.
            
13/10/2014 11:26:36 PM UTC:     AssemblyLoader::ValidateEntryAssembly() - data length: 9216
            
13/10/2014 11:26:37 PM UTC:     opened: HARDWARE\DEVICEMAP\Scsi
            
13/10/2014 11:26:37 PM UTC:     AssemblyLoader::ValidateEntryAssembly() loaded assembly: System.Reflection.Assembly
            
13/10/2014 11:26:37 PM UTC:     AssemblyLoader::ValidateEntryAssembly() machine info created.
            
13/10/2014 11:26:37 PM UTC:     AssemblyLoader::ValidateEntryAssembly() calling checkin.
            
13/10/2014 11:26:39 PM UTC:     AssemblyLoader::ValidateEntryAssembly() calling checkin.
            
13/10/2014 11:26:41 PM UTC:     Login Succeeded
            
13/10/2014 11:26:41 PM UTC:     Using: C:\Program Files\Microsoft Games\Allegiance 1.2\Production\Allegiance.exe -authenticated -callsign=johnbigbootay(0) -debug -nomovies to launch...
            
13/10/2014 11:27:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() - data length: -1
            
13/10/2014 11:27:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() loaded assembly: System.Reflection.Assembly
            
13/10/2014 11:27:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() machine info created.
            
13/10/2014 11:27:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() calling checkin.
            
13/10/2014 11:27:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() calling checkin.
            
13/10/2014 11:28:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() - data length: -1
            
13/10/2014 11:28:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() loaded assembly: System.Reflection.Assembly
            
13/10/2014 11:28:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() machine info created.
            
13/10/2014 11:28:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() calling checkin.
            
13/10/2014 11:28:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() calling checkin.
            
13/10/2014 11:29:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() - data length: -1
            
13/10/2014 11:29:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() loaded assembly: System.Reflection.Assembly
            
13/10/2014 11:29:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() machine info created.
            
13/10/2014 11:29:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() calling checkin.
            
13/10/2014 11:29:41 PM UTC:     AssemblyLoader::ValidateEntryAssembly() calling checkin.
            
13/10/2014 11:29:58 PM UTC:     ProcessHandler()::Debugger - Sending on exit task().
            
13/10/2014 11:29:58 PM UTC:     ProcessHandler()::Debugger - Calling OnExiting().
            
13/10/2014 11:29:58 PM UTC:     AllegianceLoader::process_OnExiting - Called!
            
13/10/2014 11:29:58 PM UTC:     AllegianceLoader::process_OnExiting - System Watcher Closed.
            
13/10/2014 11:29:58 PM UTC:     AllegianceLoader::process_OnExiting - Calling Allegiance Exit.
            
13/10/2014 11:29:58 PM UTC:     PlayControl::AllegianceProcess_OnExiting - Logout.
            
13/10/2014 11:29:58 PM UTC:     PlayControl::AllegianceProcess_OnExiting - AllegianceExited called.
            
13/10/2014 11:29:59 PM UTC:     Allegiance process has ended, forcing processHandler to close.
            
13/10/2014 11:30:00 PM UTC:     Allegiance process was not found, this is normal. The message was: System.ArgumentException: Process with an Id of 2368 is not running.
            at System.Diagnostics.Process.GetProcessById(Int32 processId, String machineName)
            at System.Diagnostics.Process.GetProcessById(Int32 processId)
            at Allegiance.CommunitySecuritySystem.Client.Integration.ProcessMonitor.<.ctor>b__0(Object param) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Integration\ProcessMonitor.cs:line 47

finisher2 · Post by **finisher2** » Sat Oct 18, 2014 12:05 am

finisher2 · Post by **finisher2** » Sat Oct 18, 2014 12:06 am

Hey Phantom,

Lost my high-speed internet, such as it was anyways, had it back briefly tonight, long enough to test...Pcore7 no Draconium loaded without crashing although I didn't start a game, but looks good, the other two versions still crashed, albeit the Pcore7 version seemed to take longer to crash than 06

Hopefully my internet is restored tomorrow and I can test more.

P.S. Internet is back up so I'll process mon the different cores tonight. Do you want to see the logs and if so where or how shall I send them?

Post by **BackTrak** » Mon Oct 20, 2014 9:58 pm

You know, silly me, I thought you had an installation problem... but the game is launching fine, so forget I was here...

ThePhantom032 · Post by **ThePhantom032** » Tue Oct 21, 2014 3:54 am

fin wrote:QUOTE (fin @ Oct 18 2014, 02:06 AM) Hey Phantom,

Lost my high-speed internet, such as it was anyways, had it back briefly tonight, long enough to test...Pcore7 no Draconium loaded without crashing although I didn't start a game, but looks good, the other two versions still crashed, albeit the Pcore7 version seemed to take longer to crash than 06

Hopefully my internet is restored tomorrow and I can test more.

P.S. Internet is back up so I'll process mon the different cores tonight. Do you want to see the logs and if so where or how shall I send them?

No need, yiggz has already been helpful figuring out what file crashes the cores (tafig.mdl, assuming you have the same issue)- I guess Ill be creating a Pcore7b version within the next days with an experimental fix for that. Hopefully its the only thing crashing you guys.

finisher2 · Post by **finisher2** » Tue Oct 21, 2014 4:34 pm

I think I have loaded past the tafigbmp.mdl....I promise to test a few times tonight, got caught up in actually playing the last couple of days I didn't do any testing

Can't wait to get home and some reasonable pings - hooked again

Phantom032 wrote:QUOTE (Phantom032 @ Oct 20 2014, 11:54 PM) No need, yiggz has already been helpful figuring out what file crashes the cores (tafig.mdl, assuming you have the same issue)- I guess Ill be creating a Pcore7b version within the next days with an experimental fix for that. Hopefully its the only thing crashing you guys.

finisher2 · Post by **finisher2** » Wed Oct 22, 2014 1:43 am

So I compared processmons for a 007 and 007nD game. Everything is identical in terms of artwork being read until we get into the ta_ series mdls which aren't in the nD load, I guess they are drac? The last one I read is ta_int.mdl which is after fig and sf have been read...tafigbmp is already done....

Alleg doesn't exit right away but there is an msvcr100.dll read right after which I think is anomalous and might signal the start of the end?

Then I also see a reg query that doesn't occur in the successful launch until much later than the completion of the mdl reads, which is HKLM\HARDWARE\DEVICEMAP\VIDEO\MaxObjectNumber.

Anyways, Alleg stops reading mdls long before they are done and then crashes, perhaps because none of the lobby artwork loads?

Phantom032 wrote:QUOTE (Phantom032 @ Oct 20 2014, 11:54 PM) No need, yiggz has already been helpful figuring out what file crashes the cores (tafig.mdl, assuming you have the same issue)- I guess Ill be creating a Pcore7b version within the next days with an experimental fix for that. Hopefully its the only thing crashing you guys.