[Bug 1286] - memory allocation interrupt doesnt work

[wine-bugs at winehq.com]

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





------- Additional Comments From eric.noack at gemia.de  2003-02-18 06:45 -------
something seems strange here 
 
if i just run wine (or wineconsole) with --debugmsg +all-trace test.exe 
 
i get 
 
err:font:ReadFontDir Can't open directory 
"/home/raven/.wine/fake_windows/Windows/Fonts" 
Warning: unprotecting the first 64KB of memory to allow real-mode calls. 
         NULL pointer accesses will no longer be caught. 
err:int:DOSVM_Int10Handler int10: unknown/not implemented parameters: 
int10: AX fe00, BX b800, CX 4445, DX 5351, SI 19b2, DI 0000, DS 00f7, ES b800 
Program too bigraven at VikingPC wine $ 
 
but int10h is video, that shouldnt interfere with memory at all 
 
more strange, according to the patch there should be a 
trace:"DOS conventional memory initialized, xxxxx bytes free.\n" 
or something like this, when running DOS programs with 
--debugmsg +trace 
but there isnt. 
so this function is not being run it seems 
 
more strange if i run it with winedebug it stopps with 
 
First chance exception: interrupt 21 in vm86 mode in vm86 code (00f5:0553).  
In vm86 mode.                                                                
Register dump:                                                               
 CS:00f5 SS:00f5 DS:00f5 ES:0065 FS:0000 GS:0000                             
 IP:0553 SP:241e BP:0000 FLAGS:0203(   - 00  I   - - 1C)                     
 AX:3001 BX:0006 CX:ffea DX:19c1 SI:19c2 DI:07d6                             
Stack dump:                                                                  
0x00f5:0x241e:  00e4 75ff e805 0043 cdeb f1b0 a22e 00ac                      
0x00f5:0x242e:  c3f9 892e 0836 eb2d 8e30 8ede 8bc7 2bc7                      
0x00f5:0x243e:  48c6 00a3 2600 00a3 3300 a3c0 0002 a326                      
0x00f5:0x244e:                                                               
                                                                             
Backtrace:                                                                   
=>0 0x00f5:0x0553 (bp=0000)                                                  
Bad stack frame 0x025fffd0                                                   
0x00f5:0x0553: xchgb    %al,%ah                                              
 
however winedbg seems to create errors in other dos programs were no errors 
are, any hint how to debug them? running dos debug.exe maybe? but that sais 
"wrong DOS version", as well as most programs in C:\windows\command" 
 
my dos disassembler (sourcer) 
sais "not enough memory, need 21k more" when run with 
wine 20021125 
and "Packet file corrupt" when run with newest cvs wine 
 
(i didnt downgrade again to test if wine really corrupted the file) 
 
 
 
so here is my configuration: 
 
- wine from CVS  2003.02.17  
- no real windows (at least not configured for wine) 
- gentoo linux on AMD Athlon 650 -- 640 MB ram , tenths of Gigs of diskspace 
- wine programs being run both from ext3 and fat32 partitions 
 
 

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.