HDTenEightyP/NetNews huggingface dataset:
From: bjorndahl@augustana.ab.ca
Newsgroups: comp.os.msdos.misc
Subject: Re: low level format
Date: 2 Sep 92 14:47:06 MDT
Organization: Augustana University College, Camrose, Alberta

In article <1992Sep2.123451.28639@news.clarkson.edu>, gulla@sun.soe.clarkson.edu (Jerry Gulla) writes:
> From article <6-kn4n+.bob@netcom.com>, by bob@netcom.com (Bob Becker):
>> In article <1992Sep2.004228.29293@rei.com> fox@rei.com (Fuzzy Fox) writes:
>>>gt6502a@prism.gatech.EDU (gt6502a BLAKE,JASON) writes:
>>>
>>>>	Does anyone out there know if it is possible to obtain previous data 
>>>>from an IDE hard drive that has been low level formatted?
>>>
>>>You can't low-level format an IDE drive.
>>>
>> You can indeed low level format an IDE drive.
>> You should *NEVER NEVER NEVER* do it, but it can be done.
> 
> There ARE times where you *might* want to low-level format an IDE drive :-)
> I had a Maxtor 213AT that developed "Bad blocks" AFTER using it for several
> months (The disk appeared clean when I first got it, as all IDE drives should).
> After several months, bad blocks started forming (not a good sign!).  Anyway,
> I did several re-partitions and DOS formats, but the bad blocks were always
> there.  After talking to the tech rep several times (and lots of part
> swapping :-) I determined I had a bad IDE card. I downloaded the Maxtor low-
> level format program, swapped the IDE card, did a low-level (then DOS format)
> and wala! my drive is fine (and has been since!)  The low-level format 
> "eliminated" (or mapped out) the bad blocks, so it looks like a clean drive
> again.
> 
> 
> Jerry Gulla
> gulla@sun.soe.clarkson.edu

That is good to know.  Now, what about something like SpinRite?  The one
time I tried SpinRite on an IDE drive that seemed to be having problems
(which we later traced to something entirely different) SpinRite said
it couldn't do a low level format, but could do serious pattern testing and
would relocate blocks that looked like they were going bad.  That would be
about the same thing as Jerry's experience, no?  On the other hand, I know
folks who swear that a SpinRite diskette should never even be in the
same room as an IDE drive! :-)

-- 
Sterling G. Bjorndahl, bjorndahl@Augustana.AB.CA or bjorndahl@camrose.uucp
Augustana University College, Camrose, Alberta, Canada      (403) 679-1516
Newsgroups: comp.os.msdos.misc
From: damien@reg.triumf.ca (DAMIEN GALLOP)
Subject: Re: DRDOS: Lost command.com on stacked c: drive
Summary: HELP!!!!
News-Software: VAX/VMS VNEWS 1.41    
Keywords: DRDOS
Organization: TRIUMF: Tri-University Meson Facility
Date: Mon, 31 Aug 1992 06:26:00 GMT

In article <1992Aug30.180201.6459@dragon.acadiau.ca>, 890025d@dragon.acadiau.ca (Andy DeWolfe) writes...
>Hi netters,
>	I am in big trouble. I accidentaly (sp) copied over
>my command.com on my c: drive.  I am using DRDOS 6.0 and SSTOR.
>Now whenever I boot my computer, and it loads the command.com from
>the non-stacked partition , loads devswap.com, switches all the drives
>around (logically) and then tries to load command.com off the stacked
>drive c:.  Since the command.cpm is no longer there, everything crashes.
>Any suggestions...

No doubt you have a bootable floppy handy. Add the relevant SSTOR files and
a few essential DOS utilities, e.g. SYS.COM, EDITOR.EXE, ... Then adapt your
working DCONFIG, CONFIG, & AUTOEXEC files for use on the floppy, so that
you use the floppy drivers to enable your compressed drives. If you're
really stuck, I'll mail you a bootable floppy!

					All the best. Damien
email: damien@reg.triumf.ca
Newsgroups: comp.os.msdos.misc
From: slegge@kean.ucs.mun.ca
Subject: DR-DOS... DR-Windows??
Organization: Memorial University. St.John's Nfld, Canada
Date: Thu, 3 Sep 1992 04:05:09 GMT

