Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: dvvrue95 on April 27, 2008, 05:23:15 PM
-
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
-
Hi dvvrue95,
I've recently added a CF card reader to my A4000 in the same way :-)
The IDE > CF adaptor on my Tandem card shows up as 'oktagon.device'. With my Oktagon SCSI card fitted as well, FindDevice of IDEfix97 found the CF card as Unit 100 (without my Oktagon SCSI card fitted it was seen as Unit 0).
Here is the mounlist of my CF0 driver from Workbench:Devs/DOSDrivers which can read 64MB, 1GB & 2GB fat formatted CF cards:-
/* compactflash.device $VER: 1.21 (19.10.2002) */
/* fat95 file system by Torsten Jager */
FileSystem = l:fat95
Device = oktagon.device
Unit = 100
Flags = 0
LowCyl = 0
HighCyl = 0
Surfaces = 1
BlocksPerTrack = 1
BlockSize = 512
Buffers = 20
BufMemType = 1
BootPri = 0
Stacksize = 4096
Priority = 5
GlobVec = -1
DosType = 0x46415401
(http://i120.photobucket.com/albums/o164/Cyberstorm604e/Sandy.jpg)
I also had to download 'TandemCD.dms' from HERE (http://l8r.net/install/hdc.html)and put the file 'AT' into Workbench:Expansion for it to work. The 'AT' file is set to Manufacturer 2092 and Product 6, which is how the Tandem card is seen in the 'Expansion Board Diagnostic...' screen of the 'Amiga Early Startup Control'.
(http://i120.photobucket.com/albums/o164/Cyberstorm604e/CFExpansion.jpg)
:pint:
-
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 wrote:
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?
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.
You mentioned "cfd" files. Is this compactflash.device? If so, this is not correct. Compactflash.device is for Compact Flash cards in card readers in the PCMCIA port.
You might want to check out GiggleDisk (http://aminet.net/package/dev/c/giggledisk). It will create a mountlist for your device.
--
moto
-
Just as few observations/notes/ramblings:-
1. It appears FindDevice sees the CF card itself and not the IDE > CF adaptor. So be sure to insert a CF card *before* you boot your A4000 and use FindDevice.
2. The CF0 driver that I am using is the same one used for CF cards on the PCMCIA slot of my A1200 Desktop. I have simply edited 'compactflash.device' to 'oktagon.device' and put the correct Unit number. I believe the CF0 driver that I am using will read a CF card of any capacity up to a 4GB limit prehaps (64MB, 1GB and 2GB are the only CF cards I have at the moment).
3. My CF cards are found by FindDevice as *both* 'oktagon.device' Unit 100 and 'SoftSCSI_ATE9.device' Unit 0. However, editing the CF0 driver to 'SoftSCSI_ATE9.device' Unit 0 does not give me a readable icon on screen for the cards. I have no idea if moto's giggledisk will create a SoftSCSI_ATE9 mountlist for you as I've never used it myself. Worth giving it a try though.
4. Unless FindDevice actually sees the CF card, there appears to be no point bothering with drivers to go in Workbench:Devs/DOSDrivers just yet.
5. The Tandem docs say that it is an Oktagon device.
Do you have 'oktagon.device' in the left window of FindDevice? If so, have you tried ticking the box 'Show all device types' and scanning for Oktagon devices?
-
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
-
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
-
Copy GiggleDisk_AOS68K to the C: directory. Might be easier to rename it to "giggledisk" too. Then use it as follows:
c:giggledisk SoftSCSI_ATE9.device 0 TO ram:
This should create a mountlist for the device in RAM:. Mount it to check it works, and if it does move it to devs:dosdrivers or sys:storage/dosdrivers.
--
moto
-
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
-
Nice Giggledisk instructions moto 8-)
I removed my Oktagon SCSI card to avoid any Unit number conflicts with the Tandem card and tried it:-
1. giggledisk oktagon.device 0 TO Ram:
This puts a driver called GGD0 in Ram: that mounts my CF card ok.
2. giggledisk SoftSCSI_ATE9.device 0 TO Ram:
This gives a report:-
Giggledisk: Unable to read block 15 (Size: 0x200)!
I also experienced some locking up of the A4000 when using SoftSCSI_ATE9.device :inquisitive:
-
Hi,
try http://aminet.net/disk/misc/oktapus.lha
The device for the Tandem will be "2nd.scsi.device" or
"3rd.scsi.device" if used on Oktagon, too. :-)
-
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
-
I've misplaced my 64MB card at the moment, but my 1GB CF card is a SanDisk SDCFJ from Jessops and my 2GB card is a SanDisk Ultra II bought from Staples just a few days ago for £20.
I somehow think your problem is using SoftSCSI_ATE9.device. My Tandem card still shows up as an oktagon.device even with my Oktagon 2008 SCSI card completly removed from the A4000.
-
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
-
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
-
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
-
Hi dvvrue95,
Is THIS (http://www.amiga-hardware.com/showhardware.cgi?HARDID=532) 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
(http://i120.photobucket.com/albums/o164/Cyberstorm604e/AT-Tooltype.jpg)
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?
-
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
-
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
-
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).
-
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
-
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:
-
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
-
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
-
8-)
Thanks for giving us an update :pint: