You're right! I forgot about the NT POSIX tools. But I was unable to ever get the 'chown' command to work. This stuff is pretty crude. MKS Toolkit is far superior. Has anyone ever gotten the NT reskit 'chown' to work? Here's what I get from the very latest version:

C:\WTSRV\Profiles\mmm.000>f:chown usage: f:chown [-Rf] group file ...

C:\WTSRV\Profiles\mmm.000>f:chown nt-domain\tgroup xx f:chown: unknown group id: nt-domain/tgroup

Maybe it would work if it were running in a POSIX NT subsystem. And why does it say you should supply a group? If someone wants to dig into it and figure out why it doesn't work that would be good. In the meantime, as I mentioned before, there are other programs like "subinacl" and "cacls" that I know do work to natively manipulate the NT security settings.

Mark

-----Original Message----- From: tkaczma@gryf.net [mailto:tkaczma@gryf.net] Sent: Friday, June 18, 1999 10:26 PM To: toasters@mathworks.com Subject: Windows NT Resource Kit partial contents

For those of us who are unfamiliar with the contents of the NT RK, here is the info from WHGIII's playground:

----

Microsoft Windows NT Questions and Answers

How can I ease the transition from UNIX to Microsoft Windows NT?

There are a several utilities in the Windows NT Resource Kit that will be familiar to the UNIX user. Among them are:

ar.exe, cat.exe, cc.exe, chmod.exe, chown.exe, cp.exe, devsrv.exe, find.exe, grep.exe, ld.exe, ln.exe, ls.exe, make.exe, mkdir.exe, mv.exe, rm.exe, rmdir.exe, sh.exe, touch.exe, vi.exe, and wc.exe.

When using these from the DOS shell you do not need to type the file extension. When in the 'sh' shell the extensions must be used. Please note that these files execute in upper case. Once SH.EXE has been started, an alias can be created to change case and form e.g. alias cat=CAT.EXE.

These utilities will allow you to leverage your UNIX script file investment.

----

Source:

http://www.microsoft.com/SalesInfo/QA/QA5909.HTM