HDTenEightyP/NetNews huggingface dataset:
From: mra@searchtech.com (Michael Almond)
Subject: C++ Reports
Organization: Search Technology, Inc.
Date: Fri, 28 Aug 1992 15:41:14 GMT

Does anyone know of a pacakge for C++ (or even maybe just C) that allows
you to design a report and drive it from inside your code?  Or maybe a
library of helper functions for generating reports.

-- 
Michael R. Almond (Georgia Tech Alumnus)          mra@srchtec.uucp (registered)
computer alli, inc.					    mra@searchtech.com
6000E dawson blvd.	      				    uupsi!srchtec!mra
norcross, georgia 30093				        (404) 840-1002 (office)
From: awd@atl.scscom.com (Al Degenaar)
Newsgroups: alt.msdos.programmer
Subject: Re: Truncate a file in MS-DOS with Borland C or C++
Date: 28 Aug 92 14:05:09 GMT
Organization: SCS/Compute, Inc.

In <JPL.92Aug25105414@antares.fct.unl.pt> jpl@fct.unl.pt (Joao Prospero Luis [ps]) writes:

>In article <172@chorus.chorus.fr> mir@opera.chorus.fr (Adam Mirowski) writes:

>>   Trying to make a file restoration utility, I recently noti-
>>   ced that there is no library call in Borland C and C++ to
>>   truncate a file. No truncate() and no ftruncate().
>>

Did you try looking at chsize()?  It performs the equivalent function and
has been in borland at least since 2.0, probably longer.

>>   Is there a clever trick to do to obtain that? I only need
>>   to change the size within the last cluster range: basically
>>   I want to bring a FILExxxx.CHK to its previous (and separately
>>   saved) name/size/date/time/attributes, etc.

>	Do a seek to the location where you want the file truncated
>and write zero bytes.
>	This only works if the call (write, fwrite whatever) really
>does an INT 21h to write zero bytes.

This would also work, but why give up portability...

>	JPL
>--
>Joao Prospero Luis                | BITNET/Internet: jpl@fct.unl.pt
>Universidade Nova de Lisboa       |            UUCP: jpl@unl.uucp
>FCT - Dpto. de Informatica        | Fax:   (+351) (1) 295-5641
>2825 Monte Caparica, PORTUGAL     | Phone: (+351) (1) 295-4464

Al
-- 
Albert W. Degenaar II                               work  : awd@scscom.com
SCS/Compute, Incorporated.                          other : awd@bold1.gatech.edu
#include "standard.disclaimer"                      Phone : (404)368-1040
Newsgroups: alt.msdos.programmer,comp.msdos.programmer
From: swesterback@tnclus.tele.nokia.fi
Subject: Re: XMS - Driver question
Organization: Nokia Telecommunications.
Date: Tue, 1 Sep 1992 16:20:18 GMT

ul1f@rz.uni-karlsruhe.de (H. Dobler) writes:
 
>Hi everybody,
 
>i've a question about the XMS-Driver himem.sys, which is included
>in MS-DOS. I've a 386-PC and 8 MB RAM. Now, i want to use XMS
>and Extended Memory. Is it possible to say HIMEM, that it should
>only use 4MB for the XMS-Memory ? Or is there another XMS-Driver
>outside, which includes this feature ?
 
If you have DOS 5.0 (or even better, Windows 3.1) the himem.sys driver
has a switch called /int15 which allows you to specify how much extended
memory you need. This memory is used trough the INT15h interface by a
few old programs. The rest of the extended memory is then used by XMS.

On the other hand, if you did mean EMS memory (expanded) the ems386.sys
or emm386.exe driver has a parameter that specifies the amount of EMS 
needed.

Personally i dont need EMS-memory in DOS and if i needed it i would let 
Windows emulate it and run the program in a DOS window!

I hope this will help you!

