question about PDW

[Eduardo]

Is there any reason to keep running the setup.exe after it launched the
setup1.exe?

[Deanna Earley]

On 10/05/2013 15:32, Eduardo wrote:
> Is there any reason to keep running the setup.exe after it launched the
> setup1.exe?

What's the context for this? What are you going to do (or not do)
depending on the answer?
Normally it's good practice to keep the wrapper process running until
its children have finished so it can be waited on easier.
If it exits then anything waiting on it needs to create a job object to
wait for the rest of the setup to finish and is generally a pain in the ass.
(this comes under the umbrella of "software taxes")

--
Deanna Earley (dee.e...@icode.co.uk)
iCatcher Development Team
http://www.icode.co.uk/icatcher/

iCode Systems

(Replies direct to my email address will be ignored. Please reply to the
group.)

[Eduardo]

"Deanna Earley" <dee.e...@icode.co.uk> escribió en el mensaje
news:kmj1ma$b75$1...@speranza.aioe.org...

> On 10/05/2013 15:32, Eduardo wrote:
>> Is there any reason to keep running the setup.exe after it launched the
>> setup1.exe?
>
> What's the context for this? What are you going to do (or not do)
> depending on the answer?

The context is intalling a VB application with the VB installer.

And the context is that setup.exe is eating 99% of the CPU cycles for
doing... żnothing?

My specific concern is: is there any cleanup or something that this process
must do at the end?

[Deanna Earley]

On 10/05/2013 16:06, Eduardo wrote:
> "Deanna Earley" <dee.e...@icode.co.uk> escribió en el mensaje
> news:kmj1ma$b75$1...@speranza.aioe.org...
>> On 10/05/2013 15:32, Eduardo wrote:
>>> Is there any reason to keep running the setup.exe after it launched the
>>> setup1.exe?
>>
>> What's the context for this? What are you going to do (or not do)
>> depending on the answer?
>
> The context is intalling a VB application with the VB installer.
>
> And the context is that setup.exe is eating 99% of the CPU cycles for

> doing... ¿nothing?

So... you're going to arbitrarily kill the process from setup1.exe?
I've not seen that before, maybe it's actually doing something.

> My specific concern is: is there any cleanup or something that this process
> must do at the end?

No idea, I gave up on PDW ~10 years ago for being inflexible (out of the
box) and a pita on any recent version of Windows.

[ObiWan]

> No idea, I gave up on PDW ~10 years ago for being inflexible (out of
> the box) and a pita on any recent version of Windows.

same here; and a quick and "drop in" replacement for the regular VB6
pdw is the InnoSetup package http://www.jrsoftware.org/isinfo.php the
app is able to import a VB6 setup "profile" and convert it into an IS
setup package so, (re)building a setup is almost a breeze; not just
that, it also supports a whole lot of additional features which, imHo
make it the perfect candidate for anyone seeking a good setup app; in
case someone here didn't know about it and wants to give it a spin, my
suggestion is to pick the so-called "quickstart pack"

http://www.jrsoftware.org/isdl.php

