1. Installer Associations
Hi Travis,
for some background info, I associate the .EX, .EXW, .E and .EW files with
my text editor and not with the interpreter.
The reason is that I'm doing more editing of these files than running them
so this is the "default" activity for my euphoria files.
The idea of having multiple associations (verbs) for the file types is nice
too. That way I can right-button click and select either Edit or Run .
-----------
cheers,
Derek Parnell
Senior Design Engineer
Global Technology Australasia Ltd
dparnell at glotec.com.au
---------------------
--------------------------------------------------------------------
CAUTION - This email and any files attached may contain privileged and
confidential information intended solely for the use of the individual or
entity to whom they are addressed. If you are not the intended recipient of
this message you are hereby notified that any use, dissemination,
distribution or reproduction of this message is prohibited. If you have
received this message in error please notify the sender immediately. Any
views expressed in this message are those of the individual sender and may
not necessarily reflect the views of Global Technology Australasia Limited.
--------------------------------------------------------------------
2. Re: Installer Associations
Hi Travis,
In addition tot 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.
Derek Parnell
<ddparnell@big To: EUforum <EUforum at topica.com>
pond.com> cc:
Subject: Installer Associations
07-09-2001
01:39
Please respond
to EUforum
Hi Travis,
for some background info, I associate the .EX, .EXW, .E and .EW files with
my text editor and not with the interpreter.
The reason is that I'm doing more editing of these files than running them
so this is the "default" activity for my euphoria files.
The idea of having multiple associations (verbs) for the file types is nice
too. That way I can right-button click and select either Edit or Run .
-----------
cheers,
Derek Parnell
Senior Design Engineer
Global Technology Australasia Ltd
dparnell at glotec.com.au
---------------------
distribution or reproduction of this message is prohibited. If you have
received this message in error please notify the sender immediately. Any
views expressed in this message are those of the individual sender and may
not necessarily reflect the views of Global Technology Australasia Limited.
3. 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.
4. Re: Installer Associations
Howdy y'all!
Sorry that it has taken me so long to respond. My work load suddenly shot
up about 3,000,000% in the last couple of days. But it is calming down now!
> 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.
Yes, you and Jasper have brought up some very good points -- in fact, from
what I've read, there may be some similar issues where Windows 2000 is
concerned. I am running under a bit of a handicap here because I've never
been exposed to either version of Windows ... the only versions that I have
used are '95 and Me. So, I will default here to thinking in terms of Linux,
which sounds like it has a similar system, which Micro$oft no doubt
double-engineered into Windows.
It seems to me that this will boil down a couple of different ways:
1. The installer will have to be run by the root user (or someone that can
use the Windows version of the "su" command). So I may have to put code
into the installer which can detect this programmatically.
2. The installer (or the person using it) could install Euphoria within the
user's "home" folder; unless of course, as mentioned earlier, the root user
has disallowed the installation of executable files into a user's home
directory. Then, we may end up with an "almost installation," which is a
condition I'd like to avoid, because it'll make quite a mess. One thing I
would mention here is that the installer was never meant to have the
capability to "sneak" Euphoria onto a computer: if the user needs to resort
to subterfuge to get Euphoria onto a computer, they might need to install
the Euphoria files on one computer, copy an image of those files, then
install them manually to their secret location.
An NT/2000 question: can the user do this in a batch file?
REM Euphoria.bat
@echo off
PATH=%PATH%;h:\euphoria\bin
EUDIR=h:\euphoria
exw.exw %1 %2 %3
This could be a workaround for the problem of not being able to modify the
autoexec.bat file without root permissions.
I'll do some research today about this. I know that I can programmatically
determine which version of Windows the user is attempting to install on. I
will have to determine if they are the root user, and modify the installer's
actions and messages accordingly.
By the way, my website has officially moved to a new home. If this new home
cannot handle the installer zip file, Alison Alpert at Assistech has
graciously offered to put it on their web site for me.
http://rain.prohosting.com/tbeaty
I've placed a "redirection" page on the old site, but it's anybody's guess
how long it'll be there before ArNet removes the page altogether.
Again, I would like to thank everyone for their input concerning the
installer. I apologize for the delay in reacting to it ... all the
suggestions are going onto my to do list and will be looked at. I promise
this.
Thanks to all!
Travis Beaty
Claude, Texas.
5. Re: Installer Associations
Hi Travis,
A little bit late but anyway. You batch-file looks similar to mine:
SET EUDIR=E:\EUPHORIA
SET EXW=E:\EUPHORIA\BIN\EXW
%EXW%
This works fine for me. I work on an E: - drive (this is a seperate
harddisk, not a network-drive but that should make no difference) and have
no writing rights on my C: - drive. Okay, I could ask for more
writing-rights but in Holland we say: one shouldn't awake sleeping dogs. In
my case, nobody forbid me to install non-company programs, they just shut
the sytstem for a great part. So I see no ethical restrictions there. (This
mailing list is as a matter of fact far more time-consuming at work.)
Bye,
Jasper.
Travis Beaty
<travisbeaty@a To: EUforum <EUforum at topica.com>
rn.net> cc:
Subject: Re: Installer Associations
09-09-2001
18:56
Please respond
to EUforum
-
-
-
An NT/2000 question: can the user do this in a batch file?
REM Euphoria.bat
@echo off
PATH=%PATH%;h:\euphoria\bin
EUDIR=h:\euphoria
exw.exw %1 %2 %3
This could be a workaround for the problem of not being able to modify the
autoexec.bat file without root permissions.
-
-
-
Thanks to all!
Travis Beaty
Claude, Texas.
