Re: Im New

chmod isn't supported on win32 operating systems, as they don't have file ownership/permission systems anything like what *nix does. It makes perfect sense that you're getting "bad command or filename" errors, because chmod IS a bad command for this platform.

-Any sufficiently advanced technology is
indistinguishable from doubletalk.

Comment on Re: Im New

Replies are listed 'Best First'.
Re: Re: Im New by helgi (Hermit) on Sep 16, 2002 at 10:15 UTC
Untrue. chmod as a command does not exist on Win32, unless you add it yourself via, the POSIX package in the Windows resource Kit, via Cygwin or via Perl Power Tools or the like. However, file ownership/permission systems are most definitely supported by Windows NT and its descendants, Windows 2000 and XP. In fact, permissions and access restrictions are far more sophisticated and fine grained in NT than in ordinary Unix systems (there are ACL systems available for some Unix variants). The command used to modify these permissions from the command line is called cacls. Type cacls /h for details. Regards, Helgi Briem	[reply]
Re: Re: Re: Im New by Hero Zzyzzx (Curate) on Sep 16, 2002 at 20:21 UTC
Thanks for the clarification, but I didn't say they didn't exist (I know about NT/2k/XP ACLs) I just said that they weren't anything like what *nix has. To me, this looks like a newbie typing "chmod" in a DOS console, I don't think they really care about file permissions/modes other than to get their script running. -Any sufficiently advanced technology is indistinguishable from doubletalk.	[reply]