HDTenEightyP/NetNews huggingface dataset:
From: tennis@cs.mcgill.ca (Pascal PROULX)
Subject: WARNING !!!!! MS WINDOWS 3.1 SmartDrive Problem
Organization: SOCS - Mcgill University, Montreal, Canada
Date: Thu, 13 Aug 1992 04:07:31 GMT


The following article was taken from the PC WORLD ONLINE via the America
Online BBS and is an important warning for all MS WINDOWS 3.1 users.

The following information was passed on to PC WORLD ONLINE by PCW George,
(George Campbell, a PC WORLD Editor).

"After considerable testing, I have discovered a major problem with the 
version of SmartDrive included with Windows 3.1. The default installation
of SMARTDRV.EXE enables write caching on your hard disks. Most often this
is not a problem but, under certain circumstances, it could crash your hard
disk. A typical situation is described below :


1) If you use a program wich handles multiple boot-up configurations by using
   alternative Autoexec.bat and Config.sys files then automatically
   re-booting, SmartDrive won't write the new files to the hard disk before
   the computer reboots. This could cause damage to you FAT table if the disk
   write is only partiallt completed. In most cases, however, the copying job
   will not be done, and the computer will reboot safely.

2) In some Windows programs, not enough time is allowed for SmartDRive to
   write files to disk. In this case, if you shut off your computer for some 
   reason, your files will not be saved. In the worst scenario, your FAT tables
   may be damaged.

3) If a power failure occurs during the gap before cached data is written to
   the hard disk, you could damage your FAT tables.


******************
SOLUTION :
******************

Disable write-caching in SmartDrive. This is not a documented in the Windows
Manual, but is ducomented in SmartDrive's help screen. To disable
write-caching, modify the line in your AUTOEXEC.BAT file as shown below :


Original Line (substitute your own drive information)

C:\WINDOWS\SMARTDRV.EXE

Altered line to disable write-caching : (again, supply your own drive info)

C:\WINDOWS\SMARTDRV.EXE C D E (list all hard drives)


This modification will disable write-caching. You will get a minor slowdown
in Windows, but it won't be too noticeable.


Tip from George Campbell (PCWGeorge)
Newsgroups: comp.os.msdos.misc
From: jknepley@nyx.cs.du.edu (Ranseus (Jim Knepley))
Subject: Re: Let's start a DR-DOS newsgroup- All in favor- say aye!
X-Disclaimer: Nyx is a public access Unix system run by the University
	of Denver for the Denver community.  The University has neither
	control over nor responsibility for the opinions of users.
Organization: Nyx, Public Access Unix at U. of Denver Math/CS dept.
Date: Sun, 16 Aug 92 04:42:17 GMT

In article <1992Aug14.203339.7139@novell.com> dougb@novell.com (Doug Barlow) writes:
>Ok, maybe I'm a little biased since I work for Novell but I'm an end-user
>just like the rest of you.  I wouldn't mind seeing a newsgroup about DR-DOS.
>Then, all of the hard-core Microsoft users could stay in their group and
>the rest of us have a place to go to discuss a better product. :-)

Here here!  Mark me down as a hard-fast yes for a DRDOS newsgroup!

>Comments?

Actually, I have one that's not really related to this thread:

Are Microsoft PR people the most efficient group on earth or what?  EXAMPLE:
  Pre-OS/2 2.0
    "Oh, OS/2 sucks, use windows."
  As OS/2 2.0 is released
    "Oh, OS/2 2.0 is ok, but doesn't run as well as windows."
  When OS/2 2.0 is established as a very good 32bit os
    "OK, it's better than windows, but Windows/NT is incredible!"

ANOTHER EXAMPLE: (a little more to the point)
  Pre-DR DOS 6.0
    "DRDOS 5.0?  Just wait for ours!"
  As DR DOS 6.0 is released
    "Bah!  It can't be as good as _OUR_ DOS 5.0"
  When everyone realized that DR DOS 6.0 is better than MSDOS 5.0
    "OK, it's better, but it's not compatible with Windows 3.1!"
  When Novell ships the fix for running Windows 3.1
    "Um, ok, it's still not better, but we're not sure why."

The scary point:
  There are people out there who will take Microsoft at their word!  I've even
heard rumors that DR DOS didn't work right with Netware.  As advertised, they'rea blasted efficient group...

Anyway, yes on the newsgroup...

