Jump to content

Arogtar

Community Members
  • Posts

    4
  • Joined

  • Last visited

Arogtar's Achievements

Tiro

Tiro (1/14)

0

Reputation

  1. My W machine here has 9, so what ? It's not about quantity my friend
  2. Sure, and for I did know that I had no problem with it. But take the casual guy who reinstalls windows and still has more than 1 partition which containts just EVERYTHING. Long story short: If you like to cover up this case you can make the setup routing throw a more specific error. At least "my non-IT guys" tend to have 2+ partitions, which might of course be a rare occasion - idk
  3. Sure, for the system is wiped this will be the case after every whatsoever install of W7. Which is just dumb, but ok if you look at it from MS's perspective. (They can't just preset everyone's HDD partitioning.) Of course this will fix it, and that's what I already did. Still, the wider this game will spread the more threads you will get like: # Installer doesn't work ! And I didn't get a specific error # Did you run as admin ? # No ! # Please do # Works ! The much simpler way to deal with this is to check if you can write to the install dir and throw an error if you can't. (e.g. "please run as Administrator" or stuff) Regards Oliver
  4. Hey there, can't say anything about the game yet, but I sure liked the preview from golem, so there might be more stuff coming in Given: W7 x64 Permissions like on the attached screenshot (access.JPG). Problem: Setup can only be run as administrator, but it doesn't require those permissions on startup, so no writing to the HDD is possible (error.JPG). Cause: I wiped my system drive some time ago, therefore the currently set SID (which used to define owner and access permissions) of G:\Games is gone. Restriction: I guess this will only occure on systems where W7 has at least once been installed before. At least I don't remember such problems when upgrading from XP. Solution: Let setup require administrative permissions on run Impact: I honestly don't think this is a rare problem. Also it can't easily be fixed because taking ownership of the dir is not enough, you pretty much have to clean up after Microsoft here...and by "clean up" I mean "fix everything in recursive mode"... In short: The common user won't do it. (And I won't neither ) Greetings Oliver
×
×
  • Create New...