exxos's Atari, Amiga & retro forum

Hi Amigos,

Please can someone shed some light on my TF1260 setup, ;)

I have an A1200 with the TF1260 LC chip, 128mb Fast Ram. Im running 3.2.1 OS but since I upgraded my roms to
the custom ones from retro passion as to boot from Ehided.device, the boot time is very slow, its almost 15 seconds until i see the startup sequence flash and workbench appear.

Im using one of those right angled 44 pin IDE to SD adapters. Ive also tried my old CF card adapter and Msata drive options, all of which are reliable and work via onboard ide header or TF header, There is no ribbon cable. Im fairly sure this started once I had added the custom roms, as even when i plug the SD drive into onboard header it still takes a long time to boot. Its difficult to know exactly whats happening as of course there is no hdd activity led with the TF without further modification.

I have the latest drivers installed, TF tools and the TF drive speed is double that of the internal at around 4mbps Is it something ive done wrong or perhaps its just how it is? :roll:

Any advice much appreciated.. Thanks, Jamie :-)

To save giving a long answer, this is normal behaviour for the TF ehide boot time

@supaduper Thanks mate, I know its not the end of the world but I did wonder if something may be a miss. I can put up with it :-)

Can't it be the system waiting for the onboard IDE to answer?

I believe an IDE terminator like this may solve the issue.

I bought a terminator and it did not improve the situation.

Kick 3.1.4 and Kick 3.2 just take a lot longer to boot.
You can see it in WinUAE.

Does anyone actually know WHY there is this delay before a CF card using ehide gets around to booting?

It seems like a small thing but it really annoys me and I just want to know for sure that we can’t do anything to fix this.

I'm sure the OS waits 5 seconds for internal drives to respond. if you don't have an ide terminator on there you get the delay?

EDIT: KS 3.0 had a 30 second delay, 3.2 is stupid and brought it back.

EDIT2: The reason WHY is because the spec says drives have X seconds to wake up, spin up and respond. In practice even PCs don't wait that long. it's a stupid anally retentive thing OS3.2 devs put back in to make our lives miserable

terriblefire wrote: 12 Sep 2025 07:34 I'm sure the OS waits 5 seconds for internal drives to respond. if you don't have an ide terminator on there you get the delay?

EDIT: KS 3.0 had a 30 second delay, 3.2 is stupid and brought it back.

EDIT2: The reason WHY is because the spec says drives have X seconds to wake up, spin up and respond. In practice even PCs don't wait that long. it's a stupid anally retentive thing OS3.2 devs put back in to make our lives miserable

I get the delay whether I have a terminator on the internal IDE or not. Thanks for the info, TF. Mostly I’m just glad to know the delay is “normal” when not running on internal IDE and not some issue I need to track down.

I might actually time with and without to ensure it’s actually the same duration rather guessing.