out of memory on dos programs

[Eric Noack]

i get a "Program too big" error on all programs compiled
with the "PowerBASIC" compiler pbc.exe 3.00c

and similar out of memory errors on other dos programs, when running them under wine

to my pleasure the pbc compiler itself runs fine under wine

here is an example:

http://gemia.de/test/test.bas

a hello world BASIC source

http://gemia.de/test/test.exe

the binary compiled with pbc 3.00c under wine

http://gemia.de/test/pbc.exe

same compiler

on every program compiled with a PowerBASIC compiler i get

"Program too big"
when running it under wine.
this string is given out by the executable when failing to allocate some memory

i tryed to disassemble the compiled program to check what type of memory allocation
should have taken place, but my dos disassembler (sourcer) failed under wine
with an out of memory error, too.

now is this a bug in wine, not handling some ms-dos memory allocation requests,
or did i just miss some configuration option to tell wine to give dos programs
more memory to allocate?

i hope this is not OT too much


Eric


PS: here is the console output
> raven(a)VikingPC wine $ cat test.bas
> print "hello world"
> raven(a)VikingPC wine $ wine pbc test.bas
> Warning: unprotecting the first 64KB of memory to allow real-mode calls.
>         NULL pointer accesses will no longer be caught.
> PowerBASIC Compiler Version 3.00c  Copyright (c) 1989-1993 by Robert S. Zale
> PowerBASIC Inc. *  Brentwood, CA, USA
> F:\TEST\WINE\TEST.BAS
> 3 statements, 2 lines
> Compile time: 00:00.1 Compilation speed: 1800 stmts/minute
> 272 bytes code, 2800 bytes data, 2048 bytes stack
> Segments(1): 1k
> raven(a)VikingPC wine $ wine test.exe
> Warning: unprotecting the first 64KB of memory to allow real-mode calls.
>         NULL pointer accesses will no longer be caught.
> Program too bigraven(a)VikingPC wine $

I found the string "Program too big" in test.exe at position 0000:2203 hex
I guess its just given out after failing to allocate some memory ;)
as i said my disassembler doesnt work doe to some similar error

[Tony Lambregts]

Eric Noack wrote:
> i get a "Program too big" error on all programs compiled
> with the "PowerBASIC" compiler pbc.exe 3.00c
>
> and similar out of memory errors on other dos programs, when running them under wine
>
> to my pleasure the pbc compiler itself runs fine under wine
>
> here is an example:
>
> http://gemia.de/test/test.bas
>
> a hello world BASIC source
>
> http://gemia.de/test/test.exe
>
> the binary compiled with pbc 3.00c under wine
>
> http://gemia.de/test/pbc.exe
>
> same compiler
>
> on every program compiled with a PowerBASIC compiler i get
>
> "Program too big"
> when running it under wine.
> this string is given out by the executable when failing to allocate some memory
>
> i tryed to disassemble the compiled program to check what type of memory allocation
> should have taken place, but my dos disassembler (sourcer) failed under wine
> with an out of memory error, too.
>
> now is this a bug in wine, not handling some ms-dos memory allocation requests,
> or did i just miss some configuration option to tell wine to give dos programs
> more memory to allocate?
>
> i hope this is not OT too much

Not if you intend to implement the missing functions or fix the bugs and 
are just asking for some help in that direction. Otherwise Bugzilla  is 
the place for this http:\\bugs.winehq.org
> Eric
>
> PS: here is the console output
> > raven(a)VikingPC wine $ cat test.bas
> > print "hello world"
> > raven(a)VikingPC wine $ wine pbc test.bas
> > Warning: unprotecting the first 64KB of memory to allow real-mode calls.
> >        NULL pointer accesses will no longer be caught.
> > PowerBASIC Compiler Version 3.00c  Copyright (c) 1989-1993 by Robert S. Zale
> > PowerBASIC Inc. *  Brentwood, CA, USA
> > F:\TEST\WINE\TEST.BAS
> > 3 statements, 2 lines
> > Compile time: 00:00.1 Compilation speed: 1800 stmts/minute
> > 272 bytes code, 2800 bytes data, 2048 bytes stack
> > Segments(1): 1k
> > raven(a)VikingPC wine $ wine test.exe
> > Warning: unprotecting the first 64KB of memory to allow real-mode calls.
> >        NULL pointer accesses will no longer be caught.
> > Program too bigraven(a)VikingPC wine $
>
> I found the string "Program too big" in test.exe at position 0000:2203 hex
> I guess its just given out after failing to allocate some memory ;)
> as i said my disassembler doesnt work doe to some similar error

What is your version of wine (wine -v)

[tony(a)tony tony]$ wine "f:\test"
Warning: unprotecting the first 64KB of memory to allow real-mode calls.
         NULL pointer accesses will no longer be caught.
