»

[thewalrus]

Can anybody help? I have a 4000T with Cyberstorm PPC and are having problems making a hard drive with a bootable System partition boot from the Cyberstorm Scsi Bus. I have no problem booting with another HDD attached to the 4000T's own Scsi Bus however when using another drive attached to the Cyberstorm Scsi Bus with a bootable System partition installed on it I get the error "program failed error #80000008" right at the start of the boot process. I have tried a fresh install of 3.9 1&2 and nothing else but the Cyberstorm sofware installed and only that one drive attached to the computer. I also tried a fresh install with nothing else but the 3.9 warp PPC software but still the same problem. I have tried copying over my existing system partition attached to the drive on the 4000T Scsi Bus with the Cyberstorm software installed but still the same. I have taken out zerro cards and checked the settings in the Cyberstorm boot menu. The drive attached to the Cyberstorm comes up fine when booting from the 4000T Scsi bus Its only when I make the other drive on the Cyberstorm Scsi bus bootable the problem arrises. I could leave the system partition on the drive attached to the 4000T own Scsi bus and use the drive attached to the Cyberstorm for other partitions and software but would like to solve the problem Can anybody help

[Jeff]

I have a similar setup working well. The only difference between yours and mine is my card is only CS MK III 060, however I think the SCSI portion is the same.

Make sure you have proper cabling and termination on the CS SCSI side (IE the upper 8 address lines).

I am currently not using the SCSI on the A4000T motherboard so I have A4000D 40.68 roms installed which drastically reduces the boot up time. Also make sure no hard drives with a bootable partition are on the IDE buss. Mine only has a CDRW drive as master currently and that also helps. It seems that 40.70 roms and the A4000T IDE are a less than ideal combination.

Sorry if none of this helps but it's all I can think of at the moment.

[x56h34]

@Jeff:

Interesting to know that A4000T works well with A4000D roms. I guess the only difference between 40.68 and 40.70 roms is the addition of the SCSI controller driver in 40.70 and removal of the workbench.library so that the SCSI driver could fit instead. :-)

[Jeff]

It actually works much better with 40.68 if you can live without the onboard SCSI. Even the IDE buss works correctly with a Hard Drive and CDR (master and Slave).

[thewalrus]

When I copied over my System partition to the drive on the Cyberstorm Scsi bus (with cyberstorm software installed) and booted with that drive the error came up. If I soft booted I got a red screen which suggests a rom failure however booting up the other drive on the 4000T Scsi bus with still the drive attached on the Cyberstorm (non bootable)everyting works fine. As mentioned the problem only arises if I make the Cyberstorm Scsi drive bootable. I have tried another Scsi drive on the Cyberstorm side with nothing else attached bar CD rom on IDE side as well with a clean install and still the same problem. I even tried another Scsi cable termimated at each end. After a fresh install of 3.9 1&2 the red screen does not appear on a soft boot anymore however it still crashes after starting to boot. I even reformatted one of the drives before reinstall. The problem seems to be with the scsi bus or it not liking some software on boot. maybe some one could give me there Cyberstorm boot menu settings so I can check against mine
regards the Walrus

[doctorq]

What are the SCSI setting set to in the CSPPC SCSI menu? Try setting them all to auto, to see if it helps.

About the computer crashing on boot; have you remembered to install the 040 and 060 libraries?

[thewalrus]

Done all of those things
Thanks for your help though!

[X-ray]

Recently a guy had a similar problem because of the filesystem. He had a FFS on the plain SCSI side, and formatted a drive SFS on the Cyberstorm side, and then he had the same problem you have. Long shot, but are the filesystems the same (you formatted both drives the same filesystem) or you have saved filesystem changes to the Cyberstorm drive?

[mdivancic]

Try disabling SetPatch. Your board may not like one or more of the libraries that is being patched. I've had this problem with 3.9 and other accelerator's SCSI ports. Also, have you upgraded the install to BB2?

Mike

[thewalrus]

Hi there yes I have installed BB2. Thanks for your suggestion regarding Spatch as it gives me the impresssion it is a problem such as this Kind regards
the walrus

[thewalrus]

Hi thanks for your suggestion but FFS is installed. What I did was copy my existing files over after setting up new partitions on the new drive My existing files include 3.9 BB1 and BB2 I had also installed the Cyberstorm software before copying the existing files. When that did not work I started again by formatting the drive from scratch and installing 3.9 BB1 and BB2 with no other software I then just installed the Warp PPC fron the 3.9 CD thinking they might have later 060 PPC libaries than the older Cyberstorm disks I also tried reinstalling the Cyberstorm software but no change. Also I had another 4 gig HDD and did a fresh install thinking the Cheeath drive might be the problem and as I have a spare 4000T tried that machine as well. It sort of leaves me with a 3.9 software problem as it is at the very start of the boot process the machine crashes or the Cyberstorm card itself. regards the walrus

[X-ray]

If it does it with two drives them I'm stumped :-?

[thewalrus]

The problem does seem to be in Set Patch!! If I disable it the computer does boot to a blank WB screen after stating I need a newer IDE Fix version (however I had not installed that software) I have just tried reinstalling 3.9 BB1 BB2 without updating the Rom part in BB2 (thinking that might work). It did'nt
Mike as you have had this problem some questions:
1. If I disable Set patch what other effect would it have on the system.
2.Did you use a older set patch
3. I note in the 3.9 S Startup file it states you can set SCSI device a no scsi update command or variable to something (how is that done,what is the something as stated in the S Startup file and would that make a difference I did try changing the "set ScsiUpdate 1" command to "set ScsiUpdate 0"
4. In your opinion do I just leave the system patition on the 4000T scsi controller and have my nice new Cheetah drive on the Cyberstorm controller just with other partitions because It just seems to hard!!
I would appreicate your thoughts and answers and anybody elses for that matter

[Framiga]

If you want to use ONLY the CSPPC UWSCSI chain, disable the A4KT controller from the CSPPC BootMenu (hit the ESC key during the boot)

goto System, ENABLE MapROM and set the "NCR SCSIPatch" option (this switch, disable the A4KT onboard SCSI).

btw . . . do a:

version cybppc.device FULL

to see wich version of CSPPC FlashUpdate you have currently installed.

Take a look also to the "FlashBios.doc" in this archive

http://grex.amigaworld.de/daten/driver/FlashUpdateCSPPC.lha

to know all the options in the CSPPC BootMenu.

[Doobrey]

thewalrus wrote:
The problem does seem to be in Set Patch!!
....
1. If I disable Set patch what other effect would it have on the system.

Setpatch fixes some bugs in the ROM,loads the parts of ROM Update that match the machine it's running on, and does the NSD patch (allows use of >4GB)..oh, and it also enables AGA mode on the A1200/A4000.

Have you tried removing/renaming the romupdate from DEVS: to see if Setpatch still fails? as others have reported problems with parts of the romupdate (although I've had no problems with 3.9bb2 in my A4000 with a CSmkII)