Where to find CybPPC.device?

[Quixote]

;-) I just bought the appropriate 68 conductor cable and 68 pin 50 pin adaptor to hook my CD ROM drive to my CyperStormIII's SCSI III controller.
 
:-( Unfortunately, CD0 won't mount.  SnoopDOS reports that the system cannot find cybppc.device, and neither can I.  It doesn't seem to be included with the CyberStorm Install disks, nor on Aminet, et.al.
 
:-? Where would I be able to download this driver?

[_Steve_]

It's in the ROM of the PPC card. It is not a separate device handler like say ahi.device in devs:

5.Ram Disk:> version cybppc.device
cybppc.device 44.69

Do note that on the BPPC cards, its not called cybppc.device though.

[Thomas]

First check if cabling is correct. SCSI bus termination matters a lot on the MK3. The SCSI cable must be *actively* terminated on *both* ends !

Then check if the SCSI ID of the CD-ROM is set correctly. Remember the number you set.

Then check the firmware menu (hold down Esc key during reset). Check that the SCSI bus is enabled (SCSI Patch or NCR Patch must be disabled) and check that the ID number you chose it not disabled.

Then look into the CD0 file and check that the unit number matches the SCSI ID you chose. Check the tooltypes of CD0's icon, too. Tooltypes override mountlist entries.

Finaly you could get the IDEfix archive from Aminet, unpack it to RAM: and start the FindDevice program. It will tell you if your CD-ROM drive is recognised. If it is, then you can read the correct values for device and unit from the program's listviews.

Bye,
Thomas

[Quixote]

:-( Unfortunately, the trouble is more complicated than that.  Currently, I have a SCSI hard drive terminated at the end of the chain, with the CD ROM unterminated in the middle.  SCSI Inquire reports the hard drive as unit number 0 and the CD ROM as unit number 3.  It even correctly reports the manufacturers' names, so I am confident that the connection is sound.
 
For whatever reason, CD0: does not mount, so the icon doesn't appear, and CD0: is not available in a DOpus lister.
 
It's probably down to the mountlist.  The one supplied with the CyberStorm install disks differs from other CD mountlists in a number of particulars, but neither version will mount the drive.  In fact, attempting to use the supplied mountlist will block some applications from launching, such as the shell, while other applications can still launch.  I suspect that the Mount command is waiting on some event that isn't happening.  A reboot is necessary to restore the 'miggy.  SnoopDOS doesn't report anything wrong.
 
:-? Has anyone gotten a fifty pin SCSI CD ROM to run on the CyberStormIII's sixty-eight pin SCSI bus?  How is it done?  May I copy the mountlist?

[KennyR]

Has anyone gotten a fifty pin SCSI CD ROM to run on the CyberStormIII's sixty-eight pin SCSI bus? How is it done? May I copy the mountlist?

The mountlist should not change.

[Quixote]

KennyR kibitzed:

The mountlist should not change.

:-? Not even changing the device from scsi.device to cybppc.device, or the unit number from 1 (the default) to 3 (the scsi device number to which my CD ROM is set?)
 
And if these are "obvious" exceptions, what else are "obvious" exceptions that I've missed?
 
How about HighCyl=11000 when other CD ROM mountlists use HighCyl=999?  I thought that the CD itself didn't change when moved from a CD ROM drive on a Warpdrive SCSI bus, to a CD ROM drive on a CyberStorm SCSI bus.
 

[Thomas]

Please post your mountlist(s).

Bye,
Thomas

[KennyR]

ot even changing the device from scsi.device to cybppc.device, or the unit number from 1 (the default) to 3 (the scsi device number to which my CD ROM is set?)

Well, that's pretty obvious. :-) Although I do prefer to use the UNIT and DEVICE as tooltypes on the mountfile icon... But apart from these, nothing should change. Your host controller still thinks its connected to a 50pin device. Besides which there is no difference in control codes between 50 and 64. Your drive should automatically 'downgrade' itself to SCSI-2 (64 pin drives are usually SCSI-3 or UW). This is transparent.

How about HighCyl=11000 when other CD ROM mountlists use HighCyl=999? I thought that the CD itself didn't change when moved from a CD ROM drive on a Warpdrive SCSI bus, to a CD ROM drive on a CyberStorm SCSI bus.

These perameters make no sense for a CDROM, and any CD filesystem worth its salt will ignore them anyway. On my mountfile they are both set to 0.

[RiFF_RaFF]

Hi!

I have 1 CD ROM, 1 DVD ROM and 1 CD-R connected to my CSPPC. Here is a quick cut`n`paste from my CD ROM. Try it! They are all connected to a 50 pin cable which in turn is connected to a 68 pin cable via a active terminated 68 to 50 pin adapter.
 

/***************************************************************/
/*  CacheCDFS mountlist entry © 2000 Amiga Inc.    */
/***************************************************************/
       FileSystem     = L:CacheCDFS /* The name of the game */
       Device         = "cybppc.device" /* Name of exec device driver */
       Unit           = 3 /* exec device unit */
       Flags          = 0 /* OpenDevice flags */
       BlocksPerTrack = 351000 /* Unused */
       BlockSize      = 2048 /* True, but unused */
       Mask           = 0x7ffffffe /* Memory mask for direct read */
       MaxTransfer    = 0x1000000 /* Maximum amount of bytes for direct read */
       Reserved       = 0 /* Unused */
       Interleave     = 0 /* Unused */
       LowCyl         = 0 /* Unused */
       HighCyl        = 0 /* Unused */
       Surfaces       = 1 /* Unused */
       Buffers        = 50 /* Number of cache lines */
       BufMemType     = 1 /* MEMF_PUBLIC */
       BootPri        = 2 /* Boot priority for MountCD */
       GlobVec        = -1 /* Do not change! */
       Mount          = 1 /* Mount it immediately */
       Priority       = 10 /* Priority of FileSystem task */
       DosType        = 0x43443031 /* Currently unused */
       StackSize      = 3000 /* Minimum stack required is 3000! */
       Control        = "MD=0 LC=1 DC=8 L LV AL LFC=1 S NC AUDIO=Utilities/PlayCD"
   /* The Control field is for special adjustments */
   /* L/S convert all file/volume names to lowercase */
   /* LV/S convert volume names to lowercase */
   /* AL/S Auto-Lower converts only non-Amiga CDs */
   /* LFC/N start converting at this character */
   /* LC/N/A number of blocks per cache line */
   /* DC/N/A number of cache lines for the data cache */
   /* MD/N/A number of blocks, when starting direct read, not using */
   /* the cache. 0 will be a reasonable default (LC*DC+1) */
   /* S/S Do SCSI direct commands, no Trackdisk like commands! */
   /* NC/S Do NOT use TD_ADDCHANGEINT, poll for DiskChange! */
   /* M/S Issue a TD_MOTOR (OFF) command after read */

[Quixote]

RiFF_RaFF revealed:

I have 1 CD ROM, 1 DVD ROM and 1 CD-R connected to my CSPPC. Here is a quick cut`n`paste from my CD ROM. Try it! They are all connected to a 50 pin cable which in turn is connected to a 68 pin cable via a active terminated 68 to 50 pin adapter.

;-) Thank you, sir!  I'll give it a try, and let you know how it goes.  Is there anything special in your CyberStorm's flash ROM settings?

[cdfr]

You said you kave a MK3 ?

Is the scsi device called cybppc.device on an MK3 ?
I thought cybPPC.device would be only for PPC cards.

Cybscsi.device for the mk3 maybe ?

[RiFF_RaFF]

All of them is set to Auto. BTW: Doubleclick any unused units and set them to 0 LUNS to disable them. This will speed up booting considerably as the scsi controler doesn`t need to waste time to scan them!

[Kronos]

@cdfr

The CS-MK3 IS a CS-PPC, just without the 604-CPU ....

(but don't try to "update" one, that won't work  ;-)  )

[cdfr]

OK, I have got the MK1 and the Mk2. Never got a MK3.
It sounded weird that a non PPC card would have a *PPC.device

Forget my post then  ;-)

[Quixote]

:-? Now I'm confused about the designation.  My CyberStorm has the 604e processor, running at 233 mhz, and a 68 pin SCSI III controller.  Maybe that's where the "3" comes in?