#: 40485 S4/Stacker 3.1
    24-Nov-93  17:56:41
Sb: DOS 6.2 install
Fm: Stac Electronics 75300,2755
To: David L. Dows 70373,1233 (X)

David,

basically, people whom a running Stacker 3.1 with files dated after 9/8/93.
This indicates they have the updated files for a compressed hard card.

Keith Dunlea, Stac Tech Support

#: 40821 S4/Stacker 3.1
    30-Nov-93  11:36:10
Sb: #DOS 6.2 on SCSI
Fm: James Kafura 73677,1077
To: Stac Electronics 75300,2755 (X)

Keith,

I am sorry that I did not make myself clear.  I did go through the exercise of
running REDBL.  All that does is recreate the DBLSPACE.BIN file, which I
preserved in tact before I tried to STEPUP.  This file is not damaged.  It
works just fine with MSDOS6.0.  I also went through the exercise of of STEPUP
on a non-SCSI drive without difficulty.  When I try it on my SCSI system, the
drive locks up as soon as it prints the STACKER message on the screen.  It
never makes it to the config.sys file (which I deleted).

Jim

There is 1 Reply.

#: 41013 S4/Stacker 3.1
    01-Dec-93  15:32:35
Sb: #40821-#DOS 6.2 on SCSI
Fm: Stac Electronics 75300,2755
To: James Kafura 73677,1077 (X)

James.

Reboot and hod CTRL-ALT-SHIFT to bypass the loading of Stacker. If it still
locks the problem is not caused by Stacker.  You may need to re SYS the drive
as the boot files maybe damaged.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41024 S4/Stacker 3.1
    01-Dec-93  16:03:28
Sb: #41013-#DOS 6.2 on SCSI
Fm: James Kafura 73677,1077
To: Stac Electronics 75300,2755 (X)

Keith,

I guess that I did not make it clear that I already did this.  It will boot up
fine if I bypass Stacker, but of course, I cannot access my stacked drives.
Also, there is nothing wrong with my dblspace.bin, as I can use it with DOS6.0.

Thanks,

Jim

There is 1 Reply.

#: 41271 S4/Stacker 3.1
    03-Dec-93  19:02:06
Sb: #41024-DOS 6.2 on SCSI
Fm: Stac Electronics 75300,2755
To: James Kafura 73677,1077

James,

Ok, try booting and hold F5 to bypass config/autoexec amd just load Stacker.
Does it still lock ?

background information: did it work fine under DOS 6.0 ?  Right after you
installed DOS 6.2 was it able to reboot ?  or did you immediately copy in the
old config/autoexec and dblspace.bin file ?

Sorry for all the questions but we have no other reports of this happening.

Keith Dunlea, Stac Tech Support

#: 40822 S4/Stacker 3.1
    30-Nov-93  11:36:26
Sb: DOS 6.2 on SCSI
Fm: James Kafura 73677,1077
To: Michael Chan 100033,3524 (X)

Thanks for the tip, but I have never had a problem loading stacker high.  I
have an ASPI compliant driver that allows loading high.  This is, of course,
not pertinent to the discussion at hand since I cannot even load the operating
system which loads dblspace.bin (low).

Jim

#: 40486 S4/Stacker 3.1
    24-Nov-93  17:56:44
Sb: #Stacker 3.1 & WfW 3.11
Fm: Stac Electronics 75300,2755
To: Jono Slack 100042,107 (X)

Jono,

As we already stated, its being looked into.  I realize you'd like an immediate
answer but we're doing our part and will looking into all possibilities of
running WFW 3.11 with Stacker. Thanks for your patience.

Keith Dunlea, Stac Tech Support

There are 2 Replies.

#: 40559 S4/Stacker 3.1
    25-Nov-93  15:20:18
Sb: #40486-Stacker 3.1 & WfW 3.11
Fm: Jono Slack 100042,107
To: Stac Electronics 75300,2755 (X)

<<  Thanks for your patience.  >> oops - sorry for my imp' I must say I do
sympathise with you guys, having to come up with the goods at the drop of
Microsoft's hat.

Best Wishes

#: 40585 S4/Stacker 3.1
    26-Nov-93  15:20:00
Sb: #40486-Stacker 3.1 & WfW 3.11
Fm: Colin Strain 100022,665
To: Stac Electronics 75300,2755 (X)

Keith,
        if I may but in here, I am especially pleased to note that STAC are
