Mounting a CF unit on a 4000 via Tandem IDE card

[A4000_Mad]

Yes, I've just been busy downloading and having a look at oktapus.lha. After reading that it was "beta" and "Use at your own risk as you could lose your data" my bottle completely went :oops:

I have a 9GB HDD and an Iomega 2GB Jaz drive connected to my Oktagon 2008 SCSI card and don't wanna risk messing them up. But feel free to check it out yourself and report back :-D

[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

[A4000_Mad]

Hi dvvrue95,

Is THIS your card?

This card supports any IDE device and ATAPI device connected to its IDE controller. It uses (oktagon.device) for IDE devices and (tandemat.device) for ATAPI devices.

Can you confirm that your AT file has Default Tool C:BindDrivers and Tooltypes PRODUCT=2092/6



SUGGESTION:-

Put an IDE hard drive on the IDE/ATA Connector and let us know if it shows up as an Oktagon device or something else?

[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

[A4000_Mad]

Hi dvvrue95

Just reporting something I found out.

As you can see from the screenshot above my 2GB Jaz drive on the Oktagon SCSI card is found as 'oktagon.device' unit 5. However, it is also found as 'SoftSCSI_C9EB.device' Unit 5.


I've used giggledisk with a 2GB Jaz disk inserted into the Jaz drive:-

1. giggledisk oktagon.device 5 TO Ram:

This puts a driver in Ram: that works perfectly for the 2GB Jaz disk.


2. giggledisk SoftSCSI_C9EB.device 5 TO Ram:

This causes the A4000 to lockup immediately.


It's also confusing that you don't have anything showing up as an 'oktagon.device' :crazy:

 
P.S. If I remove the file AT from Workbench:Expansion I lose 'SoftSCSI_ATE9.device' from the list in the left window of FindDevice, and my CF card is no longer seen as an 'oktagon.device' ('oktagon.device' is still in the list of the FindDevice window but the card is not found).

[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

[A4000_Mad]

Hiya,

dvvrue95 wrote:

By the way I don't see your screen shot.

It's in my very first post of this thread :-)

dvvrue95 wrote:

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.

I do *not* have a file called oktagon.device in Workbench:Devs. If you look at the previous posts in this thread you will see that moto wrote:-

It's either in the ROM of the controller, or the file in Expansion loads it directly in to RAM. In any case, it doesn't matter - if FindDevice can see it, then the device is working.

I've read the AT file with a button called ANSIRead of my DirectoryOpus4. Amongst the jumble of characters I can see oktagon.device and expansion.library. However, I cannot find expansion.library anywhere. Does it actually exist as a file and could it be required prehaps?

I've got nothing else I'm afraid :roll:

[Michael_D]

Hi,

the "SoftSCSI_ATE9.device" is not a real scsi/at-device.
It makes the Oktagon able to load a real scsi/at-device from HD.
Just like softkicking Kickstart.
If you read the whole manual of oktapus you'll understand...

You can install the driver...
in SYS:Expansion (Binddrivers)
in RDB of the first HD
in any other folder and start it manually (for testing it...)

or load it with LoadIDE (IDEFix) to make it reset proof - Autoboot with TandemIDE :-o
 :-D  

[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

[A4000_Mad]

 8-)

Thanks for giving us an update :pint: