Hey everyone, I''ve been having this really odd problem with calling a real mode mouse interrupt function and strings of garbage bytes being displayed on the video buffer. I''m using VESA 3.0 to initialize my video modes and I''m using __dpmi_int(MOUSE_INTERRUPT, &regs) syntax to call the mouse driver functions. I know that I''m using the routines correctly as I''ve followed the documentation from the driver properly. This is all in djgpp. I''ve used NASM to do a lot of my bitmap blitting routines, and I''m wondering, could this be because I didn''t push/pop all the registers that I thrash during my routines in my blitting functions, and these stale registers are throwing the interrupt out of wack? Anybody ever seen anything like this? I''m at a loss as to why this is happening. It happens for all video modes too. Thanks.