home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!rutgers!cmcl2!panix!jhawk
- From: jhawk@panix.com (John Hawkinson)
- Newsgroups: comp.os.vms
- Subject: Problems with DISM32
- Message-ID: <1992Sep7.021613.5554@panix.com>
- Date: 7 Sep 92 02:16:13 GMT
- Organization: PANIX Public Access Unix, NYC
- Lines: 92
-
- Hi there,
-
- I just got a copy of DISM32, and I'm having some weird problems.
- Firstly, it spits out a bunch of FORTRAN errors at me when I run
- it on DCL.EXE (some other things, too); could these have to do with
- it needing to be relinked? I'm running VMS 5.5, and I ftp'd the
- version from ftp.spc.edu. Anyway, here's what it says:
-
- %PHOTO-I-INIT, Recording initiated at 6-SEP-1992 20:10:09.68
-
- %DISM32-I-NONSTDIMG, non-standard native mode image of type CLI
- %DISM32-I-CREOPTFIL, image requires .OPT file; USR$SYSADMIN:[JHAWK.PROG.HACK]DCL
- .OPT;2 created
- %DISM32-I-SHRIMAGE, image is shareable (created with /SHAREABLE)
- %FOR-E-OUTCONERR, output conversion error
- unit 2 file USR$SYSADMIN:[JHAWK.PROG.HACK]DCL.MAR;2
- user PC 0010D491
- %TRACE-E-TRACEBACK, symbolic stack dump follows
- module name routine name line rel PC abs PC
-
- 00184E22 00184E22
- 00184D1F 00184D1F
- 00180E94 00180E94
- DISM32$MAIN DISM32$MAIN 1604 00001091 0010D491
- %FOR-E-OUTCONERR, output conversion error
- unit 2 file USR$SYSADMIN:[JHAWK.PROG.HACK]DCL.MAR;2
- user PC 0010D491
- %TRACE-E-TRACEBACK, symbolic stack dump follows
- module name routine name line rel PC abs PC
-
- 00184E22 00184E22
- 00184D1F 00184D1F
- 00180E94 00180E94
- DISM32$MAIN DISM32$MAIN 1604 00001091 0010D491
- %FOR-E-OUTCONERR, output conversion error
- unit 2 file USR$SYSADMIN:[JHAWK.PROG.HACK]DCL.MAR;2
- user PC 0010D491
- %TRACE-E-TRACEBACK, symbolic stack dump follows
- module name routine name line rel PC abs PC
-
- 00184E22 00184E22
- 00184D1F 00184D1F
- 00180E94 00180E94
- DISM32$MAIN DISM32$MAIN 1604 00001091 0010D491
- %FOR-E-OUTCONERR, output conversion error
- unit 2 file USR$SYSADMIN:[JHAWK.PROG.HACK]DCL.MAR;2
- user PC 0010D491
- %TRACE-E-TRACEBACK, symbolic stack dump follows
- module name routine name line rel PC abs PC
-
- 00184E22 00184E22
- 00184D1F 00184D1F
- 00180E94 00180E94
- DISM32$MAIN DISM32$MAIN 1604 00001091 0010D491
- %FOR-E-OUTCONERR, output conversion error
- unit 2 file USR$SYSADMIN:[JHAWK.PROG.HACK]DCL.MAR;2
- user PC 0010D491
- %TRACE-E-TRACEBACK, symbolic stack dump follows
- module name routine name line rel PC abs PC
-
- 00184E22 00184E22
- 00184D1F 00184D1F
- 00180E94 00180E94
- DISM32$MAIN DISM32$MAIN 1604 00001091 0010D491
- %FOR-E-OUTCONERR, output conversion error
- unit 2 file USR$SYSADMIN:[JHAWK.PROG.HACK]DCL.MAR;2
- user PC 0010D491
- %TRACE-E-TRACEBACK, symbolic stack dump follows
- module name routine name line rel PC abs PC
-
- 00184E22 00184E22
- 00184D1F 00184D1F
- 00180E94 00180E94
- DISM32$MAIN DISM32$MAIN 1604 00001091 0010D491
- Beginning pass 1...
-
- =================================CUT HERE======================
-
- Anyway, the reason I'm doing this (in case you missed my prev. post)
- was I'm trying to figure out how to patch DCL to use a prompt
- longer than 32 chars. So, I looked at Hunter's DCL recall patch. He
- mentions using DISM32 to disassemble DCL.EXE. I've done this (assuming
- the above problem isn't affecting this) and it fails to recognize
- the symbols in SYS$SYSTEM:DCLDEF.STB (not surprisingly). In an effort
- to remedy this, I did a LINK/NOEXEC/FULL/MAP SYS$SYSTEM:DCLDEF.STB and
- then converted the symbols there to DISM32 .SYM format, and gave them
- a mask of FFFFFFFF, and called the file DCL.SYM. I then ran DISM32 on
- DCL.EXE again, and it still failed to use those symbols. Ideas?
-
- --
- John Hawkinson
- jhawk@panix.com
-