HDTenEightyP/NetNews huggingface dataset:
From: yuan1@husc10.harvard.edu (Nina Yuan)
Newsgroups: comp.os.msdos.programmer
Subject: Memory problems with Borland C++ 2.0
Date: 12 Apr 92 22:14:22 GMT
Organization: Harvard University Science Center


I'm writing a large program in BC++ 2.0 that allocates large lists and
tables.  When I try to run it within the IDE, it says that it can't
allocate enough memory and aborts, but if I run it from the DOS shell,
all is well.  Short of using smaller tables and so on, is there anyway
I can get BC to use, say extended/expanded memory so that I can run it
within the environment (and thus use the debugger)?  I checked the
manual, but didn't find the answer.

Thanks for any help you can give me.
-nhy

















-- 
----------------------------------------------------------------------------
Nina H. Yuan                               "It's a miracle that curiosity
Harvard College                             survives formal education."
yuan1@husc.harvard.edu                                  - Albert Einstein
From: ts@uwasa.fi (Timo Salmi)
Newsgroups: comp.os.msdos.programmer
Subject: Re: DOS is dead.
Date: 17 Apr 92 06:52:01 GMT
Organization: University of Vaasa, Finland

In article <92106.232706CXF111@psuvm.psu.edu> CXF111@psuvm.psu.edu (Charles Fee) writes:
>>Sure gets my vote for Dork poster of the week!
>
>Huh?  The GOD of Packet drivers is a dork?

Russ's opener in this discussion was obviously deliberately
aggressive, even a bit outrageous, probably to get a strong
response.  But is a two-egded sword for an established net
personality to use.  Maybe it is not the best choice for his
continued credibility.  (*NO* flame involved, but a simple
observation grown out of experience). 

>     It is my opinion that the hodgepodge of kludges that is DOS is now
>indeed dead (If it is really anything more than a glorified bootstrap
>loader, anyway.) The Success of MS-Windows, and hopefully OS/2 along with
>the imminent release of several free Unixes (sp?) the mainstream PC market

Why do people have to look at this so subjectively.  This is not a
simple matter of opinnion.  Rather consider the current user
statistics.  No, I don't have them, but PC and other magazines often
give some estimates.  It seems that MsDos usage is still in a class
of its own in that respect.  But the success of Windows is
noteworthy, yet we are still speaking of perhaps a few million users
instead of tens of milloins.  Whether one likes it or not, the
market decides, not the company programmers' preferences. 

...................................................................
Prof. Timo Salmi
Moderating at garbo.uwasa.fi anonymous ftp archives 128.214.87.1
School of Business Studies, University of Vaasa, SF-65101, Finland
Internet: ts@chyde.uwasa.fi Funet: gado::salmi Bitnet: salmi@finfun
From: beaurega@ireq.hydro.qc.ca (Denis Beauregard)
Newsgroups: comp.os.msdos.programmer
Subject: Re: How to test for a key ALREADY pressed?
Date: 8 Apr 92 01:00:44 GMT
Organization: Hydro-Quebec

In article <rqjbpINNiqv@matt.ksu.ksu.edu> kentiler@matt.ksu.ksu.edu (Kent Iler) writes:
>Hello,
>   Is there a way to test to see if a key is already pressed.  Let say I run
>this program from the autoexec, and I want to see if the space bar is pressed.
>If it is I want to do one thing, if not I want to do another.  I don't want to
>wait there for a key to be pressed, just see if it already is.  I have C++ and
>Turbo Pascal to program with.  Thanks.
>						--Kent

The wire in front of your keyboard is a communication line.
Each time you depress and release a key, you sent a message to the PC.
Thus, if you don't watch that line, you cannot know the current state
of keys.

There are 2 exceptions : shift/alt/ctrl group and toggle group.
Keyboard routine will remember in 8 bits the state of left-shift, right-shift,
alt or ctrl keys, as well as caps-lock, num-lock, insert and scroll-lock.

So, instead of using space bar, just use other keys, and you are in business!

Check the keyboard BIOS routine to know (in keyboard status routine)
which bit does what.

Reference : Int 16h, function 02, return keyboard flags.


-- 
    Denis Beauregard       _ _ _ _  Collecting Beauregard/Jarret/Jarest/Vincent
