HDTenEightyP/NetNews huggingface dataset:
From: ejs@borland.com (Eric Swenson)
Subject: Re: BCC TDW Doesn't Work Under Win 3.1
Organization: Borland International
Date: Thu, 9 Apr 1992 22:21:59 GMT

In article <1992Apr7.202021.17304@donner.SanDiego.NCR.COM> jim@cheers.SanDiego.NCR.COM (Jim Ruehlin) writes:
>
>Windows 3.1 SDK doesn't come with WINDEBUG.DLL like 3.0 did.  It's been renamed,
>and since I'm over 30 now I can't remember what the darn thing's called!  It
>comes with the Windows SDK for 3.1, I think.
>
>You need to get that DLL and rename it to WINDEBUG.DLL.  I found this out
>because I was a beta tester for 3.1 and some of my co-workers were using the
>3.1 SDK.
>
>Shame on Borland for not filling developers in on this!

Unfortunately, Microsoft would not allow us to violate our NDA for
Windows 3.1 in order to contact BC++ users about the TDW
incompatibility.

There is a replacement WINDEBUG.DLL available that allows TDW to run
with Windows 3.1.  You can get it from:

	Compuserve
	Genie
	Bix
	Borland BBS (408-439-9096)
	
There is a document available describing the problems and solutions.
You can get it from the above places (document number 868) as well
as through

	calling tech support
	calling our techfax number (800-822-4269) 
		request document 868

On the online systems, the file is called ti868.zip.

I'm sure it is available for FTP from somewhere, I just don't know
where.  I'm calling around to find out where it is, and I'm sure
someone will post something here describing the location.

-- Eric Swenson (Borland R&D)
From: mullens@jamsun.ic.ornl.gov (James A. Mullens)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Function export problem when porting MSC code to BC 2.0
Date: 13 Apr 92 22:12:18 GMT
Distribution: na
Organization: Oak Ridge National Laboratory

In article <92Apr10.183524edt.144354@explorer.dgp.toronto.edu>, jinli@dgp.toronto.edu (Jin Tonic Li) writes:
|> 
|> I am porting a windows app written with MSC 6.0 and SDK 3.0 to BC++ 2.0
|> The C source codes compiled fine with minor changes to associate function
|> prototypes with each individual module vs putting all of them in one 
|> .h file and include it in all module files.
|> 
|> However, the linker gives warning about exporting dialog functions:
|> 
|> 	Attempt to export non-public symbol XXXXX
|> 
|> where XXXXX is the name of the dialog function.  The dialogs are called
|> through MakeProcInstance(XXXXX, hInst) which are all listed under
|> EXPORTS in .def file.
|> 
|> I have tried the options All windows functions exportable and Explicit
|> export for BC++ 2.0  The linker still gives the same warning.
|> 

Try removing the export statements from the .DEF file, and keep the _export
on the function declaration in your code.  Remember, C++ does name mangling.

jim mullens
mullens@jamsun.ic.ornl.gov (128.219.64.31)
voice: 615-574-5564
From: runeh@sofus.dhhalden.no (RUNE HALFDAN HOLST HUSEBY)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Psychotic Dialog Box Problems! BC++ 3.0 Freak?
Date: 6 Apr 92 18:35:03 GMT
Organization: Ostfold College

In article <1992Apr3.053130.15971@cs.mcgill.ca> storm@cs.mcgill.ca (Marc WANDSCHNEIDER) writes:



>I am trying to make a modeless Dialog Box.  Thus, I did the following
>sequence of things:

>FARPROC lpDlgFn;
>HWND    hDialogb;

>lpDlgFn = MakeProcInstance (AboutFunction, hInstance);
>hDialogb = CreateDialog (hInst, "AboutBoxTemplate", hwnd, lpDlgFn);

>I am using Borland C++ 3.0, and I am using C++, so what I did was to use the
>_export keyword in the function definition:

>BOOL FAR PASCAL _export AboutFunction (blahblahblahblah); etc...

>and I still left the EXPORTS part in the .DEF file, even though I still get
>warnings about illegal attempts to export functions.

