[Info-vax] How to tell SET COMMAND where the .EXE file is?

alanfe...@gmail.com alanfeldman48 at gmail.com
Tue Sep 27 00:21:08 EDT 2022


On Monday, September 26, 2022 at 11:14:12 PM UTC-4, Steven Schweda wrote:
> > I did your procedure, [...] 
> 
> I see no evidence of that.
> > $ DIRSORT :== $SCRFELD:[DIRS1A.DIRSORT.BIN.ALPHA]DIRSORT.EXE
> Are you running the pre-built executable from eighteen years ago, or 
> the one which you built today?
> > So what's wrong now?
> I don't know. Just as I don't know what you found where. Are you 
> too lazy to write a proper problem description, or do you not know how, 
> or what? 

Alright. I should have been a little more complete. Last time I did that it was a problem with a printer, and I posted everything imaginable from the VAX (circa 1992), and no one had a clue. Turned out it was an unrelated problem. I don't want to go through the trouble of posting unrelated stuff. Yeah, still, I should have posted a little more. Sorry. No need to be so rude though!
> 
> 
> > %SYSTEM-F-ACCVIO, access violation, [...] 
> 
> If I got that, then I might start by removing the "/notraceback" from 
> "descrip.mms", perhaps adding a "/list", building the thing from source 
> (as shown in "[my] procedure"), and trying my freshly built executable 
> (not some antique). 
> 
> 
> It might be worth noting that you're working with an old, 
> ODS5-unaware program. For example: 
> 
> ITS $ dire ITS$DKA0:[SMS.IZ.vlfn] 
> 
> Directory ITS$DKA0:[SMS.IZ.vlfn] 
> 
> 
> very_long_file_name_very_long_file_name_very_long_file_name_very_long_file_name_ 
> very_long_file_name_very_long_file_name_very_long_file_name_very_long_file_name_ 
> very_long_file_name_very_long_file_name_very_long_file_name.txt;1 
> 
> Total of 1 file. 
> ITS $ dirsort ITS$DKA0:[SMS.IZ.vlfn] 
> 
> Directory ITS$DKA0:[SMS.IZ.VLFN] 
> 
> %SYSTEM-W-BADFILENAME, bad file name syntax 
> ITS $

Nope. Not an ODS-5 problem. I don't even have access to an ODS-5 disk except through the logical name GNV$GNU. 

First of all, calm down, man. \relax. Take your shoes off. NO! You can leave 'em on. But you can sit a spell.

First time I tried various things with the kit from the VSI site. No luck. Even the build.com didn't work! Then I tried what you recommended and got the kit from the SCREEEEEEEEECH.

OK, I used the old executable. Sorry. I guess I assumed BUILD.COM would do that, since it did practically everything else. Silly me.

Hey, if you've got some serious woes (that's the polite version), please check them at the door before you come here. If I knew what I was doing, I wouldn't be asking for help in the first place! Or couldn't you figure that out? I am not, and never was, a "system programmer." 

I'm just a lowly ex-physicist trying to do some fun things on OpenVMS. There are a lot of very smart people here :-|  who try to help me (well, there was the Fahrenheit adventure!) and usually don't get so upset. (Well, there was Carl Lydick. A smart dude, but not very friendly!)

Anyway, the thing works! It even accepts ;*, which was critical to my needs! Doesn't seem to like a list of params, though. I can work around that.

$ dirsort to%.com;*,to-v*.com
%CLI-W-NOLIST, list of parameter values not allowed - check use of comma (,)
 \TO%.COM;*,TO\
$ 

Or maybe something with SET COMMAND would fix that? I'll give that a shot. 

One more thing: SET COMMAND DIRSORT is only three words to type. That's trying too hard?!  (~_^)



More information about the Info-vax mailing list