Borland C++ 4.0 bugs
K30...@alijku11.bitnet
the bc++ 4.0 ide. After reading a reply. I think this problem seems to occur on
ly in the german version(which was released a few months later than the english
one). I talked to some guys at the university of vienna who have got their cop
y of BC++ a few days ago and they have the same problems. But I discovered some
thing more serious. The IDE doesn't make a backup of the APX file(the database
file for the class expert) If the system crashes it is possible that the apx fi
le is destroyed and you have to reconstruct it manually (which of course is
pretty time consuming)-So backup you apx regularly|||| (maybe there is a switch
for autobackup and a haven't found it so far. If anybody knows about it please
let me know otherwise i gonna have to write a program which does it automatical
ly))
Donald Likes
these bugs so bad that you would send 4.0 back?
Also, is the upgrade worth it (compared to 3.1)???
Craig.
Brian Long
> a few months later than the english one).
That shouldn't be the case. I understood that R&D did a simultaneous
ship. Reported to be the largest simultaneous native (English) and
localised (German) product ever...
- Brian
Roy Wright
You can regenerate the APX file by right clicking on the target exe in the
project manager and selecting Special|Rescan.
Have Fun,
Roy
--------------------------------------------------------------------
Roy Wright MSGID:ROYW Internet:wri...@lobby.ti.com
Texas Instruments voice:214-575-6691 fax:214-575-6200
"I can't quite make a PC sing, but roll over and play dead is easy!"
Andrew G. Kriger
i have had these problems with BC4.0 so far:
1) resource workshop will not run - "Resource workshop requires BWCC 2.00 or
above". why wasn't this included in the installation?
2) linker errors for even the simplest of programs ("hello world" sorts of
things) - linker out of memory errors or errors related to one of the owl dll's
any clues here?
3) (not a bug but still annoying) SLOW as HELL! compiling/linking is slow.
opening/closing is slow. just about everything is slow. (not the first time
i've heard this).
i have a 386dx40 w/8meg.
anyone have suggestions, else i have no choice but to get my $$$ back and
return to 3.1
--
Andrew Kriger There exists no separation between gods and men;
akr...@halcyon.com one blends softly casual into the other.
-- Frank Herbert
Simon Tooke
>In article <94024.143...@ALIJKU11.BITNET> <K30...@ALIJKU11.BITNET> writes:
>>A few netnews articles ago i talked about some cursor blink rate problems with
>>the bc++ 4.0 ide. After reading a reply. I think this problem seems to occur on
>>ly in the german version(which was released a few months later than the english
>> one). I talked to some guys at the university of vienna who have got their cop
>>y of BC++ a few days ago and they have the same problems. But I discovered some
>>thing more serious. The IDE doesn't make a backup of the APX file(the database
>>file for the class expert) If the system crashes it is possible that the apx fi
>>le is destroyed and you have to reconstruct it manually (which of course is
>>pretty time consuming)-So backup you apx regularly|||| (maybe there is a switch
>>for autobackup and a haven't found it so far. If anybody knows about it please
>>let me know otherwise i gonna have to write a program which does it automatical
>>ly))
>You can regenerate the APX file by right clicking on the target exe in the
>project manager and selecting Special|Rescan.
Backing up the .APX file doesn't seem to be as important as backing up the
.IDE file; if you have an AppExpert application, and delete the IDE file,
it is no longer marked as AppExpert, you can't rescan, and ClassExpert no
longer even attempts to run. ClassExpert may not have run because the APX
file was gone, too, but I no longer had any way to rebuild it.
-simon tooke
===============================================================================
Simon Tooke (not speaking for) SCO Canada, Inc. Voice: (416) 922-1937
....!scocan!simon si...@sco.com Fax: (416) 922-2704
130 Bloor St. West. Suite 1001, Toronto, Ontario, Canada M5S 1N5
James L. Waletzky
>i have had these problems with BC4.0 so far:
>1) resource workshop will not run - "Resource workshop requires BWCC 2.00 or
>above". why wasn't this included in the installation?
A prof of mine had the same problem. Do you have another version of
the workshop or BWCC.DLL on your hard disk BEFORE you install? If so,
nuke the old version, then run install again. This should fix your
problem. Apparently if the install finds an old version, it does not
update with the new files... go figure.
James.
--
James Waletzky \ "There are very few problems that
University Of Manitoba / cannot be solved without a suitable
umwa...@ccu.umanitoba.ca \ application of high explosives."
wal...@ee.umanitoba.ca /
Colin Goodall
The error states that it requires BWCC.DLL 2.0, yes it is included. But
I had the same problem. What is happening is that there is an older version
of BWCC somehwere on your system that Resource Workshop is loading first.
Upon loading it the version is checked and when it doesn't match the load of
Resource Workshop is aborted.
To fix this try finding all the older versions of the BWCC Dll and remove
the older version.
In my case I had a copy of the older BWCC in my C:\WINDOWS directory.
By removing it the version 2.0 which should be installed automatically
in your C:\WINDOWS\SYSTEM directory will be loaded.
Hope this helps
Colin G
Andrew G. Kriger
thanks for the help, i'll try it (though i did remove old borland c++ including
bwcc.dll , tried it failed, removed bc4 and windows, tried and failed, but i
did just find another bwcc.dll in my soundblaster directory).
other problems i'm having that perhaps folks can offer solutions for:
1) bc4 runs way durn slow - noticable enough to be annoying - i have 8meg of
of ram on a 386dx40 - any suggestions?
2) i can't get any program to link without the following error:
Linker Error: Undefined symbol OwlMain(int, char far *far*) in
library file C:\BC4\LIB\owlwl.lib in module winmain
this is even happening for the simplest program of all:
#include <stdio.h>
void main() {
printf("hello, world");
}
what's going on?
post or email responses.
thanks in advance.
Peter Crawshaw
>Xref: mta.ca comp.os.ms-windows.programmer.misc:24899 comp.os.ms-windows.misc:21934
>Path: mta.ca!csd.unb.ca!torn!howland.reston.ans.net!pipex!uunet!nwnexus!akriger
>From: akr...@halcyon.com (Andrew G. Kriger)
>Newsgroups: comp.os.ms-windows.programmer.misc,comp.os.ms-windows.misc
>Subject: RE:Borland C++ 4.0 problems
>Date: 29 Jan 1994 21:34:13 -0800
>Organization: "A World of Information at your Fingertips"
>Lines: 25
>Sender: ne...@nwfocus.wa.com
>Message-ID: <2ifgsl$r...@nwfocus.wa.com>
>References: <D> <wright.11...@lobby.ti.com> <2icl55$b...@nwfocus.wa.com> <CKFDr...@cunews.carleton.ca>
>NNTP-Posting-Host: nwfocus.wa.com
>other problems i'm having that perhaps folks can offer solutions for:
>1) bc4 runs way durn slow - noticable enough to be annoying - i have 8meg of
>of ram on a 386dx40 - any suggestions?
I have a 486/66 w/ 16 MB RAM at work and a 386/40 w/ 8 meg. at home.
At work it's slow. Needless to say, I don't plan on using BC4 at home.
The only thing I can suggest is to use the command-line tools, or use BC++ 3.1.
>2) i can't get any program to link without the following error:
> Linker Error: Undefined symbol OwlMain(int, char far *far*) in
> library file C:\BC4\LIB\owlwl.lib in module winmain
> this is even happening for the simplest program of all:
> #include <stdio.h>
> void main() {
> printf("hello, world");
> }
> what's going on?
It looks like you're trying to compile a DOS program, but you have BC4
set for a windows target. The linker is looking for WinMain and OwlMain
because it thinks you're compiling a Windows program with OWL. Check
your compiler and linker settings.
>post or email responses.
>thanks in advance.
============================================================
Peter Crawshaw Mount Allison University
On Line Learning Centre Sackville, NB, Canada
pcra...@mta.ca E0A 3C0
Gary Raines
>
>
>i have had these problems with BC4.0 so far:
>1) resource workshop will not run - "Resource workshop requires BWCC 2.00 or
Most folks hard disks are full of old versions of BWCC.DLL. Make sure that you
have the latest version in your \windows and or \windows\system directory.
>above". why wasn't this included in the installation?
>2) linker errors for even the simplest of programs ("hello world" sorts of
>things) - linker out of memory errors or errors related to one of the owl dll's
>any clues here?
No clue. I've not seen this problem.
>3) (not a bug but still annoying) SLOW as HELL! compiling/linking is slow.
>opening/closing is slow. just about everything is slow. (not the first time
>i've heard this).
Are you executing from CD-ROM? CD-ROMs are SLOOOOOOW!
>i have a 386dx40 w/8meg.
>anyone have suggestions, else i have no choice but to get my $$$ back and
>return to 3.1
Stick with it! I am a beginner, having all kinds of kinks, but most problems
seem to be my misunderstandings.
>
>--
>Andrew Kriger There exists no separation between gods and men;
>akr...@halcyon.com one blends softly casual into the other.
> -- Frank Herbert
Gary Raines
rai...@asd2.jsc.nasa.gov
Ken Corbin
> 3) (not a bug but still annoying) SLOW as HELL! compiling/linking is slow.
> opening/closing is slow. just about everything is slow. (not the first time
> i've heard this).
> i have a 386dx40 w/8meg.
> anyone have suggestions, else i have no choice but to get my $$$ back and
> return to 3.1
This probably won't be terribly helpful, but the complaints about slow
compiler speed drop off signifigantly when you add memory. It hums
along at a respectable clip with 10-12 Meg.
Gary Raines
>
>In <2icl55$b...@nwfocus.wa.com> akr...@halcyon.com (Andrew G. Kriger) writes:
>
>
>>i have had these problems with BC4.0 so far:
>>1) resource workshop will not run - "Resource workshop requires BWCC 2.00 or
>>above". why wasn't this included in the installation?
>
>A prof of mine had the same problem. Do you have another version of
>the workshop or BWCC.DLL on your hard disk BEFORE you install? If so,
>nuke the old version, then run install again. This should fix your
>problem. Apparently if the install finds an old version, it does not
>update with the new files... go figure.
It does update it. It is just that most people's path statement takes you to
some directory like \windows first (instead of \windows\system)
This is ok, it is just that some other program has probably put a version
of BWCC.DLL in \windows and you can't get by it - delete it or update it.
nor...@mwk.com
>
> other problems i'm having that perhaps folks can offer solutions for:
> Linker Error: Undefined symbol OwlMain(int, char far *far*) in
> library file C:\BC4\LIB\owlwl.lib in module winmain
> this is even happening for the simplest program of all:
> #include <stdio.h>
> void main() {
> printf("hello, world");
> }
> what's going on?
>
You are suffering from the same problem that several other posters are:
You haven't even done 5 minutes of reading in the manual that came with
your compiler. You are getting the link error because you told the IDE to
build a WINDOWS app using OWL! Go to the project pulldown and change the
type of application to "DOS" !
Before blasting Borland and its product, at least have the decency to read the
instructions for a few minutes.
Modern compilers are not simple toys: this reminds me of a group
of 4-year-old children playing at the controls of the space shuttle...