Could the fact it's bigger have anything...

It shouldn't do. The reason it's bigger is that, according to this line:

Units = cylinders of 16065 * 512 bytes

You've got a little less than 8Mb available in a single cylinder. Since a cylinder is the smallest unit involved in partitioning, to get the 16Mb required, it's been rounded up to the next higher cylinder (thus taking a little less than 24Mb).

The other drive's geometry translation has resulted in smaller cylinders, but more of them:

Units = cylinders of 1008 * 512 bytes

Thus, the granularity is better (504Kb/cylinder), so that 16Mb minimum requires 33 cylinders, but only 16,632Kb, a little more than 16Mb, but not much.

The technical reasons for the disparity aside, the larger dynamic data partition shouldn't make any difference to the behaviour of the player. OTOH, my dynamic data partition is 16569Kb in size.

Oh, and you can use "fdisk -l" (that's a lower-case L) to list the partitions, like this:

# fdisk -l /dev/hda