ive been asked by a few people about how to update only map/poi files. They use mods of the eq2map and want to be able to update.

Best way to do this is to add an extra checkbox that says check map files or just change that one to check only poi's AND map files

could you please explain this further, any mods for eq2map should work properly with eq2map using the updater.

ok i was under the impression that it would overwrite their xml files. Guess not:)

it shouldn't if it is i need to know what files they are using that it is overwriting that it shouldnt be.

k ill have em try and see if their files get overwritten. later today :) i gotta go to work now hehe

My crash
 

As I stated before, on my computer, the eq2map updater crashes since version 0.95e (b or c did work). Perhaps I can give some more clues on what is going on now.

I just downloaded the most recent version and started it. It asked for confirmation of my EQ2 main directory, which it guessed correctly, tried to access drive A: (my floppy drive, whyever) and then crashed. I attached my Visual Studio .NET 2003 Debugger and this is what I got (w/o having the sources):

Eine nicht behandelte Ausnahme des Typs 'System.InvalidOperationException' ist in system.dll aufgetreten.
Zusätzliche Informationen: Die Anforderung kann nicht ausgeführt werden, da der Prozessleistungsindikator deaktiviert ist.

(I can try to translate that to english, if needed, but I guess the most important things are written more or less clearly.)

The stack trace shows:

> system.dll!System.Diagnostics.NtProcessManager.GetProcessInfos(System.Diagnostic s.PerformanceCounterLib library) + 0x1a5 Bytes
system.dll!System.Diagnostics.NtProcessManager.GetProcessInfos(string machineName, bool isRemoteMachine) + 0xa4 Bytes
system.dll!System.Diagnostics.ProcessManager.GetProcessInfos(string machineName) + 0x29 Bytes
system.dll!System.Diagnostics.Process.EnsureState(System.Diagnostics.Process.Sta te state) + 0x116 Bytes
system.dll!System.Diagnostics.Process.get_ProcessName() + 0x11 Bytes
EQ2MAP_Updater.exe!WindowsApplication7.Form1.Form1_Load(System.Object sender = {WindowsApplication7.Form1}, System.EventArgs e = {System.EventArgs}) + 0x8e Bytes
system.windows.forms.dll!System.Windows.Forms.Form.OnLoad(System.EventArgs e) + 0x117 Bytes
system.windows.forms.dll!System.Windows.Forms.Form.SetVisibleCore(bool value) + 0xaa Bytes
system.windows.forms.dll!System.Windows.Forms.Control.set_Visible(bool value) + 0xe Bytes
system.windows.forms.dll!ThreadContext.RunMessageLoopInner(int reason, System.Windows.Forms.ApplicationContext context) + 0xc2 Bytes
system.windows.forms.dll!ThreadContext.RunMessageLoop(int reason, System.Windows.Forms.ApplicationContext context) + 0x45 Bytes
system.windows.forms.dll!System.Windows.Forms.Application.Run(System.Windows.For ms.Form mainForm) + 0x34 Bytes
EQ2MAP_Updater.exe!WindowsApplication7.Form1.Main() + 0x21 Bytes

Maybe this gives you any clue on what might be going on. If not, feel free to contact me or ask for more help - I would really like using the eq2map updater :-)

Best regards and thanks for your work,
Laenny

I am also experiencing crashes from the later versions of the EQ2Map Updater. I attached a .NET debugger to it, and recieved this information:

This seems to be related to checking if either EQ2 or maybe the updater is running more than one instance (can't be sure since I don't have the source).

I would guess that either the exception would have to be handled or a different way of enumerating running processes without the Process class would fix this.

i will release a new version today and *try* to attempt to fix this error. however i am not what you would call an experienced programmer (this is the first useful program i have ever written and i am self taught in vb .net) so you will have to bear with me, i promise i am doing my best!

New version of the updater released (0.97)

I for one would like to say that your best is just incredible it has made using the most current maps more accessible to me.


so Thank you :nana:

The crashing bug is fixed :-) on my system. Thank you very much.

My last suggestion is add System.Windows.Forms.Application.DoEvents() in the loop for the updating operation. This will allow people to tab out to other windows and do other things while they wait for the update to finish, this is especially useful when people are doing the firsttime download and it takes awhile :-)

Thanks again.

I'm glad to hear the crashing bug was fixed for you!
application.DoEvents() is already called every time the progress % changes (so that the progress bar shows the correct percentage)....

That's strange then, because if you try to do events like drag the updater window while its updating, it doesn't happen until the entire update is complete.

Regardless, great work, I'm sure this will only continue to get better with time.

are you sure you cant move it while it is downloading updates? i just tried moving it/alt tabbing and it worked fine?

I can't reproduce this now. Must have been something screwy at the time. Please disregard :-)

im just glad its working for you now :)

Hi there!

The latest release also fixes my problem too :-)

Thanks a lot!

Great! Thanks for letting us know!

thxs for this tool its great. I just installed it and works ok but was wondering if im supposed to see my location on my map? when i open my map i have no arrow showing my location, did i do something wrong or is this normal?

No, that means something is wrong. Did you use the auto-updater or the zip file?

Quib

the newest updater

Quib, it seems we need to post the icons.dds file in the downloads section so people can fix this problem quickly. This makes more than a few. We also need to add into the download description of the updater and the zip, that if you install another UI other than this, DO NOT overwrite any files already in the dir.

i will add an option on the updater to "redownload all default" files for when this happens (to make the updater download the files that it normally only checks to see if it exists)

Anyway way to have the Updater have the ability to check for new versions of the Updater and update itself? :)

The theory was suggested and thought about, but do you really want an .exe updating itself? I doubt many people do, but if you dont mind, thanks for your trust :). But this is why the updater tells you the most up to date version, so that you will at least know when theres an update.