Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 136  |
|  Russell Tiedt to Bob Jones  |
|  Fido on a removable drive  |
|  24 Aug 06 17:02:32  |
 Hello Bob. 23 Aug 06 11:17, you wrote to me: RT>> Any suggestions on how to make Squish, msged, RT>> binkleyterm, binkd, etc operate RT>> in such a fashion that it matters not what the drive RT>> name is, the paths are RT>> sane and make sense to the programs. BJ> Most of the squish, binkleyterm, and I think even binkd control files BJ> can be set up with relative paths specified. There may be one or two BJ> spots where it may need a drive letter defined in a windows or OS/2 BJ> type environment. Hmmm ... , so it should be do-able ... RT>> Things I have considered are; RT>> Setting the drive in a batch file i.e. RT>> Set drive "equals" F RT>> and then writing paths as follows RT>> $drive\squish\msgbase RT>> or ..\squish\msgbase BJ> Games like this work in batch files, but not necessarily in the BJ> control files. Okay, batch files are fine, like this, if the control files will work with relative paths, then that would work ... RT>> otherwise writing seperate config files for each program, i.e. RT>> squish.cfg.f RT>> squish.cfg.h BJ> Use relative paths for most of the stuff in the control files, share BJ> the common control information in one file, and then in use an include BJ> statement in the drive specific control file which should have very BJ> few lines..... That is if you can not get by with using all paths in BJ> the control files without drive letters and have the batch file set BJ> the default drive to the memory stick before processing.... Okay ... sounds like it should be do-able RT>> and then run a batch file that will copy one or the other to RT>> squish.cfg depending on what drive letter is allocated to the USB RT>> drive? RT>> Am I making sense? BJ> In some ways. Good, so I am not yet toally insane. |
[ << oldest | < older | list | newer > | newest >> ]