#: 40437 S2/Stacker 1 and 2
    24-Nov-93  14:24:30
Sb: #Crosslinked Files
Fm: Stac Electronics 75300,2755
To: Mark Treadwell 73700,3344 (X)

Mark,

I have a record of your message but no follow up.  Were you working with any
one on this ?  Else i'll get started on looking into your problem.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40653 S2/Stacker 1 and 2
    27-Nov-93  22:26:27
Sb: #40437-#Crosslinked Files
Fm: Mark Treadwell 73700,3344
To: Stac Electronics 75300,2755 (X)

Keith,

No, I wasn't working with anyone on it.  It is still occuring.

Regards --- Mark



There is 1 Reply.

#: 40886 S2/Stacker 1 and 2
    30-Nov-93  18:48:15
Sb: #40653-Crosslinked Files
Fm: Stac Electronics 75300,2755
To: Mark Treadwell 73700,3344 (X)

Mark,

Ok, let me look over your information and make some suggestions.

Keith Dunlea, Stac Tech Support

#: 40473 S2/Stacker 1 and 2
    24-Nov-93  17:56:01
Sb: #STAC 2.0 FAT Integ.
Fm: Stac Electronics 75300,2755
To: Avi Lior 71033,40 (X)

Avi,

Check from v3 will work but its not recommended.  You should update the drive
to Stacker 3.0 instead then use Check.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40541 S2/Stacker 1 and 2
    25-Nov-93  08:40:25
Sb: #40473-#STAC 2.0 FAT Integ.
Fm: Avi Lior 71033,40
To: Stac Electronics 75300,2755 (X)

Hi Keith,

>Check from v3 will work but its not recommended.  You should update the drive
to Stacker 3.0 instead then use Check.

OK but I think we are going on the wrong path here.  I still have a problem
which I want to solve with my STAC 2.  The STAC utilities report that I have a
FAT integrity problem that I should use CHKDSK and or a disk fix utility to
repair.  However, chkdsk and Norton Disk Doctor do not see an error so they
can't fix it.  What shall I do next?  I am dead in the water with that
machine...

Thanx in Advance, Avi.

There are 2 Replies.

#: 40587 S2/Stacker 1 and 2
    26-Nov-93  16:55:23
Sb: #40541-#STAC 2.0 FAT Integ.
Fm: Avi Lior 71033,40
To: Avi Lior 71033,40 (X)

Hi Keith,

I posted the following message but I didn't get a reply, in case you didn't
receive the message its included here:

>Check from v3 will work but its not recommended.  You should update the drive
to Stacker 3.0 instead then use Check.

OK but I think we are going on the wrong path here.  I still have a problem
which I want to solve with my STAC 2.  The STAC utilities report that I have a
FAT integrity problem that I should use CHKDSK and or a disk fix utility to
repair.  However, chkdsk and Norton Disk Doctor do not see an error so they
can't fix it.  What shall I do next?  I am dead in the water with that
machine...

Thanx in Advance, Avi.

There is 1 Reply.

#: 40613 S2/Stacker 1 and 2
    27-Nov-93  02:54:00
Sb: #40587-#STAC 2.0 FAT Integ.
Fm: Edward Nutter [Stac] 75330,2222
To: Avi Lior 71033,40 (X)

Avi,

This is a four day weekend at Stac.  Keith won't be in until Monday.  I'm just
checking in from home.

I suspect you've got something obscure, like a volume label attribute set on
some directory or file.  NDD won't always pick up such things. If you have
something specific from SCHECK or SDEFRAG that would help.  Error numbers and
messages are very useful.  Help us out.

Ed Nutter
Stac Product Support 

There is 1 Reply.

#: 40664 S2/Stacker 1 and 2
    28-Nov-93  10:53:32
Sb: #40613-#STAC 2.0 FAT Integ.
Fm: Avi Lior 71033,40
To: Edward Nutter [Stac] 75330,2222 (X)

Ed,

>This is a four day weekend at Stac.  Keith won't be in until Monday.  I'm just
checking in from home.<

Thanx for replying.  Sorry I forgot!! In Canada it was a normal work week.
Keith was replying within 24 hours of my posts so when I didn't hear from him I
re-posted.  I guess that is what happens when you provide a useful service,
your gone one day and you are missed.  (it may also have something to do with
my type A personality)

