BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Very sloooooooooow application startup ...

 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Databases (Desktop)
View previous topic :: View next topic  
Author Message
Peter B.
Guest





PostPosted: Thu Mar 23, 2006 1:03 pm    Post subject: Very sloooooooooow application startup ... Reply with quote



Hi
I have an application which uses the BDE 5.2.0.2 and Paradox 7 and is a
local application using only (TSession) TDatasource and TTable components.
It has latterly been further developed in D7 (ported from D4 originally).
This app. has been run on Win98SE (loads in a couple of seconds, slowish
machine), WinXP Home (slightly more painful but acceptable) but Win XP Pro
takes 25 to 30 secs before the main form appears on a very fast machine !
I can tell the program actually loads very fast on the XP Pro machine
because my code to start contains a change to crHourglass and a return to
crDefault on completion (probably less than a second) but then the taskbar
network icon lights up with what appears to be severe 2 way activity for
another 25 or so seconds, then the main form appears. Although the app. is
local, the XP and Win 98 machines share ethernet but turning the 98 machine
off and running the XP Pro standalone doesn't cahange anything. Delphi 7 is
installed on both machines, PDOXUSRS.NET is in C:\ on both and LocalShare is
set to false on both. Turning antivirus software off (ie. Zone Labs, Norton
2006 can only be regarded as crippleware Wink these days) also has no effect.
I obviously cannot let this issue afflict users (although I have no
feedback about this) but any ideas what's going on here please ? I'm totally
lost here !

thanks in anticipation

best wishes always

Peter B.
Back to top
Wayne Niddery [TeamB]
Guest





PostPosted: Thu Mar 23, 2006 6:03 pm    Post subject: Re: Very sloooooooooow application startup ... Reply with quote



Peter B. wrote:
Quote:
I can tell the program actually
loads very fast on the XP Pro machine because my code to start
contains a change to crHourglass and a return to crDefault on
completion (probably less than a second) but then the taskbar network
icon lights up with what appears to be severe 2 way activity for
another 25 or so seconds, then the main form appears.

This would seem to indicate it is attempting to communicate with another
computer, but eventual failure (by turning the other computer off) is not
fatal. Check you TDatabase and/or TTable components to make sure you are not
compiling with a database path or BDE alias that points to another machine,
and the Connected or Active properties et to True (though you should get an
error message if this happens, perhaps that is being suppressed by a
try/except in your code). As a rule I always make sure data components are
not connected at compile time and I turn them on in code after making sure
the path or alias is correct.

The only other possibility is non-database components - are you using any
tcp or other such components?

--
Wayne Niddery - Logic Fundamentals, Inc. (www.logicfundamentals.com)
RADBooks: http://www.logicfundamentals.com/RADBooks.html
"True peace is not the absence of tension, but the presence of
justice." - Martin Luther King, Jr.
Back to top
Peter B.
Guest





PostPosted: Fri Mar 24, 2006 12:03 am    Post subject: Re: Very sloooooooooow application startup ... Reply with quote



Wayne
Thanks for taking the time to try and help me out here, it's much
appreciated. The coding has been checked as suggested, I'm not 'masking'
anything within a try/except block and my tables have their databasename and
active properties set at runtime always. I have deleted and restored the
alias using the BDE Administrator and using my program, which will restore
the alias if a user wipes it inadvertently, but still the same issue. Also,
I've deleted the PDOXUSRS.NET file in C:\ on the Win XP Pro machine several
times, all to no avail. All 3 machines I have access to do not share their
C: drives, so it's not a case of any interference between PDOXUSRS.NET files
on different machines.
It certainly does seem that starting my program causes severe network
activity, so I tried to track this. My event logs indicated some TCP errors,
so I opened a DOS window and tried to track using netstat with -no switches.
There I saw 65 ! attempts by the XP Pro machine to converse with my Win 98
SE machine. The event log indicates that the stack for this gets full and
then my program is allowed to execute ! So I tried the obvious and
physically disconnected the Win 98 machine from the network. Definitely no
joy there ! I received a series of runtime errors and the program seriously
fell over.
This program has been running happily on a Win 98 SE and a Win XP Home
machine for a minimum of the last 2 years but not this XP Pro machine which
has just been purchased as my main development machine - crazy or what ?
I realise that talking about TCP and operating system vagaries may fall a
little outside the scope of this particular newsgroup but I really am stuck
for ideas now and would desperately appreciate any suggestions from
yourself, any Team B colleagues or anyone because it seems TCP is the clue
and there must be many Paradox7/BDE local database applications running
quite happily on WinXP Pro machines around the world ...

