| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3068.1 | could i have some help, please? | BLAZER::MIKELIS | Software Partner's Eng. MR01-3/F26 | Fri Jul 19 1996 16:07 | 7 |
| 3068.2 | | PEACHS::GHEFF | http://tuvok.alf.dec.com/excursion | Fri Jul 19 1996 17:11 | 8 |
| 3068.3 | | LJSRV1::RICH | warped and scared | Fri Jul 19 1996 17:14 | 21 |
| 3068.4 | | PEACHS::GHEFF | http://tuvok.alf.dec.com/excursion | Fri Jul 19 1996 17:17 | 3 |
| 3068.5 | | PEACHS::GHEFF | http://tuvok.alf.dec.com/excursion | Mon Jul 22 1996 14:29 | 4 |
| 3068.6 | do you have one eye closed? :-) | LJSRV1::RICH | warped and scared | Mon Jul 22 1996 15:11 | 4 |
| 3068.7 | | PEACHS::GHEFF | http://tuvok.alf.dec.com/excursion | Mon Jul 22 1996 17:04 | 22 |
| 3068.8 | | LJSRV1::RICH | warped and scared | Mon Jul 22 1996 17:36 | 7 |
| 3068.9 | | BLAZER::MIKELIS | Software Partner's Eng. MR01-3/F26 | Mon Jul 22 1996 18:07 | 7 |
| 3068.10 | | PEACHS::GHEFF | http://tuvok.alf.dec.com/excursion | Mon Jul 22 1996 18:20 | 10 |
| 3068.11 | | PEACHS::GHEFF | http://tuvok.alf.dec.com/excursion | Tue Jul 23 1996 17:06 | 14 |
| 3068.12 | | CRONIC::LEMONS | And we thank you for your support. | Thu Feb 20 1997 17:21 | 12 |
| Hi
I'm intrigued by .3, and how SETUP.EXE works in the eXcursion kit.
SETUP.EXE runs on both Intel and Alpha hardware, tests the hardware
type, and handles control over to a hardware-specific XSETUP.EXE in a
specific-to-the-hardware subdirectory of the kit. I had thought that a
single executable image could not run on both Intel and Alpha (barring
FX!32). What's special about eXcursion's SETUP.EXE that allows this to
happen?
Thanks!
tl
|
| 3068.13 | | TARKIN::LIN | Bill Lin | Thu Feb 20 1997 17:29 | 8 |
| re: .12 by CRONIC::LEMONS
>> What's special about eXcursion's SETUP.EXE that allows this to
>> happen?
I have no idea, but maybe it is 16-bit code?
/Bill
|
| 3068.14 | | PEACHS::GHEFF | Got a head with wings | Thu Feb 20 1997 17:51 | 4 |
| I thought it was a 16-bit 286 binary. Which would allow it to run
anywhere.
#Gary
|
| 3068.15 | | CRONIC::LEMONS | And we thank you for your support. | Fri Feb 21 1997 09:37 | 10 |
| Egad. Thanks. How does one create such a beast? I have a similar
need (to install a single kit on several hardware platforms). I think
I have the choice of creating a 16-bit 286 binary, or writing a
INSTALL.BAT. Of the two, the SETUP.EXE seems more elegant, but the
INSTALL.BAT seems simpler.
Thoughts?
Thanks!
tl
|
| 3068.16 | | LJSRV1::GULDENSCHUH | | Sat Feb 22 1997 09:13 | 9 |
| INSTALL.BAT can be easier IF you have all the environment variables
available. The original version of SETUP ran on Intel, Alpha, and
MIPS, under Windows, Windows95, and Windows NT. While I don't
remember which variables were missing where, it just wasn't
possible to figure out what to do in all cases. If the product is
limited to NT, I thing you can do it easily enough with a .BAT
file.
/s/ Chuck
|
| 3068.17 | | CRONIC::LEMONS | And we thank you for your support. | Mon Feb 24 1997 13:51 | 5 |
| thanks for the reply. As I would like this install to run on Windows
95, I'd like to pursue the SETUP.EXE idea. How did you create it?
Thanks!
tl
|