At 01:22 PM 8/4/2006 +0200, Japheth wrote: > > > > Barring the fileset I requested, or other testable indication that your > > problem occurs with anyone else, I should not think that would be a > > problem. In other words, no need to wait for EMM386 3.0 - codenamed "The > > Arkady Factor". > >Since the error is evident in my eyes, I will not spent any more time to >proove this. But indeed there is no need to wait, and for those who might run >into the problem as I did, you can download a fixed Emm386 at
I asked you for an exact duplicate of a file which demonstrated the problem on your machine so I could duplicate the problem. This is trivial to provide and no effort for you. You apparently aren't interested in doing that, but rather in acting up and pushing your own and others' agenda. Very regrettable behavior. No explanation for the how only nondefault /NOX2MAX32 option could trigger this problem on YOUR machine was provided, so your remarks on the fix are at best incomplete, and possibly rank speculation. I'd look at the problem if you gave me a link to download a program that exactly matches one of the programs you have, and clear up the issue without waving my hands past the open /NOX2MAX32 question. Are you willing to do that trivial task and demonstrate an actual interest in helping to correct the issue, or will you just preach and post here? ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