which includes the barebone setup engine and the GUI/Wizard along with
some "need to have" additions (then ok, if desired you may add it the
encryption module and then some more stuff, but the quickstart carries
pretty much all you'll need to get started)

[Eduardo]

"Deanna Earley" <dee.e...@icode.co.uk> escribi� en el mensaje
news:kmj4hj$k3r$1...@speranza.aioe.org...

> On 10/05/2013 16:06, Eduardo wrote:

>> "Deanna Earley" <dee.e...@icode.co.uk> escribi� en el mensaje

>> news:kmj1ma$b75$1...@speranza.aioe.org...
>>> On 10/05/2013 15:32, Eduardo wrote:
>>>> Is there any reason to keep running the setup.exe after it launched the
>>>> setup1.exe?
>>>
>>> What's the context for this? What are you going to do (or not do)
>>> depending on the answer?
>>
>> The context is intalling a VB application with the VB installer.
>>
>> And the context is that setup.exe is eating 99% of the CPU cycles for
>> doing... �nothing?
>
> So... you're going to arbitrarily kill the process from setup1.exe?
> I've not seen that before, maybe it's actually doing something.

I already did.

>> My specific concern is: is there any cleanup or something that this
>> process
>> must do at the end?
>
> No idea, I gave up on PDW ~10 years ago for being inflexible (out of the
> box) and a pita on any recent version of Windows.

Well, in my own version I've made lot of improvements on it.

[ralph]

On Fri, 10 May 2013 12:06:14 -0300, "Eduardo" <m...@mm.com> wrote:

>
>"Deanna Earley" <dee.e...@icode.co.uk> escribi� en el mensaje

>news:kmj1ma$b75$1...@speranza.aioe.org...
>> On 10/05/2013 15:32, Eduardo wrote:
>>> Is there any reason to keep running the setup.exe after it launched the
>>> setup1.exe?
>>
>> What's the context for this? What are you going to do (or not do)
>> depending on the answer?
>
>The context is intalling a VB application with the VB installer.
>
>And the context is that setup.exe is eating 99% of the CPU cycles for

>doing... �nothing?

>
>My specific concern is: is there any cleanup or something that this process
>must do at the end?
>

I don't know off-hand, but I'd assume it does.

You can find out soon enough yourself. Download the SysInternal tools.
http://technet.microsoft.com/en-us/sysinternals/bb842062
Between the ProcessExplorer (a better task manager) and the others you
can grok it all out on your own.

But to more or less to ask the same question as Deanna - Why would you
even care?

Never read too much into CPU% unless there is a definite problem -
even then take it as a possible *indicator* of where you might start
looking - with OTHER tools.

-ralph

[Eduardo]

"ralph" <nt_con...@yahoo.com> escribi� en el mensaje
news:tg5qo856m8uk997v7...@4ax.com...

There is a definite problem: with an old one core machine it takes several
minutes to install a font when setup.exe is running and it does it in a few
seconds when it's not.

[ObiWan]

> Well, in my own version I've made lot of improvements on it.

here ya go, you just found the origin of the issue, "your own version",
now since we don't have the code, I think you'll need to find the cause
of your issue by yourself <g>

[ObiWan]

<hint>
add some logging logic to the code (to whatever logfile and/or to the
"outputdebugstring" API) and run the setup on a problem box and you'll
be able to find "where it hangs" and possibly solve the issue

[ralph]

On Fri, 10 May 2013 13:29:53 -0300, "Eduardo" <m...@mm.com> wrote:


>>
>> Never read too much into CPU% unless there is a definite problem -
>> even then take it as a possible *indicator* of where you might start
>> looking - with OTHER tools.
>
>There is a definite problem: with an old one core machine it takes several
>minutes to install a font when setup.exe is running and it does it in a few
>seconds when it's not.
>

That seems odd.

Throw-in one or two strategic DoEvents() to force a clearing of the
message queques and see what happens.

-ralph

[Eduardo]

"ObiWan" <alb.20.t...@spamgourmet.com> escribi� en el mensaje
news:20130510183...@deathstar.mil...

LOL! The problem has nothing to do with my improvements, and I already
posted the code related to the issue (and what issue are you talking about
BTW?)

[Eduardo]

"ObiWan" <alb.20.t...@spamgourmet.com> escribi� en el mensaje
news:20130510183...@deathstar.mil...

It hangs because it always hanged, it seems that it was designed to hang
(99% of hanging 1% of work) so in 1998 the people could not do anything but
wait that the setup finished.

[Eduardo]

"Eduardo" <m...@mm.com> escribi� en el mensaje
news:kmj79q$uh4$1...@speranza.aioe.org...

It seems that in fact it cleans temporary files that now are left.

[Eduardo]

"ralph" <nt_con...@yahoo.com> escribi� en el mensaje

news:ue9qo8ttpf12qts93...@4ax.com...

But I can't modify that exe, it's not VB (it's the setup.exe not the
setup1.exe)

[ralph]

Ha.

I was talking about setup1.

[Mayayana]

I've posted this before, but it might be of some use:

http://www.jsware.net/jsware/vbcode.php5

There are 2 versions of PDW there. One is cleaned
up and updated. The other does away with setup.exe
altogether. I think the notes in the download explain
it. It's a very odd arrangement. Setup.exe does a handful
of things, including moving setup1.exe into C:\Windows (?!)
and then starts setup1 .exe. It should be quitting at that
point. Either way, if you take care of what setup.exe
does in your own code you can drop it altogether. The
only reason it was ever needed was to install the runtime
and reboot. That's no longer relevant.

[CoderX]

"Eduardo" <m...@mm.com> wrote in message
news:kmj0cr$7te$1...@speranza.aioe.org...

> Is there any reason to keep running the setup.exe after it launched the
> setup1.exe?

Or, and I'm just throwing this out there...get rid of the crappy PDW and use
Inno like everyone else. For the features and the price, nothing else comes
close.

[Eduardo]

"CoderX" <co...@x.com> escribi� en el mensaje
news:kmkanq$c9r$1...@dont-email.me...

It is a possibility, but I don't have much time now to learn how to use a
new installer.

In my version of setup1, I added several features:

1) To upgrade a previous version if the same program is already installed.
2) To reinstall if the version installed of the program is the same (more or
less the same as 1), but changing the caption of a button from "Upgrade" to
"Reinstall")
1 and 2 uninstall a previous version silently before installing the program
again.
3) Set permissions to folders that will or can be used for data storage.
4) Prompt to close the program before uninstalling if it's running (also
switching to the main window of the program).
5) Prompt to close other programs if they have a file in use that need to be
updated by the installer (for example a .doc opened in Word), and switch to
the main window of that program.
6) Terminating the process if the program to reinstall is running but not
responding.
7) New and better looking uninstaller that wraps the older one and hide its
ugly windows.
8) Better looking GUI, not covering all the screen.
9) Tell the user if the files to be updated are opened by other users
sessions on the machine.