>NOW, the screwy thing, is that hDialogb = NULL whenever I try to run this 
>program, UNLESS

>Turbo C++ for Windows is running.  When that program is running, the Modeless
>Dialog box works fine, but as soon as I quit that, the handle gets set
>back to NULL again and the dialog box no trabajo!

>However, despite the fact that I am using BC++ 3.0 to compile this thing, I
>see no reason why It should be affected by the C++ windows IDE, which I have
>never used....

>Does somebody have ANY Idea what's going on...?  THis is just too weird.

>Toodles!

It could be that you need the BWCC.DLL in memory when running. Turbo C++ for 
Windows automatically loads this DLL into memory(and thus unloads it 
afterwards). To load the .DLL from your program, include a call to 
BWCCGetVersion() in the beginning of your program. It is defined in BWCC.H.

I hope this will solve your problem.

>-- 
>  storm@cs.mcgill.ca           McGill University         C program run.  Run  
>  Marc Wandschneider           Montreal, CANADA          Program run! PLEASE!
>     No Dogs were harmed in the writing of this message.  A cat got sick,
>                     somebody shot a duck, but that's it!

Rune Huseby
(runeh@sofus.dhhalden.no)
From: axb@cse.nd.edu (Arindam Banerji)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Dos drivers under Windows
Date: 15 Apr 92 10:46:55 GMT
Organization: University of Notre Dame
To: nar@math.wayne.edu (Mark Narduzzi)




The solution depends upon the direction of the communication. The
Windows app can use the DPMI interface to talk to the 
 DOS device driver ( enhanced or standard modes ) . The simplest way the
DOS device driver can communicate with the 
 windows app is to set up a shared region in low memory ( not
necessarily low, if enhanced mode is being used ), and
 let a Windows DLL poll it from time-to-time. This is not as bad as it
seems, since in enhanced mode the Windows vitual 
 machine is non-premptable, although the DOS boxes are. 

Arindam Banerji
(axb@irishvm.pcl.nd.edu)
(axb@cse.nd.edu)
(219)-239-5273

 
Newsgroups: comp.windows.ms.programmer
From: masters@cs.washington.edu (Rick Masters)
Subject: Re: DLLS sharing data between programs.
Organization: Computer Science & Engineering, U. of Washington, Seattle
Distribution: comp
Date: Thu, 16 Apr 92 19:34:58 GMT


It is completely safe to use a DLL's data segment to share
information between applications. The tricky part is
notifying the other app that new data is available.

For those of you who will receive the 3.1 SDK I encourage
you to look into the new DDEML.DLL library for using DDE
to perform interapp communication.

I hated DDE and now it is almost fun since the new library
eliminates ALL the dirty work.

DDEML is completely compatible with the older message based
DDE. You supply DDEML with a callback function and it calls
you with several informative parameters when some 
DDE thing is happening.

It also provides a nifty Abort, retry ignore dialog when
transactions are taking too long.

Rick Masters


Newsgroups: comp.windows.ms.programmer
From: ejs@borland.com (Eric Swenson)
Subject: Re: WINDEBUG.DLL and Windows v3.1
Organization: Borland International
Date: Thu, 9 Apr 1992 22:32:36 GMT

In article <645@data.rain.com> courtney@data.rain.com (Courtney Meissen) writes:
>
>Re: Using TDW with Windows 3.1, I wonder if the WINDEBUG.DLL that
>shipped with the final-beta of the 3.1 SDK would work?  Anyone
>tried this?

There is no windebug.dll in the MS Windows 3.1 SDK.  Microsoft renamed
this file cvwin.dll.  If you have the SDK, you can overwrite the 
windebug.dll in your \borlandc\bin directory with the cvwin.dll that
comes from the sdk.  This will make tdw happy.  You can also get an
updated version of windebug.dll from various places (Genie, Bix,
Compuserve, Borland Tech Support, Borland BBS, Internet, etc.)

-- Eric
Newsgroups: comp.windows.ms.programmer
From: pmoore@hemel.bull.co.uk (Paul Moore)
Subject: displaying postscript
Organization: Bull HN UK
Date: Thu, 16 Apr 92 11:04:23 GMT

