Mmm.. I think it might be overly complex (and therefore error-prone) to try and remap accesses to a second drive -- we're talking raw disk access here, and the player has only open()ed one partition for I/O. I don't think I want to try and trick it over to another disk.

But your point about partition overspill is a good one. That's free space that has zero risk associated with it.

Paul: show us your /proc/partitions data from one of your players, please
(you can grab it with either ftp or web access to your player).

Peter, how do you think the player s/w might respond to an error accessing the dynamic data? Will it just ignore it on writes, and use default (zeros?) data on reads, or will it get really peeved?

If it just takes it all in stride, then a simple binary player patch to 0xffff will work for everybody, rather than having to actually calculate the sectors available and using that value for a patch. Mind you, writing a quick app (in hijack even) to do the latter is not a really big deal for at least 20 people on this BBS.

Cheers