beaurega@ireq.hydro.qc.ca | * | * | Promoting use of QC as Quebec Postal Code
  Andre Jarret, sieur de  |===|===| Mes opinions?  Oui, oui, les miennes!
   Beauregard 1642-1992   |_*_|_*_| My opinions?  Yes, yes, mine!
From: harrison@sun.lclark.edu (Mark Harrison)
Newsgroups: comp.os.msdos.programmer
Subject: Turbo C/C++ for dos and windows - Differences?
Date: 14 Apr 92 22:14:10 GMT
Article-I.D.: lclark.1992Apr14.221410.6749
Organization: Lewis & Clark College, Portland OR


I'm not sure if this is the right place, but can anyone tell me what the
difference is between Borland's Turbo C/C++ and Turbo C/C++ for Windows?
What I really want to know is will the windows version do everything
the dos version does, or is it just for windows programming?

Mark Harrison
harrison@sun.lclark.edu
Newsgroups: comp.os.msdos.programmer
From: feustel@netcom.com (David Feustel)
Subject: Re: Programming in 386/486 protected mode
Date: Wed, 15 Apr 92 02:33:30 GMT
Organization: DAFCO: OS/2 Software Support & Consulting

bright@nazgul.UUCP (Walter Bright) writes:

>joe@proto.com (Joe Huffman) writes:
>At Comdex, we demonstrated 32 bit Zortech C++ for OS/2 2.0 and Windows NT.

When will it ship to customers?
-- 
David Feustel N9MYI, 1930 Curdes Ave, Fort Wayne, IN 46805. (219)482-9631
Republicans believe in the "carrot and stick" approach to social problems:
 	   - carrots for the rich and sticks for the poor -
From: leonard@qiclab.scn.rain.com (Leonard Erickson)
Newsgroups: comp.os.msdos.programmer
Subject: Re: MS BASIC Real Data Type Structure?
Date: 8 Apr 92 03:15:34 GMT
Article-I.D.: qiclab.1992Apr8.031534.25817
Reply-To: 70465.203@compuserve.com
Organization: SCN Research/Qic Laboratories of Tigard, Oregon.

pacheco@acs.harding.edu writes:

>Does anyone know the format for the 4 byte floating point data type (the
>single precision real) in MS BASIC?  I specifically need a routine to
>convert these values to IEEE 4 byte floating point values.  If you know
>the details of the data type and/or you have any code (C, Pascal, ASM)
>which operates on them, I would truly appreciate any assistance you
>could offer.  Thanks ...

If you have a Turbo Pascal manual, look up the format of the REAL
type (6 bytes long). you'll see 5 bytes of mantissa, with one
byte of exponent on the end. What's this got to do with BASIC? 
Take the exponent byte and move it to the other (most significant)
end of the structure. Now chop the last two byte (least significant)
of the end the exponent *used* to be at. You now have the BASIC 4-byte
format.

I was converting TP 6-byte reals to BASIC 4-byte reals by *exactly*
the method described above. It should work fine in the other direction
too. Just take a good look at the explanation of the TP structure and
my explanation above and you should get the idea.

-- 
Leonard Erickson		      leonard@qiclab.scn.rain.com
CIS: [70465,203]			 70465.203@compuserve.com
FIDO:   1:105/56	 Leonard.Erickson@f56.n105.z1.fidonet.org
(The CIS address is checked daily. The others infrequently)
From: data@cs1.bradley.edu (Mark Hall)
Newsgroups: comp.os.msdos.programmer
Subject: Re: brightwhite background text?
Date: 5 Apr 92 13:02:41 GMT
Article-I.D.: cs1.data.702478961
Organization: Digilog Technologies : Music/Midi software that works for you.

In <1992Mar30.081431.14535@actrix.gen.nz> dvincent@actrix.gen.nz (David Vincent) writes:

>can anyone tell me how to get some text on screen that has a
>*brightwhite* background and any other colour foreground?

Yeah.  It's pretty simple.  Somewhere in memory (I dont' have my manuals at
the moment) is a byte with a bit that controls whether the BLINK bit in the
attribute bytes is actually blinking or background high intensity.  Once you
have set this bit, you can program all 16 colors foreground and background
simultaneously, although blinking has been disabled.  Does this make sense?