[Eduardo]

"Mayayana" <maya...@invalid.nospam> escribió en el mensaje
news:kmjt84$k32$1...@dont-email.me...

Thanks Mayayana. Reading your "setup1 noSE directions.html" I got some
insights.

I was also able to fix and couple of bugs in my version of setup1, one was
the owNo meaning "Yes" or in any case "Don't Keep" (because I wrote code to
automatically handle what to do without asking the user), and other is the
fix of the SourceFileIsNewer function.

[Mayayana]

--
--
"CoderX" <co...@x.com> wrote in message news:kmkanq$c9r$1...@dont-email.me...

The code is all there, so it's really an issue similar
to that of using a control vs straight code. The PDW
is whatever you want it to be. I like it for that aspect.
I can design a custom GUI and customize install details
for each program. Inno is dependable...and boring. If
I were doing something like a very complex installer
for use in large businesses then Inno might seem a good
idea. One gets the advantage of someone else who
works doggedly to keep it up to date. But my own
software is usually pretty much self-contained. And it
doesn't need to accomodate things like multiple, scripted
installations across a network. An updated PDW can easily
take care of typical requirements like shortcuts, Registry
entries, user-app-data folder creation, etc.

[Mayayana]

| I was also able to fix and couple of bugs in my version of setup1, one was
| the owNo meaning "Yes" or in any case "Don't Keep" (because I wrote code
to
| automatically handle what to do without asking the user), and other is the
| fix of the SourceFileIsNewer function.
|

Don't you love that? I can never figure out whether
the Microsofties are of such middling intelligence that
they can't help producing superfluous complexity and
then tripping over it ...or whether they're so brilliant that
they produce quadruple negatives in their code out of
boredom, just to add some challenge and intimidate
the rest of us; like an eccentric, undersexed geek who
likes to write his supermarket shopping list backward, in
Greek, in a naive and sadly doomed effort to flirt with
The Ladies of Safeway. :)

