ramlib_PPC data access exception

[Vincent]

I have 2 fans in there now, an old PSU fan extracting heat out through the 3.5" drive bays and an old P500 fan cooling the 040 and ppc, I can't see it being heat related.

--edit--

There is also the original ppc fan on the board (the p500 fan is on the cooler/040 side and the original fan on the other).

The errors come up right after a cold boot after being switched off for 24 hours, so I'm pretty sure it's not heat related.

[Ryu]

Well you said it was working fine the other day vince so err what did you do to break it? whatever it was remove it and try again :-)

Personally I would check you have the WarpOS prefs setup properly, I forget what settings I use... but you have my settings already on CD so :-)

[Vincent]

I haven't installed anything, that's the strange thing.

The only thing I've done since getting it working was change screenmodes of progs to use the bvision, that was it.

I spent most of the time playing ArTKanoid ;-)

DoomWOS is working now, but anything else that uses the PPC comes up with the same error (W3Ddemos, Quake, Payback)

[Vincent]

Okay, tried your settings (deleted my CyberGraphX, PowerPC and Warp3D dirs and copied yours over).

No change, DoomWOS still works, everything else is up the swanny :-(

[Vincent]

Problem solved (well, the Warp3Ddemos work so I thought I'd post with what I did asap before anything else happens ;-) )

Checked out my libs dir and I had the following in Warp3D:

GFXDrivers
W3D_CyberGFX4.library - 40,292 bytes - version 4.2
W3D_CyberGFX4_PPC.library - 16,128 bytes - version 4.0
W3DPicasso96.library - 38,664 bytes - version 4.2
W3DPicasso96_PPC.library - 20,508 bytes - version 4.2

HWDrivers
W3DPermedia2.library - 579,708 bytes - version 4.2
W3D_Permedia2_PPC.library - 502,980 bytes - version 4.2

Now, in my backup (created as soon as the BPPC and BVision were installed and working) I had:

GFXDrivers
W3D_CyberGFX4.library - 38,996 bytes - version 4.0
W3D_CyberGFX4_PPC.library - 15,412 bytes - version 4.0

HWDrivers
W3DPermedia2.library - 93,120 bytes - version 4.31
W3D_Permedia2_PPC.library - 396,812 bytes - version 4.2


Notice the difference?  Mainly in the filesizes of the HWDrivers dir being ~700,000 missing

God knows what happened (or what installation, or me getting libs from Karlos to try Quake stuff...), but it seems to be happy now :-)

[Karlos]

 

Vincent wrote:

God knows what happened (or what installation, or me getting libs from Karlos to try Quake stuff...), but it seems to be happy now :-)

The libs you got from me are implemented rather differently from the original 4.2 - the 680x0 driver really is 93K and really does support everything its 579K predecessor did (and a lot more). The WOS version is a bit larger (180K). The 4.2 driver you had from me was just a quick bug fix and recompile of the original 4.2 source.

Compatibility wise, the 4.3 drivers should work with everything that obeys the W3D API. There is a known conflict with some versions of MiniGL (affects BlitzQuake, for example) which is due to aggressive optimisations in that version of MiniGL making assumptions about the driver and taking shortcuts.

Everything else I have tested worked OK (as I tend to use them on a daily basis ;-) )

[Vincent]

I suppose I should've stated the first list was the "current" (non working) libs, deleted and replaced by the backup ones (2nd list).

@Karlos

I'll try chucking the 4.31 lib back in later on... once I've had some fun in Quake ;-)

[Karlos]

You only have the 680x0 half, so unless you are running 680x0 3D apps you won't see a difference at all. Lemme know if you want the PPC version too.

I haven't as of yet had any chance to benchmark directly the gain of the PPC version (at the function level) since I need to compile a WOS friendly benchmarking tool for it. I doubt the gain will be as great as the 680x0 side (which is more than 2x faster in some cases) since the PPC will most likely reach bus saturation anyway.

[Kraftwerk]

I still say it is a heat issue. Replace the original fan on the PPC (the originals sucked...) with a much more powerful one.

There is no way you can get it to cool. Important is how warm the chip is, so the most important fan is the one on the PPC itself.

Keeping the chip cool did wonders for my system.

[Framiga]

@Karlos

its W3D 4.3 available for public?

[Vincent]

Kraftwerk wrote:
I still say it is a heat issue.

It's been working almost full time since getting it fixed on the 19th with only a few software errors (unrelated - I'm trying stuff out).

The issue was with the libraries themselves.