[Bug 1286] New: - memory allocation interrupt doesnt work

http://bugs.winehq.com/show_bug.cgi?id=1286

Summary: memory allocation interrupt doesnt work
           Product: Wine
           Version: unspecified
          Platform: Other
               URL: http://gemia.de/test/test.exe
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: wine-dos
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

somehow no dos program compiled with a PowerBASIC compiler runs under wine 
unlike the powerbasic compiler itself which runs perfectly

the trial version of the IDE with compiler is available at 
http://www.powerbasic.com/files/pub/trypb32.zip

it runs under wine and creates executables not running under wine 
(try compiling a  
print "hello world" 
program)

executables compiled under windows or dos behave the same so the compiler 
really works it seems

i fear some memory allocation interrupt requests are not handled correctly which 
makes those programs exit with a "Program too big" error message after internal 
checks before actually executing senseful code.

by the way, is it possible to make wine provide more memory to the dos area for 
any dos programs?

i spotted a nice interrupt handler list at 
ftp://FTP.CS.CMU.EDU/afs/cs.cmu.edu/user/ralf/pub/interrupt-list

in inter61a.zip - inter61f.zip are files reaching from INTERRUPTS.A - INTERRUPTS.R 
being several Megs of plain text in size if combined and providing a huge list of 
official and "undocumented" interrupt handlers reaching from specific BIOS 
functions over MS , DR and Novel-DOS interrupt handlers and interrupts of widely 
spread TSRs to INTs hooked by various viree 
i stepped on the link when digging through old files on my HDD

additional information will follow as soon as i disassembled the executable and 
installed the latest cvs wine src

Eric

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://bugs.winehq.com/show_bug.cgi?id=1286.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.