Jim
From: jliukkon@klaava.Helsinki.FI (Juha-Matti Liukkonen)
Newsgroups: comp.os.msdos.misc
Subject: Re: How to Un write protect a stacker volume
Date: 19 Aug 92 14:41:20 GMT
Distribution: comp.os.msdos.misc
Organization: University of Helsinki

In <1992Aug18.155027.1941@regina.cs.uregina.ca> wall@hercules writes:

>Could some please give me the command that will let me un write 
>protect my stacker volume and drive.  Thanks.  

Run SCHECK program on the drive, it should tell you the proper
operations and commands.

-- 
               Juha Liukkonen, aka jliukkon@cc.helsinki.fi
       University of Helsinki, Dept. of Paranormal Investigations
           "Trust me, I know what I'm doing." - Sledge Hammer
Newsgroups: comp.os.msdos.misc,comp.os.msdos.apps
From: backman@miller.cs.uwm.edu (Bruce A Backman)
Subject: Re: WARNING!!!! major problem with vi and possibly every other app around! (was: help I don't understand write caches like smartdrive 3.1)
Organization: University of Wisconsin, Milwaukee
Date: Thu, 20 Aug 1992 17:44:51 GMT

In article <1992Aug15.074707.24279@leland.Stanford.EDU> gsroka@leland.Stanford.EDU (Gregory Sroka) writes:
>In article <1992Aug14.232515.5824@cco.caltech.edu> nyet@cco.caltech.edu (n liu) writes:
>>The other day I was editing a file with vi and I quit using :q!
>>
>>I lost ALL my changes!!!! I belive this to be a major problem with vi.
>>
>>I've heard lots of other programs do this too.
>
>You are either new to vi or left your terminal unattended. (I've heard
>about those crazy Caltech practical jokers).

#include <HUMOR.H>
Those you who feel the urge to "help" the poor vi user
should first review the recent postings warning about
the SmartDrive program which comes with Windows 3.1.  
The tile is nearly the same, the phrases nearly identical.
CAN YOU SAY SATIRE?  I, personally found it somewhat 
humerous, but maybe that's just too much exposure to 
CRT radiation.

Bruce Backman
My opinions are MINE, ALL MINE! ahahahaha!!
From: slegge@kean.ucs.mun.ca
Subject: re: Let's start a DR-DOS newsgroup
Organization: Memorial University. St.John's Nfld, Canada
Date: Sat, 15 Aug 1992 14:17:14 GMT

> Concerning DRDOS 6.0, what's the process for starting a
> new newsgrou Would someone like to take that responsibility
> to find out?                 Do you lie the name: comp.os.drdos?
>  
>   
> Comments?    
>                                 
 
I second that notion -- I
would appreciate a seperate newsgroup for DRDOS.  COMP.OS.DRDOS sounds
just fine.
 
Stephen Legge
<SLEGGE@kean.ucs.mun.ca>             
Newsgroups: comp.os.msdos.misc
From: colgrove@emba-news.uvm.edu.UUCP (George W Colgrove)
Subject: Re: Let's start a DR-DOS newsgroup- All in favor- say aye!
Originator: colgrove@newton.emba.uvm.edu
Organization: University of Vermont -- Division of EMBA Computer Facility
Date: Mon, 17 Aug 1992 00:45:29 GMT

From article <4049@cruzio.santa-cruz.ca.us>, by aki@cruzio.santa-cruz.ca.us:
> 
> I suggest two groups:
> 
> comp.os.drdos.misc
> comp.os.drdos.programmer
> 
> The second one is very important to the multitude of programmers
> who have to fight with MSDOS "features" and correlating them to
> DRDOS.


	This is true!!   DR is not MS.  DR is better and has features that
	are not exploited much.  I am glad the bookstores shelves are filling
	up with good DR-DOS titles, one of the latest: QUE.  A separate 
	drdos newsgroup would give the OS the reconition it deserves.  
	Perhaps it could be an effective avenue for the MS-DOS woe-ers
	to see what DR-DOS can really do, and they will make the inteligent
	switch like I made and perhaps most of us DR-DOS-ers.

George Colgrove
From: bdette@gumby.Altos.COM ( AOS)
Newsgroups: comp.os.msdos.misc
Subject: Re: Let's start a DR-DOS newsgroup- All in favor- say aye!
Keywords: DRDOS
Date: 18 Aug 92 22:02:33 GMT
Reply-To: bdette@altos.COM (Bob Dette - AOS)
Organization: Altos Computer Systems, San Jose, CA

Count me in too. I'm up to DRDOS 6.01.......


------
Bob Dette      bdette@altos.com  [or]  ...!mips!svcs1!rdette
------
Newsgroups: comp.os.msdos.misc,comp.os.msdos.apps
From: ts@uwasa.fi (Timo Salmi)
Subject: Re: FAQ?
Organization: University of Vaasa, Finland
Date: Sun, 16 Aug 1992 19:01:48 GMT

In article <WRIGHT.92Aug16010053@osric.cs.odu.edu> wright@osric.cs.odu.edu (GENTLEMAN) writes:
>Hi.  Can someone point me to the FAQ for this group.  I want to know 
>if it is possible to obtain shareware via e-mail.  I hear of people doing
>this for macs.  Can it be done for dos, too?  how?? 

Yes.  See below.  It is not a FAQ for this group in particular, but
it covers your question, and, in fact so does the advice below how
to get it.  Also take to reading comp.binaries.ibm.pc.archives if
your site gets it.  You'll find it interesting judging from the
essence of your query. 

112730 Jun 13 12:23 garbo.uwasa.fi:/pc/ts/tsfaq29.zip

"If you do not know how to go about getting this material, users are
welcome to email me for the prerecorded garbo.uwasa.fi instructions
(long, circa 29Kb).  North American users are referred to the garbo
mirror on wuarchive.wustl.edu.  Australian users are referred to the
archie.au mirror.  The mirrors may lag occasionally, or might not
have all the files.  If you do not receive my reply within five
days, please ask your own site's system manager to construct a
returnable mail path for you". 

..................................................................
Prof. Timo Salmi
Moderating at garbo.uwasa.fi anonymous FTP archives 128.214.87.1
Faculty of Accounting & Industrial Management; University of Vaasa
Internet: ts@uwasa.fi Bitnet: salmi@finfun   ; SF-65101, Finland
Organization: Penn State University
Date: Fri, 14 Aug 1992 22:24:17 EDT
From: BOB CONN <REC102@psuvm.psu.edu>
Newsgroups: comp.os.msdos.misc
Subject: Re: Let's start a DR-DOS newsgroup- All in favor- say aye!

AYE!  I'm a new DR DOS user, an old NETWARE 286 user and a new LITE
user.  A DR DOS group would be most useful.
******************************
REC102 @ PSUVM
REC102 @ PSUVM.PSU.EDU (INTERNET)
BOB CONN
PENN STATE UNIVERSITY
******************************
Newsgroups: comp.os.msdos.misc
From: dcdeno@bellini.berkeley.edu (D. Curtis Deno)
Subject: DOS environment variables > 128 chars ?
Keywords: environment variable DOS MS-DOS
Reply-To: dcdeno@bellini.berkeley.edu (D. Curtis Deno)
Organization: EECS Department, UC Berkeley, Berkeley
Date: Sat, 22 Aug 1992 00:59:43 GMT

Fellow netlanders,

I would appreciate your suggestions on the matter of environment variables
whose length exceeds the 128 (127?) character limit.

I have used a utility program (appenv) to construct lengthy environment
variables.  In particular, I use a PATH of about 200 characters to allow
easy access to DOS, a set of utilities, several compilers, and some
applications.  I know this is longer than Microsoft recommends but I am
not fond of cryptic directory names and am wary of SUBST drive letters.
I do not wish to switch between multiple AUTOEXEC.BAT or CONFIG.SYS files.

Almost all programs work fine under this condition.  DOS itself will search
the entire PATH string for .exe files.  My SHELL= line in the config.sys
file specifies a total environment space of 1024 bytes and this usually
leaves a comfortable 200-400 bytes to spare.  I am using MS-DOS 5.0.

My DOS and Windows applications seem quite happy, except for 1 ...

This particular application uses the Phar Lap 386 DOS extender and won't
shell out to DOS properly if any environment variable is > 128 characters.
At least 1 other Phar Lap 386 DOS extended product is not so limited.

What is the story here?  I deplore a 128 character limit and fortunately
found that very few of my applications care.

  Must I introduce SUBST drive letters as shorthand for directories?  If
  so, what are the possible complications?
  Is NDOS or 4DOS or xxx superior in this respect?
  What might go wrong if I continue to use such a long PATH?

-- Curt Deno
Newsgroups: comp.os.msdos.misc
From: prb@chinet.chi.il.us (Paul Botts)
Subject: Floppy drive failure: help!
Organization: Chinet - Public Access UNIX
Date: Thu, 13 Aug 1992 04:01:35 GMT


I'm having trouble with my b: drive on my 386DX, running DOS 5.0 and
Windows 3.1. What happens is, whatever diskette I put in the b: drive,
it reads fine; but then the second and all subsequent diskettes in the
drive do not get read. The dir command just keeps returning the
directory of that first diskette. Among other things, this makes it
impossible to install software from the b drive, since after the first
diskette, the installation program keeps thinking I have the wrong
diskettes in the drive.
I thought perhaps this was some kind of high-memory conflict, as I am
running emm386 (the one that comes with DOS 5.0) to manage high memory.
I tried changing the include and exclude statements, removing them, even
remarking out the config.sys line with emm386 altogether - but no
change.
Any suggestions? DO I just have defective BIOS, maybe? No troubles with
the a: drive or hard drive access, just b:.

Any help appreciated....

Paul Botts
prb@chinet.chi.il.us
From: DOUG@novell.com (Doug Smith)
Newsgroups: comp.os.msdos.misc
Subject: Re: Let's start a DR-DOS newsgroup- All in favor- say aye!
Date: 14 Aug 92 21:04:11 GMT
Organization: Novell NPD

In article <1992Aug14.203339.7139@novell.com> dougb@novell.com (Doug Barlow) writes:
>From: dougb@novell.com (Doug Barlow)
>Subject: Let's start a DR-DOS newsgroup- All in favor- say aye! 
>Date: Fri, 14 Aug 1992 20:33:39 GMT
>Ok, maybe I'm a little biased since I work for Novell but I'm an end-user
>just like the rest of you.  I wouldn't mind seeing a newsgroup about DR-DOS.
>Then, all of the hard-core Microsoft users could stay in their group and
>the rest of us have a place to go to discuss a better product. :-)
>
>Seriously, I think that it would do a lot of good.  You'd be suprised how
>many people at Novell read news about people's concerns about our product
>line.  A lot of people wouldn't mind hearing what you think could be improved
>and also what you like about a product.
>
>Concerning DRDOS 6.0, what's the process for starting a new newsgroup? Would
>someone like to take that responsibility to find out?
>Do you like the name: comp.os.drdos?
>
>Comments?
>
>--------------------------------------------------------------------------
>Doug Barlow                   Email: DOUGB@NOVELL.COM
>Novell, Inc.  Provo, UT
>            The opinions expressed above are solely my own and
>	    do not in any way represent the opinions of Novell, Inc.
>--------------------------------------------------------------------------


