sunshine@convex.com (Roger Sunshine) (06/17/91)
Every so often, when running qemm and any program which makes extensive use of the extended/expanded memory it provides, my pc will get an interrupt 13 (general exception), usually in the middle of running a command. Most recently, it likes to occur when running Borland c++'s integrated environment and attempting to compile something. I have seen the problem in qemm 4.2 - the current 5.1x. The problem would appear to be qemm taking a trap because the program attempted to reference a word (or double word) at an address that would require some of the word to be fetched from the top of the segment and the rest from the bottom of the segment (eg, read a word at 0xffff in a 64k segment). The PC is a Wells American 386-25 running qemm 5.1 and msdos 3.3. A friend of mine says he has had similar problems on his PC (also a 386-25, but made by leading technologies, I think). Anyone know what the problem is, and how to fix it? it really gets annoying when you have to reboot the machine several times an hour... Thanks, Roger
ferris@gradient.cis.upenn.edu (Richard T. Ferris) (06/17/91)
In article <sunshine.677124931@convex.convex.com> (Roger Sunshine) writes: >Every so often, when running qemm and any program which makes extensive >use of the extended/expanded memory it provides, my pc will get an interrupt >13 (general exception), usually in the middle of running a command. Most >recently, it likes to occur when running Borland c++'s integrated environment >and attempting to compile something. I have seen the problem in qemm 4.2 - >the current 5.1x ... I have just installed both QEMM and Borland C++ on my Gateway 486/33 and I have found a similar problem. When I use the /X option in the buffers line in config.sys, I cannot run C++ from Windows 3. I get a system integrity error. Taking the /X option out makes everything fine. Strange? Any ideas? --RF Richard Ferris ferris@grad1.cis.upenn.edu
noesis@ucscb.UCSC.EDU (60276000) (06/17/91)
QuarterDeck likes the int 13H some much they devoted a section in the user's manual to it. in short, it is usually caused by a mis-behaved program accessing memory to which it is not entitled. This is explained fairly well in appendix A of Qemm386 V5.11 noesis