SCSI CDROM - Help Required

[diablothe2nd]

So after getting my 1d1 nice and stable by removing two caps, I've finally been able to get AOS3.9 installed on my SCSI HD via the BPPC. It's certainly faster than CF card! CF only got 1.5mb/sec while the SCSI drive is a more respectable 6mb/sec and it is REALLY noticable.

Anyway, I cannot for the life of me get the SCSI CD Drive to mount a disc. I have no other computers equipped with SCSI to test it so I've no idea if it's faulty.

from the BPPC I have an interal 50 pn adapter, going to a ribbon with 3 50 pin connectors, on the end the ribbon has a Terminator. the hard drive is the first device in the ribbon chain, pins are set to Device 0 (as the BPPC itself is device 7). next on the chain is a small external connector (not used) then another 50 pin going to the CDROM. pins on CDROM are set to device 1 and termination is active (dunno if that conflicts with the active terminator on the end of the cable, though but i tried without and no difference)

in the early boot SCSI menu i've disabled all other devices with exception to 0 and 1. set the LUNs to 1 for each, and Asynchronus. hard drive is set as non removable no cd, cd drive set to cd removable.

i'm not at all knowledgeable with SCSI so i think i've done well to even get this far! hehe

I can take photos of all the screens in the SCSI menu if needed.

software wise, i used the CS SCSI tools from Ph5 site to mount, partition and install the HD. NOTE that i cannot see the cd rom device in this list, just the quantum fireball hd.

so far CD wise i've tried installing from the AOS3.9 cd the cd drivers. no joy. just CD0 uninitialized icon on desktop.

I think the problem lies somewhere in the configuration of the drive, as i dont see it in the SCSI Tools nor in HDToolbox when perusing the BlizzPPC.device.

any of you SCSI folk have any ideas?

[roy bates]

if ive read it write.
you should have actice termination on the last device dont put termination in between two or more devices.
the other thing is,do you have a dos driver for the cdrom? setup for the device.

[diablothe2nd]

Originally Posted by roy bates

if ive read it write.
you should have actice termination on the last device dont put termination in between two or more devices.
the other thing is,do you have a dos driver for the cdrom? setup for the device.

no it goes

BPPC > HD > mini 50 connector (not used) > CD ROM (terminated) > Terminator
dev7 > d0 > --------------------------------> device1


there is cd0 or whatever its called in the devs/dosdrivers drawer

[diablothe2nd]

Images of my early boot scsi setup and whats seen in hdtoolbox

[diablothe2nd]

Sussed it!!!

i removed the internal termination from the cd drive, and increased its id number on the jumpers. then set the blizzard scsi settings to autodetect one higher in the id list.

i can now see the cd drive in hd tools and more importantly in the AsimCDFS lister

seems to be a difference between device number in the startup menu, the actual drive number with jumpers and what it sees in os3.9 but it works and the cd spun up!

[diablothe2nd]

ARGH!

still cannot see the CD inserted

and in AsimCDFS Prefs it's not showing the drive (think it's looking at scsi.device instead of blizzppc.device??) can see it in the SCSI_Inquire tool and HDtools though.

[diablothe2nd]

Ok, more info. just put an AmigaFuture disc in the drive, icon appears on desktop.

CU Amiga disc, didn't.

i guess i need some form of dos driver for isso joilet etc? surprised these didn't come with AsimCDFS

[diablothe2nd]

ok i think i've found the problem, AsimCDFS_Prefs doesn't display my device so i cannot switch to Rockridge or Joilet et al.

tried editing the tooltypes to say:
DEVICE=blizzppc.device
UNIT=1

doesn't work

tried launching from cli with various options, but no joy either. asking for syntax simply tells me:
CDROM/k



sussed it!

i put CDROM=CD0: in the tooltypes

[roy bates]

glad you got it sorted.

you might want to run a cd cleaner disk through it as well.

[diablothe2nd]

the drive is "reconditioned" but the thought had crossed my mind.

i still have a weird problem with some CDs - some will show only 8 letters broken with a ~ on all the files, yet i've turned truncation off on all settings.

[roy bates]

are you buring your own cd's?
or are you using the originals?

it might be a joliet problem maybe.

[diablothe2nd]

seems to be the case on my burned TOSEC collection... found a couple of mag discs that do it too though.

perhaps i can copy the discs that are playing up in my peecee in joilet mode?

[Loedown]

Originally Posted by diablothe2nd

the drive is "reconditioned" but the thought had crossed my mind.

i still have a weird problem with some CDs - some will show only 8 letters broken with a ~ on all the files, yet i've turned truncation off on all settings.

That's an old problem with long file names from the DOS days of 8.3

readthis.txt for example whereas readthisfirst.txt would truncate to readth~1.txt

[diablothe2nd]

yep it's that exact symptom, but on my winblows system, the long filenames are fine :/

[Loedown]

Originally Posted by diablothe2nd

yep it's that exact symptom, but on my winblows system, the long filenames are fine :/

Older versions of Windows will exhibit the same problem, 98SE if memory serves will act like this whereas 2000 onwards will not, it's to do with long file names.

[diablothe2nd]

Originally Posted by Loedown

it's to do with long file names.

agreed

just can't seem to get my amiga to stop truncating, when other discs like Amiga Future display just fine.

[ElectroBlaster]

Im gearing up to SCSI again some time soon! Have everything nearly... apart from a cd-drive. I have seen some re-conditioned Teac's on fleabay.

Dont suppose that is the one you have is it? Hoping it is as im planning on buying one and putting in a decent case.

[diablothe2nd]

no, mine is a reconditioned NEC with black fascia. forgot the model No.

[Hedeon]

I think if I remember correctly, with CacheCDFS (on the 3.9 CD?) you have correct names without the ~ character at the end.

[diablothe2nd]

ah forgot about this thread, yeah i did a complete fresh reinstall, but created a new emergency disk before i did.

everything worked great, so it must've pulled something from my hd/cd to the emergency disk involving my new hardware (which wasn't there when i had this problem).

cache was annoying me as i kept getting duplicate disks on the workbench backdrop, and the drive is fast enough (5.8mbit/sec) to not need it, so i disabled it.