Post by PaulPost by mikePost by PaulPost by mikePost by Kerr Mudd-JohnPost by GARYWCC:\>
dir /s *.jpg >listjpg.txt
why am I'm getting an ACCESS DENIED message?
(I'm running Windows 7)
you don't have read access to some subfolders, or (more likely) you
don't have write access to the current folder.
home or pro?
Are you an administrator?
Did you open the command prompt with "run as administrator"?
Remove the redirect and write to the display.
That will tell you if it's a read or write issue.
If the display is correct, change the redirect to a place
to which you do have write permission.
I can't test the read issue for you because I take
ownership of the whole damn drive on my systems.
Your command works fine on mine.
Did you actually do that on C: ?
I'm interested.
If I look at permissions for c:, all the checkboxes
in effective permissions are checked. The drive is still
owned by trustedinstaller. I think I actually
took ownership in only those places where it wouldn't let me
change permissions.
On this system, I am the owner of Program Files.
I didn't change anything that
should reduce the ability of the system to do its thing. Seems to work.
Post by PaulDoes Windows Update still work ?
Windows update has been disabled since day one via the
standard MS GUI interface.
Post by PaulCan you install a program in Program Files as normal ?
Most installers put programs in Program Files. Problem I had
was that sometimes you needed to put additional .dlls in
the program directory to enable additional functionality.
Taking ownership (and permissions) allowed that.
When it comes to forcing
the OS out of my way, I tend to use the chainsaw rather
than the scalpel.
That's one of my pet peeves with linux. It's always asking me
for a password. I have not yet discovered the inner chainsaw. ;-)
On Windows 7, you can record permissions and reload them after surgery.
For any DLLs you added to a Program Files, there would be no recorded
permissions for those, so they wouldn't match the other files
in the folder in question.
http://dandar3.blogspot.ca/2013/01/how-to-ntfs-compress-windows-winsxs.html
Thanks for the interesting link. Procedures like that are the primary
reason I don't like desktop linux. I'm not about to do it in windows ;-)
Post by PaulFor Linux, if you install the OS on a hard drive, sudo prompts
for a password. On the other hand, using a LiveCD, sudo doesn't
prompt for a password. I don't know if the password is blank
on a LiveCD and that makes a difference, or there is an actual
active method to preventing it from prompting (gksu?).
Even if you could do without a password, that opens up other
cans of worms relative to network permissions.
You can add yourself to the sudoers group or permission list or
something. That helps with the sudo stuff, but not the zillion
other things that require a password to proceed.
Problem is that there is no such thing as desktop linux. It's a random
assignment of stuff called a distro. And determining exactly how to
do anything on this version of that distro with the other desktop manager
is difficult for the newbie.
I've been messing with linux since it came on a single floppy.
I have yet to reach critical mass of stuff that works on a single
distro to make it a viable alternative to windows for those of us
who don't want to become a guru.
Not allowing logins as root was a step backwards.
First thing I do in a command prompt is sudo -i
I recently discovered gksu. In order to copy library files
I have to open a command prompt, run gksu to get nautilus to open,
run it again for another instance just so I can use the GUI to
drag/drop a damn file.
I'll shut up now. This is the wrong group for another linux rant.