Launcher problems..

**DUFFMAN** · August 17, 2010, 06:55 AM

Hello,

After PM'ing Paedric about this, I figured, maybe this is of such importance that everyone should know about it. So here goes:

I've been having some issues with the launcher after I've switched my OS from Ubuntu Linux to Windows XP. See below for a screenshot:

Spoiler Alert, click show to read:

Now, I have opened the Roma Surrectum II.au3 file in notepad to view the script for the .exe, and it turns out there is no line 2977.. the script ends at line 970 or so. I have deleted the folder and added it through SVN 2 times and the same error keeps popping up. Can anyone explain to me what is happening here, and most of all, how to solve it?

**Hellhound1** · August 17, 2010, 07:24 AM

This probably isnt much help, but i've heard of issues with GNU GRUB messing up windows installations when linux is removed..

And after googling around a bit, it seems people have similar issues because of the GUI being enabled.

take a look: http://www.autoitscript.com/forum/in...howtopic=46141

**DUFFMAN** · August 17, 2010, 07:33 AM

Yea I had seen that thread on those forums when I googled around myself

I take it the solution would be to download that AutoIt software and edit the script? Will need to do some researching for that.

But I don't understand how GRUB could mess up my windows, because I have completely erased my hard disc before installing XP, and I also believe the MBR was reset. And with GUI being enabled, do you mean the GRUB screen that let's you choose OS? I don't see that screen so I take it it doesn't exist on my install.

**Hellhound1** · August 17, 2010, 07:50 AM

cool, right first thing would be wipe your harddrive clean again, then install XP, you dont want any trace of linux on there, because GRUB might still be installed and messing something up?

The GUI Disabled thing is for AutoIt and i've browsed through the code and it seems it is disabled.
However, the undeclared variable could refer to other code thats been included somewhere, namely:

Code:

#include <GUIConstantsEx.au3>
#include <ButtonConstants.au3>
#Include <WinAPI.au3>
#include <StaticConstants.au3>
#include <Sound.au3>

Also, it would be a good idea to get AutoIt, and then compile the script yourself and see if that helps?

**DUFFMAN** · August 17, 2010, 08:02 AM

As you can probably understand I don't like to install my OS all over again, especially since I don't feel that will solve anything.

I've been searching for those other scripts mentioned, but I can't seem to find them on my hard disc...

Im gonna download AutoIt and play around with it for a bit, see if I can fix this thing myself.

**Paedric** · August 17, 2010, 03:54 PM

Before doing anything rash, i'd make sure xp is up to date, service pack and al. The exe need a recent version of microsoft.net library and other libraries.

**dvk901** · August 17, 2010, 04:13 PM

I personally think it's impossible for a previous OS to have any effect on the Launcher. I don't care what has been read. It is far MORE likely that your version of XP is missing a .DLL that the Launcher needs to run properly. I know the Launcher on my machine has never worked exactly 'right'. It launches OK, but all the buttons have no text. I'm in the process of trying to fix all that, but in short, I think it's more likely you present OS is causing the issue.

**Pat89** · August 17, 2010, 04:37 PM

Yes, AutoIt does have some issues like paedric pointed out. But it's a relatively complete package (you don't have to install a basic package like with java in order to get it to work), it has a very large help file, from which I learned everything I know about AutoIt and - very important - it's free.
With the "#Include" bits, you add pre-programmed parts of code to the script, which are far more advanced than I understand. Since the issue is at such a far down line in the script, it is likely that this issue can't be solved by a normal user (like hard-coded in RTW) as it will be part of these inported script. The only solution is to make sure your windows is up to date. (yes, that's bad news for people who stick at certain service packs for various reasons).

But for the most users - who get their windows updated automatically - there won't be a problem.

One thing, the script has at the top a line "Opt(MustDeclareVars)" or something like that. You could try to remove that, so the variables don't have to be declared, which might make the bug message disappear. Maybe the launcher will work at least enough for you to launch the game if you try that. but it can also very well be that it doesn't work anyway

(But like I said, that's all far more advanced than I understand, as I only learned to use the script via a help file)

Edit: Btw, I added the RS II symbol as icon for the .exe, it appears it doesn't work for you... Didn't it got added again after recompiling?

**DUFFMAN** · August 17, 2010, 04:54 PM

Thanks for all the answers guys.

I've switched to my Win7 pc, and I am about to install the beta on this one again, expecting that it will work. It is indeed probably caused by my OS, because I have had XP for a long time and I've been playing around with it a lot, so I have probably broken something.

@ PatricianS; deleting that one line will probably not solve the issue, and here's why: A few posts earlier I said I was gonna download AutoIt and try to figure this out, and when I got to playing around with the au3 and the exe I at some point received an error message that didn't say anything about variables not being declared, but it said something else, which I can't remember. That's when I gave up and decided to move to my win7.

Again, I have now switched to Win7, expecting that it will work without a problem. And next to that I would like to say that if anyone else is having this issue (or is going to have this issue when the mod is released), you can also use the batch files to start the mod, because they also allow you to pick a faction. Only downside to that is that you can't change vegetation and bloom like you can in the launcher.

Thanks again