thanks in anticipation

Peter B.

"Wayne Niddery [TeamB]" <wniddery (AT) chaffaci (DOT) on.ca> wrote in message
news:4422dab7$1 (AT) newsgroups (DOT) borland.com...
Quote:
Peter B. wrote:
I can tell the program actually
loads very fast on the XP Pro machine because my code to start
contains a change to crHourglass and a return to crDefault on
completion (probably less than a second) but then the taskbar network
icon lights up with what appears to be severe 2 way activity for
another 25 or so seconds, then the main form appears.

This would seem to indicate it is attempting to communicate with another
computer, but eventual failure (by turning the other computer off) is not
fatal. Check you TDatabase and/or TTable components to make sure you are
not
compiling with a database path or BDE alias that points to another
machine,
and the Connected or Active properties et to True (though you should get
an
error message if this happens, perhaps that is being suppressed by a
try/except in your code). As a rule I always make sure data components are
not connected at compile time and I turn them on in code after making sure
the path or alias is correct.

The only other possibility is non-database components - are you using any
tcp or other such components?

--
Wayne Niddery - Logic Fundamentals, Inc. (www.logicfundamentals.com)
RADBooks: http://www.logicfundamentals.com/RADBooks.html
"True peace is not the absence of tension, but the presence of
justice." - Martin Luther King, Jr.

Back to top
Peter B.
Guest





PostPosted: Fri Mar 24, 2006 4:03 pm    Post subject: Re: Very sloooooooooow application startup ... Reply with quote

OK, thanks once again Wayne. Your suggestion is being worked on at the
moment. I was put off the coding direction in the first instance simply
because the program runs well on both Win 98 and XP Home, is a local
application and possibly I have been hooked on the fact that this is a new
Delphi 7 install on a new machine. Perhaps things are definitely not what
they always seem. I shall report back in due course and if it is my code,
then I'll own up !

best wishes always

Peter B.

"Wayne Niddery [TeamB]" <wniddery (AT) chaffaci (DOT) on.ca> wrote in message
news:4424096b$1 (AT) newsgroups (DOT) borland.com...
Quote:
Peter B. wrote:
My
event logs indicated some TCP errors, so I opened a DOS window and
tried to track using netstat with -no switches. There I saw 65 !
attempts by the XP Pro machine to converse with my Win 98 SE machine.
The event log indicates that the stack for this gets full and then my
program is allowed to execute ! So I tried the obvious and physically
disconnected the Win 98 machine from the network. Definitely no joy
there ! I received a series of runtime errors and the program
seriously fell over.

Well then you've confirmed there is something in your program doing this,
you just have to figure out what. I suspect it has nothing to do with the
BDE and you have something else going on. You need to compile (build) with
full debug info and perhaps include the debug VCL libraries, and step
through to try to find it. From your previous description I would start in
the the OnCreate of your mainform (or the Create constructor if you have
overridden this).

--
Wayne Niddery - Logic Fundamentals, Inc. (www.logicfundamentals.com)
RADBooks: http://www.logicfundamentals.com/RADBooks.html
"Light is faster than sound, which is why some folks appear bright
before they speak."

Back to top
Wayne Niddery [TeamB]
Guest





PostPosted: Fri Mar 24, 2006 4:03 pm    Post subject: Re: Very sloooooooooow application startup ... Reply with quote

Peter B. wrote:
Quote:
My
event logs indicated some TCP errors, so I opened a DOS window and
tried to track using netstat with -no switches. There I saw 65 !
attempts by the XP Pro machine to converse with my Win 98 SE machine.
The event log indicates that the stack for this gets full and then my
program is allowed to execute ! So I tried the obvious and physically
disconnected the Win 98 machine from the network. Definitely no joy
there ! I received a series of runtime errors and the program
seriously fell over.

Well then you've confirmed there is something in your program doing this,
you just have to figure out what. I suspect it has nothing to do with the
BDE and you have something else going on. You need to compile (build) with
full debug info and perhaps include the debug VCL libraries, and step
through to try to find it. From your previous description I would start in
the the OnCreate of your mainform (or the Create constructor if you have
overridden this).

--
Wayne Niddery - Logic Fundamentals, Inc. (www.logicfundamentals.com)
RADBooks: http://www.logicfundamentals.com/RADBooks.html
"Light is faster than sound, which is why some folks appear bright
before they speak."
Back to top
Peter B.
Guest





