HDTenEightyP/NetNews huggingface dataset:
From: exuhag@exu.ericsson.se (James Hague)
Newsgroups: comp.os.msdos.programmer
Subject: Stony Brook email address?
Date: 6 Apr 92 22:19:04 GMT
Reply-To: exuhag@exu.ericsson.se (James Hague)
Organization: Ericsson Network Systems, Richardson, TX

Does anyone know if Stony Brook (makers of Stony Brook
Modula-2 and Pascal+) have an email address for technical
support?
--
James Hague   
exuhag@exu.ericsson.se
Newsgroups: comp.os.msdos.programmer
From: pss1@kepler.unh.edu (Paul S Secinaro)
Subject: Re: DOS is dead.
Organization: University of New Hampshire  -  Durham, NH
Date: Thu, 16 Apr 1992 11:56:55 GMT

In article <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.

[...]

>
>That leaves DOS only running on 8088s and 80286's.  These machines
>will be worth very little and so will be purchased by people on tight
>budgets (or donated to nonprofits, etc).  There will be not much
>money to spend on software.  But of course, we know the cost of
>software development is not going down like hardware costs.

Unfortunately, Microsoft is rumored to be coming out with a 32-bit
version of DOS.  The rationale behind this is beyond my comprehension.

I mean, if it's 32-bit, it won't be backwards compatible with
conventional MS-DOS anyway, so why not just stick with Windows (or
other OS'es) running DOS emulators?

Paul


-- 
Paul Secinaro            | Synthetic Vision and Pattern Analysis Lab
pss1@kepler.unh.edu      | Dept. of Electrical and Computer Engineering
p_secinaro@unhh.unh.edu  | University of New Hampshire
From: rla@media03.UUCP (Raymond van der Laan)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Need help on TSR's
Date: 17 Apr 92 07:35:03 GMT
Reply-To: rla@media03.UUCP (Raymond van der Laan)
Organization: Mediasystemen, Netherlands


>Time is cheap.  Knowledge, experience, and expertise is the real currency.

You're obviously a student. Time isn't always cheap, and sometimes
things just need to be done. That's why its useful to use the knowledge
other people have. This is especially true if the project you're working
is only done once. Besides, were would all the 'open systems' be if
everyone (re)starts to make their own databases, networks, gui's etc. ???

Furthermore, I think it's a shame that the subject of TSR's is treated
so poorly on the years by compiler-packages and MS-DOS books. TSR's are
essential to DOS, so there should have been a TSR-API right from the
start. See Mac: almost all you have to do to make a DA (equiv. of TSR in
the early days) is click the 'DA' button on your compiler-settings
dialogbox. 

I think spending time to such trivial things as making TSR's, which take
away the attention of the real issue (i.e. solving a problem), is
something for beardy hackers who spend their nights behind the tube
with a coffee-infusion in their arms.
-- 
Raymond van der Laan           Email: sun4nl!media01!rla
Mediasystemen BV               Tel. : +31 23-319075            
Haarlem                        Fax  : +31 23-315210
The Netherlands                                   
                                    'There is no masterplan.
                                     This is what we do now.'
                                            - Stuart Adamson
Newsgroups: comp.os.msdos.programmer
From: mitchell@mdd.comm.mot.com (Bill Mitchell)
Subject: Re: Warm boot?  (All suggestions so far have been dangerous!)
Bcc:  mitchell
Reply-To: mitchell@mdd.comm.mot.com (Bill Mitchell)
Organization: Motorola, Mobile Data Division - Seattle, WA
Date: Fri, 10 Apr 1992 15:56:09 GMT

>>>
>>>Many people (including me, even) suggest the standard "jmp FFFF:0000"
>>>method.
>>>
>>>But this is extremely dangerous if the user is running disk cacheing
>>>software, since it bypasses *everything*!  Caches don't get flushed,
>>>and you run the risk of trashing your hard drive!
>

Well, what I've been telling people is:

------------------------------------------------------------------

The reboot program is reboot.com.  This program is created
from a debug script named reboot.dbg by typing "debug <reboot.dbg".
Reboot.dbg looks like this:

a 100
;cs:100
MOV	SI,0080                           ;point at command tail 
MOV	CX,[SI]                           ;get the length 
XOR	CH,CH                             ;check if it was zero 
JCXZ	0115                              ;if so, jmp 
INC	SI                                ;else get first char of arg 1 
INC	SI                                 
MOV	AL,[SI]                           ;into al 
CMP	AL,43                             ;was is 'C'?
JZ	011A                              ;if so, jmp 
CMP	AL,63                             ;was it 'c'? 
JZ	011A                              ;if so, jmp 
MOV	BX,1234                           ;set bx to magic number 1234 hex
JMP	011D                              ;and jmp 
;cs:11a
MOV	BX,7F7F                           ;else set bx to non-magic number 
;cs:11d
MOV	AX,0040                           
MOV	DS,AX                              
MOV	[0072],BX                         ;store bx in 0040:0072 
JMP	FFFF:0000                         ;and reboot 

n reboot.com
r bx
0
r cx
2b
w cs:100
q

------------------------------------------------------------------

A microsoft-c program to create reboot.exe which would do the same
thing is:

----------------------------------------------------------------

/* this program reboots the pc */
/* cold boot if an argument beginning with 'C' or 'c' is supplied */
/* warm boot otherwise */

#include <dos.h>
#include <ctype.h>

main(int argc, char **argv) {
	void (far *reboot)(void);
	int far *magic;

	FP_SEG(reboot) = 0xffff;
	FP_OFF(reboot) = 0;
	FP_SEG(magic) = 0x40;
	FP_OFF(magic) = 0x72;
	if (argc > 1 && tolower(*argv[1]) == 'c') {
		*magic = 0xffff;
	else
		*magic = 0x1234;
	}
	(*reboot)();		/* this should never return */
}

----------------------------------------------------------------

If there is any system-specific shutdown processing which needs to
be done (flushing the disk cache, idling the metal-stamping machine the
PC controls, whatever) it can/should be added.

Presumably, special measures will also be taken to assure that the
special shutdown processing gets done in case of ctl-alt-del reboot,
power fail/restore handling, trapping execution of illegal instructions,
vectoring thru unsupported interrupts, etc.

-- 
mitchell@mdd.comm.mot.com (Bill Mitchell)
From: mstaben@visual.spk.wa.us (Matt Staben)
Newsgroups: comp.os.msdos.programmer
Subject: Re: DOS is dead.
Date: 17 Apr 92 19:30:58 GMT
Article-I.D.: visual.1992Apr17.193058.6878
Organization: The Visual Market Public Access Site - Spokane, WA

James said that DOS will be around for many years.  

James, I must differ.  Five years ago, a 386 was a rare thing.  Five years
from now, the 386 will have gone the way of the 8088.  With the increases
in processing power, new paradigms (ie, OOPS), and a maturation of the
"purposes" of computing - we will have embarked on a new thing.  RAM will
become cheap (I'm not placing bets) as $10.00 a gig.  (give it 10 years,
and that $10.00 is by today's monetary equivalants.)  

DOS will most certainly _not_ be around, in 5 years, much less 10.

Grow a brain, idiot!

mstaben@visual.spk.wa.us
From: gordonm@hpdmd48.boi.hp.com (Gordon Margulieux)
Newsgroups: comp.os.msdos.programmer
Subject: Re: MS C/C++ v7 - need info
Date: 16 Apr 92 23:28:10 GMT
Organization: Hewlett Packard - Boise, ID

I talked to MicroSoft about what written SDK documentation is included for
the additional $150.  Their response was:

  1.  Only the upgrade package did not include the SDK doc's.  If you
      are not upgrading ($499 list) you get all 26 manuals.  Actually
      two manuals/books were not available at the time of shipping but
      a redemption coupon is included.
   
  2.  If you are upgrading, you should receive 13 C/C++ manuals and 3
      SDK manuals (getting started, etc.).

  3.  The additional SDK doc's include only the 10 additional manuals
      (no dups).  This package is only available thru MicroSoft.

  4.  If you are upgrading from a previous version of SDK, you get all 
      13 manual plus software (you already get the software with C/C++).
      This package lists for $150 from MicroSoft but can also be
      purchased thru retailers.  This means you may be able to buy the
      completed package for less (i.e. get the doc's for less too).
From: ralf+@cs.cmu.edu (Ralf Brown)
Newsgroups: comp.os.msdos.programmer
Subject: Re: How can I silence a ^C interrupt?
Date: 15 Apr 92 02:37:25 GMT
Organization: School of Computer Science, Carnegie Mellon

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....
-- 
{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: nevries@accucx.cc.ruu.nl (Nico de Vries.)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Borland -> Zortech: Do it ?
Date: 11 Apr 92 07:53:05 GMT
Organization: Academic Computer Centre Utrecht

In <1992Apr10.124132.1203@falcon.aamrl.wpafb.af.mil> nlonginow@falcon.aamrl.wpafb.af.mil writes:

>I frequently run out of memory in my applications of Borland C++, and have
>been thinking about going to a 32-bit Compiler, like Zortech. This, as
>opposed to using Borland (or Microsoft) followed by a DOS Extender 
>(like Pharlap). The problem with the DOS extender route is being unable to
>make use of the excellent debugging tools provided by Borland (and
>Microsoft) on the runtime code. I'd like to stay with a well rounded
>development and debugging environment, but ...  ANy ideas of the 
>Zortech product ? (C++, that is)
I have them both and prefer Borland very much. IMHO the Zortech environment
is a joke and the debugger stil doesn;t exist (would arive "soon"). The Zortech
compiler is however nice for compiling 32 bit code. In most cases with VROOM
the program can be made running too but they are much faster.

If you start using ZOrtech at least DON'T trow away your Borland package. Also
notice Borland C++ dor OS/2 2.0 is comming and this will generate 32 bit code
probably Zortech will be sooner (althought if you are in a hurry you can
considder a C++->C translator and C/Set 2 or Watcom C 9.0 for OS.2 2.0.

>-- 
>Nick Longinow
>Armstrong Lab
>Human Engineering division


Nico 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: (comming)
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.
From: nelson_p@APOLLO.HP.COM
Newsgroups: comp.os.msdos.programmer
Subject: Microsoft compiler?
Date: 8 Apr 92 20:29:35 GMT



   I write C and C++ software in DOS and Windows at home for fun
   and to stay technically current.  (At work I use Pascal and C
   on HP Apollo workstations).

   Currently I use Borland C++ 3.0.  It's been a little buggy
   but they've already sent me ome patch disk and I'm getting
   by OK.     Their latest bug (that TDW does not work with 
   Windows 3.1) is more serious because it prevents me from
   upgrading to the Windows 3.1 and Borland hasn't announced
   a release date for a fix

   MY QUESTION:

   Microsoft has announced their new C7.0, C++ upgrade.
   Supposedly it doesn't require an SDK for Windows 
   development, and suposedly technical support for Windows
   development is included (Microsoft's *outrageous* pricing
   and tech support policies for the Windows SDK turned
   me and a lot of other people off it in the past so these
   would seem to be good news).

   What are the pros and cons of switching to the Microsoft
   C7.0/C++ product, especially if I anticipate doing lots
   of Windows development?   

   Microsoft may choose to be uncooperative with Borland as they
   already are with other competitors (DR DOS?).  I've talked with
   people at Borland who've hinted that this is *already* the case.
   Is this likely to become a major reliability or compatibility
   problem for people who stay with Borland?

   How do the two products compare?   Are there major reasons to 
   stay with Borland?
 
   What is the likely impact if Microsoft losese the Apple suit? 
   (Apple recently upped its claim to $5.5 **billion** and they have
   been winning on most of the pre-trial contests.   The case is expected
   to go to trial this summer.)


---peter
From: valley@gsbsun.uchicago.edu (Doug Dougherty)
Newsgroups: comp.os.msdos.programmer
Subject: Re: DOS is dead.
Date: 16 Apr 92 14:37:49 GMT
Organization: University of Chicago Computing Organizations

komarimf@craft.camp.clarkson.edu (Mark Komarinski) writes:

>ajayshah@almaak.usc.edu (Ajay Shah) writes:

>>>In article <703214134snx@crynwr.com>, nelson@crynwr.com (Russell Nelson) says:
>>>>
>>>>DOS is dead.  (At most) A year from now no one will be programming for MS-DOS.

>I think Russ's point is that people will stop buying DOS in favor of a
>real operating system, be it OS/2, UNIX, or NT.  I would not be so 
>optimistic about DOS's demise tho.  Maybe 2-3 years and most development
>for DOS-based platforms will stop.

There is a big difference between use of MS/DOS and development for MS/DOS.
The former will go on forever, in one form or another (Yes, folks,
believe it or not, in this day and age of automatic washing machines and
laundromats, there are still people who wash their clothes by hand.  In
many parts of the world [so I'm told], there are people who wash their
clothes on a rock)  The later may well die out simply because all of the
problems have been solved.

		*	*	*	*	*

	"Speaks the man who swears by his 1985 terminal program.  As far
	as I'm concerned, that problem is solved.  Has been for lo these
	7 years [to steal a line from Dickens].  In fact, yesterday was
	the 7th aniversery of my terminal program..."
****************************************************************************
The Slug		valley@gsbsun.uchicago.edu

"Can I shake your hand or would I be violating about 15 federal laws ?"

(THis [sic] message should be assumed to have been smiley captioned for the
humor impaired)
Newsgroups: comp.os.msdos.programmer
From: comptec91055@camins.camosun.bc.ca
Subject: help network card id software
Organization: Camosun College
Date: Wed, 15 Apr 1992 03:26:54 GMT



		Hello Hardware gurus hackers and programmers:

			I am attempting to write a small routine which can be
executed on any pc that returns information on the resident network card (type
mem. cap. etc.)  (assembly/c routine).. My problem is that I am unsure of which
interrupts the card takes over when it is installed, whether or not these inter-
rupts are from the dos vector table or directly from the cpu, and how they can
be used to access card info.  If anyone has the time I would very much appreciate
 any information that could be provided.  I will send anyone that responds a copy
of the final program which does a series of hardware checks and verifications
on the pc, including nice output (not that anyone responding would need this,
but what the heck..)   If there are any ideas could you please e-mail them.
 			Thanks in advance,
	
			D. Rozee
From: robert@solan.unit.no (Robert Schmidt)
Newsgroups: comp.os.msdos.programmer
Subject: Re: "Sticky" keyboard in Borland C++ 3.0
Keywords: keyboard,problem,borland
Date: 16 Apr 92 18:20:53 GMT
Organization: Norwegian Institute of Technology

In article <1992Apr13.164426.13670@tc.fluke.COM>, roger@tc.fluke.COM (Roger Hammerquist) writes:
 > 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?

The same applies to EMM386 as to QEMM386, not much difference here... except
that I don't know of any switches to fix the problem.  Check the DOS manual
for any switches similar to the QEMM's UNUSUAL8042 and IGNOREA20...

Try removing EMM386 from your CONFIG.SYS (put a REM in front of it), and see
if the problem, persists...


 > 		Roger Hammerquist
 > 		roger@tc.fluke.COM

-- 
Regards from Robert Schmidt, PC C/asm is my game, fast graphics is my 
pain  -  Watch for my VGA/SB demo!
     e-mail to robert@solan.unit.no
 snail-mail to Stud.techn. Robert Schmidt, stud.post 170,
               Norwegian Institute of Technology, Trondheim, NORWAY
From: Jim.Ficken@psycho.fidonet.org (Jim Ficken)
Newsgroups: comp.os.msdos.programmer
Subject: Telephone number for Mag
Date: 13 Apr 92 10:36:00 GMT
Organization: Psycho: The Usenet<->Fidonet Gateway of St. Pete Florida

MK>From: tanith@csd4.csd.uwm.edu (Mike Kretzer)
  >Date: Sat, 11 Apr 1992 21:52:57 GMT
  >Organization: Computing Services Division, University of Wisconsin - Milwauk
  >Message-ID: <1992Apr11.215257.12161@uwm.edu>
  >Newsgroups: comp.sys.ibm.pc,comp.sys.ibm.pc.programmer,comp.os.os2.misc

  If anyone has the phone number for Magitronic, would
  >you please send email to tanith@csd4.csd.uwm.edu.  Thanks...

Try the distributor: Liuski at 708-620-8928. We are dealers. If you
need any more Magitronic products, we'll be glad to match the prices
of your other sources if we can. 813-786-2852 (voice).
___
 X SLMR 2.1a X We all live in a yellow subroutine.

--  
Internet: Jim.Ficken@psycho.fidonet.org
UUCP: ...!uunet!myrddin!tct!psycho!Jim.Ficken
Note:psycho is a free gateway between Usenet & Fidonet. For info write to
     root@psycho.fidonet.org.
Newsgroups: comp.os.msdos.programmer
From: brown@NCoast.ORG (Stan Brown)
Subject: Re: Object file format for BC++
Organization: Oak Road Systems, Cleveland Ohio USA
Date: Tue, 14 Apr 1992 00:37:03 GMT

In article <702781917.F00006@cloud.pub.uu.oz.au> hamish@cloud.pub.uu.oz.au (Hamish Moffatt) writes:
>Hello Stan!
>
>In a message posted <Tuesday March 24 1992>, Stan Brown wrote to All (xpost:
>1):
>
> SB> By the way, there is no such newsgroup as "comp.sys.ibm.pc.programmer".
> SB> I have changed the Newsgroups line to reflect this.
>
>Well the users of that newsgroup are going to get quite a shock! I have
>comp.sys.ibm.pc.programmer here and it is definately different to
>comp.os.msdos.programmer too.

For anyone _else_ who missed this in the FAQ list--

    Q102. What's the difference from comp.sys.ibm.pc.programmer?

    A.  c.s.i.p.programmer is the old name of comp.os.msdos.programmer, and
        has been obsolete since September 1990.  However, many systems have
        not removed the old group, or have removed it but aliased it to the
        new name.  This means that some people still think they're posting
        to c.s.i.p.programmer even though they're actually posting to
        c.o.m.programmer.

        You can easily verify the non-existence of c.s.i.p.programmer by
        reference to the "List of Active Newsgroups" posted to news.groups.

If your site accepts postings to comp.sys.ibm.pc.programmer, its list of
newsgroups may be out of date.  Your sysadmin may not be aware of this.

-- 
Stan Brown, Oak Road Systems, Cleveland, Ohio, USA   brown@ncoast.org

"All my life I've wanted to be somebody. I see now I should have been
more specific."                                         --Lily Tomlin
From: dj@ctron.com (DJ Delorie)
Newsgroups: comp.os.msdos.programmer
Subject: Re: tricky batch - help
Date: 8 Apr 92 17:42:28 GMT
Reply-To: dj@ctron.com
Organization: None whatsoever

In article <1992Apr8.115703.9248@uwasa.fi>, ts@uwasa.fi (Timo Salmi) writes:
> >  Does anyone know or have an idea how to search for the files
> >and insert their filename and path into a varialbe, if they exist or not ?

If all else fails, write a prompting program that creates a second
batch file, and call it from the first.

DJ
dj@ctron.com
Life is a banana.
Xref: sparky comp.os.msdos.programmer:5365 comp.windows.ms.programmer:5406
From: shap@xanadu.com (Jonathan Shapiro)
Newsgroups: comp.os.msdos.programmer,comp.windows.ms.programmer
Subject: Need help with server under Windows
Date: 13 Apr 92 15:21:23 GMT
Reply-To: halifax!shap@xanadu.com
Organization: Xanadu Operating Company

I hope somebody out there can help me.

I'm a consultant with two clients who both need to solve the same problem.
Both are planning to release products for MS Windows, and both are doing
client-server applications.  The gotcha is that both would like their
products to be peer to peer.  The following requirements are causing us
to lose some hair, and I'm sure someone out their has solved these
already.

The specific applications in question are completely unrelated, but both
customers have expressed the following requirements:

1. If your machine is a server it will service requests any time the
   machine is powered on.  It's probably enough to do this only when
   Windows is running, but it would be better to do it any time the machine
   is powered on. Protected mode is fine (indeed, is preferred!)

2. Whether or not your machine is a server, your machine may be a client.
   While they may do dedicated server machines they also wish to be able to
   run the service on a regular user's PC in small group environments.

3. While running, both the server and the client will need to use network
   interfaces, but cannot take over the network exclusively (i.e. shouldn't
   interfere with other applications that want to use the network).

The clients understand that the state of networking in the DOS world is
such that incompatibilities between network applications may be inevitable,
but they'ld still like to minimize them.

The requirements translate into the following implementation issues:

1. How to do time-critical multitasking under windows.

2. How can I learn about standard network interface layers under Windows if
   such exist?

I'm not particularly a low-level DOS wizard, and I could use some help.  In
one case, the client would probably be willing to pay for a limited amount
of consulting time to get the solution.  In the other case, a position may
be open to work on the product.  It may be that what they want isn't possible
in the context of DOS today, in which case it would be nice to know and to
come up with alternative implementation strategies.

If you may be able to help, I would appreciate it if you would get in touch
with me by email.  Replying to me here should work (shap@xanadu.com), but
sending mail to halifax!shap@xanadu.com would be preferred.

Thanks alot.


Jonathan Shapiro
Newsgroups: comp.os.msdos.programmer