First post, by darry
On both an ICH2 ATA66 and an Ultra133 TX2, running through an IDE to SATA adapter (JMD330) , on a 500GB drive with 3 120GB primary partitions created with FreeDOS' fdisk , running TRIM.EXE -N C: F under DOS 7.1 corrupts the second and only the second partition . When running with an extended partition instead of the second and third primary partitions, that ended up being corrupted too. This occurs without going into Windows, so it is not a Windows issue . The SIL3114 native SATA I also have does not pass TRIM commands, so I cannot test TRIM.EXE (other than to have it complain of not being able to do its thing) with it .
When not using TRIM.EXE I have no issue reading and writing to all partitions under both DOS 7.1 and Windows 98 SE (BHDD31 patch is installed otherwise the ICH2, which uses ESDI506.PDR, would have issues above 127 GB) with all of these controllers .
Could this be a bug/limitation in TRIM.EXE or could this issue be due to my setup running through an IDE to SATA adapter ? I wish I had a Promise SATA 150 TX2 Plus, but at 140 Canadian dollars with shipping, I think I will pass ?
I will try a Linux BOOT CD and see if I can TRIM successfully with that .