Hyperion Entertainment Message Boards

Thanks for the reply. If it were faulty RAM, wouldn't the problem also occur when using the kick 3.2.2 and booting to 3.2.3? I have tested my DRAMs and they all passed OK.

Where are you reading the odd ROM being on/off please? I am using an ECS V4, which may explain the Denise difference?

Using kick start 3.2.2 and OS 3.2.3 I have no issues at all, but as soon as I use a kickstart 3.2.3 ROM, it fails to boot consistently and often. If it were RAM, wouldn't the problem also occur in 3.2.2?

No, since 3.2.2 rom does not use first 16K, and 3.2.3 uses ram from 4K and up.
If the updated 3.2.3 modules are loaded from disk, then in theory it should behave the same as hardware 3.2.3 rom.
Timings might be a bit different since execution from ram is faster.

Hi,

I swapped out my ECS V4 with my real Denise, and ShowConfig now reliably shows I have an ECS Denise.
I disabled my Phoenix Board SCSI entirely, and now all the expansions appear in the Boot ROM menu, under expansions.

I tried another 3.2.3 Kickstart ROM from Sordan.ie, but unfortunately the crashes continue. Swapped back to the 3.2.2 kickstart, and my machine boots reliably again. I am still using Workbench 3.2.3 with the Kickstart 3.2.2 ROM, looks like I need to live with the double boot.

Yes, perhaps timings are different, any chance of a 3.2.3.1?

Is it normal that when loading the ROM from Disk, the reporting kickstart, exec and disk versions from ShowConfig report the actual kickstart ROM and not the 3.2.3 patched ROM versions?

Operating System: Kickstart version 47.115
Exec version 47.13
Disk version 47.5

ShowConfig Version: 47.38

--------------------------------------------------------------------
Operating System: Kickstart version 47.111

Exec version 47.10

Disk version 47.5

ShowConfig Version: 47.38

Yes, it it normal to see slight variation in reported version of kickstart since when soft kicked it is more exec version based and you get real hardware rom details. However, if the modules were activated, you should have the same latest exec version displayed.

I replaced my Agnus socket on a hunch that it might be contributing to my issues. Pleased to report the 3.2.3 ROM now boots without a problem.