Posted: Wed Jan 16, 2008 7:57 pm
OK...
I have found the problem, it wasnt even in my kerenel....It is in my bootloader....there is a problem with the nubmer 128, and possibly any number over that, does anyone know if NASM uses signed integers (i.e. numbers where the MSB is 1 are negative) thats the only thing I can think of, as testing if a num = 128 works, but testing if a 128 is > than 18 doesnt work, when in a byte (cl) but does when in a word (bx)...
so I fixed that problem by making my "get_location" method, which takes an LBA address and converts to CHS, take a word, instead of a byte....however..now it gets to sector 128 (or 129, not sure) and then cant seem to find the next cluster....sigh
I have found the problem, it wasnt even in my kerenel....It is in my bootloader....there is a problem with the nubmer 128, and possibly any number over that, does anyone know if NASM uses signed integers (i.e. numbers where the MSB is 1 are negative) thats the only thing I can think of, as testing if a num = 128 works, but testing if a 128 is > than 18 doesnt work, when in a byte (cl) but does when in a word (bx)...
so I fixed that problem by making my "get_location" method, which takes an LBA address and converts to CHS, take a word, instead of a byte....however..now it gets to sector 128 (or 129, not sure) and then cant seem to find the next cluster....sigh