Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!ucbvax!info-vax From: info-vax@ucbvax.ARPA Newsgroups: fa.info-vax Subject: VAXIMA and VMS V4 Message-ID: <9366@ucbvax.ARPA> Date: Fri, 26-Jul-85 16:23:01 EDT Article-I.D.: ucbvax.9366 Posted: Fri Jul 26 16:23:01 1985 Date-Received: Sun, 28-Jul-85 09:23:20 EDT Sender: daemon@ucbvax.ARPA Organization: University of California at Berkeley Lines: 30 From: JERRY LEICHTER As has been discussed on this list before, the VMS V3 version of VAXIMA does not work on VMS V4, failing with an "Illegal image header" message (or something similar). The reason for this is simple: The VAXIMA image was NOT produced by the VMS linker, but by something home-grown (at MIT?). That home-grown linker did not fill in at least one field in the image header cor- rectly. As it happens, that field was ignored on V3, but is used on V4. The following patch, the original author of which will remain anonymous, will fix a VAXIMA image so that it will work on either V3 or V4: $ PATCH/ABSOLUTE VAXIMA.EXE REPLACE /BYTE 10 00 EXIT 01 EXIT UPDATE EXIT (All the patch actually does is change the header block count from 0 to 1. Note that this file causes PATCH to confirm that the old value of the count was 0. If PATCH finds it was not, it will exit with an error message. In that case, I can't help you....) -- Jerry ------- ------