--- In IBObjects@yahoogroups.com, "Mark Lawes" <mark.lawes@n...> wrote:

> ----- Original Message -----
> From: "Steve Harp" <steve@h...>
> To: <IBObjects@yahoogroups.com>
> Sent: 30 August 2005 22:04
> Subject: Re: [IBO] Initialization code for IBObjects
>
>
> > --- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
> > > At 12:49 AM 30/08/2005 +0000, you wrote:
> > >
> > > > > 3. In case the IBO element is coincidental, are you sure

that the

> > > > > Microsoft C and C++ runtimes are installed on the problem

servers?

> > > > >
> > > >Hi Helen,
> > > >
> > > >"don't run" means it never even flashes on the task bar. It never
> > > >shows up in processes under task manager.
> > > >
> > > >As I said the main form is created first in the dpr but it's

OnCreate

> > > >method never fires (Application.CreateForm(TfrmMain, frmMain);).
> > > >
> > > >I'm not sure this is related to IBO. I just can't think of

anything

> > > >else that's unique to these 2 applications.
> > >
> > > Nothing in the system logs?
> > >
> >
> > Our network guru type guys suggested using the Processes tab in Task
> > Manager to view CPU and Memory usage during startup. On Startup, the
> > application runs up to about 82% CPU usage and then barfs and closes.
> > However, no event log entry is made. Our other applications (the
> > ones that run correctly on these machines) do pretty much the same
> > thing; while loading they jump up to about 82% and then drop to zero
> > after loading and display about 16 MB memory usage.
> >
> > The operating system is obviously trying to load the application and
> > failing. If that's true, why is no event log entry made? Keep in
> > mind that (with logging to a text file) I've determined that the form
> > creation code in the DPR isn't even being executed.
> >
> > Steve
> >
>
> Just my two pennyworth
>
> I would be tempted to create a dead simple program in delphi which just
> instantiates a form and closes on an OK button (No IBO). This will take
> about 5 mins.
>
> If this works you have established that the machine will run a

Delphi prog.

> If fails its not IBO.
>
> If OK create a minimal program which connects to an IBO database then
> disconnects and closes on an OK button.
>
> If this fails its telling you its (probably) an out and out IBO

problem of

> some sort.

I have several Delphi apps (some of which are quite complex) that run
fine on these machines.