exxos's Atari, Amiga & retro forum

With ehide disabled 3.1 will not boot with 1200 and TF IDE hooked up...same black screen

Diagrom does boot with both hooked up but reports 256Mb ram

sparx wrote: 05 Jan 2022 11:00 With ehide disabled 3.1 will not boot with 1200 and TF IDE hooked up...same black screen

Diagrom does boot with both hooked up but reports 256Mb ram

Diagrom should report 256Mb of ram. Thats correct behaviour for current diagrom.

terriblefire wrote: 05 Jan 2022 11:01

sparx wrote: 05 Jan 2022 11:00 With ehide disabled 3.1 will not boot with 1200 and TF IDE hooked up...same black screen

Diagrom does boot with both hooked up but reports 256Mb ram

Diagrom should report 256Mb of ram. Thats correct behaviour for current diagrom.

run

VERSION FULL DEVS:ehide.device

(or wherever you have the ehide.device installed).

terriblefire wrote: 05 Jan 2022 11:08

terriblefire wrote: 05 Jan 2022 11:01

Diagrom should report 256Mb of ram. Thats correct behaviour for current diagrom.

run

VERSION FULL DEVS:ehide.device

(or wherever you have the ehide.device installed).

ehide.device 1.1 (24/07/57)
Built on 18th June 2021 / 15:59:03 (d2874a8)

sparx wrote: 05 Jan 2022 11:16

terriblefire wrote: 05 Jan 2022 11:08

run

VERSION FULL DEVS:ehide.device

(or wherever you have the ehide.device installed).

ehide.device 1.1 (24/07/57)
Built on 18th June 2021 / 15:59:03 (d2874a8)

Ok it probably wont fix the issue but try this fw

https://www.exxosforum.co.uk/forum/viewt ... =10#p73251

terriblefire wrote: 05 Jan 2022 11:25

sparx wrote: 05 Jan 2022 11:16

ehide.device 1.1 (24/07/57)
Built on 18th June 2021 / 15:59:03 (d2874a8)

Ok it probably wont fix the issue but try this fw

https://www.exxosforum.co.uk/forum/viewt ... =10#p73251

Thank you...I have already, but will give it another go :)

sparx wrote: 05 Jan 2022 11:27

terriblefire wrote: 05 Jan 2022 11:25

Ok it probably wont fix the issue but try this fw

https://www.exxosforum.co.uk/forum/viewt ... =10#p73251

Thank you...I have already, but will give it another go :)

Do you have some daft sector size on your disks? This can cause issues with ehide as discussed elsewhere. The only thing i can suggest is a test firmware that makes the TF ide become the default to rule out the driver.

terriblefire wrote: 05 Jan 2022 11:32

sparx wrote: 05 Jan 2022 11:27

Thank you...I have already, but will give it another go :)

Do you have some daft sector size on your disks? This can cause issues with ehide as discussed elsewhere. The only thing i can suggest is a test firmware that makes the TF ide become the default to rule out the driver.

I 'seem' to be making progress...
The original card that I upgraded to 128Mb suddenly decided it would boot from 3.0 rom with both IDE hooked up and addmem enabled...I could see both drives and had full 128Mb.
The only thing I did was disable and re-enable ehide in startup-sequence, using same cf/sd cards and adptors etc :o

The problematic TF board also decided to boot once I'd shortened the IDE ribbon on the TF IDE to 3cm! (It was only 10cm before trimming and worked on the other board)Totally impractical, but major progress...I also flashed that board with the alpha firmware you linked, it boots, both drives there and reports full 128Mb!

Just about to try both boards on 3.1 roms...

EDIT: Problematic board now booted on 3.1!! Just need to work out max length of IDE ribbon
@terriblefire Thank you so much for the time and patience!
I have no clue what made one board spring back to life (apart from the ehide thing) but the other was a combo of fw/cable length

If your IDE cables are longer than a couple of inches forget it. It wont work. You need a buffer. Go0se designed one based on the TF536.

terriblefire wrote: 05 Jan 2022 12:26 If your IDE cables are longer than a couple of inches forget it. It wont work. You need a buffer. Go0se designed one based on the TF536.

I never thought to check cable length, I knew it could be an issue but as my 2x 1260 and my other 1230 was ok with 10 to 15cm I never even thought to look in to it!

But, still very weird how the other one just sprang back to life by simply disabling/reenabling ehide
Ehide worked just fine when that card had 64Mb and it still has a 15cm ribbon