HDTenEightyP/NetNews huggingface dataset:
From: beross@shelley.u.washington.edu (Ben Ross)
Subject: Re: VisualBasic / VAX SQL/Server ??
Organization: University of Washington, Seattle
Date: Wed, 15 Apr 1992 07:17:58 GMT

In article <92105.17384432JJCB3@CMUVM.CSV.CMICH.EDU> Brent Langdon <32JJCB3@CMUVM.CSV.CMICH.EDU> writes:
>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.

It seems that Microsoft has a vision for its corner of the world, a vision
in which there are only two languages used: C and BASIC.  C is for any
serious project, and BASIC is for the uneducated masses.  (Note that
Microsoft's corner of the world consists of Windows).  Not a bad vision,
if you ask me: BASIC seems to be understandable to most beginning computer-
ites, and C is not a half bad language (no flames please: I develop almost
exclusively in C/C++).  Anyway, because of that Microsoft has been really
pushing BASIC.  The other people (and I have only seen two actual BASIC
compilers for DOS, but I have not looked all that carefully) saw a need 
(or thought they did) and filled it.  For a new programmer who is sick of
GWBASIC, a compiled BASIC is both cheap and easy.  Let us take a moment to
pity the poor souls..... :-)

Ben Ross
(beross@u.washington.edu)



Newsgroups: comp.windows.ms.programmer,comp.os.msdos.programmer
From: dt@dhw68k.cts.com (Donald Toy)
Subject: Programming Windows Apps
Followup-To: dt@dhw68k.cts.com
Organization: Wolfskill & Dowling residence; Anaheim, CA (USA)
Date: Thu, 16 Apr 1992 23:52:01 GMT

I'm sorry if this is a FAQ but I need information regarding a possible
port of a DOS pseudo-database application to a Windows version. I need
to know:

1) Best development environment
2) Programming languages support
3) Windows shell programs that will help jumpstart programming interface.
4) Compatibility of using DBase program libraries in Windows.
5) Any tips or techniques to come up to speed quickly on Windows.
6) Reference materials.

If there is enough interest, I will post a summary to this newsgroup. Please
send responses to me (dt@dhw68k.cts.com) as I don't get a chance to read
these newsgroups regularly.

-- 
----------------------------------------------------------------------------
Donald D. Toy				Anaheim, CA				
uucp: ...{spsd,zardoz,felix}!dhw68k!dt		InterNet: dt@dhw68k.cts.com
----------------------------------------------------------------------------
Newsgroups: comp.windows.ms.programmer
From: iam@stiatl.salestech.com (Ian Mercado)
Subject: Possible to get chars 0x01-0x1f in a single line edit??
Organization: Sales Technologies, Inc.
Date: Tue, 14 Apr 1992 15:20:24 GMT

We're developing an application that needs to be able to display (and have
the user enter) ANY character from the OEM fixed font into a single-line
edit.  Unfortunately for our hapless application, I seem to be having
the worst time trying to get a single-line edit to accept and display
any of the characters from 0x01-0x1f.  Has anyone out there successfully
done this with a single-line edit or devloped their own control to do
such?  If so, I'd appreciate any insight you might have into this matter.

Thanks,

Ian

-- 
--------   ----   ----   --    |   Ian Mercado: iam@salestech.com             |
   --     -    -  -----  --    |                emory!slammer!stiatl!iam      |
   --    -------- --  -----    |                                              |
-------- --    -- --   ----    |            "I'd rather be flying."           |
Newsgroups: comp.windows.ms.programmer
From: mccreary@sword.eng.hou.compaq.com (Ed McCreary)
Subject: Re: Doc for Win 3.1 features
Organization: Compaq Computer Corp.
Date: Fri, 10 Apr 1992 13:26:50 GMT

In article <JKF.92Apr8064801@frisky.Franz.COM> jkf@Franz.COM (Sean Foderaro) writes:
> I've got a C compiler and windows SDK for Windows 3.0 and now Windows 3.1 
>comes out with lots of neat new things that I'd like to use
>(e.g. TrueType, Dialog boxes, object linking).   Where do I find the 
>'manual pages' (to use a unixism) for these new functions?   Do I have to 
>buy a new SDK or C compiler???  I'm sure that 99% of windows purchasers don't 
>care about writing windows programs and that is why the documentation isn't
>provided with the software, however there *should* be an easy way to 
>get it (I would hope).  
>

