PDA

View Full Version : Program has incurred a problem



NewsArchive
10-22-2008, 01:30 AM
I have a problem with one installation. After install and when the program
is run, a windows box pops up stating that the program has incurred a
problem and needs to close. If they click on program the program gains
focus and runs ok. If they click on the ok button of the windows error box,
then the program aborts.

I have this program installed at many different locations and have never had
this occur. They are running XP Pro. Has anyone ever had this happen.

Don Harvey

NewsArchive
10-22-2008, 01:31 AM
Don,

> I have a problem with one installation. After install and when the
> program is run, a windows box pops up stating that the program has
> incurred a problem and needs to close. If they click on program the
> program gains focus and runs ok. If they click on the ok button of the
> windows error box, then the program aborts.
>
> I have this program installed at many different locations and have never
> had this occur. They are running XP Pro. Has anyone ever had this
> happen.

Yes, seems to be a typical "default directory" problem. Something like the
following: your program assumes that the current folder is the application
folder (not a good idea) and uses this folder to, say, load configuration
settings, load a database, etc.. But you forgot to set the correct default
directory when you start your application from the installer and so your
application GPFs (because it relies on the "default folder").

Look for somthing like ConfigFile = PATH() & '\config.tps' in your
application.

Does this help?

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

NewsArchive
10-23-2008, 01:46 AM
Thanks Friedrich,

It is very puzzling. This app has not changed and I have many installations
with no problems. In fact this company has been using the program/data for
the last 2 years buying the new data and exe just about every month. The
program and the SB install has not changed other than changing the new data
file.

All files reside in the same directory (c:\locator6). It has to be
something they have changed in their system.

Don Harvey

NewsArchive
10-23-2008, 01:47 AM
Hi Don,

> It is very puzzling. This app has not changed and I have many
> installations with no problems. In fact this company has been
> using the program/data for the last 2 years buying the new data
> and exe just about every month. The program and the SB install
> has not changed other than changing the new data file.
>
> All files reside in the same directory (c:\locator6). It has to be
> something they have changed in their system.

Aha, okay. Yes, that's quite possible.

But to be on the safe side, make sure you have the "Default Directory"
defined (see attached screenshot). In this example, sbuilder.exe is
installed to %_SB_INSTALLDIR% (whatever that is on the target machine) and
the default folder is also %_SB_INSTALLDIR%

Friedrich

NewsArchive
10-23-2008, 01:48 AM
Yes, set per attached jpg. I told them to test on another machine and see
what happens. If that fails, then I guess a refund is in order because I
have tested on my machines here at the office and also my machine at home
with no problems, and also 20 or so new installs with other clients this
month reporting no problems.

Don Harvey

NewsArchive
10-23-2008, 01:49 AM
Hi Don,

> Yes, set per attached jpg. I told them to test on another machine and see
> what happens. If that fails, then I guess a refund is in order because I
> have tested on my machines here at the office and also my machine at home
> with no problems, and also 20 or so new installs with other clients this
> month reporting no problems.

Looks okay to me.

BTW, do you have to "wait" for Icc6.exe because you start another app after
Icc6.exe finished?

Friedrich

NewsArchive
10-23-2008, 01:49 AM
No, I just noticed that.

Don Harvey

NewsArchive
10-23-2008, 01:50 AM
>
> No, I just noticed that.
>

Yes, I think it would be a good idea to disable "Wait".

Friedrich

NewsArchive
10-23-2008, 01:50 AM
By the way, please keep us posted.

Friedrich