![]() |
|
|
#1 | ||
|
Senior Member
Join Date: Dec 2005
Location: Kent, WA
Localization: enGB
Posts: 145
![]() |
Thanks a ton for listening to all of our feedback and for all the hard work and frequent updates!
I just gave 3.8 a whirl and noticed the following: - I still get rapidly repeating messages about settings being saved when I drag the main menu around the screen - Cleaning now works (yay!) - I installed a new mod (ChatFrameExtender) and put a file named nopatch in it's directory. I then updated Cosmos and it cleaned the ChatFrameExtender folder. I guess this means that nopatch files are no longer detected by the patcher? This isn't really a big deal - in fact the new addon manager is easier to work with than having to make nopatch files for every new addon I install - Saw a message in the log that says "Cleaned items have been moved to the trash under 'Cleaned Addons'" but I have no idea where "Cleaned Addons" is - A strange white circle appears on the right-hand side of the addon manager - If I open up the addon manager and then switch to my web browser for a couple of minutes (as I did twice while typing this post), then switch back to the addon manager, it will be frozen and eat up all of my CPU time (good thing I have a dual core system or it would be completely frozen probably) |
||
|
|
|
|
|
#2 | |||
|
Senior Member
|
Quote:
If your using the consildated NoPatch file then if you manually place a nopach file in the addon folder the patcher won't know it. If you place it in the folder before you install the addon using the addon manager it'll pick up the nopatch file and add it to the file. It's best to use the addon manager to install a new addon. You can always turn off the consildated option and use individual nopatch files. The cleaned addon message is partly right depending on the option of removing cleaned addons. The Cleaned AddOns folder is mostly likely still in the Inteface folder if you don't see it in the trash. Opps the circle was just to get a faded red color for the installer window. I was pretty tired and forgot to remove it. Hmm odd I'll look into the frozen problem. |
|||
|
|
|
|
|
#3 | ||||
|
Senior Member
Join Date: Dec 2005
Location: Kent, WA
Localization: enGB
Posts: 145
![]() |
Quote:
![]() Quote:
|
||||
|
|
|
|
|
#4 | ||
|
Senior Member
Join Date: Dec 2005
Location: Kent, WA
Localization: enGB
Posts: 145
![]() |
A couple more issues with the latest patcher:
- I was getting a lot of freezes in the addon manager. It was also causing Windows Explorer to freeze. I rebooted and it seemed to clear up. - The addon manager's protection feature seems to override the configuration menu's setting for cleaning Blizzard addons It might be useful for "protect/unprotect non-Cosmos addons" to exclude Blizzard addons. You might also consider removing the config option to automatically clean Blizzard addons and instead add "protect/unprotect Blizzard addons" buttons to the addon manager. This would keep everything in one place. |
||
|
|
|
|
|
#5 | ||
|
Junior Member
Join Date: May 2005
Localization: enGB
Posts: 9
![]() |
Cosmos Starting up at 6:18 PM on 4/1/2006
An excpetion occured. ErrNum: 0 Message: Stack trace: ComosFunctions.MoveFileWithDirPath%%o<FolderItem>o <FolderItem>s UninstallWindow.UninstallWindow.UninstallCosmosAdd ons%%o<UninstallWindow> UninstallWindow.UninstallWindow.Uninstall%%o<Unins tallWindow> CosmosMain.CosmosMain.uninstallcosmos_Action%%o<Co smosMain> REALbasic._RuntimeRun _Main % main This is what happened when i tried to (i'm so sorry) uninstall Cosmos. I was going to test out some features on a different UI, so decided to wipe it out using the installer. Did not work, gave me an unhandled exception. Hope this helps. |
||
|
|
|
|
|
#6 | ||
|
Junior Member
Join Date: May 2005
Localization: enGB
Posts: 9
![]() |
Cosmos Starting up at 7:38 AM on 4/2/2006
An excpetion occured. ErrNum: 0 Message: Stack trace: UnifiedNoPatch.IsProtected%b%o<UnifiedNoPatch>so<F olderItem> Installer.Installer.InsertFileInList%%o<Installer> &o<Dictionary>s&o<CosmosFile>&o<UnifiedNoPatch>si4 o<AddOnItem> Installer.Installer.BuildDownloadedList%%o<Install er> Installer.Installer.#Open%%o<Installer> Window.Window%%o<Window> Installer.Installer%o<Installer>% CosmosMain.CosmosMain.CosmosDownloadChangedDone%%o <CosmosMain> CosmosRetrieveData.CleanUp%%o<CosmosRetrieveData>b CosmosRetrieveData.ReceiveChangedFiles%%o<CosmosRe trieveData> CosmosRetrieveData.ContinueFetch%%o<CosmosRetrieve Data> CosmosRetrieveData.#DataAvailable%%o<CosmosRetriev eData> REALbasic._RuntimeRun _Main % main This one is much more fun! there was finally a new cosmos update this morning, it downloaded it, then said it was "starting installer" got an unhandled exception, and the ui files weren't actually updated. This also happens (looks identical in the log) when you try to use the "Patch Cosmos" button. AND! also happened the 2nd time i tried to start it up before it even got to the downloading part. (scanning allinoneinventoryKhaos\localization.de.lua . hope this helps at least a little. |
||
|
|
|
|
|
#7 | ||
|
Junior Member
Join Date: Mar 2006
Localization: enGB
Posts: 14
![]() |
I get the same errorog as rosshambo reported
The only solution is to download thezipped files manually! |
||
|
|
|
|
|
#8 | ||
|
Senior Member
Join Date: Dec 2005
Location: Kent, WA
Localization: enGB
Posts: 145
![]() |
Not getting that error, but more info on the freezing:
- To reproduce the freezing, I do this: 1. Open cosmos patcher 2. Open addon manager 3. Sort by Cosmos column 4. Click the checkbox next to one of the Blizzard addons I don't know whether or not I've run WoW between booting the computer and running Cosmos, so it may be a factor as well. It then freezes with 50% CPU, as I have a dual core system. If I kill it with Task Manager (ctrl+alt+del), sometimes Explorer (i.e. the start menu/task bar/folder views, not the web browser)or Firefox will then freeze at 50% CPU as well. I think it may be a dual core compatibility issue, as it seems to be the second core that freezes at full usage, and setting the patcher to only use CPU 0 in the Task Manager affinity settings seems to prevent the freezing. |
||
|
|
|
|
|
#9 | ||
|
Senior Member
|
If thats the case then it may be out of my hands as it sounds like it might be something in the RB framework causing it. I'll investigate and see what I can find.
|
||
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Patcher 3.8 not auto running WOW | xerty | Updater (Patcher) Application Discussion | 11 | 06-21-2006 10:11 PM |
| Patcher 3.8 wasting your hosting traffic | Vangual | Updater (Patcher) Application Discussion | 0 | 04-17-2006 11:23 AM |
| Patcher 3.8 problem | heschlie | Updater (Patcher) Application Discussion | 4 | 04-11-2006 05:34 PM |
| Major Patcher 3.8 Problems | 5n0wman | Updater (Patcher) Application Discussion | 0 | 04-07-2006 07:22 PM |
| One patcher 3.8 problem | Animesing | Updater (Patcher) Application Discussion | 1 | 04-05-2006 02:56 AM |