Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: k4lmp on May 07, 2012, 06:56:03 PM
-
OK, so now I have everything done, except for adding my CD-ROM. I have 3 old SCSI CD-ROMs lying around, the only one that isn't black is a CD-Burner. I realize I can't use the burner part, but would prefer to use this one because the color matches better. I use Classic WB, and regular WB 3.1, and would like to have it work on both. My SCSI card scans the bus and sees the CD drive, but I have no idea how to set it up. Could someone give me some tips on what to do or how to get started? This is an A2000 with an A2091 SCSI card.
Thanks,
Jeff
-
When I was using SCSI on my A1000 To get the CD-ROM working I needed ASIM CD-FS, which at the time was the Commodore Recommended Software. Unfortunately the product is no longer available.
I think Allegro CDFS was another product but needed the Fast IDE Interface to function.
I'll do a little more research and try to clarify a configuration.
-
you should have a cd0 icon somewhere. im at work and the way mine is laid out i have a "storage" directory for stuff i dont want mounted.
now that im trying to contribute, i cant remember where the unused icons are. but os 3.1 has them... somewhere
so hopefully they are in devs:dosdrivers.
wb3.1 icon, then devs, then dosdrivers.
click the cd0 icon 1 time, then go to the top of the screen on the menu bar and click on ICON.
a drop down menu appears...
click information.
a window opens with details about cd0:
if your cdrom is device 6, then you want to make sure it has the scsi device and id correct.
you would click on the text for device and unit one at a time so they go into the edit box.
change them to the proper settings and hit return so the edit box is empty and the new information is listed.
do the same for device driver. if you have a commodore 2091 then it would be the same.. .scsi.device.
then click save.
if you have a different scsi controller look in devs for some kind of scsi device and edit accordingly
you can actually double click on the cd0 icon and it will mount the drive - even if there is no cd in there.
if a disc is in an icon for the cd pops up on the workbench with its name.
to wrap things up you can put the cd0 icon in devs:dosdrivers and it will mount at every boot - but on a 2091 you have to wait 30 seconds for the machine to figure out the cdrom mountpoint is not coming back if the drive is empty.
i leave a "frozen" archive cd of my entire 2000 filesystem in there so it will boot quicker and have a good copy of everything handy.
you can use the drive to burn cds. my 2000 will do a burn as long as i make an image (iso) file first then burn the image (iso) direct.
the deal with a stock 2000 is trying to process all the .info (icon) files and crowded directories like fonts.
it may take some wrangling and a few colorful metaphors but it can be done.
-
You need more than just the CD0 icon. You need the CD file system.
ASIM CDFS is no longer published, but you can find used copies through various sellers. I like ASIMware CDFS better than most - it's easy to setup and works quite well. I still use it on my A2000. I am using 3.8 right now. Be careful buying 3.10 (the last one released) there are bootleg copies that have problems...
-
I use IDEFIX97. Was really easy to setup on both my A1200 (IDE) and my A2000 (SCSI).
-
You need more than just the CD0 icon. You need the CD file system.
ASIM CDFS is no longer published, but you can find used copies through various sellers. I like ASIMware CDFS better than most - it's easy to setup and works quite well. I still use it on my A2000. I am using 3.8 right now. Be careful buying 3.10 (the last one released) there are bootleg copies that have problems...
He's got ClassicWB installed so I believe he has everything he needs. He might need to edit the CD0 icon and change the unit number to match the jumper settings on the CD ROM though.
-
OK, so now I have everything done, except for adding my CD-ROM. I have 3 old SCSI CD-ROMs lying around, the only one that isn't black is a CD-Burner. I realize I can't use the burner part, but would prefer to use this one because the color matches better. I use Classic WB, and regular WB 3.1, and would like to have it work on both. My SCSI card scans the bus and sees the CD drive, but I have no idea how to set it up. Could someone give me some tips on what to do or how to get started? This is an A2000 with an A2091 SCSI card.
Thanks,
Jeff
This works with any scsi cd/cd burner etc under workbench 3.1 :
Set the cdrom device number jumper to something other than the HD/cf whatever is on your scsi chain so it doesn't conflict, make sure termination is right.
copy cd0: from storage to devs:dos drivers
edit the icon info as follows..
set the UNIT= to the right unit # (# being the cd drive #)
make sure DEVICE=scsi.device
save the icon info and reboot. pop a cd in and it should come up.
os3.1 cd filesystem isn't the best but works fine on data cd's etc.
You can easily burn cd's on amiga btw. You just need makeCD,masteriso or frying pan etc.. i recommend makecd.
Mech
-
OK, so now I have everything done, except for adding my CD-ROM. I have 3 old SCSI CD-ROMs lying around, the only one that isn't black is a CD-Burner. I realize I can't use the burner part, but would prefer to use this one because the color matches better.
Why can't you use it as a burner? I used to burn CDs all the time in my A2000 with a SCSI CD burner.
-
Ok, so I tried this in 3.1, editing the icon. I changed it to scsi-4, which I think is what it is. It does nothing. The funny thing is, when I run HDtools now, none of my scsi drives show up. It's like it doesn't even scan the bus, just comes up with no drives listed. This is in WB 3.1, not classic wb, as I haven't tried it yet. I can't figure out why nothing shows up in HDtools, it boots up fine, so it has to be seeing the hard drive. I think the last time i had the CD hooked up, it showed up as scsi 4, but I am not 100% sure, but since it doesn't show me any of my drives in HDtools anymore, I am not sure. Any reason why HDtools quit detecting drives?
Jeff
-
Ok, so I tried this in 3.1, editing the icon. I changed it to scsi-4, which I think is what it is. It does nothing. The funny thing is, when I run HDtools now, none of my scsi drives show up. It's like it doesn't even scan the bus, just comes up with no drives listed. This is in WB 3.1, not classic wb, as I haven't tried it yet. I can't figure out why nothing shows up in HDtools, it boots up fine, so it has to be seeing the hard drive. I think the last time i had the CD hooked up, it showed up as scsi 4, but I am not 100% sure, but since it doesn't show me any of my drives in HDtools anymore, I am not sure. Any reason why HDtools quit detecting drives?
Jeff
If the name of the SCSI driver in HDToolbox is wrong then it might not show up. IIRC some versions of HDToolbox only look for the SCSI driver named in the tool types while others will look for any SCSI drivers they can find.
You might find the HDToolbox in ClassicWB is your best bet.
-
look on aminet for scsilister and even scsimounter.
but first a lot of people use id 5 for a reader only or a zip disk and id 6 for cd burners.
it doesnt matter as long as you dont have the id as 7 which is most scsi controllers or 0 which is most boot drives.
if it just sits there then maybe you have both your boot drive and cdrom on the same address.
also there are some scsi connectors out there that will actually go in the wrong way becasue they arent keyed (have that bump in the middle) the red stripe on the ribbon should be closest to the power connector 99 % of the time.
i use makecd too - i had a very tiny part in getting it to work with jvc burners when patrik ohly was creating it.
here is my cd0: file
7> type cd0
/* AmiCDROM filesystem */
Handler = L:cdrom-handler
Stacksize = 10000
Priority = 10
GlobVec = -1
Mount = 1
Startup = "DEVICE=scsi.device UNIT=6 ML R"
7>
this can actually be appended to devs:mountlist but be SURE you have a # at the top of the file and # at the very bottom. look at the other device specs in the file and it will help you.
keep your chin up :)
-
In case of using AmiCDROM best to get the latest version, called AmiCDFS!
-
What happened was when I tried to use Mech's suggestion, I didn't have CD0 icon in storage or in devs. So, I re-installed WB 3.1. Now I have CD0 icon. The funny thing is if I boot from the CF in WinUAE, HDTools works fine, and shows my HD. But if I boot on my A2000, everything comes up fine, but HDTools shows no SCSI devices. I highlighted the icon, and did the information thing. I am at work, and can't rem exactly what the name was, but I think it was SCSI_DEVICE_NAME=uaehf.device. I just can't figure out why it doesn't see at least my HD now. I have tried it with LUNs enabled and disabled. I am now using my CF slot, instead of the PCMCIA adapter, so it takes about 30 seconds to boot, due to the SCSI card scanning the bus. But, the thing is, it doesn't matter, even if I use the PCMCIA adapter, with LUNs disabled, same thing, boots fine, but no drives at all in HDTools.
Jeff
One more thing, I have also booted with the CDROM not in the chain, and same result with HDTools.
-
Well, I got my CD to work in WB 3.1. When I insert a CD, it pops up on the desktop. I can go into shell and browse the CD as well, at least it worked with an old Windoze 95 disk that I have. The only thing is I noticed if I go into HDtools and modify the CD, it won't save the changes, I get Write Error-2. Don't know what that is, but it works. I ended up installing Asim CDFS 3.9, which took care of everything, except for the HDtools thing.
I haven't tried it in Classic WB yet. Darrin, I think I will leave it until you get home, maybe you could help me out with that, then.
Once I get that done, if I can burn CD's I may try to fool with that.
My baby needed some TLC, so I have replace half a thousand missing screws, and such. All I have left to do is get my CD working in Classic WB, upgrade my SCSI controller chip when I get it (on the way from Mech). Then I can permanently put the cover back on and begin to enjoy it.
I also boot now from my CF card in the CF card slot, not the PCMCIA adapter. It only takes about 30 seconds to boot, which is not any slower than a Windows machine. It is nice not to have the adapter sticking out the front, but everything nice and flush. I might put a pic of my setup on here when I get finished.
I also have to find an enclosure for my video adapter, and neaten it up.
Thanks all, for your help,
Jeff
-
you can not write the changes to a read only cdrom (device)
you dont need to save any changes in reference to the cdrom.
you took care of it by making your icon (in reality a small text file) settings.
hdtoolbox usage wuill at least show you devices, but you only poke around in it for
hard drives scsi zip drives or the good ole syquest. tape drives and cd drivew will always come up unknown and thats normal.
type "info" in a shell. you should see something like this:
[root] Network:Users/root> info
Mounted disks:
Unit Size Used Free Full Errs Status Name
CD0: 330M 169056 0 100% 0 Read Only CDROM
RAM: 167K 167 0 100% 0 Read/Write Ram Disk
DH0: 300M 135826 480150 22% 0 Read/Write WB_3.1
DF0: 837K 761 997 43% 0 Read/Write Floyd
DF1: 837K 761 997 43% 0 Read/Write Pink
Boot: 22M 6449 40299 14% 0 Read/Write Boot
DH1: 202M 18635 396659 4% 0 Read/Write Network
DH2: 500M 69816 956182 7% 0 Read/Write U0
DH4: 10M 14 21584 0% 0 Read/Write Scratch
Temp: 33M 41853 26689 61% 0 Read/Write Temp
DH3: 200M 281673 129013 69% 0 Read/Write Work
IDH0: 95M 52434 144016 27% 0 Read/Write AZip-013
Volumes available:
Library [Mounted]
CDROM [Mounted]
Ram Disk [Mounted]
AZip-013 [Mounted]
Work [Mounted]
Temp [Mounted]
Scratch [Mounted]
U0 [Mounted]
Network [Mounted]
Boot [Mounted]
Pink [Mounted]
Floyd [Mounted]
WB_3.1 [Mounted]
[root] Network:Users/root>
it looks like you are busting your way into the nuts and bolts and fun of the amiga.
-
Well, that makes sense. That makes a LOT of sense. Thanks for the info. I thought that if it was working, there couldn't be much wrong.
Thanks again,
Jeff
-
Well, that makes sense. That makes a LOT of sense. Thanks for the info. I thought that if it was working, there couldn't be much wrong.
Thanks again,
Jeff
He is right, once the cd shows up you are done. no way to save changes to a non-writeable device ;)
If you want to burn cd's look for makecd.
Normally hdtoolbox will not even show cdroms unless its patched.
Someone above mentioned scsi lister,it is a handy tool for finding devices.
In any case,glad you got it all working.
-mech-
-
Well, got to playing around with my CD in Classic WB. Got it working pretty easily. I just ran the install on AmiCDROM, and it pretty much did it, I just had to put in a few variables, like SCSI ID. Pretty much left everything default. It asked what memory to use as a buffer, and the choices included chip ram, fast ram, and maybe DMA, not sure. I checked use any memory available. Anyway, it works, so I can make CDs now with my favorite software, and have an easy way to go from my PC to the Amiga. Thanks to all for the help. I've got some sound questions about Classic WB, but will start another thread on that.
Thanks bunches,
Jeff
-
One more question, though. When I burn a CD in my PC, what format should I burn it in for best compatibility? There are several options in my burner software, which is K3B for KDE desktop. I used it and read a Windows 95 CD i put in it last night, but just want to use the best format.
Thanks,
Jeff