Is there out there any code that will let me display postscript - I mean that
I have a ps file and need to show it to the user. (A free standing utility
is no good - i need to build it into a program).

Is there a C library - a DLL - or maybe a .DRV (you could see this as a request
for a display postscript screen driver!).

Source would be nice too - and I dont mind paying - i.e. it could be a 
commercial product.

PS How about the same for PCL?

PPS This is for Windows not DOS.
-- 
!---------------------------------------------------------------!
! Paul Moore, Bull HN UK, Maxted Rd,Hemel Hempstead, HP2 7DZ.   !
! Phone:(44) 442 232222  Fax:(44) 442 234084			!	
! pmoore@hemel.bull.co.uk     "a smile, a song and a core dump" !
Newsgroups: comp.windows.ms.programmer
From: clay+@cs.cmu.edu (Clayton Bridges)
Subject: Wierdness and Bugs in Borland Products
Date: Thu, 09 Apr 92 20:31:20 GMT
Organization: School of Computer Science, Carnegie Mellon

I've got some strange problems with BC++ 3.0 and TPW. If anyone knows
a net address where I could send for help, please forward it to me.
Here are some of my problems. Post if you have solutions to these, or
similar problems.

* TDW -- I'm trying to track an Exc. 13 bug in some code which also
uses the 80x87. Whenever I try to trace into the code, I get a
"terminated, exit code 0", whenever I hit an fwait (with the 80x87
stack empty).  And when I don't trace into the code, I get the
Exception 13. Not fun.

* TCW, TPW -- The Borland-style dialog boxes are hosed in Win31. Is
there a bug fix to this or what? In addition, these guys really can't
handle the new font scheme very well.

* TCW -- the moving windows problem: I'll iconify a window in TCW, and
when I bring it back, it "disappears"; that is, it gets deiconified to
some random place on this huge TCW desktop (my only hint this was true
is that scroll bars get added to the desktop). Since I don't want to
spend 30 minutes in nowhere land looking for my window, I am forced to
cascade or tile the windows to get my "lost" window back to the "main"
part of the desktop.
From: wan@pollux.usc.edu (Qiang Wan)
Newsgroups: comp.windows.ms.programmer
Subject: MS MDI question
Date: 16 Apr 1992 13:28:15 -0700
Organization: University of Southern California, Los Angeles, CA
Distribution: usa
NNTP-Posting-Host: pollux.usc.edu

I started to write an MDI (Multiple Document Interface) application under
MS Window 3.0, using Borland C++. I encountered the following problems:

1. According to MS Windows reference manual pages on MDICREATESTRUCT,
 a child window in MDI has four valid window styles: WM_MINIMIZE,
 WM_MAXIMIZE, WM_HSCROLL, and WM_VSCROLL. The problem is that I could not
 get the scroll-bars to appear at all, while the minimize and maximize
 styles seem to work OK.
 The MS Windows programming guide shows some MDI child windows bearing
 scroll-bars. I wonder if people who have MS SDK package could verify for
 me if these scroll-bars were created by setting the window style in
 the MDICREATESTRUCT style field, or by calling CreateWindow's.

2. I registered a window class for the MDI child windows with CS_NOCLOSE set,
 which is supposed to suppress the WM Close button in the window pulldown
 menu. This doesn't seem to work either. The Close button is always shown.
 Hope some netters would have some suggestion on this. Thanks in advance.

Ching Wan
From: pierced@clvax1.cl.msu.edu (DOUG PIERCE CPS115)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Can not compile owl.h with TC++ 3.0.
Date: 8 Apr 92 14:26:46 GMT
Reply-To: pierced@clvax1.cl.msu.edu
Organization: NASA Goddard Space Flight Center - Greenbelt, MD, USA
News-Software: VAX/VMS VNEWS 1.3-4

