MAPINFO Mystery

Need help with your project? Ask here.
User avatar
Herculine
Posts: 70
Joined: Mon Feb 22, 2010 3:44
Location: Ohio
Contact:

Re: MAPINFO Mystery

Post by Herculine »

Yep. That's where they were alright.

Thank you very much for that. It's the most useful thing I've learned about Windows in a long while.
User avatar
Rachael
Developer
Developer
Posts: 3639
Joined: Sat May 13, 2006 10:30

Re: MAPINFO Mystery

Post by Rachael »

You're welcome. :)
User avatar
Graf Zahl
GZDoom Developer
GZDoom Developer
Posts: 7148
Joined: Wed Jul 20, 2005 9:48
Location: Germany
Contact:

Re: MAPINFO Mystery

Post by Graf Zahl »

Eruanna wrote:Another idea I just thought of - Try moving the entirety of those folders to your desktop instead of Program Files. It may be using VirtualStore (which may be the copy of the file you sent, as well) - causing all sorts of hairy mess if not handled properly. Virtualstore is what Windows uses on the Program Files folder if otherwise an access would be denied. In this case it should not be enabled - but it's possible that it might be. (Also, try starting GZDoom in both cases as an administrator to see if it changes anything)

FYI, between these two versions a manifest entry was added to disable the virtual store. This means that a newer GZDoom version will never be able to see any file that got copied in there.

It cannot be stressed enough: Program Files is a write protected directory. Do not store any stuff there which may get modified by external applications, and for some reason Slade does seem to do some weird stuff here.
And do not put Doom ports in there if you want to extract PWADs into the same folder. I'm not sure how it deals with other applications mucking around with it, but with Slade it seems it does make some unhealthy assumptions.
User avatar
Gez
Developer
Developer
Posts: 1399
Joined: Mon Oct 22, 2007 16:47

Re: MAPINFO Mystery

Post by Gez »

Herculine wrote:The problem appears to be SLADE and apparently Virtualstore (the latter of which I'll admit is new to me).

I moved the entirety of my Doom directory to a folder outside of Program Files, then started SLADE and, while it should then have been unable to find any files, in its history it still showed the .wads I had edited and even opened them, despite the fact that they should no longer be there. Apparently it is keeping some sort of a cache history. How GZDoom (or ZDL?) got confused by it, I'm still not sure, but this definitely seems to be the root of the problem.
Textbook virtual store thing, and absolutely 0% SLADE's fault. You tell SLADE to open a file, it tries to open it, Windows redirects the access to the virtual store where that file still exists, so the file is opened successfully. SLADE works normally and as expected, and the confusion is entirely, completely, uniquely caused by your decision to put data in the Program Files directory.
Graf Zahl wrote:And do not put Doom ports in there if you want to extract PWADs into the same folder. I'm not sure how it deals with other applications mucking around with it, but with Slade it seems it does make some unhealthy assumptions.
No assumption is made other than when the user wants to open a file, it should try to open the file. Everything is explained solely by virtual store behavior.
User avatar
Rachael
Developer
Developer
Posts: 3639
Joined: Sat May 13, 2006 10:30

Re: MAPINFO Mystery

Post by Rachael »

Gez wrote:
Graf Zahl wrote:And do not put Doom ports in there if you want to extract PWADs into the same folder. I'm not sure how it deals with other applications mucking around with it, but with Slade it seems it does make some unhealthy assumptions.
No assumption is made other than when the user wants to open a file, it should try to open the file. Everything is explained solely by virtual store behavior.
Accusatory wording notwithstanding, Graf does have a point. (I'm sorry! I don't mean this in a bad way, though..) It might be worth investigating the manifest entry that stops the Virtual Store with Slade because as has been shown quite plainly in this thread, that can be a source of confusion for users, and you saw how it took some time to even come down and nail that issue because it's completely not obvious what happens here.

In fact, you could even plainly see that I didn't even know it was a problem until I reviewed her startup logs and saw where she was loading her files from.

Just telling someone "don't put it in Program Files!!!" is really not enough.
User avatar
Enjay
Developer
Developer
Posts: 4720
Joined: Tue Aug 30, 2005 23:19
Location: Scotland
Contact:

Re: MAPINFO Mystery

Post by Enjay »

I think the main problem here is the entirely reasonable assumption from many users that "program files" is where programs are meant to go. On the face of it, it makes sense, most programs a user installs with automatically go there and they will work properly. These days, it will be fairly alien for a user to install things into a directory that they create and name outwith Program Files.

Also, most users simply won't be aware of the special handling of what happens in Program Files. Unless you go searching for it, know what to search for and understand the ramifications of what you find, the inappropriateness of putting certain programs into Program Files, the virtual store and other associated issues are things the most users will be blissfully unaware of. Therefore, the onus unfortunately falls to the producer of the software (who should understand the issues) to make it as obvious as possible that "Program Files" is inappropriate for their program if they want users to use their program successfully.
User avatar
Gez
Developer
Developer
Posts: 1399
Joined: Mon Oct 22, 2007 16:47

Re: MAPINFO Mystery

Post by Gez »

Putting programs in program files is not a problem. Putting data in program files is. Herculine's problem wasn't caused by GZDoom or SLADE being in program files; it was caused by the wad being in there.
Eruanna wrote:Accusatory wording notwithstanding, Graf does have a point. (I'm sorry! I don't mean this in a bad way, though..) It might be worth investigating the manifest entry that stops the Virtual Store with Slade because as has been shown quite plainly in this thread, that can be a source of confusion for users, and you saw how it took some time to even come down and nail that issue because it's completely not obvious what happens here.
Doesn't seem to work.

Old manifest:
Spoiler:
New manifest:
Spoiler:
I've put a test.wad file in protected folder, accessed it and saved it with SLADE to create a copy in the virtual store, then quit SLADE and deleted it from the real folder. Updating the manifest to add the trustinfo thingamabob, restarting SLADE, attempting to open the file... success, the file is retrieved from the virtual store instead of failing to open. Either there's a subtlety I'm not grasping in this Microsoft mumbo-jumbo magic manifest malarkey, or it's not working as advertised and therefore useless.
User avatar
Rachael
Developer
Developer
Posts: 3639
Joined: Sat May 13, 2006 10:30

Re: MAPINFO Mystery

Post by Rachael »

Try putting two different copies of that file. It may be retreiving from Virtual Store just because the master copy no longer exists.
Post Reply

Return to “Editing Help”