PDA

View Full Version : Cosmos 3.0.2 downgrading

taltamir
03-10-2006, 02:37 AM
I got cosmos patcher 3.0.2, I set it up and ran it, it told me there is a new cosmos***** file and wanted to update itself but instead of updating it downgraded to 1.0.0.1 (according to the version tab in the file properties)

The worst of it, the cosmos 3.0.2 deleted all the nopatch files (creating a master list), and then the v 1.0.0.1 deleted all my other extensions because they no longer had their nopatch file.
Kirkburn
03-10-2006, 06:10 PM
Yeah it's not a proper release so it'll do that for a while. Just untick 'cosmos*****' each time you use it to update for now.
taltamir
03-11-2006, 02:16 AM
Yeah it's not a proper release so it'll do that for a while. Just untick 'cosmos*****' each time you use it to update for now.

mmm, perhaps disabling the self update in a non proper release then? or giving a warning that it will do that on the website or the installation instructions?
PleegWat
03-12-2006, 10:06 AM
Or just run the 3.0 patcher from a different directory. Works from this one since it lets you configure the directory while the old patcher assumed it was in the wow root.
taltamir
03-14-2006, 08:06 PM
Or just run the 3.0 patcher from a different directory. Works from this one since it lets you configure the directory while the old patcher assumed it was in the wow root.

there are ENOUGH workarounds, my point is that there is no way to KNOW its gonna do that until it happens... there should be a warning somewhere or it should be disabled so that it doesn't do it. I already know about it now...
Daeanor
03-15-2006, 01:22 PM
I have to agree that providing a workaround doesn't really address the issue. Yes, we know it's not an official release. But it has gotten at least one update since it became available, and yet it cannot patch itself without reverting to version 2. How hard really would it be to make an exception in it's own case not to revert the patcher itself, or to draw upon a different file list for those using the new patcher? The only difference is the patcher executable.
dormlock
03-16-2006, 05:06 PM
The biggest problem is that Thott has yet to update the patch information with the latest info for the patcher. The updater is offical as far as Cosmos goes and Thott did provide me with the necessary information to complete the upload process so he approves of it. Thott has just been to busy to update the update server scripts to send correct info for the updater for both platforms.

Long term fix will be an Option to disable the autoupdate that will be on by default. When Thott has time to update the info you'll be able to reenable it own your own.
taltamir
03-16-2006, 07:34 PM
just an FYI... I tried putting the cosmos***** file on my desktop and it STILL replaces itself with the older cosmos*****

So that workaround doesn't work, the old cosmos has to be in the root directory for wow, the new one doesn't, but automatically replaces itself with any cosmos***** file it downloads...

also, I tried disabling the master nopatch list, and that didn't make it use the old nopatch system... in fact, either way it insists on deleting all my old extra extensions (all have a nopatch file in their root)...