atioglxx.dll access violation with Aurora Toolset

[Legacy_Lorthirk]

               Hello all... Yes, there's still someone who's trying to build somethigng '>

I'd like to dive in again in NWN to realize a small project, and so I reinstalled NWN. I started to play again with Aurora Toolset but, as soon as I try to add something on first area, access violations starts to pop up letting me the sole option of killing nwtoolset.exe. I am working with Windows 7 64 bit, Intel i7-820QM and a Mobility Radeon HD4670 with Catalysts 10.7. The strange thing is that if I try to play the game and load the module, everything is fine, so it seems that it's an Aurora Toolset restricted problem. I looked around for some threads but I found nothing useful. Can I have some help, even just getting a "you can't do anything, live with it" verdict? '>
               
               

               
            

[Legacy_Fester Pot]

               link
link
link

FP!
               
               

               
            

[Legacy_MrZork]

               EDIT: Wow! You have to get up pretty early in the morning to sneak in ahead of Fester Pot! '> The advice I suggested below is easy to try, but the smart money is to follow FP's links.



I am certainly not the resident expert on this sort of thing, but you should double check that you are running the Toolset in compatibility mode and as an administrator.

As I understand it, in order to prevent certain malware from spreading itself around your system, Windows Vista/7 place restrictions on where installed software can modify files. That's why there's the whole \\Users\\*username*\\AppData\\etc. tree. To accommodate software written when it was okay for apps to modify files in their own directories, the compatibility modes are supposed to allow that (among other things).

Anyway, try compatibility mode and running as Administrator and see if that helps.
               
               

               

                     Modifié par MrZork, 16 août 2010 - 09:57 .
                     
                  

            

[Legacy_Lorthirk]

               @Fester: checked, checked and checked. Since I have a relatively new card and system I can't use old drivers.



@MrZork: already did it, I'm running as administrator and tried both compatibility for Windows XP SP3 and Windows 2000.