Mounting a CF unit on a 4000 via Tandem IDE card

[dvvrue95]

Hi there,

Im trying to mount a CF pcmcia unit connected as a master to the Tandem IDE I/F on a A4000 DT. I copied some Cf files
CFD/Devs,CFD/L etc from my A1200 which has a working Cf
card but not much joy. I also copied the A1200 file system - FAT95 across to the A4000 without any luck, I also tried using the existing A4000 CacheCDFS with the A1200 device file "copmpactflash.device" but got a DOS error message "control entry in mount list missing".

So I used IDEfix97 to find device on the A4000 and it comes up with "softSCSI_ATE9.device" which at least
means the unit has been deteced. Any ideas what the mount list should look like for this configuration?

many thanks, Ian
 

[dvvrue95]

Hi A4000 MAD,

thks for the feedback, I am using a similar mountlist for my CF card and also have the "AT" file in my Expansion drawer.

Your reply resulted in me checking out a few more details and I think my problem is that I don't have a device exec. file called "SoftSCSI_ATE9.device" in my SYS:DEVS drawer, or for that matter anywhere on my machine, although IDEFIX97 identified that file using "Find device" when scanning for the CF card. So how does IDEFIX97 "know" about this file and that it associated with the CF card? I have used the "use" option in the "Find device " screen but that doesn't appear to do anything.

Question how or where can I obtain a copy of this  "SoftSCSI_ATE9.device" file from?

cheers, Ian

[dvvrue95]

Hi Moto and A4000 Mad,

useful feedback - acknowledging both :-

1. MOTO

Ok so looks good since FindDevice recognizes the card.

Yes initially I tried copying over from my 1200 some cfd files which did not work, so I guessed something wrong .

I will check out GiggleDisk (see also below).

2. A4000 Mad

Have CF card inserted before bootup.

My CF0 driver is also the one I ported from my 1200 and I edited to "SoftSCSI_ATE9.device" Unit 0. When trying this option I cannot see any CF icon although if I try to mount CF0 ADOS indicates "device already mounted". If I use Directory Opus to read CF0 I get a directory error message.

I do have octagon.device in the left window, I'm pretty sure
I had show all devices ticked, but will recheck.

thanks again for responses, Ian

[dvvrue95]

A little update, but not much progress,

IDEFix97 "FindDevice" identifies CF card as :

SoftSCSI_ATE9.device
Unit 0
Toshiba
THNCF064MMA
Rev 3.10

Have repeated "show all devices" "FindDevice" but only shows up as above, not Octagon.device.

If I try reading CF0 directory from DirOpus I get a "directory not available" error message from DOpus and a "DOS error code 115 - bad number".

I have downloaded and unpacked giggledisk but am not sure what to do with it. I have a giggledisk/bin/giggledisk_AOS68K file which if I double click just results in my A400 rebboting??? Should I add this file to my C Dir and use giggledisk as a command??  http://www.amiga.org/uploads/smil402e47bc493f4.gif
http://www.amiga.org/uploads/smil402e47bc493f4.gif

Perhaps this is turning into a S/W forum item?

Ian

[dvvrue95]

Hi Moto,

copied giggledisk to C dir and tried yr syntax (3 times)and it results in  a guru meditation error
8000 0004 with different tasks e.g. 0715a170 with a soft reboot of machine!!

I'm running OS3.5 on an unexpanded A4000 (2M + 16M)

loosing hair, sleep etc Ian

[dvvrue95]

Hi A4000 MAD,

another update,

reason my A4000 rebooted after running giggledisk SoftSCSI_ATE9.device 0 to ram: was 'cause I had forgotten that I had physically disconnected the Tandem IDE I/F last night!
(Operator problem!!)

So having reconnected things, I ran gigledisk again and I now have exactly the same result as you i.e.

 Unable to read block 15 (Size: 0x200)!

So giggledisk appears to work well done Moto.

What type of CF card have you got? I don't mean just the ID from FindDevice, my card is actually labelled as Viking Interworks CF 64mb.

thanks, Ian

[dvvrue95]

Hi A4000 MAD,

thanks for that info about your CF cards, yes I guess you are correct it must be something to do with the SoftSCSI_ATE9.device driver, although it seems to be the only one found by FindDevice.

Have you any experience of these Oktapussy "updated" drivers??,  referred to by Micheal D at

http://aminet.net/disk/misc/oktapus.lha
I might give them a try.

(Thanks for the link Michael D)

Ian

[dvvrue95]

Hi A4000 MAD,

yes that warning made me stop ....... but so near I will do a  backup and see if it helps.
I guess you have a slightly different Tandem card to me, since mine only has two 40 pin I/F's one for the older Cd32 style (I think) CD drive and one "proper IDE I/F with usual 1 master and 1 slave device setup?
To confirm I can send you a copy of my Tandem docs to your Pmail address if you wish?

Will let you know about "oktapussy" after the Bank Holiday.

Ian

[dvvrue95]

Hi A4000_Mad,

The card looks like the same type!

have checked my AT file for default Tool and Tool type which is exactly the same as yours.

I will follow up on yr. idea of connecting IDE/ATA HD  to see how IDEFix97 identifies it at the weekend.

thanks, Ian

[dvvrue95]

Hi A4000 MAD,

did a quick test with a HD connected to Tandem IDE I/F results / musings :-

1. I already have a LG DVD ROM drive connected via this I/F the driver is identified by IDEFIX97 as a tandemat.device unit 0.

2. Surprise surprise ! when I connect a ATA HD the driver  is identified as a SoftSCSI_ATE9.device unit 0. If I try to use giggledisk to create a mount file I get the same error message we both rxd. before.

3. I disconnected my DVD drive and connected both the HD and the CF to the Tandem IDE I/F. IDEFIX97 then identifies the driver for both devices as Soft SCSI_ATE9.device units 0 and 1. I set my HD as a slave since the CF is set as a master, although I could have done it as CF slave : HD master.

Notice no mention of octagon.device, even when selecting find all devices. My A4000 "internal" IDE HD is identified as scsci.device unit 0.

I also tinkered with the IDEprefs file in that octopussy folder (I'm not willing to install the whole thing yet!) And if I double click the ideprefs icon in prefs folder in ocopussy I get an error message "unable to load SoftSCSI_ATE9.device" this controller is not configurable"

time to sighn off for the weekend now, Ian

[dvvrue95]

Hi A4000_Mad,

yes sure is confusing! By the way I don't see your screen shot.

I managed to find a old TandemCDInstall disk (copy I think, not original) but unfortunately since I no longer have a Mitsumi CDROM drive the S/W won't auto install. I noticed there is a  Mount Oktagon icon on the disk but if I double click it I get to some sort of LOGIN password protected screen and I don't have any password info - another brick wall. The Tandem card was already installed in the A4000 when I bought it with a Mitsumi CDROM drive fitted. Which I changed out for an IDE CDROM.
Non of these SoftSCSI???.device files seem to work correctly.
Idea? can you send me a copy of your oktagon.device file and I will try to create a mount list for my CF drive that way.

bye , Ian

[dvvrue95]

Hi A4000_Mad and Michael D,

Michael,

yes thanks for yr comments, in particular about reading the Doc's in full. Since I wasn't getting any where with any thing else I decided to try out some of the Oktapussy "Beta" files. Which resulted in me using the "AT" file in my Expansion drawer to replace the existing "AT" file. I also edited my CF0 devs file to reference driver, softSCSI_ATE9.device.

I had my CDROM as secondary IDE and my CF as master IDE on the Tandem I/F.

I rebooted and using FindDevice I now have two exec. devices for my CF device :-

SoftSCSI_ATE9.device and
2nd.SCSI.device (*)

(*) (note this appears to be the way Oktapussy designates multiple devices)  

Anyway running HDToolbox recognized the 2nd.scsi.device and enabled me to format the CF card!!!!

Strangely enough I didn't have to run giggledisk to create a exec. device driver for CF0, I double checked my Devs DOS drivers and CF0 is still referencing softSCSI_ATE9.device??
I will try "doing the right thing" another day, at the moment every thing appears to be working OK.

Anyway  SUCCESS AFTER A LONG ........ TIME

many thanks for yr help and encouragement,
BFN, Ian