[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

240.0. "Problem with MANX C Version 3.20a" by HARRY::OSBORNE (Blade Walker) Mon Jan 05 1987 11:26

I recently (12/27/86) purchased the MANX C68 Developer package, version 
3.20a. Imagine my surprise when the introductory tutorial didn't work!
What happens is that instead of invoking the assembler after creating
the assembler source as a temporary file, the compiler ("cc") just stops,
leaving the assembler source code as a temp file in ram:, where it's
directed. If I invoke the assembler manually, using the temp file as
input, I can generate  the object (".o") file, and all is well. However,
this is very inconvenient- I can create a CLI file to do this, plus 
clean up, but one of the reasons I got MANX C was to get away from 
Lattice "execute" files.

More than a little aggrevated, I called the MANX support bb. Yes, there
is a bug in "cc", version 3.20a- it doesn't chain properly when used
with AmigaDOS 1.2. On the bb was a "patch" program (patch.c) which 
contained instructions for patching "cc" to work with 1.2. Sure enough,
when I booted with AmigaDOS 1.1, "cc" worked fine. I compiled the
patch program and ran it (it opens "cc" and replaces one longword of
the machine code). "cc" stopped working correctly on 1.1, as the patch
description said it would, but when I rebooted with AmigaDOS 1.2, it
still didn't work!

Anyway, if anyone has been through this before with Aztec C68, v.3.20a,
and has successfully patched it, would you please forward the patch
source to me via mail.

I am going to call MANX this afternoon, and will add my comments on the
results. For those considering a MANX purchase, be aware that 3.20a has
this problem.

John O.
T.RTitleUserPersonal
Name
DateLines
240.1Patches for v1.2COOKIE::WECKERDave (Cum Grano Salis) WeckerMon Jan 05 1987 21:1453
re:	.0

1)	You got rooked... v3.40 is being shipped at the end of this
	month and is ADVERTISED as the current version so make sure
	they mail you 3.40 when it ships.

2)	Perform patches (using the patch program listed below):

		1> patch cc	D51F
		1> patch make	1D37
		1> patch make	2063
		1> patch db	67A9
		1> patch c.lib	303E
		1> patch c.lib	348A
		1> patch c32.lib 3176
		1> patch c32.lib 35BE

	MAKE SURE YOU DO THIS ON COPIES ONLY!!! (or you'll never run on 1.1
	again)

==============================PATCH.C==============================

/* This should be compiled on 1.1 of the O/S to patch versions for 1.2  */
/* (If your compiler is already patched, compile this on 1.2)		*/
/*	DBW	870105							*/

main(argc,argv)
int argc;
char **argv;
    {
    int	    i,fd;
    long    pos;

    if (argc < 2 || (fd = open(argv[1],2)) == -1) {
	printf("Can't open file\n");
	exit(1);
	}
    if (argc < 3 || sscanf(argv[2],"%lx",&pos) != 1) {
	printf("Can't get address argument\n");
	exit(1);
	}

    if (lseek(fd,(long)pos,0) == -1L) {
	printf("Can't seek\n");
	exit(1);
	}
    if (write(fd,"\xa8",1) == -1) {
	printf("Can't write\n");
	exit(1);
	}
    close(fd);
    }