You'll need to get the new SDK to access the new calls and dialog boxes.
I'm not sure about availabilty though.  Since you have the 3.0 SDK,
call Microsoft and ask about the upgrade path.  I know they have a 
1-800 number, I just don't know it off hand.

--
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: richardh@hpopd.pwd.hp.com (Richard Hancock)
Date: Thu, 16 Apr 1992 10:23:25 GMT
Subject: Re: Dos drivers under Windows
Organization: The Duffer of St. George
Newsgroups: comp.windows.ms.programmer

/ hpopd:comp.windows.ms.programmer / axb@cse.nd.edu (Arindam Banerji) / 11:46 am  Apr 15, 1992 /

>[stuff deleted] This is not as bad as it
>seems, since in enhanced mode the Windows vitual 
>machine is non-premptable, although the DOS boxes are.

I think I know what you mean, but just in case anyone else
is confused, what I think you mean (to say) is that
pre-emption occurs at the virtual machine level but not at
the Windows app level.

In other words, virtual machines are
pre-emptively multitasked (by default) but Windows apps are
only ever non-pre-emptively multitasked (ie. a Windows app
must yield the processor for another Windows app to run).

While DOS apps each run in their own virtual machine, all
Windows apps run in the same virtual machine.
From: ccstb@gdt.bath.ac.uk (T Barry)
Newsgroups: comp.windows.ms.programmer
Subject: Multiple DOS sessions updating the screen
Date: 14 Apr 92 10:08:23 GMT
Organization: Bath University Computing Services, UK

Can anyone help me with this problem?

I have a DOS application that provides an enhanced console for an X.25 switch.
Running this in a window works file.

However what I really want to do is have two windows, each running a copy of
the program, executing at the same time. The comms software I am using handles
the multiplexing of the comms sessions but only the currently active window
is updated. Is there a way of having two DOS windows being updated concurrently?
Do I have to convert my application to a Windows application to be able to
do this?

Any help would be appreciated.

thanks

Trevor
-- 
Trevor Barry.				  | Phone: +44 225 826025
UUCP : ...!ukc!gdr!ccstb		  | Post : B.U.C.S
DARPA: ccstb%gdr.bath.ac.uk@cs.ucl.ac.uk  |        University of Bath
JANET: ccstb@uk.ac.bath.gdr		  |        Bath, BA2 7AY, England.
Xref: sparky comp.windows.ms.programmer:5408 comp.windows.ms:12631
From: nhj@flopsy.cs.bham.ac.uk (Nick Jurascheck)
Newsgroups: comp.windows.ms.programmer,comp.windows.ms
Subject: Re: Unwanted Multitasking!!
Date: 13 Apr 92 15:12:49 GMT
Organization: Birmingham University Computer Science

In article <1992Apr10.133656.28981@ugle.unit.no> jlongva@Siri.Unit.NO
(J|rgen Longva) writes:

> I'm writing a windos-program that must call external .exe-files during
> it's runtime. I use WinExec(...) to do this, but there is a small prob-
> lem with this method: the Windows program does not stop!
> 
> The external routine must pass data back to the windows-program, and I
> use the hard disk as a buffer:
> 
>   // Executes the external routine.
>   if (WinExec("routine.exe", SW_HIDE) < 32)
>     --> Error
> 
>   // Reads the information returned by the external routine.
>   if ((file = _open("info.txt", O_RDWR)) == -1)
>     --> Error
> 
>   ...
> 
> The problem is that the main-program continues to run - and reaches the
> line where I open the result-file too early. I've made a .pif-file for
> the externl routine that checks the "Exclusive"-flag for priority.
> 
> How can I check when the external routine is finished? Is there an al-
> ternative to WinExec(...) (the LoadModule(...) does only work for win-
> dows .exe-files)?

