🚀 go-pugleaf

On Mon, 27 Mar 2000 13:39:54 -0500, "James S. Coan" <jcoan@att.net> wrote:

>1) When I bring up bcb5 with my old project, it seemed to do the
>conversion just fine, but when I close bcb5 I get "This program has
>performed an illegal operation and will be shut down.  Contact
>vendor....
>
>One time it said illegal operation vcl50.bpl 0167:40008924
>
>another time it was Module kernel32.dll
>
>All I have to do is open bcb5 with the project and immediately close it
>to produce the illegal operation.

This sounds like a problem I had encountered back in the BCB v4 days.  It
is possible that you have faulty hardware and/or faulty device drivers for
some of your hardware.  I know I had a system which would not run reliably
at 100MHz FSB.  NT4 would install and run,  but moving large amounts of
data on that system would have problems.  Things like performing a large
copy across the network,  performing a tape backup,  launching BCB v4
(images loading for buttons, etc).  I initially resolve my problem by
"underclocking" the system until I could go replace it with a new more
reliable one...

>2) If I compile files in the project, I get "including vcl4.h instead of
>vcl.h dur to -Hr switch"  I can't find this switch, and I can't find any
>reference to it.

While this can be rather confusing,  it is considered to be "normal" and is
only supposed to be visible if you have the option checked to "show general
messages" (on the compiler tab in the project options screen).  I do not
necessarily like it either,  but according to the guys at Borland,  it is
nothing,  and should be ignored...

>When I installed bcb5, I left bcb4 installed, but I see that some files
>that bcb4 wants to access have been overwritten.

This should not be a problem.  The machine I am working on now had BCB v3,
BCB v4, BCB v5, Delphi v4, and Delphi v5 all installed on it,  and they all
appear to work just as expected.  I am aware that I have to be careful in
working with projects using both BCB v4 and BCB v5 as the project file
formats are not compatible,  but they use the same name (if the project is
upgraded)...

>What is going on?

Well,  part of your problem is that the compiler is rather vague in what it
is doing (part 2).  Another part of your problem could be a bad video
driver,  or some other problem (part 1)...
Jerry Bloomfield (TeamB)
-- 
Jerry Bloomfield                                     JersWork@wwa.com
Proud Member of Borland's TeamB
"We'll do anything if you don't pay us."