Here's what the attribute byte breaks down to:

	BL r g b I r g b
	7  6 5 4 3 2 1 0
	bit numbers ^^^^
	BL is BLInking (or hi-intensity if blink is disabled)
	r is red
	g is green
	b is blue
	I is high intensity.

hope this helps.

Mark Hall

--
| I'nt: data@{bucs1,buhub,heartland}.bradley.edu, al632@cleveland.freenet.edu |
|-----------------------------------------------------------------------------|
| F'net : 1:232/28 1:2250/9  (fname.lname@f<node>.n<net>.z<zone>.fidonet.org) |
|-----------------------------------------------------------------------------|
| "He sees you when you're sleeping, he knows when you're awake, but Captain, |
| it makes no sense!"    "But Spock, with Santa, ALL things are possible!"    |
| Kirk and Spock...Hallmark Greeting Cards                                    |
Newsgroups: comp.os.msdos.programmer,comp.sys.ibm.pc.programmer,comp.programming,alt.lang.asm
From: rparker@zeus.calpoly.edu (Richard Parker)
Subject: Re: msdos debuggers
Organization: California Polytechnic State University, San Luis Obispo
Date: Tue, 07 Apr 1992 19:41:54 GMT

    Funny, I am about to go back to Codeview, as the Turbo debugger keeps
crashing on me.  IF you are working with a COM program, then you might want
to check out AT86.  We used it at the last place I worked, and it is really 
cool for debugging 80x86 code.

-- 
*    rparker@demeter.calpoly.edu      ||                                     * 
*    rparker@blackbird.calpoly.edu    ||                                     *
*                                                                            *
From: timlee@public.btr.com
Newsgroups: comp.os.msdos.programmer
Subject: Re: C compiler reviews needed
Date: 16 Apr 92 04:23:12 GMT
Article-I.D.: public.6307
Reply-To: timlee@btr.com (Timothy J. Lee)
Followup-To: comp.os.msdos.programmer

zcookbruc@cc.curtin.edu.au writes:
|markh@csd4.csd.uwm.edu (Mark William Hopkins) writes:
|> Power C is $20 with optional add-ons, library source for extra, and a good
|> reference.  Need I say more :)
|
|GNU C is $0 with ALL the sources for the compiler, library, etc. It will run
|on 386 32bit with a virtual memory manager.
|(If you're running on anything less than a 386, this won't work)

You will probably want both -- Delorie's port of GNU C for most real
work, and Power C for things which you DON'T want a MSDOS extender
added to (e.g. driver programs).
From: hamish@cloud.pub.uu.oz.au (Hamish Moffatt)
Newsgroups: comp.os.msdos.programmer
Subject: Source to UUENCODE / XXENCODE
Date: 6 Apr 92 03:14:00 GMT

Anyone got any source to UUENCODE (prefered) and XXENCODE (if handy)? If so,
please mail it to me, or tell me where I can get it. FTP not available to me,
sorry.


Regards,
Hamish

 * Origin: Cloud Nine, Melbourne, Australia. cloud.pub.uu.oz.au (3:635/552)
Newsgroups: comp.os.msdos.programmer
From: zcookbruc@cc.curtin.edu.au
Subject: Re: looking for turbo C
Organization: Curtin University of Technology
Date: Sun, 12 Apr 1992 13:31:41 GMT

In article <1992Mar19.134421.2307@vax1.umkc.edu>, jamaleddin@vax1.umkc.edu writes:
> I am looking for a turbo C or C compiler for MS-DOS

What is the problem :
	1) You wish to purchase a turbo C compiler (cheeply) - Maybe buy a
	   kit from someone who's upgraded ?
	2) You wish for a list of compilers and their different merrits ?
	3) You are only just getting into MS-DOS and know only that you wish
	   to program in C, but have no idea of the MS-DOS arena ?

If your answer is (1), I think someone in the group could oblige

(2) or (3) Just keep looking at the discussions of the various discussions
in this group for info.

	...BRU
Newsgroups: comp.os.msdos.programmer
From: ralf+@cs.cmu.edu (Ralf Brown)
Subject: Re: Help:DOS5 -> DOS3.3
Date: Thu, 09 Apr 92 03:56:57 GMT
Organization: School of Computer Science, Carnegie Mellon

In article <36860001@hpopd.pwd.hp.com> richardh@hpopd.pwd.hp.com (Richard Hancock) writes:
}Both io.sys and msdos.sys (or their equivalents) must occupy contiguous
}clusters and must occupy the first available clusters.

The former limitation was removed in MSDOS 3.3 and the latter in MSDOS 5.0.
For DOS 5.0, the restrictions are:
	IO.SYS/IBMBIO.COM and MSDOS.SYS/IBMDOS.COM must be the first two
		files in the root directory
	The first three sectors of IO.SYS/IBMBIO.COM must be contiguous
For DOS 3.3-4.02, additionally
	The first three sectors of IO.SYS must be the first three data
		sectors on the disk.

Those first three sectors contain a smarter bootstrap loader which knows
how to follow the FAT chain; since most disks use 2K or larger clusters,
the first three sectors which must be contiguous are typically located in
a single cluster (which is by definition contiguous).

However, you can't *move* IO.SYS because its starting location is hardwired
into the boot sector (you can only do so much in 448 bytes...).



-- 
{backbone}!cs.cmu.edu!ralf  ARPA: RALF@CS.CMU.EDU  FIDO: Ralf Brown 1:129/26.1
BITnet: RALF%CS.CMU.EDU@CARNEGIE   AT&Tnet: (412)268-3053 (school)   FAX: ask
DISCLAIMER?  Did   |  Hansen's Library Axiom: The closest library doesn't
I claim something? |                          have the material you need.
From: ts@uwasa.fi (Timo Salmi)
Newsgroups: comp.os.msdos.programmer
Subject: Re: How to test for a key ALREADY pressed?
Date: 7 Apr 92 20:57:32 GMT
Organization: University of Vaasa, Finland

In article <rqjbpINNiqv@matt.ksu.ksu.edu> kentiler@matt.ksu.ksu.edu (Kent Iler) writes:
>Hello,
>   Is there a way to test to see if a key is already pressed.  Let say I run
>this program from the autoexec, and I want to see if the space bar is pressed.
>If it is I want to do one thing, if not I want to do another.  I don't want to
>wait there for a key to be pressed, just see if it already is.  I have C++ and
>Turbo Pascal to program with.  Thanks.

I am not sure how one can do it with normal keys, but the status of
the shift ctrl and alt keys are at a certain memory location (listed
in interrupt lists like Brown's).

...................................................................
Prof. Timo Salmi
Moderating at garbo.uwasa.fi anonymous ftp archives 128.214.87.1
School of Business Studies, University of Vaasa, SF-65101, Finland
Internet: ts@chyde.uwasa.fi Funet: gado::salmi Bitnet: salmi@finfun
Newsgroups: comp.os.msdos.programmer
From: joe@proto.com (Joe Huffman)
Subject: Re: Programming in 386/486 protected mode
Organization: Prototronics @ Sandpoint, Idaho
Date: Fri, 10 Apr 1992 06:16:20 GMT

crichmon@sedona.intel.com (Chris Richmond) writes:

>PC Week ran an article ( Oct. 14 1991 , page 133 ) on this topic.

>The compilers reviewed were:

>        Intel's          386/486 CodeBuilder 1.0;
>        MetaWare's       High C 2.31
>        Symantec's       Zortech C++ 3.0
>        Watcom's         C/386 8.5

This is getting a bit old.  Watcom has 9.0 out now.  Symantec has another
release out (still called 3.0 'something' though), too.  I wouldn't be
surprised if the others do also...

>For Windows 3.0 development, Zortech and Watcom would work.  Stuff
>written/compiled with Intel's compiler would run as DOS apps under
>Windows.  

Zortech C++ currently doesn't produce 32-bit apps under Windows.  Only 
32-bit apps for DOS (OS/2 2.0 support is rumored to be in beta).  I'm not 
sure about Watcom.

-- 
uunet!proto!joe
joe@proto.com
Newsgroups: comp.os.msdos.programmer
From: ralf+@cs.cmu.edu (Ralf Brown)
Subject: Re: How do I copy from COM1 to COM2 ?
Date: Wed, 15 Apr 92 02:38:45 GMT
Organization: School of Computer Science, Carnegie Mellon

In article <1992Apr13.171543.6439@odie.incom.de> tom@in.sub.org writes:
}What I thought I'd write a little program that runs in the foreground of  
}dos and copies everything that comes in at com1 out to com2 and vice  
}versa. This way the NeXT would be connected through the PC and would be  
}able to use the modem.

