TF1260 New Firmware Alpha Released!

[supaduper]

FYI , the Screen resolution say like hi-res and the number of colours you have selected can influence the mips so reduce those and you will see different speeds :)
remember more system resources used like colours used and screeen depth will always affect these mip figures

[PainDictator]

FYI , the Screen resolution say like hi-res and the number of colours you have selected can influence the mips so reduce those and you will see different speeds :)
remember more system resources used like colours used and screeen depth will always affect these mip figures

I know, that is why all Tests where done using a single bitplane pal highres noninterlaced screen. AFAIR highres with Up to two Planes will Not use additional Chip RAM cycles.

[AmigaDweeb]

Hmmm interesting stuff, as this thread appears directly related to my own thread and question here today viewtopic.php?f=101&t=6273

[arek0xff]

thanks for great card!

I'm wondering if it would be possible to add a software switch "compatibility mode" which would disable 060 CPU and leave only FAST ram? That would be great option as 060 is still problematic for older games.

thanks

[terriblefire]

thanks for great card!

I'm wondering if it would be possible to add a software switch "compatibility mode" which would disable 060 CPU and leave only FAST ram? That would be great option as 060 is still problematic for older games.

thanks

Unfortunately the 020 can only address 8Mb of fast ram and its not capable of talking to the SDRAM

[CrazyC]

Just wondering if there was any news re a new version of the ehide driver, as TF mentioned this earlier in the thread as a possibility.
I have held off upgrading from 3.2 to 3.2.2.1 but am going to do it shortly alongside flashing my tf1260 firmware and will order new physical roms at that point, and was wondering whether or not to hold off a bit longer so as to include a newer ehide.
Cheers

[terriblefire]

Just wondering if there was any news re a new version of the ehide driver, as TF mentioned this earlier in the thread as a possibility.
I have held off upgrading from 3.2 to 3.2.2.1 but am going to do it shortly alongside flashing my tf1260 firmware and will order new physical roms at that point, and was wondering whether or not to hold off a bit longer so as to include a newer ehide.
Cheers

I have ehide 1.2 but its entirely up to @erique when he releases it.

[CrazyC]

Ooh, any particular changes or just a gradual improvent or bug fix type version change?

[terriblefire]

Ooh, any particular changes or just a gradual improvent or bug fix type version change?

Its a lot of minor fixes really.

[erique]

I have ehide 1.2 but its entirely up to @erique when he releases it.

Old man moves slowly.. :coffee:

ehide_1.2_9c4ac27.tar.gz

Code: Select all

ehide 1.2 (04.7.2023) TF IDE Driver (9c4ac27)

[BUGFIX] Formatting a partition (using TD_FORMAT) could hang the device driver.
[BUGFIX] When using removable media in combination with TD_ADDCHANGEINT, a notification callback could sometimes be missed.
[BUGFIX] The expansion.library/ConfigDev was not properly initialized, causing HDToolBox to reload the driver multiple times in certain scenarios.
[BUGFIX] The error reporting (SCSI Key Code Qualifier), in case of an IDE/ATA command failure, was mostly incorrect.

[CHANGE] Executing 'ehide.device' from CLI is now handled gracefully; return code = -1.
[CHANGE] Media reporting a zero cylinder size is now considered bad/faulty, and ignored.
[CHANGE] The PIO read-loop now stores data in 16 bytes chunks (using movem.l), making the read-loop tighter.
[CHANGE] The device driver ROMTAG wasn't pointing to the end of the code segment, causing unnecessary work during ROMTAG scanning.
[CHANGE] About 15% smaller code size (~2k less)

It could also be that I managed to add some new fresh bugs; I'm sure you'll tell me if that's the case ;)