»

[acadiel]

So, I have this Tandem BSC non autoboot IDE controller in my A2000. I just put a CompactFlash 4GB card in it, partitioned it into 525MB partitions (just in case I ever need to use them), and have it sitting there waiting to be used.

The Tandem device puts something in Expansion (files named IDE something or another) to get the Amiga to recognize it.

So... how do I create a "boot floppy" and pass control to my real DH0: on the CompactFlash card, since the Tandem doesn't autoboot? I'd like to deprecate the SCSI drive if at all possible and go CF only.

[amiman99]

It's been a while, but in A2000 with supra 2000 SCSI controller that did not autoboot for me, I used the boot disk "SupraBoot" from http://amiga.resource.cx/exp/search....id=#s_wordsync
You can look at the startup-sequence to get some clues how they do it.
It's mostly assigns after the HD is recognized.

[Motormouth]

Originally Posted by acadiel

So, I have this Tandem BSC non autoboot IDE controller in my A2000. I just put a CompactFlash 4GB card in it, partitioned it into 525MB partitions (just in case I ever need to use them), and have it sitting there waiting to be used.

The Tandem device puts something in Expansion (files named IDE something or another) to get the Amiga to recognize it.

So... how do I create a "boot floppy" and pass control to my real DH0: on the CompactFlash card, since the Tandem doesn't autoboot? I'd like to deprecate the SCSI drive if at all possible and go CF only.

It is actually quite simple:

Make a bootable floppy
make sure you have assign command in the df0:c directory
at the very beginning of the floppy's startup-sequence
put the following script

df0:c/assign sys: [name of your system hard drive partition]:
assign s: sys:s
assign l: sys:l
assign fonts: sys:fonts
assign devs: sys:devs
assign libs: sys:libs
execute s:startup-sequence
endcli



This assumes that the IDE controller is recognized right away.
if not you may have to tweak it a bit in the floppy's startup-sequence,

[acadiel]

Thanks, Motormouth!

Since it's one of those non autoconfig controllers, it expects the support files in Sys:Expansion -

So, if I put the AT and At.info files in the df0:Expansion, will it read it before passing control over the the newly assigned hard drive?

[Motormouth]

Originally Posted by acadiel

Thanks, Motormouth!

Since it's one of those non autoconfig controllers, it expects the support files in Sys:Expansion -

So, if I put the AT and At.info files in the df0:Expansion, will it read it before passing control over the the newly assigned hard drive?

I am not exactly sure when the expansion directory is hit during startup. The only thing that I ever used the expansion directory was with a bridgeboard. Anyone else know?

[zipper]

Originally Posted by Motormouth

I am not exactly sure when the expansion directory is hit during startup. The only thing that I ever used the expansion directory was with a bridgeboard. Anyone else know?

After Binddrivers?