Hi Nick,
Sorry, I wasn't at all clear. That's what I was doing :P
The trick was that I had customised the path already. I was showing someone else how to change the RAM limit by telling them what to type over their shoulder (more of a mouse user than a keyboard user too). It just wasn't a great first exposure to Seq ("trust me, just uninstall/reinstall this service and specify the RAM setting whilst also getting that path right. The data should all be there when it comes back, I promise").
Very, very, very minor thing in the scheme of things :)
However, the hard RAM limit in MB rather than % would be handy to support in those cases where we have Seq sharing a VM that's got dynamic RAM enabled. Is that something that might be considered for a distant future release?