Patcher v3.5 hangs on setup screen

[Legorol]

Thanks for your reports, the author now knows about this bug. Setup wasn't supposed to be active, it's a work in progress feature. This bug will be fixed asap. In the meantime, you can manually download one of the distribution Zips, or try the following workaround:

Quick work around:
1) When the setup wizard opens - hit alt-f4
--- steps 2,3 are for first time at the setup screen ---
2) Select your World of Warcraft directory
3?) you may have to enter your WoW directory again

You can update cosmos through this patcher program once succefully past the setup screen.

[dormlock]

Ver 3.6 is on it's way to Karl as I type this. Setup has been disabled and a few other items have been fixed mostly cosmetic but some bugs as well. another version will probably follow later this week with some other changes that Karl suggested and maybe the setup wizard will be actually done as well.

[R-GO]

I tried this and i got an error that said "There was an unhandled exception."

System Information
Windows XP Media Center 2005
AMD X2 3200+
2GB DDR PC3200 Ram
Radion X1900XT

All drivers and windows updates have been installed.

[HunterZ]

I also noticed:
- the setup window appears every time (after closing it with alt+f4, then exiting, then relaunching the patcher)
- moving the window around results in constant "preferences saved" messages
- I can't pick a distribution until after I "install" Cosmos
- After installing, trying to update to the latest Alpha reported no changes; does this mean it installs the alpha by default?
- Complete File Check button on config menu seems non-functional
- If Cosmos distribution hasn't changed, cleaning does not occur and no changelog is shown
- Unhandled exception errors in several situations (sorry, didn't document them)

What would be nice:
- Addon manager should scan for nopatch files and use them to configure default protection settings, especially since it seems to respect nopatch protection
- Option in addon manager to manually initiate cleaning of non-protected addons

[dormlock]

I also noticed:
- the setup window appears every time (after closing it with alt+f4, then exiting, then relaunching the patcher)
- moving the window around results in constant "preferences saved" messages
- I can't pick a distribution until after I "install" Cosmos
- After installing, trying to update to the latest Alpha reported no changes; does this mean it installs the alpha by default?
- Complete File Check button on config menu seems non-functional
- If Cosmos distribution hasn't changed, cleaning does not occur and no changelog is shown
- Unhandled exception errors in several situations (sorry, didn't document them)

What would be nice:
- Addon manager should scan for nopatch files and use them to configure default protection settings, especially since it seems to respect nopatch protection
- Option in addon manager to manually initiate cleaning of non-protected addons


Problems noted and I'll see about getting it all fixed and rolled out by thursday evening. The non selection of a distribution is because the code that did it was removed because the setup was supposed to take care of it I guess I should finish the setup wizard with the next release. The default should be the release version for the distribution.
The addon manager does scan for nopatch files or rather the class that handles file protection will tell the addon manager if there is a nopatch file depending on option set for the merged nopatch file.
Feature requests are always welcomed and most if they make sense are added.

A lot of the problems have been cause because a lot of the core code dealing with updating and downloading was rewritten and I didn't give all the options a through testing spent most of the time making sure that the download path and install window and addon manager worked with their new code. The rest shouldn't have really broken but my bad for not testing it closer.

Next version shall be tested from a first run with non existant install.

I'd also like to apoligize for the inconvenience.

[kindo]

Thank you for your quick response.

AltF4 did the trick for me. I also got an unhandled exception message in the main window but was still able to install Cosmos.

Thanks for the great product and the dedication to supporting it. I for one, really appreciate it.

-Kindo
55 Dwarf Hunter
windrunner

[jgleigh]

Nopatch files:

I did notice something else strange about 3.5 release. In the 3.0.x release, all the entries would be

Interface\AddOns\<addon>;

but in 3.5 they would be

<addon>;

[HunterZ]

Thanks Dormlock! Looking forward to the updated release.

Also, about the nopatch thing: the patcher does recognize the nopatch files, but the addon manager doesn't list the affected mods as protected, even though they effectively are.

[larveyza]

- Just want to acknowledge that the problem exists. I gave up at 5am GMT+1 time zone. Im now at work and was looking for a fix. Ill try this when I get home. But since i understand the dev world, Here is some more info on the prob:
- Im running winxp sp2, home ed. With McAfee running. I disabled Virus Scan and Firewall to accomodate. After unzipping file, launch cosmos***** file. Both windows open. I am unable to perform anyaction and have to close program via taskmgr. The Distro pane and Cosmos Install pane. they both just sit there. all buttons are gray'd out on the distropane, and the install pane will not move forward when trying to select next or cancel. When i kill the processes, I get the errmsg "an unhandled exception message". Then another install win opens up. I also got the hour glass when first opened, as though it was running, so i left program to run overnight, came back and it was still in that state. Logged into Wow and add'ons arent updated/avail.
- Again, Im now at work and havent tried the Alt F4. So I will try this when I get home. Can you link this FAQ Forum near the Patch Downloader page, had to search for this and it wasnt easy. Thank you for your support, Cosmos is a GREAT Tool!. 8)

[Magritte]

This problem is also present in the Mac Updater. (I don't know the version; it's the newest one on the downloads page, dated March 28.) However, the alt-F4 workaround doesn't work and I have to force quit out of it.

[tortcat]

well the patcher right now is totally non usuable.....

you cannot get any of the patcher buttons to "light up"...and you get stuck in some kind of a loop where the setup window keeps coming up.....alt f4 only closes it...but the patch comos/uninstall cosmos etc etc etc are all greyed out.

Ive downloaded it twice but it just wont work

[SithPredator]

Same issue here. Approximately how long before it's resolved?

[dormlock]

Setup problem has been resolved and 3.7 is on it's way to you guys.

[Spek]

was wondering if the new release is on the way to everyone or you are trying it out with a few people...same problem here as the rest.

Thanks

[Greysyn]

I'm still getting an unhandled exception error. However, the setup screen doesn't appear and when I click "ok" to the error, I can then navigate around in version 3.7.

I was about to give it a try when I noticed that the drop down for the distribution version is empty. I want to make sure I keep the Alpha version that I always use and not the release version.

[Quishy]

with the patcher the <WowPath></WoWPath> is getting set to either encoded information or useless info... I would suspect that info to be a simple path (/hd/application/world of warcraft/) vice a string looking like : APHRcwEAAgAAAAFSAAAAAAFSAAIAAQV2dE1hYwAAAAAA... goes on and on.

Patcher runs the request to reset this path if edited by hand twice (as initial set up).

Path not getting handled correctly ?

[dormlock]

The path is indeed encoded. If you edit it by hand it'll not reconvert properly. It's encoded to make it some what portable at least according to the realbasic documentation thats what it makes it seem like.

There is really no need to edit it anyways since you can set it from the configure->wow settings.

[HunterZ]

3.7 seems a lot more stable. I only noticed one issue that I may have forgotten to report before:
- Patcher doesn't clean Blizzard addons on update even though I have it set to (and they aren't flagged as protected either)

[dormlock]

Ok i'll look into it I'll have to copy a blizzard addon over to the test folder i play with.