Delphi IDE crash on XP Pro
Duncan McNiven
with Delphi (7) crashing. Delphi simply disappears, with no warning and
no error message. Nothing appears in the event log.
This happened once last week and twice today. The first time today, it
happened whilst I was away from the PC. The second time I was simply
typing in the editor; the project was a small one, with nothing complex
in it. Just a test framework for a new class.
Any knowledge of what might be wrong?
Any clue how I go about tracing this fault?
I have been googling for info. There are many posts about Delphi & XP
but so far I have found nothing useful.
--
Duncan
Marco van de Voort
Driver problems, rotten memory, DLL hell (read Windows reinstall).
Best way is to reinstall windows and delphi from scratch. If it works then,
you know it is a windows internal software problem.
MikeB
"Marco van de Voort" <mar...@stack.nl> wrote in message news:slrnc4ud54...@toad.stack.nl...
> On 2004-03-10, Duncan McNiven <dun...@mcniven.net> wrote:
> > I have recently moved my main development to XP Pro and have a problem
> > with Delphi (7) crashing. Delphi simply disappears, with no warning and
> > no error message. Nothing appears in the event log.
> >
> > This happened once last week and twice today. The first time today, it
> > happened whilst I was away from the PC. The second time I was simply
> > typing in the editor; the project was a small one, with nothing complex
> > in it. Just a test framework for a new class.
> >
> > Any knowledge of what might be wrong?
> > Any clue how I go about tracing this fault?
> >
> > I have been googling for info. There are many posts about Delphi & XP
> > but so far I have found nothing useful.
>
> Driver problems, rotten memory, DLL hell (read Windows reinstall).
Driver Problems: could be
Rotten Memory: How will a reinstall help this?
DLL Hell: XP Pro has an excellent file protection scheme. This is Unlikely.
Is your Xp Pro an upgrade over an NT or W2k install? If so, then I would agree with the reinstall, but
only if the reinstall is a Virgin install, not an "In Place".
A successful Windows install is degraded according to how far you depart from the hardware compatibility
list.
Marco van de Voort
>
> "Marco van de Voort" <mar...@stack.nl> wrote in message news:slrnc4ud54...@toad.stack.nl...
>> On 2004-03-10, Duncan McNiven <dun...@mcniven.net> wrote:
>> > I have recently moved my main development to XP Pro and have a problem
>> > with Delphi (7) crashing. Delphi simply disappears, with no warning and
>> > no error message. Nothing appears in the event log.
>> >
>> > This happened once last week and twice today. The first time today, it
>> > happened whilst I was away from the PC. The second time I was simply
>> > typing in the editor; the project was a small one, with nothing complex
>> > in it. Just a test framework for a new class.
>> >
>> > Any knowledge of what might be wrong?
>> > Any clue how I go about tracing this fault?
>> >
>> > I have been googling for info. There are many posts about Delphi & XP
>> > but so far I have found nothing useful.
>>
>> Driver problems, rotten memory, DLL hell (read Windows reinstall).
>
> Driver Problems: could be
> Rotten Memory: How will a reinstall help this?
If the problem persists after reinstalling, you know _it is_ the problem
most likely ;_)
> DLL Hell: XP Pro has an excellent file protection scheme. This is
> Unlikely.
/me laughs. It has a stopgap protection copy_old_over_new protection, sure,
however I fail to see why that would get the qualification "excellent"?
Nothing protects you from integrated components in certain version not
cooperating.
> Is your Xp Pro an upgrade over an NT or W2k install?
Virgin 2k, an XP, after a while they all get it, upgrades get it much sooner
though.
Bruce Roberts
"Duncan McNiven" <dun...@mcniven.net> wrote in message
news:l18u40556epj13cjn...@4ax.com...
> Any knowledge of what might be wrong?
> Any clue how I go about tracing this fault?
Possibly a 3rd party component or IDE tool. I'd remove any such stuff from
your Delphi installation and see if the problem remains. If it doesn't add
them back in one at a time.
In my experience the behavior is most often caused by an access violation in
a dll being used.
Duncan McNiven
<b...@bounceitattcanada.xnet> wrote:
>
>"Duncan McNiven" <dun...@mcniven.net> wrote in message
>news:l18u40556epj13cjn...@4ax.com...
>
>> Any knowledge of what might be wrong?
>> Any clue how I go about tracing this fault?
>
>Possibly a 3rd party component or IDE tool. I'd remove any such stuff from
>your Delphi installation and see if the problem remains. If it doesn't add
>them back in one at a time.
Thanks for the suggestion. I can rule this one out easily enough though.
My upgrade is so new I haven't even got round to installing my own
custom components yet. Everything is stock Delphi.
>In my experience the behavior is most often caused by an access violation in
>a dll being used.
Wouldn't I get an access violation error message from that? I don't get
anything; Delphi just disappears.
--
Duncan
Duncan McNiven
<m.byerleyATVerizonDottieNettie> wrote:
>
>"Marco van de Voort" <mar...@stack.nl> wrote in message news:slrnc4ud54...@toad.stack.nl...
>>
>> Driver problems, rotten memory, DLL hell (read Windows reinstall).
rotten memory may be worth looking at, as I swapped memory between two
PCs when I did my OS upgrade. Short of swapping it back again, how can I
check the memory?
>Is your Xp Pro an upgrade over an NT or W2k install?
No, installed to a new disk.
It is only a few days since I installed XP and I am reluctant to go
through all that again. The first time my crash happened was within a
day of the original install, so I doubt if this was any kind of
corruption; I would get the same situation if I reinstalled I think.
Anyway, with an intermittent problem what would I conclude if it didn't
happen for a couple of days after the reinstall? Was that because my
system got corrupted again, or the fault conditions just didn't occur
for a couple of days?
Incidentally, I had the same problem again this afternoon. This time I
know exactly what I was doing - I pressed Ctrl-C to cut a line of code
to the clipboard. That gives me no clues as to cause though.
>If so, then I would agree with the reinstall, but
>only if the reinstall is a Virgin install, not an "In Place".
>A successful Windows install is degraded according to how far you depart from the hardware compatibility
>list.
All the hardware on my system is using standard drivers from the XP
install. I have applied all patches & automatic updates. I haven't had
the problem with any other software.
--
Duncan
Ray Porter
You might want to head over the the borland newsgroups
(newsgroups.borland.com) and ask your question there. The folks from TeamB
and several Borland staffers monitor those groups and are usually willing to
help. I've been running D7 Pro at home (a Dell desktop, about 1 year old)
for months and at work (IBM desktop) for a couple of weeks, both with XP Pro
with no problems whatsoever. The Borland newsgroups are your best shot at
help. Post your question there with a full description of your hardware,
particularly including video card and amount of RAM.
As others have already pointed out, the most usual sources of problems like
that you describe are a bad video driver or a badly behaved third-party
component but I certainly wouldn't rule out other problems.
Good luck,
Ray Porter
"Duncan McNiven" <dun...@mcniven.net> wrote in message
news:7i3v40d98nnooohgo...@4ax.com...
Bruce Roberts
> >In my experience the behavior is most often caused by an access violation
in
> >a dll being used.
>
> Wouldn't I get an access violation error message from that? I don't get
> anything; Delphi just disappears.
One would expect so, but my experience has been that this is not always the
case. I suspect that it may be an issue of how deeply buried the exception
is and how the various libraries involved handle the exceptions they
encounter.