CompuServe Messages

Allen, The command line looks simple enough (and correct). The only thought I have is that things may be getting screwed up because the name of Ram: is "Ram Disk:", and some programs have difficulties in processing command-lines where filenames contain spaces. What I've done to get around this problem is zap the file "ramdrive.device" in the devs: directory, changing the string "Ram Disk" to "Ram_Disk". Note that this is a kludge, but it has made a difference for a number of programs. If what you're trying to do works when you're working on a "real" disk, but not on Ram:, then this is probably the problem, and my kludge would help. However, remember to do the zapping on a BACKUP of the file. (Cover thy backside <grin>). Hope this helps… …BobR White Wolf Productions