You will not be able to post if you are still using Microsoft email addresses such as Hotmail etc
See here for more information viewtopic.php?f=20&t=7296
See here for more information viewtopic.php?f=20&t=7296
BOOKMARK THIS PAGE !
https://www.exxosforum.co.uk:8085/IP_CHECK/
You can unban yourself if needed. It also sends me reports to investigate the ban.
https://www.exxosforum.co.uk:8085/IP_CHECK/
You can unban yourself if needed. It also sends me reports to investigate the ban.
DO NOT USE MOBILE / CGNAT DEVICES WHERE THE IP CHANGES CONSTANTLY!
At this time, it is unfortunately not possible to whitelist users when your IP changes constantly.
You may inadvertently get banned because a previous attack may have used the IP you are now on.
So I suggest people only use fixed IP address devices until I can think of a solution for this problem!
At this time, it is unfortunately not possible to whitelist users when your IP changes constantly.
You may inadvertently get banned because a previous attack may have used the IP you are now on.
So I suggest people only use fixed IP address devices until I can think of a solution for this problem!
AmigaOS 3.2.3 + ehide.device 1.2
Moderators: terriblefire, Terriblefire Moderator
-
masterofdisaster
- Posts: 7
- Joined: 10 Oct 2022 23:53
AmigaOS 3.2.3 + ehide.device 1.2
Hello!
I have been using Capitoline to integrate the ehide.device v1.2 into the ROM for a while now and it worked flawlessly up until Kickstart 3.2.2.1. Possibly Capitoline is doing something wrong at this point, it has been updated for the 3.2.3 only few days ago without a proper RAT Test Profile yet so I did the manual merger.
Amiga boots fine from the integrated IDE but the ehide.device is not present and it won't boot from the tf1260.
I have been using Capitoline to integrate the ehide.device v1.2 into the ROM for a while now and it worked flawlessly up until Kickstart 3.2.2.1. Possibly Capitoline is doing something wrong at this point, it has been updated for the 3.2.3 only few days ago without a proper RAT Test Profile yet so I did the manual merger.
Amiga boots fine from the integrated IDE but the ehide.device is not present and it won't boot from the tf1260.
-
supaduper
- Site sponsor

- Posts: 663
- Joined: 08 Nov 2018 12:05
Re: AmigaOS 3.2.3 + ehide.device 1.2
I updated my rom to 3,2,3 with ehide using capitoline and it works no problem, I just rehashed the commands in the CLI and it spat out the A1200 rom all you have to do then is split( wordwise) then double the files to 512k for 27c400 eproms or double again to 1mb for 27c800 eproms so they fit on the eprom and don`t forget to byteswap the two files before programming them
if you want to do it yourselves then put the new 3.2.3 47.115 rom in the Folder in the Roms/Hyperion folder in Capitoline and make new folder called terriblefire in the `Components `folder and put the ehide in there, then copy and paste the script below and it should spit an A1200 rom into the root of the captioline folder , then just do the stuff to the files mentioned above
loadrom "ROMs/Hyperion/A1200.47.115.rom"
add "Components/TerribleFire/ehide.device"
checksum
saverom Kickstart.3.2.3.withehide
if you want to do it yourselves then put the new 3.2.3 47.115 rom in the Folder in the Roms/Hyperion folder in Capitoline and make new folder called terriblefire in the `Components `folder and put the ehide in there, then copy and paste the script below and it should spit an A1200 rom into the root of the captioline folder , then just do the stuff to the files mentioned above
loadrom "ROMs/Hyperion/A1200.47.115.rom"
add "Components/TerribleFire/ehide.device"
checksum
saverom Kickstart.3.2.3.withehide
-
masterofdisaster
- Posts: 7
- Joined: 10 Oct 2022 23:53
Re: AmigaOS 3.2.3 + ehide.device 1.2
hmm, that's almost exactly what i did except instead of saverom I did:
romprofile dual 0 0
saveprofile 512 byteswap Kickstart.3.2.3.withehide
and still no bueno
what are crc32 checksums of your roms?
mines are:
0xa7c3f923 for Kickstart.3.2.3.withehide.hi.bin
0xa61a86b9 for Kickstart.3.2.3.withehide.lo.bin
romprofile dual 0 0
saveprofile 512 byteswap Kickstart.3.2.3.withehide
and still no bueno
what are crc32 checksums of your roms?
mines are:
0xa7c3f923 for Kickstart.3.2.3.withehide.hi.bin
0xa61a86b9 for Kickstart.3.2.3.withehide.lo.bin
-
supaduper
- Site sponsor

- Posts: 663
- Joined: 08 Nov 2018 12:05
Re: AmigaOS 3.2.3 + ehide.device 1.2
You are using the latest version of Capitoline ?
Also you have 3.2.1 there I am doing 3.2.3
Also you have 3.2.1 there I am doing 3.2.3
-
masterofdisaster
- Posts: 7
- Joined: 10 Oct 2022 23:53
Re: AmigaOS 3.2.3 + ehide.device 1.2
yes, downloaded yesterday
3.2.1 was a typo
3.2.1 was a typo
-
supaduper
- Site sponsor

- Posts: 663
- Joined: 08 Nov 2018 12:05
Re: AmigaOS 3.2.3 + ehide.device 1.2
Yeah don`t bother with it doing the magic with roms with savefile, do as I did and manipulate them yourself
Your checksums match so something wrong somewhere
Checksum 8abe75c0
HI a7c3f923
LO a61a86b9
Your checksums match so something wrong somewhere
Checksum 8abe75c0
HI a7c3f923
LO a61a86b9
-
masterofdisaster
- Posts: 7
- Joined: 10 Oct 2022 23:53
Re: AmigaOS 3.2.3 + ehide.device 1.2
What firmware is your TF1260 flashed with? I'm on the latest 68090
-
supaduper
- Site sponsor

- Posts: 663
- Joined: 08 Nov 2018 12:05
Re: AmigaOS 3.2.3 + ehide.device 1.2
I am using a TF1230 with the roms, I will try the TF1260 to see if it works
Edit, just tested with TF1260 on 68090 firmware and no problems here, working fine.
.try cleaning the expansion port on your A1200
Edit, just tested with TF1260 on 68090 firmware and no problems here, working fine.
.try cleaning the expansion port on your A1200
-
masterofdisaster
- Posts: 7
- Joined: 10 Oct 2022 23:53
Re: AmigaOS 3.2.3 + ehide.device 1.2
Found the culprit. RTC clock module, when unplugged, everything works fine.
-
supaduper
- Site sponsor

- Posts: 663
- Joined: 08 Nov 2018 12:05
Re: AmigaOS 3.2.3 + ehide.device 1.2
Had me worried so I checked mine by putting a RTC on the A1200 and it still works ok, glad you sorted yours thoughmasterofdisaster wrote: 07 Apr 2025 15:50 Found the culprit. RTC clock module, when unplugged, everything works fine.
Who is online
Users browsing this forum: CCBot and 9 guests