🚀 go-pugleaf

In article <1993Jan4.223742.11978@rei.com> fox@rei.com (Fuzzy Fox) writes:
#>FJ>If you have let Stacker 'swap' the drives, so that your 390 MB stacked
#>FJ>drive is seen as C, you are simply asking for trouble (IMHO).
#
# .....  However, I do recognize that there is a class of users who have
#a use for SSWAP.  Users who have a LARGE amount of software installed
#may enjoy the convenience of not having to reconfigure the software.

Some time ago I reorganised one of the PC's I use to combine 3 partitions
(pre-Dos5) into one large DOS5 one, and then restored C: and D: backups
together to C:.  That moved most of my Windows stuff from D: to C:. 
It was a nightmare getting it all to work again!  In retrospect, it might
have been better to have put a day aside to reinstall Windows and all my
applications from scratch, and a second going through all the
reconfiguration and local setups I had.  I did have to re-install some
things in the end anyway.

The .ini files are text, but the .grp files are binary and they 'know' the
drive letters too.  I do have a binary editor but when I changed C: to D:
in .grp files Windows objected - I guess they are sum-checked in some way.

So when I bought STACKER and found it would put all my software into a new
drive (E: on my system), I was VERY glad that SSWAP would hide this from all
my programs.  Thankyou for your warning, but I'll take the risk that some
future drivers will get confused.   And I can see why using SSWAP is the
installation default - I don't think STACKER would survive the average user
installing it and then finding that Windows would not start!

I did have a problem with STACKER by the way; quite often it would be unable
to read a perfectly good file, with DISK ACCESS errors, then after doing a
retry it would work again.  I called the UK STACKER Technical Support, and 
was told to change /EMS to /NB in the first stacker line in my CONFIG.SYS,
which has solved the problem.  Aparently Stacker 3 has EMS contention on
some systems.  I'm not totally happy about this bug, as it means loosing 
more conventional RAM, but her fix has worked.

Regards, 
        David Wright  BNR Europe Ltd, London Road, Harlow, Essex  CM17 9NA, UK
dww@bnr.co.uk  <or> dww@bnr.ca  <or> uunet!stl!dww  <or> PSI%234237100122::DWW
<or> /g=David/s=Wright/org=STC Technology Ltd/prmd=STC plc/admd=Gold 400/co=GB
My other computer is a VAX but today I'm running on a Sun from this PC terminal