MUSH on USB drives

I use MUSHclient on a USB drive, and it works pretty well (barring having to make some iffy workarounds and changes to make it work across all computers), but I'm worried about clobbering the drive with writes that will deteriorate the drive more quickly. Is there any sort of buffering done, say, for logs, so that it's not constantly writing every time something is received?

I think MUSH on a stick is a great way to take MUDding with you wherever you go, but if it clobbers it with unneeded writes, it takes away a bit from its longevity. Oh, how I wish we had Fe-NAND thumb drives.

(As an aside, will the link to the MUSH download on the front Downloads page ever be updated? It's been left at 4.27 for ages)

The log files are flushed to disk every two minutes, to stop them being lost in the event of a crash, however apart from that, they are buffered in the normal way. This means every single line should not cause a write to the USB, however something will be written at least every 2 minutes.

If you are worried about USB degradation, you could write the log files to somewhere on the hard disk (eg. C:\Windows\Temp) and then when the session is over, do a single copy to copy the completed log back to the USB, and delete it from the hard disk. Of course, to save overwriting existing logs, you would need something like the date/time in the log file name, but this is easy to set up.

The version will be updated soonish, probably after version 4.38 is released.

Hi, I had a few other questions about making MUSHclient portable as well.

1) I'm currently carrying it around on my flash drive (works great, btw!) and I'm curious as to where the global prefs are saved. Even though I carry all my world info with me, each time I move to a different computer I have to set up global prefs all over again. I'd like to know where I can just stick the global prefs file onto my flash drive an hopefully MUSHclient can refer to it.

2) Since it's on a flash drive, I have a different drive letter every time. The only time it's been an issue so far is when I have sound triggers set to go off. Is there a way to point the triggers to the soundfile to get around this?

And a few questions that don't necessarily relate to portability:

3) How can I get MUSHclient to write to a new log file every time I start a session/open the world? And also append the filenames with numbers?

4) If I label triggers with a group, how can I disable the group?

Thanks a lot! I just started using MUSHclient and I'm very pleased with it :-) It's the most powerful client I've had so far.

-- Ophianne

Global prefs are in the registry, and yes, I know this isn't the greatest solution. :)

There have been some posts in the past about USB drives, and people use a simple script (I think) to save the relevant part of the registry and load it up when moving PCs.

As for the sound files, I'm not sure of the best solution - one way would be to use relative paths (so the sound file is relative to the world file location, for example).

Another would be to script the sounds playing - so the script finds where the executable is, and then get a subdirectory (eg. sounds) from there.

The log files - use the automatic log file feature and append the date/time, that way each log file will have a different name.

For the triggers, see:

http://www.gammon.com.au/scripts/doc.php?function=EnableTriggerGroup