The following is a summary of the problem.  Keith would be reading this I
assume.

 -STAC 2.0
 -had lost clusters fixed them with chkdsk
 -SCHECK reports FAT Integerity errors ... use chkdsk to repair
 -chkdsk doesn't see any errors
 -ran SDEFRAG.  It reports error #6 and gives me instructions ....
 -followed instructions but NDD doesn't see these errors either.

I'm sure this is simple to fix.  In previous postings we seem to go on a
tangent about STAC 3.0 (I have both 2.0 and 3.0) and check vs. scheck.  But I
want to solve the problem using STAC 2.0 and then perhaps upgrade to 3.0.

Originally I reported a beep sound everytime I wrote a file to disk.  I think I
found the problem.  I belive it was Norton Anti Virus (NAV) that was causing
the beep sound.  I thought it was a virus.

There is 1 Reply.

#: 40716 S2/Stacker 1 and 2
    29-Nov-93  17:07:01
Sb: #40664-STAC 2.0 FAT Integ.
Fm: Edward Nutter [Stac] 75330,2222
To: Avi Lior 71033,40 (X)

Avi,

SDEFRAG error #6 is a read error while trying to read a directory.  If Disk
Doctor couldn't find the problem, you may want to use Calibrat (also part of
Norton Utilities) instead.  Download our technote 3404.txt for a detailed
explaination on using such repair utilities with Stacker.

Edward Nutter
Stac Electronics Product Support 

#: 40755 S2/Stacker 1 and 2
    29-Nov-93  20:01:42
Sb: #40541-#STAC 2.0 FAT Integ.
Fm: Stac Electronics 75300,2755
To: Avi Lior 71033,40 (X)

Avi,

Its possible Scheck v2.0 is posting an erroneous error message. Whats the
time/date stamp of the Scheck.exe utility in \Stacker ?

Sdefrag error #6 is a read errors.  This is reported when an error is detected
on the physical host.  Run NDD and Chkdsk on the host drive to check for
errors.  This could also be related to the Scheck errors your are seeing.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40926 S2/Stacker 1 and 2
    30-Nov-93  19:04:01
Sb: #40755-#STAC 2.0 FAT Integ.
Fm: Avi Lior 71033,40
To: Stac Electronics 75300,2755 (X)

Keith,

>>Its possible Scheck v2.0 is posting an erroneous error message. Whats the
time/date stamp of the Scheck.exe utility in \Stacker ?<<

I'll have to get back to you on this but I don't think this is the problem
because both Scheck and SDEFRAG report that I have FAT Integrity problems.

>> Sdefrag error #6 is a read errors.  This is reported when an error is
detected on the physical host.  Run NDD and Chkdsk on the host drive to check
for errors.  This could also be related to the Scheck errors your are seeing.<<

"Physical host" that is my unstacked drive ie, the drive I would get if I
booted up clean with out running STAC on which I would see the STACVOL.DSK file
after I unhide it using SATTRIB -s -h -r etc....  Well if that is it then I
already ran NDD and chkdsk with both not reporting any errors.  I also read
3404.txt and used Norton's CALIBR utility which reported no errors!!!

So that is where it's at.  I'll get back with the date of Scheck but I think we
need stronger medicine?.  What's the next step?

There is 1 Reply.

#: 41070 S2/Stacker 1 and 2
    01-Dec-93  19:03:35
Sb: #40926-#STAC 2.0 FAT Integ.
Fm: Roger Hicks 74250,1407
To: Avi Lior 71033,40 (X)

Avi;

What parameter switches did you use when you ran calibrat?

Thanks,

Keith Moon
STAC Product Support

There is 1 Reply.

#: 41074 S2/Stacker 1 and 2
    01-Dec-93  20:03:34
Sb: #41070-STAC 2.0 FAT Integ.
Fm: Avi Lior 71033,40
To: Roger Hicks 74250,1407 (X)

Hi,

>>What parameter switches did you use when you ran calibrat?

I used /noformat.

In a previous message I was asked what was the date on my SCHECK.  The date for
SCHECK is 02-26-92.

#: 40474 S2/Stacker 1 and 2
    24-Nov-93  17:56:03
Sb: partitioning a drive
Fm: Stac Electronics 75300,2755
To: Steve Frank 73437,1232 (X)

Steve,

Stacker will work fine with this setup.  No special considerations

