AICU320.ADD failed to load

I relocated a working SCSI hard drive to a new Supermicro X7DA8 mobo. It was
necessary to copy the appropriate driver for the mobo's AIC-7902W adapter to the
hard drive and edit the config file. I achieved this by creating boot floppies
which included the same driver. The hard drive then booted and the USB and IDE
drivers reported their successful loading to screen, but AICU320.add reported
failure to load with error code (c0003003h) and two rows of hex data.

The mystery is why the SCSI driver loaded from floppy but not from the hard
drive.

How do I persuade it to load from the hard drive?

johnsuth@nospam.com.au wrote in news:c1.2c.39NLdY$0O1@PC1.BIGPOND.COM
> I relocated a working SCSI hard drive to a new Supermicro X7DA8 mobo.
> It was necessary to copy the appropriate driver for the mobo's AIC-7902W
> adapter to the hard drive and edit the config file.
> I achieved this by creating boot floppies which included the same driver.

> The hard drive then booted

Where as before it didn't?

> and the USB and IDE drivers reported their successful loading to screen,
> but AICU320.add reported failure to load with error code (c0003003h)
> and two rows of hex data.

> The mystery is why the SCSI driver loaded from floppy but not from the hard
> drive.

Two different definitions of "loading". Copying is not the same as running it.
Presumably the driver crashed.

>
> How do I persuade it to load from the hard drive?

On 04/27/08 02:54 am johnsuth@nospam.com.au wrote:

> I relocated a working SCSI hard drive to a new Supermicro X7DA8 mobo. It was
> necessary to copy the appropriate driver for the mobo's AIC-7902W adapter to the
> hard drive and edit the config file. I achieved this by creating boot floppies
> which included the same driver. The hard drive then booted and the USB and IDE
> drivers reported their successful loading to screen, but AICU320.add reported
> failure to load with error code (c0003003h) and two rows of hex data.
>
> The mystery is why the SCSI driver loaded from floppy but not from the hard
> drive.
>
> How do I persuade it to load from the hard drive?


Since you are using a REAL operating system, you might do better to ask
in comp.os.os2.storage.

But you might check to see whether the sequence of SCSI and IDE drivers
is the same in the CONFIG.SYS on the hd as in the one on the floppy disk.

-=-
Perce

In <Ta8Rj.246$087.157@newsfe07.lga>, "Percival P. Cassidy" <nobody@notmyISP.net> writes:
>On 04/27/08 02:54 am johnsuth@nospam.com.au wrote:
>
>> I relocated a working SCSI hard drive to a new Supermicro X7DA8 mobo. It was
>> necessary to copy the appropriate driver for the mobo's AIC-7902W adapter to the
>> hard drive and edit the config file. I achieved this by creating boot floppies
>> which included the same driver. The hard drive then booted and the USB and IDE
>> drivers reported their successful loading to screen, but AICU320.add reported
>> failure to load with error code (c0003003h) and two rows of hex data.
>>
>> The mystery is why the SCSI driver loaded from floppy but not from the hard
>> drive.
>>
>> How do I persuade it to load from the hard drive?
>
>
>Since you are using a REAL operating system, you might do better to ask
>in comp.os.os2.storage.
>
>But you might check to see whether the sequence of SCSI and IDE drivers
>is the same in the CONFIG.SYS on the hd as in the one on the floppy disk.


FD has SCSI after IDE.
HD has SCSI before IDE - this worked on previous mobo with U160 controller.
Changing order made no difference.

In <fv25q3$17qo$2@textnews.wanadoo.nl>, "Folkert Rienstra" <see_reply-to@myweb.nl> writes:
>johnsuth@nospam.com.au wrote in news:c1.2c.39NLdY$0O1@PC1.BIGPOND.COM
>> I relocated a working SCSI hard drive to a new Supermicro X7DA8 mobo.
>> It was necessary to copy the appropriate driver for the mobo's AIC-7902W
>> adapter to the hard drive and edit the config file.
>> I achieved this by creating boot floppies which included the same driver.
>
>> The hard drive then booted
>
>Where as before it didn't?
CORRECT.
>
>> and the USB and IDE drivers reported their successful loading to screen,
>> but AICU320.add reported failure to load with error code (c0003003h)
>> and two rows of hex data.
>
>> The mystery is why the SCSI driver loaded from floppy but not from the hard
>> drive.
>
>Two different definitions of "loading".
NO, loading SCSI driver enables the hard drive beyond the boot sector to be
accessed. Booting from floppy enables access to the hard drive files for
editing.

>Copying is not the same as running it.
CORRECT.

>Presumably the driver crashed.
IT reported failing to load and the system then stopped.
>>
>> How do I persuade it to load from the hard drive?

johnsuth@nospam.com.au wrote in news:c1.2c.39PXWn$0OB@PC1.BIGPOND.COM
> In <fv25q3$17qo$2@textnews.wanadoo.nl>, "Folkert Rienstra" <see_reply-to@myweb.nl> writes:
> > johnsuth@nospam.com.au wrote in news:c1.2c.39NLdY$0O1@PC1.BIGPOND.COM
> > > I relocated a working SCSI hard drive to a new Supermicro X7DA8 mobo.
> > > It was necessary to copy the appropriate driver for the mobo's AIC-7902W
> > > adapter to the hard drive and edit the config file.
> > > I achieved this by creating boot floppies which included the same driver.
> >
> > > The hard drive then booted
> >
> > Where as before it didn't?

> CORRECT.

Ok, apparently we use different definitions of 'booting'.

> >
> > > and the USB and IDE drivers reported their successful loading to screen,
> > > but AICU320.add reported failure to load with error code (c0003003h)
> > > and two rows of hex data.
> >
> > > The mystery is why the SCSI driver loaded from floppy but not from the hard
> > > drive.
> >
> > Two different definitions of "loading".
>
> NO, loading SCSI driver enables the hard drive beyond the boot sector to be
> accessed.

> Booting from floppy enables access to the hard drive files for editing.

Now see, there's where I see a difference.
Since you don't, I'll take it that the floppy image also uses the very same
drivers to gain access to the drive rather than just be using the bios for it.

>
> > Copying is not the same as running it.
>
> CORRECT.
>
> > Presumably the driver crashed.

> IT reported failing to load and the system then stopped.

What I'd mention a 'controlled' crash.

> > >
> > > How do I persuade it to load from the hard drive?