»

[keropi]

after solving the strange non-booting problem (had to re-sit the G-Rex) I noticed that when using the ppc, after a while the amiga reboots, and sometimes it crashes so bad that even if it reboots in won't load OS3.9 ... here is a what I have noticed until now... with the default 3.9 datatypes, setting the color/dither quality to HIGH and applying a jpg backdrop the amiga crashes. setting to good is OK. I run the warp3D test, gears_ppc_window. it runs fine for about 10secs and then I get a reboot. When using the 68k I have not experienced any crashes yet. I use a mATX 250W psu, connected to the 4000 via an Elbox ATX converter, the ppc has a 50x50mm 12V installed and there is a 100x100mm fan on the top blowing air at the csppc. (the ppc fan "sucks" air and blows it to the heatsink)... I have a somewhat clean 3.9 installation, g-rex drivers, cgx4, warpOS update, warp3D, warpDT datatypes, and I also run magic-menu and alt-tabber... nothing gave me probs when I had a 1200 with a g-rex + 060bppc...
any recommendations ?
what should I look for to pinpoint the prob?

edit: forgot to mention, I have changed NO ppc variables whatsoever (do I need to change some? dunno, on the bbpc I only run bppcfix...), and on the ppc-menu I have set the ram to the 60ns option. (ram installed is 60ns...)

edit2: run for 15min the 68k gears warp3d test... no crash, rock solid

[Thomas]

Check if the fans are actually working. Leave the case open for a while. Set RAM speed to 70ns.

Bye,
Thomas

[keropi]

hey thomas... the fans are working, and the case is open (due to testing) and the 100x100 fan is external and not sitting on the busboard holder and the cd-rom... I just put it there to blow fresh air...
csppc is cool... it does not overheat...
also tried to play some mp3's using amigamp's warpOS engine... after 5-6secs it crashed...

[AMIGAZ]

Feels like bad contact between the CPU card and the CPU slot, are you using the right spacers? so that the card is fully seated and horisontal
I had this problem before my CSPPC came fully loose in my tower now it's bolted down with treaded spacers

[keropi]

no, spacers are OK my friend Amigaz... after some testing and removing all wbstartup progs, it seems that phase5 CYBERPATCHER was causing this prob... gears_ppc do not crash anymore, gonna try after some reboots , and leave it render for a while...

[x56h34]

My guess would be that your simms are not too compatible with CSPPC. Get four matching simms of a quality brand name (Micron is always reliable) and make sure that the ram-speed is 60ns. I prefer to use plain FPM type, but EDO will work just fine.

[keropi]

u think? I have no probs now... I removed cyberpatcher... my simms are on sockets 1,3 IBM 60ns, and on 2,4 a 60ns pair I got from amigakit... I will check it to be sure...

[keropi]

nopee..... leave the ppc_gears and it will eventually crash... damn! tried many ram combos, still the same... even tried 2x8MB EDO ram, still crashes... I have tried 4 different pairs, always crashes after some time... is it broken??? I am gonna boot MOS PUP now to see what happens...

[stopthegop]

Take a look in WarpOS Prefs. I had similar problems early on. First, make sure memory protection is enabled. The other thing I recommend fiddling with is the "Videaddress" variable. It defaults to "ignore". When I set it to either "fallback to videoaddress" or to "always use "videoaddress" the system is MUCH more stable. At least for my setup, which is a little different. I have P96 and Voodoo 4 card. Also I use SFS, not FFS.. Not sure which filesystem you have? Actually, thats something else you might want to look at, the filesystem. Mine has proven more stable using SFS instead of FFS. I don't think that is the cause of your current problem though.. Try that videoaddress var. Worked for me..

[stopthegop]

sorry, duplicate

[keropi]

memprotection was disabled, and videoaddress was set to fallback... I changed it to always use it...
also I tested the ram with a cli memtester under pure dos, both fast and chip are fine...
gonna test more...
mos did not boot, complains about me not having/too old 680x0 lib...

[keropi]

warpOS prefs did absolutelly nothing...
as for the filesystem, I am using the default 3.9 one + both boingbags... FFS

[stopthegop]

That sucks. Are you running out of chip memory maybe? Wbprefs -> images in: "Other memory"? There is a brand new update to wballocfast library (v2.01 I believe) which I call very early in startup-sequence. Works great. Keeps everything possible in Fast Ram -- ram which theoretically is all running at the same speed. I think there are problems regarding speed/syncronization of access to fast ram vs. access to (slower) chip ram. Also I set the PPC to NOREADWAITSTATE and NOWRITEWAITSTATE and the ram speed to AUTO. On the 68K I set NOREADWAITSTATE only. If I set 68K to NOWRITEWAITSTATE the machine won't even boot. Based on what you report I think the problem is more likely software than hardware.. But having used pee-sees for so many years, I'm naturally inclined to think that. Can we take a gander at your start files maybe?

[keropi]

seeing my s-s I think will not reveal much... it is a clean 3.9 installation, + bb1/bb2 , + warpos 5.1 update + 060 libs + cgx4...
weird is that when not using the ppc, all work great. even gears 68k run for about 20min without prob.
but when the ppc gets used, after a while it crashes...
gonna try ur mem settings to see if it any better...
also tried with only the voodoo3 on the g-rex, no difference at all...

[stopthegop]

Good luck. I'll sleep on it and let you know if anything relevant occurs to me. Coming up on 0500 here in NY... L8 4 me, early for the 1st shift. Zzzzz...