Category : Tutorials + Patches
Archive   : STAC0694.ZIP
Filename : 3703.TXT

 
Output of file : 3703.TXT contained in archive : STAC0694.ZIP
-----------------------------------------------------------------
STACKER NOTE STACKER NOTE
MOUNT ID WRITE ERROR
(Applies to Stacker 3.0 & 3.1 for Windows & DOS)
STAC FAX 3703 (01-27-1994)
-----------------------------------------------------------------

BACKGROUND

If the Stacker device driver cannot successfully write the “mount
ID” to a STACVOL file, you will get the error message "Mount ID
Write Error." Two situations can cause this error:

I. The STACVOL file resides on a Hard Card whose driver loads
after Stacker attempts to mount the STACVOL file.
II. The STACVOL file resides on a drive with media errors.

This document is organized into two procedures. Complete
Procedure I if the error occurs on a Hard Card. Otherwise,
complete Procedure II.

PROCEDURE I: HARD CARD DRIVER LOADS AFTER STACKER

If the "Mount ID Write Error" occurs on a Hard Card, then
complete the appropriate steps for your version of Stacker.
Otherwise, complete Procedure II.

HARD CARDS AND STACKER 3.0


If you use Stacker 3.0, ensure that the Hard Card device driver
loads before the Stacker device driver in the CONFIG.SYS file:

1. Use any text editor to edit your CONFIG.SYS file.
2. If the Hard Card device driver appears after the Stacker
device driver, move it before the Stacker device driver
line. Otherwise, complete Procedure II.
3. Save the file and exit to DOS.
4. Restart your computer. The compressed Hard Card should
mount properly without write protection.

HARD CARDS AND STACKER 3.1


If you use Stacker 3.1, it is not possible to load the Hard Card
device driver before the pre-loading Stacker device driver. For
details on this error with Stacker 3.1, refer to Stacfax 31020.

PROCEDURE II: THE STACVOL FILE RESIDES ON A DRIVE WITH MEDIA
ERRORS

If you have completed Procedure I and the "Mount ID Write Error"
persists, or if the error is occurring on a hard disk that is not
a Hard Card, then a physical hard drive flaw is the most likely
cause of the error.

To detect and correct damaged or unreadable areas of your hard
drive, you need to run a disk repair utility, such as Norton
Utilities Calibrate, PC Tools DiskFix, or SpinRite. See document
# 3404, "Using Surface Scan Utilities with Stacker," for more
information.

Persistent errors may indicate a hardware failure in the hard
drive controller, the drive controller cable, the motherboard, or
the hard drive itself. Have a qualified repair technician check
your system.

-----------------------------------------------------------------
Copyright 1994 Stac Electronics


  3 Responses to “Category : Tutorials + Patches
Archive   : STAC0694.ZIP
Filename : 3703.TXT

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/