home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 9 Archive
/
09-Archive.zip
/
diunp303.zip
/
read.me
< prev
Wrap
Text File
|
1997-06-15
|
3KB
|
74 lines
DIUNPACK tips for new users...
What it is?:
------------
It reads disk images created with the savedskf from IBM. The images can
be on floppy, hard drive or across a lan...
What use is it?:
----------------
It allows copying all disk images of a fixpak release onto your hard
drive. Then by using a CID install, the fixpak can be applied easier,
quicker...
What are the gottchas?
----------------------
DIUNPACK is an incomplete IBM internal project. It all works, but
doesnot have ANY CRC error checking while reading the images. That is
to say, it can incorrectly read a file and you and your system will
never know it, until you're finished installing the fixpak...
How to use it?
--------------
Execute: DIUNPACK /?
What about the CID install?
---------------------------
Find and read the file README.CID on disk#2 of your kicker diskettes.
It's all there...
Is there an alternative to using DIUNPACK?
------------------------------------------
Yup, but it only works from floppy (SLOW) or a ramdrive setup to look like a
floppy (FAST). Put the desired image in the floppy drive and use:
XCOPY source: destination: /h/o/t/s/e/r/v
Can you give me a brief run down?
---------------------------------
Certainly... I downloaded all 17 disk images of fixpak #29 from the
internet. Setup a ramdisk that looked like a floppy (SVDisk 1.18) and
loaddskf'ed them on at a time to the floppy. After getting them on the
floppy I executed XCOPY E: C:\FIXPAK /h/o/t/s/e/r/v on each image until
I was done. Then I did the same to disk #2 of the kicker (csf install
disk). I then moved to C:FIXPAK and edited the RESPONSE.FIL to reflect
my system setup. When finished it looked like this:
:FLAGS REPLACE_PROTECTED REPLACE_NEWER
:SOURCE C:\FIXPAK
:SERVICE
:SYSLEVEL C:\OS2\INSTALL\SYSLEVEL.OS2
:ARCHIVE \ARCHIVE
:SERVICE
:SYSLEVEL C:\MMOS2\INSTALL\SYSLEVEL.MPM
:ARCHIVE \ARCHIVEM
Then from the FIXPAK directory I executed:
fservice /s:c:\fixpak /r:c:\fixpak\response.fil /l1:c:\service.log /sf:1
And sat back and watched the fixpak be applied. Eventually, I got up
and grabbed a beer as FP29 is a BIG one!
Anyway, applying a fixpak this way is fast and painless.
BTW and a bit BTW too! If you erased/deleted your archive directories
from the previous fixpak, then be sure to delete LOGF0000.XXX and
LOGSTART.XXX from any and all directories of the system being updated.
Otherwise the FP will not be applied!
Have fun!