Keith Dunlea, Stac Tech Support

#: 40441 S2/Stacker 1 and 2
    24-Nov-93  15:58:22
Sb: #FREE MEMORY TO SMALL
Fm: CHUCK C. BURGER 72773,312
To: STACKER

I HAVE A 386 WITH TO HARD DRIVE AND RUNNING A WINDOWS ENVIRONMENT.  I RECENTLY
PURCHASE A PROGRAM THAT REQUIRES 535K OF FREE MEMORY.  THE MOST I HAVE BEEN
ABLE TO ACHIEVE IS 529K.  STACKER HAS NOT ALLOWED ME TO INCREASE.  I HAVE
DEVICES HIGH AND RUNNING 386 ENHANCED. MY VERSION OF STACKER IS 2.0  SERIAL
#S200T1063519.  I WILL PROVIDE ANY ADDITIONAL INFOMATION ABOUT MY SYSTEM.  I
HAVE REACHED MY LIMIT ON DOS KNOWLEDGE.  THANKS FOR THE HELP.

There is 1 Reply.

#: 40733 S2/Stacker 1 and 2
    29-Nov-93  19:59:33
Sb: #40441-FREE MEMORY TO SMALL
Fm: Stac Electronics 75300,2755
To: CHUCK C. BURGER 72773,312 (X)

Chuck,

Stacker will not interfer with the optimization of your memory. We are a device
driver which requires about 38k of RAM.  This can be loaded high with your
memory manager.

Sounds like you need to optimize your memory.   First step is the refer to your
memory manager manual.  Second we have tech notes posted in lib:3 which may
help.  Tech note 2101.txt - 2106.txt

Keith Dunlea, Stac Tech Support

#: 40534 S2/Stacker 1 and 2
    25-Nov-93  00:40:11
Sb: #CONVENTIONAL MEMORY
Fm: Darren D. Dow 74640,2637
To: WHOEVER CAN HELP

I have Stacker version 2.0.  I need to free up 602K of conventional memory for
a new game, but I have only been able to get 595K available.  I am using MS DOS
5.0.  My CONFIG.SYS is loading the STACKER devices high.  DOS is also being
loaded high.  When I use the MEM /C command I find that STACKER is still
consuming 41K of memory.  I am not booting with an autoexec, so no other
programs are resident.  I would really appreciate any advice on this since I
can no longer return the game. 

There is 1 Reply.

#: 40752 S2/Stacker 1 and 2
    29-Nov-93  20:01:16
Sb: #40534-CONVENTIONAL MEMORY
Fm: Stac Electronics 75300,2755
To: Darren D. Dow 74640,2637 (X)

Darren,

Download tech note 2102.txt in lib:3 which gives tips on using Emm386.exe to
load Stacker high.

Keith Dunlea, Stac Tech Support

#: 40574 S2/Stacker 1 and 2
    26-Nov-93  09:49:33
Sb: #Stacker vs Doublespace
Fm: DON A. KOENIGSBERG 70720,527
To: all

I am currently a DOS 5 user.  I own a 386SX clone and I am not sure whether or
not to upgrade to DOS 6.2.  I currently have Stacker 2.0 with its coprocessor.
I also own QEMM.  Does anyone know If I would benefit from the upgrade.
Thanks.s

Don K.
    

There is 1 Reply.

#: 40773 S2/Stacker 1 and 2
    29-Nov-93  20:03:17
Sb: #40574-Stacker vs Doublespace
Fm: Stac Electronics 75300,2755
To: DON A. KOENIGSBERG 70720,527 (X)

Don,

If you upgrade to DOS 6.2 you may consider Stacker 3.1 as well.  Our latest
includes many new features over v2 plus some additions for MS DOS 6.   See
STAC31.REL and STAC31.ADV in lib:2 for more information

Keith Dunlea, Stac Tech Support

#: 40580 S2/Stacker 1 and 2
    26-Nov-93  13:04:08
Sb: #Stacker 2.0 Problem
Fm: Christopher Brown 76236,276
To: All

Hello, I am having some trouble with my Stacker drive.

I think the original problem occured when I ran the drive out of space.  The
program I was in reported an inability to write to drive d: (the stacked
drive), and generated a database error.

I went out and ran chkdsk, which found 1 lost cluster, and repaired it.  It
also reported that a certain file, generated in the offending program, was of
an incorrect length.  I repaired this also, then deleted the file - both the
original and the one created by chkdsk.

