🚀 go-pugleaf

In article <c0.9w.2G2ymz$03t@picard.cds-inc.com>,
 <benson@cds-inc.com.nospam> wrote:
>In <c1.0.2G2kkW$Q0u@freedom2.express.net>, os2@mistik.express.net (Mustafa Soysal MS57) writes:
>[snip]
>>>Once you get the utility disks set up (there is a program to do that 
>>                  *************
>>
>>I am concerned about this terminology.  If these are the very same disks
>>generated from the system folder (3 of them) I rather not mess with
>>them.  They destroy my disks since the disks are greater than 1GB.  As a
>>result I have to low level format the disks which takes several hours
>>for each.
>
>Well, the included utility only updates the utility disks built from Warp v3 or
>Warp v4.   There are so many different ways that boot disks could be made
>that it isn't really feasible to programatically update each different variation
>with the required files.  Also, if BA/2 were to build the boot disks itself, it
>may not work across different versions or even different configurations of OS/2.
>That said, just make sure the following files are loaded by config.sys :
>  1) Driver for your SCSI adapter
>  2) OS2SCSI.DMD
>  3) BTSSCSI.SYS
>..and the remaining BA/2 files can go on a different disk.  This assumes you
>are using a SCSI tape, of course.  If using a Zip/Jaz/Etc. you will need
>drivers for those and can omit the BTSSCSI.SYS statement from the config.sys.

Yes, I am using a SCSI tape.

>
>>The procedure looks fair enough except for the "utility disks" part, not
>>even getting into space problems with those utility boot disks.
>>
>>Isn't there a way you can do this with the "Installation Disks" or even
>>Kicker Disks?
>
>Yes, but the problem there is that neither the installation disks or the CD-ROM
>kicker disks include any additional utilities (FDISK, format, chkdsk, etc.) and
>therefore would be of limited use.  You can of course make those disks by
>hand, which would be no more difficult that what you would do for GTAK, for

Well, I don't use GTAK that way.  This would be the advantage of using
your program.  I tried setting up the utility disks with the GTAK
drivers, and ran into space problems on those disks.  When I got around
that, it didn't run.  It needs a bunch of DLLs and they don't load for
some reason.  If you get them all in, then it tips over the NLS support
files etc etc., I eventually gave up the never ending modifications to
make it work.

For a total restore, I reinstall the base, install the gtak stuff,
reboot, get the zip files from tape onto disk, reboot into installation
command prompt, unzip the files, then reboot to the restored system.
(leaving out the formatting and partitioning part which can be done as a
part of the first base install).

Hand modifying boot disks don't work too well, that's why I don't want to
spend time fiddling with making those bootdisks myself.

>example.   As for space problems, there isn't a problem with the standard utility
>diskettes.  If other stuff has been added, then there might be a space conflict 
>obviously. 

Well, the standard utility diskette runtime can't really deal too well
with greater than 1GB disks.  However, I just switched to BIOS
translation, and the situation might be different now.

>
>Brad

Best Regards,

Mustafa Soysal

--
-------------------------------------------------------------------------------
Mustafa Soysal               (313) 741-1844 Voice                      TeamOS/2
MISTIK Systems               (313) 741-1937 Fax          Author of UnTieCom(tm)
PO Box 7064                                        Authorized Motorola Reseller
Ann Arbor, MI 48107-7064, USA                            os2@mistik.express.net
               Online catalog:  http://www.express.net/mistik/
-------------------------------------------------------------------------------