Can't open file for writing (Vista)

I have found that the file is being created. It's just being written into the C:\Windows\System32 directory for some unknown reason. Since I also open files for reading, and they are read from the current directory when no location is specified, under Vista, breve must be handling files open for writing differently than it handles files open for reading. It appears that the directory it is using is the first one found in the Path system variable (itself found in the Environment Variables list of the "System" Control Panel, Advanced system settings). This is not good. Can the expected behavior - i.e. using the current directory - that is found in earlier versions of Windows be easily restored under Vista and preserved in said previous versions??

Suggestions welcome.

Marisano

Yes, I have tried it. I believe the real problem is that breve creates a new process, but that process does not have the same privileges, or at least not the same state, as the breve process itself (opened with administrator privileges). I do not know how to correct this.

You said you tried it, what are you referring to specifically?
Can you see a process traced to breve or is this just an assumption?

Just for fun now since you are the administrator, change the write privileges for the directory where your user can save her work. Then put Breve in that directory, let me know what happens?

Are you saying that any program has absolute indiscriminate control of your machine? If you don't know then how can you know it's Breve and not something else?

Carry On,

I hope you solve the issue. You shouldn't be concerned with breve specifically, 2000 and XP work, there may not be a solution.

You indicated that breve can open a file for writing from the system defined path, changing this variable has no effect on your system. It doesn't exclude the system as the cause. Vista may be more secure, from a unix perspective I have alternative user accounts for normal operation, even with administrative privileges the user still has to bypass specific systems in order to install, read, or write from other parts of the system. This is a standard security measure.

I like Microsoft's OS redundancy it's fairly simple to make a change to a gateway or remote print spool directory, many on the commands are apparent, in many cases multiple changes need to be made in order to change the operation of the system, especially in networking. There may be another system variable file or administrative application to access before the write directory of your choosing can be altered.

I have tools that can interface on the system level, but more specifically it requires root access, not just administrative access to make a change. You may want to find out how to make this change not just for breve but for your own access to your system.

I have not failed! I have only tried 100,000 ways that will not work. —Thomas Edison

I realize it can be a real pain solving these inconsistencies between systems. A .plist is a stand Apple OS X preference file, the included developer tools apps opens it. The fact we learn so much about our systems makes it in many ways more difficult we're checking permissions, and running background process traces, when an average user would say "It might be a preference or some system plugin". Good luck coding.

I have not failed! I have only tried 100,000 ways that will not work. —Thomas Edison