Saving files in Program Files (x86) in Windows 10?

[Ravick]

Hi there,

So, in my computer, Slade is unable to compile ACS ( apparently )because my OS doesn't allow it to create temporary files in system directories. I get the following when trying to compile an ACS lump:

=== Log: ===
Host byte order: LITTLE endian
=== Error log: ===
Original ACC Version 1.10 by Ben GokeyCopyright (c) 1995 Raven Software, Corp.This is version 1.54 (Mar 10 2015)This software is not supported by Raven Software or ActivisionZDoom changes and language extensions by Randy HeitFurther changes by Brad CarneyEven more changes by James BentlerSome additions by Michael "Necromage" WeberError reporting improvements and limit expansion by Ty HaldermanInclude paths added by Pascal vd Heiden**** ERROR ****Couldn't open file.File: "C:\Program Files (x86)\SLADE\temp\JOGADOR.acs"

Being myself the admin user of this comp, how can I make my OS to allow me (and my programs) to create files in system directories such as Program Files (x86)?
I've tried dozens of methods from answers.microsoft.com, but none of them have solved it.

Or... if it is not the root of the problem, what could it be?

Thanks in advanced.

[Rachael]

You have to disable UAC in order to allow this.

This is really really really not recommended. It's better to put Slade into a folder on your desktop and run it directly from there.

http://www.howtogeek.com/howto/windows- ... ows-vista/

[Ravick]

I've tried this already, but it didn't solve the problem.

[wildweasel]

Maybe this is an obvious question, but why is Slade in Program Files?

But perhaps less obvious is this: does Slade save a "temp folder" setting to an INI anywhere? Maybe that's still "stuck" to its old location, if you've already tried moving it to someplace else.

[Rachael]

Well the nitty-gritty way is to grant your user account full permissions to access the files in the Program Files folder. You do this by right-clicking on the folder in Explorer and selecting "Security".

But I really would not do this. What can Slade do in the Program Files folder that it can't do in your desktop folder? The system restrictions are in place for a reason and bypassing them is NOT a good idea.

Lastly, if you really insist on keeping it there, you can also set compatibility mode to Windows XP. This forces Windows 10 to create a virtual Program Files folder that Slade can actually write directly to. But no changes it makes will actually appear there - it will go to your VirtualStore instead. more info

[Ravick]

Well, the installer did so (IIRC o.õ ). I mean, I would not actively choose this folder to install it. Other programs, such as GZDoomBuilder were also installed there. As I didn't know win10 wold have problem with this, I just followed the installer's steps.

GZDoomBuilder, however, can compile maps's ACS lumps.

Well, I guess I'll try to move it then. Uh... do I need to re-install it?

[Rachael]

Well, I guess I'll try to move it then. Uh... do I need to re-install it?

No. Just drag-drop it to your desktop or some folder like your Documents folder.

Then open the folder and look for the Slade3 executable, and alt+drag it to the desktop (or just right click it and click "Send To>Desktop (Create Shortcut)").

After that, fix your desktop icons, and you should be good.

[Ravick]

Thank you, Eruanna and WW!

It works fine now! Let Program Files locked for good then!

[Rachael]

You're welcome.

[Graf Zahl]

The real question should be: Why does Slade even ATTEMPT to write to Program Files? That's such a gross violation of Windows standards it truly defies belief. And if this is a problem with ACC it should be clearly outlined what is missing. Normally any such intermediate output should go to the system's Temp folder and nowhere else. That's what it is there for.

[Rachael]

Probably for the same reason it doesn't support LZMA in zip archives.

I'm not saying I can do better, but this is a community based off of a very old game, and we've grown extremely comfortable with DOS standards even when they have hurt us for years...

It's a lot easier to leave things as is than it is to adapt to change.

[Graf Zahl]

In this case I declare that statement bullshit. It's either Slade running ACC from the wrong directory or not specifying an output name, most likely the latter. ACC can do it:

Code: Select all

Usage: ACC [options] source[.acs] [object[.o]]

-i [path]  Add include path to find include files
-d[file]   Output debugging information
-h         Create pcode compatible with Hexen and old ZDooms
-hh        Like -h, but use of new features is only a warning

Sorry, but shrugging a thing like this off with sticking to DOS standard does not fly.

The LZMA problem can be attributed to wxWidgets and the reluctance of using a different decompression library. It's not the only thing where wxWidgets is irreparably broken. I also found out that their image loader is also quite worthless, uncontrollably outputting error message boxes when something goes wrong instead of letting the appplication deal with such problems.

When working with wxWidgets I generally refrain from using their 'convenient' resource mangement libraries because they all are shit.

[InsanityBringer]

The real question should be: Why does Slade even ATTEMPT to write to Program Files? That's such a gross violation of Windows standards it truly defies belief. And if this is a problem with ACC it should be clearly outlined what is missing. Normally any such intermediate output should go to the system's Temp folder and nowhere else. That's what it is there for.

The weird thing is that I really don't think its supposed to by default. I have always had Slade 3 in my Program Files folder since I set up my Windows 8 and later Windows 10 machines, since the installer puts it there by default. (to be fair though my ACS executable is not within Program Files but I don't think this is relevant). I have never had this problem on my machine. I am always sure to ensure that Slade 3 doesn't get installed in "portable" mode, which may have gotten enabled here. But if portable mode was enabled, wouldn't it have trouble writing config files? (though then again, assuming Microsoft's virtual folders thing is still around, Windows might silently deal with that)

[DaMan]

You have to disable UAC in order to allow this.
http://www.howtogeek.com/howto/windows- ... ows-vista/

You have to do the registry hack to completely disable UAC in Win8/10. You won't be able to run apps if you do this.
Checking run as admin (right click, properties, security tab) on acc.exe should fix this (can try it with slade but dunno if child processes will have admin rights).

[Ethril]

You have to disable UAC in order to allow this.

You don't have to disable UAC; the demons took care of that already.