fixme:int21:DOSVM_Int21Handler SetSystemDate(81/83/17477): not allowed
fixme:int:DOSVM_Int10Handler Unknown - 0xfe
err:int:DOSVM_Int10Handler int10: unknown/not implemented parameters:
int10: AX fe00, BX b800, CX 4445, DX 5351, SI 19b2, DI 0000, DS 00ab, ES 
b800
fixme:int:DOSVM_Int16Handler Unknown INT 16 function - 0x5
Program too big


Thats a couple of interupt handlers that want some attention.

-- 

Tony Lambregts

[Eric Noack]

Am Mon, 17 Feb 2003 21:18:20 -0700
schrieb Tony Lambregts <tony_lambregts(a)telusplanet.net>:
> Not if you intend to implement the missing functions or fix the bugs and 
> are just asking for some help in that direction. Otherwise Bugzilla  is 
> the place for this http:\\bugs.winehq.org

hmm maybe i can help somehow. i didnt find the right bugdescription for this kind of bug
now at least i know that it seems to be missing interrupt handlers
i didnt have that fixme output even if i tried 

-----
> raven(a)VikingPC wine $ wine --debugmsg +fixme test.exe
> Warning: unprotecting the first 64KB of memory to allow real-mode calls.
>         NULL pointer accesses will no longer be caught.
> Program too bigraven(a)VikingPC wine $

> >
>
> What is your version of wine (wine -v)

------
> raven(a)VikingPC C $ wine -v
> Wine 20021125

> [tony(a)tony tony]$ wine "f:\test"
> Warning: unprotecting the first 64KB of memory to allow real-mode calls.
>          NULL pointer accesses will no longer be caught.
> fixme:int21:DOSVM_Int21Handler SetSystemDate(81/83/17477): not allowed
> fixme:int:DOSVM_Int10Handler Unknown - 0xfe
> err:int:DOSVM_Int10Handler int10: unknown/not implemented parameters:
> int10: AX fe00, BX b800, CX 4445, DX 5351, SI 19b2, DI 0000, DS 00ab, ES 
> b800
> fixme:int:DOSVM_Int16Handler Unknown INT 16 function - 0x5
> Program too big
>
> Thats a couple of interupt handlers that want some attention.
>
> --
>
> Tony Lambregts

thanx
i fear i dont have the time right now to dig deep enough into the wine code to write interrupt handlers
mabe later

but once there was a real interesting list of interrupt handler description available under

ftp://FTP.CS.CMU.EDU/afs/cs.cmu.edu/user/ralf/pub/interrupt-list

ok that was back in 1993, but it seems they worked further on it

combine that interrupt.a - interrupt.r files to the complete list
(in inter61a.zip - inter61f.zip right now as it seems)

maybe that can help someone

Eric

[Tony Lambregts]

Eric Noack wrote:
> Am Mon, 17 Feb 2003 21:18:20 -0700
> schrieb Tony Lambregts <tony_lambregts(a)telusplanet.net>:
> > Not if you intend to implement the missing functions or fix the bugs and 
> > are just asking for some help in that direction. Otherwise Bugzilla  is 
> > the place for this http:\\bugs.winehq.org
>
> hmm maybe i can help somehow. i didnt find the right bugdescription for this kind of bug
> now at least i know that it seems to be missing interrupt handlers
> i didnt have that fixme output even if i tried
>
> -----
> > raven(a)VikingPC wine $ wine --debugmsg +fixme test.exe
> > Warning: unprotecting the first 64KB of memory to allow real-mode calls.
> >        NULL pointer accesses will no longer be caught.
> > Program too bigraven(a)VikingPC wine $
>
> -----

Well you have an out of date Wine so that might be part of it.
> > What is your version of wine (wine -v)
>
> ------
> > raven(a)VikingPC C $ wine -v
> > Wine 20021125
>
> ------

Not counting CVS the most recent version of wine is 20030115 (Time to 
update)
> > [tony(a)tony tony]$ wine "f:\test"
> > Warning: unprotecting the first 64KB of memory to allow real-mode calls.
> >         NULL pointer accesses will no longer be caught.
> > fixme:int21:DOSVM_Int21Handler SetSystemDate(81/83/17477): not allowed
> > fixme:int:DOSVM_Int10Handler Unknown - 0xfe
> > err:int:DOSVM_Int10Handler int10: unknown/not implemented parameters:
> > int10: AX fe00, BX b800, CX 4445, DX 5351, SI 19b2, DI 0000, DS 00ab, ES 
> > b800
> > fixme:int:DOSVM_Int16Handler Unknown INT 16 function - 0x5
> > Program too big
> >
> > Thats a couple of interupt handlers that want some attention.
> >
> > --
> >
> > Tony Lambregts
>
> thanx
> i fear i dont have the time right now to dig deep enough into the wine code to write interrupt handlers
> mabe later
>
> but once there was a real interesting list of interrupt handler description available under
>
> ftp://FTP.CS.CMU.EDU/afs/cs.cmu.edu/user/ralf/pub/interrupt-list
>
> ok that was back in 1993, but it seems they worked further on it
>
> combine that interrupt.a - interrupt.r files to the complete list
> (in inter61a.zip - inter61f.zip right now as it seems)
>
> maybe that can help someone
>
> Eric