[Eduardo]

"Mayayana" <maya...@invalid.nospam> escribi� en el mensaje
news:kmldpb$tsa$1...@dont-email.me...

I see that different programmers have different ways to code.

For example some use short variable names, I prefer descriptive ones, as
long as necessary.
Some like to use the VB word "With" (With Combo1 .ListIndex), but I do
not use it in the code I write.
I like to have an indentation of 4, but I see that others use 2 spaces (or
even 1).
And there are many more examples.
I can't criticize what other like, I just can say that I prefer something
else.

Perhaps in this particular case the code can be criticized because it was
something intended to be reused by millions of people. And in that case,
yes, it's ugly (but I'm already used to it).

[Deanna Earley]

On 10/05/2013 17:58, Eduardo wrote:
> It seems that in fact it cleans temporary files that now are left.

Hence it's need to wait.

Maybe it's just not modern OS compatible (not surprising) and doesn't
wait correctly on the sub process handle.

[Deanna Earley]

On 11/05/2013 04:03, Eduardo wrote:
> "CoderX" <co...@x.com> escribió en el mensaje

> news:kmkanq$c9r$1...@dont-email.me...
>>
>> "Eduardo" <m...@mm.com> wrote in message
>> news:kmj0cr$7te$1...@speranza.aioe.org...
>>> Is there any reason to keep running the setup.exe after it launched the
>>> setup1.exe?
>>
>> Or, and I'm just throwing this out there...get rid of the crappy PDW and
>> use Inno like everyone else. For the features and the price, nothing else
>> comes close.
>
> It is a possibility, but I don't have much time now to learn how to use a
> new installer.
>
> In my version of setup1, I added several features:
>
> 1) To upgrade a previous version if the same program is already installed.

Inno does this out the box with no effort.

> 2) To reinstall if the version installed of the program is the same (more or
> less the same as 1), but changing the caption of a button from "Upgrade" to
> "Reinstall")

Reinstall is fine, changing the caption is a single line of code.

> 1 and 2 uninstall a previous version silently before installing the program
> again.

There is no need for this in the vast majority of cases.
Any orphaned/old files can be deleted on install, or just left until
uninstall time.

> 3) Set permissions to folders that will or can be used for data storage.

Easy, Permissions: everyone-all

> 4) Prompt to close the program before uninstalling if it's running

Done as part of the Restart Manager support, or a simple mutex check.

> (also switching to the main window of the program).

Easy enough with a few lines of code.

> 5) Prompt to close other programs if they have a file in use that need to be
> updated by the installer (for example a .doc opened in Word), and switch to
> the main window of that program.

Again, part of the restart manager support/mutex check.

> 6) Terminating the process if the program to reinstall is running but not
> responding.

Never a good idea to do automatically, Inno leaves it to the user or
recommends a reboot.

> 7) New and better looking uninstaller that wraps the older one and hide its
> ugly windows.
> 8) Better looking GUI, not covering all the screen.

No need, Inno looks hotter than all others :p
And full screen setups went out of fashion with PDW :p

> 9) Tell the user if the files to be updated are opened by other users
> sessions on the machine.

Again, same as 4 and 5.

Oh, and the font installation works.

Just give it a go :)

[Eduardo]

"Deanna Earley" <dee.e...@icode.co.uk> escribi� en el mensaje
news:kmqe9m$k3o$1...@speranza.aioe.org...

> On 11/05/2013 04:03, Eduardo wrote:

>> "CoderX" <co...@x.com> escribi� en el mensaje

>> news:kmkanq$c9r$1...@dont-email.me...
>>>
>>> "Eduardo" <m...@mm.com> wrote in message
>>> news:kmj0cr$7te$1...@speranza.aioe.org...
>>>> Is there any reason to keep running the setup.exe after it launched the
>>>> setup1.exe?
>>>
>>> Or, and I'm just throwing this out there...get rid of the crappy PDW and
>>> use Inno like everyone else. For the features and the price, nothing
>>> else
>>> comes close.
>>
>> It is a possibility, but I don't have much time now to learn how to use a
>> new installer.
>>
>> In my version of setup1, I added several features:
>>
>> 1) To upgrade a previous version if the same program is already
>> installed.
>
> Inno does this out the box with no effort.