There's an article in the APRIL '92 issue of PC WORLD called "DOS vs 
DOS" where DR-DOS 6.0 and MS-DOS 5 are compared.
 
It's mentioned inthe article that DRI has had (is having?) trouble 
in getting co-operation from MicroSoft for bug-fixes and such.  It
also mentions something about a possible DRI Windows clone.  Has 
anybody heard anything about this kind of development?

As GeoWorks PRO is integrated with DR-DOS 6 (more specifically, the 
TaskMAX) I'm very curious about the possibility of furthur 
developments between the two companies -- GeoWorks and NOVELL.
 
Any information, rumors, or speculations are welcomed!
 
Stephen Legge
<SLEGGE@kean.ucs.mun.ca>
Newsgroups: comp.os.msdos.misc
From: dspascha@eos.ncsu.edu (DAVID SCOTT PASCHAL)
Subject: Re: V86 mode in DOS
Originator: dspascha@c00089-100lez.eos.ncsu.edu
Reply-To: dspascha@eos.ncsu.edu (DAVID SCOTT PASCHAL)
Organization: North Carolina State University, Project Eos
Date: Tue, 1 Sep 1992 21:04:00 GMT


In article <1992Aug30.161432.5655@dragon.acadiau.ca>, 890560p@dragon.acadiau.ca (Trevor Porter) writes:
|> Path: taco!lll-winken!sun-barr!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!news.cs.indiana.edu!nstn.ns.ca!dragon.acadiau.ca!890560p
|> From: 890560p@dragon.acadiau.ca (Trevor Porter)
|> Newsgroups: comp.os.msdos.misc
|> Subject: V86 mode in DOS
|> Message-ID: <1992Aug30.161432.5655@dragon.acadiau.ca>
|> Date: Sun, 30 Aug 92 12:14:32 GMT+5:00
|> Organization: Acadia University
|> Lines: 10
|> 
|> Could somebody please explain V86 mode in DOS.  When I install EMM386.EXE
|> it puts the system in V86 mode.  The MSDOS manual doesn't mention anything 
|> about V86 and some software won't run in this mode.  Is it possible to
|> install EMM386.EXE without going into V86 mode?
|> 
|> Thanks
|> 
|> -- 
|> _-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_                               Trevor Porter    	890560p@dragon.acadiau.ca                               Acadia University                                                               Wolfville, NS, Canada                                                           -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
|>  
|> 


Hi.  On the 8086 and 8088 chips there is one operating mode -- real mode, where
only one megabyte is addressable and any program can read or write any location
in that one megabyte.  The 80286 introduced protected mode, which, like the name
suggests, allows multitasking and protects memory owned by one process from all
other processes running in the system, and up to 16 megabytes can be addressed.
However, virtually all code written for real mode won't run in protected mode.
The 80386 introduced Virtual-8086 mode, which is really a real mode process
running along other protected mode processes.  Programs like Windows which try
to switch the CPU into protected mode themselves can't run in V86 mode.  The
reason that EMM386 uses V86 mode for emulation is that it has to use the page-
translation feature of the 80386 which can only be run from within protected
mode (and in order to make real-mode MS-DOS usable, it has to use V86 mode).
I believe there is a switch to EMM386 (maybe /noems) that will prevent EMM
translation, keep the system in real mode, and allow you to use Windows.

Tschuess,
David Paschal
From: crow@coos.dartmouth.edu (Preston F. Crow)
Newsgroups: comp.os.msdos.misc
Subject: Re: DRDOS: Lost command.com on stacked c: drive
Keywords: DRDOS
Date: 30 Aug 92 20:04:05 GMT
Organization: Dartmouth College, Hanover, NH

In <1992Aug30.180201.6459@dragon.acadiau.ca> 890025d@dragon.acadiau.ca (Andy DeWolfe) writes:

>Hi netters,
>	I am in big trouble. I accidentaly (sp) copied over
>my command.com on my c: drive.  I am using DRDOS 6.0 and SSTOR.
>Now whenever I boot my computer, and it loads the command.com from
>the non-stacked partition , loads devswap.com, switches all the drives
>around (logically) and then tries to load command.com off the stacked
>drive c:.  Since the command.cpm is no longer there, everything crashes.
>Any suggestions... There is a lot of impt stuff that I can't access anymore
>and I don't have any backups.
>-Andy