PostPosted: Mon Mar 27, 2006 4:03 pm    Post subject: Re: Very sloooooooooow application startup ... Reply with quote

Wayne
When I resolved this issue I promised a reply. I'll hold my hand up (half
way!). Traced the problem to the Quick Reports project library (qrpt70.bpl).
Not my code but still my fault. The real problem was having a (not always
available) network printer set as default. Changing the default printer to
the directly connected one resolved all the problems. Things are not always
what they seem ! and to think I was so eager to blame the trusty old BDE !

best wishes always

Peter B. (slightly red faced)

"Peter B." <pcbarrett (AT) btinternet (DOT) com> wrote in message
news:44241169$1 (AT) newsgroups (DOT) borland.com...
Quote:
OK, thanks once again Wayne. Your suggestion is being worked on at the
moment. I was put off the coding direction in the first instance simply
because the program runs well on both Win 98 and XP Home, is a local
application and possibly I have been hooked on the fact that this is a new
Delphi 7 install on a new machine. Perhaps things are definitely not what
they always seem. I shall report back in due course and if it is my code,
then I'll own up !

best wishes always

Peter B.

"Wayne Niddery [TeamB]" <wniddery (AT) chaffaci (DOT) on.ca> wrote in message
news:4424096b$1 (AT) newsgroups (DOT) borland.com...
Peter B. wrote:
My
event logs indicated some TCP errors, so I opened a DOS window and
tried to track using netstat with -no switches. There I saw 65 !
attempts by the XP Pro machine to converse with my Win 98 SE machine.
The event log indicates that the stack for this gets full and then my
program is allowed to execute ! So I tried the obvious and physically
disconnected the Win 98 machine from the network. Definitely no joy
there ! I received a series of runtime errors and the program
seriously fell over.

Well then you've confirmed there is something in your program doing
this,
you just have to figure out what. I suspect it has nothing to do with
the
BDE and you have something else going on. You need to compile (build)
with
full debug info and perhaps include the debug VCL libraries, and step
through to try to find it. From your previous description I would start
in
the the OnCreate of your mainform (or the Create constructor if you have
overridden this).

--
Wayne Niddery - Logic Fundamentals, Inc. (www.logicfundamentals.com)
RADBooks: http://www.logicfundamentals.com/RADBooks.html
"Light is faster than sound, which is why some folks appear bright
before they speak."



Back to top
paladin
Guest





PostPosted: Mon Mar 27, 2006 8:03 pm    Post subject: Re: Very sloooooooooow application startup ... Reply with quote

Peter B. wrote:
Quote:
Wayne
When I resolved this issue I promised a reply. I'll hold my hand up (half
way!). Traced the problem to the Quick Reports project library (qrpt70.bpl).
Not my code but still my fault. The real problem was having a (not always
available) network printer set as default. Changing the default printer to
the directly connected one resolved all the problems. Things are not always
what they seem ! and to think I was so eager to blame the trusty old BDE !


commiseration:

We had a network printer set as the default printer on a Win2k machine.
ZoneAlarm was installed (but NOT running), but must have installed or
hooked some dll's. When the remote system was down, or off net, the Win2k
machine would NOT boot!!! I don't remember the exact particulars (blue
screen, error messages, etc.) but it was a beast to track down.


-paladin
Back to top
Wayne Niddery [TeamB]
Guest





PostPosted: Tue Mar 28, 2006 2:03 am    Post subject: Re: Very sloooooooooow application startup ... Reply with quote

Peter B. wrote:
Quote:
When I resolved this issue I promised a reply. I'll hold my hand up
(half way!). Traced the problem to the Quick Reports project library
(qrpt70.bpl). Not my code but still my fault. The real problem was
having a (not always available) network printer set as default.
Changing the default printer to the directly connected one resolved
all the problems. Things are not always what they seem ! and to think
I was so eager to blame the trusty old BDE !

So glad you got this resolved. Been a long time since I've touched QR and
then not much, but I think you should be able to make it so this doesn't
happen on start up - the QR components should be on a datamodule or form
that is only created if and when needed (not auto-created). Then the app can
start fast and function fine until the report is actually requested.

--
Wayne Niddery - Logic Fundamentals, Inc. (www.logicfundamentals.com)
RADBooks: http://www.logicfundamentals.com/RADBooks.html
"Some see private enterprise as a predatory target to be shot, others
as a cow to be milked, but few are those who see it as a sturdy horse
pulling the wagon." - Winston Churchill
Back to top
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Databases (Desktop) All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.