I already have it made, so I do it also "out the box" with no effort.
But my installer have a better looking GUI (and more personality) that the
serially used Inno.

>
>> 2) To reinstall if the version installed of the program is the same (more
>> or
>> less the same as 1), but changing the caption of a button from "Upgrade"
>> to
>> "Reinstall")
>
> Reinstall is fine, changing the caption is a single line of code.

Yes, you are right, I don't understand how you have figured it.

Also another line of code for a label to tell the user that if he/she
intended to run the program, he/she must exit the installer and look for it
in the programs shortcuts.
(I guess that Inno, as a serious installer must do that also)

>
>> 1 and 2 uninstall a previous version silently before installing the
>> program
>> again.
>
> There is no need for this in the vast majority of cases.
> Any orphaned/old files can be deleted on install, or just left until
> uninstall time.

For me it was easier to do that in that way, and works just fine.

>
>> 3) Set permissions to folders that will or can be used for data storage.
>
> Easy, Permissions: everyone-all

May be it's easy with and installer (like Inno, Mayayana's one or mine), but
it's not so easy if you don't know hw to do it or don't have a class with
all the code to do that.

>
>> 4) Prompt to close the program before uninstalling if it's running
>
> Done as part of the Restart Manager support, or a simple mutex check.

Do you have an own installer that does that????

>
>> (also switching to the main window of the program).
>
> Easy enough with a few lines of code.

All are lines of code, of course.
And of course everything is easy... if you know.

But, in fact, I have to say that's not so easy to do it properly, do you
want me to explain what could be the problems if you don't take case of some
situations?

>
>> 5) Prompt to close other programs if they have a file in use that need to
>> be
>> updated by the installer (for example a .doc opened in Word), and switch
>> to
>> the main window of that program.
>
> Again, part of the restart manager support/mutex check.

I'm not sure what are you talking about.
My code works with programs that are not services, and in Windows before
Vista.

>
>> 6) Terminating the process if the program to reinstall is running but not
>> responding.
>
> Never a good idea to do automatically, Inno leaves it to the user or
> recommends a reboot.

Yes, I prompt the user to click a button.

>
>> 7) New and better looking uninstaller that wraps the older one and hide
>> its
>> ugly windows.
>> 8) Better looking GUI, not covering all the screen.
>
> No need, Inno looks hotter than all others :p
> And full screen setups went out of fashion with PDW :p

I see it very standard (may be there is a new version that I don't know).
Also, every installer looks more or less the same, they are clones.

>
>> 9) Tell the user if the files to be updated are opened by other users
>> sessions on the machine.
>
> Again, same as 4 and 5.
>
> Oh, and the font installation works.

Mine too now.

>
> Just give it a go :)

I don't need to spend time on it at this time (and I prefer mine).

Mine has also another advantage: I create the package with VB PDW, and the
only change is to change the setup1.exe, that if it's copied in the VB
folder, it's automatic.

[Eduardo]

"Deanna Earley" <dee.e...@icode.co.uk> escribi� en el mensaje

news:kmqdtj$i5t$1...@speranza.aioe.org...

> On 10/05/2013 17:58, Eduardo wrote:
>> It seems that in fact it cleans temporary files that now are left.
>
> Hence it's need to wait.
>
> Maybe it's just not modern OS compatible (not surprising) and doesn't wait
> correctly on the sub process handle.

I think I was wrong, they were some other files.

[Deanna Earley]

On 13/05/2013 11:46, Eduardo wrote:
> "Deanna Earley" <dee.e...@icode.co.uk> escribió en el mensaje