Sten
============================================================================
Sten Westerback                INET: swesterback@tnclus.tele.nokia.fi
Address: Mets{purontie  9 B19, SF-00630 HELSINKI, FINLAND  Time zone: EET
Test the utility at WSMR-SIMTEL20.Army.mil::pd1:<msdos.dirutl>swxd303d.zip
NB! I am working, but not speaking for Nokia Telecommunications!
============================================================================
Xref: sparky alt.msdos.programmer:2260 comp.os.msdos.programmer:8815 comp.lang.pascal:5060
From: holland@matt.ksu.ksu.edu (Rich Holland)
Newsgroups: alt.msdos.programmer,comp.os.msdos.programmer,comp.windows.ms.programmer,comp.lang.pascal
Subject: Re: Windows and printscreen
Date: 26 Aug 1992 07:45:58 -0500
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

beaurega@ireq.hydro.qc.ca (Denis Beauregard) writes:

>In your example, prthru is a Windows program calling tn3270, a Windows
>program too, so int 05 and 09 are catched.  If, however, prthru and
>tn3270 are both DOS programs (i.e. Windows will install DOS prompt before
>running prthru), then you should be able to intercept printscreen, but only
>if the DOS window is active.  It is like a program writting directly to
>the screen (like a text editor I wrote years ago).  In the DOS window,
>the editor writes to the video memory directly so that in DOS full
>screen, the video memory is not intercepted.  However, in DOS window
>with Windows active, when the editor writes to the screen, Windows intercept
>the character, and re-write it on the copy of memory video in the DOS window.

But since they're both DOS programs, redirecting the keyboard interrupt
would work, in the box.  Only in the foreground?  How the *heck* are you 
going to press PRTSCR in a background box?  Why would you do it?  (anyway,
tn3270 runs full-screen by default)...

-- 
Rich Holland              | INTERNET: holland@matt.ksu.ksu.edu
100 Jardine Terr, Apt A7  | BITNET  : holland@ksuvm
Manhattan, KS  66502-3357 | UUCP    : ...!rutgers!matt.ksu.ksu.edu!holland
"Jesus saves...but Gretzky gets the rebound!  He shoots!  He scores!!"
From: remilld@ccu.umanitoba.ca (Jason Remillard)
Newsgroups: alt.msdos.programmer
Subject: Help with DEC LN03|Novell|Ms-Dos
Date: 1 Sep 92 16:09:45 GMT
Organization: University of Manitoba, Winnipeg, Manitoba, Canada

Hello there,

	I need a big favor from someone who has created and/or ported
over a Printer Definition File (PDF) for use on Novell Netware 3.11
to be able to use a Digital LN03r Scriptprinter (PostScript) on the
network..  I can run the printer through Windows 3.1 using their 
Digital LN03r printer driver and it works wonderfully.

	The book for the printer states that I should use the Apple
Laserwrite PLus printer driver, but since when does Digital know anything
about their own products.  I called DEC and they told me to look at 
CompuServe, call Novell and/or Microsoft and ask them for printer drivers.

	I guess that's what you get with 5 figure hardware/software
support charges.....   :.(



Anyways, if anyone knows of someone, or is that someone, please contact
me....




			Thank-You.

---------------------------------------------------------------------------
Jason L. M. Remillard		        remillard@ceddwntwn.lan1.umanitoba.ca
University of Manitoba DOWNTOWN			  --   or   --
MicroLab Assistant			    remilld@ccu.umanitoba.ca
----------------------------------------------------------------------------
Winnipeg, Manitoba - Way up in the Great White North, eh!!!               
----------------------------------------------------------------------------
From: scott@mycro.UUCP (Scott C. Sadow)
Newsgroups: alt.msdos.programmer
Subject: Re: VGA buffer address
Date: 25 Aug 92 14:03:56 GMT

In article <92234.143304KSADEGH@auvm.american.edu>, KSADEGH@auvm.american.edu (Kayvon Z. Sadeghi) writes:
>(stuff deleted)
>I am trying to write a program that reads the screen buffer and changes
>the contants. It works with monochrome display machines as I use the
>adress 0xB000; but when it comes to VGA or any other monitor, it gives me
>some trouble.
>(stuff deleted)


The CGA, EGA, and VGA use 0xB800. Monochrome uses 0xB000. (This is how you
can have 2 monitors on 1 system - one is CGA/EGA/VGA, there is monochome
and there are no address conflicts)


   Scott C. Sadow
   scott@mycro.UUCP
   ...gatech!nanovx!mycro!scott
Newsgroups: alt.msdos.programmer,comp.windows.ms.programmer,comp.windows.ms
From: groeneve@alumni.cs.colorado.edu (GROENEVELT ALEXANDER)
Subject: .wav format for MS Windows
Organization: University of Colorado, Boulder
Distribution: usa
Date: Fri, 28 Aug 1992 15:39:48 GMT

Good day.

I'm looking for specs on the .wav format used with MS Windows 3.1.
If someone could mail me specs on this file format or point me
to source that does conversion with this format (that way I
could get it from the source), then I'd be most appreciative.

Thanks.

groeneve@alumni.cs.colorado.edu
-alex
From: exuptr@exu.ericsson.se (Patrick I Taylor)
Newsgroups: alt.msdos.programmer
Subject: Re: follow-up: VGA buffer address
Date: 25 Aug 92 13:57:37 GMT
Organization: Ericsson Network Systems, Inc.

In article <92237.173922KSADEGH@auvm.american.edu> KSADEGH@auvm.american.edu (Kayvon Z. Sadeghi) writes:
>From: KSADEGH@auvm.american.edu (Kayvon Z. Sadeghi)
>Subject: follow-up: VGA buffer address
>Date: 24 Aug 92 21:39:21 GMT



>And for all of those who send me email: Lets say I have such a code in
>my program.


>struct character{
>    char ch;
>    unsigned char att;
>} *p;
   ^^
try 
  far * p;

 ----------------------------------------------------------------------------
    "This must be Thursday.  I never could get the hang of Thursdays"
                                                       - D Adams
  - Patrick Taylor
    Ericsson Network Systems
    exuptr@exu.ericsson.se                       "Don't let the .se fool you"
    alternately, exuptr@ZGNews.Lonestar.Org
Newsgroups: alt.msdos.programmer
From: boggs@alumni.cs.colorado.edu (Adam Boggs)
Subject: Old dos keyboard int interfering?
Organization: University of Colorado, Boulder
Date: Thu, 27 Aug 1992 06:33:06 GMT

I believe I've posted this once before a long time ago, but didn't get any
replies.  Now that we're on the subject of keyboard interrupts, I thought I'd
ask again.

I am writing my own BBS package, and grab the keyboard interrupt to re-direct
the input to my own buffers, where I parse it with my own routines.  Some of
the characters, however, I check for inside the interrupt, and set status
flage appropriatly.  My problem is that some of the characters (^S and ^P)
don't seem to get passed to my interrupt.  ^S just crashes my system, and
^P tries to output to the printer after I exit the program. (I am aware that
^S is pause and ^P turns on the printer).  Anyway, my assumption is that DOS
(or my shell? I'm using NDOS) captures these.  Can I avoid that... Here's
basically what my code looks like:

void far interrupt comint()
{
   (*OldKeyVec) ();

   if (kbhit()) {
      inchar = bioskey(0);

      switch (inchar) {
         case XOFF: ...
                    break;
         case '\x10': ...     /* ^P   */
                    break;
      }
   }
   outp(0x20, 0x20);          /* Hardware int exit routine  */
}

There are other keys that are compared, but they all seem to work except
for ^S and ^P.  I call (*OldKeyVec)() at the beginning because it changes
the keyboard scan codes to ascii for me (an presumably does something with
my problem characters).  Another possibility is that bioskey() messes it
up. (I'm using TC++ 1.0)  

So, basically, do I need to write something myself that manages the scan codes,
and get rid of (*OldKeyVec)()?  How would I do that if so?

Thanks in advance for any help...

-Adam Boggs
boggs@alumni.cs.colorado.edu

Newsgroups: alt.msdos.programmer
From: adam@microware.com (Adam Goldberg)
Subject: MS-DOS, Just say "No" (was Re: file positioning with buffered/unbuffered I/O)
Organization: Microware Systems Corp., Des Moines, Iowa
Date: Tue, 1 Sep 1992 17:26:28 GMT

In article <4855@news.duke.edu> kds@phy.duke.edu (Stokes Kevin) writes:
>
>   (Christopher H Gregg) writes:
>
>>The program is memory resident and it traps......
>>The problem is that when I try to use either DOS function 13h (delete file)
>>or DOS function 41h (which I would prefer), the program crashes.
>
>  Yuck.  DOS is a piss-poor excuse for an operation system.  My old Data
>General minicomputer (circa 1972) had a really nice true multi-tasking OS 
>which fit in less than 16k.  They should have just ported that.  Of course, 
>there is a famous Bill Gates quote "Our goal is for user to not even know 
>there is an operating system there at all."   (not exact)
>  In my opinion he has already achieved this with DOS.  He has convinced the
>whole world to use computers with no operation system, just a nice binary
>loader!

1) 'nice binary loader':  Well...a binary loader for sure.  Nice?  Hmmm..

2) Then again, there is the (other) famous Bill Gates quote:
       "It is not possible to have a multi-tasking OS in less than 4MB of
       memory." (Talking about Windows NT & Windows 3.x & Dos)

   Right, Bill.  The 1972 DG had it, and for that matter, there are still
   fully-functional modern OSs that'll run in <64k (Like Microware's OS9
   for instance [plug])




-- 
Adam G.
adamg@microware.com, or ...!uunet!mcrware!adamg
The above is not to be construed in any way as the official or unofficial
statements of Microware, or any Microware employees.
Newsgroups: alt.msdos.programmer
From: jcmorris@mwunix.mitre.org (Joe Morris)
Subject: Re: alt 255 ; question
Organization: The MITRE Corporation
Date: Wed, 2 Sep 1992 12:56:06 GMT

garrem@aix.rpi.edu (Matthew Olsen Garretson) writes:

>Is this ALT-255 thing a function of DOS or is it built into the keyboard BIOS?

>If the former is the case, it doesn't work with DOS 5 + 4DOS 4 + ansi.sys .

>If the latter is the case, it doesn't work with my chips.

The ability to generate an arbitrary byte is the responsibility of the
program which fields the keyboard interrupts.

If nobody is trying to be cute, it's the BIOS which interprets <ALT>+digits
as a one-byte character.  Programs which take over the keyboard hardware
interface -- such as Windows -- are responsible for providing the same
feature.

I can't speak for 4DOS because I don't run it.

BTW: the <ALT>+digit construct works only for the *keypad* digit keys.  It
will not work if you try to use the digit keys on the top row of the standard
QWERTY keyboard.

Joe Morris / MITRE
Newsgroups: alt.msdos.programmer
From: franke@andrej.informatik.rwth-aachen.de (Christian Franke)
Subject: Re: Input from parallel port
Organization: Rechnerbetrieb Informatik  /  RWTH Aachen
Date: 26 Aug 92 15:36:01 GMT


dspascha@eos.ncsu.edu (DAVID SCOTT PASCHAL) writes:

>Hi.  I don't know the details (like how to actually do it), but it seems to me I
>read somewhere that you can do it using some of the handshaking lines (but not
>the 8 data lines) but you can only send/receive 4-5 bits at a time! [...]

Laplink pro seems to do the following:

In the 4-Bit mode, an interlocked 4-bit transmission
is done.

	Computer A	direction	Computer B
	DATA0		=>		-ERROR
	DATA1		=>		SLCT
	DATA2		=>		PE
	DATA3		=>		-ACK
	DATA4		=>		BUSY
	-ERROR		<=		DATA0
	SLCT		<=		DATA1
	PE		<=		DATA2
	-ACK		<=		DATA3
	BUSY		<=		DATA4

Because for an interlocked transmission, one input and one output
protocol line are necessary, the transmission cannot occur in full
duplex mode.

In the 8-Bit mode, the same interlocked protocol is used,
but the following 4 (open collector!) I/O lines are used
for the remaining 4 bits:

	STROBE		<=>		STROBE
	AUTOFD		<=>		AUTOFD
	INIT		<=>		INIT
	SLIN		<=>		SLIN

Because laplink has an option to turn 8-Bit mode off,
there may be situations where this mode is not appropriate.


Because there is no hardware support for the interlocked protocol,
the speed is limited by the AT-Bus bandwidth.

To send a nibble/byte the transmitter needs 5 I/O instructions,
the receiver needs 4 I/O instructions:

Transmitter				Receiver

IN	wait for receiver ready
OUT	output data
OUT	say: data ready !
					IN	wait for data ready
						get data (no IN because same port)
					OUT	say: got data !
IN	wait for receiver
OUT	say: data not ready !
					IN	wait for data not ready
					OUT	say: receiver ready

Even on a 50/MHz 486, only about 650.000 I/O instructions can be
performed per second. So the theoretical bandwith limit is

	650.000 / 5 = 130.000 transfers / second.

In practice, because the waiting loops with repeated IN's will be executed
we found a bandwith of about 60.000 transfers / second.


Regards,

	Christian Franke

	Aachen University of Technology
	Lehrstuhl fuer Informatik I
	Ahornstrasse 55
	W-5100 Aachen
	Germany

Newsgroups: alt.msdos.programmer
From: peter@Schultz.ON.CA (Peter Roeser)
Subject: Re: Trapping 386 IO port accesses
Organization: S-S Technologies, Kitchener, ON
Distribution: na
Date: Thu, 03 Sep 1992 15:38:02 GMT

In article <tgreen.715391992@vincent2.iastate.edu> tgreen@iastate.edu (Todd Greenfield) writes:
>
>what about doing this under windows?  I know nothing of windows
>programming,  but wouldn't it be possible to write a windows
>driver (for 386 enh mode of course) to do something like this?

  I have been told that although Windows uses protected mode to do
  memory management( ie. traps when you talk to non-available mem.)
  it does not trap IO references.

>
>I'd be interested in seeing what others think, and how one 
>would go about doing it, as I have a similar need.

  Let's keep the discussion going


-- 
Peter Roeser                 | peter@Schultz.ON.CA
S-S Technologies Inc.        | uunet.uu.net!watserv1.uwaterloo.ca!schultz!peter
88 Ardelt Avenue             | voice: (519) 571-1434 x227
Kitchener, ON Canada N2C 2C9 | FAX:   (519) 743-3610
From: tjb@enh.nist.gov
Newsgroups: alt.msdos.programmer
Subject: com port problem
Date: 30 Aug 92 00:28:41 GMT
Organization: NIST

Hi,
I have an Xt and a 386,
the XT is connected to a printer and a modem
the 386's COM2 is connected to the XT's COM1 through a null-modem
cable.
i want to be able to use the printer&modem from the 386
i can use the printer using a network program, but it's not compatible
with a lot of stuff, and takes up LOTS of memory.
i wanted to use the modem by writing a small C program that
makes the XT transfer COM1 to COM2 and COM2 to COM1
so that COM2(direct link to XT) on the 386 will function as a modem
  386               XT
 ---------      --------------
    COM2  ->   COM1  ->  COM2  ->  modem
    COM2  <-   COM1  <-  COM2  <-  modem

my program so far is:
---------------------------------------------------------
#include <conio.h>
#include <dos.h>
#undef inportb
#undef outportb
#define COM1 0x3f8
#define COM2 0x2f8
#define COM1S 0x3fd
#define COM2S 0x2fd
main()
{
    int com1,com1s,com2,com2s;
    while( !kbhit() )
    {
        com1s = inport( COM1S );
        if( com1s & 2)
        {
            com1 = inport( COM1 );
            outport( COM2, com1 );
            printf("got %d from com1\n",com1);
        }
        com2s = inport( COM2S );
        if( com2s & 2 )
        {
            com2 = inport( COM2 );
            outport( COM1, com2 );
            printf("got %d from com2\n",com2);
        }
    }
}
-----------------------------------------------------------
the program works if i type each letter twice slowly.
does anyone know how to make it work??
Thanks,
Omri Barak
Internet: barak@bguee.bgu.ac.il
Bitner  : barak@bguee
Newsgroups: alt.msdos.programmer,comp.sys.intel,comp.lang.c++
From: ohmann@sab57.larc.nasa.gov (Dale Ohmann)
Subject: Re: Problems with MSC7.0 and Intel 302 box
Organization: NASA Langley Research Center, Hampton, VA  USA
Date: Mon, 31 Aug 1992 14:29:32 GMT

In article <1992Aug28.144629.11627@truevision.com>, Bob Zigon <bobz@truevision.com> writes:
|> I am having a great deal of difficulty getting MSC7.0 to run on an Intel
|> 302 box.
|> This is a 25mhz 386 machine. My tests are showing that there is something
|> strange
|> about the hardware that is preventing the C compiler from running under
|> DOS 5.0.
|> The C compiler (CL) reports the message "R6906 : DOSX32 - not enough
|> conventional memory 
|> for exec". I have worked with Qualitas (makers of 386MAX) to see if they
|> can help. No luck.
|> Microsoft is also looking into the problem. There must be something funny
|> about the
|> machine. I say this because the DOS directory where DOS 5.0 is installed
|> has a README
|> that "singles out" the Intel 302 box whenever you install HIMEM.SYS. You
|> must include
|> a /MACHINE:8 parameter to HIMEM.SYS.
|> 
|> Anyone got any ideas?


I've had a little bit of problem configuring Microsoft C/C++ 7.0, also.
Some additional information about your machine might clear things up.

How much total memory is installed in your machine?
It seems that the compiler (cl) needs about 3Mb in order to compile.  This
implies that your machine should probably have 4Mb if you expect to use
this compiler.

Is a DPMI (386MAX) installed ?
The compiler is a protected mode program.  A Dos Mode Protected Interface
is necessary.

Are you compiling from Programmer's Workbench (PWB)?
If so, check the numeric parameters to see if "keepmem" (I think) is set to
the default of 2Mb.  Change it to something smaller (like 0).  This parameter
controls how much memory is reserved for the editor when it shells out to 
do other things.

-- 
=====================================================
|   Dale Ohmann       ohmann@sabaad.larc.nasa.gov   |
=====================================================
From: mlevis@ringer.cs.utsa.edu (Mike Levis)
Newsgroups: alt.msdos.programmer
Subject: Re: Calling ASM from BC++
Date: 25 Aug 92 23:27:41 GMT
Organization: University of Texas at San Antonio

In article <1992Aug24.204813.16175@schunix.uucp> sonix@schunix.uucp (Duane Morin) writes:
>I'm trying to call an assembly routine from some standard Borland C++ (2.0)
>code.  Here's what I've got (in the C++):
>
>extern foo_bar3(int G, int P);
>.
>.
>.
>foo_bar3(i, x);
>
>And, in the ASM module, I've got:
>
>	PUBLIC	_foo_bar3
>PROC	foo_bar3	FAR
>	ARGS	G:word, P:word
>	.
>	.
>	.
>
>But C++ fails to recognize the foo_bar3 function.  Keeps telling me 
>unrecognized symbol.  As if it doesn't get the connection, because I'm not
>declaring the two int parameters in the actual definition in the ASM file.
>I got the syntax for doing this out of an "Interfacing C and ASM" book, so
>I assume that maybe I need to do somethng else to make this work in C++.

C++ uses name mangling.  Under C, the compiler pre-pends an underline
to the the function name, and writes it to the .obj file for the linker.
Under C++, the compiler also appends extra characters to the function
name.  This is name mangling.

These extra characters are based on the parameters of the function.
This is why you can overload functions in C++ (as long as the parameter
types differ), where as in C you must specify a unique function name.

As the Borland manuals state, the algorithm that Borland C++ uses
to mangle names is undocumented.  In other words, C++ compilers
use different techniques for mangling names.

>Any suggestions?  Minor errors in my transcription of the code might be 
>typos of mine just in this post, as I put that code in there from memory
>and may have slipped up (ARG vs ARGS or something).  Any help, however, 
>still appreciated.

Declare your assembler function with a C interface rather than a
C++ interface.  Change

   extern foo_bar3 (int, int);

to

   extern "C" {
      foo_bar3 (int, int);
   }

There are other ways to call assembler functions from C++.  These
other ways are documented in the Borland Manuals, such as chapter
5, "Interfacing Turbo Assembler with Borland C++".

>Thank you,
> Duane Morin
> Walker Sonix, Inc.
> sonix@schunix.uucp


-- 
==== Mike Levis   mlevis@ringer.cs.utsa.edu ====
::   ftp ftp.cs.widener.edu (147.31.254.132)  ::  .--.
::   for ``The Simpsons'' information.  Get   :: (OS/2)
:::: ``Simpsons'' FAQL in dir /pub/simpsons ::::  ~--~
Newsgroups: alt.msdos.programmer
Subject: Re: alt 255
From: rmathews@zeus.calpoly.edu (Bob Mathews)
Date: Wed, 26 Aug 1992 23:27:18 GMT
Organization: California Polytechnic State University, San Luis Obispo

exuptr@exu.ericsson.se (exuptr@exu.ericsson.se) writes:
>From a program, you can actually put a space (ASCII 32) in the filename.  
>This will prevent some hacker from using the alt-255 trick to delete your 
>file.  Of course, if you create a file ' abc.xyz', it can be gotten rid of
>with the command 'del *.xyz'.

Or with any decent sector editor or directory-maintainence program
like Xtree.  There's virtually no way of stopping a determined hacker,
but tricks like this are good for keeping newbies out of things.  I
used to use the alt-255 thing to keep people from playing my Rogue
games at school...

swehtam bob