Re: Currently Seeking Auto Execs
On 27 Jun 2001, at 0:27, Gerardo wrote:
> My copy of Win98 (should check other versions) maintains an environment
> variable called 'winbootdir' that contains the string 'C:\WINDOWS'. This I
> take to mean 'the Windows directory in the drive from which the current
> instance of Windows has been booted.'
>
> Of course, this doesn't mean that it's the only bootable Windows disk in the
> system, but it should give you a head start, perhaps to offer as first choice
> to
> the installing user.
I've decided on the simple approach to determining which autoexec.bat file to
modify. I've built up a form which is displayed when it comes time to modify
the autoexec file. This form contains a combo box which shows a listing of all
the drives on the user's system. It will of course default to the drive upon
which Euphoria has been installed.
That was where the consideration of removable media came in. For 80% of the
human race, this won't be a problem because the only removable media listed
would be the 3.5er and the CD-ROM. But there may be those techno-junkies out
there installing Euphoria on a box with five floppies, four CD-ROMs, three
DVDs, two zip drives, and a partridge in a pear linked tree.
> If you modify autoexec.bat, even with the user's permission, don't forget to
> make a copy of the old file, _and_ tell the user what you called it: say,
> autoexec.eu4. Please, don't call it autoexec.old!
Will do.
> And if the user declines your kind offer to modify autoexec.bat (suspicious
> people, and you such a nice guy!), it would only be courteous to tell them to
> (no, not that!) add this string and that, later, at their convenience.
Ah, I've got that covered as well. The user will have four options.
1) Let the installer modify the file.
2) Let the installer modify the file, but confirm each modification before its
made.
3) Make their own modifications later on.
4) Open up install.txt (it would have been installed by that point), so they
can read about what's going on.
If they choose Option 4, they can then choose 1-3 once they've read what they
wanted to read.
> Q: are you leaving the user an after-install text file, detailing every step
> you
> took and every change you made. I've always found that rather helpful.
I had not considered doing that. Sort of like a LOG file, showing all
deletions, creations, etc.? Or just the modifications to autoexec.bat?
Since you mentioned the registry above, I should mention that, at least for
this version, there will be no modifications made to the registry at this
point. In future releases, I'd like to have the installer associate Euphoria
files with the interpreter for "Run" and the user's choice of editor for
"Open." (That's how mine's set up, anyway.) However, I will need to get much
more experience with the registry, or else I'll feel as nervous as a frog with
a glass ass.
I've also looked into shortcuts as well -- my idea was to provide shortcuts to
ed/ee, and Judith's IDE if installed, as well as the documentation. However,
I've looked at the API for creating links, as well as the file format, and I
fear that is also way over my head at this point.
One final point is that I'm planning on releasing an alpha which will install
Euphoria 2.2; however, since it appears the release of 2.3 is reasonably
imminent, I may hold off on releasing an "official" version until 2.3 is
released. In the interim, the beta can be tested repeatedly and every nook and
cranny can be poked, until the thing is right. After all, this program may be
the first experience people have with Euphoria. Unlike a certain other
organization (won't mention names but Washington state should ring a bell), I'm
embarrassed when my apps crash. 
Thanks for everyone's help in this,
Travis Beaty
Claude, Texas.
|
Not Categorized, Please Help
|
|
