Problems with the installer on a new machine

Catch-all for all development not having a specific forum.
Post Reply
lexaal
Posts: 2612
Joined: Sun Oct 07, 2007 12:58 pm

Post by lexaal »

I installed
-Chrome
-Firefox
-avast
-acrobat reader
-vlc
and did all proposed updates on a fresh vista2006 home premium windows install.

I followed all instructions by our installer and said yes to everything except the ogg-uncompression (screen1). It included the installation of directX but i think no installation of .net (or an installation without user interation, since i was watching telly during the installation).

(lexaal in newb-mode)
Now I report my first - very bad - impressions:
1) I double-click on allegiance in my desktop.
2) I get an "severe error" warning (according to this). In future I propose to use at maximum a regular warning or just an notification button.
3) so far only one optical error not affecting functionality. Now: OOBE failed.
4) I click on log in, it doesn't work.
Log:
CODEto debug log.
• Starting OOBE
• Unable to write to debug log.
• OOBE Failed.
• Unable to write to debug log.
• Es wurde versucht, einen nicht autorisierten Vorgang auszuführen. --> it was tried to execute an unauthorised task
• Unable to write to debug log.
• Checking for system updates
• Unable to write to debug log.
• Checking for existing processes
• Unable to write to debug log.
• Saving Settings
• Unable to write to debug log.
• Unable to Save Registry Values.
• Unable to write to debug log.
• Es wurde versucht, einen nicht autorisierten Vorgang auszuführen. --> ditto
• Unable to write to debug log.
• Checking connectivity
• Unable to write to debug log.
• Using Port: DirectPlay
• Unable to write to debug log.
• Checking ASGS Client Version
• Unable to write to debug log.
• Client Version: 212
• Unable to write to debug log.
• Server Version: 210
• Unable to write to debug log.
• Securing Installation
• Unable to write to debug log.
• Unable to secure Allegiance installation.
• Unable to write to debug log.
• Der Zugriff auf den Pfad "C:\Program Files\Microsoft Games\Allegiance\Artwork\12968a46-bec8-4e91-b8e9-a25ee7d1208f.lock" wurde verweigert. --> access to path ".." is denied.
• Unable to write to debug log.
5) I click in the headline menu: Help->Help & Support. I receive another severe error messagebox(this time real) Header: xenocode postbuild 2008, Content: The application has encountered an error (0xD0000002), please contact the publicher for more info... Same happens on every button which will send me to an webpage.
6) I click ok and go back to main ASGS and close it. I receive another severe error warning. Header ASGS2.2, content: Unhandled Exception in the application, click on continue to ignore that error and continue the application. If you click on "end" the application is immediatly terminated. It was tried to execute an unautorised transaction. (translated from german.) The message in details: see below.

CODEInformationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.UnauthorizedAccessException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
bei Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str)
bei Microsoft.Win32.RegistryKey.SetValue(String name, Object value, RegistryValueKind valueKind)
bei Microsoft.Win32.RegistryKey.SetValue(String name, Object value)
bei ASGSClient.٭.ٱ(ٴ ٯ, String ֡, String ֭, String Ӱ)
bei ASGSClient.Ӓ.ּ()
bei ASGSClient.Ӓ.ו(Object ֘, CancelEventArgs ֙)
bei System.Windows.Forms.Form.OnClosing(CancelEventArgs e)
bei System.Windows.Forms.Form.WmClose(Message& m)
bei System.Windows.Forms.Form.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Geladene Assemblys **************
mscorlib
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.3603 (GDR.050727-3600).
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll.
----------------------------------------
ASGSClient
Assembly-Version: 2.2.3530.29059.
Win32-Version: 2.2.3530.29059.
CodeBase: file:///C:/Program%20Files/Microsoft%20Games/Allegiance/ASGSClient.exe.
----------------------------------------
Microsoft.VisualBasic
Assembly-Version: 8.0.0.0.
Win32-Version: 8.0.50727.3053 (netfxsp.050727-3000).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.
----------------------------------------
System
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.3053 (netfxsp.050727-3000).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Windows.Forms
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.3053 (netfxsp.050727-3000).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System.Drawing
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.3053 (netfxsp.050727-3000).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
System.Data
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.3053 (netfxsp.050727-3000).
CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll.
----------------------------------------
System.Xml
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.3074 (QFE.050727-3000).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
mscorlib.resources
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.3603 (GDR.050727-3600).
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll.
----------------------------------------
System.Management
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.3053 (netfxsp.050727-3000).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll.
----------------------------------------
System.Web.Services
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.3053 (netfxsp.050727-3000).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll.
----------------------------------------
System.Configuration
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.3053 (netfxsp.050727-3000).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
----------------------------------------
n1cbkdyw
Assembly-Version: 2.2.3530.29059.
Win32-Version: 2.0.50727.3053 (netfxsp.050727-3000).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Windows.Forms.resources
Assembly-Version: 2.0.0.0.
Win32-Version: 2.0.50727.3053 (netfxsp.050727-3000).
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.



Short version: I am damn pissed an have go the painfully way of first launching it with correct adming rights + compatibility mode, then uninstall/install, then checking .Net, then contacting tech support.

I will be able to play because i have technical skill and knowledge about getting allegiance to run and bring enough willpower. But damn... will a random newbie do the same?



Edit #1:
with correct admin right + compatibility to Windows Server 2003 SP1, visual themes and desktop composition deactivated I can join the lobby but no connection to a game yet.
Last edited by lexaal on Sat Jul 21, 2012 6:34 pm, edited 1 time in total.
I have a johnson photo in my profile since 2010.
pkk
Posts: 5417
Joined: Tue Jul 01, 2003 7:00 am
Location: Germany, Munich

Post by pkk »

lexaal wrote:QUOTE (lexaal @ Jul 21 2012, 08:21 PM) I installed
-avast
lexaal wrote:QUOTE (lexaal @ Jul 21 2012, 08:21 PM) Edit #1:
with correct admin right + compatibility to Windows Server 2003 SP1, visual themes and desktop composition deactivated I can join the lobby but no connection to a game yet.
Do you use Avast's Network Shield? If you do, uninstall it.
The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.
lexaal
Posts: 2612
Joined: Sun Oct 07, 2007 12:58 pm

Post by lexaal »

I posted this very intentionally on the dev-zone.

For me it's easy to fix (not easy-easy but 20-minutes-easy). From the eyes of a newbie it is very very bad.


Especially compatibility mode is extremely critical
-it makes logging in impossible
-it denies you even the link to help/support.
-every second button and even closing the program results in unhandled exceptions.

--> with XPSP3 all our newbies are IT-engineers and admins with enough skills to fix that problem.

We need an instant-fix like shipping a real big FAQ and in my opinion we should either early release ACSS altough not everything is fixed or we need to touch and fix ASGS again.
I have a johnson photo in my profile since 2010.
pkk
Posts: 5417
Joined: Tue Jul 01, 2003 7:00 am
Location: Germany, Munich

Post by pkk »

There are two problems:
ASGS
Some systems need compatibility mode, some don't. ACSS doesn't have that problem and is the solution we've already chosen.Allegiance DirectPlay
Most 3rd party firewalls block ports of DirectPlay. The only solution I see is getting rid of DirectPlay. It's exactly the same problem like the freelancer community has.
The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.
lexaal
Posts: 2612
Joined: Sun Oct 07, 2007 12:58 pm

Post by lexaal »

~fixed
I have a johnson photo in my profile since 2010.
Post Reply