InstallationRuntime 10
Herbert Lehmann
Hi, everyone!
I´m just changing from Runtime 8 to Vers. 10. Was used to Paradox
Distribution Expert which does not longer exist. In order to write
installation routines for my application I'm forced to use INNO-Setup now.
I'got no idea how to connect the installation of Runtime10 (which I have as
Pdx10Run.exe from the internet) to Inno-Setup: I need an option in Inno for
the Customer to say 'Yes, I want to install Runtime' or 'No, I have it
already'.
Any suggestion / solution is welcome
Herb
Debbie
I don't think asking a user whether or not they need Runtime installed (even
if you could do this with Inno) would work. How would they know? Most people
who are buying a custom App probably don't have Pdox or RT but they could
have someone else's custom app on their machine that did install RT or BDE.
Inno set up extensions, an addon for Inno (you can download this from a link
on the same site you got Inno setup) can allow you to detect from the
registry setting whether or not Pdox 10 or Pdox RT 10 exists on the machine.
Then you could do a "conditional" run command in the run section of Inno
based on whether Pdox was there and run the RT install exe. Using Inno
extensions however requires you to learn its scripting language (Pascal )
which for me was not that easy and while Inno also has a great newsgroup
they don't tend to give samples, just pointers on where to go look.
However, even if you master this and get Inno to choose to install the RT or
not, AFTER the install of the runtime is the only way you can create your
startup and or desktop icon commands to start Pdox. Inno needs to use HKLM
keys in the registry to determine location of the pdoxwin32.exe (full
Pdox)or pdoxrwn32.exe(RT) and then it can create the start menu or desktop
icon. You can of course add Pdox switches to control your app's opening or
set working and or private directories to this after you determine where
Pdox is.
The way we are doing it is with two Inno setups, one to install the app and
if necessary, RT. Then in the run section we run another Inno setup that
just creates the start menu and desktop icons for our app with switches.
This Inno is run silent with no start or finish page. This has to be run
AFTER RT is installed so that you know the registry keys exist. As a further
note of caution: if your app requires RT the Corel RT install will run in
the run section of the first Inno set up. If this is the first instance of
Pdox being installed on this machine the Wise Install (the program Corel
uses) will alert the user that a reboot is necessary. This will happen
before Inno gets to run the next setup to create the icons and start menu.
Most users will check OK when asked to reboot and if they do, the rest of
your install will not be run.
There really isn't a decent way to install a Pdox app with Runtime similar
to the way the PDE did it. The above method will start your own install in
Inno but then what appears to be right in the middle, the user will see a
totally different "Wise Install" Corel Paradox Runtime install and then when
its done the user will also now have a Wordperfect Office 2002 entry on
their start menu.
I have an Inno script that completely installs the BDE and Pdox runtime
including ALL the registry keys. It also adds the additional registry keys
required to get the table repair to work that the Corel RT install leaves
out and adds the two files and the "experts" directory in Paradox Runtime
for these as well. However, the BDE and RT license require you to use their
install. Its up to you, I can send the script to you if you want it. It is
well documented and all you would have to do is substitute your data and the
location of where it gets its files from and where you want to install to.
We use it internally so I am not that worried about the license issue but my
guess is you can't do this commercially.
Debbie
"Herbert Lehmann" <LSSLe...@t-online.de> wrote in message
news:3e219d93$1_1@cnews...
Ken Loomis
Debbie:
If you use the {pf} constant in Inno you can install your icons and RT
in one run. If you want to give your user a choice of drives you can
do that with the extensions and still do it in one run.
Ken
On Sun, 12 Jan 2003 13:56:22 -0600, "Debbie" <Mo...@sbcglobal.net>
wrote:
john mahan
I'm converting from PDOX 7 to PDOX 10 Runtime using PC-Install for
installation. Need to know all the programs to install and the registry
settings, etc because I control everything during the install. I've found
the FAQ for PDOX9 Runtime install using InstallShield... which is helpful.
Any other references?? THX, John
"Herbert Lehmann" <LSSLe...@t-online.de> wrote in message
news:3e219d93$1_1@cnews...
>
Debbie
Ken,
How can you do this? I know about the {pf} constant but how does this help
with creating the icon or start menu entry for the APP? Everything I have
seen in Inno tells me the only way to create the icon or start menu for a
Pdox app is to use the {reg} constant to locate where Pdox or RT programs
is located followed by the correct .exe file. So unless RT or full Pdox is
already on the machine don't you have to use the Corel RT install in the
"run" section of Inno? As Inno creates the icons and start menu before the
"run" section, how can you do this? I know it is very easy to do if you
create your own install for the Pdox RT instead of using Corel's but then
isn't there a license issue?
When I say I use another Inno set up .exe I mean I run in the "run" section.
It is not really even visible to the user. Have you found a way to use the
Corel RT install in Inno that the user doesn't see and that also will not
give the re-boot screen?
Debbie
"Ken Loomis" <klo...@it-resourcesREMOVETHECAPS.com> wrote in message
news:m5v32vgi0f5eql3pe...@4ax.com...
wrote:
Ken Loomis
Debbie:
I have not installed P10 via Inno, only P9; however, I assume that the
P10 runtime install puts the runtime in the same place under Program
Files with its long Corel.. etc. path. Hence you can use {pf} and the
path in your icon. Now, I suppose there could have been a prior
Paradox install in a non-standard place, and I don't know if you'd
want to go with it. Do you want to upgrade someone elses Pdox? I can't
answer that. In any case, if you want to put it in a non-standard
place you can use the Inno Extensions to do that. There's a current
thread in the Inno newsgroup on that.
Out of curiosity, why would you enable a user to put PDOX in a
non-default place? If you want to put it on another drive, which is
the only option I can see reasonable to give, you can use the
extensions for that, too.
On Mon, 13 Jan 2003 05:09:24 -0600, "Debbie" <Mo...@sbcglobal.net>
wrote:
Ken Loomis
search for install threads here and at pnews.
Ken
On Sun, 12 Jan 2003 21:00:20 -0800, "john mahan" <john....@isg.com>
wrote:
Debbie
Ken:
1) Your suggestion would work even if the RT is installed in the "run"
section after the icons and startup are created but what if the user chooses
to install RT in another place other than the default? I don't have the P9
RT but the P10 version allows the user to choose the complete destination
(drive and directory) for both the {pf} files and the {cf} files so if you
create the icon and start menu with the assumption the user put it in its
default {pf} and they don't, what happens then?
2) If I use Corel's RT install I can't control where the user puts it. I am
not enabling them to do it, the RT install is.
3) All this would work fine if I could incorporate the RT files, BDE files,
and both reg. entries directly in my Inno install but don't you have to use
the complete RT.exe?
Debbie
"Ken Loomis" <klo...@it-resourcesREMOVETHECAPS.com> wrote in message
news:kl652v04ia6uev2mb...@4ax.com...
Tony McGuire
Doesn't Inno allow you to get user input as to 'destination to install'?
Then, can't you pass this to the RT 10 install and do a 'silent install' as
Dan A recommended?
As to files to install, as well as registry changes, it has been made plain
that Corel isn't going to publish all the gory details. Too much/many
parameters (integration with the rest of the WPO suite), and then they'd
probably wind up trying to support every favorite installer out there (or
that'd be the expectation of some users).
--
--
<brag>Liz 'The Goddess of Paradox' and I are marrying January 18th!</brag>
Tony
"I woke up and was able to get myself out of bed.
Being that fortunate, what's to complain about?"
_____________
Debbie
I never saw anything from Dan A. concerning a RT install, where was this
posted?
I know you can use the {app} constant which is where the user chooses to
install the app but how would you pass this to the RT.exe in Inno? I saw in
the Inno newsgroup where there was utility program to enter keys
automatically during the install so you could keep a silent install silent.
If there is some way to pass this {app} variable to the RT install in the
"run" section of Inno than that would solve all the problems. The {cf}
portions could go where they belong and the Paradox portions could be
installed right in the APP directory. You would be sure where the pdox.exe
is and could create the Icon and start menu before RT is installed. Anybody
know how to pass this variable to the RT install?
As to the registry details I think I have them. I did a RT install on a
Win9x and NT machine then searched the reg for all Corel and Borland entries
and exported these. I made an Inno install from these and the Pdox RT and
Borland files and it works fine on Win9x and NT. The only reg entry I didn't
add and the one I think may cause the "reboot?" is the one that creates the
BDE admin icon in the control panel. Unfortunately you can't use this type
of install and stay within the Corel License.
Debbie
"Tony McGuire" <to...@paradoxcommunity.com> wrote in message
news:3e22bd85_2@cnews...
Robert Emmons
Ken Loomis <klo...@it-resourcesREMOVETHECAPS.com> wrote:
>Out of curiosity, why would you enable a user to put PDOX in a
>non-default place? If you want to put it on another drive, which is
>the only option I can see reasonable to give, you can use the
>extensions for that, too.
Why does the Paradox 10 Runtime installer allow the user to install it
in a non- default location? Why does almost every installer of every
commercial software allow the user to install in a non-default
location? Becasue it is impossible to predict what a user might want
to do in every instance for the life of your software program.
----------------------------------------------------
Robert Emmons, Aurigen Inc.
rem...@aurigen.com, http://www.aurigen.com
Computer Programming and Consulting
Robert Emmons
"Debbie" <Mo...@sbcglobal.net> wrote:
>I don't think asking a user whether or not they need Runtime installed (even
>if you could do this with Inno) would work. How would they know? Most people
>who are buying a custom App probably don't have Pdox or RT but they could
>have someone else's custom app on their machine that did install RT or BDE.
>
>
I think you are doing the install exacty right. You have to install
RT first, and read the registry key to be sure you know where the user
installed Runtime.
We use a similar procedure. Our installation CD auto-launches a
standard Windows Help file which opens with a screen that shows the
installation instructions, and two command buttons:
* Install 1st: Paradox 10 Runtime
* Install 2nd Our Application
Your procedure of running the RT installer 1st automatically seems
similar. I just like the user to know exactly what is happening at
all times. Of course, this means he has more to do, and can become
more confused. There are trade offs between your method, and ours.
Ken Loomis
OK, so you're saying that the pdox10 runtime exe has built-in a user
option for RT's location, right. I haven't done it, but the Inno
newsgroups suggests InstallReady will do the trick. I belive it's in
the extension, but I'm not sure. Did you check the thread over there?
Ken
On Mon, 13 Jan 2003 07:01:42 -0600, "Debbie" <Mo...@sbcglobal.net>
wrote: