HDTenEightyP/NetNews huggingface dataset:
From: Ralf.Brown@B.GP.CS.CMU.EDU
Newsgroups: comp.os.msdos.programmer
Subject: Re: Need a Good Program Editor
Date: 15 Apr 92 11:20:55 GMT
Organization: Carnegie Mellon University School of Computer Science
Originator: ralf@B.GP.CS.CMU.EDU

In article <1992Apr15.175507.1@cc.curtin.edu.au>, zcookbruc@cc.curtin.edu.au wrote:
}Another editor you could try if you're realy in a JAM is the BORLAND C IDE
}compiler editor (NOT TURBO C). It readly blew my socks off when I found
}a PC editor that could actually do paged editing (but to find it in a compiler
}is realy impressive !).

Paged editing, as you call it, is quite common; you just haven't been looking
at the right programs.	Try BlackBeard (shareware up to v7.4 or so), Lugaru's
Epsilon, Borland's Sprint, PC Tools DESKTOP's notepad, WordPerfect, etc.

-- 
{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: roger@tc.fluke.COM (Roger Hammerquist)
Subject: Re: "Sticky" keyboard in Borland C++ 3.0
Summary: Not just in BC++
Keywords: keyboard,problem,borland
Organization: John Fluke Mfg. Co., Inc., Everett, WA
Date: Mon, 13 Apr 1992 16:44:26 GMT

In article <osPqiB1w164w@vicuna.ocunix.on.ca>, frampton@vicuna.ocunix.on.ca (Steve Frampton) writes:
> For those people experiencing keyboard problems under BC++ 3.0 (and other 
> software products), if you are using the Quarterdeck QEMM Memory Manager 
> software, try adding the following:
>   IGNOREA20 UNUSUAL8042
> to your 'device=c:\qemm...' statement in your CONFIG.SYS file.

I've been having the "Sticky" shift problem, too;
however, I'm not using BC++,
  and    I'm not using QEMM.

It seemed to start when I upgraded to MS-DOS version 5.0 (as did losing input
characters on the serial ports).  However, it could be related to use of an
extended memory manager, since that was when I started using EMM386, as well.
Any suggestions?

		Roger Hammerquist
		roger@tc.fluke.COM
Newsgroups: comp.os.msdos.programmer
From: trappetj@cheops.qld.tne.oz.au (John Trappett @ Telecom Australia)
Subject: Re: DOS is dead.
Organization: Telecom Australia, TNE Computer Support Services
Date: Thu, 16 Apr 1992 02:58:38 GMT

nelson@crynwr.com (Russell Nelson) writes:

>DOS is dead.  (At most) A year from now no one will be programming for MS-DOS.

Sure gets my vote for Dork poster of the week!

John
-- 
John Trappett                           ....     o       
Telecom Australia                      ....   _/\_>      
trappetj@cheops.qld.tne.oz.au           .....O,> / O...  
Newsgroups: comp.os.msdos.programmer
From: smayo@wang.com (Scott Mayo)
Subject: Re: Detecting VGA
Organization: Wang Labs, Lowell MA, USA
Date: Wed, 08 Apr 92 18:25:19 GMT

holmesda@spot.Colorado.EDU (ASTAROTH) writes:

>	This time I need to know how to detect whether the current vidcard
>is CGA, EGA, or VGA.  Can someone send me the assembly needed to perform
>such a feat?  Please?  Or at least point me in the right direction?

set ah to 12h
set al to 0
set bl to 32h
invoke int86 10h
if the result is al == 12h, it is a VGA. If not...

ah/ 12h
bl/ 10h
invoke int86, 10h
if the result in bl is 10h, it is not an EGA. If it is less than 3,
it is a small EGA (less than 256K memory)
if bh comes back nonzero, it is not a color monitor.

I don't know how to ask for a CGA, but if it flunks these tests you could
just *assume* CGA.
--
These are only my opinions.  You should hear my convictions.
smayo@wang.com
Newsgroups: comp.os.msdos.programmer
From: kibirev@csa.bu.edu (oleg kibirev)
Subject: Re: How can I silence a ^C interrupt?
Organization: Computer Science Department, Boston University, Boston, MA, USA
Reply-To: kibirev@csa.UUCP (oleg kibirev)
Date: Wed, 15 Apr 1992 03:48:32 GMT

In article <1992Apr15.023725.104692@cs.cmu.edu> ralf+@cs.cmu.edu (Ralf Brown) writes:
#In article <1992Apr14.210313.21622@ux1.cso.uiuc.edu> jas37876@uxa.cso.uiuc.edu (John A. Slagel) writes:
#}    An easy way to get rid of it is to locate the cursor at a 
#}    non-displayed location, like row 26 when you're not using it.
#
#That won't completely solve things, because the CRLF that gets output would
#cause the screen to scroll.  You can't hardcode row 26 either, because the
#screen might be 43, 44, 50, 60, 64, 66, or even 75 lines.  And it will
#probably crash my system if run on my mono display because the "^C" will
#overwrite highloaded TSRs at B100h....

Probably, the simpliest method to avoid ^C is to intercept INT 9 &
remove offensive keystrokes (ie ^C, Break and ^@). Or better yet, not
to use DOS for screen output :-).

							Kibirev Oleg
							kibirev@CSA.BU.EDU


