On Sat, Nov 29, 2008 at 01:14:33PM +0000, James Woodcock wrote: > Sounds like a good starting point. I'll probably add a third option to > specify read-only or read-write. I may split it up into 3 lines (for > readability, and for Windows/MacOS which is more likely to have spaces > in the path): > hostfsname0 = Boot > hostfspath0 = ~/hostfs > hostfsperm0 = read,write
Good idea. I don't know if you want to tweak the naming slightly so it's more readable? How about: hostfs.drive0.name = Boot hostfs.drive0.path = ~/hostfs Or: [hostfs.drive0] name = Boot path = ~/hostfs (Allegro supports sections in config files like this) > hostfsperm(n) would default to read-only, I think. I see potential for confusion here. If you do that, this should perhaps be made obvious to the user in some way. You could give a message on startup: "HostFS drive <name> mounted read-only at <path>: to change, add 'hostfs.drive3.path = rw' to rpc.cfg" (but are users going to read that, if rpcemu's started from a menu?) Or make sure some very obvious comments are output into rpc.cfg? (I've forgotten if rpcemu actually saves that file at any point - if it does the comments would need to be rewritten) Theo _______________________________________________ Rpcemu mailing list [email protected] http://www.riscos.info/cgi-bin/mailman/listinfo/rpcemu