You will have to boot from floppy and edit your (d)config.sys file on
drive C:.  You need a line like, "SHELL=D:\COMMAND.COM /P."  That should
tell it to load command.com from logical drive D: after the config.sys is
done being processed.  If that doesn't work, copy the sstor driver to
a bootable floppy and a device= line on the floppy's config.sys.  Now
you should be able to read your hard drive (though the drives won't be
swapped).  Simply copy command.com to what is normally drive C: and
you won't have any more problems.

Personally, I would recommend putting command.com in the root directory of
drive C: (logical drive C:, that is) even if you don't think you need it.
You never know when some program will assume that it's there and crash when
you least expect it to.

--PC

--
"If guns were outlawed, only outlaws would shoot people."
"Guns don't kill people, lack of structural integrity of the brain does."
"I wasn't aborted, and I vote!"
Newsgroups: comp.os.msdos.misc
From: fox@rei.com (Fuzzy Fox)
Subject: Re: Windows Enhanced Mode + UMB_DRVR
Date: Thu, 3 Sep 1992 23:56:19 GMT
Organization: Recognition Equipment, Inc.

jliukkon@klaava.Helsinki.FI (Juha-Matti Liukkonen) writes:

>UMB_DRVR versions 5.21 and up *do* work with Windows Enhanced mode. 
>You'll need an EMMExclude = A000-FFFF statement, though, and 4 megs of
>memory.  MONOUMB.386 will also be nice.

I run UMB_DRVR 5.21 with Windows 3.1, with no EMMExclude at all, and 2
megs of memory.  No MONOUMB either.  Works fine.  However, I do tell
UMB_DRVR not to use the area from B000-B7FF, because SmartDrive crashed
when loaded there.  MONOUMB[2].386 did not fix this.

-- 
#ifdef TRUE         | Fuzzy Fox                  fuzzy@netcom.com
#define  TRUE   0   | a.k.a. David DeSimone      an207@cleveland.freenet.edu
#define  FALSE  1   |
#endif              |         How's my posting?  Call 1-800-ALT-FLAME
From: s870694@yallara.cs.rmit.OZ.AU (Alfred Porziella)
Newsgroups: comp.os.msdos.misc
Subject: Windows Enhanced Mode + UMB's is it possible?
Date: 23 Aug 92 16:02:31 GMT


I have installed various UMB providers on my 486sx (Opti Chipset) in order
to load all my TSR's + drivers into upper memory and they have worked fine
as I now have a LOT more conventional memory to work with.

Unfortunately windows 3.0 no longer runs in Enhanced mode and dies returning
a "Insufficient memory to initialise Windows in Enhanced mode, remove any
unecessary drivers and TSR's from config & autoexec files".

The UMB providers I have used are UMB_DRVR.SYS (v5.21) and LASTBYTE.SYS
using HIGHUMM.SYS (v2.11). I can't get either to work with windows.

I have managed to exclude a 64k block at D000-DFFF so that EMM386.EXE (DOS5)
can provide EMS. But windows enhanced mode still wont work!

Any ideas would be appreciated.


       ----------------------------------------------------------------
      |                     Alfred Porziella                           |
      | Royal Melbourne Institute of Technology, Melbourne, Australia. |
      |           Internet : s870694@minyos.xx.rmit.oz.au              |
      |________________________________________________________________|
--
        Whenever you have eliminated the impossible, whatever remains,
             however improbable, must be the truth. - A. Doyle.
From: yhlin@kiwi.ucs.indiana.edu (yue-herng lin)
Newsgroups: comp.os.msdos.misc,in.pc
Subject: Re: Reboot a PC from a batch file.
Date: 29 Aug 92 04:11:33 GMT
Organization: Indiana University, Bloomington

Here's a sample code that you can use Turbo C(++) to do:

#include <dos.h>
void far (*func_ptr)();
main()
{
    func_ptr = (void far *)0xffff0;
    (*func_ptr)();
}
From: fox@rei.com (Fuzzy Fox)
Subject: Re: Windows Enhanced Mode + UMB's is it possible?
Date: Fri, 28 Aug 1992 15:49:06 GMT
Organization: Recognition Equipment, Inc.

Deon.Strydom@p16.f1.n7104.z5.fidonet.org (Deon Strydom) writes:

>The docs of UMB_DRVR clearly states that it doesn't work with Windows.

The docs should be amended to say that it does not work too well with
Windows 3.0.  I run Windows 3.1 with UMB_DRVR all the time, and the only
requirement is that I must exclude the B000-B7FF range from UMB's.

Everything loads high, including Stacker, Novell, Combi, etc...

-- 
#ifdef TRUE         | Fuzzy Fox                  fuzzy@netcom.com
#define  TRUE   0   | a.k.a. David DeSimone      an207@cleveland.freenet.edu
#define  FALSE  1   |
#endif              |         How's my posting?  Call 1-800-ALT-FLAME
From: franks@hpuamsa.neth.hp.com (Frank Slootweg CRC)
Date: Thu, 27 Aug 1992 06:34:37 GMT
Subject: Re: FORMAT under DRDOS
Organization: Hewlett-Packard, The Netherlands
Newsgroups: comp.os.msdos.misc

  On August 5 hjh@swan.dsto.gov.au (H.J.Harvey-AEG. Hi Howie!) wrote:

>I tried formatting some 3.5" HD floppies using FORMAT B: /U under DRDOS V6
>last week.  I noted that all diskettes had only about 1.3Mb out of 1.44MB
>capacity.  Using WIN3.1 formatting worked OK, and doing a diskscan on 
>supposedly bad disks showed no errors.
>
>I fixed the problem by disabling SUPERPCK (using SUPERPCK/D) while formatting.
>Any one noted a similar problem or know exactly why my system behaved
>that way?

  First the good news: I think your "problem" is an innocent feature of
the DR DOS 6.0 FORMAT and SUPERPCK combination. But then again: There
may be danger ahead (see the end of my posting).

  I had some problems reproducing your problem. I started with a
never-formatted diskette (fresh from the box) and did repeated
"FORMAT B: /U" operations, but could not get it to fail. Then I
completely filled the (now already formatted) diskette by
"XCOPY C: B:" (while in the DRDOS directory) and then did a
"FORMAT B: /U". Now FORMAT indeed reported

"1,457,664 bytes total disk space.
 1,345,024 bytes available on disk."

"CHKDSK B:" also reported the same information and (PC Tools 6.0)
DISKFIX reported

"There are multiple copies of the File Allocation Table
 on your disk and at least one copy has been corrupted."

  A subsequent Norton DT (Disk Test, both DISK and FILE test) and NDD
(Norton Disk Doctor, including "test ... for Defective Sectors") gave no
errors and a subsequent CHKDSK gave again the normal "1,457,664 bytes
available on disk.". So, like you, I suspected the Super PC-Kwik disk-cache.

  To cut a very long story short: Now the solution/workaround: After
FORMAT reports the wrong number of "bytes available on disk.", just do :

remove and re-insert diskette and/or
"SUPERPCK /F" (flush cache) and/or
"SUPERPCK /D" (disable cache (does a flush)) and optionally "SUPERPCK /E".

  My suspicion is that the in-memory copy of the FAT is not quite
correct, directly after a "FORMAT B: /U". Flushing the cache or removing/
re-inserting the diskette causes DR DOS to read a fresh copy of the FAT
from the diskette.

  Other notes:

- Sometimes (always?) I also got an error from CHKDSK when the number of
  "bytes available on disk." was wrong :
  "Errors detected /F option required to update disk.
  [blank line]
  720 lost clusters in 215 chains."

- Sometimes the number of "bytes available on disk." was different:
  1,346,560 or 1,346,536.

- I could not reproduce the problem with (PC Tools 6.0)
  "PCFORMAT B: /DESTROY" ("/DESTROY" is like the "/U" of the DR DOS 6.0
  FORMAT).

- I used DR DOS 6.0 without any of the updates, i.e. the pre-Dec'91
  version.

  The only thing which worries me is that if the in-memory FAT is indeed
wrong, then it is perhaps possible that the diskette becomes corrupted
if files are written to it *before* any of the above solutions/
workarounds have been performed. Perhaps the Novell/DRI people could
comment on this scenario and could explain what is "wrong" with FORMAT
and/or SUPERPCK in the first place.

  Hope this helps.

