From: "Tim Van Holder" To: Subject: RE: stubify and Windows ME Date: Thu, 8 Mar 2001 18:43:31 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-Mimeole: Produced By Microsoft MimeOLE V5.50.4133.2400 In-reply-to: <8011-Thu08Mar2001091403+0200-eliz@is.elta.co.il> 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 Precedence: bulk > Thanks. What does VER and Control Panel -> System say about the > Windows version on your machine? VER says: 4DOS 6,01A (Win98) DOS 8,00 under 4Dos and Windows Millennium [Version 4.90.3000] under command.com. The control panel agrees with the latter. > > Maybe the executable was open (possibly running in another window)? > > He says that the executable was never created in the first place > (because of the problem with stubify). Well, I was unable to get EINVAL with stubify -v foo. If 'foo' does not exist, I get foo: No such file or directory (ENOENT) (regardless of whether foo.exe exists). If foo exists, but is neither COFF or stubbed COFF, I get Warning: input file is not COFF or stubbed COFF (regardless of whether foo.exe exists). If foo exists and is COFF (stubbed or otherwise), I get stubify: foo -> foo.exe or stubify: foo -> foo.000 -> foo.exe depending on whether foo.exe already exists There's no other case I can think of. I suggest you ask the person in question to try again, and post a) the exact input file used b) the specs file c) the exact output produced by gcc