Chkdsk now reports no problems.  However, when I use the SCheck utility, it
still reports an incorrect file length, and tells me to use chkdsk to repair it
- which is pointless as chkdsk doesn't acknowledge the existence of such a
problem.

Scarier still, when I entered SDefrag to view the level of fragmentation, it
came up with the message "Fatal Error: Error #14 Chkdsk error found" while
doing its FAT check.

So what's the story?  Everything seems to be rolling along despite this, but it
is making me nervous.  Any help/information that could be provided would be
greatly appreciated.

                                                Chris

There is 1 Reply.

#: 40776 S2/Stacker 1 and 2
    29-Nov-93  20:03:31
Sb: #40580-#Stacker 2.0 Problem
Fm: Stac Electronics 75300,2755
To: Christopher Brown 76236,276 (X)

Christopher,

Try booting with just Stacker loaded and retry Scheck and Sdefrag. This will
test for a tsr conflict with the error reporting

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 40785 S2/Stacker 1 and 2
    29-Nov-93  21:06:25
Sb: #40776-#Stacker 2.0 Problem
Fm: CSB 76236,276
To: Stac Electronics 75300,2755 (X)

Keith,

Thanks for the response.  I have no TSR's in particular running - but... the
error message went away!

Although I had tried a cold boot prior to sending my last message, with no
luck, when I turned it off overnight the error messages vanished. This little
bit of PC behavior never ceases to amaze me.

Given that the messages are not recurring, do you advise running further
diagnostics, or can I assume all is well?  Any thoughts on what happened in the
first place?

Again, I appreciate your quick response.

                                                            Chris

There is 1 Reply.

#: 41001 S2/Stacker 1 and 2
    01-Dec-93  15:31:50
Sb: #40785-Stacker 2.0 Problem
Fm: Stac Electronics 75300,2755
To: CSB 76236,276 (X)

Chris.

Sometimes, under version 2, you need to reboot the machine after running a disk
utility or scheck /f. Its also possible scheck/f didn't update the drive map
and the error continued to be reported.   Try using the lastest copy of Scheck
v2 that is posted in LIB:1   This is bit more robust Keith Dunlea, Stac Tech
Support

#: 40592 S2/Stacker 1 and 2
    26-Nov-93  19:41:53
Sb: EXPANSION OF FREE MEMORY
Fm: CHUCK C. BURGER 72773,312
To: ED LISLE 73164,2746

ED, I NEED TO EXPAND THE AMOUNT OF FREE MEMORY I CURRENTLY HAVE FROM 529K TO
55OK.  I AM USING STACKER 2.0 AND HAVE MADE CHANGES TO MY CONFIG AND AUTOEXE TO
MOVE AS MUCH AS POSSIBLE TO HIGH MEMORY IN DOS.  THIS HAS NOT BE WORKED. DO YOU
HAVE ANY SUGGESTIONS OR HAVE THERE BEEN INFORMATION RELEASED TO SOLVE THIS
PROBLEM.  I HAVE A DOS PROGRAM WHICH WILL NOT RUN WITHOUT THE INCREASE IN
MEMORY. THANKS

#: 40599 S2/Stacker 1 and 2
    26-Nov-93  23:43:20
Sb: #Help with MC-16 Install
Fm: David Heggie 70731,516
To: all

It's a long story but I've wound up with an MC-16 Coprocessor and Stacker
software for the AT-16 model (all legitimate and registered). INSTALL takes me
down the AT-16 path when I need to be launched on the MC-16 route.  INSTALL.COM
is a binary so can't edit it. Is there a copy of the MC-16 INSTALL program I
can download from the library?  Can someone send me the file I need to do the
install? I'm upgrading from Stacker Ver 1.10 to 2.01 enroute to 3.0 which I
have in hand.  Yep, plan to go to 3.1 when I get that far. Any assistance will
be appreciated.

There is 1 Reply.

#: 40612 S2/Stacker 1 and 2
    27-Nov-93  02:44:54
Sb: #40599-Help with MC-16 Install
Fm: Edward Nutter [Stac] 75330,2222
To: David Heggie 70731,516 (X)

David,

I also answered your question about this in the Non-Technical area.  Use: SETUP
/MC
This invokes the MD/16 card install routines.

Ed Nutter
Stac Product Support