Agreed!!

Doug Smith
Novell NPD
jdsmith@novell.com
Newsgroups: comp.os.msdos.misc
From: GSPIEGEL@bsa1.kent.edu (Greg Spiegelberg)
Subject: DOS 5.0 bootup woes
Keywords: DOS5
Organization: Kent State University, School of Business Admin
Date: Fri, 21 Aug 1992 15:17:13 GMT

We have an old AST 286 Inboard machine here that we're trying to upgrade 
to DOS 5 and it doesn't want to boot up.  The drive is fine and so's the 
machine.  It'll boot okay on the hard drive (DOS 3.3) though.

Anyone run into any problems like this??

-Greg

gspiegel@bsa1.kent.edu
greg@bsamail1.kent.edu
Newsgroups: comp.os.msdos.misc,comp.os.ms-windows.misc
From: fox@rei.com (Fuzzy Fox)
Subject: Re: Why DOS 5.0 for Windows 3.1 ???
Date: Fri, 14 Aug 1992 17:50:49 GMT
Organization: Recognition Equipment, Inc.

milan@bcsaic.boeing.com (Milan Richter) writes:

>I am presently running Windows 3.1 with DOS 4.01. Is it worth it to upgrade
>to DOS 5.0? What specifically do I gain?

DOS 5 has many advantages.  It does not require SHARE.EXE for large
media hard drives.  It takes less memory than DOS 4, even if you don't
load it high.  If you do load it high, it takes phenomenally less memory
than DOS 4.  DOS 5 supports upper memory blocks, which Windows will use.
Under a DOS 5 shell from Windows 3.1 you can have as much as 600K free,
with the proper setup.