> news:kmqe9m$k3o$1...@speranza.aioe.org...
>> On 11/05/2013 04:03, Eduardo wrote:
>>> 2) To reinstall if the version installed of the program is the
>>> same (more or less the same as 1), but changing the caption of a
>>> button from "Upgrade" to "Reinstall")
>>
>> Reinstall is fine, changing the caption is a single line of code.
>
> Yes, you are right, I don't understand how you have figured it.
>
> Also another line of code for a label to tell the user that if he/she
> intended to run the program, he/she must exit the installer and look for it
> in the programs shortcuts.
> (I guess that Inno, as a serious installer must do that also)

No need, it just has a "Run" option. After all, it knows what it's just
installed.

>>> 3) Set permissions to folders that will or can be used for data storage.
>>
>> Easy, Permissions: everyone-all
>
> May be it's easy with and installer (like Inno, Mayayana's one or mine), but
> it's not so easy if you don't know hw to do it or don't have a class with
> all the code to do that.

Glad you agree.

>>> 4) Prompt to close the program before uninstalling if it's running
>>
>> Done as part of the Restart Manager support, or a simple mutex check.
>
> Do you have an own installer that does that????

I don't do the mutex check, I rely on Restart Manager to detect them
running.
(with a fix to stop my app locking up in the VB6 runtime with the
Restart Manager)

> But, in fact, I have to say that's not so easy to do it properly, do you
> want me to explain what could be the problems if you don't take case of some
> situations?

What are you talking about now?
Oh, and no need to tell me how to "do it properly" as I'm evil already.

>>> 5) Prompt to close other programs if they have a file in use that
>>> need to be updated by the installer (for example a .doc opened in
>>> Word), and switch to the main window of that program.
>>
>> Again, part of the restart manager support/mutex check.
>
> I'm not sure what are you talking about.

5 and 4 were the same feature. The Restart Manager picks up on both
cases in the same way.

> My code works with programs that are not services, and in Windows before
> Vista.

Fair enough.

>>> 7) New and better looking uninstaller that wraps the older one
>>> and hide its ugly windows.
>>> 8) Better looking GUI, not covering all the screen.
>>
>> No need, Inno looks hotter than all others :p
>> And full screen setups went out of fashion with PDW :p
>
> I see it very standard (may be there is a new version that I don't know).
> Also, every installer looks more or less the same, they are clones.

Yes, users expect things to look familiar. There are UI development
guidelines for a reason.

> Mine has also another advantage: I create the package with VB PDW, and the
> only change is to change the setup1.exe, that if it's copied in the VB
> folder, it's automatic.

#include "blah.isi"

[Eduardo]

"Deanna Earley" <dee.e...@icode.co.uk> escribi� en el mensaje

news:kmqlnq$c1n$1...@speranza.aioe.org...

> On 13/05/2013 11:46, Eduardo wrote:

>> "Deanna Earley" <dee.e...@icode.co.uk> escribi� en el mensaje
>> news:kmqe9m$k3o$1...@speranza.aioe.org...

Ok, tell me what you wan't me to do with my installers so you can be happy.

[ObiWan]

> 1) To upgrade a previous version if the same program is already
> installed.

comes by default with inno, it even allows to create "patch setups"
which will only run if a previous version of the app is installed and
which will just "patch" it as desired

> 2) To reinstall if the version installed of the program is
> the same (more or less the same as 1), but changing the caption of a
> button from "Upgrade" to "Reinstall")

not a problem with inno

> 1 and 2 uninstall a previous version silently before installing the
> program again.

no need, inno does that and then some more

> 3) Set permissions to folders that will or can be used for data
> storage. 4) Prompt to close the program before uninstalling if it's
> running (also switching to the main window of the program).

ditto, inno handles that

> 5) Prompt to close other programs if they have a file in use that
> need to be updated by the installer (for example a .doc opened in
> Word), and switch to the main window of that program.

easy with inno

> 6) Terminating the process if the program to reinstall is running but
> not responding.

same as above

> 7) New and better looking uninstaller that wraps the older one and
> hide its ugly windows.

inno has a "regular" setup and uninstaller as well; not only that, if
you want you'll be able to configure the uninstall step to leave the
user settings in place or remove them

> 8) Better looking GUI, not covering all the screen.

inno had that for eons

> 9) Tell the user if the files to be updated are opened by other users
> sessions on the machine.

easy with inno

plus: you have a bunch of other goodies, like the ability to download
missing bits from the internet, of installing libs/files based on the
OS version, to add your own dialogs (e.g. to enter registration infos
or whatever else) and then some more; also, and I already wrote it,
inno can directly import a regular PDW setup config file and turn it
into a basic inno setup project, so converting an existing setup to an
inno one is really easy

what are you waiting ?

[ObiWan]

> > <hint>
> > add some logging logic to the code (to whatever logfile and/or to
> > the "outputdebugstring" API) and run the setup on a problem box and
> > you'll be able to find "where it hangs" and possibly solve the issue

> It hangs because it always hanged

so, if you already knew this, why are you asking here ?

[Deanna Earley]

On 13/05/2013 14:00, Eduardo wrote:
> "Deanna Earley" <dee.e...@icode.co.uk> escribió en el mensaje

> news:kmqlnq$c1n$1...@speranza.aioe.org...
>> On 13/05/2013 11:46, Eduardo wrote:

>>> "Deanna Earley" <dee.e...@icode.co.uk> escribió en el mensaje

>>> news:kmqe9m$k3o$1...@speranza.aioe.org...
>
> Ok, tell me what you wan't me to do with my installers so you can be happy.

You don't have to do anything, as long as you're happy.
Obviously if you have problems with your system, them you know what the
options are.

(If only these applied to religion :)

[ralph]

I doubt very much Setup is "hung" in any meaningful way. The Task
Manager is simply showing that it has a token to run. Any bottlenecks
or performance issues are entirely related to your code in Setup1. You
are chasing a red herring.

-ralph

[Eduardo]

"Deanna Earley" <dee.e...@icode.co.uk> escribió en el mensaje

news:kmqt79$52l$1...@speranza.aioe.org...

> On 13/05/2013 14:00, Eduardo wrote:
>> "Deanna Earley" <dee.e...@icode.co.uk> escribió en el mensaje
>> news:kmqlnq$c1n$1...@speranza.aioe.org...
>>> On 13/05/2013 11:46, Eduardo wrote:
>>>> "Deanna Earley" <dee.e...@icode.co.uk> escribió en el mensaje
>>>> news:kmqe9m$k3o$1...@speranza.aioe.org...
>>
>> Ok, tell me what you wan't me to do with my installers so you can be
>> happy.

> You don't have to do anything, as long as you're happy.
> Obviously if you have problems with your system, them you know what the
> options are.

I have no problems.

[Eduardo]

"ObiWan" <alb.20.t...@spamgourmet.com> escribió en el mensaje
news:20130513162...@deathstar.mil...

Asking what? I didn't ask about any hanging issue.

[Eduardo]

"ralph" <nt_con...@yahoo.com> escribi� en el mensaje
news:npv1p89j43ptvqv8h...@4ax.com...

I don't think so. If I kill it, the setup1 process goes much faster.

BTW, the particular task that took too long time (with setup.exe running)
was the code to register fonts with Olaf's code using some system script.
(may be also combined with the antivirus and the "defense" program, and of
course, in an old one core machine).

[Eduardo]

"ObiWan" <alb.20.t...@spamgourmet.com> escribi� en el mensaje
news:20130513162...@deathstar.mil...

[Inno, Inno... Inno]

But I never said that Inno didn't do that.

I answered to CoderX when he said:

"get rid of the crappy PDW"

and I explained that it wasn't the original PWD, that I have added some
features that I wanted and that I changed/fixed some crappy things of the
original one.

> what are you waiting ?

One thing is that I no have time now to try something new and that I didn't
find a problem that I couldn't fix.