From:	softbrek AT cip-s01 DOT informatik DOT rwth-aachen DOT de (Hans-Bernhard Broeker)
Subject:	Re: Unkown filetype / Can't load file <-v>
To:	enok AT lysator DOT liu DOT se
Date:	Wed, 7 Dec 1994 11:21:50 +0100 (MET)
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu (djgpp), dj AT ctron DOT com (DJ Delorie)

Hi, all

Seems as if another poor user got caught in the "multiple go32.exe"
trap (or I'm totally mistaken, in that case you may correct me).
(DJ: this one should be put in the FAQ, I think)

Oskar Enoksson asked :

> 
> Hi all!
> I tried to invoke gasp (the gnu assembler preprocessor), but I keep getting
> the error "unknown filetype (xxxx)" where xxxx are hexadecimal digits
> which appear to be the first two bytes of the sourcecode file I am trying
> to compile! What am I doing wrong ????
> 

and (in another mail, cited from memory, so excuse any errors, please)

>Several gcc-programs give messages like 'Can't open the file <-bar>'
>or the like, when invoked as 'foo -bar'. What's happening ???

Well, I might be wrong on this, but this looks like you're having
problems with multiple versions of go32.exe in your PATH. If just
typing 

	go32

on the commandline does *not* give you a message of about 6 lines,
including information of what version of go32.exe you have just
invoked (version should be "1.12maint2"), then you should try to make
%DJGPP%\bin the *first* entry of your PATH variable (and keep a copy
of the newest go32.exe you have in there), and the problem should go
away. 

Alternatively, you might want to erase all older versions from all
other directories in your PATH, perhaps keeping backups under names
like go32_115.exe for 1.11maint5, and so on, just in case some program
really relies on its own version (oemacs v4.1 and caml386 v6 need
their own go32.exe's, for example). Then you can trick around to
make them use the exact version of go32 they need using a recent
stub.exe and stubedit'ing the name of go32 into the executable. (Ask,
if you need details on this).

I prefer the second way, as it works even if you haven't called
setdjgpp.bat, or %DJGPP%\bin isn't in your normal PATH at all, but
only put into it if needed.

Hope this is of any use to someone

Hans-Bernhard Broeker 
(	softbrek AT pool DOT informatik DOT rwth-aachen DOT de )
(or 	Broeker AT axpmgr DOT physik DOT rwth-aachen DOT de    )

- Raw text -