My new box can be booted successfully with Warp floppies, and not quite booted
from the SCSI HD.

I am wondering whether the apparent success is due to IBMINT13.I13 rather than
AICU320.ADD. e.g.:-

When booting with floppies and using Tedit to alter and save files on the SCSI
HD, is the I13 or the AIC driver the enabler?

When booting from SCSI HD and being told that the AIC driver failed to load yet
seeing the autocheck report and all the basedevs, devices and IFSs scroll down
the screen, is the I13 or AIC driver the enabler?

johnsuth@nospam.com.au wrote:
Remove the I13 driver, and you will know it.
Normally it should not be included in the CONFIG.SYS of installed systems.

Furthermore you will know it from the speed. The I13 driver is
incredibly slow.

And last but not least there are several restrictions of the I13 driver.
It only works on small disks.


Marcel

In <485bb648$0$7542$9b4e6d93@newsspool1.arcor-online.net>, =?ISO-8859-1?Q?Marcel_M=FCller?= <news.5.maazl@spamgourmet.org> writes:

Well, that showed that AIC was not loaded and that the 1GB partition almost
boots on the I13 driver.

As the box is primarily for Win and secondarily for Warp, I would be happy to
run Warp on the I13 driver if that is possible. I wil start a new thread on
this.

johnsuth@nospam.com.au wrote:
You don't want to do that.

The I13 driver brings you back 386 feeling even on recent hardware. It
is really slow, because it cannot do anything in parallel.


Marcel

Clarify please?

Marcel Müller wrote:
We are talking about Warp 4 and not MCP2 here, right? I have AICU160 running
just fine as far as I can tell on MCP2 latest XC05 Fix Pack and everything. I
have a copy of AICU320.ADD but have not chosen to go toward that level yet.

Thanks.

--


--> Sleep well; OS2's still awake!

Mike Luther

In <eEr7k.2150$Fj5.1648@newsfe23.lga>, Mike Luther <mike.luther@ziplog.com> writes:

We are talking MCP2 and the drive was previously running with an AICU160
controller. The problem arose on moving it to a newer box.