Vista, writing to files on c:\

One of our access based systems at work requires access to two files on the root of c:, problem is, Vista denies it. If I go and open the files myself I only get read only access :rolleyes:.

Anyone know a way to fix these permissions? I need to be able to write to these files and locating them elsewhere is not an option :(.

easy anser is sstop using vista :wink:

That’s not an answer at all…

Have this or this got any bearing on the subject ???

if on a network give users local admin rights to c:\

Or rather than open up the whole c Drive just give permissions to the specific file / folder hat file is in

you can make it just C:\ and not subdirectories … sounds like its trying to save to route , if the file name is not the same each time Vista would deny file access as it does now.

Open an administrator command prompt by typing cmd into the start menu search box, and hit the Ctrl+Shift+Enter key combination.

takeown /f C:*filename*
That will give you ownership of the file.
cacls C:*filename* /G username:F
This will allow you to delete the systemfile.
You may have to reboot into safemode to do the above.

[QUOTE=MickeyC;369162]Open an administrator command prompt by typing cmd into the start menu search box, and hit the Ctrl+Shift+Enter key combination.

takeown /f C:*filename*
That will give you ownership of the file.
cacls C:*filename* /G username:F
This will allow you to delete the systemfile.
You may have to reboot into safemode to do the above.[/QUOTE]

Had a go…

C:\Windows\system32>takeown /f C:\calls.mdb

SUCCESS: The file (or folder): "C:\calls.mdb" now owned by user "*************\*****".

C:\Windows\system32>takeown /f c:\goodsin.mdb

SUCCESS: The file (or folder): "c:\goodsin.mdb" now owned by user "*************\*****".

C:\Windows\system32>cacls c:\calls.mdb /G *************\*****:F
Are you sure (Y/N)?y
processed file: c:\calls.mdb

C:\Windows\system32>cacls c:\goodsin.mdb /G *************\*****:F
Are you sure (Y/N)?y
processed file: c:\goodsin.mdb

(Stars added by me)

End result? Exactly the same :(. Open a file that’s in C:\ ‘this file is read only’.

Just a thought…try renaming the files, or better on boot copy out of a directory back into root. You could have this on shut down copy the files back to a directory. I had this once, and well the root was protected by an old ADMIN. But the user had ADMIn rights, but it looked all the root files, but when I copied into directory it worked…worth a try. You may need to use a few flags.

Darin B IM’d me and could you check if you have any ldb files. These are made when file is opened, and should be gone when you look at C:\ root. If not the file is left in a locked single use position. Make sure in your code to set db = nothing on exit.

View the permissions on the file and see if “Trustedinstaller” is the owner, or has permissions on the file.
If so then you need to remove that “user” from the permissions to take full control.

Speedo (Alex) got it all sorted…used XP. Seems Vista is still not ready for normal daily things…oh well!

Investigations temporarily suspended due to driver stabilities :rolleyes:, forced to use xp to stop the random rebooting :(.