My Amiga doesn't like exec.library 45.20 (OS3.9).

[Ral-Clan]

After much testing and narrowing down, I've determined my A2000 just doesn't like the new exec.library (v45.20) contained in the AMIGAOS ROM UPDATE file of OS3.9's Boing Bag #2.

When Setpatch implements this ROM update, the computer re-boots, but then freezes on a grey screen.

I got a Kickflash card, and was able to install all the updated ROM modules from this file separately.  Every one of the new OS3.9 ROM updates installed & worked fine, but as soon as I added the new exec.library (of even installed it by itself) the Amiga would always freeze on a reboot.

Can anyone think what might be conflicting with this new exec.library?

My first assumption would be my PP&S A2000 68040 accelerator card.  So if any other owners of this card are using OS3.9 I'd love to hear from you.

I know it's not a software conflict, because even from a cold boot with the startup-sequence disabled, if I type SETPATCH from a CLI, I see all the new modules installed, then the Amiga re-boots and hangs immediately on a light grey screen.

Here is my setup:

A2000 rev. 4.4
3.1 ROM.  OS3.0 installed.
DKB MegaChip
A2091 SCSI controller w/ Guru-ROM & latest WD chip +2MB RAM.
SupraRAM card w/ 6MB RAM.
Progressive Peripherals & Software A2000/040 acclerator w/ 32MB RAM.
Repulse audio card.
Kickflash card.
Picasso II graphics card w/ 2MB onboard RAM.

I have been using OS3.9 for years.  But I really didn't notice until recently that the Kickstart version still shows up as 40.63 and not 45.x as it should (probably due to the lack of the new exec.library being activated).  It would be nice to solve this problem and start using the "modern" kickstart.

[Matt_H]

It might not be related, but unless your Picasso II is running in segmented mode, your Zorro II bus is overloaded.

You could also try Piru's Exec44 or an Exec from an earlier 3.9 or 3.5 ROM update.

[Ral-Clan]

I'm not so sure it's a hardware fault anymore.

I just temporarily disabled ROMTAGMEM in my startup sequence (it's the first item in my S-S, and must be executed before SetPatch to work), and I was able to use the updated exec.library fine (in the AmigaOS ROM UPDATE).  My Amiga finally registered as having Kickstart 45.3!  

However, without ROMTAGMEM, I cannot activate the 32 MB or FASTRAM on my Accelerator  :-? .  No good.

[matthey]

There are other newer programs that add memory at a physical address to the free memory pool. They might work. The ROMTAGMEM maybe adds a reset proof program to add the memory at bootup. The old ROMTAGMEM reset proof stuff maybe interferes with the newer AmigaOS 3.9 reset proof update.
The Kickflash I believe plays with the ColdCapture, CoolCapture, WarmCapture reset proof workings as well.
Someone else can probably recommend a good program to add memory to the free pool. The first 2 arguments for ROMTAGMEM are probably the location and size of the memory to add?

[Ral-Clan]

I would love to know of a newer program than ROMTAGMEM to add non-autoconfiguring RAM to the memory pool.  If anyone can suggest a more up to date solution I would appreciate it.

The first 2 arguments for ROMTAGMEM are probably the location and size of the memory to add?

Yes, the command looks like this in my Startup-sequence

ROMTAGMEM -D 8000000 2000000 5 10 ;activates 32MB of 32-bit FAST RAM on accelerator card.

the -D tag causes a warm reboot to happen.  I don't know what the 5 and 10 settings do.

Strange thing is, the 32 MB on the card is mounted in two chunks.  One about 28MB and the other 4MB.  But that's another mystery altogether.

[Robert17]

I used to have a PP&S 2000-040 card, it never would work with the Boingbag romupdates, I had to put "NOROMUPDATES" next to something in the startup sequence, though I don't remember what exactly.

Robert

[matthey]

The first 2 numbers are probably the physical addresses of the memory to add and the second 2 maybe the memory priorities of them? We need Piru for this one. He has all the answers on these hardware specific problems ;-).

[Matt_H]

@ ral-clan

Try the ROMTAGMEM command without the warm reset. Sometimes a whole bunch of modules that need a reset can be kicked in with a single reboot. For example,

SomeModule NORESET
SomeOtherModule NORESET
SetPatch

There are some AddMem programs on Aminet that might help, too.