@Joseph_Joestar,
@douglar:
Thanks for your useful information regarding industrial and consumer grade CF cards.
--
As promised here are pics of my CF as well as SSD solution.
First I had the CF solution with StarTech 3.5" IDE to CF adapter (35BAYCF2IDE), #3 in initial post mounted into a mobile rack.
For mentioned reasons I switched to SSD using StarTech IDE to SATA adapter (IDE2SAT2) in Orico 2.5" to 3.5" caddy mounted into the mobile rack as well.
I think the SSD solution looks much nicer.
I will stay with the SSD method.
Using a 128GB SSD under MS-DOS 7.10 gives me no problems on an Asus P5A board with ALi Alladdin V chipset.
BIOS detects the full 128GB, as well as all diagnostics tools and scandisk is working correctly.
As with all modern HDDs/SSDs effective capacity is less. In this case about 120GB.
The only downside is that R. Loew's TRIM.EXE is not working for reasons I did not found out yet.
The SSD model, a Samsung 850 Pro supports Trim by firmware. So that should not be the problem.
For a Samsung 870 EVO 256GB (max LBA limited to 128GB) in my Win98 machine TRIM.EXE works correctly.
So I experimented with a Samsung 850 Pro 256GB drive (also max LBA limited to 128GB) in that DOS machine.
TRIM.EXE doesn't work either.
Maybe it's the difference in SSD model (850 Pro vs. 870 EVO).
Good thing would have been that I would have been able to use the full effective capacity of 128GB instead of "only" 120GB.
But I had some negative effects with that drive:
- BIOS reports 80GB capacity (found out that this is the CHS capacity)
- some diagnostics tools also report that 80GB (assume they show the CHS value) whereas others report the 128GB (LBA capacity)
- scandisk is not working and reports sector problems with the drive
- as mentioned TRIM.EXE is not working
So I didn't follow this route any further and am now using 128GB SSD without Trim possibility so far.
I'm making regular Ghost image backups. So if the SSD fails I just put in another SSD (cheap to have) and restore my backup on it.