I have done this successfully by using FindWindow to check when
"routine.exe" has terminated.  The code (from memory) looks something like:

	WinExec("routine.exe", SW_HIDE);
	while(FindWindow(NULL, "routine.exe", ...) != NULL)
	{
		; /* Wait until routine.exe terminates... */
	}
	/* Now process the file created by routine.exe: */
	.
	.

I also tried checking for existence of the file created, but this
caused some problems with Win 3.0.

Hope this helps,
	
	Nick 

JANET: JurascheckNH@cs.bham.ac.uk  |  UUCP: ...!mcvax!bhamcs!JurascheckNH
BITNET: JurascheckNH%cs.bham.ac.uk@ukacrl.bitnet
INTERNET: JurascheckNH%cs.bham.ac.uk@cunyvm.cuny.edu
-- 
Nick			
JANET: JurascheckNH@uk.ac.bham.cs  |  UUCP: ...!mcvax!bhamcs!JurascheckNH
BITNET: JurascheckNH%cs.bham.ac.uk@ukacrl.bitnet
INTERNET: JurascheckNH%cs.bham.ac.uk@cunyvm.cuny.edu
Newsgroups: comp.windows.ms.programmer
From: ursb@bernina.ethz.ch (Urs Beckmann)
Subject: Re: How to select a font with size in points? - HELP
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Date: Tue, 7 Apr 1992 17:18:52 GMT

In article <266570021@hpopd.pwd.hp.com> richardh@hpopd.pwd.hp.com (Richard Hancock) writes:
>/ hpopd:comp.windows.ms.programmer / tonym@polari.com /  2:29 pm  Apr  2, 1992 /
>
>
>Try this out. Create a DC for the printer. Set the mapping mode to MM_TWIPS.
>Enumerate all the available fonts. Choose one of these fonts and use
>CreateFontIndirect() to create a HFONT using the lpLogFont passed during the
>enumeration. Terminate the enumeration. Select the font into the DC for the
>printer. Get the text metrics of the font.
>
>You should find that the text metrics DO NOT match those passed during the
>enumeration.
>

My experience with postscript printer driver and Courier Font was, that the matching
didnt work for MM_TEXT nor MM_TWIPS. The resulted Fontsize from TextMetrics
was smaller than the desired one from LOGFONT-structure.
An interesting additional fact is that internalleading and external leading were
both zero for this font.
What worked for me was modifying the LOGFONT-structure after EnumFonts().
The desired fontsize is entered directly into LOGFONT:
lf.lfHeight=-20*12;	(Assuming 12 pts-font and MM_TWIPS-mode)

The miracle is that you really get a 12 pts font on paper.

>>Point size generally refers to line height not character height, so you do not
>>need to subtract the internal leading.
>
>Not according to Petzold, and not according to my own experience with
>LaserJets.

Internal leading is not included in pointsize. The printerdriver handles this
correctly if lf.lfHeight has a negative value.


Urs

-----
U. Beckmann	Rechenzentrum der ETH Zuerich	Switzerland

Newsgroups: comp.windows.ms.programmer
From: chris@debra.dgbt.doc.ca (Chris Justus)
Subject: Where can I get more Windows fonts for MS-C 6.0
Organization: Communications Research Centre, Ottawa, Canada
Date: Wed, 8 Apr 1992 13:25:43 GMT


Ok... I've asked this question in comp.msdos.programmer and comp.fonts
(??) but so far I haven't been able to get a great response.

I writing a program with MS-C 6.0 that uses the fonts that are
included with MSC.  The problem is that there is only 6 of them, and
I'd like to find some more (and maybe better) ones.  Some of the
windows fonts work (all of the crumby CGA ones...) but any font file
over 50K or so is just garbage.  Does anyone know where I can get more
fonts and/or why some of the windows fonts don't work???
Thanks in Advance

-- 
                   Chris Justus      chris@debra.doc.ca     

Co-Op Student at Communications Research Centre, Communications Canada, Ottawa
From: rjt8@aber.ac.uk (Richard James Taylor)
Newsgroups: comp.windows.ms.programmer
Subject: Can not compile owl.h with TC++ 3.0.
Date: 6 Apr 92 16:05:29 GMT
Organization: University College of Wales, Aberystwyth


   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.


