terrell@musky2.EDU (Roger Terrell) (02/04/88)
I took VERB from comp.os.vms, unSHARed it with no errors, compiled it
via the COMPILE.COM command file with no errors, and ran it. This was
the output...
$ RUN VERB
Error parsing 'width'
Specified entity not found in command tables
Symbolic stack dump follows
module name routine name line rel PC abs PC
7FF946F5 7FF946F5
7FF944FB 7FF944FB
7FF9401C 7FF9401C
00008D7A 00008D7A
VERB_EXTRACTOR VERB_EXTRACTOR 32 0000001D 00008A1D
Does anyone have an idea of the problem?
Thanks,
Roger
--
Roger Terrell
Muskingum College ...cbosgd!musky2!terrell (UUCP)
New Concord, OH 43762hydrovax@nmtsun.nmt.edu (M. Warner Losh) (02/05/88)
In article <52@musky2.EDU>, terrell@musky2.EDU (Roger Terrell) writes: > > I took VERB from comp.os.vms, unSHARed it with no errors, compiled it > via the COMPILE.COM command file with no errors, and ran it. This was > the output... > > $ RUN VERB > [error deleted] > Does anyone have an idea of the problem? Yes, actually. I do. Since I was the poster of this program I know a thing or two about it. Unfortunately note enough things, but I can answer this question. In the readme file, there should have been a reference to the .cld file that the program needs. You should do a $ SET COMMAND VERB.CLD and have EXE$DIR defined to point to the current directory (quickest and easiest way that I know of is DEFINE EXE$DIR 'F$ENVIRONMENT("DEFAULT")). Then just type VERB verb, and it will give you the definition of verb on your terminal. I just looked the distribution I made, and sure enough, there aren't explicit instructions on it's setup. And the instructions on it's use were a little vague (and found in the BLURB.TXT file). The command file stuff is the crtical bit here. Sorry for any confusion that I may have generated. :-(. -- bitnet: losh@nmt.csnet M. Warner Losh warner@hydrovax.nmt.csnet ! Don't know if this works, let me know. csnet: warner@hydrovax.nmt.edu uucp: ...{cmcl2, ihnp4}!lanl!unmvax!nmtsun!warner%hydrovax
ignatz@chinet.UUCP (Dave Ihnat) (02/07/88)
Yep. It's using the CLI command parser calls to try and get it's arguments; and you havent' installed the command via 'INSTALL'. -- Dave Ihnat ihnp4!homebru!ignatz || ihnp4!chinet!ignatz (w) (312) 882-4673
hydrovax@nmtsun.nmt.edu (M. Warner Losh) (02/08/88)
In article <2266@chinet.UUCP>, ignatz@chinet.UUCP (Dave Ihnat) writes: > Yep. It's using the CLI command parser calls to try and get it's > arguments; and you havent' installed the command via 'INSTALL'. This isn't entirely correct. You do need to do something special, but it isn't install. You need to do a SET COMMAND VERB and then run verb via $VERB ... Other than that, you are correct about verb using the command parser. -- bitnet: losh@nmt.csnet M. Warner Losh warner@hydrovax.nmt.csnet ! Don't know if this works, let me know. csnet: warner@hydrovax.nmt.edu uucp: ...{cmcl2, ihnp4}!lanl!unmvax!nmtsun!warner%hydrovax