Can all registered uses please login, even just for a few minutes..
It helps build a picture where our "good traffic" is coming from..
Thanks :)
It helps build a picture where our "good traffic" is coming from..
Thanks :)
CD32, TF360 and AmigaOS 3.2
Moderators: terriblefire, Terriblefire Moderator
CD32, TF360 and AmigaOS 3.2
Anyone here that is running AmigaOS 3.2.x on their CD32 with TF360 here?
I am having the following issue:
I have installed AmigaOS 3.2 and after that the general CPU libraries from the 3.2 install floppy, system boots fine with this setup
When I update to AmigaOS 3.2.2 I get LoadModule failed returncode 10 when booting
I have noticed that the startup-sequence gets some stuff added when updating from 3.2 -> 3.2.2 that must be the root cause but I cannot understand the logic and would appreciate if I could get some help with what I should change, add or edit to successfully get my system up and running
3.2 startup-sequence
3.2.2 startup-sequence, here the extra stuff added with the LoadModule commands must be the culprit. But what exactly?
I am having the following issue:
I have installed AmigaOS 3.2 and after that the general CPU libraries from the 3.2 install floppy, system boots fine with this setup
When I update to AmigaOS 3.2.2 I get LoadModule failed returncode 10 when booting
I have noticed that the startup-sequence gets some stuff added when updating from 3.2 -> 3.2.2 that must be the root cause but I cannot understand the logic and would appreciate if I could get some help with what I should change, add or edit to successfully get my system up and running
3.2 startup-sequence
3.2.2 startup-sequence, here the extra stuff added with the LoadModule commands must be the culprit. But what exactly?
-
terriblefire
- Admin sponsor

- Posts: 5687
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: CD32, TF360 and AmigaOS 3.2
This is a question for the OS 3.2 team. Not really much i can help with here. I've not tried 3.2 on the CD32 yet
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: CD32, TF360 and AmigaOS 3.2
You need to get a 3.2 rom for the CD32 as using the 3.1 rom will give you problems
Re: CD32, TF360 and AmigaOS 3.2
Yes, I already have a physical 3.2 ROM in this machinesupaduper wrote: Sat Apr 06, 2024 12:57 pm You need to get a 3.2 rom for the CD32 as using the 3.1 rom will give you problems
I now started with the trace option from the early startup menu
It seems like it is missing files (??) that in my opinion should be there? Put there by the AmigaOS installer
Re: CD32, TF360 and AmigaOS 3.2
And it is definitely a 3.2 rom made for the CD32 ?
Anyway I will email you
Anyway I will email you
Re: CD32, TF360 and AmigaOS 3.2
Yessupaduper wrote: Sat Apr 06, 2024 2:13 pm And it is definitely a 3.2 rom made for the CD32 ?
Anyway I will email you
Re: CD32, TF360 and AmigaOS 3.2
Problem solved to a very helpful soul and hero here
-
terriblefire
- Admin sponsor

- Posts: 5687
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: CD32, TF360 and AmigaOS 3.2
what was the issue? so others know
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: CD32, TF360 and AmigaOS 3.2
Not 100% sure but it seems like some files where never copied to L and Libs by the AmigaOS 3.2.2 patch installer which are needed by LoadModule in the startup-sequence.
I prepped my CF card in WinAUE.
Re: CD32, TF360 and AmigaOS 3.2
Yes just an OS 3.2 system install problem, so long as you correctly update the OS 3.2 with the hotfixes available you should have no problem, as we confirmed via email
