Errors when installing DAzips through DAUpdater

[DarkeWolf]

hrm.

Well, I do know that simply changing the username doesn't affect the folder structure. All it does, is instead of showing say... Compaq_User, it would show JohnSmith. But the folder structures would still be for Compaq_User :(

Setting up a new user account is actually pretty simple, IF you have access to the account that has admin privileges. http://answers.microsoft.com/en-us/windows/forum/windows_7-security/how-to-change-user-name-in-windows-7-professional/d95ddaa7-4235-454e-83d6-77232207c7e2

 

Otherwise, what I think that you are going to have to do, is set it up so that your mods and whatnot go into a folder that is NOT in Documents, or any of the folders which are listed in the username directories. You can actually install to the installation directory of the game itself, tho that's not recommended. So something like C:/program files/Bioware/Dragon Age/packages/core

/addins

/override

 

And then use a mod manager like DAM or DAMM which can be set to use different directories than the default. Which, AFAIK, the updater.exe does NOT allow you to do :(

 

DAM- http://www.dragonagenexus.com/downloads/file.php?id=286

DAMM- http://www.dragonagenexus.com/downloads/file.php?id=277

 

Now, both of these can be set to use custom directories, and both do the same thing. The biggest difference is in the file types that they can handle.

 

 

I will also note that if you've got that problem with the account username, you're also not going to be able to take screenshots :(

So if at all possible, I'd recommend creating a new account to install the stuff to. If that's a possibility ;)

[markusDAO]

Oh, you mean my Bioware/EA account? Oh THAT'S fine. All one word at googlemail. That's all good.

 

I'll have a tinker with it tomorrow, see what I can get working.

[DarkeWolf]

Markus- nope, I was talking about in game screenshots. I know that a lot of people have not been able to take screenshots of stuff going on in the game, if the Username that they are logged in on, on the computer has a non alphanumerical character in it.

Once it gets to the non alphanumerical character, the game can't follow the folder pathway, so it just stops trying; and doesn't take the screenshot.

[markusDAO]

I tried installing DAModder. And unfortunately I get the same error at the same line there, too.

 

"Invalid character in the given encoding. Line 30, position 47"

 

I have no idea which file this is referring to, or how I would fix the error. But clearly it's that which is preventing Mods from being installed on my machine.

 

So far, however, it doesn't appear to be effecting the game itself.

 

Does anybody have a clue what is going on here?

[markusDAO]

I tried installing the extra Dog slot mod, with DAModder. And this at least gave me some kind of debug code details.

 

I have no idea if this will help narrow down the problem in any way, but they are as follows:

 

 

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

 

  Reveal hidden contents

 

************** Exception Text **************

System.Xml.XmlException: Invalid character in the given encoding. Line 30, position 47.

at System.Xml.XmlTextReaderImpl.Throw(Exception e)

at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)

at System.Xml.XmlTextReaderImpl.Throw(Int32 pos, String res)

at System.Xml.XmlTextReaderImpl.InvalidCharRecovery(Int32& bytesCount, Int32& charsCount)

at System.Xml.XmlTextReaderImpl.GetChars(Int32 maxCharsCount)

at System.Xml.XmlTextReaderImpl.ReadData()

at System.Xml.XmlTextReaderImpl.ParseCDataOrComment(XmlNodeType type, Int32& outStartPos, Int32& outEndPos)

at System.Xml.XmlTextReaderImpl.ParseCDataOrComment(XmlNodeType type)

at System.Xml.XmlTextReaderImpl.ParseElementContent()

at System.Xml.XmlTextReaderImpl.Read()

at System.Xml.XmlTextReader.Read()

at DAModder.DAXMLParser.ReadModDetails(String sFilePath, DAModDetails details)

at DAModder.DAModDetails.Load()

at DAModder.DAModDetails.Load(String sModUID)

at DAModder.Form1.prepareModForInstall(String sMod)

at DAModder.Form1.buttonInstall_Click(Object sender, EventArgs e)

at System.Windows.Forms.Control.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ButtonBase.WndProc(Message& m)

at System.Windows.Forms.Button.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.3620 (GDR.050727-3600)

CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

DAModder

Assembly Version: 0.2.1.2

Win32 Version: 0.2.1.2

CodeBase: file:///C:/Documents%20and%20Settings/Compaq_Owner/My%20Documents/DAModder/DAModder.exe

----------------------------------------

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

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.3614 (GDR.050727-3600)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.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.Xml

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.3082 (QFE.050727-3000)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

ICSharpCode.SharpZipLib

Assembly Version: 0.85.5.452

Win32 Version: 0.85.5.452

CodeBase: file:///C:/Documents%20and%20Settings/Compaq_Owner/My%20Documents/DAModder/ICSharpCode.SharpZipLib.DLL

----------------------------------------

System.Core

Assembly Version: 3.5.0.0

Win32 Version: 3.5.30729.1 built by: SP

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll

----------------------------------------

Microsoft.mshtml

Assembly Version: 7.0.3300.0

Win32 Version: 7.0.3300.0

CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

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

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

 

 

[Thandal]

Do you have the most recent version of the .NET framework installed? (I know DAMM requires at least v3.0.)