Re: Problems with edd

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: H. Peter Anvin
Date: Tuesday, June 10, 2008 - 3:48 pm

devzero@web.de wrote:

This message means something has invoked an interrupt in the range 0x20 
to 0x3f, which it should never have done, since that's in the operating 
system range.

Given the complaint about vesamenu further down the page, I'm assuming 
the VESA BIOS is invoking a DOS interrupt(!!!!)... although it's very 
hard to say for sure.

It might be possible to track down by augmenting syslinux to print the 
CS:IP of the supposed DOS system call; if this is the VESA BIOS, it 
would be in the range C000:xxxx.

This probably would be a useful hack anyway, so I'll just implement it.

	-hpa
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Problems with edd, devzero, (Tue Jun 10, 2:58 pm)
Re: Problems with edd, H. Peter Anvin, (Tue Jun 10, 3:44 pm)
Re: Problems with edd, H. Peter Anvin, (Tue Jun 10, 3:48 pm)
Re: Problems with edd, H. Peter Anvin, (Tue Jun 10, 4:39 pm)
Re: Problems with edd, Keith Roberts, (Wed Jun 11, 4:18 am)
Re: Problems with edd, Keith Roberts, (Wed Jun 11, 1:08 pm)
Re: Problems with edd, H. Peter Anvin, (Wed Jun 11, 1:13 pm)
Re: Problems with edd, Keith Roberts, (Wed Jun 11, 4:52 pm)
Re: Problems with edd, H. Peter Anvin, (Wed Jun 11, 4:55 pm)