Message-ID: <339C5A3F.75C3@cs.com>
Date: Mon, 09 Jun 1997 19:32:15 +0000
From: "John M. Aldrich" <fighteer AT cs DOT com>
Reply-To: fighteer AT cs DOT com
Organization: Two pounds of chaos and a pinch of salt
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: Robert Hoehne <robert DOT hoehne AT mathematik DOT tu-chemnitz DOT de>,
        DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: Latest stub
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970609135020 DOT 618J-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Eli Zaretskii wrote:
> 
> The bug with 8-char basename in a symlink is real; I got hit by it the
> other day.  I think the solution is just to code explicit 0 where a 0 is
> (incorrectly) assumed.
> 
> I don't recall any other stub-related problems.

I don't know if you folks recall, but a while back when discussing
functionality for DJVERIFY, we had a discussion about how to get an
external program, like a batch file, to figure out what happened if the
stub failed to load.  I made a trivial modification to stub.asm to make
it return a unique code in the 100-110 range corresponding to each
possible error message that it could emit, thus allowing the batch file
to read this code and and display an appropriate diagnostic message. 
Currently the stub exits with code 255 for all errors.

Would this be a valuable thing to add to the theoretical new stub?

Just my 2 bytes worth...

-- 
---------------------------------------------------------------------
| John M. Aldrich, aka Fighteer I |     mailto:fighteer AT cs DOT com      |
| Proud owner of what might one   |   http://www.cs.com/fighteer    |
| day be a spectacular MUD...     | Plan: To make Bill Gates suffer |
---------------------------------------------------------------------