In article <1992Apr6.160529.15456@aber.ac.uk>, rjt8@aber.ac.uk (Richard James Taylor) writes...
> 
>   We recently upgraded from BC++ 2.0 to BC++ 3.0. We already had the OWL libraries and these worked fine with BC++ 2.0.
> 
>   When we tried to compile an application that used owl.h we got errors from the compiler. We thought it might be somthing in our application but we found that
>even the example program step1.cpp would not compile. We tried BC++ 3.0 and
>TC++ 3.0 without success. The errors from the compiler are as follows.
> 
..

There is an OWL upgrade that you should receive (for free) with your BC++ 3.0
upgrade.  The older OWL libraries may somehow be persuaded to work, but it
is easier to get the new ones... no doubt there are some fixes in there too.


   Doug Pierce                   |  "Truth is a virus."
   College of Human Medicine     |      -- Hard Harry, 
   Michigan State University     |          'Pump up the Volume'
   pierced@clvax1.cps.msu.edu
Newsgroups: comp.windows.ms.programmer
From: kting@cse.unl.edu (Kea Ting)
Subject: Actor 3.0
Organization: University of Nebraska - Lincoln
Date: Mon, 13 Apr 1992 06:08:54 GMT

   I have a Actor 3.0 for sale. I want to sale it for $70.00. If interested
please mail me.




soon.

From: privat@hpcc01.corp.hp.com (Jim Privat)
Date: Fri, 10 Apr 1992 18:20:58 GMT
Subject: Re: How to Scroll?
Organization: the HP Corporate notes server
Newsgroups: comp.windows.ms.programmer

> Please help me. It is very important for my thesis.

Your thesis?  Isn't that supposed to be straight from your *own*
brain?  Good luck.
Organization: Central Michigan University
Date: Tuesday, 14 Apr 1992 17:38:43 EDT
From: Brent Langdon <32JJCB3@CMUVM.CSV.CMICH.EDU>
Newsgroups: comp.windows.ms.programmer
Subject: Re: VisualBasic / VAX SQL/Server ??


>I'am tyring to get a Visual-Basic program runnin against VAX/VMS

I know this has nothing to do with windows programming, but has anyone
else found it funny that thier are so many beefed up BASIC compilers
out there.  Nothing personal, but I thought that BASIC written to be
an instructional language and not for full fledged programming.


                                    Just my opinion,
                                    Brent Langdon
                                    Central Michigan University
Newsgroups: comp.windows.ms.programmer
From: aa596@cleveland.Freenet.Edu (Peter Haller)
Subject: Re: MS MDI question
Reply-To: aa596@cleveland.Freenet.Edu (Peter Haller)
Organization: Case Western Reserve University, Cleveland, OH (USA)
Date: Thu, 16 Apr 92 23:46:47 GMT


In a previous article, wan@pollux.usc.edu (Qiang Wan) says:

>I started to write an MDI (Multiple Document Interface) application under
>MS Window 3.0, using Borland C++. I encountered the following problems:
>
>1. According to MS Windows reference manual pages on MDICREATESTRUCT,
> a child window in MDI has four valid window styles: WM_MINIMIZE,
> WM_MAXIMIZE, WM_HSCROLL, and WM_VSCROLL. The problem is that I could not
> get the scroll-bars to appear at all, while the minimize and maximize
> styles seem to work OK.
> The MS Windows programming guide shows some MDI child windows bearing
> scroll-bars. I wonder if people who have MS SDK package could verify for
> me if these scroll-bars were created by setting the window style in
> the MDICREATESTRUCT style field, or by calling CreateWindow's.
You must call SetScrollRange() with the ranges not equal to each other.
This forces the scroll bars to be drawn.

PCH
-- 
Peter C. Haller				|	'If you do what you 
Imagination Processing Systems		|	have always done,
aa596@cleveland.Freenet.Edu 		|	expect what you have
"Are we having fun yet?"		|	always recieved.'
Newsgroups: comp.windows.ms.programmer
From: masters@cs.washington.edu (Rick Masters)
Subject: Re: Dialog Box message loops
Organization: Computer Science & Engineering, U. of Washington, Seattle
Distribution: usa
Date: Thu, 16 Apr 92 19:16:13 GMT

Jeff Witzer:

You write that have been checking a communications port
inside your applications PeekMessage loop. I suggest
that you set a timer and check the port every time
you get a WM_TIMER message. In this way you have more control
over how often you check the port.

If you use your message loop, you may run into problems
because when your application yields you may not get
another message for a long time. The only way around
this is to not yield correctly which I suspect you
may be doing if you are using PeekMessage instead
of GetMessage in your main application's message loop.

Rick Masters

P.S. My first post. No scathing flames please.
Newsgroups: comp.windows.ms.programmer
Subject: VB: Combo Box, Click Event
From: sturgeon_c@eis.dofasco.ca
Date: 8 Apr 92 13:17:46 GMT
Organization: Dofasco Inc, Hamilton, Ont. Can.
Nntp-Posting-User: sturgeon_c

VB question--Does anyone know why a combo box recognizes a Click event when
the user selects an item from it's list, even if that selection was via the
keyboard?  (Pg. 139.. Programmer's Guide.)
-- 
____________________________________________________________________________

Craig Sturgeon
(sturgeon_c@eis.dofasco.ca)

Dofasco Steel Inc.                                          100 Lyons Ave.,
1330 Burlington St. East                                 Brantford, Ontario
Hamilton, Ontario                                           Canada  N3R 4R4
Canada  L8N 3J5
(416) 548-4420
____________________________________________________________________________
Newsgroups: comp.windows.ms.programmer
From: zong@huey.huji.ac.il (Yaniv Azriel)
Subject: porting to windows
Organization: Mail to News Gateway
Date: 10 Apr 92 07:33:37 GMT

I have a plain ms-dos application, which needs a series face-lift.
I am considering, in accordance with the new wave that seems to be sweeping the PC world,
to rewrite it for windows. I have several questions:

i) My application needs to gets regular interrupts (100Hz) from a hardware board.
   Does window 3.0 (3.1 ??) intercept these interuupts and hence make interrupt
   using in windows impossible ??
ii) My application among other things simulates a CRO tube (like heart rate hospital
    monitors). Most of the work is currently done using individual pixel manupilation,
    which on a 386 only barely runs fast enough. Will porting to window greatly increase
    the time taken to handle this sort of graphic ??
iii) Finally - i have literally already put out a purchase order for:
     BC ++ v3 and application framework, when i a book on windows mentioned the
     need for the MicroSoft SDK or Borland's OWL. Does the above package include
     the neccesary bits&pieces to develop windoew applications ???

I would appreatiate any informarion on these topics.

------------------------------------------------------------------------------------------
Yaniv Azriel	|	zong@cs.huji.ac.il	/ 	I will think of something..  
-------------------------------------------------------------------------------------------
From: bjorn@ludd.luth.se (Bjorn Fahller)
Newsgroups: comp.windows.ms.programmer
Subject: Internationalizing DLL uploaded
Date: 8 Apr 92 16:40:29 GMT
Organization: Lule} H|gskolas datorf|rening ( Ludd )

The INTL package, a DLL for internationalizing win3.x applications is uploaded
to garbo.uwasa.fi (/pc/win3/incoming) and nic.funet.fi (pub/msdo/incoming).
I don't know of any US site now when cica is down, but let me know, and I'll
upload it there too.
   _
/Bjorn.
From: skrause@hubinf.UUCP (Steffen Krause)
Newsgroups: comp.windows.ms.programmer
Subject: Re: File size limit ?
Summary: Edit Control allocates local heap
Keywords: Edit Controls
Date: 9 Apr 92 09:22:34 GMT
Followup-To: <1992Apr2.170151.3597@kodak.kodak.com>
Distribution: comp.windows.ms.programmer
Organization: FB_16

Sure edit controls ( and TFileWindow built on top of it) have a limit of 
about 32KByte of text. The reason is that edit controls allocate their
buffer from the program's local (!) heap, which is only up to 64 kByte in
size. So if you have a lot of the local heap allocated, edit controls even
may have a smaller limit.
To avoid this problem you have to write your own edit window.