Frank Slootweg
Newsgroups: comp.os.msdos.misc
From: reichert@rtsg.mot.com (Charles H. Reichert)
Subject: Re: A prospective user has questions about DR-DOS 6.xx
Organization: Motorola Inc., Cellular Infrastructure Group
Distribution: na
Date: Tue, 25 Aug 1992 13:58:37 GMT

thouse@csri.toronto.edu (D. Tennenhouse) writes:

>Hi, I'd like to switch to DR-DOS, but I'd like to find out a few things 
>first.

>1.  Can the partition from which DR-DOS would boot be a SuperStore disk or not?

	Yes, but I'd make a small uncompressed drive C and make the other
	partitions compressed.  If you need to, then drive C can be made
        partially uncompressed (for system bootup files) and the rest
        compressed.

>2.  Which programs CAN NOT run with a SuperStore disk.  I am especially
>     interested to know about:
>	a. Any of the Norton utilites V 5.0
>	b. Windows 3.1
>	c. 386MAX
>	d. Microsoft C/C++ 7.0

	My Norton's 4.5 (especially SD) work great on compressed drives.
	Ditto for WIN 3.1, don't know about 386MAX, MS C++ 7.0 but
        Borlands C++ 3.0, MS BASIC PDS 7.1 work great.
        QEMM worked great, but Manifest would hang.  Thinks it had to do with
        the Local Bus Video Card.  It worked great on my previous 386-25DX
        with SSTOR drives.

>3.  Is it true that I could have some logical drives be Superstore, others
>    logical drives non-SuperStore, and yet another partition with another
>    operating system (like Linux) on it?

	Yes, I've done it with OS/2

>4.  I hear that SmartDrive can not run with a SuperStore drive, is that true?
>
	Don't know, never tried it.  SuperPCK.SYS Cache works great with SSTOR
        and none SSTOR drives.


4.a.If SmartDrive can't work with a SuperStore drive, does DR-DOS have its
>    own caching utility that can?

	Ditto with SuperPCK cache supplied with DR-DOSA 6.0.

	BTW, make sure you get the Novell WIN 3.1 update disk which allows
        WIN 3.1 to fly with DR-DOS 6.0


	Chuck Reichert    
-- 
     ====================================================================
     | Charles H. Reichert  708-632-6669 Work - MOTOROLA, INC  Cellular |
     | KD9JQ                708-358-3827 HOME - after 8PM CST  weekdays |
     |                      955 Concord Ln.  Hoffman Ests., IL. 60195   |
Newsgroups: comp.os.msdos.misc,comp.os.msdos.programmer
From: jimmy@namao.ucs.ualberta.ca 
Subject: Simple print routines for DOS
Organization: University of Alberta
Date: Mon, 31 Aug 1992 23:39:50 GMT

Does anyone have routines that can draw lines/text on dot matrix printers ?
I have the lines as a series of points. Basically, I need to draw on paper
just the way I draw on screen (using graphics.lib).
Please email,
Jimmy

--
jimmy@namao.ucs.ualberta.ca
Newsgroups: comp.os.msdos.misc
Subject: Test if Pkt Drv Loaded
From: hippo@sonoma.edu (Michel Davidoff)
Date: 31 Aug 92 15:39:42 PDT
Organization: Sonoma state university

How do I test in a batch file if a 
packet driver has been loaded ?

Thank you
Michel
From: west@esd.dl.nec.com (Mike West)
Newsgroups: comp.os.msdos.misc
Subject: Debug'ing with DRDOS
Date: 31 Aug 92 16:56:10 GMT
Organization: NEC America, Engineering & Support

I have a Adaptec ACB-2372B RLL disk drive controller.  In order to
add a disk to the controller, I must select drive type 1 in the
CMOS setup (no problem), but then I must go to memory location
C800 and run a program which is in the board's ROM to do the
actual configuration of the new disk.  The board's pamphlet
gives instructions on how to do this with MSDOS debug.  However,
I have DRDOS.  How do I do this with SID?

Mike West
west@esd.dl.nec.com
From: sph0301@utsph.sph.uth.tmc.edu (Kate Wilson)
Newsgroups: comp.os.msdos.misc
Subject: Re: DOS environment variables > 128 chars ?
Keywords: environment variable DOS MS-DOS
Date: 23 Aug 1992 19:06:18 GMT
Organization: Univ. of Texas School of Public Health