Compiling STEP1.CPP:
Warning ..\..\INCLUDE\TCOLLECT.H 18: Style of function definition is now obsolete
Error ..\..\INCLUDE\TCOLLECT.H 18: Multiple declaration for 'Pvoid'
Warning ..\..\INCLUDE\TCOLLECT.H 19: Style of function definition is now obsolete
Error ..\..\INCLUDE\TCOLLECT.H 19: Multiple declaration for 'Pvoid'
Error ..\..\INCLUDE\TCOLLECT.H 22: Undefined symbol 'Pvoid'
Error ..\..\INCLUDE\TCOLLECT.H 22: Not an allowed type
Warning ..\..\INCLUDE\TCOLLECT.H 22: Division by zero
Error ..\..\INCLUDE\TCOLLECT.H 36: Type name expected
Error ..\..\INCLUDE\TCOLLECT.H 36: Declaration missing ;
Error ..\..\INCLUDE\TCOLLECT.H 37: 'Pvoid' cannot start a parameter declaration
Error ..\..\INCLUDE\TCOLLECT.H 41: 'Pvoid' cannot start a parameter declaration
Error ..\..\INCLUDE\TCOLLECT.H 43: 'Pvoid' cannot start a parameter declaration
Error ..\..\INCLUDE\TCOLLECT.H 46: ) expected
Error ..\..\INCLUDE\TCOLLECT.H 47: ) expected
Error ..\..\INCLUDE\TCOLLECT.H 48: 'Pvoid' cannot start a parameter declaration
Error ..\..\INCLUDE\TCOLLECT.H 52: Type name expected
Error ..\..\INCLUDE\TCOLLECT.H 52: Multiple declaration for 'Pvoid'
Error ..\..\INCLUDE\TCOLLECT.H 52: Declaration missing ;
Error ..\..\INCLUDE\TCOLLECT.H 53: Type name expected
Error ..\..\INCLUDE\TCOLLECT.H 53: Multiple declaration for 'Pvoid'
Error ..\..\INCLUDE\TCOLLECT.H 53: Declaration missing ;
Error ..\..\INCLUDE\TCOLLECT.H 54: ) expected
Error ..\..\INCLUDE\TCOLLECT.H 66: Type name expected
Error ..\..\INCLUDE\TCOLLECT.H 66: Multiple declaration for 'Pvoid'
Error ..\..\INCLUDE\TCOLLECT.H 66: Declaration missing ;
Error ..\..\INCLUDE\TCOLLECT.H 74: 'Pvoid' cannot start a parameter declaration
Error ..\..\INCLUDE\TCOLLECT.H 85: 'Pvoid' cannot start a parameter declaration
Error ..\..\INCLUDE\TCOLLECT.H 87: 'Pvoid' cannot start a parameter declaration
Error ..\..\INCLUDE\TCOLLECT.H 87: Too many error or warning messages

   I am new to windows, BC++ and PC's in general, so I do not understand what is
happening here. I have tried everything I can think of.

Any ideas would be greatly appreciated.

Richard Taylor

rjt8@uk.ac.aber
Newsgroups: comp.windows.ms.programmer
Subject: Re: BorDlgs in 3.1
From: rocker@desire.wright.edu
Date: 12 Apr 92 19:13:22 EST
Organization: Wright State University 

In article <1992Apr10.142752.27495@wuecl.wustl.edu>, wilcox@wucs1.wustl.edu (Don Wilcox) writes:
> Am I the only one to see this problem (I posted a couple of days ago and got
> nothing).  Under 3.1, all my BorDlgs are mis-sized.  I also noticed that the
> one in Borland RW were wrong as well.  The strange thing is, when I edit my
> dialogs in RW, they look okay.
> 

	On a related subject, I've noticed that all of TPW's dialog (options,
file|Open compiling...) are REALLY messed up under SVGA resolution.

> I'd call Borland's tech support number, but I haven't the $$$ to wait on hold
> all morning.
> 
	I find calling at 10:30am ET  works fairly well.


