Xref:	news-dnh.mv.net comp.os.msdos.djgpp:1968
Path:	news-dnh.mv.net!mv!news.NH.Destek.Net!news2.net99.net!news.cais.net!ringer.cs.utsa.edu!swrinde!howland.reston.ans.net!math.ohio-state.edu!magnus.acs.ohio-state.edu!cis.ohio-state.edu!nntp.sei.cmu.edu!bb3.andrew.cmu.edu!andrew.cmu.edu!wnolan+
From:	William Nolan <wnolan+@andrew.cmu.edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Serious V2 beta bug...
Date:	Sat, 9 Sep 1995 18:38:15 -0400
Organization:	Sophomore, Computer Science, Carnegie Mellon, Pittsburgh, PA
Lines:	24
References:	<gkHaowu00aw6M7u3x4 AT andrew DOT cmu DOT edu> <304e74ac DOT sandmann AT praline DOT no DOT NeoSoft DOT com>
Nntp-Posting-Host:	po8.andrew.cmu.edu
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

Excerpts from netnews.comp.os.msdos.djgpp: 6-Sep-95 Re: Serious V2 beta
bug... by Charles Sandmann AT praline 
> Please check out the routines being used; if there are any HW interrupts
> involved which don't lock every byte of memory, please notify the author to 
> remove them from public distribution as they are a bomb waiting to
nuke a disk.

What you said makes sense -- maybe I should clarify what I was compiling
at the time, so you might be able to get a better idea of who was the
culprit.  I was (in BOTH cases, here) writing a program that used the
SB_LIB and the XLIB .a includes.  Having only taken a cursory look
through both, I can't tell you if they locked memory up okay.  It
*looked* like the SB_LIB actually did some locking, I didn't check out
the XLIB stuff, so I don't know.  Are the authors of these two libraries
(the XLIB being a conversion from Borland, anyway) reading this
newsgroup?


 _ _    _ _   _ _   _ _     _ _
[@@@|  |@@@] [@@@] [@@@]   [@@@]
[~~~|/\|~~~] [~~~] [~~~]_  [~~~]_    William Nolan -- wn22 AT andrew DOT cmu DOT edu
[!!!!!!!!!!] [!!!] [!!!!!] [!!!!!]
 \ _ /\ _ /  [_ _] [_ _ _] [_ _ _]

- Raw text -