Switched from A3000 SCSI to WarpEngine SCSI???

[amigadave]

After removing my A3640 and replacing it with a 3040 WarpEngine accelerator card, I am getting the following error messages that prevent my OS3.9 installation from getting all the way to a Picasso96 screen on my RetinaZ3 graphics card.

Cache CDFS
Cannot open "scsi.device" unit1
Abort

After that error appears another message opens in front of it that says:

System Request
Intuition is attempting to reset the Workbench screen, Please close all windows, except drawers.
Retry     Cancel

I have looked all over trying to find where the CDFS env-archive file is or where it is started in the Startup-Sequence, or User-Startup files, but have not found where I can reroute CDFS to the warpdrive.device.

I have forgotten more Amiga stuff than I remember these days and I know this is something simple.  I just can't think of it right now.

[jmbattle]

How about devs:mountlist ?

Cheers,
James
x

[MozzerFan]

I think it's devs:dosdrivers/cd0.

Regards,
Lloyd

[amigadave]

jmbattle wrote:
How about devs:mountlist ?

Cheers,
James
x

No such file exists in my system.

Any other ideas or help?

[amigadave]

MozzerFan wrote:
I think it's devs:dosdrivers/cd0.

Regards,
Lloyd

Not there either?

[MozzerFan]

Can you name the files which are in devs:dosdrivers?

Regards,
Lloyd

[wawrzon]

ive never had a warp engine but sure u have a problem with a cd drive_id number within your scsidevice driver. it's location must have changed when u switched to another scsi cintroler. first of all under 3.x systems if i recall right u have to have a device in ur devs/dosdrivers called "cdo" which contains information about where to find ur cd-rom drive and how to deal with it.if u dont there is a template in ur strorage/dosdivers that u will have to modify. further there probably is cdfs prefs in ur prefs drawer. i recommend the program scsi_lister that ive got from aminet if i recall it right. otherwise use another system monitor. locate ur scsi_device, an unit_number of ur drive and fill in the cdo-driver or its tooltypes (depends on cdo-file version u use). maybe u have to check cdfs-prefs too.
hope that helps. (sorry 4 my typing, good luck)
 

[amigadave]

Okay, found CacheCDFS program in Workbench/Prefs (don't know how I missed it the first time) but when I run it, there is no way to assign the warpdrive.device instead of scsi.device.

When I choose information in the menu when it is highlighted there is no device=xxxxx.xxxxx.  Should I just add a line that equals this?

DEVICE=warpdrive.device

I ran the SCSI tools that comes with the WarpEngine and it did not detect any CDROM, only the hard drive.

[MozzerFan]

The CacheCDFS prefs program is only for settings of
cdfilesystem (cachecdfs). The cdrom is mounted by
a mountlist which must reside in devs:dosdrivers.
That's why I asked which files are in your devs:dosdrivers
drawer,

Regards,
Lloyd

[amigadave]

MozzerFan wrote:
The CacheCDFS prefs program is only for settings of
cdfilesystem (cachecdfs). The cdrom is mounted by
a mountlist which must reside in devs:dosdrivers.
That's why I asked which files are in your devs:dosdrivers
drawer,

Regards,
Lloyd

No mount list, no CD0: in Devs:DOSDrivers

I have used mostly AsimCDFS on my other Amigas as I have never understood how CacheCDFS works in OS3.9, or OS3.5 for that matter.  I guess I could go through my L: and Prefs: and delete all signs of CacheCDFS and just install AsimCDFS instead, but thought I would try to figure this out and stay with CacheCDFS for a change on my A3000T.  It was working fine with the stock A3000T scsi controller and all I changed was to install the WarpEngine and move the SCSI cable to the WE's SCSI controller, as it is so much faster than the onboard one.

I am stumped!

[MozzerFan]

Forgive me for doubting you, but can you do the following:

Startup a cli window and type: List devs:dosdrivers/#?

If really nothing shows up, what you can try is copy
cd0 and cd0.info from the devs:dosdrivers drawer from
your emergency startup disk and then change it.

Regards,
Lloyd

[Boot_WB]

Bear in mind, it does not have to be called CD0 or anthing like. It would, as Mozzerfan said, be useful to list all files in the devs:dosdrivers directory.

You could also have a look in your startup-sequence and user-startup files. There could be a "MOUNT randomlocation/randomfilename" command in there.
Also, the mountfile could be in the wbstartup drawer, with the file associated with "mount" in the icon prefs.

Also, when you do find the file (and it is there somewhere!), change the device name in both the text of hte file itself, and in the tooltypes. I'm sure one is dominant over the other, but buggered if I can remember which.

[amigadave]

MozzerFan wrote:
Forgive me for doubting you, but can you do the following:

Startup a cli window and type: List devs:dosdrivers/#?

If really nothing shows up, what you can try is copy
cd0 and cd0.info from the devs:dosdrivers drawer from
your emergency startup disk and then change it.

Regards,
Lloyd

As I said I have no CD0: in devs:dosdrivers, but here are the results you asked for anyway (you are very kind to try to help).

PIPE
VNC
VNR
EMERGENCY_CD
PC0
AWNPipe

I left out all the .info files that are also there, but that is it.

As I said, the CDROM used to work fine without any apparent CD0: dosdriver file, so I am really confused about how CacheCDFS works???

[Boot_WB]

Emergency_CD sounds like a good bet :-P

Use a text editor to open it.
Change the line:
Device = scsi.device
to
Device = warpdrive.device (or whatever the warp engine scsi device is called)

EDIT - also, make sure you check the tooltypes, as mentioned previously.

Reboot.

Regards



Rich

PS - Just noticed this info on Amiga.resource.cx:

# Fast SCSI 2 controller  NCR 53C710 @ 40 MHz
...
# autoboot ROM (warpdrive.device) - can be disabled by a jumper
# incompatible with the A3000's motherboard SCSI controller - replacing the A3000's SCSI chip to rev. 08 solves the problem

Which A3000 scsi chip do you have? iirc the A3K comes with rev04 as default...
Also, best to check that the autoboot rom disable jumper is not set, otherwise you will probably need to put warpdrive.device into devs: for this device to function.

[MozzerFan]

You might want to check out the emergency_cd mountlist.
Just edit it with editpad. If it uses the l:cachecdfs
handler, you've found your problem mountlist.

Edit: BootWB was faster than me.

Regards,
Lloyd