Steffen Krause  skrause%hp832@hubinf.informatik.hu-berlin.de
Newsgroups: comp.windows.ms.programmer
From: pbh@athena.mit.edu (Paul B Hill)
Subject: fatal exit code 0x0506 ?
Organization: Massachusetts Institute of Technology
Date: Fri, 17 Apr 1992 15:22:19 GMT

Does anyone know what fatal exit code 506 means? When I look it up in the 3.0 SDK
manual I don't find it. My manual skips from 505 to 600.

Paul B. Hill
pbh@mit.edu
From: emartins@uxh.cso.uiuc.edu (Eduardo Martins)
Newsgroups: comp.windows.ms.programmer
Subject: Re: SDK 3.1
Keywords: SDK
Date: 14 Apr 92 03:59:16 GMT
Organization: University of Illinois at Urbana

ddoherty@ics.uci.edu (Donald Doherty) writes:

>In article <1992Apr13.100123.6976@news.cs.indiana.edu> guthrie@iuvax.cs.indiana.edu (Stephen Guthrie) writes:
>>
>>   Has anyone paid the $150 for the SDK 3.1 manuals?  
>>   Was is worth it?  Necessary? 	

>I haven't seen the manuals yet but I beta tested without them.  There is a
>lot of online help so they shouldn't be necessary (although I will probably
>order them anyway since I like docs :^) ).

Man, you'll be a happy puppy when you get the 3.1 SDK. I ordered mine today,
and it'll come with over 5,000 pages of docs (something like 13 books  
altogether)!!! Guess it's time to buy a new shelf... :-)

BTW, if you beta-tested the SDK, don't buy anything yet. You should have
received, or will receive soon, a GREAT offer from MicroSoft in the mail.

--
******************************************************************************
| Eduardo Martins                            | Internet:   emartins@uiuc.edu |
| Regional Economics Applications Laboratory | Bitnet:     emartins@uiucvmd  |
| University of Illinois at Urbana-Champaign | CompuServe: 73300,267         |
******************************************************************************
Newsgroups: comp.windows.ms.programmer
From: mccreary@sword.eng.hou.compaq.com (Ed McCreary)
Subject: Re: grey scales on a color monitor?
Organization: Compaq Computer Corp.
Date: Wed, 15 Apr 1992 17:58:57 GMT

In article <2728@fedfil.UUCP> news@fedfil.UUCP (news) writes:
>I've got another strange problem here...  I need to get a grey-scale
>effect on color monitors (customer demands it...)   
>

What are you using to display the image?  Is it SetDIBitsToDevice or
are you using BitBlt?  

You may be having trouble since you are using a logical palette with
256 entries.  What video card are you using?  Is it SuperVGA?  This
guy will only support 64 levels of grey scale so you should set your
palette to something like

   for(i=0;i>64;i++)
    {
     grey = 4*i;
     ...set RGB values to grey...
    }

I've never tried using a 256 entry palette before and don't know what
the implications may be.  I *have* used a 64 entry palette before and
have had no trouble.




--
McCreary@sword.eng.hou.compaq.com     Computers are like Old Testament gods;
Me? Speak for Compaq?  Yeah, right.   lots of rules and no mercy.
                                                             Joseph Campbell
From: freyer@hauk.hsr.no (Freyer, Stle)
Newsgroups: comp.windows.ms.programmer
Subject: VB and API calls to 3.1 (Open file, etc)
Keywords: VB, API, Open File, 3.1
Date: 14 Apr 92 11:19:16 GMT
Organization: Rogaland University Centre


At the moment I am not able to recall where I read it, but someone stated 
that the win3.1 would have standard routines for opening (or rather: 
selecting) files.

Is there a new API.TXT (ver 3.1) to use with VB, with these routines
(assuming they exist) included?

* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - *
| Staale Freyer               | E-Mail: freyer@hsr.no                       |
| Rogaland University Centre  | Tel: +47-4-874100(exchange)                 |
| Ullandhaug,N-4004 Stavanger | Tel: +47-4-874419(direct), Fax: +47-4-874300|
* - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - *
Newsgroups: comp.windows.ms.programmer