RE: Installer Associations
Having been a Corporate LAN Administrator, I can tell you that if the
company has decided that they don't want you to install software, they
probably aren't going to let you do much in the Control Panel either.
Additionally, if there is a good chance that a periodic job runs looking for
unauthorized executables in "personal" space. Before you achieve a work
around in such a case, you should check your personal risk level in regard
to Corporate Policy on bootlegging unauthorized software.
One of my monthly functions was to find unauthorized software in users
"personal" space and delete it. On the second occurrence for any given
user, they received a warning from Corporate Security, their manager got a
copy. On the third occurrence, both they and their manager received an
opportunity to explain it to the CIO. I never ran across a third instance,
so I don't know for sure what would have happened next.
ET
-----Original Message-----
From: freeplay at mailandnews.com [mailto:freeplay at mailandnews.com]
Sent: Friday, September 07, 2001 8:40 PM
To: EUforum
Subject: Re: Installer Associations
At 11:39 07/09/01 +0200, you wrote:
>Hi Travis,
>
>In addition to Derek's comment the following. On my computer at work I
>associate the exw-files with a batch-file. This because it runs NT and due
>to corporate policy I have no permissions on my C: drive. (Yes, I'm a
>loan-slave.) This brings up an other issue: How to install EU in a NT
>enviroment with limited writing rights. For editing I use the right-button
>and then Send To .... text editor.
>
>Bye,
>
>Jasper.
I was going to wait until I had experimented with EWI more before posting
comments but the issue Jasper raises about using a Windows NT 4.0
workstation (service pack whatever) that has been "locked down" is, IMHO,
worth a bit more discussion.
Here are some problems I think might crop up in this scenario if the NT
administrator has gone to unusual lengths to prevent you doing anything
"interesting" - and that includes installing software!
You don't have access rights to create or modify the C:\AUTOEXEC.BAT file.
You might be able to get around this using "Start : Control Panel : System"
and clicking on the Environment tab. Here you can modify PATH to include
the Euphoria BIN subdirectory at the end of PATH and also set EUDIR to the
correct directory. This is how I do it with the RDS installer: I don't
allow it to modify AUTOEXEC.BAT and then manually make the changes via the
System (Environment) Control Panel. I suspect there must be an API that
allows you to do this but I'm no Windows programmer 
You can't create C:\EUPHORIA. The only directory you have full access to
might be a network drive such as H: - the installer should cope with this
right now because you can specify both the drive letter and directory. It
just might be something to look out for.
Unable to use an existing or create a new temporary working directory.
Personally once the user had stated they want to install to "C:\SOMEDIR" I
would create "C:\SOMEDIR\tmp52314.dir" and use that and then at the end of
the install clear it out and remove it. Although you would like to assume
that C:\WINNT\TEMP is a perfectly good temporary directory to use I would
rather trust a directory I had managed to create myself.
That's about all that springs to mind right now.
Regards,
FP.
|
Not Categorized, Please Help
|
|
