#More Setpatch Info
10 messages in this thread
Steve: I copied the sequence of events that happen when my machine
crashes:
1) Insert WB 3.1 floppy.
2) After 2 sec delay, floppy is accessed.
3) Hard Drive accessed once.
4) Power light blinks 7 times.
5) After about 2-3 seconds the following message appears:
****Software Failure*****
Error: 8000 0004 Task: 07C0DEB0
Press left mouse button to continue.
If I press the left mouse button (or even if I don't) the system goes
through the same steps above, again.
Commenting out the "C:Setpatch Quiet" line results in a fine boot.
Here is my system configuration as reported by the machine:
Processor: CPU 68030/68882fpu/68030mmu
Custom Chips: ESC NTSC Agnus (id=$0030), ECS Denise (id=$00FC)
Vers: Kickstart version 40.68, Exec version 40.10, Disk version 40.42
RAM: Node type $A, Attributes $505 (FAST) at $7C00000-$7FFFFF (4.0 Meg)
Node type $A, Attributes $703 (Chip) at $400-$1FFFFF (~2.0 Meg)
Boards: None
I also notice my machine is slightly slower than it used to be. Any
suggestions?
I think I will try your file and see what happens.
— Dave
Dave,
I have no idea. I've been installing and running every OS update since 2.01 on
my 3000 with never a problem. Hopefully someone will see this thread and jump
in with suggestions. Did you ever, at any time, use BATTMEM or SCRAM or any
other such program to change the default states of the caches? I don't know if
that would negatively affect installation of 3.1 — just a guess. If you did
try to restore it default.
Steve: Yes I did change the BATTMEM settings….
1) Changed the time-out to 2 seconds due to someone reporting that the
ROMs loaded quickly, so the drive wasn't ready.
2) Changed the SYNC bit to ON due to another report…
According to SCRAM, the battmem had suffered an "amnesia" so I don't know
exactly what the defauts are, but I will try to set the SYNC bit back, and
then the timeout and see what happens.
Thanks… talk later
— Dave
Steve:
I put the BATTMEM bit for the Sync SCSI back to NO… no change.
I also noticed that the CPU command would give the following under 3.1:
System: 68030 68882 (INST: Cache NoBurst) Data: NoCache No Burst)
Whereas under 2.04 it was:
System: 68030 68882 FastROM (Inst: Cache NoBurst) (Data: Cache NoBurst)
Turning the Data cache and FASTROM on had no effect, other than to spped
up my computer noticably.
I just don't get it.
Is it dangerous or bad to run without SETPATCH? The machine seems to be
working fine without it.
— Dave
Dave,
No…it's not dangerous per se to run without SetPatch, but what that
does is fix known bugs or problems with the OS. It *may* be that you've got a
corrupt SetPatch file or even possible you've got the wrong version.
Any chance you can recopy the original and see if that fixes things?
Don
Don:
What do you mean by 'the original'?
Both copies of SetPatch (on the Install disk and WB3.1 disk) will not
work. They are Version 40.16. At least, the computer hangs when booting.
The SetPatch line in my 2.04 installation worked, though… it was Version
37.10. I remember trying the updated SetPatch (37.38) a while back, and
pretty much the same thing happened… computer wouldn't boot.
I'm running 3.1 now without SetPatch. Here's what is being reported:
KS 40.68 (in ROM) WB 40.42. I have an A3000 25 , which had the bootstrap
ROM and the SuperKickstart 2.04 prior to this.
I just can't figure this out, as I have heard noone having the same
problem as I have. I even tried wiping the SYS partition (formatting it)
and re-installing 3.1 from scratch, to no avail. I'm at a loss to figure
this out.
Gee, I sure wish someone was home in West Chester…. <g>
By 'the Original" do you mean the old V37.10 2.04 SetPatch?
BTW: Here is my present Startup-Sequence:
; $VER: Startup-Sequence_HardDrive 40.2 (25.2.93)
; Startup-Sequence for hard drive systems
; C:SetPatch QUIET
C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21
C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ
Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE
Assign >NIL: ENV: RAM:ENV
; run >nil: C:MagicWB-Demon 4,123,123,123 5,175,175,175 6,170,144,124
7,255,169,151 8,0,0,255 ; Don't remove this entry!Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Assign >NIL: REXX: S:
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Assign >NIL: LIBS: SYS:Classes ADD
Assign >NIL: HELP: LOCALE:Help DEFER
BindDrivers
C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)
IF EXISTS DEVS:Monitors
IF EXISTS DEVS:Monitors/VGAOnly
DEVS:Monitors/VGAOnly
EndIF
C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) TO T:M LFORMAT
"DEVS:Monitors/%s" Execute T:M
C:Delete >NIL: T:M
EndIF
SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart
C:AddDataTypes REFRESH QUIET
C:IPrefs
C:ConClip
Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs
SYS:WBStartup SYS:Tools SYS:Tools/Commodities
IF EXISTS S:User-Startup
Execute S:User-Startup
EndIF
Resident Execute REMOVE
Resident Assign REMOVE
C:LoadWB
EndCLI >NIL:
— Dave
Dave,
No…by original, I mean recopy from your floppy to your HD.
I see you've done that though.
Don
Don:
I just tried the SetPatch in the library here, V40.14 (I have V40.16), and
got the exact same thing. Looks like I might have to live without a
SetPatch.
Do you think I should try the old 2.04 one? (V37.10)?
— Dave
Dave,
No on the old v2.04 SetPatch.
Don