There has been a fair amount of work on this end of things done by 
(mostly) Jukka Heinonen. He may be interested in this. If nothing else 
this has the makeings of a very good bug report.  

-- 

Tony Lambregts

[Eric Noack]

Am Mon, 17 Feb 2003 22:30:46 -0700
schrieb Tony Lambregts <tony_lambregts(a)telusplanet.net>:
> >
>
> Well you have an out of date Wine so that might be part of it.

is seems that i just missed a wrapper script my distribution installed at /usr/bin that runned
wine with --debugmsg -all after setting some environment vars. i fixed that now it sais

err:int:DOSVM_Int10Handler int10: unknown/not implemented parameters:
int10: AX fe00, BX b800, CX 4445, DX 5351, SI 19b2, DI 0000, DS 1120, ES b800

int 10 are video functions afaik, so this shouldnt be the error cause
> >
>
> Not counting CVS the most recent version of wine is 20030115 (Time to 
> update)

if i start digging into the handlers i wont get around cvs ;)
> >
>
> There has been a fair amount of work on this end of things done by 
> (mostly) Jukka Heinonen. He may be interested in this. If nothing else 
> this has the makeings of a very good bug report.

:-)

i'll write a verbous bug report to the bugzilla, now that i know what kind of bug it is
i should be able to report it properly ;) thanks for your help


Eric

[Eric Noack]

Am Tue, 18 Feb 2003 04:38:30 +0100
schrieb Eric Noack <eric.noack(a)gmx.de>:
> http://gemia.de/test/pbc.exe
>
> same compiler

it seems this program is still copyrighted, so please get the demo version

3.2 from

http://www.powerbasic.com/files/pub/trypb32.zip

instead
this one causes the same error but has some trial restrictions. it should do for testing


Eric

[Sylvain Petreolle]

dont try to run it a real windows...
it tries to set the date incorrectly when run under wcmd.exe.
(no  "Program too big" though)

perhaps a problem into the exe loader ?
 --- Eric Noack <eric.noack(a)gmx.de> a écrit : > i get a "Program too
big" error on all programs compiled
> with the "PowerBASIC" compiler pbc.exe 3.00c
>
> and similar out of memory errors on other dos programs, when running
> them under wine
>
> to my pleasure the pbc compiler itself runs fine under wine
>
> here is an example:
>
> http://gemia.de/test/test.bas
>
> a hello world BASIC source
>
> http://gemia.de/test/test.exe
>
> the binary compiled with pbc 3.00c under wine
>
> http://gemia.de/test/pbc.exe
>
> same compiler
>
> on every program compiled with a PowerBASIC compiler i get
>
> "Program too big"
> when running it under wine.
> this string is given out by the executable when failing to allocate
> some memory
>
> i tryed to disassemble the compiled program to check what type of
> memory allocation
> should have taken place, but my dos disassembler (sourcer) failed
> under wine
> with an out of memory error, too.
>
> now is this a bug in wine, not handling some ms-dos memory allocation
> requests,
> or did i just miss some configuration option to tell wine to give dos
> programs
> more memory to allocate?
>
> i hope this is not OT too much
>
> Eric
>
> PS: here is the console output
> > raven(a)VikingPC wine $ cat test.bas
> > print "hello world"
> > raven(a)VikingPC wine $ wine pbc test.bas
> > Warning: unprotecting the first 64KB of memory to allow real-mode
> > calls.
> >         NULL pointer accesses will no longer be caught.
> > PowerBASIC Compiler Version 3.00c  Copyright (c) 1989-1993 by Robert
> > S. Zale
> > PowerBASIC Inc. *  Brentwood, CA, USA
> > F:\TEST\WINE\TEST.BAS
> > 3 statements, 2 lines
> > Compile time: 00:00.1 Compilation speed: 1800 stmts/minute
> > 272 bytes code, 2800 bytes data, 2048 bytes stack
> > Segments(1): 1k
> > raven(a)VikingPC wine $ wine test.exe
> > Warning: unprotecting the first 64KB of memory to allow real-mode
> > calls.
> >         NULL pointer accesses will no longer be caught.
> > Program too bigraven(a)VikingPC wine $
>
> I found the string "Program too big" in test.exe at position
> 0000:2203 hex
> I guess its just given out after failing to allocate some memory ;)
> as i said my disassembler doesnt work doe to some similar error

=====
Sylvain Petreolle
spetreolle(a)users.sourceforge.net 
Fight against Spam ! http://www.euro.cauce.org/en/index.html
ICQ #170597259

"Don't think you are. Know you are." Morpheus, in "Matrix".

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

[Eric Noack]

i reported the thing as bug 1286
additional info there - maybe


Eric