#: 40608 S2/Stacker 1 and 2
    27-Nov-93  01:18:22
Sb: #Stacker Fatal Error
Fm: Robert Newman 73521,3175
To: ALL

I have a problem with stacker 2.0.  It has worked flawlessly until the oth day.
When I run the optimizer from the STAC program, I get a red box indicating a
fatal error.  It tells me to run CHECK.  When I run CHECK it finds no errors, a
complete disk scan shows no bad sectors.  When I run the optimizer again I get
the same error. What's the problem?  I seem to be able to access the drive O.K.
but I won't be able to optimize it. Any suggestions? Thanks, Robert.


There is 1 Reply.

#: 40872 S2/Stacker 1 and 2
    30-Nov-93  18:47:29
Sb: #40608-Stacker Fatal Error
Fm: Stac Electronics 75300,2755
To: Robert Newman 73521,3175

Robert,

Whats the error message ?

Keith Dunlea, Stac Tech Support

#: 40648 S2/Stacker 1 and 2
    27-Nov-93  21:21:51
Sb: problem with emm386
Fm: Steven Rosen 71620,2564
To: sysop (X)

I have a problem with Stacker 2.00.1 conflicting with DOS 6's 386emm.exe. At
boot I get "Warning: EMS Driver not found. Using DOS memory. 47024 Bites used
during itialization at 056C:0000."

I'm not using MS's doublespace.

Most of my DOS and Windows programs work OK but  Reveal's Jurassic Park gives
me a message that it can't find the memory manager which is in both the DOS and
the E:\Stacker directories. The game won't load.

#: 40699 S2/Stacker 1 and 2
    29-Nov-93  01:11:35
Sb: #Stacker and Dos 6
Fm: Edward MacKinnon 73710,1564
To: Tech. Support

I have Stacker 2 and a 120 MB hd partitioned under Dos5 When I upgraded to DOS
6 it will not load the Stacked drive. Is there any way to load this without
reformatting the hard drive?  

There is 1 Reply.

#: 40910 S2/Stacker 1 and 2
    30-Nov-93  18:49:41
Sb: #40699-Stacker and Dos 6
Fm: Stac Electronics 75300,2755
To: Edward MacKinnon 73710,1564 (X)

Edward,

make sure you have the appropiate stacker lines in your config.sys

Keith Dunlea, Stac Tech Support

#: 40709 S2/Stacker 1 and 2
    29-Nov-93  14:55:46
Sb: #Bad sector problem
Fm: Jed Rothwell 72240,1256
To:  75300,2755 (X)

I am running a hardware Stacker, vers. 2.0. How do you map out a bad sector? I
got one during a tape backup and confirmed it with a COPY command. I did an
SDEFRAG and the problem went away, but I bet it will show up again later. Is
there a way to go through all unused sectors and map out a weak or bad one, the
way a FORMAT is supposed to do (but seldom does)?

- Jed

There is 1 Reply.

#: 40914 S2/Stacker 1 and 2
    30-Nov-93  18:49:56
Sb: #40709-#Bad sector problem
Fm: Stac Electronics 75300,2755
To: Jed Rothwell 72240,1256 (X)

Jed,

see tech note 3404.txt in lib:3 for details on using disk utilities

Keith Dunlea, Stac Tech Support

There are 2 Replies.

#: 41023 S2/Stacker 1 and 2
    01-Dec-93  16:00:26
Sb: #40914-Bad sector problem
Fm: Jed Rothwell 72240,1256
To: Stac Electronics 75300,2755 (X)

Thanks. Will do.

- Jed

#: 41025 S2/Stacker 1 and 2
    01-Dec-93  16:09:55
Sb: #40914-#Bad sector problem
Fm: Jed Rothwell 72240,1256
To: Stac Electronics 75300,2755 (X)

Wow! Document 3403.TXT describes a real hard core clean up procedure. I guess I
better bite the bullet ("byte the bullet?") and do it. I have to get an updated
version of one of those utilities, it has been years since I did one... Sigh.

I suggest you add a statement to Document 3403.TXT along the following lines:

     "Be sure to back up your hard disk completely, first."

There's no harm in repeating *that* statement.

- Jed

There is 1 Reply.

#: 41149 S2/Stacker 1 and 2
    02-Dec-93  18:58:54
