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.
|
Not Categorized, Please Help
|
|
