i'm running ashell version 5.0.1000.4. I have a question about creating 'buffer' files with the `submit` command. when i run the command: `SUBMIT CMD:ORGALT.CTL LL /BC ORGALT` the submit command seems to generate (2) buffer files. The first one "orgalt.buf" is 4k in size and has some screen shoots in it. the 2nd file "orgalt.BUF" ((notice the difference is CASE at the end)) is 2k in size and contains info from the command line execution. My question is: WHY is there (2) different buf/BUF files created? also, when i am in ashell and i issue the command: `vue orgalt.buf` which file is opened? Is this a bug or a feature?

As much as I'd like to suggest that it is a feature, I'm not sure how useful it would be. (Unless it was just to keep the command line execution screen shots out of the main buf file.)

Most likely the buf and BUF case discrepancy (good eye in spotting that!) was inadvertent.

When you use ".vue orgalt.buf" from the command prompt, you will always get the lower case version, because A-Shell always folds AMOS-compatible filespecs to lower case before trying to create or access the file in the native filesystem.

However, you can also vue the other version from the command prompt just by including "./" at the start:

.vue "./orgalt.BUF"

(The quotes are actually optional in this case, but in general, when using native filespecs with LIT commands, they should be quoted.)

So, if you're willing to go along with the "feature" theory, then I guess our work is done here. Otherwise, I'll need to track down the source of the problem, and most likely create a patch. (Interestingly, I don't seem to be able to reproduce this in 5.1, so perhaps it was fixed inadvertently as well?)

A possible workaround would be for you to specify the file extension in the SUBMIT command line. I suspect if you just specified ... /BC ORGALT.BUF (or perhaps /BC orgalt.buf) the problem would take care of itself.

specifying '/BC ORGALT.BUF' does result in one file being created (in small case) 'orgalt.buf'. Thanks again Jack.