'looking into' this issue, and I, for one, and for once, will try to be
patient.  I know it's not easy, but things are made so much easier when someone
is honest enough to say 'it's being worked on' - (obviously) with a view to a
successful conclusion. I hope (and trust( that you will be successful.

#: 40638 S4/Stacker 3.1
    27-Nov-93  17:32:26
Sb: #Still lost CD
Fm: DAVID H. BETOF 70754,1471
To: Stac Electronics 75300,2755 (X)

I am experiencing a problem in attempting to install a Mitsumi CD-ROM on a
Gateway 486 with Stacker 3.1 installed.
Their are at least two isues:
1. How is the new drive designated during the install process (note: there is
an L: switch to indicate the drive to be assigned-which I entered E: since I
compressed my entire hard drive.
2. Upon attempting to complete the installation of the Mitsumi Cd-ROM device
Drivers FX series version 1.1 I get the following message:
  Run-time error R6001
        -null pointer assignment

Gateway Tech support is at a loss, and referred the problem to Stac through me.
Please also note that on my other Gateway 486 WITHOUT Stacker the software
installs flawlessly.

HELP.............Thanks

There is 1 Reply.

#: 40878 S4/Stacker 3.1
    30-Nov-93  18:47:47
Sb: #40638-#Still lost CD
Fm: Stac Electronics 75300,2755
To: DAVID H. BETOF 70754,1471 (X)

David,

Their default install may try to use drive D.  Edit the Stacker.ini file and
add /BD=E  to mount Stacker on E.   then reinstall the cd-rom software as it
will use D

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40933 S4/Stacker 3.1
    30-Nov-93  19:26:50
Sb: #40878-Still lost CD
Fm: DAVID H. BETOF 70754,1471
To: Stac Electronics 75300,2755 (X)

You were correct...........Thanks

#: 41082 S4/Stacker 3.1
    01-Dec-93  21:45:10
Sb: #PCTools 9.0/Stacker Prob
Fm: Richard Dunn 70523,514
To: Edward Nutter [Stac] 75330,2222 (X)

Edward,
        PMJI, noted comment on NU 7... does Stacker 3.1 work well with the new
Norton Desktop for Windows 3.0, also?? ...particularly the disk doctor, etc.
utilities?? (Any problems noted yet?) Thanks, RDunn 

There is 1 Reply.

#: 41126 S4/Stacker 3.1
    02-Dec-93  15:24:56
Sb: #41082-#PCTools 9.0/Stacker Prob
Fm: Edward Nutter [Stac] 75330,2222
To: Richard Dunn 70523,514 (X)

Rich,

I don't know if we integrate with the desktop, but all the latest Norton
Utilities work on Stacker drives, including SpeeDisk (v 7.x or higher)

Edward Nutter
Stac Electronics Product Support 

There is 1 Reply.

#: 41291 S4/Stacker 3.1
    03-Dec-93  22:23:21
Sb: #41126-#PCTools 9.0/Stacker Prob
Fm: Ron Lewis 72377,1474
To: Edward Nutter [Stac] 75330,2222 (X)

Maybe it's me, but PCTOOLS (Central Point Software) is not the same as Norton
anything?  What gives?

There is 1 Reply.

#: 41380 S4/Stacker 3.1
    06-Dec-93  12:08:05
Sb: #41291-PCTools 9.0/Stacker Prob
Fm: Edward Nutter [Stac] 75330,2222
To: Ron Lewis 72377,1474

Ron,

I'm not sure what you're asking, but PC Tools is of course a Central Point
product.  Their latest version (PC Tools 9 Pro) is Stacker aware, or so I'm
told. We haven't finished our own tests on it yet.  Norton and all those
utilities were bought by Symantec.  All the Norton utilities other than
SpeeDisk have worked on Stacker drives since forever.  As of version 7,
SpeeDisk has also worked correctly on Stacker drives.

Edward Nutter
Stac Electronics Product Support 

#: 40505 S4/Stacker 3.1
    24-Nov-93  18:39:12
Sb: #Lost Drive - Need Help
Fm: Edward Nutter [Stac] 75330,2222
To: Joe Miller 72167,2014 (X)

Joe,

<< I cannot access the dead disk.  DOS tells me it is stacked and wont work on
it. >>

Those two sentences contradict each other.  If DOS is saying that the disk is
stacked, then the disk is being accessed.  If DOS could not access it, then it
would return a message about an invalid drive.  You can't have it both ways.

If you can get to any DOS prompt on that machine, type "C:" and press enter.
If you get a C:_ prompt, then enter the DIR command.  If you don't get an error
message (other than "file not found") then you are accessing the hard disk.  If
you are accessing the hard disk then enter: DIR /AH
Let us know what files show up.

Edward Nutter
Stac Electronics Product Support 

There is 1 Reply.

#: 40531 S4/Stacker 3.1
    24-Nov-93  23:12:32
Sb: #40505-#Lost Drive - Need Help
Fm: Joe Miller 72167,2014
To: Edward Nutter [Stac] 75330,2222 (X)

Ed. - We are on a merry-go-round.  I repeat - I cannot access the disk. You
interpret DOS your way and I'll do it mine. I have two hard drives. A C-drive
and a D-drive.  My C-drive works and my D-drive doesn't. When I try to use
F-Disk DOS says it cannot access the drive.  When I try to stac the D-drive
again stac tells me it is already stacked. OK, both DOS and stac are accessing
the drive. - Now what.  In all the messages in this thread I have said I cannot
access the drive. The drive is dead.  You people are the experts. Tell me what
to do now - and I don't need English lessons. =jm=

There is 1 Reply.

#: 40556 S4/Stacker 3.1
    25-Nov-93  14:41:00
Sb: #40531-#Lost Drive - Need Help
Fm: Joe Miller 72167,2014
To: Joe Miller 72167,2014 (X)

To Ed Nutter - Ed.- To be very specific about what happens.: I boot on the
C-drive which is working and following your instructions I enter "dir d:/ah".
The computer responds with "Not ready reading drive D" - "Abort, Retry, Fail".
  If I go through the procedure for a low level format of drive-D the drive
light will go on for a long length of time but the drive has not been low level
formatted. If I use FDISK the program will tell me "Unable to access Drive 2."
If I use the Stac commands and enter SCREATE D: I get the message "SCREATE
ERROR #27:  Drive is write protected or other error. Please insert a non-write
protected disk and try again."
 The Stacker drive map is as follows: Drive a: was drive A:  at boot time;
Drive B: was drive B: at boot time; Drive C: was drive C: at boot time; Drive
D: was drive D: at boot time [ * -- Not monted ] No available replacable
drive(s).
  When I said I was unable to access drive D, I said it in the sense that FDISK
returns the same wording.  Obiously something is going on and the disk is being
accessed but not in any way to do me much good.
  Now what?  =jm=

There are 2 Replies.

#: 40762 S4/Stacker 3.1
    29-Nov-93  20:02:15
Sb: #40556-Lost Drive - Need Help
Fm: Stac Electronics 75300,2755
To: Joe Miller 72167,2014 (X)

Joe,

edit your Stacker.ini or Config.sys file.  On the Stacker line there must be a
* which is creating the fictious drive D.

If Stacker is not on the machine, remove all references to Stacker from the
config.sys and or Stacker.ini file.  They would reside on drive C.  Type DIR C:
/AH

Keith Dunlea, Stac Tech Support

#: 40780 S4/Stacker 3.1
    29-Nov-93  20:43:59
Sb: #40556-Lost Drive - Need Help
Fm: Edward Nutter [Stac] 75330,2222
To: Joe Miller 72167,2014 (X)

Joe,

<< If I go through the procedure for a low level format of drive-D the drive
light will go on for a long length of time but the drive has not been low level
formatted. If I use FDISK the program will tell me "Unable to access Drive 2."
>>

This sounds like a problem with the disk drive itself.  If FDISK can't access
it, then neither can DOS, and neither can Stacker.

If you're loading Stacker at boot, and there is no Stacker drive for it to
mount, then here's what's happening.

We identify ourselves to DOS as a block device driver.  When we do that, DOS
creates an entry in the drive table and returns it's location to us.  This
entry will be accessed by the next available letter.  If we're not given a
STACVOL to mount, we just exit and this dummy drive letter remains in the
table.

Your hard drive is so far gone that DOS dosn't recognize that it exists.
Therefore it never gets assigned a drive letter.  There's no D: when Stacker
loads, so D: gets assigned to us.

The "Drive 2" as reported by FDISK and "D:" as reported by DOS are not the
same.  One is a hard drive and the other is the DOS logical construct.  This is
a hardware problem.

Edward Nutter
Stac Electronics Product Support 

#: 40557 S4/Stacker 3.1
    25-Nov-93  14:53:01
Sb: #Loading Stacker 3.1
Fm: Robert Sobolevitch 75570,1641
To: Stac Electronics 75300,2755 (X)

Keith - pardon me for jumping in here but my memory fades on how to do things
and this seems an appropriate catagory. I am a registered owner of Stacker 3.0
and purchased the 3.1 upgrade from you folks. My computer has had - shall we
say a traumatic incident <g>- and all data was erased and we reloaded. I now
have Dos 6.2 loaded but no Stacker at all. Do I load 3.0 followed by 3.1 or
will the disks from 3.1 alone suffice?

Second question. I have installed a Bernoulli drive which has removable disks.
Can I stack one disk for storage and then replace it with another disk that is
used unstacked?

Bob Sobolevitch, Berwyn, PA 

There is 1 Reply.

#: 40763 S4/Stacker 3.1
    29-Nov-93  20:02:23
Sb: #40557-Loading Stacker 3.1
Fm: Stac Electronics 75300,2755
To: Robert Sobolevitch 75570,1641 (X)

Robert,

If DOS 6.2 is loaded you can install Stacker 3.1; its a stand alone.

Stacker can compressed Bernoulli's as well.  No problem swaping in compressed
and non-compressed disks.

Keith Dunlea, Stac Tech Support

#: 40528 S4/Stacker 3.1
    24-Nov-93  22:39:23
Sb: ..disk write error..
Fm: Mark D. Robinson 73314,636
To: Edward Nutter [Stac] 75330,2222 (X)

The config.sys file was sent to Keith Dunlea. However, I seem to have the
problem solved. A friend suggested moving my hard card device driver (my hard
card is my boot drive) to the very top of the file, even ahead of the windows
memory driver. It worked. No more error messages. No more check /f needed when
I boot.


#: 40605 S4/Stacker 3.1
    27-Nov-93  00:48:43
Sb: #Is WFWG 3.11 compatible?
Fm: Charles Brannon 70720,462
To: Michael Chan 100033,3524 (X)

Don't worry, the 64K limits for the GDI and heap are a relic of the code needed
to make Windows run on a 286.  Can you believe it?  The 286 chip can only span
64K at a time, so your 9Mb is divided up into little pieces.  This is obviously
inefficient.

The flat memory model used by Windows NT, OS/2 and soon Win 4.0 (Chicago) only
works on 386s and above (486, Pentium).  It treats all your memory as one
continuous stream, so there are, in principle, no limits to resources. However,
Chicago is compatible with existing Windows 3.1 programs, so there may be some
compromises that we have yet to hear about yet.

NT has no limits on resources, but runs all 16-bit Win3.1 applications within a
4Mb memory space, no matter how much memory your machine has (the rest of your
memory is for 32-bit applications, and there aren't many of these).

OS/2 lets you run each Windows application in its own machine, so each
application gets its own 64K GDI and 64K Heap that is not deducted by other
programs.  This will tend to use more memory overall, though.  OS/2 also
requires as powerful as machine as Windows NT.

Chicago is designed to be lean and mean, and run well on 8Mb 386/486 machines.

There is 1 Reply.

#: 40701 S4/Stacker 3.1
    29-Nov-93  07:51:29
Sb: #40605-#Is WFWG 3.11 compatible?
Fm: Michael Chan 100033,3524
To: Charles Brannon 70720,462 (X)

Sometimes, Charles, I think its Microsoft's application developers who are more
to blame for the resources drying up (despite Windows reporting more than
enough resources).

Take an example...Ami Professional 3.0 for Windows runs fine with no problems
in a similar environment where Word for Windows 2.0b would fall over and start
complaining about resource problems.

The way I look at it is, since Word for Windows 2.0b is a 16 bit app that runs
like a dog in NT but doesn't run very well in Windows 3.x, it does say a lot
about Microsoft internal developers.

Microsoft needs to tighten control over their application developers/designers
so that they start to produce decent code to run in the aforementioned limits
of the Intel 286 memory model. Not all of us can afford 486DX2/Pentium or DEC
Alpha boxes. I say this running OS/2 2.1 happily on a 486DX-33.



Mike.

There is 1 Reply.

#: 40798 S4/Stacker 3.1
    30-Nov-93  00:08:32
Sb: #40701-Is WFWG 3.11 compatible?
Fm: Charles Brannon 70720,462
To: Michael Chan 100033,3524 (X)

While Microsoft tries to design for a range of computers from low end 386s to
Dual Pentiums, it can't afford to focus on the least common denominator.
Especially since during the life of the operating system, hardware will advance
apace.  There is no reason to support 286s with Windows 4.0, but Windows 3.1
will still be available as a viable platform for those machines for a little
while longer.  The truth is that those who won't upgrade to new hardware at
least once in a while won't be buying new OS's or new versions of 32-bit
software anyway.

Notice how the 8/16 bit DOS software market has almost completely dried up,
despite the huge installed base of 8088/80286 machines still chugging away with
green screens glaring, across corporate America.  They have the software they
need already, and until it runs out of steam, won't be joining the rest of us
soon.  Wordperfect 5.1 in DOS with a NLQ dot matrix is all the word processor
most businesses will need for some time to come.

Windows can sneak into such an office with WFWG 3.11, since the Workgroup
Connection in DOS can now share local printers and drives on DOS-only machines.
Networking is one thing these offices still need by and large, and don't want
to pay for Netware. Bit by bit, terminals will be reconverted into personal
computers again, as icon envy takes hold.

#: 40944 S4/Stacker 3.1
    30-Nov-93  20:44:31
Sb: #WFW 3.11 32 Bit File Acc
Fm: Chip May 70712,314
To: MIKE 72170,1112

Mike,

Running a stand-alone with Stac3.1, 540M HD with 2-256M Stacker volumes, and a
200M HD slave with a 180M Stacker vol. Just upgraded from Win3.1 to WFWG3.11
last night - to get vshare.386 & some of the other upgrade features.  Am
running DOS6.2.

So far 32-Bit File access is working just fine across all 3 Stacker volumes.
Really noticeable difference in speed.

Be sure the DOS driver IF??.sys is loaded at boot-up - and apparently you MUST
have DOS6.2 from what the WFWG forum says (upgrade available on CIS from 6.0).

Chip

There is 1 Reply.

#: 40960 S4/Stacker 3.1
    30-Nov-93  23:37:48
Sb: #40944-#WFW 3.11 32 Bit File Acc
Fm: Laurence M. Johansen 71260,3377
To: Chip May 70712,314 (X)

From MS WFW 3.11 brochure that comes with the package titled "Most Common
Questions about....":

"Q:  What is 32-Bit Fill Access and how can I get it running on my computer?"

"A:  32-Bit File Access provides a faster way to read and write to the disk
cache in Windows for Worgoups 3.11 than SMARTDrive can provide.  It provides a
much higher disk access performance boost on compatible hard drive controllers
when running  WFW 3.11 by utilizing a 32-bit cache as opposed to SMARTDrive's
16-bit cache.  However, SMARTDrive is still used for caching floppy disk drives
with WFW 3.11...."

Could it be that the problem really lies in the "compatible hard drive
controllers", and that maybe many of the existing controllers are not
compatible??

Regards,  --Larry



There is 1 Reply.

#: 41200 S4/Stacker 3.1
    03-Dec-93  00:15:19
Sb: #40960-#WFW 3.11 32 Bit File Acc
Fm: Chip May 70712,314
To: Laurence M. Johansen 71260,3377 (X)

Guess that I must be one of the lucky ones, since all my drives - physical and
virtual (Stacker), read 32-bit file acces is enabled.

Funny, but the same "compatible controller" jargon was used to describe 32 bit
DISK access since WIN3.1 came out.  You would think that if your controller was
"disk" access compatible, it should also be "file" access compatible. Then
again, my controller is built onto the LB of my Micronics VLB motherboard,
which is supposed to provide a 32 bit path to the drives (versus an ISA
controller card which has to reside on a 16-bit bus).

Chip


There is 1 Reply.

#: 41348 S4/Stacker 3.1
    05-Dec-93  19:28:31
Sb: #41200-WFW 3.11 32 Bit File Acc
Fm: Laurence M. Johansen 71260,3377
To: Chip May 70712,314

I wonder if the "compatable controller" relates to the drive hardware itself,
particularly with IDE drives?  I also note that WFW 3.11 32 Bit File Access is
compatible with DOS 6.2 Doublespace, but not with DOS 6.0 Doublespace.  Maybe
this is part of the key???  Who knows.

Regards,  --Larry


#: 40503 S4/Stacker 3.1
    24-Nov-93  18:39:01
Sb: Stacker and VMS
Fm: Edward Nutter [Stac] 75330,2222
To: Michael R. Pekarik 72677,3654 (X)

OOPS!!

That should have been... speak to Alex Gillette or Bruce Behymer.

Edward Nutter
Stac Electronics Product Support 

#: 40535 S4/Stacker 3.1
    25-Nov-93  01:24:36
Sb: #STACHIGH.SYS Problem
Fm: Phil Fenley 75030,3167
To: Edward Nutter [Stac] 75330,2222 (X)

Thanks for the input....I finally found what happened...When stacking a new
drive my stac.ini file was changed and the drive letters were reversed.  Simple
problem, I and your support staff on the phone looked right at it without ever
seeing it.  Thanks to everyone for the quick response....It doesn't get much
better! 

There is 1 Reply.

#: 40555 S4/Stacker 3.1
    25-Nov-93  14:16:22
Sb: #40535-#STACHIGH.SYS Problem
Fm: Gary Pickavet 75410,122
To: Phil Fenley 75030,3167 (X)

Phil,

You had the SAME problem I did.  I just added another stacked drive to my
computer.  I had a stacker volume C: and D: was the uncompressed volume.  I
wanted to turn some uncompressed space on drive D: into another stacker
volume.  I did so.  BUT then, I had a heck of a time getting the drives in
the order I wanted them.  I wanted them like this:

c:  400M stacker volume
D:  150M Stacker Volume (the new one I just created.)
E:  300M Uncompress volume which has the data for C; & D:.


I finally played with the Stacker.INI file (the SW and NS parameters until I
was able to get what I needed.  Unfortunately, the only way to get the
drives to swap the way I wanted was to reverse the order of the Disk Volume
ID's in my Stacker.INI file.  Do now, I list the D: volume (150M) first,
then the C: volume (400M).  After I reversed these 2 lines, everything
worked just the way I wanted.  C: was the 400M, D: was the 150M and E: was
the uncompressed disk.  Unfortunately, now WHENEVER I runt he STACHIGH.SYS
command in my CONFIG.SYS file, my system hangs.

Did I gather you figured out how to fix this problem?

Thanks!

Gary

There is 1 Reply.

#: 40616 S4/Stacker 3.1
    27-Nov-93  03:21:35
Sb: #40555-#STACHIGH.SYS Problem
Fm: Edward Nutter [Stac] 75330,2222
To: Gary Pickavet 75410,122 (X)

Gary,

From the sound of what you're after, I suggest...

C:\STACVOL.000,NS
C:\STACVOL.DSK,NS
/SW CE

...in addition to the existing configuration switches.

I'd have to see your existing STACKER.INI and CONFIG.SYS to get a clue as to
why STACHIGH hangs.  Is there any message?

Ed Nutter
Stac Product Support

There is 1 Reply.

#: 40633 S4/Stacker 3.1
    27-Nov-93  14:25:52
Sb: #40616-#STACHIGH.SYS Problem
Fm: Gary Pickavet 75410,122
To: Edward Nutter [Stac] 75330,2222 (X)

Edward,

To answer your question, there is NO message when STACHIGH hangs the system (if
I don't use the memory manager.)

Gary


There is 1 Reply.

#: 40681 S4/Stacker 3.1
    28-Nov-93  15:20:20
Sb: #40633-#STACHIGH.SYS Problem
Fm: Glen C. Bodie 71371,1637
To: Gary Pickavet 75410,122 (X)

Count me in on this bug too.  At present I am running with the STACHIGH.SYS
line commented out of my CONFIG.SYS just so I can boot!  After installing 3.1 I
have never managed to get the system past this line without it hanging.  There
is no message, the system just freezes.

I run DOS 6.0, Stacker 3.1, RAMDRIVE, SMARTDRV, EMM386 and HIMEM on a 486DX/50
with 2 physical hard disks.  I had a little trouble getting the STAC.INI to
setup the right drive with the right letters (really poor instructions!) but at
least that is running OK now.

I'm suspecting it is some kind of a high memory overlay, but really dont feel
like going through all of the pain of trying everything one at a time to figure
out what.  I'm kind of hoping you've already done that and have an answer for
me!

There are 2 Replies.

#: 40691 S4/Stacker 3.1
    28-Nov-93  22:31:48
Sb: #40681-STACHIGH.SYS Problem
Fm: Gary Pickavet 75410,122
To: Glen C. Bodie 71371,1637

Glen,

Unfortunately, I currently had to do the same thing you have done.... comment
out STACHIGH.SYS to get my computer just to boot!!!  I hope Stac will provide
an answer.  I'm not sure exactly what STACHIGH even does BUT I know I don't
have as much free memory when I DON'T run it so it must have something to do
with memory management.

What is maddening to me is that everything worked fine for a week and then on
one reboot, BOOM, STACHIGH no longer loads, it locks up the system.

If Stac lets me know, we'll both know.  I've been a Stacker user for a LONG
time, but this is frustrating and now there are other choices out there. I'll
give them first shot at answering this question.

Gary


#: 40718 S4/Stacker 3.1
    29-Nov-93  17:07:17
Sb: #40681-STACHIGH.SYS Problem
Fm: Edward Nutter [Stac] 75330,2222
To: Glen C. Bodie 71371,1637

Glen,

Everyone's configuration is different.  If you'll run the command...
SYSINFO /S /H
... from your Stacker directory, you'll generate a file named SYSINFO.TXT.
Include that file into your reply to this message.  We should be able to figure
out how you should modify your configuration.

Edward Nutter
Stac Electronics Product Support 

#: 40687 S4/Stacker 3.1
    28-Nov-93  18:24:12
Sb: #Interlnk and Stacker
Fm: Barry Axelrood 76350,3650
To: Stac Electronics 75300,2755 (X)

I ran Interlnk without Share.  I got corrupted data.  I have been posting
messages on Exec-PC BBS as well, and got a response that Interlnk had problems
with Stacker 2.1 on the machine that was running Intersvr.  When Interlnk got
the wrong amount of free space, it would give the "Error reading drive
[drive:]" message.  When I removed Share, I got corrupted data in two files and
several lost chains.

I was also told that DoubleSpace does not have this problem.  I really don't
want to give up a product like Stacker that has been very stable for me.  Could
you tell me what the differences are between MS DOS 6.2 Doublespc and Stacker
3.1?

I am also thinking of installing Windows For Workgroups on my machines to do
the data transfer for the backup.  Are there any problems that I should know
about this combination?

There is 1 Reply.

#: 40904 S4/Stacker 3.1
    30-Nov-93  18:49:23
Sb: #40687-#Interlnk and Stacker
Fm: Stac Electronics 75300,2755
To: Barry Axelrood 76350,3650 (X)

Barry,

Not familair with any problems with Stacker 2.1 and interlink.  However, you
are running Stacker 3.1 and this would not be an issue.

Have you tries it without Setver laoded ?  Or with just Stacker and Interlink
active ?

See STAC31.ADV in lib:2 for a comparison between DOS 6 and Stacker 3.1

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41343 S4/Stacker 3.1
    05-Dec-93  18:02:22
Sb: #40904-Interlnk and Stacker
Fm: Barry Axelrood 76350,3650
To: Stac Electronics 75300,2755 (X)

I booted my notebook with only the drivers for QEMM and Stacker.  Then ran
intersvr.  I booted my desktop with the drivers for QEMM, Stacker and Interlnk.
I did not use setver.

Everything appear to work properly when I ran Norton Backup for Windows. When I
rebooted the machines, I got allocation size errors, cross linked files and
lost sectors on the D drive of both machines.

No more experimentation!!!!!!!!!!!!!!!!!!

I have asked MS how interlnk works to determine what could be causing the
corruption of the directories (at least that is what I think is happening).

!^NavFont01F0007RGHHHD98972

#: 40601 S4/Stacker 3.1
    27-Nov-93  00:01:27
Sb: #MS DOS 6.2 UPGRADE..OOPS
Fm: Diane Jernigan[Dvorak] 72662,737
To: Stac Electronics 75300,2755 (X)

Keith:

 > DOS 6.2 may/maynot correctly identify the Stacker drive,  If not, run
 > STAC62.EXE [contained in 62stac.exe] and install DOS 6.2 Thats it.
 > All other functions of DOS 6.2 work fine with Stacker.

Uhmm, just to clarify...we've got 6.2 installed, are having problems <bizarre
ones> and we are wondering if we can use that patch, 62stac.exe, to bail
ourselves out of the problems?  Given that 6.2 is already installed and due to
not being allowed to create an uninstall disk we're stuck with 6.2 and trying
to figure out if we're going to have to re-do a slew of drives.

Do I read you right in that you're saying to just go ahead run the patch and
then upgrade to 6.2 again?  Or?



 Diane Jernigan 72662,737
 Dvorak Development, Technical Support
 26-Nov-1993 23:10:11
 Windows NavCIS PRO 1.02C

There is 1 Reply.

#: 40870 S4/Stacker 3.1
    30-Nov-93  18:47:22
Sb: #40601-MS DOS 6.2 UPGRADE..OOPS
Fm: Stac Electronics 75300,2755
To: Diane Jernigan[Dvorak] 72662,737

Dianne,

If DOS 6.2 is installed you dont need the STAC62 utility.  Your problem would
be caused from something else.

Whta types of problems are you having ?

To remove DOS 6.2 just follow the setps in tech note 3302.txt in lib:3 It
refers to DOS 6.0 but is applicable for DOS 6.2

Keith Dunlea, Stac Tech Support

#: 40487 S4/Stacker 3.1
    24-Nov-93  17:56:47
Sb: SDEFRAG Error #120
Fm: Stac Electronics 75300,2755
To: Tom Gutman 70444,205 (X)

Tom,

The updated sdefrag is for Stacker 3.0.  Since you have Stacker 3.1 this is not
needed.  We have updated files for a compressed hardcard that is time stamped
3.11, but nothing was chnaged in regards to sdefrag.

Keith Dunlea, Stac Tech Support

#: 40488 S4/Stacker 3.1
    24-Nov-93  17:56:49
Sb: Upgrade to 6.2, TI EnhDo
Fm: Stac Electronics 75300,2755
To: David Arnold 72137,355 (X)

David,

Stacker should work fine with this versions.  No issues with batterypro either

Keith Dunlea, Stac Tech Support

#: 40524 S4/Stacker 3.1
    24-Nov-93  22:05:52
Sb: HARDCARD EX 240 meg
Fm: ALAN ROSS 70373,630
To: Edward Nutter [Stac] 75330,2222 (X)

BINGO!

Thankyou

Alan Ross


#: 40533 S4/Stacker 3.1
    25-Nov-93  00:36:39
Sb: Support For Large Drives
Fm: Richard Henry 76106,3376
To: Stac Electronics 75300,2755 (X)

Thanks,

Rich

#: 40811 S4/Stacker 3.1
    30-Nov-93  06:18:31
Sb: #PCDOS6.1 SuperStor/DS
Fm: Gary Greenberg 72616,10
To: Robert G. Gourley 70233,2300 (X)

You:
    I am using Stacker 3.1 with PC DOS 6.1, and the preload driver.  I
    used sstor to initialize my intention to compress my drive, then
    renamed sstor.exe to dblspace.exe after the reboot - then I installed
    Stacker.

Me:
    I bought PC-DOS 6.1 and found that it needed to load Stacker
    within the CONFIG.SYS (and _NOT_ with a pre-load driver).  I
    therefore returned to MS-DOS 6.0 and later to 6.2.... but would
    like to be running PC-DOS.

    How did you get a preload driver to happen in PC-DOS 6.1?  As far
    as I can tell, PC-DOS doesn't support the "hooks" for pre-boot
    disk compression (originally setup as DoubleSpace, now Stacker
    for us here).  My information has not previously been
    contradicted (reading the IBM BBS is a local for me, & I also
    logon to the CIS MS-DOS and Stacker fora)

Thanks, Gary Greenberg, writing 30-Nov-93 at 5:31a EDT

There is 1 Reply.

#: 40819 S4/Stacker 3.1
    30-Nov-93  10:33:08
Sb: #40811-PCDOS6.1 SuperStor/DS
Fm: Robert G. Gourley 70233,2300
To: Gary Greenberg 72616,10 (X)

Gary,

 >> How did you get a preload driver to happen in PC-DOS 6.1?

First you must have the latest version of PC DOS 6.1 - file dates 30Sep93. Then
once you have installed it you must run sstor.exe - the exact steps after this
might be different for you since I tried to get SuperStor/DS to work for me
before I gave up and ordered another copy of Stacker 3.1.

My best guess is that once you initialize disk compression using sstor.exe,
which will have you reboot before restarting the program to actually do the
compression, you rename the file after the reboot to dblspace.exe and install
Stacker 3.1.  It's been awhile since I did this, but if memory serves those are
the steps.

The only "problem" I've had is with 386MAX v7 - I cannot load all the files in
my config.sys from my compressed drive.  It's a small problem, and I haven't
thoroughly explored all the suggestions given me by Qualitas yet.  I'm trying a
beta version of the 386load files.

Hope this helps, Robert

#: 40489 S4/Stacker 3.1
    24-Nov-93  17:56:52
Sb: #PCDOS6.1 SuperStor/DS
Fm: Stac Electronics 75300,2755
To: Lee Jackson 76040,2743 (X)

Lee,

I would imagine the lab has already tested Stacker with PC DOS 6.1 And our tech
writers are working on a document which should be available real soon.  It will
cover PC DOS 6.1

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40512 S4/Stacker 3.1
    24-Nov-93  20:08:03
Sb: #40489-#PCDOS6.1 SuperStor/DS
Fm: Robert G. Gourley 70233,2300
To: Stac Electronics 75300,2755 (X)

 >> I would imagine the lab has already tested Stacker with PC DOS 6.1 And
 >> our tech writers are working on a document which should be available real
 >> soon.  It will cover PC DOS 6.1

Is this likely to be an electronic doc ?

There is 1 Reply.

#: 40743 S4/Stacker 3.1
    29-Nov-93  20:00:20
Sb: #40512-PCDOS6.1 SuperStor/DS
Fm: Stac Electronics 75300,2755
To: Robert G. Gourley 70233,2300 (X)

Robert,

Yes, and it will be posted in lib:4

Keith Dunlea, Stac Tech Support

#: 40604 S4/Stacker 3.1
    27-Nov-93  00:48:39
Sb: #VFAT!!!!
Fm: Charles Brannon 70720,462
To: David L. Dows 70373,1233 (X)

I am not making the claim that a network-less WFWG 3.11 will be sold as 3.2.
But I have seen this mentioned by various sources.  Wait and see for yourself.
In any case, there is no question that WFWG 3.11 IS "Windows 3.2," in that it
REPLACES Windows 3.1 and WFWG 3.11 no matter what is is called.  I really don't
think Microsoft marketing has finalized the version number of the networkless
version, if they do decide to sell it without network drivers, but I did not
make this up, out of the blue.  I have read in two other messages, that
Microsoft is no longer selling "original" Windows 3.1 to many of its usual
customers.  What do you think that means?

It's time to get excited by WFWG 3.11.  No longer a lackluster performer, it
will get a big boost as every Windows 3.1 users wants to upgrade to the latest
version of Windows.  It will be _perceived_ as Windows 3.2, and there will be
tremendous pressure for Stacker to hurry up and support full speed file
support, just as happened when Microsoft when from DOS 5.0 to DOS 6.0. DOS 6.0
could arguably be called DOS 5.1, but so what?  Everybody knows that Windows
3.1 was really a 4.0 by normal standards. It's what is perceived by the
marketplace that matters.  I sometimes think we should stop using version
numbers as a method of marketing.  It's ridiculous when Microsoft jumps Word
from 2.0 to 6.0 in a bound, even if they can partly justify this due to code
sharing with the DOS version that went from 5.0 to 6.0 recently.

(Meanwhile, do you want to qualify your assertion?  Are you privy to Microsoft
marketing plans?  Forgive me if I don't know who you are.)

Besides, one message, by one Compuserve user (me), is not going to "cloud the
issue."  I give other readers credit to know to verify information for
themselves.

There is 1 Reply.

#: 40636 S4/Stacker 3.1
    27-Nov-93  16:59:51
Sb: #40604-#VFAT!!!!
Fm: David L. Dows 70373,1233
To: Charles Brannon 70720,462 (X)

"I really don't think Microsoft marketing has finalized the version
number of the networkless version, if they do decide to sell it without
network drivers, but I did not make this up, out of the blue."

If you paid attention to the trade press & Microsoft announcements as I do,
you would know there is no need to offer 3.11 without the network capability
since there is an option during the install procedure to disable it.  The whole

idea is to sell it as is for both networked & standalone systems.

"Microsoft is no longer selling "original" Windows 3.1"

Microsoft has convinced many OEMs to offer WFWG 3.11 as the installed version.

It is in Microsoft's best interest to get the network version into as many
hands as
possible in their competition with Netware.  It is well known that the next
version
of Windows (4.0 or Chicago) is expected to include network capability.
There will NOT be another version without it.

There is 1 Reply.

#: 40797 S4/Stacker 3.1
    30-Nov-93  00:08:28
Sb: #40636-VFAT!!!!
Fm: Charles Brannon 70720,462
To: David L. Dows 70373,1233 (X)

Thank you for helping me clarify these issues.  It is difficult to separate
speculation from rumors from an inside scoop.  Strategically, I have always
believed that selling WFWG as Windows with free built-in networking was the way
to go.  There won't be a "Chicago for Workgroups," so why does Microsoft still
need to use a terminology that has completely flopped in the marketplace?  Just
call the new version Windows 3.11 and let it be so.  The fact that this hasn't
happened begs to ask: what will the product be called that is the midrange
upgrade from straight Windows 3.1?  Even if WFWG can be installed standalone
(and I've known this for some time), the public will be reluctant to buy what
they may perceive is a specialized version of Windows.

I appreciate your taking the time to chat with me about this.

#: 40537 S4/Stacker 3.1
    25-Nov-93  02:10:27
Sb: #STACKER 3.1/PARADOX4.0
Fm: Cornelius J. Hallahan 71510,2627
To: Stac Electronics 75300,2755 (X)

Keith,

Thanks for the quick reply. I did try booting with just STACKER loaded; no
problem w/PARADOX there. In the meantime I messaged Qualitas and have since
tried their suggestions with no luck.

Here is my config.sys: Device=c:\386max\386max.sys Pro=c:\386max\386max.pro
Device=c:\386max\386load.sys Size=11504 Prog=c:\dos\setver.exe
Device=c:\386max\386load.sys Size=18976 Prog=c:\ppr\ppr.sys ;Mouse program

Break=on Buffers=30 Files=40 Lastdrive=e Shell=c:\dos\command.com c:\dos\ /e256
/p Dos=high Device=c:\386max\386load.sys size=58848
Prog=c:\STACKER\STACHIGH.SYS Stacks=0,0 REM MAXIMIZE: ExtraDos must come at end
of config.sys Device=c:\386max\ExtraDos.max Pro=c:\386max\ExtraDos.pro
Install=c:\386max\ExtraDos.max

Thanks,

Con Hallahan


There is 1 Reply.

#: 41036 S4/Stacker 3.1
    01-Dec-93  18:17:44
Sb: #40537-#STACKER 3.1/PARADOX4.0
Fm: Stac Electronics 75300,2755
To: Cornelius J. Hallahan 71510,2627 (X)

Cornelius,

Ok, thanks for the information.  We also need your Stacker.ini file from the
host boot drive

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41098 S4/Stacker 3.1
    02-Dec-93  01:42:28
Sb: #41036-#STACKER 3.1/PARADOX4.0
Fm: Cornelius J. Hallahan 71510,2627
To: Stac Electronics 75300,2755 (X)

Keith,

Here's my Stacker.ini:

/DIR=C:\STACKER\ C:\STACVOL.DSK,SW

I've also tried some suggestions from Qualitas tech. support, but keep getting
the same result.

Thanks,

Con Hallahan


There is 1 Reply.

#: 41166 S4/Stacker 3.1
    02-Dec-93  18:59:53
Sb: #41098-STACKER 3.1/PARADOX4.0
Fm: Stac Electronics 75300,2755
To: Cornelius J. Hallahan 71510,2627 (X)

Cornelius,

Ok, Stacker is not using /EMS  so there would be no conflict with Stacker.  In
some cases with /EMS active [using EMS pageframe] some apps may not be happy.
You should try disabling Paradox's use of EMS to see if that helps

Keith Dunlea, Stac Tech Support

#: 40603 S4/Stacker 3.1
    27-Nov-93  00:48:35
Sb: Is WFWG 3.11 compatible?
Fm: Charles Brannon 70720,462
To: David L. Dows 70373,1233 (X)

Well, gee, Dave, I'm glad you cleared that up for me.  Without access to my
prior messages, I can't be sure what we were talking about before, and besides,
I hate to quibble.

I do realize that 150% faster is 2.5 times faster, but that 150% as fast is the
same as 1.5 times faster, which is the same as 50% faster.  (Of course 50% as
fast would be half as fast).  I think all these %%%%%%% need to get chucked!

Anyway, faster is better, so I of course I ordered WFWG 3.11.  Naturally, I
always like to get the latest version of anything, but watch out--it's not
always a good idea.  Norton Desktop for 3.0 has a few nice improvements, but in
some ways it is inferior to 2.2.  The user interface is more intuitive in some
respects, but much less so in others.  There are no major changes in
functionality, but a lot more window dressing.  It's an obvious attempt to
respond to PC Tools for Windows.

It is starting to grow on me, though.

#: 40490 S4/Stacker 3.1
    24-Nov-93  17:56:55
Sb: #Disk repair utilities ?
Fm: Stac Electronics 75300,2755
To: George Crickard 71051,1325 (X)

Geroge,

Both Norton 7 and PC Tools 9 are Stacker aware.  Either ones on these would be
fine.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40818 S4/Stacker 3.1
    30-Nov-93  10:08:30
Sb: #40490-Disk repair utilities ?
Fm: George Crickard 71051,1325
To: Stac Electronics 75300,2755 (X)

Keith,

Since I have like the way Norton works somewhat better, I will stick with it.

  Thanks,

  George - Columbus, OH - 30-Nov-93 at 09:59:09 EST

#: 40491 S4/Stacker 3.1
    24-Nov-93  17:56:59
Sb: HARDCARD AND STACKER 3.1
Fm: Stac Electronics 75300,2755
To: Howard Schwartz 76702,257 (X)

Howard,

The issure may be in load order of the hard card under DOS 6.2 Make sure its
the first driver after your memory manager.  If you have questions on this post
your config.sys file

Keith Dunlea, Stac Tech Support

#: 40492 S4/Stacker 3.1
    24-Nov-93  17:57:02
Sb: #STEPUP 6.2 fails...
Fm: Stac Electronics 75300,2755
To: Rich Grossman [Tech III] 75300,1556 (X)

Rich,

You may need to 62STAC.EXE utility posted in lib:1  This self extracting file
contains a utility to help you install DOS 6.2

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40591 S4/Stacker 3.1
    26-Nov-93  18:40:53
Sb: #40492-#STEPUP 6.2 fails...
Fm: Anthony A. Lattanzio 70642,1670
To: Stac Electronics 75300,2755 (X)

I think I understand this Stacker 3.1 and MS DOS 6.2 Stepup problem.

I have a computer with all drives stacker including the boot drive. The host
for the boot drive has 1 MB of free space.

When MSDOS 6.2 Stepup looks to update the system it uses the host drive
(uncompressed) to update DOS....but it needs 4.2 MB of free space (only 1 MB is
available). So no matter how much space is on the C: drive (compressed drive)
MS DOS 6.2 does not install properly due to lack of space.

C:\DOS (compressed) is where I want it installed...

D:\DOS (uncompressed) is were it tries to install it..but only 1 MB free space
is available.

The STAC62.EXE utility may tell MS DOS 6.2 were the right C:\DOS directory
is..but this still doesnot work?

Any ideas??? I am sure this is a MSDOS 6.2 bug..ARGH!!! Sue the pants off of
them...

Cheers Tony L.

There is 1 Reply.

#: 40865 S4/Stacker 3.1
    30-Nov-93  18:47:06
Sb: #40591-#STEPUP 6.2 fails...
Fm: Stac Electronics 75300,2755
To: Anthony A. Lattanzio 70642,1670 (X)

Anothony,

MS DOS 6.2 is not correctly identifying the Stacker drive.  STAC62.EXE should
correct this during the install.   Make sure after you run STAC62 start the DOS
6.2 update.   If this doesn't help explain what happens. Any error messages ?

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41099 S4/Stacker 3.1
    02-Dec-93  02:24:58
Sb: #40865-#STEPUP 6.2 fails...
Fm: Anthony A. Lattanzio 70642,1670
To: Stac Electronics 75300,2755 (X)

<<MS DOS 6.2 is not correctly identifying the Stacker drive.  STAC62.EXE should
correct this during the install.   Make sure after you run STAC62 start the DOS
6.2 update.   If this doesn't help explain what happens. Any error messages ?>>

Does not work...no error messages..

MSDOS6.2 still wants 4.2 MB free disk space....will not even just copy files to
hard disk..MS did a horrible job with the Setup install program....

Cheers Tony L.

There is 1 Reply.

#: 41167 S4/Stacker 3.1
    02-Dec-93  18:59:57
Sb: #41099-#STEPUP 6.2 fails...
Fm: Stac Electronics 75300,2755
To: Anthony A. Lattanzio 70642,1670 (X)

Anthony,

After STAC62.EXE is run it should work.  Does DIR or CHECKs projetcted bytes
free  report atleast 4+m free bytes.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41203 S4/Stacker 3.1
    03-Dec-93  00:37:55
Sb: #41167-#STEPUP 6.2 fails...
Fm: David L. Foster 72672,1415
To: Stac Electronics 75300,2755 (X)

I am having the same problem too.  Like Anthony I have all drives stacked and
have a actual boot drive on F:.  I have tried enlarging the F: drive, but I
stilll get the "Not enought space DOS 6.2 needs 4.2meg of space".  I am using
the Stac62.exe and it still does the same thing.  Hope you can help, I am at my
witts end!

David

There is 1 Reply.

#: 41242 S4/Stacker 3.1
    03-Dec-93  13:42:11
Sb: #41203-#STEPUP 6.2 fails...
Fm: Stac Electronics 75300,2755
To: David L. Foster 72672,1415 (X)

David,

After you run STAC62.EXE and it report "you can now install DOS 6.2" what
happens next.  Do you run SETUP for DOS 6.2 ?  What drive does it report not
having enough free space ?  Type CHECK and look at projected bytes free. It
should be at least 4.2m or better

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41292 S4/Stacker 3.1
    04-Dec-93  00:06:59
Sb: #41242-STEPUP 6.2 fails...
Fm: David L. Foster 72672,1415
To: Stac Electronics 75300,2755 (X)

Last night after 1am I finally got it to take.  What I had to do was to
increase my F: drive space so that it would be over the 4.2meg min.  And at the
same time make my C: drive have over the 4.2meg min.  I don't know why, but it
didn't work until I increased the unstacked drives space and the stacked space.
Strange!
I am having trouble with the MSCDEX.EXE file for my CD-ROM that it came with,
but that is for MS to figure out.  Thanks for the reply.  I hope what I have
said here may help.  Thanks!

David

#: 40493 S4/Stacker 3.1
    24-Nov-93  17:57:05
Sb: #going to dos 6.2
Fm: Stac Electronics 75300,2755
To: Mitchell F. Brin, M.D. 76340,2711 (X)

Mitchell,

Yes, but if you may need 62STAC.EXE in lib:1 to assist you. This is a self
-extracting file with a utility called STAC62.EXE

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40526 S4/Stacker 3.1
    24-Nov-93  22:13:59
Sb: #40493-going to dos 6.2
Fm: Mitchell F. Brin, M.D. 76340,2711
To: Stac Electronics 75300,2755 (X)

Thanks.  I'll download it.

Mitchell


#: 40494 S4/Stacker 3.1
    24-Nov-93  17:57:07
Sb: # 3003.txt won't work
Fm: Stac Electronics 75300,2755
To: TOM LOFFMAN 70252,1536 (X)

Tom.

Try using Setup /F

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40525 S4/Stacker 3.1
    24-Nov-93  22:09:42
Sb: #40494- 3003.txt won't work
Fm: TOM LOFFMAN 70252,1536
To: Stac Electronics 75300,2755 (X)

Keith,

Doesn't work with SETUP /F. Works up to step 7. with SETUP /=F. Then asks me to
insert Stacker floppy. Won't let me proceed beyond. When asked for drive in
step 7 I tried all of the following C:\, C:\STACKER, C:\TEMP and tried leaving
it blank. It won't get beyond this step. Tom

#: 40495 S4/Stacker 3.1
    24-Nov-93  17:57:11
Sb: Stacker 3.1 & WfW 3.11
Fm: Stac Electronics 75300,2755
To: David L. Dows 70373,1233 (X)

David,

WFW 3.11 will work fine with Stacker.  However its the VFAT system that may
not.  This part of the new program is what we need to test.

Keith Dunlea, Stac Tech Support

#: 40496 S4/Stacker 3.1
    24-Nov-93  17:57:13
Sb:  3.1 and Windows
Fm: Stac Electronics 75300,2755
To: Tom Atkins 71161,3717 (X)

Tom,

No, Stacker 3.1 is for DOS and Windows.  To use Stacker under OS/2 you would
need Stacker for OS/2.

See lib:2 for product and upgrade information.

Keith Dunlea, Stac Tech Support

#: 40730 S4/Stacker 3.1
    29-Nov-93  19:59:15
Sb: Speedisk for Windows
Fm: Stac Electronics 75300,2755
To: Jeff Donels 75030,2622 (X)

Jeff,

We have no reports of Speedisk for Windows.  Is it available yet ? Do they
advertise as being Stacker aware ?

Keith Dunlea, Stac Tech Support

#: 40497 S4/Stacker 3.1
    24-Nov-93  17:57:17
Sb: #AT/16 working??
Fm: Stac Electronics 75300,2755
To: Bill Tsai 76666,223 (X)

Bill,

You need to remove the Stacker-tuner.  Edit the Stacker.ini file and remove
/P=#, then reboot.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41347 S4/Stacker 3.1
    05-Dec-93  19:22:08
Sb: #40497-AT/16 working??
Fm: Ronald  Lloyd 71754,1134
To: Stac Electronics 75300,2755 (X)

I'm running low on expansion slots on my 386/20Mz system.  I've been running
Stacker since rev 2.0, and I'm now at 3.10 ans wondering how much real benefit
I'm getting from the AT/16 card.  (None unless I make the change in the
previous note, I'll bet.)  If I take out the card what difference will it make?
I don't think that you even sell it any longer, do you?

#: 40735 S4/Stacker 3.1
    29-Nov-93  19:59:41
Sb: Dos 6.2 Upgrade w Stac
Fm: Stac Electronics 75300,2755
To: Frank 72240,3255

Frank,

Download 62STAC.EXE from lib:1   This self extracting file contains an utility
to help you upgrade from DOS 6.0 - 6.2 on a Stacker 3.1 drive.

Keith Dunlea, Stac Tech Support

#: 40463 S4/Stacker 3.1
    24-Nov-93  17:19:36
Sb: #DOS 6.2 step-up version
Fm: Mark Llewellyn 100025,2754
To: ALL

Can anyone help me ?

In order to upgrade to DOS 6.2 the forum file 31306.TXT (23Nov93) says I need
to run a program called 62STAC.EXE which is supposed to contain the files
before62.exe and after62.exe, but it actually contains only one executable file
STAC62.EXE (3Nov93) and I am now confused !

Which is the correct version, the 'before and after' version, or the 'all in
one' version ? If it is the 'before and after' version, where can I get it
since the downloadable version is the 'all in one' version (3Nov93) ?

I have a free step-up version of the MSDOS 6.2 system and need to know if the
program(s) mentioned above will work with the step-up version as well as with
the full 6.2 installation version, since no-one at the magazine that issued the
disk could tell me.

There are 2 Replies.

#: 40515 S4/Stacker 3.1
    24-Nov-93  21:10:35
Sb: #40463-DOS 6.2 step-up version
Fm: WG  NORMAN 72163,2245
To: Mark Llewellyn 100025,2754 (X)

I just loaded the DOS 6.2 on two Staced drives (about 2 weeks ago) without
doing anything other than the DOS install and everything works fine...

#: 40738 S4/Stacker 3.1
    29-Nov-93  19:59:54
Sb: #40463-#DOS 6.2 step-up version
Fm: Stac Electronics 75300,2755
To: Mark Llewellyn 100025,2754 (X)

Mark,

62STAC.EXE have been updated to contain those files.  You can download this
file from lib:1

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41134 S4/Stacker 3.1
    02-Dec-93  17:43:26
Sb: #40738-DOS 6.2 step-up version
Fm: Mark Llewellyn 100025,2754
To: Stac Electronics 75300,2755 (X)

Keith,

Thanks very much, I only hope it doesn't object to my step-up version !

  - Mark [ 30-Nov-93 at 9:41p GMT ]

#: 40502 S4/Stacker 3.1
    24-Nov-93  18:37:25
Sb: #Increasing compr space
Fm: Larry D. Eggert 72037,3555
To: Stac Electronics 75300,2755 (X)

I recently stacked my 504 MB HD. When I did it, I had a Win permanent swap
file. I have installed more RAM, and would like to convert the permanent swap
file back to my C: drive. I have removed the swap file in Win, and now have no
"virtual memory". The hidden files are gone from \Windows and my uncompressed
drive. When I attempt to increase my compressed space and add the 16 MB that
was in my swap file, I am told that I am too near the disk capacity and the
utility won't let me. The compression factor is 2.2:1 and I currently measure
2.1:1. I am only using about 500 MB of my 1 gigabyte compressed drive. Is there
some trick I'm missing, or will that 16 MB always be lost on the uncompressed
drive, and never retrievable to the compressed drive?

I am using Stacker 3.1, MS-DOS 6.2 & WFW 3.1; my mem manager is QEMM7. If you
need more configuration info, please ask.

Thanks for your help.

There is 1 Reply.

#: 40741 S4/Stacker 3.1
    29-Nov-93  20:00:08
Sb: #40502-Increasing compr space
Fm: Stac Electronics 75300,2755
To: Larry D. Eggert 72037,3555

Larry,

Post your CHECK /D report for the drive and we can take a look. You may be near
the 512m limit where you need to change cluster sizes.

When compressing a drive greater than 256m you need to select 16k clusters in
advanced options.  Unstack the drive and rerun SETUP.

For drives greater than 512m select 32k clusters.

Keith Dunlea, Stac Tech Support

#: 40510 S4/Stacker 3.1
    24-Nov-93  19:56:44
Sb: #Help!
Fm: Keith Dees 73062,665
To: stac

I have a customer with a drive double spaced. This drive has crashed and will
not boot. will your product "resurect" this drive? As best I can tell the
container file is still intact,
Keith

There is 1 Reply.

#: 40619 S4/Stacker 3.1
    27-Nov-93  03:33:05
Sb: #40510-#Help!
Fm: Edward Nutter [Stac] 75330,2222
To: Keith Dees 73062,665 (X)

Keith,

Stacker can't resurrect that drive.  We could convert an intact DBLSPACE
container file on a working drive, but it seems that the drive isn't to where
you should try that yet.

Ed Nutter
Stac Product Support

There is 1 Reply.

#: 40674 S4/Stacker 3.1
    28-Nov-93  13:46:58
Sb: #40619-Help!
Fm: Keith Dees 73062,665
To: Edward Nutter [Stac] 75330,2222 (X)

Thanks Ed,
Live and learn...<G>
Keith

#: 40513 S4/Stacker 3.1
    24-Nov-93  20:24:57
Sb: #StackHIGH locks system
Fm: Gary Pickavet 75410,122
To: All

Hi,

I'm running Stacker 3.1 with DOS 6.2.  I also am running 386MAX version 7.
When I run STACHIGH, the machine locks up.  This didn't start happening
until I added a new stacked volume this afternoon.  To get the drive
assignments to switch around correctly, I had to play around a bit but I
thought I had everything correct.

Here is my Stacker.INI file


/DIR=C:\UTILITY\STACKER\
/P=1
c:\stacvol.000,NS
C:\STACVOL.DSK,SW

After this change, STACHIGH would load no more!!!

Any ideas?!

Gary

There is 1 Reply.

#: 40617 S4/Stacker 3.1
    27-Nov-93  03:26:57
Sb: #40513-#StackHIGH locks system
Fm: Edward Nutter [Stac] 75330,2222
To: Gary Pickavet 75410,122 (X)

Gary,

Adding a drive increases the size of the Stacker driver by about 3K, which
increases the amount of memory that STACHIGH wants from the memory manager.
Maximize has already decreed that STACHIGH will get the lesser space, so 386MAX
chokes.

Remove the memory management syntax from the STACHIGH.SYS line. Then rerun
Maximize to setup memory for the new Stacker driver size.

Ed Nutter
Stac Product Support

There is 1 Reply.

#: 40632 S4/Stacker 3.1
    27-Nov-93  14:25:49
Sb: #40617-#StackHIGH locks system
Fm: Gary Pickavet 75410,122
To: Edward Nutter [Stac] 75330,2222 (X)

Edward,

In another post, I indicated my config.sys and Stacker.ini files.  As I noted,
if I run STACHIGH without a memory manager altogether, STACHIGH just locks up
the system.  If I don't load the RAMDISK driver at all, STACHIGH loads just
fine.  Is that a clue?

Gary


There is 1 Reply.

#: 40719 S4/Stacker 3.1
    29-Nov-93  17:07:26
Sb: #40632-#StackHIGH locks system
Fm: Edward Nutter [Stac] 75330,2222
To: Gary Pickavet 75410,122 (X)

Gary,

I found your earlier post of your config files.  I'm sure you must have made
some changes in them, as what you wanted to do in that message wouldn't have
worked correctly with what you posted.

If you have NOT changed those files, then try deleting "F:\STACVOL.DSK,RP" from
your STACKER.INI file.  Leave config.sys and autoexec.bat as is.

Edward Nutter
Stac Electronics Product Support


There is 1 Reply.

#: 40783 S4/Stacker 3.1
    29-Nov-93  20:58:50
Sb: #40719-#StackHIGH locks system
Fm: Gary Pickavet 75410,122
To: Edward Nutter [Stac] 75330,2222 (X)

Edward,

You sent me a message that refers to an earlier post of my CONFIG files. you
suggest I delete a line "F:\STACVOL.DSK,RP" from my STACKER.INI file.  In my
latest post to you, I am not using that statement in my STACKER.INI file.

PLEASE look at message number 40631.  That message has my current CONFIG.SYS
and AUTOEXEC.BAT and STACKER.INI files.  Originally, I was having a problem
with getting my RAM disk to load and then to switch to be my "F:" drive. That
problem was fixed and resolved.  I think that is the STACKER.INI file you were
looking at.... the one I need help with a week and 1/2 ago.  Since then, and
after working flawlessly for a week, STACHIGH started locking up my system.
I've reinstalled the Stacker files with not relief.  Message number 40631 has
my current CONFIG.SYS,  etc. files in it.

Please let me know how to resolve this problem.

Gary

P.S.  not to take away from the StacHIGH locking my system problem, but I am
also curious, what exactly does STACHIGH do?


There is 1 Reply.

#: 40827 S4/Stacker 3.1
    30-Nov-93  13:17:13
Sb: #40783-#StackHIGH locks system
Fm: Edward Nutter [Stac] 75330,2222
To: Gary Pickavet 75410,122 (X)

Gary,

OK, I found your current config.  I suggest you modify your various sections of
config.sys as follows: <I'll leave out the load high stuff>

device=c:\utility\386.max\386max.sys pro=c:\utility\386max\386max.pro
device=c:\dos\setver.exe
device=c:\utility\stacker\stachigh.sys
device=c:\dos\ramdrive.sys 2048 /e
device=c:\utility\stacker\screate.sys f:
... etc.

Then modify STACKER.INI to read...
DIR=C:\UTILITY\STACKER\
/RP=2
/P=1
C:\STACVOL.DSK,SW
C:\STACVOL.000,NS

Finally, in autoexec.bat somewhere add the line...

c:\utility\stacker\stacker f:

Essentially, move STACHIGH.SYS above the RAM drive, which will (among other
things) lock in the hard drive letter assignments topping out at E:.  The RAM
drive then becomes F:, and SCREATE.SYS creates a STACVOL in it.  Finally, the
STACVOL is mounted in autoexec.bat.

Edward Nutter
Stac Electronics Product Support 

There is 1 Reply.

#: 40940 S4/Stacker 3.1
    30-Nov-93  20:26:27
Sb: #40827-#StackHIGH locks system
Fm: Gary Pickavet 75410,122
To: Edward Nutter [Stac] 75330,2222 (X)

Edward,

Stachigh.sys continues to lockup my system.  To facilitate things, I've pared
down my CONFIG.SYS files and eliminated any and all references to 386MAX.
There is absolutely no message from STACHIGH.SYS when it locks the system.  It
just crashes it.  When the computer boots up and processes the CONFIG.SYS file,
only 4 commands execute prior to the lockup.

DOS=HIGH HIMEM.SYS EMM386

Then, STACHIGH.SYS loads and locks up the system.  In fact, we purchased more
than one copy of Stacker 3.1 and STACHIGH.SYS is now locking up 2 of our
computers.  Both Gateway 486/66 machines with 16M of memory.

Here is my CONFIG.SYS file:


[menu] menuitem=Net, Start the network menuitem=No_Net, Do not start the
network menuitem=CD_ROM, Run CD Rom Programs menucolor=15,1 menudefault=Net, 10
[common]

Device=c:\dos\himem.sys device=c:\dos\emm386.exe ram rem
device=c:\utility\stacker\stachigh.sys

BUFFERS=10,0 FILES=80 FCBS=20,0 SHELL=C:\DOS\COMMAND.COM C:\DOS\ /E:900 /p
DOS=HIGH LASTDRIVE=Q REM device=d:\ramdrive.sys 1024 /a switches=/k [No_Net]
[Net] DEVICE=C:\DOS\SETVER.EXE DEVICE=C:\GRAPHICS\NEC\MVSOUND.SYS D:3 Q:7 T:1
DEVICE=C:\GRAPHICS\NEC\NECCDR.SYS /D:NECCD DEVICE=C:\GRAPHICS\NEC\SNDBK12.SYS 1
7 220 2 Stacks=0,0 [CD_ROM]

[common]

HERE IS MY STACKER.INI file:

/DIR=C:\UTILITY\STACKER\ /P=1 /SW DE c:\stacvol.dsk,SW c:\stacvol.000,NS


There is 1 Reply.

#: 40991 S4/Stacker 3.1
    01-Dec-93  14:16:39
Sb: #40940-StackHIGH locks system
Fm: Edward Nutter [Stac] 75330,2222
To: Gary Pickavet 75410,122 (X)

Gary,

This problem seems to be progressively getting worse.  I'd like to see the
SYSINFO /S /H for the other Gateway machine.  However, re. the one we've been
hacking on...

1. Get rid of the "/SW DE" in Stacker.ini as I requested in my last message.

2. Install a new copy of the Stacker driver itself.  To do this...
   a) Run the command STACKER and note the drive map.  You will see...
      Drive C: was drive C: at boot time.  [x:\STACVOL.DSK =nnn.nMB ]
   b) Insert the Stacker diskette #1 and log onto it.
   c) Enter \TOOLS\REDBL x:  <<"x:" is the letter in the drive map above>>

Reenable STACHIGH.SYS and see what happens when you reboot.  If it still hangs,
use F8 to get past STACHIGH.  Run SYSINFO /S /H, then post the SYSINFO.TXT
along with your message.

Edward Nutter
Stac Electronics Product Support 

#: 40514 S4/Stacker 3.1
    24-Nov-93  20:37:19
Sb: #No screen progress rep.
Fm: Mireille(Mimi)Petit/ORH 70713,235
To: all

I am currently installing Stacker on a new 486 Contura notebook.
 It has MS DOS 6 installed and Windows 3.1. Stacker is 3.1 for DOS/Windows (DOS
6).

Everything went fine. It told me to take out disk two...and then hit continue,
or enter or something like that. Then the screen went blank...but the hard
drive was chruning. I figured that it was compressing. But that stopped after
20 minutes. There is no on-screen progress report, as described in the manual.
I'm afraid to reboot, in case I corrupt something being compressed (though i
hear/see no activity). It's a 120 meg frive with maybe only 40 megs filled.

Should I reboot?

Mimi


There is 1 Reply.

#: 40744 S4/Stacker 3.1
    29-Nov-93  20:00:25
Sb: #40514-No screen progress rep.
Fm: Stac Electronics 75300,2755
To: Mireille(Mimi)Petit/ORH 70713,235

Mireille,

Sounds like you have a screen saver active ?

Either way hit return [enter key] to see if the screen comes back. If not,
restart the computer and check the STacker line at boot time for error message.
There is a very good chance Stacker installed OK and you will boot fine.

Keith Dunlea, Stac Tech Support

#: 40522 S4/Stacker 3.1
    24-Nov-93  21:40:55
Sb: #hardcard and host of c:
Fm: Roger S Ward 70253,2751
To: Stac Electronics 75300,2755 (X)

I have a long term problem with my hard card that is different from the write
protect error that had generated so many messages.  The hardcard is not
compressed and I do not wish to do so.  The card appears to be a immage of the
host of c: drive.  A dir of the hard card will give the same information as the
dir of the host of drive c:.  Later in this message I have appended the
sysinfo.txt and you can see that drive g is the same size as drive e.  They are
not the same size.  Furthermore the program msd.exe reports the same number of
heads, cylinders and tracks.  The problem was fixed with the stacker 3.11
upgrade disks, but returned when I upgraded to dos 6.2.
Please call me at (408)-289-3941 to discuss the problem.
************sysinfo.txt follows****************
========================================================================
=
SYSINFO.TXT - Version 3.10, Stac Technical Support Info Extractor
========================================================================
=

Wed Nov 24 17:58:49 1993

0-620310-40758-S000
Stacker Version Number: 3.10

========================================================================
=
SOFTWARE INFORMATION
========================================================================
=

-------------------------------------------------------------------------
***** DOS VERSION



MS-DOS Version 6.20

-------------------------------------------------------------------------
***** C:\CONFIG.SYS


DEVICE=C:\DOS\SETVER.EXE
[common]
REM BUFFERS=40,0
files=60
LASTDRIVE=T
FCBS=4,0
STACKS=18,256
BREAK=ON
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /E:2048 /p

DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS h=96 x=c800-cbff i=e000-efff
rem DEVICE=c:\ndw\NAV&.SYS /b
DEVICEHIGH /L:1,9072 =C:\DOS\ANSI.SYS /X
DEVICEhigh=C:\DOS\STACKER\STACHIGH.SYS
device=c:\dos\hardcard\atdosxl.sys
rem DEVICEHIGH=C:\DOS\ramdrive.sys 64 /e
DOS=HIGH,UMB





BUFFERS=10,0
-------------------------------------------------------------------------
***** C:\AUTOEXEC.BAT


@loadhigh C:\DOS\SHARE.EXE /l:500 /f:5100
@rem STARTING AUTOEXEC.BAT
@ECHO OFF
rem pause

REM SET COMSPEC=C:\DOS\COMMAND.COM
set SCOM=SA
set dircmd=/p /o:en
set temp=C:\temp
set tem=c:\temp
set DPIMEM=MAXMEM 4000
SET NU=D:\NU
SET SYMANTEC=C:\SYMANTEC
set mouse=C:\dos\ms-Mouse

VERIFY OFF

rem PATH d:\tc\bin;%path%
PATH d:\nu;C:\DOS\STACKER;C:\TEMP;%path%
PATH C:\XTG;%path%
PATH C:\winword;%path%
PATH C:\excel;%path%
PATH C:\windows;C:\ndw;%path%
PATH C:\;C:\dos;%path%

C:\DOS\STACKER\CHECK c: /f /b
C:\DOS\STACKER\CHECK d: /f /b
C:\ndw\image
C:\dos\setclock\pcclock.exe /A5
C:\DOS\debug.exe <C:\dos\fixcom.deb
C:\dos\ms-Mouse\mouse.exe
LH /L:0;1,42576 /S C:\DOS\SMARTDRV.EXE
LH /L:1,6400 C:\DOS\doskey /insert
lh C:\ndw\smartcan /on

rem C:\WINDOWS\AD_WRAP.COM
rem for win3.1 loadhigh C:\DOS\GRAPHICS GRAPHICS
rem for win3.1 loadhigh C:\dos\PRINT /D:LPT1

C:\DOS\SPIDER\SETMODE 3+ m3-
C:\DOS\mode con: cols=80 lines=50
VER
prompt Roger & Pam $P$G



-------------------------------------------------------------------------
***** E:\STACKER.INI


/Q-
/DIR=C:\DOS\STACKER\
/w-
/P=1
; /RP=2 ; # of drives to reserve
C:\STACVOL.DSK,SW
D:\STACVOL.000,SW
-------------------------------------------------------------------------
***** DOS PROGRAMS LOADED


PRINT.EXE loaded       :   NO
ASSIGN.COM/EXE loaded  :   NO
SHARE.EXE loaded       :  YES
NET REDIRECTOR loaded  :   NO
NLSFUNC loaded         :   NO
ANSI.SYS loaded        :  YES
DOSKEY.COM loaded      :  YES
GRAFTABL.COM loaded    :   NO
APPEND.EXE loaded      :   NO
IPX loaded             :   NO
KEYB.COM loaded        :   NO
-------------------------------------------------------------------------
***** Drivers as listed in CONFIG.SYS


Date == 0 indicates that the file was not found.
# indicates Host Mode.
@ indicates Replaceable drive.

----DATE---TIME----SIZE--FILENAME----------------------------------------
11-09-93  9:53a   12015  C:\DOS\SETVER.EXE
09-30-93  6:20a   54619  C:\DOS\COMMAND.COM
09-30-93  6:20a   29136  C:\DOS\HIMEM.SYS
09-30-93  6:20a  120926  C:\DOS\EMM386.EXE
09-30-93  6:20a    9065  C:\DOS\ANSI.SYS
09-08-93  3:11a   25484  C:\DOS\STACKER\STACHIGH.SYS
11-07-90 11:33a   22577  C:\DOS\HARDCARD\ATDOSXL.SYS

========================================================================
=
ERRORS FROM STACKER.LOG FILES
========================================================================
=

-------------------------------------------------------------------------
***** ERRORS FROM E:\STACKER.LOG


CREATE 3.00  Sun Jan 17 15:11:20 1993

Stack of Existing Drive
Filename:  C:\STACVOL.DSK

0 files were too large and were not copied (from E:\STACKER.LOG)
***** List of files with READ errors (from E:\STACKER.LOG)0 file(s) listed*****
List of HIDDEN
files not copied (from E:\STACKER.LOG)   C:\386SPART.PAR   C:\SD.INI
C:\IMAGE.IDX3
file(s)
listed-------------------------------------------------------------------------
***** ERRORS FROM F:\STACKER.LOG


CREATE 3.10  Sun Aug 01 12:50:36 1993

Stack of Empty Drive
Filename:  D:\STACVOL.000

0 files were too large and were not copied (from F:\STACKER.LOG)
***** List of files with READ errors (from F:\STACKER.LOG)0 file(s) listed*****
List of HIDDEN
files not copied (from F:\STACKER.LOG)0 file(s) listed
========================================================================
=
HARDWARE INFORMATION
========================================================================
=

Current CPU type       : 80486 or higher
Numeric coprocessor    : YES

Computer Model ID      : 0xFC
BIOS ROM Date          : 06/06/92

First Hard Drive Type  : 47
Second Hard Drive Type : 47

Net BIOS active        :  NO

Primary display        : VGA (PS/2 Color)
Secondary display      : NONE

Mouse installed        : YES
Installed mouse type   : Serial mouse
Mouse driver version   : 9.00
Mouse interrupt        : IRQ 4
-------------------------------------------------------------------------
***** MEMORY INFORMATION


Total DOS Memory       : 655360 bytes
Available DOS Memory   : 596848 bytes

Total Ext. Mem.        :  7340032 bytes
Available Ext. Mem.    :        0 bytes

XMS Driver Present     : YES
XMS Version Number     : 3.0
XMS Revision Number    : 3.10

XMS Total free         :  4870144 bytes
XMS Largest free       :  4870144 bytes
UMB Largest free       :        0 bytes

EMS Present            :  NO
-------------------------------------------------------------------------
***** ENVIRONMENT INFO


COMSPEC=C:\DOS\COMMAND.COM
SCOM=SA
DIRCMD=/p /o:en
TEMP=C:\temp
TEM=c:\temp
DPIMEM=MAXMEM 4000
NU=D:\NU
SYMANTEC=C:\SYMANTEC
MOUSE=C:\dos\ms-Mouse
PATH=C:\;C:\DOS;C:\WINDOWS;C:\NDW;C:\EXCEL;C:\WINWORD;C:\XTG;D:\NU;C:\DOS\STA
CKER;C:\TEMP;C:\DOS
PROMPT=Roger & Pam $P$G


     268 bytes of memory are currently used by the DOS environment.

-------------------------------------------------------------------------
***** PHYSICAL DRIVE INFORMATION


Drive Type      Local/LAN  Total (K)    Free (K)     S/C  Version  RWD
----- -------   ---------  -----------  -----------  ---  -------  ---
 A:   1.44MB    Local
 B:   1.44MB    Local
 C:   Fixed     Local        200425472     28041216   16     3.00  ___
 D:   Fixed     Local        147800064     25231360   16     3.00  ___
 E:   Fixed     Local        124389376      8636416
 F:   Fixed     Local         83683328      3678208
 G:   Fixed     Local        124389376      8636416
-------------------------------------------------------------------------
***** STACVOL FILE INFO


Drive C:
   None found!
Drive D:
   None found!
Drive E:
   STACVOL.DSK      114,461,696  Sys Hid R/O
Drive F:
   STACVOL.000       80,000,000  Sys Hid R/O
Drive G:
   STACVOL.DSK      114,461,696  Sys Hid R/O
-------------------------------------------------------------------------
***** STACKER COMMAND INFO


Stacker hardware information :  Software only
Stacker using EMS            :   NO
Stacker loaded high          :  YES
Available replaceable drives :  1
Number of unmounted drives   :  0 (excluding removable drives)
Number of replaced drives    :  0
Number of read-only drives   :  0
Number of damaged drives     :  0

Stacker drive map:
   Drive A: was drive A: at boot time
   Drive B: was drive B: at boot time
   Drive C: was drive C: at boot time  [ E:\STACVOL.DSK = 109.1MB  ]
   Drive D: was drive D: at boot time  [ F:\STACVOL.000 = 76.2MB  ]
   Drive E: was drive E: at boot time
   Drive F: was drive F: at boot time
   Drive G: was drive G: at boot time
========================================================================
=
WINDOWS INFORMATION
========================================================================
=

-------------------------------------------------------------------------
-------------------------------------------------------------------------
***** In C:\WINDOWS\ *****


Windows Version 3.10
-------------------------------------------------------------------------
***** WINDOWS PERMANENT SWAP FILE(S)



     0 permanent swap file(s) found.
-------------------------------------------------------------------------
***** C:\WINDOWS\WIN.INI

This information was edited out.  It is not important tothe problem
The problem occurs in dos before windows is loaded.
-------------------------------------------------------------------------
***** END OF STACKER INFO FILE ***

There is 1 Reply.

#: 40748 S4/Stacker 3.1
    29-Nov-93  20:00:53
Sb: #40522-#hardcard and host of c:
Fm: Stac Electronics 75300,2755
To: Roger S Ward 70253,2751 (X)

Roger,

Please give more details.   Is drive E:  swaped with C ?   Is drive G:  the
hardcard ?   Post your drive map, type STACKER plus the Total Bytes as reported
by CHKDSK for both E: and G:

If you prefer phone assistance please call Stac tech support.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40969 S4/Stacker 3.1
    01-Dec-93  01:09:43
Sb: #40748-hardcard and host of c:
Fm: Roger S Ward 70253,2751
To: Stac Electronics 75300,2755 (X)

You did not read all of the original message.  The majority of the measage is
the contents of the log file made by stacker program sysinfo.  See also message
40825  for the description of the solution to the problem.

#: 40539 S4/Stacker 3.1
    25-Nov-93  03:15:02
Sb: #Hardcard and Stacker 3.1
Fm: Howard Schwartz 76702,257
To: Stac Electronics, 75300,2755 (X)

Thanks for the suggestion of moving the hardcard driver (ATDOSXL.SYS) up in
Config.sys, following the memory manager. I tried this but it didn't do the
trick, so I've uploaded a copy of my config.sys, as you requested. I hope
you'll be able to pinpoint the problem. Thanks for your help.

DEVICE=C:\QEMM\DOSDATA.SYS DEVICE=C:\QEMM\QEMM386.SYS RAM R:3 DBF=2 ST:F
DEVICE=C:\QEMM\DOS-UP.SYS @C:\QEMM\DOS-UP.DAT DEVICE=C:\QEMM\LOADHI.SYS /R:1
/SIZE=8592 C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP SWAPSIZE=1024
DEVICE=C:\QEMM\LOADHI.SYS /R:3 /SIZE=22880 C:\ATDOSXL.SYS
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /E:398 /p STACKS=0,0 DOS=HIGH BUFFERS=20
FILES=35 LASTDRIVE=H DEVICE=C:\DOS\SETVER.EXE DEVICE=C:\QEMM\LOADHI.SYS /R:3
/SIZE=41200 C:\STACKER\STACHIGH.SYS DEVICE=C:\QEMM\LOADHI.SYS /R:3 /SIZE=9360
C:\DOS\ANSI.SYS SWITCHES=/F DEVICE=E:\DISKTECH\DT_GOLD.SYS
DEVICE=c:\bpcdrom\bpcddrv.sys /d:bpcddrv$

There is 1 Reply.

#: 40754 S4/Stacker 3.1
    29-Nov-93  20:01:30
Sb: #40539-#Hardcard and Stacker 3.1
Fm: Stac Electronics 75300,2755
To: Howard Schwartz 76702,257 (X)

Howard,

The HC drive needs to be after the Qemm driver.   For example

DEVICE=C:\QEMM\DOSDATA.SYS DEVICE=C:\QEMM\QEMM386.SYS RAM R:3 DBF=2 ST:F
>>>>DEVICE=C:\QEMM\LOADHI.SYS /R:3 /SIZE=22880 C:\ATDOSXL.SYS
DEVICE=C:\QEMM\DOS-UP.SYS @C:\QEMM\DOS-UP.DAT DEVICE=C:\QEMM\LOADHI.SYS /R:1
/SIZE=8592 C:\QEMM\QDPMI.SYS SWAPFILE=DPMI.SWP SWAPSIZE=1024
DEVICE=C:\QEMM\LOADHI.SYS /R:3 /SIZE=22880 C:\ATDOSXL.SYS


Let me know if this doesn't help/

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40784 S4/Stacker 3.1
    29-Nov-93  21:02:34
Sb: #40754-#Hardcard and Stacker 3.1
Fm: Howard Schwartz 76702,257
To: Stac Electronics 75300,2755 (X)

That did the trick. Thanks for your help. I'm very glad to have the hardcard
fixed.

There is 1 Reply.

#: 41014 S4/Stacker 3.1
    01-Dec-93  15:32:38
Sb: #40784-Hardcard and Stacker 3.1
Fm: Stac Electronics 75300,2755
To: Howard Schwartz 76702,257 (X)

Howard,

Thanks for the report back!

Keith Dunlea, Stac Tech Support

#: 40546 S4/Stacker 3.1
    25-Nov-93  09:41:01
Sb: #62STAC.EXE PROBLEMS
Fm: Ken Pfister 73522,2533
To: SYSOP (X)

I NEED SOME HELP....I just installed stac 3.1...that's ok...however when I
upgraded to dos 6.2, I got a message telling me that I could no longer access
my stacker drive..  That's ok because I have your stacker note 31306.txt about
using 62stac.exe.  Well I ran 62stac.exe and now unfortunately, only the
stac62.txt & stac62.exe files are available. Your document said that when
62stac.exe was run, BEFORE62.EXE AND AFTER62.EXE would be created.  So now I am
kind of stuck at this point.

Problem # 2 -

When I installed stac 3.1, I noticed now that I can print absolutely nothing in
windows.  I'm blaming stac 3.1, but nothing will print.  However, when I go to
DOS, I can print find.   I'm not sure where to look at this point, but any help
would be appreciated......
Thanks.....Look forward to hearing from u soon.....

There is 1 Reply.

#: 40757 S4/Stacker 3.1
    29-Nov-93  20:01:51
Sb: #40546-62STAC.EXE PROBLEMS
Fm: Stac Electronics 75300,2755
To: Ken Pfister 73522,2533

Ken,

If DOS 6.2 is installed you may need to recreate a Stacker aware dblspace.bin
file.  Run REDBL C:  from the TOOLS directory on the Stacker 3.1 install
diskette.

As for printing, Stacker would not interfer.  Make sure you have the correct
setting in the Control Panel.

Keith Dunlea, Stac Tech Support

#: 40547 S4/Stacker 3.1
    25-Nov-93  10:10:54
Sb: #Stacker 8-bit co-proc.
Fm: Gary L. Heimstead 72322,1212
To: ALL

I have had an 8-bit co-processor since the Stacker 1.x daze.  I took it out
after upgrading to version 2 because my LAN benchmarks for disk access were
higher without it.  Just for your information, I had also changed my server to
a 386DX40, from a 286/20.  I'm now using Stacker 3.1, with the same server, and
found my old co-proc. card sitting on the shelf.  Before I lose the card again,
I was wondering if anyone could tell me whether what I found in terms of
performance without the card is normal.  Would Stacker 3.1 run faster with it,
or with out it, and if it would run faster with it, what should I be looking
for that may cause the slow down I experienced?  Thanks in advance for any
thoughts...

Talk to ya
Gary

There is 1 Reply.

#: 40618 S4/Stacker 3.1
    27-Nov-93  03:30:13
Sb: #40547-#Stacker 8-bit co-proc.
Fm: Edward Nutter [Stac] 75330,2222
To: Gary L. Heimstead 72322,1212 (X)

Gary,

Lose the card, or put it in an XT.  The AT/16 would have improved throughput on
the 286, but Stacker 3.1 on a 386DX-40MHz will outrun and out compress the old
hardware.

Ed Nutter
Stac Product Support

There is 1 Reply.

#: 40786 S4/Stacker 3.1
    29-Nov-93  21:37:15
Sb: #40618-Stacker 8-bit co-proc.
Fm: Gary L. Heimstead 72322,1212
To: Edward Nutter [Stac] 75330,2222 (X)

 >>Lose the card, or put it in an XT.

   Thanks, I thought that's what the conclusion would be.

Talk to ya
Gary

#: 40549 S4/Stacker 3.1
    25-Nov-93  10:59:34
Sb: #Lost Cluster
Fm: Bruno Deschjnes 76646,3552
To:  75300,2755 (X)

Dear Keith, Thank you very much for your answer to my message.  There is one
other problem that keeps recurring are lost clusters when passing Norton Disk
Doctor /quick.  Today I had 2 errors on the compression structure.  On a
regular basis I have lost cluster which I rarely had before I installed Stacker
3.1.  Do you know what could cause that? Thanks a lot for your help!


There is 1 Reply.

#: 40759 S4/Stacker 3.1
    29-Nov-93  20:02:00
Sb: #40549-#Lost Cluster
Fm: Stac Electronics 75300,2755
To: Bruno Deschjnes 76646,3552 (X)

Bruno,

DId you try the suggestions from my first message  ?   The lost clusters are
caused by your applications locking.

As for NND/ Q    If your running NU7 make sure you have the latest copy of NU
7.1   It can be downloaded from the Symantec forum

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40826 S4/Stacker 3.1
    30-Nov-93  12:52:00
Sb: #40759-Lost Cluster
Fm: Bruno Deschjnes 76646,3552
To: Stac Electronics 75300,2755 (X)

Dear Keith: Yes I did, but I will then try to get NU 7.1. Thanks a lot!

#: 40550 S4/Stacker 3.1
    25-Nov-93  12:12:47
Sb: #Dos 6.2 and 3.11?
Fm: Fred Skrotzki 73647,2345
To: all

I found notes for Stacker 3.11 while scanning the MS knowlage base for dos 6.2.
Is this a new version/Bug Fixes/Update?  Is it a free upgrade of costs?  What
improvements does it provide.

it's interesting that MS is supplying the 6.2 step up free on line all you need
to do is type go dos62.

There is 1 Reply.

#: 40760 S4/Stacker 3.1
    29-Nov-93  20:02:03
Sb: #40550-Dos 6.2 and 3.11?
Fm: Stac Electronics 75300,2755
To: Fred Skrotzki 73647,2345 (X)

Fred,

The only change to the software was an update for compressed hard cards.  To
label this we has to change the time stamp to 3.11.  If your not running a hard
card or having problems with one, the upate is not needed.

Keith Dunlea, Stac Tech Support

#: 40554 S4/Stacker 3.1
    25-Nov-93  13:27:35
Sb: #STACKING BOOT AFTER HARD
Fm: BARRY HURET 71640,1746
To: SYSOP (X)

I left a message about a week ago on forum. I have stacked 100meg hardcard
using 3.1 and DOS6.0. No problem (afterI received faxnotes on use of hardcard.
It should be in addendum in manual). Now I am considering stacking my
bootdrive, a 245meg hardDISK. Currently, DISK is C, Hardcard is D (stacked) and
E (small unstacked portion). I want to stack my C drive, and hope that the
unstacked (small boot portion) will automatically be called F; leaving my C, D,
E as presently recognized by programs.... This is important because of windows.
While I am fully backedup on tape, I don't want to waste time/effort. Can you
advise if stacking C will give result I am looking for, or are other actions
needed by me? (Also, will I have to edit the hidden stacker ini file again?
Right now it is set to recognize the hardcard.) Thanks for reply. Hope you
have/had good Thanksgiving Holiday.  Barry

There is 1 Reply.

#: 40761 S4/Stacker 3.1
    29-Nov-93  20:02:09
Sb: #40554-#STACKING BOOT AFTER HARD
Fm: Stac Electronics 75300,2755
To: BARRY HURET 71640,1746 (X)

Barry,

Yes, when you compress drive C it will be assigned the next available drive
letter; drive F:

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40789 S4/Stacker 3.1
    29-Nov-93  22:38:00
Sb: #40761-#STACKING BOOT AFTER HARD
Fm: BARRY HURET 71640,1746
To: Stac Electronics 75300,2755 (X)

Keith, Thanks. It did work. Regards, Barry

There is 1 Reply.

#: 41015 S4/Stacker 3.1
    01-Dec-93  15:32:42
Sb: #40789-STACKING BOOT AFTER HARD
Fm: Stac Electronics 75300,2755
To: BARRY HURET 71640,1746

Barry,

Thanks for the report back!

Keith Dunlea, Stac Tech Support

#: 40563 S4/Stacker 3.1
    25-Nov-93  18:47:37
Sb: #Stacker 3.1 versions
Fm: E.R. Tippelt 100115,3301
To: Keith Dunlea 75300,2755 (X)

I have just noticed that the Microsoft MSDOS forum has posted a warning about
upgrading to MSDOS 6.02 if you are using Stacker 3.1, and goes on to reference
two versions of Stacker 3.1  - 3.1a dated 06.03.93 (which I have) and an
apparent later version, 3.1b dated 09.08.93. The later version is the one that
MS expects to give problems, but can you tell me what is the difference in the
functionality of the two releases of Stacker 3.1.

Also - are there any compatibility issues between either version of Stacker 3.1
and QEMM 7, 7.01, 7.02 or 7.03, as I plan to upgrade from QEMM 6 shortly, and
from Windows 3.1 to Windows for Workgroups 3.11

Thanks

Ed



There is 1 Reply.

#: 40765 S4/Stacker 3.1
    29-Nov-93  20:02:36
Sb: #40563-Stacker 3.1 versions
Fm: Stac Electronics 75300,2755
To: E.R. Tippelt 100115,3301 (X)

Ed,

We updated the Stacker 3.1 driver for an issue with compressed hard cards.  To
keep a record of this change the time stamps on the files were changes to 3.11
No other changes have been made.

Keith Dunlea, Stac Tech Support

#: 40565 S4/Stacker 3.1
    25-Nov-93  21:05:11
Sb: #SDEFRAG Write Error 110
Fm: Stephen E. Sullivan 72702,351
To: Stac Electronics 75300,2755 (X)

As you suggested, I downloaded the 3405.txt and followed the instructions.
Using Norton V7, I was able to correct the problem so that SDEFRAG, CHECK and
Norton's CALIBRATE are happy... and so am I.  Thanks for you help. 

There is 1 Reply.

#: 40766 S4/Stacker 3.1
    29-Nov-93  20:02:41
Sb: #40565-SDEFRAG Write Error 110
Fm: Stac Electronics 75300,2755
To: Stephen E. Sullivan 72702,351

Stephen.

Thanks for the report back!

Keith Dunlea, Stac Tech Support

#: 40569 S4/Stacker 3.1
    25-Nov-93  22:22:12
Sb: #Slow floppy access
Fm: LAWRENCE P. SINNAEVE 71553,336
To: sysop (X)

I recently upgraded my system to DOS 6.2 and Stacker 3.1 and now when I try to
access my floppy drives it takes forever to get an A: or B: prompt.  However,
when I boot from a floppy using Dos5.0 and no Stacker, my access time to the
floppies is greatly increased.  My system is a 486dx33 and I never had this
problem before.

Does anybody have any ideas what the problem might be?
 

There is 1 Reply.

#: 40579 S4/Stacker 3.1
    26-Nov-93  12:47:53
Sb: #40569-Slow floppy access
Fm: Russ Mueller 76662,1623
To: LAWRENCE P. SINNAEVE 71553,336 (X)

Add /-AUTO to your Stacker line to prevent auto logging of Stac'ed floppies.

#: 40570 S4/Stacker 3.1
    26-Nov-93  00:43:38
Sb: OS/2 for Windows
Fm: Albert Rodriguez 72254,1215
To: sysop (X)

I want to buy OS/2 for Windows.  I know I can't install the program on a
stacked drive, but will I be able to read drive D: which is a stacked drive.
IBM says yes, but I wasn't to confident with whom I spoke.  Please settle this
for me.


            -Albert- 

#: 40571 S4/Stacker 3.1
    26-Nov-93  01:52:17
Sb: #Dos 6.2 step-up
Fm: John Brown 72437,2517
To: Stac Electronics 75300,2755 (X)

I have 3.1 (hardcard update). When I tried to "stepup" from DOS 6.0
to 6.2 I was informed that my C drive didn't have enough free space.
I have about 80 MB actual (140 MB stacked) free!
C: was C at boot
D: was D at boot (hardcard)
E: was E  " "   Stacvol for C
F: was F  " "      "    for hardcard

Will 62stac.exe fix this ?
 

There is 1 Reply.

#: 40771 S4/Stacker 3.1
    29-Nov-93  20:03:07
Sb: #40571-Dos 6.2 step-up
Fm: Stac Electronics 75300,2755
To: John Brown 72437,2517

John,

Yes, you need to download 62stac.exe and run it to extract two-utilities plus a
TEXT files with instructions.

Keith Dunlea, Stac Tech Support

#: 40573 S4/Stacker 3.1
    26-Nov-93  07:53:05
Sb: #Stack install problem
Fm: Walter Haeberle 71760,1703
To: Keith Dunlea

To: Keith Dunlea, Tech Suppt.


Keith,

Thanks for your message.  The error message I got was:

Installation error, unable to locate SETUP.SAF

I think I discovered the real the nature of the problem:

chkdsk found allocation problems, junk, etc., further investigation uncovered a
virus NOINT which seems to have left permanent damage to the files on the disk.

Please instruct me on how I can return the disks to you for a replacement.

Walter Haeberle

There is 1 Reply.

#: 40772 S4/Stacker 3.1
    29-Nov-93  20:03:12
Sb: #40573-Stack install problem
Fm: Stac Electronics 75300,2755
To: Walter Haeberle 71760,1703 (X)

Wlater,

Please call 800-522-7822 and ask for customer service.  They will be able to
help

Keith Dunlea, Stac Tech Support

#: 40581 S4/Stacker 3.1
    26-Nov-93  13:27:43
Sb: #Upgrading to DOS 6.2
Fm: Emil J. Tillona 71345,253
To: 75300, 2755

Hello.

I have Stacker Ver 3.1 and DOS 5.0 running on a 386DX system.  How do I go
about upgrading to DOS 6.2?  Can I do away with the drive swapping completely.
When I stacked by drive I was unble to run some DOS applications that use the
SUBST command.

Any help to can shed on the above problems would be most appreciated.


There is 1 Reply.

#: 40777 S4/Stacker 3.1
    29-Nov-93  20:03:35
Sb: #40581-Upgrading to DOS 6.2
Fm: Stac Electronics 75300,2755
To: Emil J. Tillona 71345,253

Emil,

If running DOS 5 you must be using Stacker 3.0  In this case DOS 6.2 will
install without conflict,  Then upgrade to Stacker 3.1

Stacker 3.1 will use a "pre-load" driver,  The drives still sswap but before
config/autoexec runs

Keith Dunlea, Stac Tech Support

#: 40582 S4/Stacker 3.1
    26-Nov-93  13:29:38
Sb: #Peculiar new hidden file
Fm: Don Howard 71155,1370
To: Sysop (X)

Hello,

I just installed Stacker 3.1 running under Windows and checked the results.
Everything seems to be in order according to my preliminary understanding of
Stacker except on drive D: I see a non system-related path structure leading to
a bunch of hidden files called daynarid.sys that have no equivalent on C:.  How
did they get there?  I hope I provided enough information in this message.  If
not, please tell me what more you need to know and I'll respond.  Thanks,

- Don Howard

There is 1 Reply.

#: 40861 S4/Stacker 3.1
    30-Nov-93  18:46:51
Sb: #40582-#Peculiar new hidden file
Fm: Stac Electronics 75300,2755
To: Don Howard 71155,1370 (X)

Don,

By default,  Stacker leaves hidden files,  which may be part of a copyright
protected program, alone.   If you don't know what apps they belong too it
maybe left over from some software that your removed.

the delete the files use attrib -h -r -s *.*  to unhide then remove.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40946 S4/Stacker 3.1
    30-Nov-93  20:49:31
Sb: #40861-#Peculiar new hidden file
Fm: Don Howard 71155,1370
To: Stac Electronics 75300,2755 (X)

Keith,

Thanks for the response.  I checked on the installation diskette for that
product and, sure enough, saw the hidden files.  I have no idea why this
product, some source code accompanying a book, put the hidden files there but
they did.

So far so good on Stacker.  I like the ability you gave it to be up and running
with a minimum of effort then optimize it as time passes.

- Don Howard

There is 1 Reply.

#: 41168 S4/Stacker 3.1
    02-Dec-93  19:00:00
Sb: #40946-Peculiar new hidden file
Fm: Stac Electronics 75300,2755
To: Don Howard 71155,1370

Dom

Good to see you found the owners of those files.

Keith Dunlea, Stac Tech Support

#: 40588 S4/Stacker 3.1
    26-Nov-93  17:53:37
Sb: #Move Swapfile to front
Fm: Kenn Croft 70534,1660
To: ALL

To any expert:

My Windows 3.1 permanent swap file is in the middle of my host (D:) drive,
surrounded by STACVOL.DSK.  I want to get ny swap file relocated to the
front of the drive.

I've acsertained that I can defragment STACVOL.DSK using SATTRIB and
CREATE /p from the Stacker 3.1 install disk.  Most likely then I can get my
swap file out of the middle of STACVOL.DSK, but the swap file probably
ends up at the back of the drive.

If I remove the s,h,r attributes from STACVOL.DSK with DOS's attrib and run
DOS's DEFRAG (I would use /SD or SD-) to move STACVOL.DSK to the end
of the host drive's root directory and the swap file (actually a dummy-file
substitute after removing swap-file in Windows) to the front of the root
directory, I think I'll
achieve what I want.  Of course, then I would restore the s,r,h attributes to
STACVOL.DSK.

Can I do this to STACVOL.DSK, or would everything be all screwed up ?

Thanks,
               Kenn

There is 1 Reply.

#: 40620 S4/Stacker 3.1
    27-Nov-93  03:40:24
Sb: #40588-#Move Swapfile to front
Fm: Edward Nutter [Stac] 75330,2222
To: Kenn Croft 70534,1660 (X)

Kenn,

You can do that, but it's not clear why you would want to.  There's no
advantage to having the permanent swap file at the start of the root directory.
Windows only reads the entry once to find out where it is on disk, and does
direct sector I/O via the controller chip thereafter.  You may avoid some seek
time during program launch or file opening by having the swap file adjacent to
the header end of the STACVOL, but I doubt you could measure it.

Ed Nutter
Stac Product Support

There is 1 Reply.

#: 40627 S4/Stacker 3.1
    27-Nov-93  10:32:26
Sb: #40620-Move Swapfile to front
Fm: Kenn Croft 70534,1660
To: Edward Nutter [Stac] 75330,2222 (X)

Ed:

I've been sifting through my issues of Windows Sources and found, on page 341
of the July issue:

"To improve the performance of a permanent swap file even further, you should
configure the file to reside at the beginning of your hard disk, near the
system area (boot sector, FAT, and root directory).  By definition, the swap
file is usually a very active area of the hard disk.  Locating the permanent
swap file near the beginning of the hard disk can confine a large number of
disk accesses to a small portion of your hard disk."

Since I have 4MB RAM (rather than what seems to be a recommended 8 MB
nowadays), I figured I would
go to the trouble to make sure my swap file was optimally placed.

On the other hand, I just got my new 486 a couple of weeks ago, after running a
286 for 5 years, and perhaps I'm just enjoying tweaking my system (measurably
or not) a bit much !

Thanks for the reply.

Kenn

#: 40589 S4/Stacker 3.1
    26-Nov-93  17:55:46
Sb: #Lost Sectors
Fm: Charles Vortreflich 70640,1524
To: Tech Support

Since installing Stacker 3.1, I find that, more often than not, "chkdsk"
command gives me a message that lost sector groups were found, even though
nothing unusual occurred during the Windows session just completed.  When I run
"chkdsk/f", usually one lost sector group is reclaimed. This often happens when
I use graphical programs such as Photoshop. This hardly ever happened before
installing Stacker and, when it did, it occurred when something unusual
happened while running windows (ie--power outage).

Is this a problem or can it lead to a problem? How should I handle it?

There is 1 Reply.

#: 40863 S4/Stacker 3.1
    30-Nov-93  18:46:59
Sb: #40589-Lost Sectors
Fm: Stac Electronics 75300,2755
To: Charles Vortreflich 70640,1524 (X)

Charles,

Are you seeing lost clusters or sectors ?  Lost sectors would be from Stacker
and are "erased space" which has yet to be claimed. This is considered normal
and tends to happen when large temp files are removed.  See tech note 3501.txt
in lib:3 Is Photoshop using a temp file ?   What else is loaded ?

Keith Dunlea, Stac Tech Support

#: 40594 S4/Stacker 3.1
    26-Nov-93  21:55:42
Sb: #Unfixable Disk Error
Fm: Tim Larmour 70307,1332
To: SYSOP (X)

I have Stacker 3.1 for Windows running on a 386 clone under DR-DOS 6 and Win
3.1, and it has been humming away happily for several months.  I developed a
problem this week though with drive access, and cannot do a backup using
PCTools - it reports lost clusters, use CHKDSK.  Using CHECK /F reports a FAT
problem but doesn't do anything to fix it.  CHKDSK aborts midway into it's run
and fixes nothing.  So, how do I get this problem fixed?  I hate the feeling of
having 250 Meg ready to crash and being unable to even do a backup before it
does.  Any help welcome and appreciated.   /Tim

There is 1 Reply.

#: 40867 S4/Stacker 3.1
    30-Nov-93  18:47:12
Sb: #40594-Unfixable Disk Error
Fm: Stac Electronics 75300,2755
To: Tim Larmour 70307,1332 (X)

Tim,

Chkdsk like error can only be corrected by CHKDSK /F or running your DISK FIX
from PC Tools.  Its recommended your run the latter. IF the compressed drive is
write protected use CHECK /=W then run disk fix

Keith Dunlea, Stac Tech Support

#: 40595 S4/Stacker 3.1
    26-Nov-93  22:02:12
Sb: #DOS 6.2 upgrade?
Fm: Rick Shumway 72047,225
To: sysop (X)

Are there any problems in upgrading to DOS 6.2 while running Staker 3.1?

Rick

There is 1 Reply.

#: 40868 S4/Stacker 3.1
    30-Nov-93  18:47:14
Sb: #40595-#DOS 6.2 upgrade?
Fm: Stac Electronics 75300,2755
To: Rick Shumway 72047,225 (X)

Rick,

See forum News Flash and download 62STAC.EXE

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40987 S4/Stacker 3.1
    01-Dec-93  11:38:29
Sb: #40868-DOS 6.2 upgrade?
Fm: Rick Shumway 72047,225
To: Stac Electronics 75300,2755 (X)

Thanks.

Rick

#: 40597 S4/Stacker 3.1
    26-Nov-93  23:23:37
Sb: #STAC 3.1 AFTER DOS 6.2
Fm: Christian J Johnen 70413,3561
To: STAC

I have just updated my new system with DOS 6.2; I want now to install Stacker
3.1. Should I uninstall DOS 6.2? Should I expect problems? I shall greatly
appreciate any advice.
Thank you,
Chris.

There is 1 Reply.

#: 40869 S4/Stacker 3.1
    30-Nov-93  18:47:17
Sb: #40597-STAC 3.1 AFTER DOS 6.2
Fm: Stac Electronics 75300,2755
To: Christian J Johnen 70413,3561

Chris

Stacker 3.1 will run fine with DOS 6.2   Just run SETUP and let Stacker do the
rest

Keith Dunlea, Stac Tech Support

#: 40602 S4/Stacker 3.1
    27-Nov-93  00:39:24
Sb: #Autoexec.bat&Stacker3.1
Fm: Michael Borenstein 71513,1222
To: All

This is the third posting of this message is anyone out there!!!!
Has anyone experenced this problem?-with DOS 6.2 BOTH config.sys AND
autoexec.bat can be loaded interactively by pressing F8. I have found that I
have no control over autoexec.bat loading -no matter what I do autoexec.bat
always runs. I posted this to both Microsoft and Stac and they said they are
looking into it but no response so far. I have noticed that there seems to be
no problem when running doublespace.

There are 2 Replies.

#: 40871 S4/Stacker 3.1
    30-Nov-93  18:47:26
Sb: #40602-#Autoexec.bat&Stacker3.1
Fm: Stac Electronics 75300,2755
To: Michael Borenstein 71513,1222 (X)

Michael,

The problem has been reported and is being looked into.  I'll try it myself to
see if this is the case.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40958 S4/Stacker 3.1
    30-Nov-93  23:13:19
Sb: #40871-#Autoexec.bat&Stacker3.1
Fm: Michael Borenstein 71513,1222
To: Stac Electronics 75300,2755 (X)

Thanks Keith, but how will I know if a fix has been found ? Will you contact
me?

There is 1 Reply.

#: 41046 S4/Stacker 3.1
    01-Dec-93  19:01:19
Sb: #40958-Autoexec.bat&Stacker3.1
Fm: Roger Hicks 74250,1407
To: Michael Borenstein 71513,1222 (X)

Michael;

Usually we will post a technical note or message within the forum. Please check
back in about a week.

Thanks,

Keith Moon
STAC Product Support

#: 41037 S4/Stacker 3.1
    01-Dec-93  18:17:49
Sb: #40602-Autoexec.bat&Stacker3.1
Fm: Stac Electronics 75300,2755
To: Michael Borenstein 71513,1222 (X)

Michael.

As you know, its been reported and we are looking into this matter.  Thanks for
your patience

Keith Dunlea, Stac Tech Support

#: 40606 S4/Stacker 3.1
    27-Nov-93  00:51:51
Sb: Stacker 3.1 & WP6.0a
Fm: Ron VanAbrahams 76414,270
To: Keith Dunlea 70674,3364


....Ron     ==> Northern California, USA @  9:44p PDST on Thu, 25-NOV-1993

#: 40609 S4/Stacker 3.1
    27-Nov-93  01:58:14
Sb: #STACKER 3.1 & WP6.0a
Fm: Ron VanAbrahams 76414,270
To: Keith Dunlea 70674,3364

Keith,      <Sorry about the blank message; I messed up!>

I thought I have cured my problems with STACKER 3.1 and WordPerfect 6.0a
when I eliminated the "DOS ERROR 30" messages I was getting.  That was not
the case, however.  Now I've got a new problem.  I cannot write WP6 files to
the "stacked" part of the HD at all!

I run WP6 on both a 386DX33Mhz-8Meg desktop and 386DX16Mhz-8Meg laptop.
These machines are very similarly configured except the *laptop also runs
STACKER 3.1.  I've had no problems with any software on either machine
except for WP6 on the laptop.  Everytime I try and write a WP file on the
laptop, WP just hangs, requiring a warm reboot!

I've methodically stripped both CONFIG.SYS and AUTOEXEC.BAT and nothing
solves the problem.  The only thing that works is to write WP6 files to the
unSTACKED part of the disk.  As it is, I've offloaded some apps to expand
the uncompressed part of the disk as all WP temporary files now use this
part of the disk (that's what cured the "DOS ERROR 30" problems, I guess).
Unfortunately, I cannot afford the luxury of putting all my WP files on the
unSTACKED part of the disk.

I've gotten no solution from WPUSERS and before I go further with WPC, I'd
like to gather any information you might have that could be of help to me.
I know my laptop is an "old" (read that, slow) machine but I'm not
convinced that is the entire problem.

Any help or insights you might be able to offer would be very much
appreciated.  Thanks in advance.

....Ron     ==> Northern California, USA @ 10:14p PDST on Thu, 25-NOV-1993

There is 1 Reply.

#: 41038 S4/Stacker 3.1
    01-Dec-93  18:17:54
Sb: #40609-#STACKER 3.1 & WP6.0a
Fm: Stac Electronics 75300,2755
To: Ron VanAbrahams 76414,270 (X)

Ron,

DOS ERROR 30 indicates either there are damaged WP files or a problem using the
temp file. Run a disk utility plus Check /F to check for errors.  Then set your
temp files to a non-compressed drive to see if that helps

Let me know the results

Keith Dunlea, Stac Tech Support

There are 2 Replies.

#: 41075 S4/Stacker 3.1
    01-Dec-93  20:04:26
Sb: #41038-#STACKER 3.1 & WP6.0a
Fm: Ron Curtin 76057,112
To: Stac Electronics 75300,2755 (X)

I have had similar problems in using WPWIN 6.0.  I have taken it off my machine
and am using AmiPro instead.  Is there a problem with WP 6.0???

There is 1 Reply.

#: 41169 S4/Stacker 3.1
    02-Dec-93  19:00:04
Sb: #41075-STACKER 3.1 & WP6.0a
Fm: Stac Electronics 75300,2755
To: Ron Curtin 76057,112 (X)

Ron,

As stated, DISK ERROR 30 could be from a damaged file or the temp file.
Solution is to run a disk utility and move the temp file to a uncompressed
drive.

Keith Dunlea, Stac Tech Support

#: 41128 S4/Stacker 3.1
    02-Dec-93  16:22:17
Sb: #41038-#STACKER 3.1 & WP6.0a
Fm: Ron VanAbrahams 76414,270
To: Stac Electronics 75300,2755 (X)

Keith,

Here are the results of CHKDSK and some other material.  I also confirmed
Shft-F1 (setup) looks at D:\TEMP for writing timed backup files.  WP reports
it's "Using D:\TEMP" when it loads.

Because WP recently totally destroyed its own directory (sorta like doing
bad stuff in your own nest, if you get my drift), I totally reinstalled WP
from the distribution disks a week ago.  This problem occured before the
re-install and still occurs.

What I've noticed is that WP starts to write to the disk with no apparent
reason (like would occur with a timed backup) and that's when the problems
begin.  The first symptom is the DOS ERROR 30 report.  Sometimes I don't
even get that but when I hit either F10 (save) or F7 (save and exit), WP
locks requiring a warm reboot.

I've no other problems on this machine.... only WP6 won't work.

AUTOEXEC.BAT (excerpted)
============
  \stacker\check /wp
  set wp=/du/ne/rx/nh/np/w-*,*,*/d-d:\temp/pf-d:\temp/mono
  \netroom\xload.exe -sC001 -m46336 c:\pcache\pcache.com /k
  \netroom\xload.exe -sC001 -m47216 \81mouse\mouse.com /c1 /n3

CONFIG.SYS (excerpted)
==========
device=c:\netroom\rm386.exe auto nowin3 nof not nops2 xms=F000-F6FF
       xms=FC00-FDFF
device=c:\netroom\vidcloak.exe /pmbios
fcbs=1,0
stacks=0,0
device=c:\netroom\xload.sys -sE156 -m59152 c:\stacker\stachigh.sys
device=c:\netroom\xload.sys -sC001 -m48192 c:\hyper\hyperdkx.exe c:2048
       or ok:X0E

CHECKD.DMP ("CHKDSK D:") (excerpted)
==========
Volume C-DRIVE     created 06-12-1991 12:06p
   42,366,976 bytes total disk space
    2,816,000 bytes available on disk

CHECKC.DMP ("CHKDSK C:") (excerpted)
==========
Volume STACVOL_000 created 09-25-1992 11:09p
   69,058,560 bytes total disk space
    3,563,520 bytes available on disk

      655,360 total bytes memory
      638,112 bytes free

CHECK - 3.10, (c) Copyright 1990-93 Stac Electronics, Carlsbad, CA

Volume in drive C is STACVOL_000

No errors found

Stacker Drive Compression Ratio = 1.8:1
Projected Bytes Free            = 3,563,520

SET.DMP ("SET") (excerpted)
=======
WP=/du/ne/rx/nh/np/w-*,*,*/d-d:\temp/pf-d:\temp/mono

. /DU=Don't use upper memory; /NE=Don't use exPanded memory (there is none);
. /RX=Load WP overlay into exTended memory; /NH=Don't print to hardware port;
. /W=WP to use all available memory;  /MONO=It's an LCD screen;
. /D and /PF=Write *all temp files to designated drive

Thanks for your help.

....Ron     ==> Northern California, USA @  1:19p PDT on Thu, 02-DEC-1993

There is 1 Reply.

#: 41135 S4/Stacker 3.1
    02-Dec-93  18:29:00
Sb: #41128-STACKER 3.1 & WP6.0a
Fm: Roger Hicks 74250,1407
To: Ron VanAbrahams 76414,270 (X)

Ron;

I everything looks fine to me in terms of system configuration. I'll submit a
copy of you message to our engineering team to
see if they have any ideas.

Thanks,

Keith Moon
STAC Product Support

#: 40622 S4/Stacker 3.1
    27-Nov-93  03:47:23
Sb: #Two Problems: WFW and F5
Fm: Jeff Cherniss 71510,3243
To: Sysop (X)

Please help me.
I have been an avid STAC user and have loved the product.  I just upgraded to
3.1 and lost some key features that I am rather upset about.
1. I have WFW  and I do not get a STACKER menu in File Manager.  Why didn't you
tell me before I bought the product?  Now what do I do?  I bought the upgrade
in order to have that Menu item in File manager?

2.  I always use the F5 key when DOS is loading so that I can load a
configuration that uses a minimum amount of memory.   This is important form
running many of the memory intensive games I use.   Now, when I press F5 and
Stacker loads, I find that stacker is taking my DOS memory away.  Why is this?
How can I now boot dos and get a configuration that leaves most of my DOS
memory (below 655kb) intact?

Thanks

Jeff

There is 1 Reply.

#: 40873 S4/Stacker 3.1
    30-Nov-93  18:47:32
Sb: #40622-#Two Problems: WFW and F5
Fm: Stac Electronics 75300,2755
To: Jeff Cherniss 71510,3243 (X)

Jeff,

1.   Stacker should be included in the file manager.  Select FILE and RUN and
type SGROUP.  This should rebuild the enteries.

2.  Stacker 3.1 is a pre-loaded before Config/autoexec.bat  If you prefer to
mount if from the config.sys you would have to add the appropiate Stacker lines
back into the config.sys Then remove dblspace.bin and stacker.ini [both hidden]
from the host boot drive.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40970 S4/Stacker 3.1
    01-Dec-93  01:35:52
Sb: #40873-#Two Problems: WFW and F5
Fm: Jeff Cherniss 71510,3243
To: Stac Electronics 75300,2755 (X)

Thank you. I appreciate your response.  You solved problem #1 for me very
well!!! I now want to proceed with your solution to problem #2.  Please help me
by giving me some idea what the correct format of the lines in the config.sys
file should be. Is it possible to use the information that is in the hidden
files to get the correct paramaters for my system?   I do not want to make any
errors or minimize the performance of Stacker.  Thanks.

P.S. Please advise: besides not loading stacker immediately, am I giving up any
other benefits of stacker by proceeding with the solution in step #2?

There are 2 Replies.

#: 41047 S4/Stacker 3.1
    01-Dec-93  19:01:23
Sb: #40970-#Two Problems: WFW and F5
Fm: Roger Hicks 74250,1407
To: Jeff Cherniss 71510,3243 (X)

Jeff;

No you are not giving up any other benefits.

Thanks,

Keith Moon
STAC Product Support

There is 1 Reply.

#: 41096 S4/Stacker 3.1
    02-Dec-93  01:08:27
Sb: #41047-Two Problems: WFW and F5
Fm: Jeff Cherniss 71510,3243
To: Roger Hicks 74250,1407 (X)

Thanks Keith, but you didn't help me with the first part of my message.

How can I find what lines I am to enter into the config.sys file?  Will you
please be as specific as possible so that I can be sure not to make an error.
(This is so that STACKER 3.1 is not automatically loaded upon startup...)

thanks...

#: 41170 S4/Stacker 3.1
    02-Dec-93  19:00:09
Sb: #40970-Two Problems: WFW and F5
Fm: Stac Electronics 75300,2755
To: Jeff Cherniss 71510,3243 (X)

Jeff,

The Stacker lines will differ for each machine.  the primary layout is as
follows

device=c:\stacker\stacker.com c:\stacvol.dsk device=c:\stacker\sswap.com
c:\stacvol.dsk /sync

if you have more than one stacvol file, add each to the Stacker.com line plus a
sswp line.  refer to your stacker.ini file for name of stacvol file

Keith Dunlea, Stac Tech Support

#: 40624 S4/Stacker 3.1
    27-Nov-93  04:27:32
Sb: #Stacker 3.1 & WfW 3.11
Fm: Peter C. Reilly 76555,1177
To: Stac Electronics 75300,2755 (X)


Dear Keith,

Since I started this series, I appreciate Stac's working on this. As an
American living in England for a year, I feel a bit cut off from developments
in the States. CIS helps quite a bit, but new product introductions or
upgrades, and magazine reviews seem to lag behind the States by weeks or
months. So that is why I wanted to check on WfW 3.11 before I did anything
rash, like upgrade to it and find out later that Stacker doesn't work with it,
and I lose all my file structures, etc.!

I will be patient. I was surprised when I checked the forum and found so many
messages on this topic. I use WinCIM, and I hadn't been alerted that I had any
replies to my messages. Isn't WinCim supposed to alert me to that? Or do I have
to set some obscure switch to turn this on? Or am I supposed to just check the
forum on my own?

I am a satisfied customer of Stac. It is much more stable compared to
Doublspace and could compress my whole 400 Meg drive, not just 250.

Thanks again, Keith. I look forward to your research.

Sincerely,

PETER C. REILLY      c/o Senior Common Room      PHONE & FAX:
                            St. Mary's College                      (091)
374-2571
                            University of Durham
                            Elvet Hill Road
                            Durham DH1 3LR           INTERNET E-Mail:
                            United Kingdom
peter.reilly@durham.ac.uk

There is 1 Reply.

#: 40875 S4/Stacker 3.1
    30-Nov-93  18:47:38
Sb: #40624-Stacker 3.1 & WfW 3.11
Fm: Stac Electronics 75300,2755
To: Peter C. Reilly 76555,1177 (X)

Peter,

If a message is sent in the Forum you must rejoin it to receive mail.  IF the
message is sent to your mailbox it would be flagged upon entry to CompuServe

Keith Dunlea, Stac Tech Support

#: 40631 S4/Stacker 3.1
    27-Nov-93  14:04:44
Sb: #STACHIGH locks system
Fm: Gary Pickavet 75410,122
To: Stac Electronics 75300,2755 (X)

I am VERY frustrated with Stacker 3.1 and DOS 6.2.  I had all sorts of
problems getting my RAM Drive to get created and swapped to f:.  I have a
Gateway 486/66 with 16M of memory.  I have ONE hard drive.  I have used
Stacker to create 2 stacker volumes.  I have and want to have a C: stacker
volume, a D: stacker volume, E: as my uncompressed disk which has the
stacker volumes on them, and F: as my RAM drive (which is initially created
as D: in the CONFIG.SYS file.)  After a LOT of dinking around, I FINALLY got
this setup to work.  Now, for no apparent reason, I turned my machine on
this morning and STACHIGH just locks up my computer whenever it runs!!!  I
installed STACHIGH from my original floppy disk and still have the same
results!  If I am running 386MAX 7.0, instead of locking the system, I get
the message:

"A privileged operation exception at A300:0000 has occured."  This happens
when I run STACHIGH.  It has been running for a week without a problem. If I
don't first load the RAMDRIVE.SYS driver, STACHIGH doesn't crash. I looked
at the change dates on AUTOEXEC.BAT, CONFIG.SYS, STACKER.INI, and all the
386MAX profile files and NONE have been changed in the last 2 days. So why,
all of a sudden, would things stop working!!! This is very frustrating.

Any ideas?  Like QUICK!!!  I'm ready to switch to myself and my office to
DOS's disk doubling software!

Gary  -- Here are some files to help solve the problem (I Hope!)

*******************************************************


[menu]
menuitem=Win, Normal startup - Start Windows
menuitem=No_Win, Normal startup - Don't Start Windows
menuitem=Kidpix, Run KidPix Program
menuitem=Grolier, Run Groliers CD Rom Encyclopedia
menucolor=15,1
menudefault=Win, 10

[common]

buffers=10,1
FILES=80
lastdrive=Z
FCBS=20,0
DOS=HIGH
break=on
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /e:800 /p
rem install=c:\dos\share.exe /L:100
Stacks=0,0

[Grolier]
Device=c:\utility\386max\386max.sys pro=c:\utility\386max\386max.pro
device =C:\UTILITY\386MAX\386load.sys size=11504 flexframe prog=C:\DOS\SETVER.EXE
DEVICE=C:\UTILITY\386MAX\386load.sys size=5888 flexframe prog=C:\DOS\ramdrive.sys 2048/E
device=c:\utility\stacker\screate.sys D:
device =C:\UTILITY\386MAX\386load.sys size=63216 prgreg=2 flexframe prog=C:\UTILITY\STACKER\STACHIGH.SYS
device =C:\UTILITY\386MAX\386load.sys size=9072 flexframe prog=C:\DOS\ANSI.SYS
device =C:\UTILITY\386MAX\386load.sys size=13856 flexframe prog=C:\SBCD\SBCD.SYS /D:MSCD001 /P:250 /T:2 /S:A0
DEVICE=D:\CD\NGME\sndbk12.sys 1 7 220 2

[Win]
Device=c:\utility\386max\386max.sys pro=c:\utility\386max\386max.pro
device =C:\UTILITY\386MAX\386load.sys size=11504 flexframe prog=C:\DOS\SETVER.EXE
DEVICE=C:\UTILITY\386MAX\386load.sys size=5888 flexframe prog=C:\DOS\ramdrive.sys 2048/E
device=c:\utility\stacker\screate.sys D:
device =C:\UTILITY\386MAX\386load.sys size=63216 prgreg=2 flexframe prog=C:\UTILITY\STACKER\STACHIGH.SYS
device =C:\UTILITY\386MAX\386load.sys size=9072 flexframe prog=C:\DOS\ANSI.SYS
device =C:\UTILITY\386MAX\386load.sys size=13856 flexframe prog=C:\SBCD\SBCD.SYS /D:MSCD001 /P:250 /T:2 /S:A0

[No_Win]
Device=c:\utility\386max\386max.sys pro=c:\utility\386max\386max.pro
device =C:\UTILITY\386MAX\386load.sys size=11504 flexframe prog=C:\DOS\SETVER.EXE
DEVICE=C:\UTILITY\386MAX\386load.sys size=5888 flexframe prog=C:\DOS\ramdrive.sys 2048/E
device=c:\utility\stacker\screate.sys D:
device =C:\UTILITY\386MAX\386load.sys size=63216 prgreg=2 flexframe prog=C:\UTILITY\STACKER\STACHIGH.SYS
device =C:\UTILITY\386MAX\386load.sys size=9072 flexframe prog=C:\DOS\ANSI.SYS
device =C:\UTILITY\386MAX\386load.sys size=13856 flexframe prog=C:\SBCD\SBCD.SYS /D:MSCD001 /P:250 /T:2 /S:A0

[Kidpix]
Device=c:\utility\386max\386max.sys pro=c:\utility\386max\386max.pro
device =C:\UTILITY\386MAX\386load.sys size=11504 flexframe prog=C:\DOS\SETVER.EXE
DEVICE=C:\UTILITY\386MAX\386load.sys size=5888 flexframe prog=C:\DOS\ramdrive.sys 2048/E
device=c:\utility\stacker\screate.sys D:
device =C:\UTILITY\386MAX\386load.sys size=63216 prgreg=2 flexframe prog=C:\UTILITY\STACKER\STACHIGH.SYS
device =C:\UTILITY\386MAX\386load.sys size=9072 flexframe prog=C:\DOS\ANSI.SYS
device =C:\UTILITY\386MAX\386load.sys size=13856 flexframe prog=C:\SBCD\SBCD.SYS /D:MSCD001 /P:250 /T:2 /S:A0

[common]

[Win]
REM MAXIMIZE: ExtraDOS must come at the end of CONFIG.SYS
Device=C:\UTILITY\386MAX\ExtraDOS.max pro=C:\UTILITY\386MAX\ExtraDOS.PRO
Install=C:\UTILITY\386MAX\ExtraDOS.max


It's the 5th line in the [WIN] section that causes 386MAX to crash!!!  (The
STACHIGH.SYS driver.)  When loaded without BLUEMAX, the STACHIGH command
just locks up the computer.  Here is my STACKER.INI file:


/DIR=C:\UTILITY\STACKER\
/rp=2
/P=1
/sw = DF
C:\STACVOL.DSK,SW
C:\STACVOL.000,NS
D:\STACVOL.DSK,RP

HHHHHHHHHEEEEEEEEEEEELLLLLLLLLLLLLLLPPPPPPPPPPPP!!!!!!!!!!!!!!!

There is 1 Reply.

#: 40876 S4/Stacker 3.1
    30-Nov-93  18:47:42
Sb: #40631-#STACHIGH locks system
Fm: Stac Electronics 75300,2755
To: Gary Pickavet 75410,122 (X)

Gary,

>After a LOT of dinking around, I FINALLY got >this setup to work.  Now, for no
apparent reason, I turned my machine on >this morning and STACHIGH just locks
up my computer whenever it runs!!!

Well, somehting must have been changes.  try loading the RAM drives after
Stachigh.sys in the config.sys   If this doesn't help, drop the 386 info from
the Stachigh line and rerun Maxamize.  It may need to resize the driver.

Keith Dunlea, Stac Tech Support

There are 2 Replies.

#: 40943 S4/Stacker 3.1
    30-Nov-93  20:42:29
Sb: #40876-STACHIGH locks system
Fm: Gary Pickavet 75410,122
To: Stac Electronics 75300,2755 (X)

Keith,

I don't want to clog up the CIS BBS but I received your note after I sent
one to Edward about the STACHIGH.SYS problem.  To recap, I have simplified
my CONFIG.SYS file to the minimum commands to duplicate the problem.
STACHIGH.SYS crashes the system in exactly 4 commands.  No message is
displayed from STACHIGH.SYS and if I don't load it, the system performs
absolutely fine (EXCEPT I lose quite a bit of conventional memory which is
why I need to get this problem fixed.)  When DOS gets to the STACHIGH.SYS
line, the Hard Disk light flashes for about 2 seconds and the system locks
up tighter than a drum--requiring either a CTRL-ALT-DEL or push of the reset
button.

I haven't backup up the files and convered to the diskcompression program
that comes with DOS 6.2, I haven't wanted to.  But this problem is extremely
frustrating and has been very time consuming.  I've gotten notes from other
on CIS that have the same problem with STACHIGH.SYS locking their system.
We now have 2 machines that will lock on the STACHIGH.SYS command
execution--both Gateway 486/66 with 16M memory and MS-DOS 6.2.

Help IS appreciated!@!!

Here is my CONFIG.SYS file (with some annotation):


[menu]
menuitem=Net, Start the network
menuitem=No_Net, Do not start the network
menuitem=CD_ROM, Run CD Rom Programs
menucolor=15,1
menudefault=Net, 10
[common]

Device=c:\dos\himem.sys
device=c:\dos\emm386.exe ram
device=c:\utility\stacker\stachigh.sys  <--- CONFIG.SYS LOCKS UP HERE

BUFFERS=10,0
FILES=80
FCBS=20,0
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /E:900 /p
DOS=HIGH
LASTDRIVE=Q
REM device=d:\ramdrive.sys 1024 /a
switches=/k
[No_Net]
[Net]
DEVICE=C:\DOS\SETVER.EXE
DEVICE=C:\GRAPHICS\NEC\MVSOUND.SYS D:3 Q:7 T:1
DEVICE=C:\GRAPHICS\NEC\NECCDR.SYS /D:NECCD
DEVICE=C:\GRAPHICS\NEC\SNDBK12.SYS 1 7 220 2
Stacks=0,0
[CD_ROM]

[common]

HERE IS MY STACKER.INI file:

/DIR=C:\UTILITY\STACKER\
/P=1
/SW DE
c:\stacvol.dsk,SW
c:\stacvol.000,NS


#: 40948 S4/Stacker 3.1
    30-Nov-93  21:06:58
Sb: #40876-#STACHIGH locks system
Fm: Gary Pickavet 75410,122
To: Stac Electronics 75300,2755 (X)

Keith,

By moving STACHIGH to the bottom of my CONFIG.SYS file (see earlier posting),
instead of locking up the system, my system now does a reboot.  By moving the
STACHIGH.SYS command up in the CONFIG.SYS file a little further, I got this
message when STACHIGH.SYS ran:

"EMM386 has detected error #12 in an application at memory address 0000:0005.
To minimize the chance of data loss, EMM386 has halted your computer."

I copied STACHIGH from my factory Stacker 3.1 disk to my hard disk with no
luck.  I also changed the STACKS 0,0 command to STACKS 18,512 with no
improvement in the results.

Gary




There are 2 Replies.

#: 41048 S4/Stacker 3.1
    01-Dec-93  19:01:26
Sb: #40948-STACHIGH locks system
Fm: Roger Hicks 74250,1407
To: Gary Pickavet 75410,122 (X)

Gary;


What happens if you remark out your emm386 line. Does stachigh load then?

Thanks,

Keith Moon
STAC Product Support

#: 41171 S4/Stacker 3.1
    02-Dec-93  19:00:13
Sb: #40948-#STACHIGH locks system
Fm: Stac Electronics 75300,2755
To: Gary Pickavet 75410,122 (X)

Gary,

This is the frist report of such error. Surprised to see your firends did
report this to us.  Are they too running on a Gateway machine ?

The other issue is that Stachigh.sys is not using Emm386 without the DEVICEHIGH
command.  Do we have the correct config.sys ?   What happens if you REMark out
the himem.sys and emm386 line ?  These files may be damaged. LEt me know the
results.



Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41209 S4/Stacker 3.1
    03-Dec-93  03:11:03
Sb: #41171-#STACHIGH locks system
Fm: Gary Pickavet 75410,122
To: Stac Electronics 75300,2755 (X)

Keith,

I ended up spending 1 1/2 hours with tech support on the phone.  We've
determined that although it is an interaction with memory managers, it is
either a problem with STACHIGH or the way the Gateway 486/66 uses memory. I'm
being sent a maintenance release of STACHIGH to try.  I backward installed DOS
6.0 and that didn't help.  You have my actual and real CONFIG.SYS (and
STACKER.INI file).  I have two Stacker volumes.  If I use the semicolon to
comment out one of the volumes, STACHIGH loads just fine. Tech support (Sam I
think was his name) indicated that each stacker volume adds another 3K to the
footprint what STACHIGH moves.  So, it seems that it is a problem moving
whatever is moved by STACHIGH.  So it becomes a trade off between having 2
Stacker volumes or using STACHIGH to recover conventional memory (which I
desparately need so I can run network drivers.)

The two machines we are having the problems on so far ARE both Gateway 486/66
local bus video machines with 16M and ATI Graphics Ultra Pro video cards.

STACHIGH crashes whether I use EMM386 and HIMEM or 386MAX's version 7 so it
doesn't seem to be corupt files.  Tech support had me reinstall the key STACKER
files from the factory disk with no luck.

So, I am very frustrated but hopefully the new version of STACHIGH will do the
trick.

Thanks.. If you have any more ideas, I'm all ears.

Gary


There is 1 Reply.

#: 41243 S4/Stacker 3.1
    03-Dec-93  13:42:14
Sb: #41209-#STACHIGH locks system
Fm: Stac Electronics 75300,2755
To: Gary Pickavet 75410,122 (X)

Gary,

According to your Config file you sent, Stachigh.sys is not getting loaded. It
must have DEVICEHIGH or The 386MAX driver lines in front of it. Whta happens if
you remark our the memory manager ?

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41321 S4/Stacker 3.1
    04-Dec-93  18:52:56
Sb: #41243-STACHIGH locks system
Fm: Gary Pickavet 75410,122
To: Stac Electronics 75300,2755 (X)

Keith,

If I sent you a CONFIG.SYS without STACHIGH.SYS loading, it's because I'd used
"REM" to keep it from loading since it locks the system.  I haven't tried
loading StacHIGH.SYS without ANY memory manager.  I'll try it and let you know
what happens.

Gary


#: 40634 S4/Stacker 3.1
    27-Nov-93  14:28:27
Sb: # Gateway Colorbook Again
Fm: Fred Pitzner 71570,3522
To: STAC Electronics 75300,2755 (X)

11/27/93
Sending this again - had to leave town right after sent this before 11/7 -
hoped to have a reply when I returned, BUT none showed.

Perhaps too much time elapsed.  Please respond.
-----------------
11/7/93
Tried to stack my new Gateway 2000 Colorbook 486/33 DX. 170 meg. drive.

Custom method

Got to point where your screen said "Choose Stack to begin stacking"

BUT, everything froze.  Couldn't exit, esc, ctl break, ctl alt del, and even
the power off switch wouldn't work.

Had to pull the plug on the power cable, but with the battery, the machine kept
running.  Today, will remove battery to shut down the computer.  Assume I may
have wiped myself out.

ANY thoughts on what is going on - why this happened?

This surely has caused me a major inconvenience.

Very Frustrated.

Fred Pitzner
  

There is 1 Reply.

#: 40877 S4/Stacker 3.1
    30-Nov-93  18:47:44
Sb: #40634- Gateway Colorbook Again
Fm: Stac Electronics 75300,2755
To: Fred Pitzner 71570,3522

Fred,

Reboot and hold F5 to bypass the config/autoexec and retry the Stacker install
from DOS.  Let me know if this doesn't help

Keith Dunlea, Stac Tech Support

#: 40641 S4/Stacker 3.1
    27-Nov-93  19:24:13
Sb: #62stac.exe
Fm: charles mims 71162,3475
To: sysop (X)

When I run 62stac.exe I get two files stac62.exe and stac62.txt.  I do not make
before62.exe or after62.exe.

There is 1 Reply.

#: 40879 S4/Stacker 3.1
    30-Nov-93  18:47:50
Sb: #40641-62stac.exe
Fm: Stac Electronics 75300,2755
To: charles mims 71162,3475 (X)

Charles,

The files has been updated.  Please re-download 62STAC.EXE

Keith Dunlea, Stac Tech Support

#: 40645 S4/Stacker 3.1
    27-Nov-93  20:19:16
Sb: #DOS 5/Stac 2 to 6.0/3.1
Fm: Bill Jones Jr. 70451,1202
To: All

I'm currently at DOS 5.0 and Stacker 2.0 on a 2 drive Windows 386/33 system,
both drives stacked.  I want to go to DOS 6 and Stacker 3.1, so I naturally
went out and got MS-DOS 6.0 and the Stacker 3.1 upgrades.

Rumour has it that upgrading to Stacker 3.1 makes the DOS 6 upgrade a snap.
Made sense to me, given the hassels with DOS 5 and Stacker upgrades.

Not with what I got.  Stacker 3.1 won't load with DOS 5.  Seems I oughta check
before I turn MS loose in a Stacker system.  So here I am.  Calling for help.

Questions of the day: How do I get from DOS 5.0 and Stacker 2.0 to DOS 6.0 and
Stacker 3.1?  Should I go on up to DOS 6.2 and skip 6.0 altogether?

TIA.  Bye Y'all.  BJjr

There is 1 Reply.

#: 40696 S4/Stacker 3.1
    28-Nov-93  23:28:15
Sb: #40645-DOS 5/Stac 2 to 6.0/3.1
Fm: Ron  DEau Claire 71644,201
To: Bill Jones Jr. 70451,1202 (X)

Bill, I believe Stacker 3.1 works _only_  with DOS 6.0 or 6.2.  I upgraded my
system from DOS 6.0 to DOS 6.2, then installed Stacker 3.0 and later upgraded
to  Stacker 3.1 on my 500 Meg drive. Works like a champ!

#: 40652 S4/Stacker 3.1
    27-Nov-93  22:01:09
Sb: #Stacker 2.0 to 3.1.
Fm: Craig A. Daniels 71551,3057
To: Technical Support

I purchased a Stacker Upgrade from you for 2.0 (with a board) to release 3.1.
First off I ONLY receive ONLY the upgrade disettes and information on how to do
the install, NO manual.  Don't I get a manual with the upgrade?

Having to do a backup before the upgrade I let it slide for several weeks.  At
the same time I also decided to do MS-DOS 6.0 to 6.2 which I had just
downloaded from MS.  Tried the upgrade, but it said I didn't have sufficient
room on my D drive, my non-stacked drive.  I then gave up on the 6.2 upgrade.

I then proceeded with the Stacker 3.1 upgrade.  There were no problems with the
upgrade.

I then tried to Re-Stack my C drive.  I started the re-stack from the Windows
menu and it ran for about 45 minutes and completed about 67% of the C drive
when I received a fatal error.  The message to follow something like this:
  demout the C drive
  issue an ATTRIBUTE command
  run a utility to fix the error
  issue the opposite ATTRIBUTE command
  remount the C drive
Then it said refer to the 3.1 manual.

I tried this, but it never accepted the 1st ATTRIBUTE command; I finally
rebooted.

The system came up, but since then I'm experiencing intermitent hangs,
particularly in running DOS applications from Windows.

My questions:
  1.  Do I get a manual when upgrading from release 2.0 to 3.1?
  2.  What was the error that occured when I was re-stacking?
  3.  Should I triy to re-stack again?
  4.  How can I increase the size of my D drive to upgrade DOS 6.0 to 6.2?  

There is 1 Reply.

#: 40885 S4/Stacker 3.1
    30-Nov-93  18:48:12
Sb: #40652-Stacker 2.0 to 3.1.
Fm: Stac Electronics 75300,2755
To: Craig A. Daniels 71551,3057 (X)

Craig,

>  1.  Do I get a manual when upgrading from release 2.0 to 3.1? Yes.  If your
missing one just call Stac Sales at 800-522-7822

>  2.  What was the error that occured when I was re-stacking? Good question,
what was the error message and number ?

>  3.  Should I triy to re-stack again? Yes.  If you get an error write it down
and post it here.

>  4.  How can I increase the size of my D drive to upgrade DOS 6.0 to 6.2?

Run Sdefrag /GP to make more uncomrpessed space.  I believe DOS 6.2 needs 600k
on the host boot drive

Keith Dunlea, Stac Tech Support

#: 40656 S4/Stacker 3.1
    28-Nov-93  05:09:19
Sb: #space???
Fm: Christopher Ponder 70254,44
To: all

I have installed Stacker 3.1.  Before Stacker I had 2 drives - C: 202meg and D:
202meg.  I am leaving drive C: uncompressed.  Drive D: was backed up,
repartitioned as D: and E: with 100meg and 102 meg respectifully.

Before restoring, I stacked drive D: then drive E:.  I was thinking that I
would get 200 meg out of each logical drive (D: and E:).  Instead, after
restoring, I have only about 85 megs more than before I repartitioned and
stacked.

In other words, I was expection 400 meg out of the 200 meg hard drive.

Also, what can I do about getting some of the conventional ram back?  In case
there is nothing I can do about lowering the amount of ram used - what can I do
when a game says "You must free up more memory to load this game".  Can I do
anything about the 50 or so k that I am giving to stacker.

                        Thanks,
                        Chris......

There is 1 Reply.

#: 40888 S4/Stacker 3.1
    30-Nov-93  18:48:24
Sb: #40656-space???
Fm: Stac Electronics 75300,2755
To: Christopher Ponder 70254,44 (X)

Chris,

 you can load Stacker high using your memory manager.  see tech notes 2101.txt
- 2106.txt

Space reporting on a Stacker drive depends on your drive compression ratio.
During install the drive is created with an expected compression of 2.0-1.  If
the data stored on the drive has an overall compression ratio of less than
2.0-1 it will occupy more compressed space than originally anticipated.  Use
CHECK or SCHECK and DIR to accuratley report fee space.

see TECH NOTE 2602.txt in lib:3 for more details

Keith Dunlea, Stac Tech Support

#: 40657 S4/Stacker 3.1
    28-Nov-93  05:43:05
Sb: #Emergency with stacvol.
Fm: DANIEL KATZ 71773,3571
To: Sysop, All (X)

THIS IS AN EMERGENCY!!!!!!! Yesterday I ran stacker on my 340MB HD.  After it
finished I pressed esc on the defragmentation thinking I could do it later.
When it rebooted stacvol.dsk was not mounted because of to much fragmentation.
I have put some files from disks onto the root which was left with 1.5MB free,
like a dumb communication program, to speak to somone. It is the only thing I
have access to right now.  I do not know what to do.  I cannot run Sdefrag or
Norton SD because my stack disk isn't mounted and stacvol is all in hidden
sectors. I am right now outside the US traveling in Israel, but I really need
my computer, if you think you can help leave me your number and I'll call you.
Again Stacvol.dsk is in perfect condition but to fragmented to be mounted.
Please get back to me ASAP.  Thank's for reading this.

         --Daniel exit

There is 1 Reply.

#: 40889 S4/Stacker 3.1
    30-Nov-93  18:48:28
Sb: #40657-Emergency with stacvol.
Fm: Stac Electronics 75300,2755
To: DANIEL KATZ 71773,3571 (X)

Daniel,

Since the stacvol file was is fragmented you need to do the following

1.  remove the files which you just added 2.  from the stacker install diskette
type
        c:\dos\attrib -h -r -s c:\stacvol.dsk   ; to unhide the file.
        create c:\stacvol.dsk /p                ; defrag file 3.  Upon
completion reboot to mount your Stacker drive

Keith Dunlea, Stac Tech Support

#: 40659 S4/Stacker 3.1
    28-Nov-93  08:39:26
Sb: #Configure Smartdrv
Fm: William Semple 76340,2465
To: Syscon

I have the typical setup: DOS 6.2., Win 3.1, Stacker 3.1, no ramdrive. Two
floppies A&B. All on a ZEOS 66DX2. Right now, smartdrive seems to be read
caching Drives A, B, and F(the CD-ROM). It is read-writing Drive D, the
uncompressed drive.

It doesn't seem to be doing anything with the Stacker Vol drive E. Both the DOS
Smartdrv and Win SmartMon show that the E drive is not being cached. Why not?
Shouldn't I cache the Stacker Vol. Wouldn't I get increased performance? Since
I load Smartdrive without any switches or drive indications, why doesn't it
default to drive E? Finally, any suggestions how to write the autoexec.bat
entry?

There is 1 Reply.

#: 40891 S4/Stacker 3.1
    30-Nov-93  18:48:33
Sb: #40659-Configure Smartdrv
Fm: Stac Electronics 75300,2755
To: William Semple 76340,2465

William,

see tech note 2401.txt on using disk cache with Stacker. Basically, disk cache
only need to read the drive which contains the Stacvol file

Keith Dunlea, Stac Tech Support

#: 40666 S4/Stacker 3.1
    28-Nov-93  12:29:49
Sb: #CD ROM STACKER & VIDEO
Fm: EDWARD B. SPERLING 76010,2067
To: SYSOPS (X)

I tried stacking my C drive where my multimeda apps are located and I noticed
a slight slow down in the frames being played by various AVI formats.
Is stacker the cause?  Do you have any suggestions?  It doesn't happen
when my C drive is not stacked.
PLEASE HELP
ED

There is 1 Reply.

#: 40893 S4/Stacker 3.1
    30-Nov-93  18:48:40
Sb: #40666-CD ROM STACKER & VIDEO
Fm: Stac Electronics 75300,2755
To: EDWARD B. SPERLING 76010,2067 (X)

Edward,

Stacker would not affect AVI files.  I run them on my compressed drive without
any performance decrease. Try booting with just Stacker and himem.sys loaded.
This will test for a tsr conflict

Keith Dunlea, Stac Tech Support

#: 40667 S4/Stacker 3.1
    28-Nov-93  12:32:45
Sb: #MYM AND RE DIRECT
Fm: EDWARD B. SPERLING 76010,2067
To: SYSOPS (X)

Is there a new version of Stac to correct the problem outlined below?...ED
Subj:  STACKER REDIRECT                 Section: MYM 10 - Other From:  EDWARD
B. SPERLING, 76010,2067 #94466   To:  SYSOPS
Thursday, November 25, 1993 9:35:40 PM

Hi
In MYM V9.0   if you had Stacker on your disk MYM would lockup until
you edited the Stacker ini file by putting a "redirect" command in the file.
Do you still have to do this in version 10?
PLEAS ADVISE
ED

There is 1 Reply.

#: 40894 S4/Stacker 3.1
    30-Nov-93  18:48:44
Sb: #40667-MYM AND RE DIRECT
Fm: Stac Electronics 75300,2755
To: EDWARD B. SPERLING 76010,2067 (X)

Edward,

When using MYM with Stacker 3.1 you need to disable the command interceptor in
the Stacker.ini file and renable it in the autoexec.bat.

1.  edit the Stacker.ini file (see 3.1 readme) and add
    /i- 2.  add C:\STACKER\REDIRECT.COM to your autoexec.bat

Keith Dunlea, Stac Tech Support

#: 40668 S4/Stacker 3.1
    28-Nov-93  12:41:12
Sb: #Insufficient Memory msg
Fm: Richard Emery 72571,3110
To: All

All,

I am unable to run FoxPro for Windows due to insufficient memory.
I've included my CONFIG.SYS, AUTOEXEC.BAT, CONFIG.FPW, and output
from "mem /s".

I used to run FoxPro with DoubleSpace and SMARTDRV active.  After
these programs (one or both) clobbered several drive directories,
I performed an FDISK on the drive, and installed Stacker to do my
data compression.

My configuration is:
 Compudyne 386DX/33Mhz, 4 meg RAM
 Mouse Systems Mouse (using Windows own MS driver)
 121 Meg hard drive

Any help you all can give me will be greatly appreciated.

rick
-------------------------------------------------------------------
**** config.sys ****
[menu]
menuitem=NoEMS386, No EMS386.SYS (Windows)
menuitem=EMS386, Load EMS386.SYS
menuitem=Windows, Load Windows
menudefault=NoEMS386,5

[common]
DEVICE=C:\DOS\HIMEM.SYS

[NoEMS386]

[Windows]

[EMS386]
DEVICE=C:\DOS\EMM386.EXE RAM HIGHSCAN

[common]
BUFFERS=8,0
FILES=40
LASTDRIVE=H
FCBS=4,0
DEVICEHIGH /L:1,12048 =C:\DOS\SETVER.EXE
DOS=HIGH,UMB
BREAK=ON
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /E:256 /p
DEVICEHIGH /L:1,9072 =C:\DOS\ANSI.SYS /X
rem INSTALL=C:\DOS\FASTOPEN.EXE C:=(150,150)
numlock=OFF
DEVICEHIGH=c:\util\mscmouse.sys /c1
DEVICEHIGH=C:\STACKER\STACHIGH.SYS
STACKS=9,256

**** autoexec.bat ****
@ECHO OFF
rem C:\SMARTDRV.EXE a- b- 0
SET PCPLUS=C:\COMM\
REM  THE "CHECK" LINE BELOW PROVIDES ADDITIONAL SAFETY FOR STACKER DRIVES.
REM  PLEASE DO NOT REMOVE IT.
C:\STACKER\CHECK /WP
SET COMSPEC=c:\COMMAND.COM
set PATH=c:;c:\dos;c:\util;c:\bat;c:\windows;c:\games\bat;C:\bc\bin;C:\STACKER;
set PROMPT=[1;37;44m*[1;37;41mss[40;30;36m $p$g [0m
set TEMP=C:\TEMP
SET BLASTER=A220 I7 D1 T4
VERIFY OFF
pushd .
popd
goto %config%

:NoEMS386
goto end

:Windows
win
goto end

:EMS386
:end
echo on

**** \foxprow\config.fpw ****
MEMLIMIT = 80,1024,4096
KEYCOMP = WINDOWS

**** mem /s ****
Modules using memory below 1 MB:

  Name           Total       =          Conventional   +   Upper Memory
  --------  ----------------                     ----------------
----------------
  MSDOS        15325   (15K)      15325   (15K)       0    (0K)
  HIMEM          1168    (1K)       1168    (1K)          0    (0K)
  SETVER          784    (1K)        784    (1K)           0    (0K)
  ANSI             4208    (4K)       4208    (4K)          0    (0K)
  STACHIGH   91808   (90K)      91808   (90K)       0    (0K)
  COMMAND     3056    (3K)       3056    (3K)         0    (0K)
  PUSHD          1296    (1K)       1296    (1K)         0    (0K)
  WIN              2288    (2K)       2288    (2K)         0    (0K)
  win386          3008    (3K)       3008    (3K)         0    (0K)
  COMMAND     3184    (3K)       3184    (3K)        0    (0K)
  Free           529024  (517K) 529024  (517K)       0    (0K)

Memory Summary:

  Type of Memory          Total       =       Used        +       Free
  ----------------             -----------------   -----------------
-----------------
  Conventional        655360        (640K)       126336   (123K)      529024
(517K)
  Upper                           0            (0K)                 0     (0K)
0      (0K)
  Adapter RAM/ROM     393216   (384K)       393216   (384K)              0
(0K)
  Extended (XMS)     3145728    (3072K)    2203648  (2152K)     942080   (920K)
  ----------------  -----------------   -----------------   -----------------
  Total memory       4194304      (4096K)    2723200  (2659K)    1471104
(1437K)

  Total under 1 MB    655360       (640K)       126336   (123K)      529024
(517K)

  Total Expanded (EMS)                     1048576  (1024K)
  Free Expanded (EMS)                        933888   (912K)
  Largest executable program size         529008   (517K)
  Largest free upper memory block              0     (0K)
  MS-DOS is resident in the high memory area.

There is 1 Reply.

#: 40895 S4/Stacker 3.1
    30-Nov-93  18:48:47
Sb: #40668-#Insufficient Memory msg
Fm: Stac Electronics 75300,2755
To: Richard Emery 72571,3110 (X)

Richard,

It appears you only have 517k free of lower ram.  Is this enough to run Foxpro
?   Make sure all your drivers are getting loaded high.  If running DOS 6 then
try using MemMaker

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40941 S4/Stacker 3.1
    30-Nov-93  20:31:40
Sb: #40895-Insufficient Memory msg
Fm: Richard Emery 72571,3110
To: Stac Electronics 75300,2755 (X)

Keith,
I'm not sure what FoxPro needs in conventional memory.  I do load all my
drivers high.  Without EMM386.SYS running
(because it appears that what Windows requires), I chew up a LOT of
conventional memory.  Over on the FoxForum,
the Microsoft tech rep suggested I load nothing high.  I'll try it both ways
and pass the results on.

Meanwhile, I'll ask the MS guy how much convential memory FoxPro needs.  That's
a darn good question.

rick

#: 40679 S4/Stacker 3.1
    28-Nov-93  14:32:28
Sb: #Stacker and 2 Hardcards
Fm: John Kevan 71554,2141
To: Edward Nutter 75330,2222 (X)

I have 2 hard cards I am trying to stac.  I downloaded the text that explained
how to fix the problems with them not loading but was only able to get one of
them to be recognized on boot up.  The second hard card I have to manually add
everytime.  Do you have any suggestions on how to fix.


John

There are 2 Replies.

#: 40715 S4/Stacker 3.1
    29-Nov-93  17:06:51
Sb: #40679-Stacker and 2 Hardcards
Fm: Edward Nutter [Stac] 75330,2222
To: John Kevan 71554,2141 (X)

John,

I'll have some suggestions if you'll provide some more information.

Change to the Stacker directory and run...
SYSINFO /S /H

This will generate a file named SYSINFO.TXT.  Include SYSINFO.TXT in your reply
to this message and we should be able to indicate some specific configuration
changes.

Edward Nutter
Stac Electronics Product Support 

#: 40779 S4/Stacker 3.1
    29-Nov-93  20:43:48
Sb: #40679-#Stacker and 2 Hardcards
Fm: Edward Nutter [Stac] 75330,2222
To: John Kevan 71554,2141 (X)

John,

Please run SYSINFO /S /H

Include the SYSINFO.TXT that gets generated by that command into your reply to
this.

Edward Nutter
Stac Electronics Product Support

There is 1 Reply.

#: 40976 S4/Stacker 3.1
    01-Dec-93  08:15:57
Sb: #40779-#Stacker and 2 Hardcards
Fm: John Kevan 71554,2141
To: Edward Nutter [Stac] 75330,2222 (X)

Edward

I will be sending 3 additional pieces to this.  I'm not sure how much you
really needed.
Mail 1-(This message) The messages I received when I use the Drive Integrity
option to fix the problem each time it occures.
Mail 2-Using "sysinfo /s /h" before the drive is stacked
Mail 3-Using "sysinfo /s /h" after the drive is stacked but not fixing it with
the               drive integrity option.
Mail 4-Using "sysinfo /s /h" after the drive is stacked and after fixing it
with the            drive integrity option.

As of this point, I do not have the drive stacked because I do not want to take
the chance of loosing data on it.

John

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Mail 1
"The following is what I got when I first rebooted after stacking the d:
hardcard."


CHECK - 3.10, (c) Copyright 1990-93 Stac Electronics, Carlsbad, CA

Volume in drive D is STACVOL_DSK

Error Summary:

                 Free sector count invalid
                 Erased sector count invalid
                 Sector allocation map signature not valid
                 Sector allocation map not valid
               2 Sectors which should be allocated but are not
                 Volume mounted read only

Repair drive D? ["yes"/no]: yes

       2 Errors corrected
Write protection removed from drive D:


Projected Bytes Free            = 207,863,808

===============================================================
"I then started getting the following after I fixed it above and soft booted"


CHECK - 3.10, (c) Copyright 1990-93 Stac Electronics, Carlsbad, CA

Volume in drive D is STACVOL_DSK

No errors found
Write protection removed from drive D:


Projected Bytes Free            = 207,863,808

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

There is 1 Reply.

#: 40989 S4/Stacker 3.1
    01-Dec-93  13:35:47
Sb: #40976-#Stacker and 2 Hardcards
Fm: Edward Nutter [Stac] 75330,2222
To: John Kevan 71554,2141 (X)

John,

DOS 6.2 changes some rules about how things work at boot time.  Your #2
config.sys looked like...

DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS x=c000-c9ff x=d400-d7ff
DOS=HIGH,UMB
BUFFERS=10,0
FILES=30
LASTDRIVE=K
FCBS=16,8
DEVICEHIGH /L:1,18864 =C:\NDW\NAV&.SYS /B
DEVICEHIGH /L:1,12048 =C:\DOS\SETVER.EXE
rem DEVICE=C:\DOS\EMM386.EXE NOEMS x=c000-c9ff x=d400-d7ff X=C900-C9FF
X=CB00-CBFF
rem DEVICE=C:\DOS\EMM386.EXE NOEMS X=C000-C9FF
rem DEVICE=C:\DOS\EMM386.EXE NOEMS X=C000-CFFF
DEVICEHIGH=ATDOSXL.SYS
DEVICEHIGH /L:1,5888 =C:\DOS\RAMDRIVE.SYS 3060 /E
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /E:512 /p
DEVICEHIGH /L:1,9072 =C:\DOS\ANSI.SYS
DEVICEHIGH /L:2,16880 =C:\SUPPORT\HIGH_RES.SYS /M:03 /BIOS
STACKS=9,256
DEVICEhigh=C:\STACKER\STACHIGH.SYS
REM DEVICE=C:\STACKER\STACKER.COM /P=1 C:\STACVOL.000
DEVICE=G:\DESKSCAN\SJDRIVER.SYS

Do this...

DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS x=c000-c9ff x=d400-d7ff
DOS=HIGH,UMB
BUFFERS=10,0
FILES=30
LASTDRIVE=K
FCBS=16,8
DEVICEHIGH=ATDOSXL.SYS  <-- to here
------------------------------------------------<
DEVICEHIGH /L:1,18864 =C:\NDW\NAV&.SYS /B
|
DEVICEHIGH /L:1,12048 =C:\DOS\SETVER.EXE
|
rem DEVICE=C:\DOS\EMM386.EXE NOEMS x=c000-c9ff x=d400-d7ff X=C900-C9FF
X=CB00-CBFF  |
rem DEVICE=C:\DOS\EMM386.EXE NOEMS X=C000-C9FF
|
rem DEVICE=C:\DOS\EMM386.EXE NOEMS X=C000-CFFF
|
    <move the hardcard driver from
here>--------------------------------------------^
DEVICEHIGH /L:1,5888 =C:\DOS\RAMDRIVE.SYS 3060 /E
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /E:512 /p
DEVICEHIGH /L:1,9072 =C:\DOS\ANSI.SYS
DEVICEHIGH /L:2,16880 =C:\SUPPORT\HIGH_RES.SYS /M:03 /BIOS
STACKS=9,256
DEVICEhigh=C:\STACKER\STACHIGH.SYS
REM DEVICE=C:\STACKER\STACKER.COM /P=1 C:\STACVOL.000
DEVICE=G:\DESKSCAN\SJDRIVER.SYS

If the hardcard drive is one of the first four "device=" lines the problem
should go away.

Edward Nutter
Stac Electronics Product Support 

There is 1 Reply.

#: 41218 S4/Stacker 3.1
    03-Dec-93  10:10:18
Sb: #40989-#Stacker and 2 Hardcards
Fm: John Kevan 71554,2141
To: Edward Nutter [Stac] 75330,2222 (X)

Ed

I tried the fix you suggested.  I am still getting write errors everytime I
boot up on the D drive and have to go in and use the drive integrity option to
load the drive.
The second hard card (E drive) still loads fine everytime and the compressed
portion of my C drive (ie. G drive) work fine everytime also.  It's only when I
try to compress and use the first hard card (D drive).

Any other suggestions?

John

There is 1 Reply.

#: 41230 S4/Stacker 3.1
    03-Dec-93  12:28:31
Sb: #41218-#Stacker and 2 Hardcards
Fm: Edward Nutter [Stac] 75330,2222
To: John Kevan 71554,2141 (X)

John,

Try...

DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS x=c000-c9ff x=d400-d7ff
DOS=HIGH,UMB
DEVICEHIGH=ATDOSXL.SYS  <--<moveing the hardcard drive to here >
BUFFERS=10,0
FILES=30
LASTDRIVE=K
FCBS=16,8

With DOS 6.2 and Stacker 3.1 you'll have to keep the HardCard driver within the
first lines of the config.sys.

Edward Nutter
Stac Electronics Product Support 

There is 1 Reply.

#: 41389 S4/Stacker 3.1
    06-Dec-93  19:04:55
Sb: #41230-Stacker and 2 Hardcards
Fm: John Kevan 71554,2141
To: Edward Nutter [Stac] 75330,2222

Ed

No luck, I still get the same write error on the second (or first hard card
depedending on how you look at it)  Any other suggestions.

John

#: 40680 S4/Stacker 3.1
    28-Nov-93  15:10:58
Sb: #Quantum Hardcard
Fm: John W. Sandilands 71773,2345
To: sysop (X)

Hi there,
        I understand there is a fix for Stacker 3.1 so it will recognize
Quantum Hardcards when the dblspace.bin driver is loaded and not until after
the atdosxl.sys driver is loaded for the hardcard. Who do I have to e-mail to
get a copy of this fix?
        Thanks in advance
        Wade

There is 1 Reply.

#: 40900 S4/Stacker 3.1
    30-Nov-93  18:49:05
Sb: #40680-Quantum Hardcard
Fm: Stac Electronics 75300,2755
To: John W. Sandilands 71773,2345 (X)

John,

the update 3.1 files are to eliminate the "write protect" on a mounted
compressed hard card/  Are you getting this ?  If so, send Email to our account
[75300,2755] and include address, diskette size, daytime phone number and
stacker serial #.

thanks

Keith Dunlea, Stac Tech Support

#: 40683 S4/Stacker 3.1
    28-Nov-93  16:07:58
Sb: #still got problem
Fm: Duane Austin 70272,2601
To: Keith Dunlea [Stac Tech]

I am still having trouble with "Error 109".  I have tried the procedure as
described in "STAC FAX #3405" and Norton 7/Diagnostics does not recofnize the
drive, while Norton Disk Doctor finds no errors in the "host test" but still
reports "Drive is write protected" and will not complete the analysis (of the
compressed stacvol, I presume).  I downloaded/installed at least one upgrade or
patch for Norton 7 -- I've installed so many upgrades and patches lately, I've
lost track.  Any more advice?

There is 1 Reply.

#: 41039 S4/Stacker 3.1
    01-Dec-93  18:18:00
Sb: #40683-still got problem
Fm: Stac Electronics 75300,2755
To: Duane Austin 70272,2601 (X)

Duane,

Ok, what is CHECK /F reporting when /R is added to the Stacker.ini file.  MAke
sure you reboot after adding /R then run CHECK /F. You should be running NU 7.1
their latest, also try a pattern test on the host drive to scan for errors.
If nothing  works download TECHSP.FRM from lib:1, fill it out and upload it to
lib:1 This is our engineer report

Keith Dunlea, Stac Tech Support

#: 40692 S4/Stacker 3.1
    28-Nov-93  22:45:41
Sb: #Lost Stacker Disk
Fm: Bruce J. Murdock 73260,3002
To: sysop (X)

Greetings,

        I can not find my stacker disk!  I tore my room apart twice to try and
find it.  I believe I sent in my registration, my memory is pretty sure about
this, but I am also sure that I can produce proof of purchase (reciept, etc.).
        Is it possible to get a new Stacker 3.1 disk?

                Going crazy,
                Bruce Murdock

There is 1 Reply.

#: 40905 S4/Stacker 3.1
    30-Nov-93  18:49:25
Sb: #40692-Lost Stacker Disk
Fm: Stac Electronics 75300,2755
To: Bruce J. Murdock 73260,3002 (X)

Bruce,

Please call Stac Customer services at 800-522-7822

Keith Dunlea, Stac Tech Support

#: 40694 S4/Stacker 3.1
    28-Nov-93  23:18:21
Sb: #stachigh and qemm
Fm: Amos Lakos 74020,143
To:  75300,2755 (X)

I restacked my drive, and at the end of the optimization, at the first reboot,
I received an Exception #13 message at D73B:0A30. I run Dos6.0, QEMM7.02, and
Stacker 3.1 W/D. QEMM manifest identified the problem as the stachigh area. The
line in the config.sys is: DEVICE=C:\QEMM\LOADHI.SYS /R:1 /SIZE=58864
C:\STACKER\STACHIGH.SYS The last line on the AUTOEXEC.BAT is: c:\mouse\mouse

I am new to both Stacker and QEMM.

Any ideas?


There are 2 Replies.

#: 40906 S4/Stacker 3.1
    30-Nov-93  18:49:30
Sb: #40694-stachigh and qemm
Fm: Stac Electronics 75300,2755
To: Amos Lakos 74020,143 (X)

Amos,

>DEVICE=C:\QEMM\LOADHI.SYS /R:1 /SIZE=58864 C:\STACKER\STACHIGH.SYS

drop the Qemm information

DEVICE=C:\STACKER\STACHIGH.SYS

and rerun Optimize.  It may need to resize the Stacker driver

Keith Dunlea, Stac Tech Support

#: 40972 S4/Stacker 3.1
    01-Dec-93  02:40:03
Sb: #40694-stachigh and qemm
Fm: Gary Pickavet 75410,122
To: Amos Lakos 74020,143

Amos,

I've had problems with STACHIGH.SYS for almost a week now.  It locks up my
system every time.  Then, I got an Exception #12 message.  I'll monitor your
messages here and see if you get your STACHIGH problem solved.  I hope you do.

Gary


#: 40698 S4/Stacker 3.1
    29-Nov-93  00:31:30
Sb: #DOS 6 and Stacker
Fm: William  Fleming 70303,1023
To: sysop (X)

Help -

I am currently using DOS 5 and Stacker 3.0, I an interested in upgrading to DOS
6.  I have a copy of Stacker 3.1 but I am a little confused, I can't load 3.1
until DOS 6 is installed but....is it safe to install DOS 6 while currently
running DOS 5 and Stacker 3.0?  Hope this process can be easy.

thx for any help - bill


There is 1 Reply.

#: 40909 S4/Stacker 3.1
    30-Nov-93  18:49:39
Sb: #40698-DOS 6 and Stacker
Fm: Stac Electronics 75300,2755
To: William  Fleming 70303,1023

Bill,

Stacker 3.0 works fine with DOS 6.x   Upgrade to OS first, then Stacker 3.1

Keith Dunlea, Stac Tech Support

#: 40707 S4/Stacker 3.1
    29-Nov-93  13:23:38
Sb: #BOOT ERROR?
Fm: Charles Eichhorn 70631,32
To: TECH SUPPORT

[A [A [A [A [A


[A



I am using Stacker 3.1 (upgrade) with DOS 6.0 and now 6.2. The problem seems to
be the same.  As the system is booting, I get the message: F:=C:STACVOL.DSK
Updating Stacker Allocation Map...ERROR complete)
  (run CHECK /F) (Write protected)
  Press any key to continue

I then run CHECK /F and after some time passes, the message is that there are
no errors.

This routine happens ALMOST  every boot. [D [D [D [D [D [D [D [D [D [D

[D [D [D [D [DSorry.  What gives?  Stacker created C: and G: stacked drives on
850mb drive C: Fragmentation is under 1%. [A/exit

[A [A [D [D



There is 1 Reply.

#: 40918 S4/Stacker 3.1
    30-Nov-93  18:50:10
Sb: #40707-#BOOT ERROR?
Fm: Stac Electronics 75300,2755
To: Charles Eichhorn 70631,32 (X)

Charles,

Stacker automaticaly runs CHECK at boot time from the autoexec.  by the time
you run it the error is cleared.

what else is loaded ?  any external devices like a hard card ?

Keith Dunlea, Stac Tech Support

There are 2 Replies.

#: 40955 S4/Stacker 3.1
    30-Nov-93  22:28:52
Sb: #40918-#BOOT ERROR?
Fm: Charles Eichhorn 70631,32
To: Stac Electronics 75300,2755 (X)

Hi Keith. The CONFIG has loaded CDROM drivers, ASPI driver for SCSI HD, etc.
The HD is not double buffered - didn't seem to need it. (UltraStor 34F VLB).
Want a whole list of the CONFIG?

There is 1 Reply.

#: 41049 S4/Stacker 3.1
    01-Dec-93  19:01:29
Sb: #40955-BOOT ERROR?
Fm: Roger Hicks 74250,1407
To: Charles Eichhorn 70631,32

Charles;

I don't see a problem with your config.sys file. I assisting Keith, what is
your problem.


Thanks,

Keith Moon
STAC Product

#: 40956 S4/Stacker 3.1
    30-Nov-93  22:34:40
Sb: #40918-#BOOT ERROR?
Fm: Charles Eichhorn 70631,32
To: Stac Electronics 75300,2755 (X)

Here's the CONFIG (if I can make this work):

DEVICE=C:\QEMM\DOSDATA.SYS DEVICE=C:\DOS\SETVER.EXE DEVICE=C:\QEMM\QEMM386.SYS
RAM ST:M R:3 XST=C000 X=A000-C7FF DEVICE=C:\QEMM\DOS-UP.SYS @C:\QEMM\DOS-UP.DAT
DEVICE=C:\QEMM\LOADHI.SYS /R:2 /SIZE=8592 C:\QEMM\QDPMI.
    SYS SWAPFILE=DPMI.SWP SWAPSIZE=1024 DOS=HIGH SHELL=C:\QEMM\LOADHI.COM /R:2
C:\DOS\COMMAND.COM C:\DOS\ /E:1024 /p DEVICE=C:\DOS\ULTRA\USPI14.SYS
DEVICE=C:\QEMM\LOADHI.SYS /R:2 /SIZE=15904 C:\DOS\ULTRA\ULTRACD.
   SYS /D:MSCD0001 rem DEVICE=C:\QEMM\LOADHI.SYS /R:2 C:\DOS\MOUSE\MOUSE.SYS SER
1 rem DEVICE=C:\ENCYCLO\SNDBK12.SYS 1 5 220 2 DEVICE=C:\STACKER\STACHIGH.SYS
FILES=50 STACKS=0,0 LASTDRIVE=K BUFFERS=10,0

Well, everything doubled for some reason (Stacker?) Just kidding. Whatcha
think?

There is 1 Reply.

#: 41172 S4/Stacker 3.1
    02-Dec-93  19:00:17
Sb: #40956-BOOT ERROR?
Fm: Stac Electronics 75300,2755
To: Charles Eichhorn 70631,32

Charles,

your files look fine.  the lost clusters is a DOS error.  Usually caused by a
files left open when the machine is rebooted.

As a test create a boot floppy.  type SYS A: Reboot from A: which will loaded
only Stacker.  Do you still get the boot error ?

Keith Dunlea, Stac Tech Support

#: 40711 S4/Stacker 3.1
    29-Nov-93  16:15:28
Sb: #SDEFRAG
Fm: luk van de heyning 73064,3331
To: SYSOP (X)

Dear Sir, as I was 'playing around' with Stacker 3,1 DOS/WINDOWS I noticed
folowing 'strange effects':

-When asking a full defragmentation, even when the fragmentation level =0 (I
have the impression it is always 0!), it takes a lot of time to do this. Even
with a frag-level of 0, there are a lot of gaps in the used area of the
harddisk. How is the fragmentation-level measured?

-When I ask the STAC-program to change or check the expected level of
compression JUST AFTER I DID A FULL DEFRAGMENTATION, it starts the full-defrag
all over again, and again it takes a lot of time. How can this be, when the HD
was defragmentated 'a second ago'??

STrange....

Thanks for your attention.

There are 2 Replies.

#: 40781 S4/Stacker 3.1
    29-Nov-93  20:44:05
Sb: #40711-#SDEFRAG
Fm: Edward Nutter [Stac] 75330,2222
To: luk van de heyning 73064,3331 (X)

Luk,

There are three types of fragmentation.  That kind we measure is specific to
Stacker.  However, a full optimize with SDEFRAG will take care of all three.
What is telling you that there are gaps?

Anytime you change the physical or logical size of the drive, SDEFRAG does a
full defragmentation.  That's just the way it works.

Edward Nutter
Stac Electronics Product Support 

There is 1 Reply.

#: 40992 S4/Stacker 3.1
    01-Dec-93  15:07:50
Sb: #40781-#SDEFRAG
Fm: luk van de heyning 73064,3331
To: Edward Nutter [Stac] 75330,2222 (X)

SDEFRAG itself tells me there are 'gaps' , just by showing them to me on the
display!

And this is AFTER i run a FULL defrag! And thay's what surprises me!

There is 1 Reply.

#: 41125 S4/Stacker 3.1
    02-Dec-93  15:24:51
Sb: #40992-SDEFRAG
Fm: Edward Nutter [Stac] 75330,2222
To: luk van de heyning 73064,3331

Luk,

The only thing I can think of that would cause Stacker to leave gaps would be
if the files were marked system or hidden.  Most defraggers will skip over such
files.  You can override that by adding the /H parameter to the SDEFRAG command
line.  You should be wary however, of moving such files.  Some program may not
work correctly if they're not at the expected cluster.

Edward Nutter
Stac Electronics Product Support 

#: 40919 S4/Stacker 3.1
    30-Nov-93  18:50:14
Sb: #40711-#SDEFRAG
Fm: Stac Electronics 75300,2755
To: luk van de heyning 73064,3331 (X)

Luk,

sdefrag was designed to start over regardless if you just ran it. it had been
suggested to change this

fragmentation is based on a combination of things; ie: number of files
fragmented.  i'll have to ask again for a more precise answer and post it here.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41202 S4/Stacker 3.1
    03-Dec-93  00:24:10
Sb: #40919-#SDEFRAG
Fm: Chip May 70712,314
To: Stac Electronics 75300,2755 (X)

I agree that we should not be forced to a full optimize just to change the
expected compression level.

Chip

There is 1 Reply.

#: 41229 S4/Stacker 3.1
    03-Dec-93  12:28:26
Sb: #41202-SDEFRAG
Fm: Edward Nutter [Stac] 75330,2222
To: Chip May 70712,314 (X)

Chip,

Changing the expected compression is not a trivial task.  The size of both FATs
are being changed, and that without endangering your data.  Some "what if"
testing could be added to skip the defragmenting IF the drive were already
fully defragged, but in order to handle all the potentially pathological
situations you would end up with a much bigger SDEFRAG.  That testing is part
of the defragmentation process, but you have to be defragging to make it a
valid test.  Soooo, unless you like putting your data integrity at risk, you'll
have to defrag in order to change the expected compression.

Edward Nutter
Stac Electronics Product Support 

#: 40712 S4/Stacker 3.1
    29-Nov-93  16:33:35
Sb: #STAC 3.1 AFTER DOS 6.2
Fm: Christian J Johnen 70413,3561
To: STAC ELECTRONICS

I have upgrade my system from DOS 6.0 to 6.2. . I would like to install Stacker
3.1. Can I proceed, or should I uninstall 6.2 first or should I take any other
steps? I would greatly appreciate a reply.
Chris.

There is 1 Reply.

#: 40920 S4/Stacker 3.1
    30-Nov-93  18:50:18
Sb: #40712-STAC 3.1 AFTER DOS 6.2
Fm: Stac Electronics 75300,2755
To: Christian J Johnen 70413,3561

Chris,

Just install Stacker 3.1  It works fine with DOS 6.2

Keith Dunlea, Stac Tech Support

#: 40721 S4/Stacker 3.1
    29-Nov-93  18:00:02
Sb: #Stacker v3.16???
Fm: Robert Stahlbrand 73313,2710
To: All

Greetings All,


        Can anyone tell me whether there's such a thing as Stacker v3.16?  If
there does happen to be such a thing, can you also tell me what the differences
are between Stacker v3.10 and Stacker v3.16?

        Regards,

                                                        - =  B o b  = -

There is 1 Reply.

#: 40921 S4/Stacker 3.1
    30-Nov-93  18:50:21
Sb: #40721-Stacker v3.16???
Fm: Stac Electronics 75300,2755
To: Robert Stahlbrand 73313,2710 (X)

Robert,

The latest is Stacker 3.1

Keith Dunlea, Stac Tech Support

#: 40722 S4/Stacker 3.1
    29-Nov-93  18:27:10
Sb: #Deleting Files
Fm: Mark Schwartzman 76126,134
To: SYSOP - Customer Support (X)

I recently upgraded from Stacker Version 2. to Version 3.1.  With Version 2 I
had a number of files - Stacker and DOS primarily on the unstacked portion of
the disk.  Can I delete some or all of those now with Version 3.1?  Which do I
have to keep, if any?

Thanks for the help.

There is 1 Reply.

#: 40922 S4/Stacker 3.1
    30-Nov-93  18:50:25
Sb: #40722-Deleting Files
Fm: Stac Electronics 75300,2755
To: Mark Schwartzman 76126,134 (X)

Mark,


With 3.1 we leave the following uncompressed \Stacker check.exe config ed
stacker.com sysinfo.exe the files in \Dos attrib.exe chkdsk.exe command.com

thats its.

Keith Dunlea, Stac Tech Support

#: 40723 S4/Stacker 3.1
    29-Nov-93  19:07:40
Sb: #CROSS-LINKED FILES W/3.1
Fm: Andy Cartwright 76460,3135
To: STAC ELECTRONICS 75300,2755 (X)

Since moving to DOS 6.0 and Stacker 3.1 for DOS I have been having problems
with Cross Linked files.  It is becomming a severe problem that is occuring on
an almost daily basis. I have good backups and NDD, as a result have not yet
lost anything I could not recover.  I am seeing others report the problem, is
Stacker 3.1 suspect and is there a known fix you can supply me with?

                        Keeping my fingers crossed,
                                                                Andy

There is 1 Reply.

#: 40923 S4/Stacker 3.1
    30-Nov-93  18:50:29
Sb: #40723-#CROSS-LINKED FILES W/3.1
Fm: Stac Electronics 75300,2755
To: Andy Cartwright 76460,3135 (X)

Andy,

Corss links are not caused by Stacker.  It maybe more apparent as we report
file errors and may write protect a Stacker drive.

what else is loaded ?  post your config,autoexec and stacker.ini files

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40963 S4/Stacker 3.1
    01-Dec-93  00:24:49
Sb: #40923-#CROSS-LINKED FILES W/3.1
Fm: Andy Cartwright 76460,3135
To: Stac Electronics 75300,2755 (X)

Subj:  CROSS-LINKED FILES W/3.1         Section: Stacker 3.1 From:  Andy
Cartwright, 76460,3135     To:  Stac Electronics, 75300,2755    Tuesday
November 30 1993 11:13:04 PM

Keith,
A copy of the information you wanted to see follows. Lantastic is version 4.10,
QEMM is version 7.01, Smartdrv is version 4.0, the machine is a 386 w/8Mb of
memory. The 386 in question is the server, one work station is attached. The
drive where I am seeing the problem (STACVOL.000 which is assigned as E: from
the host C: drive ) is a Conner 250Mb IDE.  The E: disk sees 98% of all disk
activity after a boot.  Stacker has not detected any problems.  I have
discovered them in most cases as General Protection faults in windows programs
that failed to execute.  When this problem appears I run NDD (After booting W/O
the Network) from Norton 7.0, thats when I discover the problem. I am also
finding lost clusters more often than ever.

Thanks for your response, any help in finding the problem is appreciated.

                                                                      Andy

----------------------------STACKER.INI---------------------------------

/DIR=C:\STACKER\
/P=1
/EMS
C:\STACVOL.000,NS
C:\STACVOL.001,NS
D:\STACVOL.DSK,SW

----------------------------CONFIG.SYS----------------------------------

[Menu]
MenuItem=Default, Normal Configuration
MenuItem=No_Net, Normal Configuration Minus Network
MenuItem=No_Cache, Normal Configuration Minus Smartdrv.exe
MenuItem=No_Cache_Net, Normal Configuration Minus Smartdriv & Network
MenuItem=Bare_Sys, Dos With Bare Minimums
NumLock=Off
MenuDefault=Default,10

[Default]
DEVICE=C:\QEMM\DOSDATA.SYS
DEVICE=C:\QEMM\QEMM386.SYS DBF:2 RAM ST:M R:1
DEVICE=C:\QEMM\DOS-UP.SYS @C:\QEMM\DOS-UP.DAT
DEVICE=C:\QEMM\LOADHI.SYS /R:2 C:\STACKER\STACHIGH.SYS
DEVICE=C:\QEMM\LOADHI.SYS /R:2 C:\DOS\SETVER.EXE
SHELL=C:\QEMM\LOADHI.COM /R:2 C:\DOS\COMMAND.COM C:\DOS\  /p
DOS=HIGH

[No_Net]
Include=Default

[No_Cache]
Include=Default

[No_Cache_Net]
Include=Default

[Bare_Sys]
DEVICE=C:\DOS\SETVER.EXE
SHELL=C:\DOS\COMMAND.COM C:\DOS\  /p

[Common]
STACKS=0,0
FILES=30
BUFFERS=30
LASTDRIVE=G
FCBS=32,8
BREAK=ON

----------------------------AUTOEXEC.BAT-----------------------------------

REM  THE CHECK LINE BELOW PROVIDES ADDITIONAL SAFETY FOR STACKER DRIVES.
REM  PLEASE DO NOT REMOVE IT.
C:\STACKER\CHECK /WP

@ECHO OFF
PROMPT [$p]
PATH
C:\QEMM;C:\DOS;C:\Lantasti;e:\WINDOWS;E:\UTILS;E:\SPF;E:\NORTON;E:\EXCEL;E:\WIN
ORD;E:\NDW;C:\STACKER;

GoTo %config%
:Default
:No_Net
:Bare_Sys
:No_Cache
:No_Cache_Net

If "%Config%"=="Bare_Sys" GoTo End

SET SYMANTEC=E:\SYMANTEC
SET NU=E:\NORTON
SET SOUND=E:\SB
SET TEMP=E:\TEMP

If "%Config%"=="No_Cache" GoTo No_Smartdrv

If "%Config%"=="No_Cache_Net" GoTo No_Smartdrv


C:\QEMM\LOADHI /R:2 SMARTDRV.EXE A- 2048 2048

:No_Smartdrv

C:\QEMM\LOADHI /R:1 DOSKEY/BUFSIZE=1024

DOSKEY WIN=E: $T CD\WINDOWS $T WIN.COM/3
DOSKEY XTALK=E: $T CD\XTALK4 $T XTALK.EXE
DOSKEY PRODIGY=E: $T CD\PRODIGY $T PRODIGY.EXE

C:\QEMM\LOADHI /R:2 C:\DOS\MOUSE.COM

C:\QEMM\LOADHI /R:2 C:\DOS\SHARE.EXE /L:200

If "%Config%"=="No_Net" GoTo End

If "%Config%"=="No_Cache_Net" GoTo End

C:\QEMM\LOADHI /R:2 NODERUN
c:\qemm\loadhi /r:2 AILANBIO /ack_timeout=4 /retry_period=4 /timeout=4
C:\QEMM\LOADHI /R:2 REDIR ANDY LOGINS=4
C:\QEMM\LOADHI /R:2 SERVER
NET LOGIN/WAIT \\ANDY ANDY
NET LPT TIMEOUT 10

E:
VER
:End


There is 1 Reply.

#: 41050 S4/Stacker 3.1
    01-Dec-93  19:01:33
Sb: #40963-#CROSS-LINKED FILES W/3.1
Fm: Roger Hicks 74250,1407
To: Andy Cartwright 76460,3135 (X)

Andy;

How big is your Swapfile for Windows?

Thanks,

Keith Moon
STAC Product Support

There is 1 Reply.

#: 41095 S4/Stacker 3.1
    02-Dec-93  00:47:18
Sb: #41050-CROSS-LINKED FILES W/3.1
Fm: Andy Cartwright 76460,3135
To: Roger Hicks 74250,1407 (X)

Keith,
4092 Kb using 32 bit access.

                                               Andy

#: 40729 S4/Stacker 3.1
    29-Nov-93  19:56:38
Sb: #Stacker vs. WFWG 3.11
Fm: Steve Hoek 72674,326
To: Stac Technical Support

Hello,

I have been running Stacker 3.1 with the new Windows for Workgroups v3.11 for
about 5 days now with its new VFAT 32-bit FILE access enabled.  From all the
tech notes I can find in the Microsoft Knowledge Base, they do not warn against
trying Disk Compression products other than their own DoubleSpace with WFWG
3.11, so I decided to try it (plus, this forum didn't have a straight answer --
one tech. says it works, one says it doesn't!).

Anyway, I still have all my data.  But, when I do a DIR of the stacked drive,
it reports MORE free space than under DOS or the old Windows 3.1.  The number
it reports is the same as CHECK reports for its freespace on the Stacker drive
before applying the expected/actual compression ratio calculation.

Also, when I run SDIR, it says that it cannot read the STACVOL header.  Then
VFAT steps in with a message saying that SDIR "attempted an INT26 (direct
sector write)" and should be run from DOS instead.

What's the final word on WFWG 3.11 VFAT/VCACHE compatibility with Stacker 3.1?
I'd like to know as soon as possible if my data is in peril!

Please don't write WFWG 3.11 off as a minor product.  As Jesse Berst said in
his Windows Magazine column "Windows for Workgroups v3.11 is the best version
of Windows out there".  I agree!  Thanks...

Steve Hoek X-Rite, Inc.

There is 1 Reply.

#: 40924 S4/Stacker 3.1
    30-Nov-93  18:50:33
Sb: #40729-#Stacker vs. WFWG 3.11
Fm: Stac Electronics 75300,2755
To: Steve Hoek 72674,326 (X)

Steve,

At this time we are looking into WGW 3.11 and should have a tech note posted
real soon.  In the meantime we would not recommend using the 32-bit disk access
with Stacker.  Initial reports indicate it will not work.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41366 S4/Stacker 3.1
    06-Dec-93  03:45:55
Sb: #40924-Stacker vs. WFWG 3.11
Fm: Michael Chan 100033,3524
To: Stac Electronics 75300,2755 (X)

>At this time we are looking into WGW 3.11 and should have a tech note posted
>real soon.  In the meantime we would not recommend using the 32-bit disk
>access with Stacker.  Initial reports indicate it will not work.

Don't you mean 32-bit "FILE" access as opposed to Disk access? I have 5
machines running on 32 bit "DISK" access with no problems. Microsoft doesn't
say that 32 bit "DISK" access is a problem. Only 32 bit "FILE" access is a
problem.


Mike.

#: 40787 S4/Stacker 3.1
    29-Nov-93  22:30:13
Sb: #EMS memory
Fm: Larry Thompson 72627,2415
To: Sysop (X)

Is there anyway to reduce the amount of conventional/upper memory used by
STACKHIGH?  It is currently taking up about 25K.  I would like to load as much
as possible into EMS.  It is common to have 25K in either upper or conventional
memory?  I have the /EMS switch in the STACKER.INI file.  Thanks for your help!

-Larry

There is 1 Reply.

#: 41016 S4/Stacker 3.1
    01-Dec-93  15:32:46
Sb: #40787-EMS memory
Fm: Stac Electronics 75300,2755
To: Larry Thompson 72627,2415 (X)

Larry,

By using /EMS it loads part of the drive "buffers" into a EMS page frame thus
reduing the resident portion to 25k.  This can not be reduced further. Therfore
just load it high using your memory manager.

Keith Dunlea, Stac Tech Support

#: 40808 S4/Stacker 3.1
    30-Nov-93  04:46:10
Sb: #Laptop problem
Fm: TOM LOFFMAN 70252,1536
To: STAC Electronics 75300,2755 (X)

Keith,

Still haven't figured out how to STAC my laptop from the hard drive. Perhaps
you guys could just send me some 3.5" disks. I do have a 3.5" drive to attach
to the laptop. I can send you my serial number, but you probably have it in
your database already.

Thanks,

Tom Loffman 130 Merritt Way Sacramento, CA 95864

There is 1 Reply.

#: 41017 S4/Stacker 3.1
    01-Dec-93  15:32:54
Sb: #40808-#Laptop problem
Fm: Stac Electronics 75300,2755
To: TOM LOFFMAN 70252,1536 (X)

Tom,

Yes, we can send replacements.  However, we need your Stacker 3.1 serial #.  I
checked and you are not registered under v 3.1



Thanks!

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41105 S4/Stacker 3.1
    02-Dec-93  06:26:26
Sb: #41017-#Laptop problem
Fm: TOM LOFFMAN 70252,1536
To: Stac Electronics 75300,2755 (X)

Keith,

And where might the serial number be - I have checked all packaging and find no
serial number for the 3.1 upgrade. On the envelope it says: order no:
17171900172, shipped 6/21/93. Serial number not on disks. Where do I look? Have
we given up trying to stack the laptop without the floppies? Tom

There is 1 Reply.

#: 41173 S4/Stacker 3.1
    02-Dec-93  19:00:20
Sb: #41105-#Laptop problem
Fm: Stac Electronics 75300,2755
To: TOM LOFFMAN 70252,1536 (X)

Tom,

The serial  is on the yellow card.  it should come with three stickers

> Have we given up trying to stack the laptop without the floppies? Tom Not
sure what this means.  We supply the 3 1/2 diskette.  If you need the 5 1/4
there is a card to send in for the diskettes.  Along with the card should be
your Stacker serial #.  IF one is not present, then call Stac Customer Service
at 800-522-7822 and they can assign you one and send out the 5 1/4 floppies

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41210 S4/Stacker 3.1
    03-Dec-93  06:18:43
Sb: #41173-#Laptop problem
Fm: TOM LOFFMAN 70252,1536
To: Stac Electronics 75300,2755 (X)

Keith,

We seem to have gotten off the track here. The 3003.TXT solution doesn't work.
I can't stac my drive on the laptop using any method that was suggested in that
text. I have 5.25" floppies. I need 3.5" disks IF there is no other way to stac
the laptop. Unfortunately, I am leaving on a vacation Dec. 7 and was hoping to
stac the laptop before then. The reason why I asked "have we given up trying to
stac the laptop without the floppies?" is that I tried the 3003.TXT method and
it didn't work. No matter what I did it kept asking me to insert the floppies.
It just wouldn't continue beyond that question - I even used /F and /=F and
they didn't work. Tom

There are 2 Replies.

#: 41244 S4/Stacker 3.1
    03-Dec-93  13:42:18
Sb: #41210-#Laptop problem
Fm: Stac Electronics 75300,2755
To: TOM LOFFMAN 70252,1536 (X)

Tom,

Using the tech note is a last resort for installing Stacker on a floppyless
computer.  It appears to not work well on your system.  Since you have 3.5 inch
drive it maybe better getting a set of those disks.

You can also try a manual install.  type CREATE

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41299 S4/Stacker 3.1
    04-Dec-93  05:45:43
Sb: #41244-Laptop problem
Fm: TOM LOFFMAN 70252,1536
To: Stac Electronics 75300,2755 (X)

Keith,

A note additional to last message: I used ATTRIB and found the STACVOL.DSK and
removed the SHR attributes, then erased it. So I am back to over 30,000,000
free bytes again. Actually, after I ran CREATE I had NO free space left on the
disk. So everything is back to the way it was before. I guess I'll have to wait
for the 3.5" floppies. Do I have to call customer service for this or can you
order them for me? I found my card with the serial number. Tom

#: 41247 S4/Stacker 3.1
    03-Dec-93  14:15:40
Sb: #41210-#Laptop problem
Fm: Stac Electronics 75300,2755
To: TOM LOFFMAN 70252,1536 (X)

Tom.

in addition...

you may try the following.

from the Stacker install diskette in the TOOLS directory run REDBL C:  to build
a Stacker aware dblspace.bin file.  Then create a STACKER directory on C, type
MD C:\STACKER and copy Stacker.com, Check.exe, Sedit.exe and Config.exe into
it.  Reboot and this will load the Stacker driver into memory. Then from the
other drive, run SETUP.  It was asking for the floppy since Stacker was not in
memory.  Using /F or /=F bypasses this warning but for some reason doesn't work
on your machine.

Hopefully the above steps will.  Let me know the results.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41298 S4/Stacker 3.1
    04-Dec-93  05:24:38
Sb: #41247-Laptop problem
Fm: TOM LOFFMAN 70252,1536
To: Stac Electronics 75300,2755 (X)

Keith,

I copied REDBL.BAT to my c:\stacker directory, then over to the laptop. I also
copied to the laptop Stacker.com, check.exe, and config.exe along with all the
other stacker files on my main PC. I ran dedbl.bat on the laptop and got the
following message: The copy process failed for some reason. Please check drive
c: and retry this operation. I then tried to run redbl.bat from the c:\
directory on the laptop and got the same message. I could not find sedit.exe on
my stacker disks. I read the manual about the CREATE command and it says this
is for floppies and ramdrives and other hard drives. I haven't tried it yet but
will do so next to see what happens. Will let you know if it works. Tom OK - I
ran CREATE and now I have 6,000,000 bytes free instead of 36,000,000 but now
what do I do to get stacker to run? I can't even find the STACVOL.DSK anywhere.

#: 40809 S4/Stacker 3.1
    30-Nov-93  05:07:46
Sb: Laptop problem
Fm: TOM LOFFMAN 70252,1536
To: STAC Electronics 75300,2755 (X)

Keith,

Forgot to tell you - I am trying to STAC my laptop using v3.1 which I loaded
from 5.25" upgrade disks - if this matters. Tom

#: 40816 S4/Stacker 3.1
    30-Nov-93  09:53:11
Sb: #resize stacker drive
Fm: george roukas 76044,723
To: sysop (X)

I have to reduce the size of my stacker drive to create a windows permanent
swap file and went through the procedure in STAC.EXE.  I let stacker make the
changes and it reported that I have 11,000K unstacked.  When I go back out to
DOS to test the size of the partition it's still only 1K in size.  Is there
some other operation I have to run to get it to free up the space?

thx. 

There is 1 Reply.

#: 41018 S4/Stacker 3.1
    01-Dec-93  15:33:03
Sb: #40816-#resize stacker drive
Fm: Stac Electronics 75300,2755
To: george roukas 76044,723 (X)

George,

What steps did you take to create more uncompressed disk space? What amount was
entered to be freed ?  The free space will be made on the drive that  is
sswaped.  Is this the drive you checked ?

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41196 S4/Stacker 3.1
    02-Dec-93  22:35:25
Sb: #41018-#resize stacker drive
Fm: george roukas 76044,723
To: Stac Electronics 75300,2755 (X)

I ran the STAC.EXE program and asked to change the size of the stacker disk. It
ran a defrag and asked how many bytes it should allocate to the unstacked
portion of the drive.  I entered 11000K and it asked if it should make the
chaes.  I said yes to confirm and then exited the program. I have both C: and
D: (logical) drives stacked.  I checked the E: drive which (I think) represents
the uncompressed portion of D: and it said I had 512K free. When I went into
Windows to set a permanent swap file it only showed three valid drives--A:, B:,
and E:.  A and B are floppies and E is the drive with 512K left.  It should
have 11MB free.  What am I missing? How can I find out where that 11MB went to?

Thx, --george

There is 1 Reply.

#: 41248 S4/Stacker 3.1
    03-Dec-93  14:15:44
Sb: #41196-resize stacker drive
Fm: Stac Electronics 75300,2755
To: george roukas 76044,723

Geroge,

Sounds like you took the correct steps.  How much is free on D:  ?  Type CHECK
and look at projected bytes free.

Also, is C drive compressed ?  You may have D: setup "replaced" and this would
prevent access to the uncompressed area.  Check your Stacker.ini file [see 3.1
readme for help] and make sure it reads D:\Stacvol.dsk,SW

Keith Dunlea, Stac Tech Support

#: 40817 S4/Stacker 3.1
    30-Nov-93  10:05:00
Sb: #Stac/Concerto/DOS v6.0
Fm: Chris Means/intFAR 71544,2474
To: ALL

Hi,

I've just purchased a Compaq Concerto 486/33 250MB DOSv6.0 machine.  I
currently own Stacker v3.0 and use it on my Compaq SLT/386 which I will sell.

What issues if any are there with upgrading to v3.1 of Stacker and putting it
on my Concerto with DOS v6.0?  Should I upgrade to DOS v6.2?  What does Stacker
give me that DOS v6.2 doesn't?

I read a vague message in the Compaq Forum that there was a problem with
Stacker v3.1 and the Concerto's hibernation feature...can anyone shed any light
on this or another problems.

TIA.

P.S.  I've tried to reach Stac Electronics technical/customer support on many
occasions only to be on-hold for 10+ minutes...are there so many problems with
Stacker that they're too busy to service calls promptly?  This long wait costs
me time/money and does not give me a good feeling towards staying with this
product.  I've used it since v1.0 and have been happy with the product, but
I've never needed technical support before...if I can't get it when I need
it...I will be reluctant to use or recommed the product in the future.

-Chris Means
intFAR Productions

There is 1 Reply.

#: 41019 S4/Stacker 3.1
    01-Dec-93  15:33:09
Sb: #40817-#Stac/Concerto/DOS v6.0
Fm: Stac Electronics 75300,2755
To: Chris Means/intFAR 71544,2474 (X)

Chris,

Yes, you should upgrade to DOS 6.2 first then Stacker 3.1.  This eliminates the
need to use STAC62.EXE utility to help you install.

Stacker 3.1 offers many advantages oveer dblspace.  See STAC31.ADV in lib:2 for
more details.

re: phone time

for the most part you should have very little wait reaching a phone tech. Out
busiest hours are 8-9 pst and 11:30-1:00pm pst during lunch.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41042 S4/Stacker 3.1
    01-Dec-93  18:49:23
Sb: #41019-Stac/Concerto/DOS v6.0
Fm: Chris Means/intFAR 71544,2474
To: Stac Electronics 75300,2755 (X)

Thanks.

-Chris

#: 40825 S4/Stacker 3.1
    30-Nov-93  12:18:09
Sb: #hardcard and host of c:
Fm: Roger S Ward 70253,2751
To: Stac Electronics 75300,2755 (X)

please refer to privious messages with simular subject.

I believe that I have proven the problem to be that I was shadowing the rom
bios for the hardcard.  When I disable rom bios shadowing for the hardcard's
bios address range the hard card is accesable.  When shaddowing is enabled the
hard card appears to the system as the host of drive c: (see first message on
this subbject were I included the text of the file produced by your sysinfo
program.)
Is there a problem with my hardware or is the problem with dos/stacker
software?
Thanks

There is 1 Reply.

#: 41020 S4/Stacker 3.1
    01-Dec-93  15:33:12
Sb: #40825-hardcard and host of c:
Fm: Stac Electronics 75300,2755
To: Roger S Ward 70253,2751 (X)

Roger,

Sounds like your found the root of your problem and its hardware related.

Keith Dunlea, Stac Tech Support

#: 40856 S4/Stacker 3.1
    30-Nov-93  16:37:34
Sb: #Remove CD Rom?
Fm: MARY E. GRUESKIN 73021,2412
To: sysop (X)

Hi! About two monthes ago, I stacked my drive with Stacker and lost the CD Rom
drive. After talking with Tech support via telephone, we re-configured it. In
the meantime, the whole computer got trashed and was replaced by the
manufacturer.I would like to stack the new computer. Would I be better off
removing the Rom software and re-installing it after the stack? I am running a
Dell 486DX2-66 450mg. HD, 16mg. ram,DOS 6.2, Win 3.1,3 1/2" floppy, CD Rom, &
Qemm Memory Manager. Do you see any problems here? I am a registered owner of
Stacker 3.1 for DOS 6 & WIN.  I will wait to hear from you before I tackle this
again! I love your product; It works very well! It's this operator I'm not sure
about ! Thank you for your help.  Mary Grueskin 

There is 1 Reply.

#: 41021 S4/Stacker 3.1
    01-Dec-93  15:33:16
Sb: #40856-#Remove CD Rom?
Fm: Stac Electronics 75300,2755
To: MARY E. GRUESKIN 73021,2412 (X)

Mary,

Install Stacker first.  Then edit your Stacker.ini file [see 3.1 readme] and
add "/bd=E:"  This will allow Stacker to mount on E: and leave the D for the
cd-rom Next, install the cd-rom software

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41186 S4/Stacker 3.1
    02-Dec-93  20:32:58
Sb: #41021-#Remove CD Rom?
Fm: MARY E. GRUESKIN 73021,2412
To: Stac Electronics 75300,2755 (X)

Thank you for the very prompt reply. One more question please. Since the CD Rom
is already installed with the software, should I remove the software and all
reference to that drive before I actually install Stacker? Or should I leave it
as is and make the notations to the ini file after the stack is completed?
Thank you very much for your help.
Mary Grueskin

There is 1 Reply.

#: 41249 S4/Stacker 3.1
    03-Dec-93  14:15:47
Sb: #41186-Remove CD Rom?
Fm: Stac Electronics 75300,2755
To: MARY E. GRUESKIN 73021,2412 (X)

Mary,

If Stacker is not installed yet then don't worry about it.  During install
Stacker will leave the cd-rom alone.

Keith Dunlea, Stac Tech Support

#: 40857 S4/Stacker 3.1
    30-Nov-93  16:44:57
Sb: #Stacker 3.1 Big problems
Fm: Mark E Story 75120,2623
To: All

I have a new Zenith Zstar 486/33 (Cyrix/AMI BIOS), with DOS 6. I bought the new
Stacker and wammo. I keep getting cross-linked files and a big mess. Every few
days more files get zapped.

I always had good luck with the old Stacker, But I can't afford this. About to
try Doublespace...

Any help ?

Thanks

There are 2 Replies.

#: 41022 S4/Stacker 3.1
    01-Dec-93  15:33:20
Sb: #40857-Stacker 3.1 Big problems
Fm: Stac Electronics 75300,2755
To: Mark E Story 75120,2623 (X)

Mark,

What else is loaded ?   Are any specific files cross-links ?  Does it occur
after any specific

Keith Dunlea, Stac Tech Support

#: 41051 S4/Stacker 3.1
    01-Dec-93  19:01:37
Sb: #40857-#Stacker 3.1 Big problems
Fm: Roger Hicks 74250,1407
To: Mark E Story 75120,2623 (X)

Mark;

You didn't post a lot of background information. Was the errors detected at
boot time. Did you have to reboot from
a hung application?  Need more information to be of assistance.

Thanks,

Keith Moon
STAC Product Support

There is 1 Reply.

#: 41103 S4/Stacker 3.1
    02-Dec-93  05:46:42
Sb: #41051-Stacker 3.1 Big problems
Fm: Mark E Story 75120,2623
To: Roger Hicks 74250,1407 (X)

Even though it is a new computer, I suspect a hard disk problem. So since it is
warrantyed (and we are dealers) - will try that route first. If that doesn't do
it, I can upload that sysinfo file... Thanks

#: 40858 S4/Stacker 3.1
    30-Nov-93  17:00:04
Sb: #System err/DOSprogsinwin
Fm: Alan Milewczyk (UK) 70630,506
To: Sysop (X)

Hi folks!

I have a problem on my son's PC and *THINK* I have narrowed it down to Stacker.
The system is a 386DX25 with 4 Meg RAM running MS-DOS 5 - his hard drive was
running a bit low on spare space, so we got him Stacker 3.1 and I installed the
version for "Other DOS".

Since then he gets "System error - cannot read from drive c - cancel/retry"
error messages when he clicks on icons in Windows 3.1. If he clicks on "retry",
nothing happens - but if he repeatedly "clicks" on cancel a few times the
program is accessed OK, although the message returns on exiting from the
program.

The problems only occur when he is running *DOS* programs under *Windows* - no
problems running these DOS programs under DOS and no problems running Windows
programs, such as Write, Paintbrush, Word, etc., under Windows - ONLY *DOS*
programs being run under *Windows*! The programs which are largely games ALL
worked well, without problems prior to Stacker. The programs are run direct
from the command line in the windows icon, although I have tried setting up
some PIFs but without any difference to the problem.

Any thoughts?

 Alan >(8-{)>
 Glossop, Derbyshire, UK on 30-Nov-93 at 21:57:16 GMT

There is 1 Reply.

#: 41052 S4/Stacker 3.1
    01-Dec-93  19:01:42
Sb: #40858-#System err/DOSprogsinwin
Fm: Roger Hicks 74250,1407
To: Alan Milewczyk (UK) 70630,506 (X)

Alan;

I would try reinstalling windows. You don't have to worry about your groups,
only the system files will be copied over.

Thanks,

Keith Moon
STAC Product Support

There are 2 Replies.

#: 41071 S4/Stacker 3.1
    01-Dec-93  19:16:59
Sb: #41052-System err/DOSprogsinwin
Fm: Alan Milewczyk (UK) 70630,506
To: Roger Hicks 74250,1407 (X)

Roger

OK will give it a go - won't be able to do it until Friday but I'll come back
to you if there's a problem.

Thanks again

 Alan >(8-{)>
 Glossop, Derbyshire, UK on 02-Dec-93 at 00:15:20 GMT

#: 41101 S4/Stacker 3.1
    02-Dec-93  03:22:49
Sb: #41052-System err/DOSprogsinwin
Fm: Alan Milewczyk (UK) 70630,506
To: Roger Hicks 74250,1407 (X)

Roger

Tried it - it didn't work - what now?

 Alan >(8-{)>
 Glossop, Derbyshire, UK on 02-Dec-93 at 08:21:43 GMT

#: 40932 S4/Stacker 3.1
    30-Nov-93  19:25:14
Sb: Stacker w/Windows & EMS
Fm: Thomas B. Simpson 70373,2735
To: SYSOP (X)

Is is possible to use the EMS setting of Stacker 3.0 (/EMS) with Windows 3.1?
I didn't know if you could use EMS memory prior to running Windows (in 386
enhanced mode).  Using the /EMS setting would help free some of my high memory
for use, but I don't want to mess up my Windows.

Thanks in advance.

        /Tom

#: 40967 S4/Stacker 3.1
    01-Dec-93  00:59:39
Sb: #Stacker and Word 6.0
Fm: David C Brune 70671,2063
To: All

All,

I'm running stacker on a Bernoulli 90 meg disk and have just installed
Microsoft office with Word 6.0 and Access.  Whenever I try using these programs
I either get GPF errors, or other strange errors.  Is it possible that Stacker
is causing this, and if so is there something that I can do without deleting
the stacker partition off the Bernoulli disk?  If this is a problem, is it
being fixed?

David

There is 1 Reply.

#: 41053 S4/Stacker 3.1
    01-Dec-93  19:01:45
Sb: #40967-#Stacker and Word 6.0
Fm: Roger Hicks 74250,1407
To: David C Brune 70671,2063 (X)

David;


We have not heard of any reported issues with running MS Office. I will submit
your message to our compatablilty team.

Thanks,

Keith Moon
STAC Product Support

There is 1 Reply.

#: 41073 S4/Stacker 3.1
    01-Dec-93  20:02:57
Sb: #41053-Stacker and Word 6.0
Fm: David C Brune 70671,2063
To: Roger Hicks 74250,1407 (X)

Roger,

>> We have not heard of any reported issues with running MS Office. I will
submit >> your message to our compatablilty team.

I'll be interested in what they say.  I've been using Stacker since it's
inception, and have been very happy with it, till now that is.  To test the
theory of whether it is stacker or not, I have reinstalled the software onto
another Bernoulli disk that is not stacked, and it works flawlessly.  Hence, I
believe it is stacker, for some strange reason.  I hope your compatibility team
can come up with some answers, because I fear that when the new Excel and
Powerpoint are released, the situation is going to get worse.  Please keep me
informed.

Thanks,

David

#: 40974 S4/Stacker 3.1
    01-Dec-93  06:29:42
Sb: #/EMS and Windows
Fm: Jay Ambrose 72677,3601
To: Sysop (X)

Have you had any problems with using /EMS with Stacker 3.1 and 386max and
Windows.  MAX warns you not to use a disk caching program under windows that
uses EMS.  It does allow you to turn this message off.

There is 1 Reply.

#: 41054 S4/Stacker 3.1
    01-Dec-93  19:01:49
Sb: #40974-/EMS and Windows
Fm: Roger Hicks 74250,1407
To: Jay Ambrose 72677,3601 (X)

Jay;

There have not been any reported problems with running the parameter switch
/EMS with 386MAX.


Thanks,

Keith Moon
STAC Product Support

#: 40975 S4/Stacker 3.1
    01-Dec-93  07:37:37
Sb: #loading stac high?
Fm: rich sledz 73304,1027
To: all

I use stacker for windows and am having trouble with RAM. I have 572k and need
575k. stacker uses 33k. Is there any way to load Stacker High?

There is 1 Reply.

#: 41055 S4/Stacker 3.1
    01-Dec-93  19:01:53
Sb: #40975-loading stac high?
Fm: Roger Hicks 74250,1407
To: rich sledz 73304,1027 (X)

Rich;

Are you running a memory management program like DOS emm386.exe and have
already run memmaker? If so, I would suggest getting a third party memory
manager like QEMM 386 from Quarterdeck or 386MAX from Qualitas.

Thanks,

Keith Moon
STAC Product Support

#: 40978 S4/Stacker 3.1
    01-Dec-93  09:04:42
Sb: Stacker questions
Fm: Ken Jancef 73321,2107
To: Sysop (X)

I have a few questions about Stacker 3.1 before buying:

1. Now that 3.1 works invisibly like DoubleSpace, can I use Smartdrive or any
other disk cache on the Stacker volume?

2. Would there be a problem bypassing the CONFIG.SYS and AUTOEXEC.BAT with the
F5 key in DOS 6? Would I still see the compressed C: drive ok?

I think that's it for now. A bunch of my friends have Stacker 3.1, but are
kinda computer illiterate, so I figured I'd go to the source. Thanks for the
help.
 
Ken Jancef
73321,2107 

#: 41111 S4/Stacker 3.1
    02-Dec-93  09:12:35
Sb: Stacker questions
Fm: Ken Jancef 73321,2107
To: Roger Hicks 74250,1407 (X)

Ok, thanks for the info. I see about caching the uncompressed drive. Good idea.
Thanks agian.

Ken Jancef
73321,2107 

#: 40979 S4/Stacker 3.1
    01-Dec-93  09:41:07
Sb: #DOS 5/Stac 2 upgrade
Fm: Bill Jones Jr. 70451,1202
To: SYSOP (X)

This is a re-post since my 11/27 message to ALL didn't get the technical
response I was looking for.

I'm currently at DOS 5.0 and Stacker 2.0 on a 2 drive Windows 3.1 386/33
system, both drives stacked.  I want to go to DOS 6 and Stacker 3.1, so I
naturally went out and got MS-DOS 6.0 and the Stacker 3.1 upgrades.

I tried upgrading Stacker first, but Stacker 3.1 won't load with DOS 5.  That
makes sense, I guess, since the disks are clearly labelled Stacker for MS DOS
6.0.  I thought v3.1 only required DOS 3.3 or higher, but....

I'm not about to turn MS loose on this config until I get your blessing -- so
here are my questions:
        1- Do I have what I need to upgrade?
        2- Do I upgrade DOS first?
        3- Should I upgrade to DOS 6.0 and then on up to 6.2?

The hidden agenda item is simple.  How can I perserve my 2 pretty full drives
and still get this upgrade to work?

TIA (again).  Bye Y'all.  BJjr

There is 1 Reply.

#: 41057 S4/Stacker 3.1
    01-Dec-93  19:02:01
Sb: #40979-DOS 5/Stac 2 upgrade
Fm: Roger Hicks 74250,1407
To: Bill Jones Jr. 70451,1202

Bill;

You can install MSDOS 6.0 then 6.2 First.

Please run Sdefrag /g and select make more uncompressed space on the stacked
boot drive. You need to free up about
8MB so when asked how much type in "8000". Now simply do your DOS upgrades.
Once you have DOS 6.2 on the system,
then install Stacker 3.1.

Thanks,

Keith Moon
STAC Product Support

#: 40983 S4/Stacker 3.1
    01-Dec-93  10:39:31
Sb: #Vanishing Disk Space
Fm: Kevin Price 70631,213
To: ALL

I have MS DOS 6.2 and Stacker 3.1 installed.  My directory list said I had 35
Megabytes of Hard Disk Space.  I tried to install a program that requires 2 MB
of Hard Disk Space.  It did not install correctly saying I did not have enough
disk space to install.  I checked my directory again and the hard drive I had 0
bytes free.  I did a chkdsk /f and reclaimed the 35 Megabytes in a .chk file
and erased it.  I tried running sdefrag for the drive and it says I have about
20 percent fragmentation.  It would not do a full optimization saying I don't
have 909,000 bytes of hard disk space on the drive and my hard drive still says
it has 35 Megabytes of space left.  This baffles me.  Does anyone have any
suggestions for me?  I would surely appreciate them.
Thanks,
Kevin Price

There is 1 Reply.

#: 41058 S4/Stacker 3.1
    01-Dec-93  19:02:08
Sb: #40983-Vanishing Disk Space
Fm: Roger Hicks 74250,1407
To: Kevin Price 70631,213

Kevin;

Run the command "check /d" this will show you the projected bytes free on your
drive. The formula is overall compression ratio x bytes free in right hand
column. This number will be different than the number reported in the bytes
free left hand column. The reason for the discrepancy is that we at install
time select a 2.0:1 compression ratio, we are not getting that
on every file. We probably are at 1.6-1.9:1. The difference in space between
lets say 1.8 and 2.0 is .2. this is that space
that is reported which is not usable because there is no place to physically
place it. You need to delete some files to bring
up the bytes free in the right hand column, and then after running a full
optmize, run the command "sdefrag /gl". This
will allow you to set your actual compression ratio over your anticipated
compression ratio.

Thanks,

Keith Moon
STAC Product Support

#: 41034 S4/Stacker 3.1
    01-Dec-93  18:17:25
Sb: #
Fm: Michael Borenstein 71513,1222
To: [F] ALL .

Has anyone experenced this problem?-with DOS 6.2 BOTH config.sys AND
autoexec.bat can be loaded interactively by pressing F8. I have found that I
have no control over autoexec.bat loading -no matter what I do autoexec.bat
always runs. I posted this to both Microsoft and Stac and they said they are
looking into it. I have noticed that there seems to be no problem when running
doublespace.

There is 1 Reply.

#: 41175 S4/Stacker 3.1
    02-Dec-93  19:00:26
Sb: #41034-#
Fm: Stac Electronics 75300,2755
To: Michael Borenstein 71513,1222 (X)

Michael,

Did you have this problem under DOS 6.0 with Stacker 3.1 ?

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41314 S4/Stacker 3.1
    04-Dec-93  16:03:16
Sb: #41175-
Fm: Michael Borenstein 71513,1222
To: Stac Electronics 75300,2755 (X)

Keith: DOS 6.0 did not have an interactive boot feature with autoexec.bat only
with config.sys. DOS 6.2 allows interactive boot with BOTH config.sys AND
autoexec.bat.
Mike

#: 41035 S4/Stacker 3.1
    01-Dec-93  18:17:36
Sb: #
Fm: David Hale 72772,1253
To: [F] All .

While trying to uncover a hard disk problem I re-installed DOS 6.0 and now my
Stacker volumes are unavailable. Did the new 'dblspace.bin' send my Stacker
setup bye-bye? How do I recover from this?

There is 1 Reply.

#: 41176 S4/Stacker 3.1
    02-Dec-93  19:00:29
Sb: #41035-
Fm: Stac Electronics 75300,2755
To: David Hale 72772,1253

David,

refer to the Stacker 3.1 manual.

Use REDBL to rebuild the dblspace.bin and CONFIG.EXE to recreate the
Stacker.ini file

Keith Dunlea, Stac Tech Support

#: 41086 S4/Stacker 3.1
    01-Dec-93  22:30:46
Sb: #stacking after install
Fm: Paul E. Pancoast 70372,1401
To: technical support

I just installed stacker in my NEC ultralite versa, with 120 M internal hard
disk, and want to know how to continue the stacking of my disk as I add
additional applications and documents.  Will they automatically be stacked and
compressed, or do I need to do something extra to make them stacked.  I started
out with 6 MB free, and after running stacker, I have about 70 MB free, which
is good, but I want to make the most of it.  How do I make sure that subsequent
applications are stacked, without running setup again, and watching or waiting
for another 2 hours?

There is 1 Reply.

#: 41177 S4/Stacker 3.1
    02-Dec-93  19:00:32
Sb: #41086-#stacking after install
Fm: Stac Electronics 75300,2755
To: Paul E. Pancoast 70372,1401 (X)

Paul,

The data is automatically "compressed" when written to a Stacker drive and
"decompressed" when read.  All in real time.

see tech note 3405.txt in lib:3 on adding new software or hardware

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41222 S4/Stacker 3.1
    03-Dec-93  10:59:02
Sb: #41177-#stacking after install
Fm: Paul E. Pancoast 70372,1401
To: Stac Electronics 75300,2755 (X)

Dear Keith, If I put a floppy, 1.4M, into A:, and run the stacker utility on
it, does this mean that I will then be able to put up to 2M+ onto it, without
doing anything different, and it will be usable on any computer, regardless of
whether or not it has stacker?  I am interested in making several 1.4 HD
floppys with greater storage capacity for file transfer with friends who don't
use stacker on their desktops.

Thanks, Paul

There is 1 Reply.

#: 41250 S4/Stacker 3.1
    03-Dec-93  14:15:49
Sb: #41222-#stacking after install
Fm: Stac Electronics 75300,2755
To: Paul E. Pancoast 70372,1401 (X)

Paul,

Yes, you are correct.  This is part of Stacker-Anywhere

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41282 S4/Stacker 3.1
    03-Dec-93  20:29:20
Sb: #41250-stacking after install
Fm: Paul E. Pancoast 70372,1401
To: Stac Electronics 75300,2755 (X)

Keith Dunlea,

Great!  Why don't you guys market already-stacker-formatted floppies of 2.8 M?
I bet they would sell easily!  (No answer required)

Paul

#: 41088 S4/Stacker 3.1
    01-Dec-93  22:42:08
Sb: #3.1 Install fail
Fm: Richard B. Rios 72133,2536
To: STAC support

I received a "Create error 83: File seek operation failure."   message sometine
into the actual compressing of my hard drive during installation.  I couldn't
find any additional help in the users guide, so I hit enter to continue.  The
system tried a reboot but got the following msg "D: =C:STACVOL.DSK (size
mismatch) (write protected).        Help.

I am trying to install STACKER 3.1 on the DOS partition on my PC with DOS 6.2
and Windows 3.1.  A twizle might be the other inactive partition is running SCO
Open DeskTop (ie. UNIX).  I have been able to bring the DOS partition up with a
boot disk, used FDISK to make the other non-DOS partition active and am now
working from UNIX. 

There is 1 Reply.

#: 41178 S4/Stacker 3.1
    02-Dec-93  19:00:36
Sb: #41088-#3.1 Install fail
Fm: Stac Electronics 75300,2755
To: Richard B. Rios 72133,2536 (X)

Richard,

error 83 occurs when there is a write error during install. you need to Unstack
the drive to decompress the files then run a disk repair utility on the drive
to check for errors.

You can also try running the disk repair utility first then restart the SETUP
as Stacker will either continue with the install or back out.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41303 S4/Stacker 3.1
    04-Dec-93  10:01:49
Sb: #41178-3.1 Install fail
Fm: Richard B. Rios 72133,2536
To: Stac Electronics 75300,2755 (X)

Indeed, I must have had a bad sector on the disk.  I have recovered from the
fail with the execellent help from John on the support line.  We got MSDOS 6.2
access to the scandisk utility, ran it, didn't find an error (which was not
totally unexpected) and then unstacked, deleted STACKER, rebooted, ran scandisk
again(again no problem found) and then reinstalled STACKER w/o a failure.

I only wonder why STACKER didn't originally check for bad sector first.

In any case, I a very happy camper.  Full Unix and MS Windows on athe same
machine.  Now if I can get OS/2 to cooexist.....

#: 41093 S4/Stacker 3.1
    01-Dec-93  23:42:54
Sb: Iomega 21 meg floptical
Fm: James W. Ognibene 70700,124
To: Stacker tech group

Just a quick question: Does Stacker 3.1 for ms-dos 6 support the
Iomega Floptical Drive ? I tried to mount it but I either didn't
wait long enough or it didn't seem to work , alothough it was recognized in the
'Drive F' Position wher it belongs. Is it me or does it take longer to access
drives in general (I.E. typing form c>a:)?
 While I think of it : does it recognize a shareware program called DCOPY which
is a one pass floppy type copying program? it came up with an error
which escapes me at the moment. My registration is in the mail!
                    Thanks!
                                    Jim 

#: 41108 S4/Stacker 3.1
    02-Dec-93  09:08:48
Sb: #Reserve drive letter
Fm: Jim Mihalski 72712,2431
To: sysop (X)

I have a Toshiba T4600C and they have a new PCMCIA driver that I must  install.
The driver will use drive D: (I have no control over that).

Can stacker 3.1 be forced to reserve drive D - If so how can it be done???

Thanks for help.

Jim

There is 1 Reply.

#: 41136 S4/Stacker 3.1
    02-Dec-93  18:29:05
Sb: #41108-Reserve drive letter
Fm: Roger Hicks 74250,1407
To: Jim Mihalski 72712,2431 (X)

Jim;

Yes. Please refer to the readme.txt file and read about the switch "/BD" in the
stacker.ini file.

Thanks,

Keith Moon

#: 41116 S4/Stacker 3.1
    02-Dec-93  11:28:26
Sb: ongoing stacking
Fm: Paul E. Pancoast 70372,1401
To: Edward Nutter [Stac] 75330,2222 (X)

I installed stacker yesterday on my NEC Ultralite versa, and went from 6M free
to 70M free on my 120M drive.  How do I make sure that continuing applications
that I add, like a new Fax program, are added stacked, to conserve my remaining
free disk space?  I have scanned the manual and didn't see the answer.  I hate
to spend another 2 hours restacking my disk just to compress 20M of additional
applications.

#: 41205 S4/Stacker 3.1
    03-Dec-93  01:13:51
Sb: #WINDOWS SWAP FILE
Fm: Martin Schray 71035,3605
To: ALL

Is there anyway to get make space on the actual physical drive without
unstacking and restacking.  I need to get enough nonstacked disk space to put a
windows permanet swap file.


There is 1 Reply.

#: 41251 S4/Stacker 3.1
    03-Dec-93  14:15:52
Sb: #41205-#WINDOWS SWAP FILE
Fm: Stac Electronics 75300,2755
To: Martin Schray 71035,3605 (X)

martin,

Just run SDEFRAG /GP.  Refer to your manaul for more details

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41293 S4/Stacker 3.1
    04-Dec-93  00:34:07
Sb: #41251-WINDOWS SWAP FILE
Fm: Martin Schray 71035,3605
To: Stac Electronics 75300,2755 (X)

Thanks.  I'll give it a try.

#: 41217 S4/Stacker 3.1
    03-Dec-93  09:38:24
Sb: #WIN.INI load=??
Fm: Barry Schindler 73110,3333
To: Sysop (X)

I had a comm disconnect while uploading this message. Forgive me if you receive
it twice:

My WIN.INI file contains the following entry:

load=C:\STACKER\sgroup.exe C:\STACKER\sgroup.exe

Is this caused my more than one installation? Do I need it twice? Does it need
to remain after Stacker and its group has been installed?


There is 1 Reply.

#: 41252 S4/Stacker 3.1
    03-Dec-93  14:15:56
Sb: #41217-WIN.INI load=??
Fm: Stac Electronics 75300,2755
To: Barry Schindler 73110,3333 (X)

Barry,

You only need it once.  Remove the second C:\Stacker\Sgroup.exe

Keith Dunlea, Stac Tech Support

#: 41225 S4/Stacker 3.1
    03-Dec-93  12:08:49
Sb: #Stacker & Bernoulli
Fm: Peter T. Szymonik 70474,235
To: All

I just added a Bernoulli 150 removable to my system and am confused about how
Stacker works with it.  First, I stacked the removable disk and it offered 300
megs, but I have to run a STACKER.EXE to mount it that way.

This is fine, except that I noticed that Central Point's Backup program doesn't
seem to recognize that the drive has been stacked.  It tries to backup 271 megs
worth of data, and regardless of whether the drive is stacked and mounted, or
unstacked and mounted, it still asks for a new disk when its about 70% done
with the backup.

Second problem is that when the drive is mounted and I run STACKER.EXE off the
disk, I constantly get a message that "STACKER Doubles Your Disk Space!!", how
do I get rid of this message?

Finally, if I want to remove Stacker from the disc, how do I do it? Stacker
utilities don't seem to recognize the dik even though its stacked and mounted.
SO UNSTACK doesn't work, it give me a fatal "DIsk not found" error message.

Thanx Peter Szymonik Middletown, CT

There is 1 Reply.

#: 41260 S4/Stacker 3.1
    03-Dec-93  17:34:12
Sb: #41225-#Stacker & Bernoulli
Fm: Stac Electronics 75300,2755
To: Peter T. Szymonik 70474,235 (X)

Peter,

Did you run SETUP to install Stacker ?  Sounds like you didn't.

Stacker 3.1 sets up a Stacker.ini file.  Edit this and make it references the
Bernoulli drive.  FOr example if the Bernoulli is on E: it would read

e:\stacvol.dskp,rp


this will enable automount to mount the drive at boot time.  once mounted you
should not get any error from the Stacker utilities

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41276 S4/Stacker 3.1
    03-Dec-93  19:36:27
Sb: #41260-Stacker & Bernoulli
Fm: Peter T. Szymonik 70474,235
To: Stac Electronics 75300,2755 (X)

I think I did: STACK G:

Peter

#: 41284 S4/Stacker 3.1
    03-Dec-93  20:44:54
Sb: W4Workgroups 3.11
Fm: George W. Gilchrist 76350,3113
To: All

Are there any known problems with Stacker 3.1 and Windows for Workgroups, v.
3.11? I'd be especially interested in anything you know about the 32 bit file
access in W4W 3.11. I'm just trying to anticipate troubles, if you know what I
mean...

Thanks for any info.

George

#: 41285 S4/Stacker 3.1
    03-Dec-93  20:53:03
Sb: WinNT
Fm: Harry Forster 100316,1573
To: all

Stacker for Windows NT.
Using Stacher 3.1 for DOS and OS/2 already, I am looking for  a possibility to
use stacked drives under WinNT as well. DOS/Win, OS/2, WinNT and SCO ODT are
installed on same HD. DOS, OS/2 and ODT are on a Primary-Partition each, NT is
on Drive G:; Drives E: and F: are stacked.

#: 41305 S4/Stacker 3.1
    04-Dec-93  11:08:20
Sb: Defragmenting
Fm: Thomas Bartlett 71072,3671
To: SYSOP (X)

I use Stacker 3.1 with DOS 6.2.  I have installed your patch that removes
incompatibilities between these two.  Everything seems to be okay for now.
Before using Stacker, I used to degragment my drive by bootup up from the A:
drive so that no TSR's would load, then run Norton Speedisk.  Now I understand
that I should use Stacker's OPTIMIZE or SDEFRAG to degfragment my stacked file,
and I can continue to use another optimizer, such as PCTOOLS' optimizer, Norton
Speedisk, etc., for all uncompressed regions.  The question I have now is this:
I don't see any indication in the Stacker 3.1 documentation that I should avoid
loading TSR's before using Stacker's SDEFRAG or STAC/OPTIMIZE functions. Is
this true?  Is is because Stacker 3.1 is integrated into DOS that I need not
worry about TSR's being loaded when degragmenting the compressed portion of my
hard drive?  (After swapping, the uncompressed portion of my original C: drive
is called E:, and I also have an entirely uncompressed D: drive.)  I have just
defragmented by this method, and everything seems to be okay, but I am somewhat
surprised and pleased to think that there is a simpler method available than
what I used in the past.  I'd appreciate your advice about the best way to
defragment in future.  Thanks.


T. Bartlett

#: 41311 S4/Stacker 3.1
    04-Dec-93  14:31:36
Sb: Bernoulli 90PRO
Fm: Edward W. Ulle 70043,312
To:  75300,2755 (X)

I am running MS-DOS 6 386MAX 7 and Stacker 3.1 with 90PRO Bernoulli. Since I
upgraded to 3.1 I have discovered Iomega OADUTIL does not recognize the
Bernoulli as an Iomega disk drive.  I can not format new cartriges. C: is
stacked and becomes E:.  The OAD driver assignes logical D: to the Bernoulli
but stacker reassigns it to F:.  The Bernoulli is also stacked. Otherwise old
cartriges converted from 3.0 to 3.1 work fine.

I would also like to know why stacker commands are not used in place of DOS
commands.  I get a message "Stacker ... program not found.".

Lastly, I use PC Tools for windows file manager.  I would like to know if there
is a simple way to use the Windows file and disk utilities from PC Tools.  I
can customize the menus but don't know the DLL function calls and parameters.

Any suggestions would be appreciated.

#: 41317 S4/Stacker 3.1
    04-Dec-93  17:23:46
Sb: error 136 HELP?
Fm: Joe Daigle 76570,1536
To: sysop (X)

Stac,

       I tried to change my expected compression ratio today, and while Stacker
was trying to do it's thing, after the SDEFRAG (the status screen for sdefrag
was still in the background showing 100% complete), a nasty red box popped up
and said "Size change error 136 - Internal error", and to type any key to exit.

       Help?  What can I do?  What does this mean?  Everything appears to be
just fine with all of my files ( I ran check, NDD, SCANDISK, CHKDSK,
..).   Nothing found any errors of any kind.

       The one odd thing I noticed is that I have an expected compression ratio
of 3.9, which to the best of my knowledge I never set.  I did for a short time
run Stacker for OS/2 and DOS, which is around the time I started noticing the
expected ratio being 3.9, not 2.0 which is what I thought it should be.  I have
since taken both Stacker for OS/2 and OS/2 itself off my system.

Any help would be greatly appreciated.

Joe


#: 41318 S4/Stacker 3.1
    04-Dec-93  17:41:13
Sb: Stac Card w/3.1
Fm: Ed Wolfstein 73447,1424
To: Sysop (X)

Just upgraded to Stacker 3.1 (from 3.0) and I tried to set the stac compression
to continue to use my 16 bit stacker card.  But every time I check this, it
reverts to non-card use.  Any suggestions?  Checked the stacker.ini file, but
this didn't have a particular toggle for using the card - only the rate of
speed/compression.
            - Ed Wolfstein
              Burlington, Vermont

#: 41319 S4/Stacker 3.1
    04-Dec-93  18:15:58
Sb: 3.1 and Macola Lock-up
Fm: John E. Katich 73510,350
To: Stac 75300,2755 (X)

I just upgraded from  Stacker 3.0 to 3.1 (DOS 6.2  & QEMM 7.03).   When
attempting to run  MACOLA ACCOUNTING APPILCATIONS my system locks up.  It
worked OK with 3.0 and 6.2.  Macola uses BTRIEVE.

I have to move Macola to a non-stacked drive and "rem out"  stachigh.sys to get
it to work.

This also happened when I went  from 2.0 to 3.0.   At that time I used the
undocmented switch /NB  to get it to work.  /NB is in stacker.ini, but of no
avail..

Any ideas???... Next payroll is in a week!!!   Also, what is /NB and
STACHIGH.SYS  neither are documented?

Regards
JEK

#: 41325 S4/Stacker 3.1
    04-Dec-93  23:28:49
Sb: Unable to create dir.
Fm: Jeff Goodsite 76702,775
To: all

        I don't know if this is a DOS (6.2) problem or Stacker, but I'll post
the same message in both places and see what I get:
        I tried to install a piece of software that wanted to create a new
directory, and Windows returned a useless message.  After ascertaining that the
message was in response to the installer's attempt to create a certain
directory, I just opened a DOS window and tried to create it.  "Unable to
create directory".
        I can create a directory with a different name in exactly the same
place on the directory tree, but for some reason, DOS/Stacker will _not_ let me
create C:\MXGLIBS\MGXFONTS.  I can create MGXFONTS from the root of C

#: 41326 S4/Stacker 3.1
    04-Dec-93  23:33:40
Sb: #Unable to create dir.
Fm: Jeff Goodsite 76702,775
To: all

        I don't know if this is a DOS (6.2) problem or Stacker, but I'll post
the same message in both places and see what I get:
        I tried to install a piece of software that wanted to create a new
directory, and Windows returned a useless message.  After ascertaining that the
message was in response to the installer's attempt to create a certain
directory, I just opened a DOS window and tried to create it.  "Unable to
create directory".
        I can create a directory with a different name in exactly the same
place on the directory tree, but for some reason, DOS/Stacker will _not_ let me
create C:\MXGLIBS\MGXFONTS.  I can create MGXFONTS from the root of C, I can
create any number of subdirectories underneath MGXLIBS, I can create a
subdirectory named MGXFONT, but the minute I add the "S", I get the same
message.
        All the DOS and Stacker diagnostics check out fine, and there's like
145M free on the disk.
        Any idea, anyone?
Jeff

There is 1 Reply.

#: 41328 S4/Stacker 3.1
    05-Dec-93  04:03:21
Sb: #41326-Unable to create dir.
Fm: Tom Gutman 70444,205
To: Jeff Goodsite 76702,775 (X)

Do you have a hidden directory by that name?

     Tom Gutman

#: 41329 S4/Stacker 3.1
    05-Dec-93  07:39:34
Sb: #3.1 setup & Filemanager
Fm: Willem P Offenberg 100022,1502
To: sysop (X)

I have installed stacker 3.1 (MSDOS6 version) in wfw 3.1 on a stand alone
Compaq 386s/20 from A: drive running MSDOS 6.2. I left the C: drive unstacked,
but stacked a Plus Hardcard XL 105 to swap D:/E:. I have used the work around
with /SW=DE and * in stacini and mounting the drive in autoexec.bat.
After installation the program offered to install the stacker group in progman
on windows startup. It created the stacker group, but did not upgrade File
manager to include the stacker menu option. I have tried to re-create the group
with file manager in main, accessories and applications groups in the original
wfw desktop, but no success.
Any suggestions ?

There is 1 Reply.

#: 41361 S4/Stacker 3.1
    05-Dec-93  23:54:44
Sb: #41329-#3.1 setup & Filemanager
Fm: Soto Armijo 73124,310
To: Willem P Offenberg 100022,1502 (X)

Willem,

        In Windows 3.1 there is an [AddOns] section in the WINFILE.INI file
that goes like this:

[AddOns] Stacker Extension=c:\stacker\stacfm.dll

I would assume that the File Manager for WFW works the same as Windows 3.1 and
if the [AddOns] section doesn't exist you can add it manually along with the
Stacker Extension line. If the path to your STACFM.DLL file is different than
mine then specify the proper path for your PC. I hope this helps you get going.
                                        Soto

There is 1 Reply.

#: 41384 S4/Stacker 3.1
    06-Dec-93  15:34:46
Sb: #41361-3.1 setup & Filemanager
Fm: Willem P Offenberg 100022,1502
To: Soto Armijo 73124,310

Thanks for the suggestion. I'll have a look. Will let you know.

#: 41340 S4/Stacker 3.1
    05-Dec-93  16:48:50
Sb:   DOS STEPUP/62ST
Fm: scott holland 71214,162
To: Stac Electronics 75300,2755 (X)

Hi,

I know this question has been asked at least a million times but...I am running
STACKER 3.1, time stamped 6/10/93 at 3:10 a.m.  I have downloaded STEPUP.EXE
from CIS and 62STAC.EXE from here.

Do I need to run BEFORE and AFTER62.EXE or not?

Thanks.

Scott

#: 41341 S4/Stacker 3.1
    05-Dec-93  17:10:24
Sb: Wont compress 25M?
Fm: James Vasil 72157,1340
To: sysop (X)

Hello,

I am running Stacker 3.1 on a Gateway 2000 with a 340 Mb drive.  My
uncompressed drive (E:) shows about 25M of unused space.  I would like to
compresss most of that and add it to my C: drive which is currently showing
about 520Mb total space.  But when I run sdefrag (from Dos) it tells me that
using all of the available memory.  I tried forcing a compaction by telling
sdefrag I wanted to increase the amount of uncompressed space.  After speed
disk ran, I exited (F10) without changing the space reserved.  Note that I do
have a perm. swap file on C: but I don't think that should be causing this
problem.

I am at a loss of where to go from here.  Any help you could provide would be
appreciated.

Regards,
James Vasil

#: 41342 S4/Stacker 3.1
    05-Dec-93  17:25:45
Sb: UNSTACK problem
Fm: Eddie Myers 71240,656
To: Whomever

 I have a 486 DX2/66 with Dos 6.0 upgraded to 6.2.  When I installed Staker
3.1, there was no problem.  However, I noted the new drives created.  With 345
meg hard drive, I found that instead of the A through D(CD-Rom), I now have A
through F(the new directory for the CD-Rom.)  When I decided to UNSTACK, all
worked well with Drive C, but when it went to D, where the Stacker files were
located, it indicated not enough space to decompress.  The information report
for that drive is weird -- with 345 meg size, but only 1.07 meg available.
Drive C had 446 meg size with 178 meg available.  How can I UNSTACK and not
have it give an error message when it moves to the drives the system created on
the installation?  I also have an E drive created (Stacvol.Dsk) with 149 meg
size and 149 meg. available.  I would like to go back to the original system,
with all uncompressed and only my original C (345 meg.) and D(CD Rom) and my
floppy drives(A&B).  Could you give me some help in either preparation needed
prior to UNSTACK or what to do when it reports that the D drive does not have
enough room to unstack its contents. -- actually there is plenty of room.
    Thanks for the help.             Eddie Myers/Bay Villiage, OH       

#: 41344 S4/Stacker 3.1
    05-Dec-93  18:44:38
Sb: WFW 3.11 32 Bit File Acc
Fm: Steve Hoek 72674,326
To: Chip May 70712,314

PMFJI, but I'd also like to say that I am running WFWG 3.11 with 32-bit DISK
and FILE access on 2 IDE HD's and a Stacker volume.  Only problems I've seen so
far are with SDIR (gives an error message) and the DS.EXE (DirSort) utility
that comes with Norton Utilities.

According to tech. notes in the Microsoft Knowledge Base, Stacker drives are
supported under WFWG 3.11 and 32-bit FILE access.  However, only DoubleSpace
drives (as well as "real" drives) have write-back caching enabled by default.
To change this for you Stacker drive, put the following line in your SYSTEM.INI
in the [386Enh] section:
   ForceLazyWrites=CDE    -- where CDE are the letters of the drives you want
                             affected.

If you want to read about this yourself, GO to MSKB and search for "32-bit" and
"VFAT" and "VCACHE" under the WFWG 3.11 product.

Also, SMARTDrive is only needed to cache floppies and CD's under WFWG 3.11 with
32-bit FILE access on.  DOS VM's get cached just fine thank-you by VCACHE and
the rest of the 32-bit FILE access drivers.

Of course, we're *STILL* waiting for an official response from STAC on all of
this!  It seems like they would've had a Beta or something along the way and
been able to be ready the DAY OF Windows for Workgroups v3.11 release.  I'm
actually considering converting to DoubleSpace just because I'm sure Microsoft
will come out with disk compression for NT and Chicago way before STAC does.

Any response STAC?

Hope this helps...

Steve Hoek X-Rite, Inc.

#: 41349 S4/Stacker 3.1
    05-Dec-93  19:54:23
Sb: Stacker/PC-Tools win
Fm: Franklin Rakes 75460,433
To: Tech support

Dear Tech Support:
I use PC-Tools for win desktop shell. After
loading stacker...I got the message:
"Stacker detected an incompatible shell
create the stacker group using the procedure
described in Win desktop shell manual"

So I tried using the instructions on pg.
117 of the stacker manual. Then I tried
to create a new folder using PC-Tools
DT...same message.

Please offer your help
Franklin Rakes    Stacker 3.1

#: 41357 S4/Stacker 3.1
    05-Dec-93  21:25:54
Sb: DOS 6.02
Fm: Glenn Romualdo 70042,3303
To: All

Is the latest version of Stacker (3.1) compatible with DOS 6.02?  If not will
there be an upgrade?  Will the stac copressor be compatible with DOS 6.02?

#: 41364 S4/Stacker 3.1
    06-Dec-93  01:53:35
Sb: stacker 3.1 and windows
Fm: Andrew Mark  Cohen 72613,757
To: all

I am having a problem and could use some help. I am running an IBM 486SX 33mhz
machine with Windows for Workgroups 3.11 and DOS 6.2 I cannot format any disks
in my a: or b: drives from File Manager. I can, however, format just fine from
DOS. This problem only began when I installed Stacker 3.10 onto my computer
which came preloaded with windows 3.1. I thought loading WFW 3.11 would repair
the problem but it doesn't seem to have made a diference. Anybody got any
suggestions?
                        andy

#: 41365 S4/Stacker 3.1
    06-Dec-93  03:36:45
Sb: Stacker+CPBackup=death
Fm: Robert Cauthorn 73647,22
To: all

I've run into a serious problem with corrupted Stacker 3.1 volumes after
backing up a Novell 3.11 drive using Central Point Backup. The stacked drive is
fine in normal use and fine when files are restored to it using CPBackup. The
problem arises after I conduct a regular back up of files from the Netware
server.

The backup itself goes uneventfully. After I've completed the backup I still
have full access to the Stacker volume. However once I reboot the machine, I
get a Stacker error message that says the FAT is unreadable on the compressed
drive and therefore the volume doesn't mount. That, of course is followed by an
error message when the machine hits the Stacker /Check line in the
autoexec.bat.

It takes forever to boot because after each of the error messages the machine
freezes for four minutes or so as the light on the D: drive (the uncompressed
drive on which the Stacker volume resides) shines. Moreover, once the machine
boots on C: whenever I enter a command that requires DOS to check the path it
takes forever while it checks the D: drive, even though there are no
directories on D: in the path.

If I try to run Norton 7 Disk Doctor on drive D: it gives me an error message
saying "insert Disk for drive D:" This, despite the fact it senses the drive as
a fixed disk. The Stacker supplied utilities don't help either.

The weird thing is if I run Central Point DiskFix on the drive I can revive the
Stacker volume. First I run the diagnostic program, which reports NO ERRORS (!)
on the drive. Then if I run the Scan disk option (again NO ERRORS) and reboot,
I can get the Stacker drive to mount!

HELP!!!! I'm writing this on Sunday night and on Tuesday I'm supposed to
install a VERY expensive and very large set of data on the stacked drive that
keeps going foobar. I need to be able to use the tape backup without having to
go through the DiskFix song and dance. Moreover, even though I can get the
Stacker volume back, I'm still worried about losing the data at a later point.

I don't know if the corruption happens if I simply backup a local hard drive
because I'm too nervous about this problem to try. Besides, it takes so long to
go through the steps to rebuild the sucker. And no, I'm not trying to back up
the Netware bindery, only a single directory on the server.

Individually all these parts work together fine, when you combine them, it
blows up in your face.

Here's the system information for any bright person who can help me....

The hardware: DEC MTE 486/33 w/12 megs RAM, drive C is a Quantum 127 meg IDE,
drive D: a Conner CP30544 IDE entirely devoted to the Stacked volume. The tape
drive is a Conner Tape*Stor 250 meg on the floppy controller.

The software: MSDOS 6.2 (the step up installed prior to Stacker), QEMM 7
(Stealth enabled), Central Point Backup from PCTools 8.0, Stacker 3.1 and I'm
using the DOSODI shell to attach to a Netware 3.11 server. Because Stacker is
using EMS I've set the QEMM command line to DB:2. I'm also loading the new
smartdrv version that comes with the DOS 6.2 step up. Write caching has been
disabled.

Any and all assistance would be of great help. I'm cross posting this note on
the Stac, Central Point and QEMM forums, in the hopes of getting a fix and to
warn others of this apparent conflict.

Sorry for the length of this, but the techs always want details. Hope this is
enough.

Thanks in advance,

Bob

#: 41368 S4/Stacker 3.1
    06-Dec-93  04:34:35
Sb: Hidden files and Stak3.1
Fm: Gerald Fay 72271,1316
To: ALL

Since I've upgraded to Stacker 3.1 a while back. I'm wondering what the purpose
of having hidden system files on both the D: drive and the Stacked C: drive in
the root directory. Last night I got adventuresome and erased the command.com
from the D: drive with no trouble. I note that the stacker.ini file is just on
D: while the dblspace.bin is on both. Just what hidden system files can I get
rid of and on what drive?

Thanks

#: 41369 S4/Stacker 3.1
    06-Dec-93  08:10:51
Sb: Drive Not Mounted
Fm: Dave Michael 76424,3150
To: SYSOP (X)

I have intermittent error of E:=C:\STACVOL.000 Cannot read initial STACVOL file
sectores - not mounted...  Rebooting can sometimes relieve msg from appearing.
Called tech support twice, each time repairs seemed okay but problem still
shows intermittently. This is a portion of STACINI.txt performed AFTER bootup
with F5 depressed (actual hardware setup has Bernoulli drive as D: [not
Stacked] and CD ROM drive as F:,  C drive is boot drive at approx 330MB
uncompressed):

***** PHYSICAL DRIVE INFORMATION
Drive Type      Local/LAN  Total (K)    Free (K)     S/C  Version  RWD
----- -------   ---------  -----------  -----------  ---  -------  ---
 A:   1.44MB    Local
 B:   1.2MB     Local
 C:   Fixed     Local        473980928    351043584   16     3.00  ___
 D:   Fixed     Local        340746240      1064960
 E:   Stacked   Local                0            0    4     0.00  ___
-------------------------------------------------------------------------  *****
STACVOL FILE INFO
Drive C:
   None found!
Drive D:
   STACVOL.DSK      268,435,456  Sys Hid R/O
   STACVOL.000       55,299,072  Sys Hid R/O
Drive E:
   Drive not mounted!
-------------------------------------------------------------------------
***** STACKER COMMAND INFO
Stacker hardware information :  Software only
Stacker using EMS            :   NO
Stacker loaded high          :  YES
Available replaceable drives :  1
Number of unmounted drives   :  1 (excluding removable drives)
Number of replaced drives    :  0
Number of read-only drives   :  0
Number of damaged drives     :  0
Stacker drive map:
   Drive A: was drive A: at boot time
   Drive B: was drive B: at boot time
   Drive C: was drive C: at boot time  [ D:\STACVOL.DSK = 256.0MB  ]
   Drive D: was drive D: at boot time
   Drive E: was drive E: at boot time  [ C:\STACVOL.000 -- Not mounted ]
=========================================================================
WINDOWS INFORMATION
=========================================================================
***** WINDOWS PERMANENT SWAP FILE(S)
Windows Permanent Swap File found:  D:\ (15,360,000 bytes)
1 permanent swap file(s) found.
***** Unable to locate WINDOWS WIN.INI FILE *****
***** Unable to locate WINDOWS SYSTEM.INI FILE *****

Using Stacker 3.1 with DOS 6.0 -- registered new Ser No. with Tech Spt with
each call. Any help appreciated.

DaveM
(Richard David Michael, Markinetics Inc., 614 374-6615)  

#: 41375 S4/Stacker 3.1
    06-Dec-93  11:00:34
Sb: Increasing Stacker Drive
Fm: Joe DiCostanzo, NY 71203,210
To: Tech Support

Tech Support,

        I use Stacker 3.1 on my Gateway 2000 486DX2/50.  I have DOS 6.0 and
Windows 3.1.  I have a 330 M SCSI hard drive and when Stacker installed it
created a 484 M Stacker drive and left 64 M uncompressed on the host drive.
Since I don't use the uncompressed space much, I thought I could make more
efficient use of it by increasing the Stacker drive size, but after invoking
the Stacker Drive Size command from the Configure Group of the DOS Stacker Tool
Box I received a message that my Stacker Drive was already at or near its
maximum and could not be increased.  I thought Stacker drives could go up to 2
gigabytes?  What's the problem?

Joe DiCostanzo/NY

#: 41376 S4/Stacker 3.1
    06-Dec-93  11:06:53
Sb: Stacvol files Problems
Fm: andrei grant 100120,1711
To: ALL

I have tried to install DOS 6.2 on my system with the upgrade but had immense
problems, I've tried to install with 62STAC.EXE but to no avail. So I tried to
upgrade with an uncompressed ver of 6.2 dos but this seemed to lose me access
to my STACVOL hidden files. Which are still safe but I cannot access them how
do I recover them ANYBODY HELP ME as far as I can see I will only have one
option of formatting my HD, & I don't want to do this.

HELP PLEASE      

#: 41377 S4/Stacker 3.1
    06-Dec-93  11:46:47
Sb: Windows for Workgroups
Fm: Jerry Craig Jackson 76460,2047
To: SYSOP (X)

As a devoted Stacker user I was extremely disappointed to learn that the
Windows utilities in Stacker 3.1 will not work in WFWG using 32-bit file
access.
Please release a patch to correct this problem as I would much prefer to use
Stacker 3.1 for my disk compression vs. DoubleSpace. Please let me know if
anything is planned so I may act accordingly. Thankyou.




#: 41386 S4/Stacker 3.1
    06-Dec-93  16:50:20
Sb: dos 6.2
Fm: Dave Hunter 75126,62
To: Stac Electronics 75300,2755 (X)

I recently did the step up from DOS 6 to DOS 6.2. After this was done I noticed
a high rate of cross allocated files.  I have talked to other people who had
the same problem. ie: ALREADY RUNNING STACKER 3.1 THEN UPGRADING TO DOS. The
only variable seemed to DOS 6.2. I don't know if this helps anyone else, but I
tried a full re-stack after I had the problems and haven't had them since. An
interesting side note is that all the files that were cross allocated were in
my windows subdirectory. Possible Smartdrv conflict?? Anyway, everything seems
fine now, either I got lucky and guessed a fix, or it's waiting to crash on me
again!

Dave

