Of course, there were more barriers to come, so there was an opportunity to reintroduce further versions of the feature, but they missed it. (Of course, now with SATA it has little relevance, though a functionally similar feature could theoretically be provided on a SATA drive by emulating a "port multiplier", but that requires host support, which not all SATA ports have.)
Conceptually:
- 4,096 cylinder limit - split a 4.2GB drive into 2×2.1GB
- 6,322 cylinder limit - split a 6.5GB drive into 2×3.2GB
- Int13h address limit - split a 17GB drive into 2×8.4GB
- 65,536 cylinder limit - split a 60GB drive into 2×30GB
- 28-bit LBA limit - split a 250GB drive into 2×125GB
Device 0 ("master") - jumper 7-8
Device 1 ("slave") - no jumpers (or 5-7 which does nothing as both of those are ground)
Cable select - jumper 5-6
Force slave present - jumper 7-8 and 5-6
Limit capacity - jumper 1-2
Pins 3 and 4 are not for configuration, but are a serial terminal interface which is only to be accessed for data recovery. There are no other possibilities using the remaining pins, although, could they have programmed the controller to switch into split mode upon receiving the same signal it transmitted?