-- 
#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
Newsgroups: comp.os.msdos.misc,comp.os.msdos.apps
From: cantor@boa.cis.ohio-state.edu (scott eric cantor)
Subject: Re: WARNING !!!!! MS WINDOWS 3.1 SmartDrive Problem
Organization: The Ohio State University, Department of Computer and Information Science
Date: Fri, 14 Aug 1992 15:27:04 GMT

In article <1992Aug14.141659.328@csc.canterbury.ac.nz> cctr132@csc.canterbury.ac.nz (Nick FitzGerald, CSC, Uni. of Canterbury, NZ) writes:
>In article <1992Aug13.202720.22761@serval.net.wsu.edu>,
>mwoodwar@yoda.eecs.wsu.edu (woodward matthew d - CS350) writes:
>> In article <1992Aug13.040731.2286@cs.mcgill.ca> George Mitchell (passed on)
>> writes...
>[George Mitchell's warning about smartdrive deleted]
>> 
>> George is correct that this is dangerous.  This, however, is neither a bug
>> nor a problem with the Win 3.1 smartdrive program.  
>
>I agree it's not a bug - some may disagree that it's not a problem.  To
>make write-behind caching the -default- and --NOT-- clearly explain this
>to users - many of whom will have no concept of what disk caching is,
>let alone the potential problems of write-behind caching - is bordering
>on negligent, IMHO.

	I can see your point for users who don't understand caching, but
I simply haven't had any problems with it at all.  I have no reason to
want it off.

> 
>> The problem is PC users who don't think before they flip the switch, and 
>> Microsoft not trapping the warmboot vector to flush the cache before a 
>> warmboot.
>
>This is incorrect to the best of my knowledge.  With smartdrive loaded,
>at DOS proper - not a DOS prompt run from inside Win31 - the keyboard to
>screen response is slower on my 386/20-8MB than on an XT/4.77, much
>slower.  I take this as evidence that smartdrive totally usurps the
>keyboard for its own purposes - presumably to catch Ctrl/Alt/Del.  Once
>Win31 is running it can drop this practice, as Windows does the reboot
>checking for it and presumably signals smartdrive to flush its unwritten
>buffers should the user actually insist on rebooting.
>
>Anyone know better?
>

	Smartdrv does indeed trap Ctrl-Alt-Del and flush the buffer before
rebooting.

	 _______________________________________________________
	|							|
	|	Shine on.........				|
	|			Scott <Crazy Diamond> Cantor	|
	|							|
	|	[<<<<<< cantor@cis.ohio-state.edu >>>>>>]	|
	|_______________________________________________________|
From: as789@cleveland.Freenet.Edu (Francisco J. Diaz)
Newsgroups: comp.os.msdos.misc
Subject: Re: MS-DOS 6?
Date: 21 Aug 92 23:26:28 GMT
Organization: Case Western Reserve University, Cleveland, Ohio, (USA)


Yes, it's true. It will include an antivirus, disk data compress
ion utility and some other goodies. I can tell you that the main
players in DOS 6.0 will be Central Point, Symantec and others.
How do I know it? I have a friend that works for Microsoft and he
told me all about it, he even told me the exact programs that will
be included in MSDOS v6.0, I could tell you everything but rather
wait until it comes out..:-) (Plus don;t want my friend to get
fired!) :-) Cheers! :-)
-- 
|     Francisco J. Diaz Rivera     |                           |
|     University of Puerto Rico    | If the shoe fits, buy it! |
|  "I hate calculus classes!" :-)  |           - Imelda Marcos |
|     STUD137@CUTB.UPR.CLU.EDU     |                           |
Xref: sparky comp.os.msdos.misc:4685 comp.os.ms-windows.misc:2021
From: milan@bcsaic.boeing.com (Milan Richter)
Newsgroups: comp.os.msdos.misc,comp.os.ms-windows.misc
Subject: Why DOS 5.0 for Windows 3.1 ???
Date: 12 Aug 92 16:28:54 GMT
Organization: Boeing Computer Services AI Center, Seattle

