From:	"Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>, <djgpp-workers AT delorie DOT com>
Subject:	RE: stubify and Windows ME
Date:	Thu, 15 Mar 2001 19:13:09 +0100
Message-ID:	<CAEGKOHJKAAFPKOCLHDIIEJLCBAA.tim.van.holder@pandora.be>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To:	<Pine.SUN.3.91.1010315191956.10192A-100000@is>
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
Importance:	Normal
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> I have an idea: what if the users who have this problem use non-LFN
> setup on Windows?  Tim, could you please set LFN=n and try link a
> simple program on Windows ME?
Success! Well, er, failure!

"Regular" linking works fine (i.e. without stubify).

'stubify -g bar.exe' works fine.

'stubify foo' works fine if foo.exe does not exist.

'stubify foo' fails if foo.exe exists:
rename of foo.000 to foo.exe failed.
The error was: Invalid argument (EINVAL)

Afterwards, foo.exe is gone and foo.000 exists.

Debugging (using sources from current CVS), I see that the int 21/43ff
call leaves 0x3003 in flags (ax: 1, bx: 0, cx:7f56).
Disabling the LFN version of this call in _rename (falling back on
21/56) makes it work.

Anything else I should look into?

- Raw text -