Caroc
04-15-2006, 07:31 PM
As was mentioned in my multiple monitors thread, I recently lost all my wow addons and saved settings to a bad block on my hdd, so I decided to start fresh. I deleted my interface folder and WTF folders. Downloaded the latest patched from the website - v3.8(0) r3418 - and proceeded to rebuild my wow mod library. In case it isn't apparent, I am running Windows XP completely patched.
Couple issues explained below
First, when I attempted to disable "AllInOneInventory" the addon asked if I wanted to disable any dependencies and I said Yes. I then got an unexpected handling error as was mentioned in other peoples postings. So far, of all the addons I disable and choose to disable other dependencies, it was the only one which gave the error. I was able to disable it fine though as long as I manually disabled the other dependencies separately.
Second, any mods I disable are properly moved into the disabledaddons folder. However, when I tell cosmos to run the patcher update, it redownloads those and puts them back into my addons folder. I then have multiple copies of the same addons in my addons folder and disabledaddons folder which creates multiple addons listing entries in the patcher program.
Third, if I attempt to re-disable the new downloaded ones, the patcher creates a new disableddisabledaddons folder for the old one. This will continue forever creating longer and longer folder names everytime I run the patcher and re-disable the addons I dont want.
As a result of the above errors, I have stopped updating my cosmos distribution through the patcher until they are addressed. I guess its back to manual updating so I don't have to spend 15 minutes before I log into WoW to configure my addons folder.
P.S. The nopatch.nopatch is working fine for me... however, I needed to copy my third party mods (like titan panel) into the folder after the patcher ran the first time and then go into the manageaddons option to "protect" them so that the patcher wouldn't delete them. The first time I attempted to do this, it removed my other addons, but I think I have them adequately protected now (btw, all third party mods have a nopatch file in their respective folder which I thought was suppose to stop the patcher from cleaning them).
Couple issues explained below
First, when I attempted to disable "AllInOneInventory" the addon asked if I wanted to disable any dependencies and I said Yes. I then got an unexpected handling error as was mentioned in other peoples postings. So far, of all the addons I disable and choose to disable other dependencies, it was the only one which gave the error. I was able to disable it fine though as long as I manually disabled the other dependencies separately.
Second, any mods I disable are properly moved into the disabledaddons folder. However, when I tell cosmos to run the patcher update, it redownloads those and puts them back into my addons folder. I then have multiple copies of the same addons in my addons folder and disabledaddons folder which creates multiple addons listing entries in the patcher program.
Third, if I attempt to re-disable the new downloaded ones, the patcher creates a new disableddisabledaddons folder for the old one. This will continue forever creating longer and longer folder names everytime I run the patcher and re-disable the addons I dont want.
As a result of the above errors, I have stopped updating my cosmos distribution through the patcher until they are addressed. I guess its back to manual updating so I don't have to spend 15 minutes before I log into WoW to configure my addons folder.
P.S. The nopatch.nopatch is working fine for me... however, I needed to copy my third party mods (like titan panel) into the folder after the patcher ran the first time and then go into the manageaddons option to "protect" them so that the patcher wouldn't delete them. The first time I attempted to do this, it removed my other addons, but I think I have them adequately protected now (btw, all third party mods have a nopatch file in their respective folder which I thought was suppose to stop the patcher from cleaning them).