#SetPatch Fails A3000/3.1
14 messages in this thread
Steve:
I tried installing 3.1 as you described on the HD, but came up with the
same problem as before (the system crashes with a Software Failure at
boot-up) The only thing I can do to boot the system is to comment-out the
C:SetPatch Quiet line in the Startup sequence.
This is VERY puzzling, as it seems nobody else has this problem.
I might try using your "super kickstart" file next, but I fear the same
thing will happen.
I will write another message telling you what the failure message is,
maybe you can get an idea of the problem.
Talk later
— Dave
I have a 4000/040 and get a software failure on bootup, however, if I
either cancel it or just let it be, the computer continues to boot.
Jim R. Ollick
Using AP from Bergenfield, NJ
James:
That is interesting. If I let it be, or if I cancel it, the computer
cycles through the same thing, always ending in a software failure unless
I boot w/ a ss that does not have SetPatch. I think I let it try 3 times
before I stopped it.
I'm going to download the setpatch file here on CIS and see what the docs
say about it, and what version it is. Maybe that'll help.
BTW, 3.1 seems to be doing fine, the only beef I have is that the color
allocation scheme is screwed up, and I can't use pattern prefs from 2.04.
I nixed the MWB demon program because I don't like the default MWB colors
on my monitor.
I'm glad you mentioned that you get a 'guru' also… I thought I had a
nutty machine (or maybe a prototype) for a while! <g>
More later….
— Dave
Dave:
That's a very interesting problem. I do know that the 3.1 SetPatch
(v40.16) is compatible with the A3000. It works fine on my souped-up
3000T and a friend's stock 3000. Here's the output from my system:
Amiga Operating System
Copyright C 1985-1993 Commodore-Amiga, Inc.
All Rights Reserved.
SetPatch (V40.16) has already been installed. Patch list:
68040 Support Code Loaded
Enabled Advanced Graphics Modes
graphics/WriteChunkyPixel() patched
Memory Pools
Enabled data cache
I actually started using this version of SetPatch before I upgraded from
Workbench 2.1. It worked fine then too, but the patch list was a bit
longer. 🙂 Anyway, there must be something unique to your system that
makes SetPatch crash. Have you messed with your DMAC/Ramsey settings at
all? Do earlier versions (say v37.xx) work on your system? I'm curious
because I've never seen an Amiga that crashes SetPatch. As they say,
there's a first time for everything…
Wayne
Hi, Wayne… thanks for replying & trying to help, looks like I'm going to
need some! <g> I tried a few things, and here's what I found:
1) Booted with WB 1.3 floppy. WB V34.34, SetPatch V1.38 Installed; no
patch list. Booted Fine.
2) Booted with WB 2.04 floppy, WB V37.67, SetPatch V37.10. Booted,
installed fine. PatchList: Enabled Data Cache.
3) Boot with WB 2.04 floppy, with SetPatch V37.38. System crashes. Exactly
the same as the 3.1 floppy.
4) Boot with WB 3.1 floppy, SetPatch V40.14 crashes, V40.16 crashes.
5) Boot from HD, WB 3.1, SetPatch V40.16 System Crashes.
So, it seems any SetPatch higher than V37.10 crashes my system… if only
I knew what these newer setpaches are looking at!
I ran SCRAM before installation (weeks before) to check my system. The
only modifcations I made were:
1) Set SCSI timeout to 2 seconds (based on another person's recomendation)
2) Enabled SYNC SCSI transfers (I put that back to OFF, no change)
Here is what SCRAM is showing for infos:
Motherboard: CPU:68030 FPU:68882
Ramsey: Normal, Code $0d, Page Detect OFF, Burst Mode ON, Wrap Mode OFF.
Gary: Normal, Code $00, Timeout:ON Mode:BERR
Agnus: ECS NTSC 8372 Code $30
Denise: ECS Code $fc
Ram Chips: 1×4, Refresh rate:238 clocks Type:Page Chip:2M, Fast:4M.
BattMem Status: SCSI Timeout:2 Sec LUNs:Only 0 SyncXfer:OFF HostID:Unit6
"Amnesias": Amiga bits OK Shared bits OK
That last entry "Amnesias" originally came up "LOST", meaning the memory
lost power & default settings. I manually revived them by clicking on the
gadget.
My System is a vanilla A3000/25, no boards, single 50 Meg Quantum ProDrive
HD, one floppy.
Does anything here look odd?
— Dave
Dave:
Very interesting. Do you still have your 2.04 ROM's around? If so, try
putting them back in and booting with a 2.x floppy that's equipped with
SetPatch v40.16. I was using v40.16 when I still had Kickstart/Workbench
2.x, so it should work (it did quite a few patches). This might help
determine if it is something that SetPatch is looking for or if you have
some goofy 3.1 ROM's.
Wayne
OK, I'll try that, but I probably won't be able to get to it for a couple
days… no time to tear apart the computer again. <g>
Actually, so far the computer is working fine without SetPatch… things
seem to run quicker too… I might just leave it as is!
BTW, I remember about a year ago I downloaded the SetPatch V37.38 from
CIS, and tried it out on my old WB 2.04 system, and it crashed, so I
relegated it to the trash heap. I would tend to think that, given this
experience, changing the ROMs back would probably not work, either. I'll
give it a shot, though. I just wonder what is it about my computer that
makes SetPatches crash?
— Dave
> I just wonder what is it about my computer that makes SetPatches crash?
So do I! I've never encountered this kind of problem before. Perhaps
there is simply something wrong with your hardware. Oh well… If it's
working the way it is, I wouldn't lose too much sleep over it.
Jim:
I just tried booting with the SetPatch here in the Library, Version 40.14
(mine is 40.16), and got the same thing. Looks like I'll have to live
without a SetPatch.
— Dave
At least until the next release of WB.
Jim R. Ollick
Using AP from Bergenfield, NJ
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
Harry… Thanks for the reply & advice.
I have tried your suggestion about entering the 'CPU Cache' command. That
works. I have since put it in my User-Startup file, due to the increased
performance I get in that mode. The SetPatch is commented-out.
The only thing I can think of at this point is the possibility that
SetPatch is trying to enable Burst Mode on the CPU, which means, since I
have Page-type RAM, that the machine will crash. I think I will try to
issue the command 'CPU Burst' and see what happens… if the same thing
happens as SetPatch, then we may be on to something.
I'll let you know what happens..
— Dave
If you work with 040 and OS 3.1 then look to replace the
68040.lib from your 040 install disk. OS 3.1 contents a old
version of this lib.
NAVCIS from Switzerland Andres Staubli
Version reports 37.30 for my 68040.library, is this the latest? If not
where can I get it?
Jim R. Ollick
Using AP from Bergenfield, NJ