#SetPatch Fails A3000/3.1
01-Oct-94 12:42:09
Sb: #165575-#SetPatch Fails A3000/3.1
Fm: Harald W. Schulz 100022,744
To: Dave Arre 70337,1642
Dave, allow me to drop in:
For a couple of weeks I try to find different opinions and experiences
with OS 3.1, and so I followed this thread …
Two years ago I had a similar problem with a 68030-board; some programs
did crash when they should run, and I still had installed WB 2.0 at this
time… just deactivate the setpatch-command in the startup-sequence
…
-> ; setpatch >nil: QUIET
…
Boot and try to switch the caches on with 'CPU CACHE'; if you get a crash,
then you might have a broken chip on your board, and the FPU will not
work. I know this could mean bad news for you; 3-( ; if your board will
really be faulty, there are only two solutions: sent it to service, or
change it.
If you can live with the lower speed (without cache), try SETPATCH with
the option NOCACHE 🙂
But I hope for you, it's something else…
Harry with AP