Newsgroups: comp.os.msdos.programmer
From: joe@proto.com (Joe Huffman)
Subject: Re: Can BC 3.0 be made to run on a computer with 1M of RAM?
Organization: Prototronics @ Sandpoint, Idaho
Date: Thu, 16 Apr 1992 17:01:56 GMT

kibirev@csa.bu.edu (oleg kibirev) writes:

>I have a 286 with 1M of RAM & no place to put more memory. The

>Now the question. I've never written protected mode programs, but I
>think that if BC 3.0 is using DPMI, it should be possible to give
>it as much "extended memory" as it wants by swapping to the disk. Is
>there a program to replace DPMILOAD that will do this?

A '286 machine can't implement DPMI.  Sorry...

-- 
uunet!proto!joe
joe@proto.com
Newsgroups: comp.os.msdos.programmer
From: ralf+@cs.cmu.edu (Ralf Brown)
Subject: Re: How can I silence a ^C interrupt?
Date: Wed, 15 Apr 92 02:27:26 GMT
Organization: School of Computer Science, Carnegie Mellon

In article <37390028@hpopd.pwd.hp.com> richardh@hpopd.pwd.hp.com (Richard Hancock) writes:
}/ hpopd:comp.os.msdos.programmer / halvers@procyon.crd.ge.com (peter c halverson) /  6:55 pm  Apr  9, 1992 /
}To quote an old DOS reference manual :- "If the Ctrl-Break interrupts
}functions 9 or 10, buffered I/O, then C, carriage-return, and linefeed are
}output."
}
}This implies that you will need to make sure that you do not use buffered
}I/O to/from the console when that buffering is performed by DOS via Int 21H,
}functions 9 or 10.

Actually, you'll have to make sure you don't use *any* DOS console I/O
function that checks for Ctrl-C or Ctrl-Break.  This includes unbuffered
I/O as well as functions 9 and 10.
-- 
{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: hamish@cloud.pub.uu.oz.au (Hamish Moffatt)
Newsgroups: comp.os.msdos.programmer
Subject: PKWARE's AV code found
Date: 11 Apr 92 05:02:14 GMT

Hello Paul!

In a message posted <Tuesday March 31 1992>, Paul Carl Kocher wrote to All:

 PK> From: kocherp@leland.Stanford.EDU (Paul Carl Kocher)

 PK> begin 666 FORGE_AV.ZIP
[...]
 PK> end

I decoded this program. PAK T says no errors; archive is fine.

PKUNZIP, on the other hand, says insufficient memory, and 545K is available!!

I don't think you beat PKWare this time..!


Regards,
Hamish

 * Origin: Cloud Nine, Melbourne, Australia. cloud.pub.uu.oz.au (3:635/552)
From: N.J.Watts@bradford.ac.uk (NJ WATTS)
Newsgroups: comp.os.msdos.programmer
Subject: Printer off-line
Date: 15 Apr 92 15:13:28 GMT
Organization: University of Bradford, UK
Originator: 88621168@november

Dear all,
   	Is it possible to determine whether or not a printer on the stdprn 
stream is on-line or not before sending any information to it?  I cannot 
get around the problem that the operating system cuts in whenever the printer 
is off-line and leaves an unsightly message in the middle of my applications.
		    
    		   Any thoughts greatly appreciated...
From: feustel@netcom.com (David Feustel)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Borland -> Zortech: Do it ?
Date: 12 Apr 92 15:31:28 GMT
Article-I.D.: netcom.l9vjb5.feustel
Organization: DAFCO: OS/2 Software Support & Consulting

Has anyone successfully run an application compiled with ZTC and 
using the Dosx 32-bit dos extender under OS/2 v2.0 by taking advantage
of the DPMI?
-- 
David Feustel N9MYI, 1930 Curdes Ave, Fort Wayne, IN 46805. (219)482-9631
= Candidate Bush wouldn't recognize principle if he were standing upon it =
From: pbreton@snowhite.WPI.EDU (Peter R Breton)
Newsgroups: comp.os.msdos.programmer
Subject: TSR Programming Source
Keywords: TSR Programming
Date: 13 Apr 92 18:49:40 GMT
Article-I.D.: wpi.1992Apr13.184940.10870
Organization: Worcester Polytechnic Institute


     I'm trying to learn how to go about programming TSRs.  Could anyone
reccommend any good references?  Be they books, magazine articles, etc...
Any help would be greatly appreciated.

Thanks.

*****************************************************************************
-Peter Breton (pbreton@snowhite.wpi.edu) (pete%hweng%banyan@thing.banyan.com)
Organization: Carnegie Mellon, Pittsburgh, PA
Newsgroups: comp.os.msdos.programmer,comp.sys.ibm.pc.programmer,comp.programming,alt.lang.asm
Date: Tue,  7 Apr 1992 04:52:05 -0400 
From: Rahul Verma <rv0s+@andrew.cmu.edu>
Subject: Re: msdos debuggers

Excerpts from netnews.comp.os.msdos.programmer: 7-Apr-92 msdos debuggers
by Charles A Lynch@world.st 
> Hi. I wonder if anyone out there knows of some good debuggers. I'm
> using Microsoft's Codeview now, but it kind of stinks...I almost
> prefer to use DEBUG. So anyway, please let me know, preferably in email,
> of any good 8086 machine code debuggers. If commercial, you could hint
> where to pick it up, or if shareware, where I can FTP it from.

I use Borlands integrated environment debuggers most of the time. They
are really awesome. Sometimes, when I really get streched, Turbo
Debugger comes to my rescue. You should really check them out.

Rahul
-------------------------------------------------------------------
Remember that anywhere you go, well, there you are!
-------------------------------------------------------------------
Secretary of the CMU Computer Club.
-------------------------------------------------------------------
From: nevries@accucx.cc.ruu.nl (Nico de Vries.)
Newsgroups: comp.os.msdos.programmer
Subject: Re: DOS is dead.
Date: 16 Apr 92 07:35:17 GMT
Organization: Academic Computer Centre Utrecht

In <703214134snx@crynwr.com> nelson@crynwr.com (Russell Nelson) writes:

>DOS is dead.  (At most) A year from now no one will be programming for MS-DOS.
I hope so but I am abit more pessimisic.

>What will spur the abandonment of DOS?  Well, people have long
>acknowledged that DOS is not a real operating system.  The only
>reason to run DOS is because you can't run a real operating system.
Hmmm. T think most users use DOS because their applications run on it
and because the don't want to fix something working.

>We now have the metal to run those operating systems.  Because the
>benefits of a real operating system will outweigh the cost, people
>will run them on their new machines.
If you are refering to OS/2 2.0 or Windows/NT the question is if the "costs"
, more hardware, new OS etc will give the users bennefits over lets say
Windows 3.1. The user doesn't care about bad design he just
wants to get his job done.

>...

>So, the only people buying expensive new software will be people
>running the new real OS(es).  Programmers interested in making the
>big bucks will program to this new audience.  And it *won't* be
>Windows, which is as lame an OS as DOS is.
I often hear this. I have to admit from a technical viewpoint there are
many things "wrong" about windows. But somehow the users like it and
is probably the widest used GUI around. And Microsoft (and don't forget
the most important their marketting) are working hard on keeping it that
way.

>Oh yes, there will be *some* people programming for MS-DOS, just like
>there are still new programs being written for the Zenith Z-100,
>Tandy Color Computer, Commodore C-64, CP/M, etc.  But there will not
>be much money in it.
I hope you are right, really. I don't think however this will all be done
on only a single year.


>-russ <nelson@crynwr.com>  I'm proud to be a humble Quaker!
>Crynwr Software            Crynwr Software sells packet driver support.
>11 Grant St.               315-268-1925 Voice
>Potsdam, NY 13676          315-268-9201 FAX

Nico E. de Vries
-----------------------------------------------------------------------------
USENET: nevries@cc.ruu.nl                 FIDO      : 2:281/708.1  (very new) 
VOICE : +31-3404-24931 (+31-30-316931)    FAX       : +31-30-312033 
BBS   : +31-30-341401 (Nico De_vries)     COMPUSERVE: (coming)
MAIL  : Hortensialaan 45, 3702VE, Zeist, The Netherlands 

IMPORT StdDisclaimer, MyPersonalOpinion;          - O   Place reserved for
Complaints about my spelling to DEV/NUL please.    |    funny joke. Sugestions 
I work for BITECH, I don't SPEAK for BITECH.      \_/   apreciated.
Newsgroups: comp.os.msdos.programmer
Subject: Can MS-DOS machines be multi-programmed??
From: christen@vax.sonoma.edu
Date: 7 Apr 92 11:06:30 -0800
Organization: Sonoma State University

Hello all,

I am writing a multi-line bbs on the amiga, and am trying to make the code
compatible as possible between amiga and msdos...

Problem is - Amiga os is multitasking, with nice features such as message-
passing and resident libraries... I guess I cant use those features 
and be compatible with dos. Anyone know if there is a toolkit for writing
a scheduler in msdos? 

Do any of the multi-line bbs progs out there support multi-line AND 
doors programs at the same time? 
Any clue as to how these are programmed ( if they exist )


Thanks for your time...

paulc@hpsad.sad.hp.com

   - or  -

christen@sonoma.edu

Newsgroups: comp.os.msdos.programmer,alt.msdos.programmer
From: adingus@magnus.acs.ohio-state.edu (Aaron T Dingus)
Subject: HELP with Joystick Input
Organization: The Ohio State University
Date: Thu, 16 Apr 1992 23:08:42 GMT

If anyone out there can help me, I would
greatly appreciated it.

I am trying to recieve input from the built-in
joystick ports on my TANDY 1000EX i8088.

They work on some games, etc., so I am sure that they
are functioning.

Does anybody know what DOS/BIOS interrupts/function
calls and what registers I should send/recieve to recieve
data from the stick and the buttons?

Any input on this would be of great help to me.

Thanks.

-ATD
-- 
Aaron T. Dingus
Professional Athelete
The Ohio State Univeristy
adingus@magnus.acs.ohio-state.edu
From: aki@cruzio.santa-cruz.ca.us
Newsgroups: comp.os.msdos.programmer
Subject: 386 SX Bug
Keywords: 386SX, BUG, INTEL
Date: Wed, 15 Apr 92 03:21:28 PDT
Reply-To: aki@cruzio.santa-cruz.ca.us


I was going through some of my old files and just happened to find a file
describing a bug with the 386SX.  This particular problem is _not_ documented
in any publication I could get my hands on,  so if there is anyone out there
keeping track of Intel's bugs...  (BTW,  it was a pain to ID this problem,
since all the debuggers would execute the command correctly.  I imagine
trapped execution mode prevents the problem).  Description follows:

/************************************************************************
  The followning INLINE code turned up a _BUG_ in the Intel 386 SX 16 MHz
  ***********************************************************************/
 
/**************************************************************************
   When the CPU gets to CALLing the hardcoded addr, it will not return.
   It gets lost in never never land. It seems,  that the address is not
   correctly stored to the target memory location with the MOV command.
 
   I solved the problem by adding some NOP statements between the MOV and
   the CALL.
 
   Aki Korhonen, January 5th, 1992.
 
   PS. Check out PC-BENCH 1.4 and the soon-to-be-released PC-DIAG!
***************************************************************************/
 
  asm     mov ax, segm
  asm     mov bx, 0
  asm     mov di, offset offs_tavu
  asm     mov cs:[di], bx
  asm     inc di
  asm     inc di
  asm     mov cs:[di], ax
 
  asm     db 0x9A        /* CALL FAR, next two words are: OFFS, SEGM */
  asm    offs_tavu:
  asm     dw 0
  asm     dw 0


Aki.

PS.  I know the code looks terrible,  and don't ask me why I didn't use
far pointers.  I always work worst after 3 AM.
-- 
/  Phone: 408-662 9664 Fax: 662 9676  |  "Aki" pronounced: Ah-Key. I know  \ 
\  GENIE: A.KORHONEN  Home: /dev/nul  |  what I'm doing most of the time.  /
Organization: Little, if any.
X-Mac-Bust:   The Best Way To accelerate a Macintoy is at 9.8m/s^2
Date: Wednesday, 15 Apr 1992 23:27:06 EDT
From: Charles Fee <CXF111@psuvm.psu.edu>
Newsgroups: comp.os.msdos.programmer
Subject: Re: DOS is dead.
 <1992Apr16.025838.17912@cheops.qld.tne.oz.au>


In article <1992Apr16.025838.17912@cheops.qld.tne.oz.au>,
trappetj@cheops.qld.tne.oz.au (John Trappett @ Telecom Australia) says:
>Sure gets my vote for Dork poster of the week!

Huh?  The GOD of Packet drivers is a dork?

     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
will abandon Intel's heretical chips and venture into the promised land of
huge memory models and preemptive multitasking.  I am going to OS/2 2.0 and I
also have windows 3.1 as a fallback.  DOS has been the stumbling block for
many great advances in PC technology, and like cp/m (except for the problems
associated with the huge installed base) it is time to leave the cradle and
venture to the real world, whether it be OS/2, Windows (NT?), or a Unix
variant.  The time has come.
---
Charles A. Fee                           I'd Rather Be FTPing...
cxf111@psuvm.psu.edu
Xref: sparky comp.os.msdos.programmer:5457 comp.lang.pascal:2913
From: LAAAA43@cc1.kuleuven.ac.be (Peter Arien)
Newsgroups: comp.os.msdos.programmer,comp.lang.pascal
Subject: Re: SoundBlaster inoformation requested
Date: 16 Apr 92 09:31:38 GMT
 <1992Apr14.092738.6989@cco.caltech.edu>
Organization: K.U.Leuven - Academic Computing Center

In article <1992Apr14.092738.6989@cco.caltech.edu>, heathh@cco.caltech.edu
(Heath Ian Hunnicutt) says:
>
>Regarding info on the SoundBlaster:
>
>There is a mailing list for programmers, also a newsgroup.
>
>To subscribe to the mailing list, send
>subscribe joblow Joe Blow
>to listserv@porter.geo.brown.edu
>
Well, this should be : send

SUBSCRIBE BLASTER Your Name

to listerv@porter.geo.brown.edu

So I would send : subscribe blaster Peter Arien

