Odd issue with a Blizzard PPC board

[x56h34]

I would suggest double checking FastATA controller. See if it sits inside the rom sockets securely (god I hate how they designed this, with the cable ties holding it through motherboard holes designed for 2.5" hd cradle).
I've had lots of trouble in the past with FastATA and BPPC cards due to weak contacts with the FastATA controller and rom sockets, as the controller really, and I mean really needs to be tightened well with cable ties unless you want it to pop out. I would suggest checking if FastATA is seated well.

ATA3Prefs utility almost always declares that a BPPC card is defective. I also suspect that this is related to poorly seated FastATA controller in the rom sockets.

Try removing FastATA altogether and use the native IDE controller, just for a while until you straignten things out.

[x56h34]

Come to think of it, there may be an 040 specific BPPCFix module that comes with BlizKick. Perhaps you need to use that one? :-?

[x56h34]

Framiga wrote:
the SCSI chip is been removed? or the card was originally without SCSI?

 

If he were to post a picture of the board, I'd most likely be able to tell him if there was originally a SCSI chip on it or not.

[x56h34]

Have you flashed the card with the latest flashrom update (the one from 2000, not the one from 1999 that was on DCE's page as the latest one with BVision support, although it was not)?

Have you tried using different simm(s) on the card?

Try placing BPPCFix040 module somewhere else in the BlizKick line. I've had instances in the past in which certain modules would work when placed at a particular spot and not work if placed elsewhere.

Make sure there's enough buffers (I forget the exact name of this) for all the modules to be loaded within BlizKick.

[x56h34]

This is the last one before the Grex flashroms came out:

FlashUpdates-09042000.lha

Not that it's going to make a huge difference, but it might be worth a try to use it.

Later today I will c&p in this thread my startup-sequence script with the blizkick line in it for you to try, so that you could compare it with yours. I have a feeling that it's something very simple that causes problems, but we'll see. :-)

[x56h34]

Here's my BlizKick line. It's the first line of Startup-Sequence file:

Blizkick * EXTRESBUF=165000 HOGWAITBLIT SpeedROM MODULE BPPCFix Bblank NewAlert ROMFIXES Noclick MoveVBR RemCards FixMath404 MuMove4k FixGetMsg scsi.device FastFileSystem Filesystem.Resource console.device Ram-Handler romupdate.idtag shell Bootmenu exec.library NOPUPREBOOT KEEPEXEC QUIET

Setpatch line should look like this:

SetPatch NOROMUPDATE QUIET

If I were you, I'd place the FastATA line after the BlizKick line.