Board index » delphi » Re: Program can not start in new WinXP

2003-08-29 06:05:59 AM
delphi245
Impossible to say without a precise error description.
"blow up" doesn't tell us anything.
--
Finn Tolderlund
"Dixon Epperson" <XXXX@XXXXX.COM>skrev i en meddelelse

Hi Dixon,
We had a similar problem where one of our programs did not pass its units'
initializations when started from a XP client. Starting from a Win2k client
was ok. At first, we suspected the XP policies. The customers' sysop forbid
a lot of services to the users. This may be a reason for your problem, too.
We gave the customer a version, where every unit logged its initialization
start and effort to a file.
This version worked! It seemed to be a timing problem or an order problem.
Changing the unit initialization order solved our problem.
best wishes, Achim.
Dixon Epperson writes:

Thanks Achim, that certainly makes sense, as it was erroring out in the
initialization of the exe. I uses packages to build and deploy, I wonder
if that is a contributing factor?
Here is what I discovered last night that was causing the problem,
though I am not sure, at all as to why.
The problem was solved when we turned hyperthreading on at the bios
level. I had turned it off, as I had heard that Firebird has problems with
hyperthreading and even though this is a client, I like to keep all my
machines as unified in their configurations as possible.
When we turned hyperthreading back on, it all worked. So it very well could
be a timing issue.
btw - blow up means the exe erred, tried to send an error report to Windows
and then shut down.
Dixon
"Achim Berg" <XXXX@XXXXX.COM>writes