> Don
> Don Wilcox                         | "For I am not ashamed of the Gospel of
> Washington University in St. Louis |   Christ, for it is the power of salvation
> email: wilcox@cs.wustl.edu         |   to all who believe."

rock hhard
From: jcmorris@mwunix.mitre.org (Joe Morris)
Newsgroups: comp.windows.ms.programmer
Subject: Microsoft Test: Has anyone tried it?
Keywords: windows, testing
Date: 17 Apr 92 12:45:32 GMT
Article-I.D.: mwunix.jcmorris.703514732
Organization: The MITRE Corporation

I recently received a solicitation from Microsoft to buy their new product
"Microsoft Test".  The abstract on the glossy reads:

  Automate the testing of your applications for the Windows operating system
  with Microsoft Test for Windows.  It makes comprehensive testing easier,
  reduces testing costs, and helps you validate the quality of software
  as you write it, so that you can deliver better applications for 
  Windows in less time.

Microsoft's price in the flyer is $299 plus tax and $7.50 shipping.

Since the net usually has already developed several long threads before
I receive an order form from Microsoft, I'm surprised that I haven't
seen any discussion of the product.  Does anyone have some experience
to share?

Joe Morris
From: conrozi@kk188.ericsson.se (Roman Zielinski TT/TSM)
Newsgroups: comp.windows.ms.programmer
Subject: TDW patches to win3.1
Date: 14 Apr 92 07:31:22 GMT
Distribution: comp
Organization: Ericsson

There was a mail in friday that the following files
has been uploaded to simtel
/PDGET MAIL pd:<msdos.turbo-c>TDWIN31.ZIP UUENCODE
/PDGET MAIL pd:<msdos.turbo-c>TI868.ZIP UUENCODE

I tried to fetch them from LISTSERV@VM1.NoDak.EDU
but they are not there. Probably the mirror update
at simtel has not catched them yet.

Is there any other mailserv containing these files
somewhere????? I need them urgently.

/Roman
Newsgroups: comp.windows.ms.programmer
From: emartins@uxh.cso.uiuc.edu (Eduardo Martins)
Subject: Re: Standard file management dialogs?
Organization: University of Illinois at Urbana
Date: Mon, 6 Apr 1992 17:51:15 GMT

steve@monu6.cc.monash.edu.au (Steve Balogh (+61 3 565 4747)) writes:

>In article <1992Apr2.053330.18656@smsc.sony.com> dce@smsc.sony.com (David Elliott) writes:
>>Are there any "standard" file "open" and "save as" dialogs and
>>code around?  I don't mind writing a set, but it seems to me
>>that if MicroSoft wanted people to make their applications look
>>similar, a standard dialog would be a good idea.
>>
>>In case it matters, I'm using QuickC for Windows and Case:W (Corporate).

