Bad exe

[admiral coeyman]

Group,
    While running tests at my end, I found an odd problem that seems to have
developed out of the blue.  It seems that only 32 bit dos executables will now
run on my system.  All of the 16-bit executables that I've been using for the
past few years generate 'bad exe' errors.  I've redownloaded most of the tree
and nothing has fixed this problem.  
    Before I look too deep, is this a problem that anybody else has?  It's
possible that my local tree has been damaged or that my development tools are
not right.
    God Bless,
    	--Robert 'Admiral' Coeyman
[I've had vga planets 4.0 running.]

[Uwe Bonnes]

> > > > > "admiral" == admiral coeyman  writes:

admiral> Group, While running tests at my end, I found an odd problem
    admiral> that seems to have developed out of the blue.  It seems that
    admiral> only 32 bit dos executables will now run on my system.  All of
    admiral> the 16-bit executables that I've been using for the past few
    admiral> years generate 'bad exe' errors.  I've redownloaded most of the
    admiral> tree and nothing has fixed this problem.  Before I look too
    admiral> deep, is this a problem that anybody else has?  It's possible
    admiral> that my local tree has been damaged or that my development
    admiral> tools are not right.  God Bless, --Robert 'Admiral' Coeyman
    admiral> [I've had vga planets 4.0 running.]

Alexandre submitted something with regard to 16 bit yesterday
(wine/dlls/version info.c). Remove this and if that doesn't help remove all
other yesterdays patches step by step.

Bye

[admiral coeyman]

Uwe Bonnes,
> Alexandre submitted something with regard to 16 bit yesterday
> (wine/dlls/version info.c). Remove this and if that doesn't help remove all
> other yesterdays patches step by step.

This problem, 'invalid exe file,' is not that new.  I've been having it for a
little while.  It seems that all of the programs compiled under gcc work.  No
other dos executable is currently working.  I am just checking to see if
anybody else is having this problem to see if this is something that I need to
patch or if it's a problem with my system.  Does anybody else run a test dos
executable that is 16 bit?
    God Bless,
    	--Robert 'Admiral' Coeyman

[Christian Costa]

admiral coeyman wrote:
> Uwe Bonnes,
> > Alexandre submitted something with regard to 16 bit yesterday
> > (wine/dlls/version info.c). Remove this and if that doesn't help remove all
> > other yesterdays patches step by step.
>
> This problem, 'invalid exe file,' is not that new.  I've been having it for a
> little while.  It seems that all of the programs compiled under gcc work.  No
> other dos executable is currently working.  I am just checking to see if
> anybody else is having this problem to see if this is something that I need to
> patch or if it's a problem with my system.  Does anybody else run a test dos
> executable that is 16 bit?
>    God Bless,
>    	--Robert 'Admiral' Coeyman

I experienced this problem some times ago. But it happened only under 
the debugger.
The problem was happening  during the parsing of the exe header. It 
turned out
to be a failure in the llseek unix function. I did not figure out what 
really happened and did
not investigate further.

Don't know if you're experiencing the same problem though...

Bye
Christian

[admiral coeyman]

Christian Costa,
> I experienced this problem some times ago. But it happened only under
> the debugger.

When I tried running a program under 'wine --debugmsg +all,' I got an endless
loop.  I tested it with edit.exe.  What I was hoping for is that the program
would crash and I could get an idea of where the program was having the
problem.  That would have given me a starting point.  That did not happen.
> The problem was happening  during the parsing of the exe header. It
> turned out
> to be a failure in the llseek unix function. I did not figure out what
> really happened and did not investigate further.

My problem seems to only effect programs compiled for 16 bit dos.  32 bit dos
programs appear to be running correctly.  I'm saying 32 bit because I know that
gcc compiled these programs to be 32 bits.
> Don't know if you're experiencing the same problem though...

It's worth checking into.  Any pointer will help.
    God Bless,
    	--Robert 'Admiral' Coeyman

[Oliver Ob]

admiral coeyman schrieb:
> Group,
>         While running tests at my end, I found an odd problem that seems to have
> developed out of the blue.  It seems that only 32 bit dos executables will now
> run on my system.  All of the 16-bit executables that I've been using for the
> past few years generate 'bad exe' errors.  I've redownloaded most of the tree
> and nothing has fixed this problem.
>         Before I look too deep, is this a problem that anybody else has?  It's
> possible that my local tree has been damaged or that my development tools are
> not right.
>         God Bless,
>                 --Robert 'Admiral' Coeyman
> [I've had vga planets 4.0 running.]

Aye aye sir! Good to read you here, Rob!

As you know I am also fiddling around with VGAP/WinPlan/P4 and also
had sort of these errors.

I have no dev tools here, but am going to reinstall as I said in PM.

All the best Admiral
Regards from Jenneraaal.. :-)

(Try to pronounce that haha!)