No, that's Larry's memory detection code. My patch calls
int 15h, ax=0e801h, grabs that result if the call succeeded,
then calls int 15h, ah=88h, grabs that result, and uses the
largest of the two values as the memory size. You can't
just check the return from ah=88h against 64mb, because
some bioses take a conservative approach and only return
a maximum of 16mb (Compaq comes immediately to mind here)
____
david parsons \bi/ hardwiring memory sizes is icky
\/