I am presently running Windows 3.1 with DOS 4.01. Is it worth it to upgrade
to DOS 5.0? What specifically do I gain?

Thanks for advice.

==========================================================
== Milan Richter                                        ==
== Boeing Computer Services     milan@atc.boeing.com    ==
== M/S 6C-04                    tel.: 206-477-5202      ==
== P.O. Box 24346               fax.: 206-477-1001      ==
== Seattle, WA 98124-0346                               ==
==========================================================
Newsgroups: comp.os.msdos.misc
From: dspascha@eos.ncsu.edu (DAVID SCOTT PASCHAL)
Subject: Re: DOS environment variables > 128 chars ?
Originator: dspascha@c00083-100lez.eos.ncsu.edu
Keywords: environment variable DOS MS-DOS
Reply-To: dspascha@eos.ncsu.edu (DAVID SCOTT PASCHAL)
Organization: North Carolina State University, Project Eos
Date: Sat, 22 Aug 1992 19:39:38 GMT


Hi.  The only reason environment variables are "limited" to 128 characters is
because of COMMAND.COM's 128-character limitation for command lines, which is
based on DOS's 128-character limitation for passing command-line parameters to
child processes.  Except for what you mentioned, the only problem I can forsee
with using too-long environment variables is when you put a line in a batch file
that references environment variables, such as:

@echo off
set oldpath=%path%
path c:\new.dir\to.add\to.path;%path%
.
. (do something)
.
path %oldpath%

When COMMAND.COM expands lines contining %variable% or %number, any characters
past the 128th or so are truncated.  Thus, you will lose part of your PATH in
the fragment above!

Tschuess,
David Paschal
From: aki@cruzio.santa-cruz.ca.us
Newsgroups: comp.os.msdos.misc
Subject: Re: Let's start a DR-DOS newsgroup- All in favor- say aye!
Date: Sat, 15 Aug 92 23:07:56 PDT
Reply-To: aki@cruzio.santa-cruz.ca.us


I suggest two groups:

comp.os.drdos.misc
comp.os.drdos.programmer

The second one is very important to the multitude of programmers
who have to fight with MSDOS "features" and correlating them to
DRDOS.

Aki.
-- 
/  Phone: 408-662 9664   Fax: 662 9676  |  "Aki" pronounced: Ah-Key. I know  \ 
\  125 Searidge Ct #D, Aptos, CA 95003  |  what I'm doing most of the time.  /
From: pvonk@scott.skidmore.edu (Pierre VonKaenel)
Newsgroups: comp.os.msdos.misc
Subject: Re: How to Un write protect a stacker volume
Date: 20 Aug 92 21:17:27 GMT
Distribution: comp.os.msdos.misc
Organization: Skidmore College, Saratoga Springs NY, 12866

In article <1992Aug20.145620.17443@rei.com> fox@rei.com (Fuzzy Fox) writes:
>discar@nosc.mil (Joe Discar) writes:
>
>>>>Could some please give me the command that will let me un write 
>>>>protect my stacker volume and drive.  Thanks.  
>
>>  .... [an incorrect reply]...
>>
>---> THIS IS TOTALLY WRONG!  DO NOT PERFORM THE ABOVE OPERATION!!! <---
>
>Stacker write-protects the hard drive when it finds a serious error in
>the data tables that it uses.  Use the programs CHKDSK (from DOS) and
>SCHECK (from Stacker) to fix the disk, and it will not be write
>protected anymore.
>

I *just* found myself in the same situation yesterday :-(
Unfortunately, I get the error when stacker tries to start up and
hangs with a message saying "wrong version or missing command
processor".  I can't use SCHECK since Stacker won't come up.  Can't
use CHKDSK since system hangs.  Even more unfortunately, I didn't
think of trying CHKDSK from a boot floppy.  This is the situation
where the stacker drive becomes the C disk (after swapping drives); I
suspect that the command.com version on the stacker volume was messed
up.  Since stacker won't come up, I didn't see a way of copying a
fresh version of command.com to stacvol.dsk.  Today I get to reinstall
EVERYTHING. 

Question:  (this is hindsight)  If I edit out the line in config.sys
that swaps the C and D drives and then bring up Stacker, will the
stacker volume appear as D and can I get into it, even if the volume
is "write-protected"?



-- 
Pierre von Kaenel	| Skidmore College	     | pvonk@scott.skidmore.edu
Math & CS Dept.		| Saratoga Springs, NY 12866 | (518)584-5000 Ext 2391
When asked his position on euthanasia, our local state rep. responded:
"I support youth all over the world."
Newsgroups: comp.os.msdos.misc