about INUSE

  • Thread starter Thread starter Eddy Furlender
  • Start date Start date
E

Eddy Furlender

Hello All,

I found some strange phenomenon with the INUSE utility -
the file updated with it looses Everyone's or Users'
security attributes and is not accessible (unable to run)
by a limited user.

Any idea?

Thanks in advance,

Eddy.
 
Eddy,

I don't know about this "bug" so can't help you with it.

However, I was wondering about your concerns. For me it'd make a sense to use InUse (or any other tool that just delays the file
copy/move until the reboot though pending operation) to replace OS locked files (system Dlls, etc.). For those Dlls I can hardly
imagine setting custom security attributes. Could you tell me why would you need that?
 
KM,

I tried to use the INUSE for our (non-system) application
located under Program Files. Some files are activated on
the login and appear in system tray as indicators. I
wanted to use the INUSE to replace them. What happens -
after the replace procedure is completed, if a Power User
logs in, everything works. But if a limited user logs in,
these files can not not be activated. I was unable even
see their icons or properties. The reason for this was
that the limited user is not in the list (in the Security
tab of Properties). I can add the user or Users manually
(when logged in as Administrator) and then these files
work.

Any suggestion?

Thanks,

Eddy.
-----Original Message-----
Eddy,

I don't know about this "bug" so can't help you with it.

However, I was wondering about your concerns. For me it'd
Click to expand...
make a sense to use InUse (or any other tool that just
delays the file
copy/move until the reboot though pending operation) to
Click to expand...
replace OS locked files (system Dlls, etc.). For those
Dlls I can hardly
imagine setting custom security attributes. Could you
Click to expand...
tell me why would you need that?
 
KM,

Thank you very much for your time and for the
information. The CALCS.EXE works, but the whole procedure
is not acceptable - the CALCS.EXE must be activated after
the computer restart, after the files are actually
copied. If the EWF is enabled, two restarts are required
to commit changes.

There is nothing better than make own procedure - very
small procedure that uses MoveFileEx. It keeps access
control for all users - inherits from the folder list.

Thank you again,

Eddy
 
Back
Top