Text 846, 105 rader
Skriven 2007-10-26 08:11:28 av Mike Luther (1:117/3001.0)
     Kommentar till en text av Warp 4 users
Ärende: DaniS506.ADD
====================
Just trying to help here.

If you are using or want to use DaniS506.ADD with Warp 4, you might want to
keep track of something.  It has nothing to do with any error in Dani's code.

Because of the changes in the DaniS506.ADD for the version starting with 1.8.0
which will not work with the IBMIDE and IBMATAPI drivers, be careful.  It is
possible to still use the DaniS506.ADD and rename it to IBM1S506.ADD and keep
your CONFIG.SYS file in the original composition. In fact, the 1.8.0 upward
will actually still work that way, although per her documentation logging
operations for the utilities may not be what you need, if you need that.

However, watch out for other problems using these tools when you make the
Utility Diskette emergency boot floppies.  Especially if you are using any of
the Adaptec SCSI device drivers.  As you may or may not know, the Adaptec SCSI
device drivers of the AIC7870 and AIC78U2 and AICU160.ADD were modified several
times to fix several problems during the time when Warp 4 was offered.  It is
possible that you may have changed one of these drivers out without passing
through the Warp 4 Fix Pack levels on beyond FP15, to fix problems which
efforts were made to help people with beyond FP15 here.

But the size of these Adaptec device driver files grew substantially in the
process.  They grew so large that with FP15 and Warp 4 if using the Adaptec
SCSI equipment that you could not successfully build the Utility Diskettes
because the second disk, DISK 01, ran out of room.  As far as I know, this
whole issue was never fixed by IBM by changes in the program BOOTDISK.EXE which
makes these diskettes, in the OS2\INSTALL directory, until at least FP16,  And
it is my recall that in some variations of this, the final 'fix' for this
wasn't available until FP17 for Warp4.

The final fix for this is 'simple', but many may not know how.  You will get a
warning when creating the second diskette which has the Utility Diskette
CONFIG.SYS, SNOOP.LST and device drivers on it, that it has run out of space. 
At that point, you take the diskette being created out of the floppy drive. 
You place it in another computer floppy drive and delete unneeded Adaptec
device drivers, such as the AHA15, AHA16 and AHA17 device drivers you will not
need.  When done, you put the floppy back in the drive you are using to build
the diskettes.  You simply click on the OK button.  The build process will
continue.

However .. as I have found out, if you are using DaniS506.ADD that you have
renamed to IBM1S506.ADD, or used it with the DaniS506.ADD name and modified
your CONFIG.SYS file on your hard drive, because you need it,watch out!  You
just set yourself up for failure to boot issues with the Utility Diskette
package.  The only way, in some cases, you can get an emergency diskette boot
run to work, that I have found, which needs the DaniS506.ADD is to use the
renamed file as IBM1S506.ADD.  Which also still uses the IBMIDE and IBMATAPI
files.  This, per my research, limits you to the use of not higher than her 1.7
series of releases, which ended recently.  Although I have a library of 'last
working' such things, I'm not sure you can just get the 1.7 latest off Hobbs
and such any longer either.

You get into this conundrum when using the option, as you must, to Copy The
Files From the Hard Disk during the diskette creation process.

OK, but as well, the IBM diskette creation program also knows nothing about the
switcheroo of ATAPI drivers needed for the 1.8 level of Dani's code.  And even
with the renamed 1.7 versions of it will contribute, as I have found, to fatal
'errors' leading to the crash which results in the warning, "OS/2 is unable to
operate your hard drive ..."

This is not at all the issue of hard drive partitions sizes and so on that does
this here.  To fix it, you must also go into the CONFIG.SYS which has been
created on this Disk 1, the SECOND diskette.  You must remove the line in it
for each device driver you took off this diskette to get room for the larger
Adaptec device drivers.  Then you must also edit the SNOOP.LST to remove the
snoop names for the class of SCSI drivers you took out as well, the AHA15,
AHA16 and AHA17 snoop items.

That done, the glitch will go away and your newly created Utility Diskette
floppies will finish the boot run for you.  At least that has been the case
with three different incantations of Warp 4 Fix Pack 17 systems I've done this
on at this point.

You might also note, that the IBM utility does not know anything at all about
the Adaptec 29160 driver level.  If you build the floppies for this level
system, it will blindly assume that you are using the U2 type code.  In this
case you will have to remove at least one of the AIC7870 or AIC78U2 device
drivers to even get room on the floppy for the later version AICU160.ADD
driver.  Then you will have to place the proper device driver name for it by
hand in the CONFIG.SYS file on the boot diskette.  You won't have to modify the
SNOOP.LST for it though, in that the snoop list for all these larger drivers
seems generic as to what it is looking for in whatever is present.

Lastly, be very careful that as well, in your final incantation of all this,
when you are SURE you are all ok, you need to go in and run the OS/2 archive
installation utility ARCHINST from a command line.  That will go back and
change the entire floor emergency boot operation for your OS/2 operation to the
proper device drivers and CONFIG.SYS so that at the <ALT F1> emergency boot run
from the OS/2 blob at the startup,that you will get a booted box to the command
line that way.

Just trying to help here.  As you can see, there is a LOT of stuff here that is
just some of the very real reasons you really need to go through the Fix Pack
17 if you want to keep using Warp 4 for more modern equipment.


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001



--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)