G
Guest
Hello, everyone.
I'm thinking of calling inuse.exe from a batch file that's incorporated in
an exe created by InstallShield. To allow the batch file to call inuse.exe
successfully, a copy of inuse.exe is copied to a user's machine temporary,
and when the batch file execution is done, inuse.exe is deleted permanently.
My concern is insue.exe has its EULA that the user of inuse has to agree it.
If some other people that uses my InstallShield created exe, they would not
know inuse.exe has been utilized. If they don't know, how do they consent to
the EULA?
Can someone enlight me on this concern? I've tried to search for the
information that says other people, who can run my Install/Uninstall EXE, do
not have to consent, or is given consent automatically as soon as they run my
EXE, but no avail.
TIA.
Min.
I'm thinking of calling inuse.exe from a batch file that's incorporated in
an exe created by InstallShield. To allow the batch file to call inuse.exe
successfully, a copy of inuse.exe is copied to a user's machine temporary,
and when the batch file execution is done, inuse.exe is deleted permanently.
My concern is insue.exe has its EULA that the user of inuse has to agree it.
If some other people that uses my InstallShield created exe, they would not
know inuse.exe has been utilized. If they don't know, how do they consent to
the EULA?
Can someone enlight me on this concern? I've tried to search for the
information that says other people, who can run my Install/Uninstall EXE, do
not have to consent, or is given consent automatically as soon as they run my
EXE, but no avail.
TIA.
Min.