SCSI card reader questions....

[Cammy]

Heya Mech, I had an idea that could maybe help out people with these drives, and anyone looking to buy one for themselves in the future.

Maybe everyone who has got and used one of these SCSI card readers can write up a little bit about how they got it to work and detail their hardware setup, then we could combine the information to make some documentation to give to people who buy the drives, and post it on the website.

I can borrow one from Rebel, and maybe with Lunithy's help we can write up how it works on the A2091, then maybe test the GVP HC-8 with it too, and I can try it with the Squirrel SCSI interface on my A1200 and A600 if I can get it to work with my CD ROM drive in my external SCSI minitower.

I wouldn't mind compiling all the info and making up some form of document to display online or print out, maybe we could even work out some kind of boot disk to help mount and format the cards for people who don't have the software already downloaded, and haven't got an easy way to transfer files to their Amiga from a PC yet (which is perhaps why they bought the SCSI card reader in the first place).

It's just an idea, but I feel it would help people out a bit and I'd like to help out in any way I can.

[TheGoose]

So just a little more followup, for my A3000D I found this today:

1 - 3.1 HDToolBox worked with multiple slots and CF, SD and PCcard slot
(although it could not read the size of the media upon scan)

2 - Now, HDInstTool (which is more recent and updated) would only report back 'unsupported' whenever I tried the CF or SD slot. PCcard slot is fine.

[mechy]

Heya Mech, I had an idea that could maybe help out people with these drives, and anyone looking to buy one for themselves in the future.

Maybe everyone who has got and used one of these SCSI card readers can write up a little bit about how they got it to work and detail their hardware setup, then we could combine the information to make some documentation to give to people who buy the drives, and post it on the website.

I can borrow one from Rebel, and maybe with Lunithy's help we can write up how it works on the A2091, then maybe test the GVP HC-8 with it too, and I can try it with the Squirrel SCSI interface on my A1200 and A600 if I can get it to work with my CD ROM drive in my external SCSI minitower.

I wouldn't mind compiling all the info and making up some form of document to display online or print out, maybe we could even work out some kind of boot disk to help mount and format the cards for people who don't have the software already downloaded, and haven't got an easy way to transfer files to their Amiga from a PC yet (which is perhaps why they bought the SCSI card reader in the first place).

It's just an idea, but I feel it would help people out a bit and I'd like to help out in any way I can.

That would be a major help cammy i had intended to write up what i tested with or do video's but seems there is always one more project and i don't get to it. some have left reviews on the shopping cart,but its usually not enough info of the setup to help much. This would be a great help if you have the time thanks!.It "should" woprk on on the hcII+8 as i think its the same controller in the gvp A530,which i have a card reader in and all slots work like a champ.

mech

[Heiroglyph]

I've got several different SCSI cards, usually not the newest firmware, but it's more points of reference.

I wouldn't mind giving you feedback on each of them.

[mechy]

I've got several different SCSI cards, usually not the newest firmware, but it's more points of reference.

I wouldn't mind giving you feedback on each of them.

Everyones feedback is welcome. Noting card revisions,card roms,jumper settings would help compile a accurate working list.

I figured out why the card reader didn't work at your house that day john,apparently the 2091 is a bit odd on luns,and only likes the card reader at device 0 when using all the slots. like this every slot is bootable/useable and such.
i really need to take better notes on this stuff i shouldn't say its odd,but its probabaly a case of using a true scsi II device(card reader) on a scsi 1 card like the 2091. I wonder if updating the western digital proto4 chip to rev 8 would do anything like in the A3000,it makes for a proper scsi II mode in the A3k.. if i have a spare WD8 i will check it.

Mech

[TheGoose]

"I wonder if updating the western digital proto4 chip to rev 8 would do anything like in the A3000,it makes for a proper scsi II mode in the A3k.. if i have a spare WD8 i will check it."

Mechy, I am using WD8 in my system. Maybe do a youtube video later today...

[Heiroglyph]

Wow, that's really odd.

I'm going to rejumper the WarpEngine ones later today and see if that fixes my problem there.  So far that only works on LUN 0, with the PCMCIA.

Now that I think about it, the 4000T didn't care for SD cards, but PCMCIA and CF work great.

I'll retry the selection of cards I have with device 0 and give a full report on PCMCIA, CF and SD slots.  I've got no media for the others.

[mechy]

"I wonder if updating the western digital proto4 chip to rev 8 would do anything like in the A3000,it makes for a proper scsi II mode in the A3k.. if i have a spare WD8 i will check it."

Mechy, I am using WD8 in my system. Maybe do a youtube video later today...

