Fatal Runtime Error

I have been receiving a fatal runtime error (Access Violation) when I
run any program through Delphi 5. The debugger shows it to me in the
Classes unit at the procedure TList.IndexOf. I tried loading a
program that does not contain any TList objects, but I continue to
receive the same error. I then tried unistalling the last few
components and I still am receiving the error. I am of the opinion
that something is corrupt and I need to reinstall Delphi. Does anyone
have any insite as to what might be causing this problem and how I
might go about fixing it? I appreciate any help you might be able to
give.

c-ya
dj

"D.J. Overman" <djoverman@perfero.com> skrev i melding
news:b9d0086c.0308180552.584a9e42@posting.google.c om...
> I have been receiving a fatal runtime error (Access Violation) when I
> run any program through Delphi 5. The debugger shows it to me in the
> Classes unit at the procedure TList.IndexOf. I tried loading a
> program that does not contain any TList objects, but I continue to
> receive the same error. I then tried unistalling the last few
> components and I still am receiving the error. I am of the opinion
> that something is corrupt and I need to reinstall Delphi. Does anyone
> have any insite as to what might be causing this problem and how I
> might go about fixing it? I appreciate any help you might be able to
> give.
>
> c-ya
> dj

Maybe you're not haunted by the infamous FIFB (Find In Files Bug) ?
If you do a "Find in Files" search, and delete code that's listed in the
search results - you may be dragged with EAccessViolations.
Try closing the 'search results' window by clicking the 'x'. If this does
not work, there are methods for making it close (as you otherwise won't be
able to save your modified source files).

--
Regards,

Bjørge Sæther
bjorge@haha_itte.no
-------------------------------------
I'll not spend any money on American Software products
until armed forces are out of Iraq.

On Mon, 18 Aug 2003 21:01:27 +0200, "Bjørge Sæther"
<bjorge@hahaha_itte.no> wrote:

>Maybe you're not haunted by the infamous FIFB (Find In Files Bug) ?
>If you do a "Find in Files" search, and delete code that's listed in the
>search results - you may be dragged with EAccessViolations.
>Try closing the 'search results' window by clicking the 'x'. If this does
>not work, there are methods for making it close (as you otherwise won't be
>able to save your modified source files).

Ahhh! So that's what bugged me the other week! For future reference,
what *are* the methods of closing it?

MH.

"Martin Harvey" <martin@pergolesi.demon.co.uk> skrev i melding
news:9dm2kv019c0l5kn0bbu4urj69e8kvgeget@4ax.com...
> On Mon, 18 Aug 2003 21:01:27 +0200, "Bjørge Sæther"
> <bjorge@hahaha_itte.no> wrote:
>
> >Maybe you're not haunted by the infamous FIFB (Find In Files Bug) ?
> >If you do a "Find in Files" search, and delete code that's listed in the
> >search results - you may be dragged with EAccessViolations.
> >Try closing the 'search results' window by clicking the 'x'. If this does
> >not work, there are methods for making it close (as you otherwise won't
be
> >able to save your modified source files).
>
> Ahhh! So that's what bugged me the other week! For future reference,
> what *are* the methods of closing it?

1) On a slow machine (The last one I succeded with: 350MHz AMD K6-2):
--------------------
- When EAccessViolation messages start popping up, press ENTER and keep it
pressed. This closes the error dialogs at the speed of the keyboard repeat
frequency.
- With your mouse, click 'x' (the tiny close button) in "search result
window" frenetically.
- At some point, you'll manage to get a mouse click inbetween two Exception
dialogs, the window closes, and your ENTER keystrokes starts making empty
lines in the editor. It may take a minute if you're out of luck ;-|
- Release the key, delete the unwanted empty lines.
- Save your work
- Restart Delphi. Search results are not stored...;-)

2) On a fast machine (mine is 2GHz):
--------------------
- Run an application that eats as much CPU time as possible (e.g. a tight
endless loop in a Delphi app). Interbase/Firebird is suitable, running a
query that will take some time to finish (IB consumes some 99% when running,
regardless what other apps are up to)
- Use the technique desribed in 1)

To avoid the problem:
----------------------------
- Save your work every now and then ;-)
- Clear search results after you've finished using them (right click in
"search results window")

Hope this helps !

--
Regards,

Bjørge Sæther
bjorge@haha_itte.no
-------------------------------------
I'll not spend any money on American Software products
until armed forces are out of Iraq.