Sb: #41025-Bad sector problem
Fm: Stac Electronics 75300,2755
To: Jed Rothwell 72240,1256 (X)

Jed,

Thanks!  I'll pass on your suggestion to our tech writers.

Keith Dunlea, Stac Tech Support

#: 40710 S2/Stacker 1 and 2
    29-Nov-93  16:05:32
Sb: #Stac 2.0
Fm: Matthew Lockwood 70713,1012
To: Managment

Dear Stacker,

        Recently I purchased your Stacker 2.0.  At first, it was useful, but
now it is slowly ruining my system.  I am about to backup what I can and
reformat my HDD.  I hope there is some kind of upgrade that I could be sent
FREE, or some solution can be presented to me,  as I am very dissapointed with
your software.  I have twice had to boot up thru unconventional means due to
Stacker 2.0, and I'm ready to delete it and spread the bad word about it
around..

Sincerely,

Matthew Lockwood
Serial # b201b022015
 

There are 2 Replies.

#: 40728 S2/Stacker 1 and 2
    29-Nov-93  19:51:50
Sb: #40710-Stac 2.0
Fm: Avi Lior 71033,40
To: Matthew Lockwood 70713,1012

Matthew,

I'm not a part of the Stacker support team, but I read your letter and I had to
respond to it.

1) Don't post your serial number.

2) You don't have to threat "I'm ready to delete it and spread the bad word
about it around" ooooh... "not the bad word" <g>

I've been using Stac 2.0 and 3.0 for a long time now.  I had a couple of
problems and they have been resolved by Stac to my satisfaction.  Instead of
uttering threats perhaps you can post messages that describe your problems so
people can help you.  Then if you are still not satisfied, then constructive
messages to the right people and/or a phone call should get you results.

3) Why would you buy version 2.0 when 3.0 has been out for several months?

#: 40915 S2/Stacker 1 and 2
    30-Nov-93  18:50:00
Sb: #40710-Stac 2.0
Fm: Stac Electronics 75300,2755
To: Matthew Lockwood 70713,1012

Matthew,

If you just purhcased Stacker 2 , return it and purchase the latest version,
Stacker 3.1.  or upgrade to Stacker 3.1 for $49.95 plus /sh.

Stacker 2 could run slow on a slow machine, ie: low end 386, 286.

Keith Dunlea, Stac Tech Support

#: 40985 S2/Stacker 1 and 2
    01-Dec-93  11:01:33
Sb: #Stacker 2.0 HD compat
Fm: Mike Castrogiovanni 72704,40
To: Stac Elec.

Is Stacker 2.0 compatible with a Conner CFA340A(CP30344) 340 MB hard drive?
SCHECK finds lost sectors.  SDEFRAG reports a fatal error #64.  Norton 6.0 says
the drive checks out OK.  We had no problems here with the previous 130 MB
ST3144A Seagate hard drive and Stacker 2.0.  Ever since we put this new drive
in, we were NEVER able to get through SDEFRAG without a fatal error!  On the
other hand, the STACKed drive seems to work OK, but there are a lot of programs
we still haven't checked out.

Mike @ Network Communications
  

There is 1 Reply.

#: 41044 S2/Stacker 1 and 2
    01-Dec-93  19:01:10
Sb: #40985-Stacker 2.0 HD compat
Fm: Roger Hicks 74250,1407
To: Mike Castrogiovanni 72704,40 (X)

Mike;

There have been no reported issues with Conner drives in general. Make sure
CMOS setting are properly set for
the drive.

Thanks,

Keith Moon
STAC Product Support

#: 40988 S2/Stacker 1 and 2
    01-Dec-93  12:02:57
Sb: #Disk protected error
Fm: jorge bela 76450,2252
To: jorge bela 76450,2252 (X)

I have stacker 2.0 installed on my machine. Now I am getting a disk portected
error message for dirve c: I assume that this may be due to a pro problem with
Stacker. I called customer support, but they will only help me if I ODif I pay
a minimum of 20 dollars. I am a student and do not have the money to upgrade or
pay expensive customer support. Can anyone tell me if thei write protect error
is due to a Stacker error and how can i go to solve it?

Thanks.

Jorge 76450,2252

There is 1 Reply.

#: 41045 S2/Stacker 1 and 2
    01-Dec-93  19:01:16
Sb: #40988-Disk protected error
Fm: Roger Hicks 74250,1407
To: jorge bela 76450,2252

