another bugfix

I found what causes the init program to display the errant table location
during boot