Thread View: comp.os.os2.programmer
4 messages
4 total messages
Started by David Feustel
Wed, 22 Jul 1992 23:37
Major Borland C++ 3.1 Bugs
Author: David Feustel
Date: Wed, 22 Jul 1992 23:37
Date: Wed, 22 Jul 1992 23:37
24 lines
1405 bytes
1405 bytes
I've started using Borland's C++ 3.1 on stock GA OS/2 v2.0 and I've run into major problems which may be caused by defects in DPMI.SYS. 1) Erratic Keyboard - on several ocasions keyboard input simply was ignored until I clicked on the mouse. 2) Erratic Mouse - many mouse clicks are ignored. Often a single click produces the effect of a quick double click. 3) linker doesn't find member function and continues to report undefined member function even after all occurances of the name have been changed. 4) linker prints class name in lower case even though the definition was entirely in upper case. 5) file date & time set to Jan 1, 1980 on files produced by the compiler. 6) linker unable to open object file produced by the compiler. I'm getting a new version of DPMI.SYS in a few days and I ferverently hope that installing it gets rid of these bugs which make Borland's c++ unusable on my machine. -- Dave Feustel N9MYI <feustel@netcom.com> --- What's the different between a Salem Witch Hunter and a modern day Drug Warrior? - 3 centuries.
Re: Major Borland C++ 3.1 Bugs
Author: David Feustel
Date: Thu, 23 Jul 1992 03:31
Date: Thu, 23 Jul 1992 03:31
36 lines
1910 bytes
1910 bytes
feustel@netcom.com (David Feustel) writes: >I've started using Borland's C++ 3.1 on stock GA OS/2 v2.0 and I've >run into major problems which may be caused by defects in DPMI.SYS. >1) Erratic Keyboard - on several ocasions keyboard input simply was >ignored until I clicked on the mouse. >2) Erratic Mouse - many mouse clicks are ignored. Often a single click >produces the effect of a quick double click. >3) linker doesn't find member function and continues to report >undefined member function even after all occurances of the name have >been changed. >4) linker prints class name in lower case even though the definition >was entirely in upper case. >5) file date & time set to Jan 1, 1980 on files produced by the >compiler. >6) linker unable to open object file produced by the compiler. I tried running bc under msdos 5.0 and still had the problem that the compiler produced no object modules even though the code compiled successfully. I got code and was able to run the program after deselecting the "produce asm files" from the compiler options box. DPMI.SYS does not appear to be available from software.watson.ibm.com. Does anyone know where the file can be FTP'd from? >I'm getting a new version of DPMI.SYS in a few days and I ferverently >hope that installing it gets rid of these bugs which make Borland's >c++ unusable on my machine. >-- -- Dave Feustel N9MYI <feustel@netcom.com> --- What's the different between a Salem Witch Hunter and a modern day Drug Warrior? - 3 centuries.
Re: Major Borland C++ 3.1 Bugs
Author: Timothy F. Sipples
Date: Thu, 23 Jul 1992 04:31
Date: Thu, 23 Jul 1992 04:31
23 lines
1822 bytes
1822 bytes
In article <zagmfyc.feustel@netcom.com> feustel@netcom.com (David Feustel) writes: >>I've started using Borland's C++ 3.1 on stock GA OS/2 v2.0 and I've >>run into major problems which may be caused by defects in DPMI.SYS. >I tried running bc under msdos 5.0 and still had the problem that the >compiler produced no object modules even though the code compiled >successfully. I got code and was able to run the program after >deselecting the "produce asm files" from the compiler options box. >DPMI.SYS does not appear to be available from software.watson.ibm.com. >Does anyone know where the file can be FTP'd from? I am not aware of any patch to the DPMI portion of OS/2, unless there's something internal. Stupid question perhaps, but have you set DPMI to ENABLED in DOS settings? Also, have tried to resolve the keyboard problems by turning on the keyboard rate lock and turning off the keyboard extended buffer, again both in DOS settings? -- Get the OS/2 FREQ. ASKED QUESTIONS LIST | Timothy F. Sipples from 128.123.35.151, anonymous ftp, | Internet: sip1@ellis.uchicago.edu directory pub/os2/all/faq, or from | Dept. of Econ., U. Chicago, 60637 LISTSERV@BLEKUL11.BITNET (send "HELP"). | Tsongas > Perot > Clinton. Yay.
Re: Major Borland C++ 3.1 Bugs
Author: Joe Huffman
Date: Thu, 23 Jul 1992 18:05
Date: Thu, 23 Jul 1992 18:05
16 lines
1068 bytes
1068 bytes
sip1@ellis.uchicago.edu (Timothy F. Sipples) writes: >I am not aware of any patch to the DPMI portion of OS/2, unless >there's something internal. FlashTek (the company I work for) received a 'private' fix for some DPMI bugs from IBM that we distribute with our 32-bit DOS extender that requires DPMI support from OS/2. This fixed some problems with the Zortech compiler under OS/2, but we haven't tried the Borland DOS compiler under OS/2 yet. It was our understanding that IBM would be making an official release of this version of DPMI.SYS at some time in the future... -- netcom!proto!joe joe@proto.com
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads