On 9/16/07, Darx Kies <[EMAIL PROTECTED]> wrote:
>
> The interrupt is not fired anymore. That was due to a bug in the PIT code.
lolz, I hadn't gotten around to eliminating the PIT code just yet. It
explains why every time I modified the kernel code a little, the error would
occur during a new, random point of execution.
William: The stack overflow now doesn't seem to overflow anymore but the
> keymap stuff
> still doesn't work. Could you take a look at it?
Did we ever fix the error with the kernel's command-line parser not working
correctly? Because that was contributing to part of the keymap issues,
before. *scratches head*
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
