Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: curtis on June 16, 2015, 12:27:39 AM
-
So, I'm working on my A2000 with the above item in it.
I have a CF inserted in the CF slot and a SD card inserted in its appropriate slot. Try to run hdtoolbox to format the 2MB SD card and the LUN isn't recognized.
When I fire up toolbox, it scans only LUN's 0 and 1 at SCSI address 0 (which is what the media reader is set for). But it scans ALL LUN's 0-7 for the other addresses, even tho nothing is installed on any of them!
What am I doing wrong here?
I checked and LUN's are set to 7 in the information on the icon.
Using GURU ROM 6.13 also.
Any help would be greatly appreciated.
Curtis
-
I would go back and check your termination, also comment out or delete all the settings from HDToolbox except for "ASKDEVICE".
Here is a quick photo of one of mine, you can see it's detecting all the LUN's (I have two cards installed in this particular system, a CF in slot 0 and an xD in slot 5; ID 2 is my DVD drive):
-
And no joy.
Only lines in the info file are the askdevice and the scsi_device_name lines.
Even went so far as to reboot, just in case.
Just reads 0.0, 0.1, then on to 1.x...
-
But it reads the cards in LUN's 0 and 1 successfully?
What version of HDToolbox?
Try setting the reader to a different SCSI ID #?
Is the termination jumper on, and are there any other devices in the chain?
What controller?
Is this one of Mechy's readers? I have the PCD-60B models, which as I recall were a "little bit better", but I can't recall the difference. Perhaps shoot him a PM and ask if he has any advice?
-
Edit - anything in this thread helpful?
Post #5:
http://www.amiga.org/forums/showthread.php?t=65297
-
But it reads the cards in LUN's 0 and 1 successfully?
What version of HDToolbox?
Try setting the reader to a different SCSI ID #?
Is the termination jumper on, and are there any other devices in the chain?
What controller?
Is this one of Mechy's readers? I have the PCD-60B models, which as I recall were a "little bit better", but I can't recall the difference. Perhaps shoot him a PM and ask if he has any advice?
am guessing it is either wrong or double termination issue. The pcd60b was no different from the 50b,other than it had the xdpicture slot. they both work the same.
@curtis Use hdtoolbox from os3.9 if you can.
if not some things to check:
Make sure termination is exact,if you dont you will be fighting it and not getting anywhere forever.
Try different sd cards, some off brand are nothing but troubles, but sandisk,most transcend etc work fine(i have used up to 32GB,but realize over 4gb you may need nsd/td64 patches or os3.9 to make life easy. Stick with 4Gb or less for a simple life.
Many ebay cards are fakes and give problems, if you bought it there or a china site like dhgate etc you may have problems.
if the card cant be seen, try formatting it fresh in a pc to fat 32, then retry in the card reader.
HDinsttools does odd things to some cards i found, if you used it to partition,i have seen cards completely disappear and haven't figured a way to get them back,even formatting/partitioning in a pc doesnt help(ironically they work on the pc still).I dont know what this does to them,i recommend avoiding it.
mech
-
Well, since the unit does its own termination via a jumper and it's the last and only unit on the chain, don't think termination is the problem.
Anyhoo, tried changing the address from 0 to 6 and the problem follows the address. If I move the address to 1 then on 1.0 and 1.1 are found. Ditto for all the others.
I'm using hdtoolbox for OS 3.1.
The original card I tried is a authentic Sandisk 2.0 GB. Just tried a PNY 2GB with same results. Only other cards I have are microSD 8 and 32GB. PRetty sure those will not work well.
One interesting observation. From 0 to 5 HDTB merrily scanned all LUN's except for the active one and no comments. When I got to 6, it actually told me drives had changed, been added/deleted!
Formatted both cards FAT32 on Win 7 machine and same result.
BTW, don't think toolbox from 3.9 is an option as I'm strictly 68000.
-
Another observation.
Pulled out the normal boot disk/CF card.
Boot with my Install disk for WB 3.1 and running HDToolBox. No sign of it.
OOPS!!! Forgot to change to omniscsi.device!
Reboot. HDToolBox sees the drive! Partition, save info, reboot.
There it is! Format and rename. Voila!
Pop my regular boot HD back in and the card disappeared!
Hmmm. Might need to re-install my OS.
Comments before I go there?
-
You're formatting with FFS? Or something else?
Personally I always do a fresh reinstall of the OS on any new device, if I'm planning on making it my primary device (that goes for Windows or whatever, really). Only way to make sure you have a clean system, then you can use your old card as a backup.
Wonder if a 68010 would let you run 3.9? Granted it would be dog-slow unless you dropped the screen colors and replaced the icons with MWB or something, but they're only like $5 on ebay. From what I recall only a handful of programs in 3.9 actually "require" an '020+ (instructions), anyway.
-
It's going to be DOS. Will be using the SD card for my bridgeboard hard drive. Was kicking around the idea of installing OS/2 Warp. Liked it when it came out. Just felt better than Winblows.
Not sure about the 68010. IF I remember correctly, it has to be at least an '020 for 3.9.
-
Another observation.
Pulled out the normal boot disk/CF card.
Boot with my Install disk for WB 3.1 and running HDToolBox. No sign of it.
OOPS!!! Forgot to change to omniscsi.device!
Reboot. HDToolBox sees the drive! Partition, save info, reboot.
There it is! Format and rename. Voila!
Pop my regular boot HD back in and the card disappeared!
Hmmm. Might need to re-install my OS.
Comments before I go there?
It sounds like the hd is also terminated and its a case of double termination. is there any termination on the external gvp port?
mech
-
Nope. External port is just sitting there waiting for something to be plugged in.
-
!@#$@@##$^!!!!!!!!!!!!!!!!!!
Just finished the fresh 3.1 install and guess what doesn't show up anymore? Yep, the SD card. 0.0 and 0.1 only for address/LUN then all of the others.
Checked the termination. Automatic via jumper on the media reader. Nothing else on the cable.
Only things attached are the media reader with the CF card in place and the SD card in place.
-
Oh, and the info file only has askdevice and SCSI_DEVICE_NAME=omniscsi.device.
-
Okay, this is starting to get REALLY WEIRD!!!!
Tried booting from the floppy with the CF boot card and SD card in place. Floppy booted fine and the CF card was recognized and that was all.
Popped the CF card out and booted from floppy. SD card is now recognized!
Perchance is there something wrong with the CF card???
Is it somehow locking out any LUN's after its position?
Guess I'll try a different CF card and once again install the OS.
-
Okay, before my head explodes, I'm signing out until tomorrow.
Time to turn the brain off and watch some Torchwood and Dr. Who! Intelligent TV!!!!!
-
Okay, this is starting to get REALLY WEIRD!!!!
Tried booting from the floppy with the CF boot card and SD card in place. Floppy booted fine and the CF card was recognized and that was all.
Popped the CF card out and booted from floppy. SD card is now recognized!
Perchance is there something wrong with the CF card???
Is it somehow locking out any LUN's after its position?
Guess I'll try a different CF card and once again install the OS.
Basically, the same exact thing was happening to me and it turned out to be two bad, brand new, SanDisk CF cards! Are they SanDisk by chance? I was gonna ask Mike how his new Transcend card worked out. But from what I've been reading on the net lately, SanDisk has done something weird with their CF cards as of late. I shoulda bookmarked the reasons. I was tearing my hair out! Tried an old 2GB Transcend and all was great (with a dual boot double CF card setup).
-
Basically, the same exact thing was happening to me and it turned out to be two bad, brand new, SanDisk CF cards! Are they SanDisk by chance? I was gonna ask Mike how his new Transcend card worked out. But from what I've been reading on the net lately, SanDisk has done something weird with their CF cards as of late. I shoulda bookmarked the reasons. I was tearing my hair out! Tried an old 2GB Transcend and all was great (with a dual boot double CF card setup).
i have used the new style sandisk ultras, with the different labels and they all worked fine( i tried about a dozen). Check your card serial #'s on sandisk site to make sure they are legit.(you can register for the lifetime warranty)-turn it in for a new one if its flakey. The transcend with the orange label(4gb) seem to work(i have about 6). and the 2gb transcends(blue&purple industrial) work always
Mech
-
i have used the new style sandisk ultras, with the different labels and they all worked fine( i tried about a dozen). Check your card serial #'s on sandisk site to make sure they are legit.(you can register for the lifetime warranty)-turn it in for a new one if its flakey. The transcend with the orange label(4gb) seem to work(i have about 6). and the 2gb transcends(blue&purple industrial) work always
Mech
Thanks for the info Mech! I'll do that tonight! And yes, my old 2GB Transcend ALWAYS works!
-
It's going to be DOS. Will be using the SD card for my bridgeboard hard drive.
Not sure if I understand correctly, think I'm getting lost on this thread. ;) But to clarify, you're trying to prep the device with two cards:
1 - a CF card (presumably formatted with FFS) for your Amiga partition
2 - an SD card formatted as FAT/FAT32/"FAT95" for your DOS partition
Correct?
I would take it a step back and make sure the CF card is working 100% before trying to add another card.
For the FAT95/DOS partition I've never had any luck prepping them through HDToolbox; easier to just create a Mountlist/DOSDriver entry on your Miggy and format the card on a PC, that's what I do. Then I can interchangeably pop it out of my Amiga and into the card reader on my PC to transfer files. I still use it often enough that I sometimes forget that my Amiga has USB, too. ;)
-
Sorry to butt in with no constructive advice but, the two new bad CF cards are made by Kingston - with no front label and no verifiable part number searching the web.
-
I had the exact same problem with the card reader in my A1500, where I could get HDToolBox to recognize both a CF and SD card, but not at the same time. After an whole evening of LUNacy, I finally gave up and tried HDInstTools instead, which worked like a charm. The reason for this is because HDInstTools has a Last Lun option, and something similar seems to be missing in WB3.1 HDToolBox.
Now I'm able to use three cards at the same time if I want to (PCMCIA-CF, CF & SD).
-
HDInstTools has a Last Lun option, and something similar seems to be missing in WB3.1 HDToolBox
That's the same thing that Thomas said to me recently, when I had an unrelated issue. My problem actually turned out to be me being a dumbass and not using HDToolbox correctly, coupled with having one bad card that was throwing me off.
In Curtis's case however, maybe his limiting factor may be the 3.1 version of HDToolbox? I swear by the 3.9 version, however, and would use that over HDInstTools, any day. ;)
-
HDinsttools does odd things to some cards i found, if you used it to partition,i have seen cards completely disappear and haven't figured a way to get them back,even formatting/partitioning in a pc doesnt help(ironically they work on the pc still).I dont know what this does to them,i recommend avoiding it.
mech
Must say that I have never experienced any kind problems like this by using HDInstTools, but then again I have mostly used it with disks connected to the A1200 & A600 IDE controller. Maybe it's just a SCSI thing?
-
That's the same thing that Thomas said to me recently, when I had an unrelated issue. My problem actually turned out to be me being a dumbass and not using HDToolbox correctly, coupled with having one bad card that was throwing me off.
In Curtis's case however, maybe his limiting factor may be the 3.1 version of HDToolbox? I swear by the 3.9 version, however, and would use that over HDInstTools, any day. ;)
I have to agree, OS3.9 HDToolBox is the best for setting up harddisks due to so many reasons. But in case this is not possible, I use 3.1 HDToolBox for disks up to 4GB, and HDInstTools for disks larger than 4GB.
-
Update.
After pulling the Hitachi 2GM Microdrive that I was using as my boot disk and replacing it with another identical unit, I was able to have it recognized by HDToolBox, partition it, format it, and install OS3.1 successfully. My Sandisk SD 2.0GB is also recognized!
Conclusions:
It appears SOMETHING WEIRD is going on with my original Hitachi 2GB boot microdrive that precluded the system from recognizing the 2GB SD card!
I may try to recover the original microdrive at a later date, but for now, everything is working fine so onward to installing the 2386SX bridgeboard and getting that working with the SD card as the boot drive!
Details to follow, I'm sure!
-
Update.
After pulling the Hitachi 2GM Microdrive that I was using as my boot disk and replacing it with another identical unit, I was able to have it recognized by HDToolBox, partition it, format it, and install OS3.1 successfully. My Sandisk SD 2.0GB is also recognized!
Conclusions:
It appears SOMETHING WEIRD is going on with my original Hitachi 2GB boot microdrive that precluded the system from recognizing the 2GB SD card!
I may try to recover the original microdrive at a later date, but for now, everything is working fine so onward to installing the 2386SX bridgeboard and getting that working with the SD card as the boot drive!
Details to follow, I'm sure!
Glad you got it sorted! That's what it seemed to me too... something was faulty. Have fun with your Bridgeboard, I'm jealous!
-
Must say that I have never experienced any kind problems like this by using HDInstTools, but then again I have mostly used it with disks connected to the A1200 & A600 IDE controller. Maybe it's just a SCSI thing?
No, it was well documented it set up disks/cf's etc with a non-standard RDB. If you then made the mistake of using hdtoolbox etc on it, it would scramble the RDB, or something to that effect. I seem to think the newer version may of been fxed, but dont auote me on that.
-
Update.
After pulling the Hitachi 2GM Microdrive that I was using as my boot disk and replacing it with another identical unit, I was able to have it recognized by HDToolBox, partition it, format it, and install OS3.1 successfully. My Sandisk SD 2.0GB is also recognized!
Conclusions:
It appears SOMETHING WEIRD is going on with my original Hitachi 2GB boot microdrive that precluded the system from recognizing the 2GB SD card!
I may try to recover the original microdrive at a later date, but for now, everything is working fine so onward to installing the 2386SX bridgeboard and getting that working with the SD card as the boot drive!
Details to follow, I'm sure!
All that trouble because you wouldn't go out and buy a decent $15 cf :) lol i am glad you worked it out, i must say that was a odd problem that i would of never guessed.
personally i think microdrives suck ,since they are not solid state and are basically miniature hard drives with motors etc,but much more delicate than a real HD. The whole point of a cf reader is to use CF etc which are so much quicker in response time and near bullet proof.
-
All that trouble because you wouldn't go out and buy a decent $15 cf :)
Mechy, you know Amiga users are notoriously cheap! :hammer:
:roflmao: :roflmao:
No offense Curtis, glad you got it sorted! :)
-
This is nothing really to do with this thread but a bit of insight when i was selling scsi card readers.
In the 3 years i sold over 1200 scsi card readers, 99% of the tech help i gave to people were because they insisted on using junk no name media,counterfiet media from ebay,and or microdrives. The other 1% was usually split between helping them understand how to set the jumpers properly(i guess the label was confusing lol),and explaining how the power should be put to them so they didnt fry them.
In the three years of the 1200 drives sold, 8 came back. 4 of those 8 had power applied wrong and let the magic smoke out(the picture i drew showing how to power it apparently went ignored).
2 drives were genuine factory defects which i replaced.
1 drive a guy jammed the cf in upside down with what i believe was a hammer,breaking the slot to pieces inside as well as the bezel.
1 was returned because no matter how hard i tried,how many pictures i sent showing actual jumper settings and no matter how much i explained, the poor guy just couldn't grasp how to do it,so i refunded him when he returned it-this drive was resold as used..
Other Info:
The PCD-50B/60B scsi card reader can use up to 32GB cards in CF,SD,SDHC,MMC etc.
Sony memory stick can only be the original(not PRO or DUO- i think up to 128MB( i use 128MB).
SmartMedia slot can take up to 32MB smart media card.
on pcd60-i have never owned a XD Picture Card so i cant comment on sizes it can handle.XD cards come in sized up to 2GB,so my guess is that is it.
Filling all the slots with amiga formatted cards makes lun scanning go quicker on most slow scsi cards(gvp/2091/590 etc).
Mech
-
on pcd60-i have never owned a XD Picture Card so i cant comment on sizes it can handle.XD cards come in sized up to 2GB,so my guess is that is it.
My old Fuji camera uses xD cards and I have successfully used type M and M+ cards up to 2GB many times without issue.
Lost my darned type H card, it was so much faster, don't know where around here I put it! :(
1200 readers, I hope you made a good profit! I got mad when I saw people reselling yours on ebay for 2-3x what you were selling them for. :(
Care to tell us any stories about how you came across all those? :lol:
-
My old Fuji camera uses xD cards and I have successfully used type M and M+ cards up to 2GB many times without issue.
Lost my darned type H card, it was so much faster, don't know where around here I put it! :(
1200 readers, I hope you made a good profit! I got mad when I saw people reselling yours on ebay for 2-3x what you were selling them for. :(
Care to tell us any stories about how you came across all those? :lol:
I had aquired 4 batches total,900-pcd-50b NOS,1500-pcd-50b new(second batch cost me more), 100-pcd-60B used-this batch cost way more than the 50's)and 50-pcd-47b's as memory serves.
Well,i made a modest profit, no where near what i could of sold them for,but i was trying to give the amiga community something reasonably affordable.. the irony was Amigans bought hardly any of them and 90% went to sampler users. I sold very few in the USA,most went overseas :( i would of thought amiga people would of went nuts for a new scsi cf for $69(i think is what i had the pcd-50'b initial batch priced.)
I built some custom ones for sampler users and a couple A3000 amiga users into slim 3.5" drive cases with power supplies and external scsi cabling.
I hated to see the price gouging also, but they were over $200 new originally. you would think new old stock should be cheaper.
I had to price them to move as quick as possible because what they cost me was like having a mortgage lol. (don't ask me about the 5 pin square din production run i did-yeow).
I actually found the original batch of pcd-50b's from Sikorsky (yep, the helicopter company). They had new old stock in a warehouse. I found them by tracking down a military NSN number for these drives which was no small feat.
This eventually led me to them by some obscure web site listing surplus inventory. It was a matter of getting to the right person after that. i think i spent over a month securing the stock-i remember being exhausted by the time 2-fedex trucks arrived with over 50 boxes to unload. But oh no! work wasn't finished yet! I had to flash each and every drive with a read/write firmware(they came write protected).
the pcd-50/60 was not bad, but setting up a old pc with win95 and a obscure adaptec scsi library to use the pcd-47b flash tools was a right pain in the butt.
No lack of exercise ;)
I had a small batch of the rare pcd-47b drives, these were 4 slots and used 2 or 3-scsi ID's and no LUNS, they sold out the day i posted them. No amiga people bought any of these to my knowledge ,all went to sampler guys.
-
I traded Mechy a genuine DEAD A3000T for one SCSI Reader... worth every penny he may have got for the Amiga. BTW, Mech... what ever happened to that A3000T? Did you ever get it running? If so, what the heck was wrong with that beast? I tried everything to get it to boot!
-
I traded Mechy a genuine DEAD A3000T for one SCSI Reader... worth every penny he may have got for the Amiga. BTW, Mech... what ever happened to that A3000T? Did you ever get it running? If so, what the heck was wrong with that beast? I tried everything to get it to boot!
Wow Gizmo,i completely forgot about that.. my memory is hazy but i still have it and got it going. I seem to recall a few problems.. low voltage on the power supply, fixed that and it still wouldn't go. I remember desoldering chip ram,it turned out to be toshiba zips and a few were dead. common problem on 3000t's is dead toshiba chip ram(fixed many a 3000t with this problem in 20 years). last i recall was a flaky proto scsi chip was the last piece of the puzzle. I rarely sell any amigas, i love all the different models and their quirks. for some reason i like trying to fix basket cases.. well its love/hate thing.. i get into the project all gung-ho to fix it, then half way thru i am pulling my hair out going "why did i take this on!?":angry:, but i win mostly in the end. :D:D
-
That's awesome you got 'er going! After dinking with it 6 or 8 hours, I knew I wouldn't be able to get it to boot without some spare parts. I'm just glad you kept it and didn't schlog it on eBay or elsewhere. Good to see Miggies get good homes!
-
Hey bridgeboard gurus. I started a new thread regarding getting the SC card I FINALLY got recognized to serve as a full-time DOS drive for my 2386SX bridgeboard.
I would really appreciate any help on that little project.