Good deal goose,look forward to it. be sure and post a link for us here.

Mech

[Motormouth]

So just a little more followup, for my A3000D I found this today:

1 - 3.1 HDToolBox worked with multiple slots and CF, SD and PCcard slot
(although it could not read the size of the media upon scan)

2 - Now, HDInstTool (which is more recent and updated) would only report back 'unsupported' whenever I tried the CF or SD slot. PCcard slot is fine.

I bought one of these SCSI card readers from mechy a few months ago, just got around attaching it to my A3000 with a WD -08 in it.  

Also on the scsi chain are two internal drive id 0 and 1, The card reader is on the external scsi and set to id 2, I also have a external cd rom on id 3.

to get the multiple LUNS working one needs to set the access the nvram in the A3000.  I used SetBatt from fred fish disk 535, Probably can get this from aminet.

Use SetBatt to turn multiple luns on.  In both of my a3000s the default was multiple luns off.

I still cannot get the a3000 to autoboot of the CF card.  I have to use mounter (comes with 3.9) or SCSImount to get the partitions to mount.

someone mentioned needing to have the card reader set as and internal device to get it to card reader to autoboot.  This should really not matter, but I have seen stranger things with scsi devices.  I would love to get my a3000 to autoboot with the card reader,

I have two gvp scsi cards, a trumpcard, and a dataflyer.  I will see if can get these to work with the card reader.

[Motormouth]

I know this is a old thread but just an update on Mechy's scsi card reader.

Unlike the autoboot and mounting issues with a3000
both of my gvp scsi cards (2000 HC+8 and A500 HD 8+) worked flawlessly.  Full automount and autoboot.

I will check the trumpcard and dataflyer

[Kremlar]

Interesting.  FYI, my 3000 with latest SCSI chip boots to the CF card reader without issue.  I did need to enable LUNs to get it to recognize the CF card slot.
 
Also, HDToolBox did error out trying to partition the card when in the CF card slot.  I used the PCMCIA adapter just to partition, format, and install the OS.  Once I did that I moved the CF card directly to the CF card slot and it has worked fine since.

[Zac67]

SCSI / LUN support on the 3000 internal SCSI may depend on the ROM version in use...

[Motormouth]

SCSI / LUN support on the 3000 internal SCSI may depend on the ROM version in use...

mmmm...

I was able to get the card reader to work with multiple luns both as an internal scsi device and an external device.  The problem is I cannot get them to automount or autoboot,  I have to use mounter or scsi mounter.

I am using  a WD -08 scsi chip with 3.1 roms and 3.9 updated to the unofficial boing bag 4 and a v3.2 a3640.  I wonder if the softbooted rom that comes with 3.9 bb2 or above is giving it problems, or even the 3640.... (eventhough it has never been a problem before)

I will try the card reader in an unexpanded stock 25mhz 68030 backup a3000.  The only updates stuff in it are the WD -08 scsi controller, 3.1 roms and 16 megs of 32bit fast ram.


As for other scsi controllers (all tested in an a2000 with 3.1 roms and fusion forty 68040 board).

I was able to get a trumpcard pro working with the card reader to autoboot and automount but only with lun 0 (eventhough it is suppose to support multiple luns)

I was unable to get the dataflyer scsi to work at all.   This is odd since it uses a similar amd scsi controller as the trumpcard.  However this controller has always been finicky.

as stated in an earlier post the gvpscsi (both in the a2000 and the a500) cards worked flawlessly....  multiple lun, autoboot, and automount .

[Motormouth]

I will try the card reader in an unexpanded stock 25mhz 68030 backup a3000.  The only updates stuff in it are the WD -08 scsi controller, 3.1 roms and 16 megs of 32bit fast ram.

Well what do you know.....  The card reader works flawlessly in my backup a3000.

mmmm....  Is the problem with my main a3000 hardware or software related?

[Tenacious]

Everyones feedback is welcome. Noting card revisions,card roms,jumper settings would help compile a accurate working list.

Mech

So, has this information been gathered and given a logical home since last August?  I recently acquired one of these card readers and love the concept (good job Mechy).  This thread is the most useful info I've seen so far.  

My goal is not necessarily to boot from CF cards, but rather, to read (and share) files through SD cards with my Palm, Mp3 player, camera, etc.  Apparently, no one has done this so far?  I think I'm going to need to mount a compatible file system.  Formatting the various style cards with a file system only usable with Amiga has little utility for me.   I'm not afraid to experiment and share results.

[Zac67]

LUN support has very little to do with the controller chip in question, it's 99% due to the driver (=boot ROM or embedded in Kickstart).