From:	kunst AT prl DOT philips DOT nl
Subject:	Re: Problems with stub.exe
To:	TJSSTE01 AT Uctvax DOT UCT DOT AC DOT ZA
Date:	Tue, 1 Feb 1994 12:18:33 +0100 (MET)
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu (DJGPP users list)

Stephen Tjasink (stjasink AT uctvax DOT uct DOT ac DOT za) writes:
> 
> I've got a problem that is causing me great distress at the moment...
> I'm using version 1.10 because 1.11 kept crashing on my computer with 
> 'unsupported interrupt 0x0d' or something.
> Anyway... this is what happened:
> I compiled my program and got my output file 'a'.
> Then I ran 'aout2exe a' and it made 'a.exe' as I would expect.
> If I delete 'a' and try running 'a.exe', it runs as it I had just run a copy
> of 'stub.exe' or 'go32.exe' and gives me the '/stuff/a.exe version 1.10 by
> D.J. Delorie, usage: /stuff/a.exe program [options]' or whatever 'stub.exe' or
> 'go32.exe' gives when you run it without any parameters.
> Stub seems to be ignoring the 100k of program that it appended to it. :(
> If I leave 'a' and run 'a.exe', then it runs okay because it runs as if I had
> 
> I'm sure it all used to work okay before I tried installing 1.11, deleted it
> and then reinstalled 1.10.
> Any help would be appreciated.

It looks like you're using a mix of version 1.10 and version 1.11 tools.
I would install DJGPP 1.11 (and dj111m1.zip and dj111m2.zip) if I were you.

You can use 'symify' (1.11) to locate the source of your 'unsupported 
interrupt 0x0d'. Make sure not to 'strip' your executable.

Your 'unsupported interrupt 0x0d' has a great chance to be due to
a call to int86x() somewhere in your program, or somewhere in one of
the routines in the library used by your program.

Hope this helps,

Pieter Kunst (kunst AT prl DOT philips DOT nl)

- Raw text -