Category : Tutorials + Patches
Archive   : TEC999.ZIP
Filename : TEC032.DOC

 
Output of file : TEC032.DOC contained in archive : TEC999.ZIP
___________________________________________________________________________
STACKER NOTE Stac Electronics Technical Note

SUBJECT: Installing the IBM Corrective Service Diskettes on a
"Stacked" hardisk.

Tec032- 3/26/92
Page 1 of 2
____________________________________________________________________________

The key to installing these new programs is to NOT boot up from the IBM
Corrective Service Diskettes (as the instructions indicate), but instead to
simply boot normally, thereby having the Stacker drives mounted and available.

1. Begin the process by inserting the first IBM Corrective Service Diskette
into the A: diskette drive (this procedure will not work from the B:
drive or any other external floppy drive). If you can only install from
your B: drive (due to broken A:, etc), you can use the ASSIGN command to
switch the drive letter specifications.

2. Run the 'AUTOEXEC' file. It contains the command 'UPDATE x' where 'x'
represents the number of Corrective Service Diskettes to be run from
the update package (UPDATE.COM is an IBM program on the first CSD).

3. The README file will automatically be displayed. Continue to press any
key until the end of the README file is reached.

4. At the prompt:

Enter your keyboard code: ( hit 'Enter' to accept the default of 'US').

5. At the prompt:

Enter the drive which contains DOS 5.0 files to be replaced: ( enter
the drive letter which contains the directory or directories you wish
to update and hit 'Enter').

6. The next information displayed will indicate whether the target drive is
or is not 'IBM DOS version 5.0'. This indicates the presence of the
DOS system files in the root directory of the drive.

If the following prompt appears:

"Target is IBM DOS version 5.0.
Do you want to replace the DOS files in all directories (Y/N)?"

Then hit 'Enter' to accept the default of 'Y'.


7. If the following prompt appears:

"Target is NOT IBM DOS version 5.0
Be sure to specify your IBM DOS 5.0 subdirectory.
Enter the target directory name (\path):"

Then enter the name of the DOS directory (including the '\').

The system will begin the automated process by first 'SYS'ing the drive
if the IBM system files were previously detected. It will then continue
by replacing the appropriate IBM DOS 5.0 files it can find in the root
directory and subdirectories.

8. The user will then be instructed to:

"Insert next IBM DOS Corrective Service Diskette into drive A:
Press any key to continue..."

This sequence will be repeated until all the Corrective Service Diskettes
have been processed and the various update programs copied to the
respective directories.

9. When the procedure is finished, the user will be prompted either to:

"Remove IBM DOS Corrective Service Diskette from drive A:
Press any key to restart system..."

or to choose:

"Another target directory name (Y/N)?" if updating a 'NON IBM DOS' drive.

10. If there are more drives or directories to update, the user then restarts
the procedure by changing to the diskette drive and re-running 'UPDATE x'
again, this time choosing a different drive letter or directory to update.
If you are "swapping" the C: drive with Stacker, then you will want to
to update the uncompressed/host drive as well. To see which drive is
swapping with C:, run SWAPMAP.


There have been sporadic problems reported with the UPDATE program hanging
the system when hitting 'Enter' after entering the drive letter to update. In
every instance the solution has been to remove the diskette, reboot the system
and restart the procedure once again. The second time, everything goes OK.
This problem is not destructive.



















  3 Responses to “Category : Tutorials + Patches
Archive   : TEC999.ZIP
Filename : TEC032.DOC

  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/