Check out
"PD1:","<MSDOS.MODEM>","PIPELN10.ZIP",1,18965,8,900916,""
on SIMTEL20.




-- 
{backbone}!cs.cmu.edu!ralf  ARPA: RALF@CS.CMU.EDU  FIDO: Ralf Brown 1:129/26.1
BITnet: RALF%CS.CMU.EDU@CARNEGIE   AT&Tnet: (412)268-3053 (school)   FAX: ask
DISCLAIMER?  Did   |  Hansen's Library Axiom: The closest library doesn't
I claim something? |                          have the material you need.
From: cornet@duteca2.et.tudelft.nl (Jan-Pieter Cornet)
Newsgroups: comp.os.msdos.programmer
Subject: Re: How do you tell which key is about to be pressed?
Date: 17 Apr 92 10:25:02 GMT
Organization: Delft University of Technology, Dept. of Electrical Engineering

phil@ux1.cso.uiuc.edu (Phil Howard) writes:

>Mischa_Sandberg@mindlink.bc.ca (Mischa Sandberg) writes:

>>Could someone tell me if there is a DOS or BIOS system call that
>>can tell me which key the user is about to press? One user of
>...
>>So here I am, stuck with my one last hope: that the hesitating
>>finger of the user, hovering over the "X" key, then the "Enter"
>>key, then the "Print Screen" key, can be detected by the hardware
>>(why DO they call it an 'enhanced' keyboard, anyway?), evaluated
>>for likelihood of being what the user really wants, and substitute
>>the correct keystroke instead.

>I believe this is going to require a further hardware upgrade.
Indeed. You should order part 1-A412751-65.1 from Intel and it'll
fly. There's no manual with it, tho'. Since this device rather heavily
depends on a persons psi and chara, you can never be sure where the
I/O ports end up, and what they'll do exactly. The only thing that's
guaranteed is that it doesn't interfere with your harddisk normally.

Which brings me to my second advice: There's a well-known short routine
for calculating the next hard disk head crash. This will be a tremendous
help to your customers. You can include warnings in your program of the
like: "When you haven't finished this in XXXX, it's gonna be all worthless",
or: "When you need a good excuse for not finishing your project make sure
you boss is around at XXXX, so he can witness the head crash."

The routine is of course:
	CLI
	MOV AL,0
	OUT 43h,AL
	NOP
	NOP
	JMP $+2
	IN AL,40h
	MOV AH,AL
	IN AL,40h
	STI
	XCHG AL,AH

Which leaves the number of estimated hours before the next head crash in AX.
 
-- Jan-Pieter
cornet@duteca.et.tudelft.nl
From: wood@Software.Mitel.COM (Dale Wood)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Programming in 386/486 protected mode
Date: 15 Apr 92 12:59:26 GMT
	<1992Apr10.061620.1080@proto.com> <663@nazgul.UUCP>
Organization: Mitel Corporation; Kanata, Ontario, Canada
In-reply-to: bright@nazgul.UUCP's message of 11 Apr 92 21:08:13 GMT

In article <663@nazgul.UUCP> bright@nazgul.UUCP (Walter Bright) writes:

>   /Zortech C++ currently doesn't produce 32-bit apps under Windows.  Only 
>   /32-bit apps for DOS (OS/2 2.0 support is rumored to be in beta).  I'm not 
>  /sure about Watcom.

Watcom produces 32 bit apps for Windows - it comes with a DLL that interfaces
the 32 bit app to the 16 bit Windows API.

Watcom has memory models as well - 

	The small model uses near pointers (32 bit) to reference the data.
	All referances are with respect to the DS segment. Hence in a small
	model all the data in your program must be less then 4GB. :-)

...Dale Wood
wood@Software.Mitel.COM
Newsgroups: comp.os.msdos.programmer
From: price@helios.unl.edu (Chad  Price)
Subject: Re: Bug of Turbo C 2.0?
Organization: University of Nebraska - Lincoln
Date: 15 Apr 92 15:12:42 GMT

zcookbruc@cc.curtin.edu.au writes:

