After some trouble i found out that Boot 1.04 and 2.01 (downloaded from github) need TOS4.04 in ROM.I had EmuTOS in there which works great with boot 1.03c. 1.03c contains full TOS4, but 1.04 and 2.01 seemto copy at least som parts from ROM at boot time.With EmuTOS in the TOS-ROM socket, the standard font is a garbled pixel mess.

Additionally, CTPCI needs to be the first board on the CT-expansion bus. With the IRQ cable connected,i can now run the SuperVidel and EtherNat on top of CTPCI and boot off the CTPCI's IDE port.

The boot up text screen, where firmware versions and PCI bios messages are shown are not readable onSV output until SVXBIOS.PRG is run from auto folder. Usually, its only the Atari logo in the top left cornerthats messed up.

Conclusion for today: CTPCI, SV and EN can be active in one system. Greets,Beetle

Not sure what's with his configuration. On my system the CTPCI IDE are at least 2x read speed of the falc IDE. Faster MINT boot up

These were done back in 2012 using Kronos:Running on using MINT Falcon IDE: DISK_READ=6.190; (Mo/sec)DISK_WRITE=5.893; (Mo/sec)DISK_MULTIREAD=38.669; (Mo/sec)DISK_MULTIWRITE=36.499; (Mo/sec)DISK_CREATE_DELETE=159.0; (op/sec)DISK_READ_WRITE_CACHE=37.616; (Mo/sec)

How did you get 6 MB/sec with the stock Falcon internal IDE?If I remember well, Falcon IDE port spec is 2.5 MB/sec, and with a fast ide DOM I get 2.3 MB/sec. You may be measuring the cache speed I guess.

May be yes, may be not, it could also depends on where the cache is stored and the way it is managed. If it's STRam for Falcon IDE and TTram for CTPCI, you may be reading just the memory speed boost. Anyway, CTPCI IDE has been reported to be 2x faster by other sources. I was just puzzled by these very high values.

Let me answer myself my bullshit comment. It has nothing to do with different cache speed (oops)Multi read and multi write, which very likely use 100% cache only, are the same in both case. So the cache speed is the same in both case. Regarding the conclusion we can only conclude that CTPCI IDE is faster, but not how much. Depending on the size of the cache and the size of the file used for testing, it can be less or more than 2x.

There are more ways to test this. As soon as the file is big enough, cache speed doesn't matter. For example, start Kobold and read a 10MB file into memory, and measure the needed time with a stop watch. It will not be very precise, but should show the actual speed gain good enough. For small files, reading the FAT, head movement in case of hard disks and other factors come into play.

As Mint is configured and rest of hard ware is the same, cache by Mint should be the same area of memory ( TTram or STram).HDD internal cache also the same, but may depend on where it's write/read but that's Kronos job.So the speed up should be only due to the CTPCI speed increase.

if other ppl are not getting the speed up on the CF, my guess is that the bottle neck is the CF itself.Important that the CF or HDD can go much much faster than the bus, so that you can see the speed up.