Eric, >> Thus far, I have been absolutely UNABLE to "break into" a V86 >> system ... > > VCPI is there to share protected mode, not to keep you outside.
I was discussing "V86", not VCPI. But in my opinion, requiring VCPI goes a bit too far, since I now have "XMS only" methods for UIDE/UIDE2 that are fast-enough for caching purposes. In real- mode, my drivers make only "A20 enable/disable" calls to the XMS manager and do their own "unreal mode" XMS moves. In protected mode, the drivers do only "Int 15h AH=87h" move-memory requests, an "old" BIOS call which is now "trapped" and handled by JEMM386 or whatever "EMM" driver is active. I have NO further interest in VCPI nor in other "schemes", that now would only "add CODE"!! > But indeed while you are in V86, you have limitations. Running > your stuff in protected mode with HELP of VCPI would fix this, > but it is annoying to need TWO strategies - while there is no > V86, it is easy to have unlimited access and faster than even > shared protected mode with V86. "Might fix this", as the current XMS-only UIDE has not received any complaints related to its speed! VCPI also requires a 4K- byte block for its initialization, which is almost as big as my entire driver! NO, Thank-You! > You can also "break" EMM386 itself by patching it in RAM but > I do not see why that would be good for you. "Forgetting" EMM386 and its miserable 130K size, I have NO wish to do "patches" on it, on JEMMEX/JEMM386 (an insult to Japheth, which I will NOT do!), nor to ANY "front line" programs I might ever write! Time has taught me "The BEST Way!" for UIDE/UIDE2 is to use only "standard" schemes, the simplest of which proved to be XMS memory only! >>> EMM386 only exists for backwards compatibility with EMS-using >>> software ... >> >> I must DISAGREE: EMM386 may have been written for "EMS" memory >> but it EVOLVED into Microsoft's protected-mode provider... > > I disagree again - EMM386 got the VCPI extension so Windows and > EMM386 can cooperate instead of being in the way of each other ... My intent above was to show Rugxulo that EMM386 is NOT "solely" an "EMS" driver, not as it evolved. You are free to quote its extra features, like VCPI. I hope you see I am NOT-interested in VCPI, or DPMI, or anything but "regular" XMS, as that is the only system feature besides Int 13h on which my run-time drivers now "depend". Best wishes, Jack R. Ellis ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