In article <1992Aug22.005943.26092@pasteur.Berkeley.EDU> dcdeno@bellini.berkeley.edu (D. Curtis Deno) writes:
>I would appreciate your suggestions on the matter of environment variables
>whose length exceeds the 128 (127?) character limit.
[stuff deleted]
>  Is NDOS or 4DOS or xxx superior in this respect?

4DOS will allow a command line up to 255 characters.
Xref: sparky comp.os.msdos.misc:4935 comp.os.msdos.apps:4565
From: alan@acpub.duke.edu (Alan M. Gallatin)
Newsgroups: comp.os.msdos.misc,comp.os.msdos.apps
Subject: Sticky shift key, errant num-lock... Probably a FAQ
Date: 29 Aug 92 04:50:42 GMT
Followup-To: comp.os.msdos.misc
Organization: Duke University; Durham, N.C.
Originator: alan@north7.acpub.duke.edu

Here's one that I'm sure I saw answered over a year ago...

Whenever I have more than 2 or 3 TSR's loaded (low or high), my shift
keys (generally the left one) and my num-lock keys behave strangely.
In particular, at some seemingly random point, every key I type will
be shifted (alphanumeric, function keys, the works) although this
phenomenon is generally NOT preceded by my touching the shift key.
The only cure is to simply press the left shift key and release it,
thereby ending my woes until it all starts up again.

On a related note, when the same (or different!) 2 or 3 TSR's are
loaded and my numeric-lock is enabled, the arrow keys behave
strangely; when I hold them down to auto-repeat, the number associated
with them on the keypad sometimes "sneaks in" or worse yet, takes
over and repeats.  (e.g.  If I held the down arrow repeatedly, one
or many "2" characters will be generated in place of arrow movements).
When this occurs, I am using the arrow keys NOT on the numeric
keypad.  When I disable num-lock, the arrow keys work fine (but I
lose use of my numeric keypad).

Why does this happen?  The TSR's causing it are apparently irrelevant
since any combination of 2, 3 or more seems to be causing it.

I'm using a 486/33 AMI BIOS, although the same problem occured on my
former computer, a 386DX/20 Award BIOS.

Please e-mail responses if possible, although posting is fine.

THANKS!!!!!!!!!

-- 
Alan M. Gallatin <alan@acpub.duke.edu>
Duke University School of Law; Durham NC
Newsgroups: in.pc,comp.os.msdos.misc
From: cummins@a.cs.okstate.edu (CUMMINS JOHN WILLI)
Subject: Re: Missing character questions....
Organization: Oklahoma State University, Computer Science, Stillwater
Date: Thu, 3 Sep 92 20:12:26 GMT

In article <Bu0CD5.5ry@usenet.ucs.indiana.edu> rcbaker@silver.ucs.indiana.edu (Bob Baker) writes:
>While working on converting some VERY old DOS files at work, we've
>discovered an interesting dilemma.  When we do a directory listing of
>the files, we see things like:
>
>H FRAME   TXT   09-01-84  etc., etc.
>S H HOUS  TXT   09-01-84
>.
I use attrib with ? to represent the spaces.  Perhaps copy will work as well!
(copy h?frame*.txt
 copy s?h?hous.txt

Try it!

jc
Newsgroups: comp.os.msdos.misc
From: 890025d@dragon.acadiau.ca (Andy DeWolfe)
Subject: DRDOS: Lost command.com on stacked c: drive
Summary: HELP!!!!
Keywords: DRDOS
Organization: Acadia University
Date: Sun, 30 Aug 1992 18:02:01 GMT

Hi netters,
	I am in big trouble. I accidentaly (sp) copied over
my command.com on my c: drive.  I am using DRDOS 6.0 and SSTOR.
Now whenever I boot my computer, and it loads the command.com from
the non-stacked partition , loads devswap.com, switches all the drives
around (logically) and then tries to load command.com off the stacked
drive c:.  Since the command.cpm is no longer there, everything crashes.
Any suggestions... There is a lot of impt stuff that I can't access anymore
and I don't have any backups.
-Andy


-- 
---------------------------------------------------------------
Andy DeWolfe		Address: andy.dewolfe@dragon.acadiau.ca
Acadia University	Phone  : (902) 883-9894
Canada
Newsgroups: comp.os.msdos.misc