Upgrading to OS3.9 with a WarpEngine?

[jaesonk]

I'm trying to re-assemble an A3KT with a WarpEngine4040. The system
is stripped down. OS3.1 ROMs. 18MB on the motherboard. 128MB on the
WE4040. SCSI HD & CDRW on the WE4040. One internal HD Floppy & one
external HD Floppy.

The OS3.1 install works just fine.

I run into problems with OS3.9. I don't think the WE4040 likes
softkicking the updated ROM. I've read that the WE4040 lacks maprom
support. After setpatch does it's thing and reboots the system, it
crashes on me.

Is there a way to get OS3.9 working with my WE4040?

Thanks,
Jaeson

[Thomas Richter]

Post by jaesonk
I'm trying to re-assemble an A3KT with a WarpEngine4040. The system
is stripped down. OS3.1 ROMs. 18MB on the motherboard. 128MB on the
WE4040. SCSI HD & CDRW on the WE4040. One internal HD Floppy & one
external HD Floppy.
The OS3.1 install works just fine.
I run into problems with OS3.9. I don't think the WE4040 likes
softkicking the updated ROM. I've read that the WE4040 lacks maprom
support. After setpatch does it's thing and reboots the system, it
crashes on me.
Is there a way to get OS3.9 working with my WE4040?

3.9 doesn't "softkick a ROM". It only installs new modules via the
KickTag mechanism of the kickstart.

What you could try is bypass the new modules of 3.9 with the appropriate
SetPatch argument, and then use something like LoadModules (on aminet)
that offers you more options to control in which memory the kicktags end
up. A problem might be that the WE4040 marks memory as "appropriate" for
kicktags even though it really isn't. In worst case, these modules have
to go into chipmem.

Greetings,
Thomas

[Daniele Gratteri]

Post by jaesonk
Is there a way to get OS3.9 working with my WE4040?

I am using a WE4040 on my Amiga 4000T and got no problem with OS 3.9
installation, in fact I did a clean install of 3.9 from the CD and the
system works just fine.

What I can't remember now is if I installed it with an Apollo 4060 and
then switched to WE4040 or not, however I didn't disable any updated module.

Try using the "mmu.library" archive, or run a memtest software for
checking the RAM against errors: maybe some bit is defective and it
gives problems when loading the updates?