1. i hate this driver
- Posted by Matt Arriola <vomitthesoul616 at yahoo.com> Mar 29, 2005
- 484 views
i just tried to use one of the examples that came with neil. all i ended up with was a blank screen, then my mouse pointer, then a BSOD telling me "ialmrnt5" got into an infinite loop. before that i tried to translate MVM to C and run it (just mode 18), but at least windows recovered that time, telling me that ialmrnt5 was the problem. does anyone else have problems like this?
2. Re: i hate this driver
- Posted by Hayden McKay <hmck1 at dodo.com.au> Mar 29, 2005
- 475 views
Matt Arriola wrote: > > i just tried to use one of the examples that came with neil. all i ended up > with was > a blank screen, then my mouse pointer, then a BSOD telling me "ialmrnt5" got > into an > infinite loop. before that i tried to translate MVM to C and run it (just mode > 18), > but at least windows recovered that time, telling me that ialmrnt5 was the > problem. > does anyone else have problems like this? > I've has the same problem and here is my analysis .... (dos graphics modes) (banked mades) * niel.e/niel2.e assumes all banked video windows to be at segment A000h. This is not the case for all video adaptor manufactures wich means that it's possible for niel.e/niel2.2 to output video data to an invalid video window causing memory corruption. (linear modes) * If the mode-set is linear and you are running Win NT/2000/XP then you need to get the "descriptor" for the "linear address" (after convertion from the "physical base address") and set the "access rights" useing the DPMI functions provided by Micheal Divore to allow access to ALL memory areas if your not affraid to do this. * This is why Euphoria has a "use_vesa()" function since not all video cards have the same characteristics even though they may have the same VGA BIOS- VESA extentions.
3. Re: i hate this driver
- Posted by Alexander Toresson <alexander.toresson at gmail.com> Mar 29, 2005
- 467 views
Matt Arriola wrote: > > i just tried to use one of the examples that came with neil. all i ended up > with was > a blank screen, then my mouse pointer, then a BSOD telling me "ialmrnt5" got > into an > infinite loop. before that i tried to translate MVM to C and run it (just mode > 18), > but at least windows recovered that time, telling me that ialmrnt5 was the > problem. > does anyone else have problems like this? > The newer versions of windows has some real compatibility problems with vesa. You should switch to windows programming if you want high res modes. Regards, Alexander Toresson
4. Re: i hate this driver
- Posted by Matt Arriola <vomitthesoul616 at yahoo.com> Mar 29, 2005
- 485 views
Hayden McKay wrote: > (banked mades) > * niel.e/niel2.e assumes all banked video windows to be at segment A000h. > This is not the case for all video adaptor manufactures wich means that > it's possible for niel.e/niel2.2 to output video data to an invalid video > window causing memory corruption. i just checked my adapter, and one of the ranges it uses is A0000 to BFFFF. that's segment A000h, isn't it?
5. Re: i hate this driver
- Posted by Hayden McKay <hmck1 at dodo.com.au> Mar 30, 2005
- 463 views
Matt Arriola wrote: > > Hayden McKay wrote: > > (banked mades) > > * niel.e/niel2.e assumes all banked video windows to be at segment A000h. > > This is not the case for all video adaptor manufactures wich means that > > it's possible for niel.e/niel2.2 to output video data to an invalid video > > window causing memory corruption. > > i just checked my adapter, and one of the ranges it uses is A0000 to BFFFF. > that's > segment A000h, isn't it? > Yes... A000h is in "segment" form and A0000h is in "selector" form. What are you useing to check the window segment for the adaptor? you should be useing INT 10h func 4F01h and then read the word at WinAseg, and WinBseg (discription can be found at www.vesa.org) Another reason why the window may be blank is because some cards have a read only window and a write only window. in this case both windows need to point to the same segment ex A000h. (I hav'nt checked niel.e for this case) Anyway this is only applicable to DOS modes if your useing Modes Under Windows I suggest useing the Windows API via "Win32EngR.ew" like alexander states. NB I have tested the modes that dont work with niel.e/niel2.e with my svga.e and svga.e sets the modes successfuly. You might try set the mode with svga.e then modify/preset some variables in niel.e niel2.e to use pete's excelent graphics routines.