Jorge;

We write-protect your drive because we found some type of data integrity error.
to fix the drive, type "scheck /f". I do
strongly suggest upgrading to Stacker version 3.1 which would give you the
additional benefits of our 3rd generation
product and free live technical support.

Thanks,

Keith Moon
STAC Product Support

#: 41106 S2/Stacker 1 and 2
    02-Dec-93  08:08:17
Sb: #swaping new drives
Fm: Steve Frank 73437,1232
To: Sysop (X)

I installed an additional hard drive and have attempted to stack one of the new
partitions.  Below is the portion of config.sys before doing this:

  DEVICEHIGH=C:\STACKER\STACKER.COM /EMS c:\STACVOL.DSK d:\STACVOL.DSK @
  DEVICE=C:\STACKER\SSWAP.COM D:\STACVOL.DSK
  DEVICE=C:\STACKER\SSWAP.COM C:\STACVOL.DSK /SYNC

What I did was to create an empty drive, and this resulted in my 'problem'.  I
previously had drives C: and D: (the 'fake' disks) and E: and F: (the 'real'
ones containing the large stacker file).  I created four partitions on my new
drive (E: thru H:) and ended up with I: and J: as the 'real' drive.  I now have
drive.  My new 'fake' drive is K: and the real drive is E:.  I thought that I
could 'swap' these and make the fake drive E: and the real one K: by inserting
a line in config.sys:

  DEVICEHIGH=C:\STACKER\STACKER.COM /EMS C:\STACVOL.DSK D:\STACVOL.DSK @
E:\STACVOL.000
  DEVICE=C:\STACKER\SSWAP.COM e:\STACVOL.DSK  <<---  I added this line
  DEVICE=C:\STACKER\SSWAP.COM D:\STACVOL.DSK
  DEVICE=C:\STACKER\SSWAP.COM C:\STACVOL.DSK /SYNC

This resulted in an 'unable to swap' message during boot.

How can I swap the drives?  Or should I remove and restack 'with data'?

There are 2 Replies.

#: 41138 S2/Stacker 1 and 2
    02-Dec-93  18:29:15
Sb: #41106-swaping new drives
Fm: Roger Hicks 74250,1407
To: Steve Frank 73437,1232 (X)

Steve;

You should unstack and then restack using with data.


Thanks,

Keith Moon
STAC Product Support

#: 41150 S2/Stacker 1 and 2
    02-Dec-93  18:58:57
Sb: #41106-swaping new drives
Fm: Stac Electronics 75300,2755
To: Steve Frank 73437,1232

Steve,

  DEVICEHIGH=C:\STACKER\STACKER.COM /EMS C:\STACVOL.DSK D:\STACVOL.DSK @
E:\STACVOL.000
  DEVICE=C:\STACKER\SSWAP.COM e:\STACVOL.DSK  <<---  I added this line

You have the wrong file name, its E:\STACVOL.000

Keith Dunlea, Stac Tech Support

#: 41191 S2/Stacker 1 and 2
    02-Dec-93  21:28:19
Sb: #allocation errors
Fm: KYLE COLE 76150,2127
To: sysop (X)

HELP! I have a 300 meg ESDI with a stacker partition.  I was running windows
and the machine locked up.  When I rebooted the stacker drive would not come
up.  I kept getting an error message stating that the file size allocation
table didn't match.  I could not run any of the stacker software as the drive
wouldn't mount.  I ran chkdsk and it reported a cross linked cluster between
the stack.vol and another program.  I deleted the cross linked file and now I
get allocation erro on stac.vol with chkdsk.  I ran chkdsk /f but told it not
to convert lost clusters.  I am getting about 90 meg free on my c drive which
is about the sizeof the stac.vol file (which is still there) WHAT CAN I DO
  I will be devastated if I can not retreive my data. Please help.  If there
are no utillities available is there a service that can retrieve the data?
Thanks Kyle

There is 1 Reply.

#: 41234 S2/Stacker 1 and 2
    03-Dec-93  13:41:36
Sb: #41191-#allocation errors
Fm: Stac Electronics 75300,2755
To: KYLE COLE 76150,2127 (X)

Kyle,

We have a utility on our BBS which may help.  First run CHKDSK /F and make sure
no more corss-links exist.  Then go into the root directory and delete all
FILE000.CHK files.

