Welcome, Guest. Please login or register.

Author Topic: Kickstart oddities with WB3.1  (Read 4081 times)

Description:

0 Members and 1 Guest are viewing this topic.

Online SkulleateRTopic starter

Kickstart oddities with WB3.1
« on: September 20, 2024, 12:44:55 PM »
I created a simple HDF with just the Workbench 3.1 files on it (not installed, just a "COPY DF0: to DH0: CLONE ALL" ) but if I set that up on the A600GS I only get a Red Screen (Rom error) with JIT and a Software Failure without JIT enabled ... but when I make the same setup only using the ADF everything works (but slow of course) and it´s also showing me the correct kickstart/wb version after boot.

The HDF works fine in FS-UAE and Amiberry on my Mac, so what is the problem here ?
 

Online SkulleateRTopic starter

Re: Kickstart oddities with WB3.1
« Reply #1 on: September 20, 2024, 01:32:02 PM »
Just switched to A600GS-AGA config and here the HDF ist booting but looks "weird"  :o

 

Online SkulleateRTopic starter

Re: Kickstart oddities with WB3.1
« Reply #2 on: September 20, 2024, 03:50:07 PM »
Isnt that loading the AROS rom, hence the odd icons and stuff. Plus your getting verbose output in CLI, which happens with AROS rom.
Kickstart 51.51 is not 3.1, 3.1 is 40.68

Sure, that´s the replacement ROM because I changed from A1200 config to A600GS-AGA config, the point is -> the HDF is working but it isn´t with Kick 3.1 in A1200 config ! That´s my point  8)
 

Online SkulleateRTopic starter

Re: Kickstart oddities with WB3.1
« Reply #3 on: October 05, 2024, 07:15:33 PM »
Ok, I had a retry with my old A1200/OS3.9 setup and that works with A1200 Config and Kick 3.1 ... seems that FS-UAE did some funny things with my HDF, just created a new one on WinUAE in a VM on my Mac and that works perfectly. So sorry for the "fake news"  ::)
 

Online SkulleateRTopic starter

Re: Kickstart oddities with WB3.1
« Reply #4 on: October 06, 2024, 12:03:52 AM »
Probably worth checking for any FS-UAE updates.
Probably not, last update was around three years ago ... ;)

But since i know the problem I also know how to workaround ... thanks :)