I know this sounds obvious, but Joel Plutchak (this is the
guy you should contact if you want more info about this
mailing list : plutchak@porter.geo.brown.edu) noticed that a lot
of people were sending 'subscribe joblow Joe Blow' to the listserver.
Suppose lots of Joe Blows are now subscribe to the list joblow.
What would they be talking about...

Greetings.

Peter.

============================== = = = = = = = = = = = = = = = = = = = ====
Peter Arien                  =   LAAAA43@cc1.kuleuven.ac.be          =
Academic Computing Center    =   LAAAA43@cc5.kuleuven.ac.be          =
K.U.Leuven - Belgium         =   LAAAA43@blekul11.bitnet             =
                             =   peter%psl%cc3@cc3.kuleuven.ac.be    =
============================== = = = = = = = = = = = = = = = = = = = ====
Newsgroups: comp.os.msdos.programmer
From: ralf+@cs.cmu.edu (Ralf Brown)
Subject: Re: Detecting VGA
Date: Thu, 09 Apr 92 03:47:20 GMT
Organization: School of Computer Science, Carnegie Mellon

In article <bmej69.bn6@wang.com> smayo@wang.com (Scott Mayo) writes:
}[...]
}if the result is al == 12h, it is a VGA. If not...
}
}[...]
}if the result in bl is 10h, it is not an EGA. If it is less than 3,
}it is a small EGA (less than 256K memory)
}if bh comes back nonzero, it is not a color monitor.

And if it fails the tests,

set AH to 0Fh
invoke INT 10h
if AL == 7, assume MDA/HGC and set display address to B000h
else assume CGA

One final step will make text-based applications compatible with DESQview
and with Memory Commander's/All Charge Card's relocation of the video
memory:

After determining the display type and display address (B800h for color),
set ES to the display address segment
set DI to 0000h
set AH to FEh
invoke INT 10h
store the returned ES:DI as the start address of video memory

This last call will also make the program compatible with non-full-screen
operation under TopView, TaskView, OmniView, and MS Windows if the program
additionally makes calls to INT 10h/AH=FFh to let the environment know
about screen updates.
-- 
{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: chris@debra.dgbt.doc.ca (Chris Justus)
Subject: EMS memory (how do I use it??)
Organization: Communications Research Centre, Ottawa, Canada
Date: Wed, 8 Apr 1992 19:02:16 GMT


I'd like to write a program that uses EMS memory (so I can use more
than 640K).  How do I go about doing this?? I've read something about
physical pages and logical pages (what are these???).  Are there
public domain libraries (for MS-C 6.0) to access EMS memory?? Any and
all help would be greatly appreciated!!

-- 
                   Chris Justus      chris@debra.doc.ca     

Co-Op Student at Communications Research Centre, Communications Canada, Ottawa
From: aaron@clark.edu (Aaron Auseth)
Newsgroups: comp.os.msdos.programmer
Subject: Re: read with noecho
Date: 9 Apr 92 00:46:20 GMT
Article-I.D.: clark.1992Apr9.004620.13732
Organization: Clark College, Vancouver, Wa.  USA

In article <73164@netnews.upenn.edu> yates@a.chem.upenn.edu (John H. Yates) writes:
>I need to call a function or routine from Fortran
>that will prompt the user for a password, not
>echo it as it is typed, and return that password
>to the calling program for checking.
>
>Can anyone supply, or point me to such an example for
>SGI IRIX for 4D hardware, or on a MS DOS 5.0 platform?
>(I need to get this working on both).
>
>I had this working on VAX/VMS with system sys$qio
>calls coded in Fortran. I now need to port the code
>to DOS and IRIX now, and just be done with it.
>
>The called routine can be in Assembler, Fortran, or
>C, it only needs to be called from my Fortran.

It's easy to do in C, in TURBO C there is a getch() function, you could make
a simple function in C:

		char anyoldfunction()
		{
			return getch();
		}

This will wait for a key to be pressed then return the ASCII value.  This
routine uses the BIOS keyboard buffer, I assume fortran keeps this intact.
If you are using a PC based fortran compiler, there should be something
similar in the PC fortran language!