• 0

    posted a message on ItemDataCache
    I did do an update that includes a lot of the new quest rewards, it added just under 1000 items. I also extracted a list of over 39k items but I am not sure I just want to willy nilly add them in to bulk up the db, for now I would prefer to keep it to useful/seen items. In fact I made a list of some items to delete in a future update.


    So data files please :)
    Posted in: General AddOns
  • 0

    posted a message on Recommending you run an application as Adminstrator.
    Quote from Allara


    I have not checked for sure, but I don't think you can just modify an ACL to a Program Files location to allow a standard user to write to that location, as long as UAC is turned on. You have to turn off UAC. If I'm wrong about this, and you can override this UAC behavior by modifying an ACL and leaving UAC on, you are absolutely breaking what Microsoft intends to do in Vista. This should never be in an installer.


    FYI, you can do this, this is what I did at first before I had read enough to see what the virtulazation was doing in the first few hours I had a vista laptop to mess with. The only real issue with virulazation is people just see the empty addons folder, a simple junction link here fixes that quickly and easily as well.




    Basically what it comes down to is this: WoW needed a pretty big redesign in several key areas in order to conform to Windows Vista best practices. They chose to basically do the cheap way out, the way that was least backwards incompatible for their users, and probably the way that made the most sense to them from a cross-platform standpoint, which was to just pull the entire folder out into a public one. This means there is no longer the issue of separate virtualization per user, their custom patcher works, and users can manually drop in add-ons like they're used to.


    and all they would need to do is set up the proper read permissions after a patch/install to at least AVOID WoW from needing to run as admin, the installer/patcher sure, but at least wow on a day to day basis would not need to be run as admin with an out of the box install.
    This takes zero redisgn and a not much code. It is a days work tops. They would more then save it in reduced tech support costs.


    You'd have to turn off UAC to do any of that within Program Files. UAC is intrinsically involved here; this is why it gets brought up.

    not in my experience, all this is just default access rights, nothing from UAC here. UAC only has to do with writing files from a user account without access... writing, not running/reading the program.
    That is handled by the virulazation, and a simple link would make it work better, but has nothing to do with the bliz saying you need to run as root.


    To get wow to work on the account I wanted to quckly, once I figured out their error message was bogus, all I did as a quick fix was chown the files, now works grand.
    Posted in: General Chat
  • 0

    posted a message on Recommending you run an application as Adminstrator.
    I still see nothing in that that says the UAC means you should force a user to run a program as admin.. can you please give me a even more specific link, I am just missing it I guess.

    And moving it out of the programs files DID NOT solve the issue... I have it installed on its own W: partition and the installer failed to update to something running without using 'run as admin' out of the box. Changing the owner and default permissions fixes this.

    I still can not see what UAC has to do with it what an installer that installs something that you do not need be be admin to run has to do with UAC. I also see nothing in the UAC that says anything about setting default permissions on files 'I' install being against it. UAC has NOTHING to do with normal users, it has to do with the split admin account tokens and escalations of rights while running under an admin log in.

    I can find nothing in either link that says otherwise. You do not have to turn off UAC to allow those writes, they also just work due to the virtualazation as it out of the box.

    You tell me thousands of windows programs have this issue, but I sure as heck know I am not running other programs as admin, granted windows is not my main boxes OS, but I still find this hard to believe, that UAC requires this and this is the accepted solution.
    The issue can be fixed by the installer , all it needs to do is make sure all the files are readable by the accounts that should be allowed to run it. UAC has nothing to do with this.
    Posted in: General Chat
  • 0

    posted a message on ItemDataCache
    yes, it is for now... it will have a lot more soon, and it is self learning.
    Posted in: General AddOns
  • 0

    posted a message on Recommending you run an application as Adminstrator.
    Oh I agree if I want to disable UAC I should be able to, or whatever else. To be honest I am not sure at all why people even mention UAC as part of this, it has nothing to do with it as far as I can tell. And in either case Blizzard should not be telling people to turn it off to run wow either, or to run wow as an Administrator.
    Posted in: General Chat
  • 0

    posted a message on ItemPrice-1.1 (official thread)
    yes, the armory does not show items till they are 'discovered' what the delay is for this to then update I don't know though... and the armory data is bad since they updated it for Woltk on the 13th in many areas.. so I don't really trust it right now anyway. Can you share your code to read the wdb files?
    Posted in: Libraries
  • 0

    posted a message on Recommending you run an application as Adminstrator.
    Quote from flarecde
    That is definately a problem. If their installer can't assign proper permissions to a file, it's broken. If that's why they are telling people to run as administrator then that's just wrong.


    hmm.. the cynic in me just came up with that they want to have their warden program run as admin as the real reason they don't fix this.
    Posted in: General Chat
  • 0

    posted a message on Recommending you run an application as Adminstrator.
    Quote from flarecde
    What I understand of UAC, and correct me if I'm wrong, but basically the (effective) permissions of Program Files should be:

    Users - Read
    Administrator - Read + Write

    With UAC prompting and/or denying on a User trying to write into that directory. UAC is supposed to allow the user to write in protected areas (behave like an admin), but only after confirmation so there's a degree of protection without crippling the basic user account.


    UAC is what comes up and says this program wants to do XXX, allow / deny for
    when you need to elevate your privileges to do something. Near as I can tell it has nothing to do with reading and writing regular files in the OS. Now MS did set up more restrictive defaults on the inherited default acls with Vista and I think some are confusing this with UAC.
    Posted in: General Chat
  • 0

    posted a message on how to update directly from wowace.com?
    hmm.. I still think there should be a wip category, which would be do not touch unless you are coding, but then that is probably because I am one of those that works on different machines and would like to have place out of the net to start the files when it is time to go to eat etc and I will likely be in a different place when I pick work back up again.
    Posted in: Updaters
  • 0

    posted a message on ItemDataCache
    http://wow.curse.com/downloads/wow-addons/details/item-data-cache.aspx

    A couple of months back I wrote a program to update the price information using the armory as a source. A week or so I got access to be able to update the program at curse. I would like to start to add in Wotlk items now. I need help for this.

    Please upload your local Cache files so I can merge them into the main file.

    http://data.warcraft.org.ru/ItemDataCache/
    Posted in: General AddOns
  • 0

    posted a message on Recommending you run an application as Adminstrator.
    Quote from flarecde
    That is definately a problem. If their installer can't assign proper permissions to a file, it's broken. If that's why they are telling people to run as administrator then that's just wrong.



    I agree but if you say that then people say you can't do that as it breaks UAC.. no idea how, but if it does then then it should be broken. From what I can tell it is file permissions and the default acls that break writing into Program Files not UAC.
    Posted in: General Chat
  • 0

    posted a message on Recommending you run an application as Adminstrator.
    yes, it is... but they don't seem to know it
    Posted in: General Chat
  • 0

    posted a message on Recommending you run an application as Adminstrator.
    Now in this thread they tell the user to just turn off UAC to run WoW.... seriosly how can just setting the permissions on files you install be worse then this and break UAC? How is it that turning it off is then better?

    edit.. it pasted the wrong thead.. let me see if I can find it again. but their search is lousy

    ok, found the right thead again, see post # 5

    http://forums.worldofwarcraft.com/thread.html?topicId=12661301751&postId=126599415855&sid=1#9


    btw, how do you link to single posts in the wow forums? anyone know?
    Posted in: General Chat
  • 0

    posted a message on Recommending you run an application as Adminstrator.
    Quote from Allara
    My perception from your posts above is that you were advocating for the WoW installer to modify Program Files\World of Warcraft ACLs in such a way as to allow access by any user and circumventing UAC. I think we've miscommunicated -- the virtualization should fix the issue. (In fact, with UAC turned on, it should be impossible for the above scenario to happen, and that was my original point.)

    I haven't looked into it -- if WoW indeed isn't setting this up properly, then they should fix it. Telling users to run as admin certainly isn't a good idea.



    Absolutely -- that's the whole point of UAC. It may or may not have been the best solution, but it was an attempt at fixing this fundamental flaw in Windows design.


    Just to be clear, I am advocating installing WoW so it runs from a non Admin account and blizzard changing their stance from recommending it be run as Admin.

    Others have said UAC prevents this, and I have said that you can set the acls and permissions on the files you installed to allow just this. You then said this violates windows best practices and breaks UAC. I still don't see how, but I reply that if that is so then it is worth breaking them as they are really bad practices.
    Posted in: General Chat
  • 0

    posted a message on Recommending you run an application as Adminstrator.
    Quote from flarecde
    I guess I dodge this issue a lot, although I run Vista, I do not use the Program Files folder.

    I was under the impression one of the more recent patches fixed WoW so it does virtualize properly, but I could be wrong.




    Here is the issue.... and this happened with WoW outside of Program Files anyway.

    The WoW installer can leave some of the files such as lichking.MPQ being owned by Administrator with no read rights for anyone else. This also gives a very misleading error message. Blizzards solution is to have you repatch, repair, and resinstall. Once this fails their solution is to have you run WoW as admin. Real solution is to fix the installer to put in proper access rights. The other issues are side issues really.
    Posted in: General Chat
  • To post a comment, please or register a new account.