>You could always use rx.exe (available on cica) to extract the required
>dialog boxes from an MS Windows product (eg Write) and use that. Not sure
>what the copyright implications are for using standards in this manner! :-(

Windows 3.1 includes a COMMDLGS.DLL, which contains exactly what you want = 
a common set of dialogs and routines to open and save files. Take a look at
Word for Windows 2.0, for example, and you'll see what they look like. Also,
Borland's ObjectWindows has a different set of routines, with a different
look and feel, called STDDLGS.

--
******************************************************************************
| 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: kmcnabb@pcserver2.Naitc.Com (Keith McNabb)
Subject: NEED HELP - Visual Basic Memory Problem
Organization: A. C. Nielsen Co., Bannockburn, IL
Distribution: na
Date: Wed, 8 Apr 92 21:48:05 GMT

One of our software development groups is experiencing a problem in
exhausting global memory in a Visual Basic program.  Granted, a memory
error is so often not the real, underlying culprit.  However, has
anyone run into memory problems using Visual Basic and found ways to
solve them?  Something like a "Ten Greatest Hits" of causes and
solutions (or a recommended technical source) would be so much
appreciated.

Keith McNabb
kmcnabb@nis.naitc.com
From: sinster@cse.ucsc.edu (Darren Senn)
Newsgroups: comp.windows.ms.programmer
Subject: Re: BorDlgs in 3.1
Date: 13 Apr 92 19:56:45 GMT
Organization: University of California, Santa Cruz (CE/CIS Boards)

In article <1992Apr10.142752.27495@wuecl.wustl.edu> wilcox@wucs1.wustl.edu (Don Wilcox) writes:
>Am I the only one to see this problem (I posted a couple of days ago and got
>nothing).  Under 3.1, all my BorDlgs are mis-sized.  I also noticed that the
>one in Borland RW were wrong as well.  The strange thing is, when I edit my
>dialogs in RW, they look okay.

I'm using 3.1 as well, and I don't have problems.  It might be that your
system font is messed up.  The system font determines the size of a
dialog unit.  Are you using a Windows 3.1 or 3.0 display driver?
-- 
Darren Senn                                            Phone:    (408) 479-1521
sinster@scintilla.capitola.ca.us                       Snail: 1785 Halterman #1
Wasurenaide -- doko e itte mo soko ni anata wa iru yo.     Santa Cruz, Ca 95062
Newsgroups: comp.windows.ms.programmer
From: mmshah@im.lcs.mit.edu (Milan Shah)
Subject: Re: Goodbye UAE?
Organization: MIT Lab for Computer Science
Date: Tue, 14 Apr 1992 19:13:55 GMT



  Or can we? Just because the message is gone, doesn't mean that a new
  UAE dialog isn't out there, waiting. 

I can't believe how badly misunderstood this 'No UAE' business has. Pray,
tell me, as a programmer, how in hey do you expect *any* OS to detect 
and correct an error in an application? What do you want Windows to do
when you dereference a Null pointer?

UAE's were terrible because of the following - an application error would
not be detected at the time of the error, but would manifest itself later
on at seemingly completely random times. So for example, Program A could
do something illegal (like delete a resource not belonging to it), things
would continue fine, and then later on, Program B, owner of resource, 
dies with UAE. Now, the poor programmer of Program B is trying to figure 
out what s/he did wrong. (This is probably a bad example, but you get the
point)

The GPF flags an error when it occurs, so that the fault is correctly 
identified to be with Program A.

The following program will die under every OS of the past, present, and
future: whether you call it UAE, GPF, segmentation fault, bus error, or
whatever. 

void main()
{
	int *pnCrash;

	pnCrash = 0;
	*pnCrash = 1;
}

The big improvement in Windows is not that UAE's don't occur (they *must*,
if there is an error in the user program), but that they are *detected*
correctly and at the time the error occurs.

Milan


Newsgroups: comp.windows.ms.programmer,comp.lang.c++
From: sidney@borland.com (Sidney Markowitz)
Subject: Re: BCC TDW Doesn't Work Under Win 3.1
Organization: Borland International
Date: Fri, 10 Apr 1992 00:04:53 GMT

ejs@borland.com (Eric Swenson) writes:
>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:
[...]
>There is a document available describing the problems and solutions.
[...]
>	calling our techfax number (800-822-4269) 
>		request document 868
>On the online systems, the file is called ti868.zip.

I'll upload TI868.ZIP to Simtel20 today, where it can join TDWIN31.ZIP
that I placed there yesterday. For those who didn't see my other
message, TDWIN31.ZIP contains a replacement for the version 3.0
WINDEBUG.DLL that should work with both Windows 3.0 and 3.1. TI868.ZIP
is the same as the document 868 from our techfax number, and describes
the other issues you will run into using BC++ 3.0 with Windows 3.1,
and what to do about them. Look for the files on
wsmr-simtel20.army.mil in directory pd:<msdos.turbo-c>, or on the
archive mirror sites wustl.wuarchive.edu and oak.oakland.edu in
directories with names like /msdos/turbo-c and /mirrors/msdos/turbo-c
once they have had time to migrate over there.

I also uploaded to the pd:<msdos.turbopas> directory TPWN31.ZIP, which
contains files for Turbo Pascal for Windows users who have Windows 3.1.

 -- sidney markowitz <sidney@borland.com>
Newsgroups: comp.windows.ms.programmer