Keith Dunlea, Stac Tech Support

There is 1 Reply.

#: 41246 S2/Stacker 1 and 2
    03-Dec-93  14:09:32
Sb: #41234-allocation errors
Fm: KYLE COLE 76150,2127
To: Stac Electronics 75300,2755 (X)

SO WHATS THE NAME OF THE UTILLITY?

#: 41193 S2/Stacker 1 and 2
    02-Dec-93  22:16:08
Sb: #Unknown error message
Fm: Tom Gyllenspetz 72667,1760
To: sysop (X)

Please I need help. I have tried to get an answer from Stac but so far only the
runaround! My PC is unusable until I get an answer....

I receive the following error message:

D:=C: STACVOLDSK Stacvol too fragmented - not mounted.

What is my remedy ? Did I loose the data? Why isn't this error message in my
manual?

Thanks

There is 1 Reply.

#: 41235 S2/Stacker 1 and 2
    03-Dec-93  13:41:44
Sb: #41193-Unknown error message
Fm: Stac Electronics 75300,2755
To: Tom Gyllenspetz 72667,1760

Tom,

At this point the Stacvol file has been created but its very fragmented. Please
do the following to correct the problem.

1. Check the drive for a file called Stacker.log. Type it to the screen and
remove any file listed with read/write errors. 2. From the Stacker diskette
type "sattrib -h -r -s c:\stacvol.dsk" to unhide the file then type "screate
c:\stacvol.dsk /p" to optimize the file and padd it to its full size. 3.Upon
completion reboot to access your Stacker drive.

Keith Dunlea, Stac Tech Support

#: 41213 S2/Stacker 1 and 2
    03-Dec-93  08:15:31
Sb: STAC 2.0 FAT Integ.
Fm: Avi Lior 71033,40
To: Stac Electronics 75300,2755 (X)

Keith,

I guess I'm addressing this to you since I started with you.  I've been trying
to get help here for two weeks.  After 11 messages I am still dead in the
water!!!  Is this not a STAC support forum?  Should I be calling STAC directly?

Here is a summary of events:

-from day one I report that SCHECK reports FAT integrity errors -from day one I
report that SDEFRAG also reports FAT integrity errors -from day one I report
that I've followed the remedies that both SCHECK and SDEFRAG suggest and that
CHKDSK and NDD do not see the errors -STAC (Ed Nutter?) recommends using
CALIBRATE and reading 3404.txt -CALIBRATE does not find any problems. -STAC
(Keith) suggest that perhaps that SCHECK that is out of date and reporting
errors falsely. Also in the same letter STAC suggests that the error is on the
physical host and I should run NDD and CHKDSK.  Which I already did even before
I came here for help (see above). -I return mail that I will send date of
SCHECK but didn't think that was the problem because both SCHECK and SDEFRAG
are reporting errors. SCHECK date is 02-26-92. -STAC (?) asks what switches I
used for CALIB.  I report back that I used \noformat.

So what do I do next?  Is it time to trash the STACVOL.DSK file?

#: 41227 S2/Stacker 1 and 2
    03-Dec-93  12:26:08
Sb: #Will 2.0 work w/ WIN 3.1
Fm: Ronald M. Specht 72702,2754
To: all

I have Stacker 2.0 (not installed).  Will it work with Windows 3.1?  Is there
anything that I'll need to setup differently than what the book says for
Windows 3.0?


There is 1 Reply.

#: 41259 S2/Stacker 1 and 2
    03-Dec-93  17:34:08
Sb: #41227-Will 2.0 work w/ WIN 3.1
Fm: Stac Electronics 75300,2755
To: Ronald M. Specht 72702,2754 (X)

Ronald,

Yes, Stacker 2 will work with Windows.  But if you have Stacker 3 why use ver
2.

Keith Dunlea, Stac Tech Support

#: 41355 S2/Stacker 1 and 2
    05-Dec-93  20:35:17
Sb: operating system
Fm: JIM MUSTARD 73040,2426
To: Sysop (X)

When my system normally boots, it is now saying "missing operating system".
Yet when I boot from the A drive and then check the base directory there is
both a command.com and the hidden io & msdos files.  Are they in the wrong dir
or what do you think gives.  I have dos 5.0 and stacker 2.0.  I am still using
my computer but now with a system disk always in drive a.  Any ideas? 

