6 réponses à ce sujet

[simuseb]

I've run into a strange issue that, if it's not fixable, I'm glad I've found it now before I invested too much into developing this module. I've spent a few days creating a module. I decided to run the toolset as an administrator to fix an issue, but I found I could no longer open my module. It wasn't appearing in the list of modules. Strange. I looked in the folder... it was gone! I opened the toolset again, this time not as an administrator, and found the module. What? I decided to save the module as a new file. This new file did not appear in the module folder and is inaccessible when the toolset is run as an administrator. Should I ever finish this module, I may wish to share it, but I cannot do that if it's not there. I don't understand what could be causing this issue.

[simuseb]

This has been fixed.

[Tarot Redhand]

So what was the cause and the solution?

 

TR

[simuseb]

Cause? No idea. It's a weird issue. I just had to overwrite an existing module while running the toolset not as an administrator, and then, while running it as an administrator, open the overwrittern file. I assumed it has something to do with premissions. Maybe the toolset, when it isn't being ran as an admin, isn't allowed to create new files, I dunno.

[Tarot Redhand]

AFAIK if a program is going to write stuff to disk, it needs administrator permissions on all versions of windows starting with vista.

 

TR

[simuseb]

Yes, but I don't know why the module, that wasn't saved to the folder apparently, was accessible via the toolset in the first place considering the file was non-existing lol

[Tarot Redhand]

It's your PC - it's haunted 

 

TR