System crash in OS3.9

[cmsj]

Hey

I have just acquired an A4000D with a GVP A4060 (T-Rex II) 060 board with 128MB of Fast RAM.

I've just done a fresh install of OS3.9, BB1 and BB2, and GVP's 68040/68060 libraries (v1.2 of 68060.library, by Ralph Babel).

In CED5, any Save operation causes the machine to immediately hang, I see a busy pointer and the power LED starts flashing and the machine reboots itself. I've tried both the 000 and 020 binaries and it's the same. I also tried running it directly from the CD, just in case the install had corrupted, and it still crashes the machine.

CED4 does not do this, and CED5 on my A600 (with a Vampire accelerator) also does not do this.

I did also try switching to ThoR's MMULib 68060 library, but it made no difference, nor did running his MuForce tool.

I'm happy to provide any information you want, to track this down - I really need my CED!

Cheers,
Chris

[cmsj]

I also just tried doing it on a native screenmode instead of RTG and noticed that I get a Guru - 8000 0003

[geijer]

Hi,

Late answer but:

My crashes while saving was solved by increasing the stack

[cmsj]

Hi,

Late answer but:

My crashes while saving was solved by increasing the stack

That does indeed seem to have done the trick, thanks very much for your reply!

[k1ds3ns4t10n]

Any suggestions on what to increase the stack to? When I type stack in CLI it says it was currently 4096. I set it to 50000 and I still have the system freeze when saving with CED5.

UPDATE: I now realize that setting the stack in CLI is for that session only. I right clicked on the CED icon and went to Information..., In the icon tab, I increased stacksize to 12096 (it was originally 8000) and i no longer have the crash!

UPDATE 2: I also added "stack 12096" to the end of S:shell-startup so that it doesn't crash when launching CED from the command line.

I chose the 12096 size arbitrarily, but so far it appears to be working.

[daxb]

I chose the 12096 size arbitrarily, but so far it appears to be working.

If you don't need to save memory then chose a larger stack value for the Shell. E.g. 65536 or larger. Depends on what you are using. E.g. ghostscript needs a very large stack: http://www.whoosh777.com/index.php?txt=1#startup