>In article <1992Apr15.045942.9349@ux1.cso.uiuc.edu>, klg0582@uxa.cso.uiuc.edu (Ken-Huang Lin) writes:
>> 
>>   I was writing a program using Turbo C 2.0.  The program seemed to be
>> working.  However, after I moved part of the code into a function, it
>> gave me this run-time error message when the program reached the same
>> code now in the function:
>> 
>> "scanf: floating point formats not linked"
>> 
>>   I downloaded the patch "tc2pat.arc" and applied it.  Only some
>> patches would work.  The file "patfloat.bat", which is supposed to fix
>> "floating point formats not linked" problem, said "Incorrect file or
>> version of program file".  (The compiler is version 2.01.)  Does
>> anyone have any clue?
>> 
>> Ken H. Lin
>> khlin@uiwpls.ece.uiuc.edu

>here's a guess based on sources I've seen of other C libraries:

>Some libraries, because of size problems, don't have atof(), atod(),
>dtoa(), ftoa() in the main C library, instead they have a dummy function
>that says somthing along the lines of "floating point foramts not linked".

>The way to cure this (In the cases I've delt with) is to link in the maths
>library, if possible before the c library (est way to ensure linkage order
>in TC 2 is to use TLINK).

>I personally have never had the problem with any versions of TURBO/BORLAND C
>this may be because I always use TLINK.


I have had and fixed the problem. Get the patch file from Borland. Same file, 
not arc'd. It is on the Borland BBS (or at least it used to be). You will need
your serial number to log onto the BBS.

The problem is in the Borland compliler, which does not link in the floating
point stuff unless a floating point variable is declared and used in the
function. 

chad
price@helios.unl.edu
From: Ralf.Brown@B.GP.CS.CMU.EDU
Newsgroups: comp.os.msdos.programmer
Subject: Re: Tseng-4000 1280x1024 & 1280 x 960 mode, Question + remarks
Date: 16 Apr 92 11:31:40 GMT
Organization: Carnegie Mellon University School of Computer Science
Originator: ralf@B.GP.CS.CMU.EDU

In article <1992Apr16.072328.18517@mhres>, hst@mh_co2.mh.nl (Klaas Hemstra) wrote:
}From article <29eb978a@ralf>, by Ralf.Brown@B.GP.CS.CMU.EDU:
}> Mode 3Dh (which can also be set with "VMODE 3D", an undocumented switch)
}> sets a 1280x1024 graphics mode with 16 colors and 128x64 text (using an
}> 8x16 character cell).
}
}A few more notes and a question on this:
}- Somewhere i also saw (VPIC ?) that there is also a 1280x960 mode (3E) which
}  preserves the 1:1 pixel ratio. (1280:960 = 4:3).

VPIC's config file says the Definicon has a mode 3Eh which is 1280x961.
However, that mode does not exist on my card.

Speaking of undocumented stuff, VMODE also has an undocumented "80M"
switch, which I guess sets 72Hz refresh at 1024x768.


-- 
{backbone}!cs.cmu.edu!ralf  ARPA: RALF@CS.CMU.EDU  FIDO: Ralf Brown 1:129/26.1
BITnet: RALF%CS.CMU.EDU@CARNEGIE   AT&Tnet: (412)268-3053 (school)   FAX: ask
DISCLAIMER?  Did   |  Hansen's Library Axiom: The closest library doesn't
I claim something? |                          have the material you need.
Newsgroups: comp.os.msdos.programmer
From: klg0582@uxa.cso.uiuc.edu (Ken-Huang Lin)
Subject: Bug of Turbo C 2.0?
Keywords: Turbo C
Organization: University of Illinois at Urbana
Date: Wed, 15 Apr 1992 04:59:42 GMT


  I was writing a program using Turbo C 2.0.  The program seemed to be
working.  However, after I moved part of the code into a function, it
gave me this run-time error message when the program reached the same
code now in the function:

"scanf: floating point formats not linked"

  I downloaded the patch "tc2pat.arc" and applied it.  Only some
patches would work.  The file "patfloat.bat", which is supposed to fix
"floating point formats not linked" problem, said "Incorrect file or
version of program file".  (The compiler is version 2.01.)  Does
anyone have any clue?

Ken H. Lin
khlin@uiwpls.ece.uiuc.edu
Newsgroups: comp.os.msdos.programmer