🚀 go-pugleaf

  Can anyone out there shed some light on a dim subject (my brain).. that
being what in the heck the format is of the .ndx files that are produced
by QWK compatible doors... I'm currently stuck on this 1 point, I'm writing a
QWK Mail door and for the life of me can't figure it out... I have misc
docs of the QWK standards, everything else is a piece of cake but here is my
situation:
    The QWK docs say that the numbers in the .ndx files are MSBIN or BasicReal
format, and that I have to convert them to/from a Float format??? why would
they be floating point numbers anyways, a Long int (4 odd million) would seem
sufficient, but anyways, here is a routine I pulled out of the docs..
 
union Converter
{
unsigned char uc[10];
unsigned int  ui[5];
unsigned long ul[2];
float       f[2];
double       d[1];
}
 
float MSBINToIEEE(float f)
{
union Converter t;
int sign, exp;
 
t.f[0] = f;
 
sign = t.uc[2] / 0x80;
exp  = (t.uc[3] - 0x81 + 0x7F) & 0xFF;
 
t.ui[1] = (t.ui[1] & 0x7F) | (exp << 7) | (sign << 15);
return(t.f[0]);
}
 
 
  I have many QWK packets I've pulled off of many boards, and always, the first
.ndx file (the one that pertains to the first message in Message.dat) contains
for the first message 0x82... which is 130 in decimal... if you run that
through the converter you don't get a Byte seek position or a 128byte block
position?? At least that is one common thing... from there on out it seems
erratic as to what the next value will be... Someone told me that they were
Shown 86%, press <SPACE> for more, 'q' to quit, or 'h' for help
not MSBIN numbers and were just Byte seek positions for the Message.dat file
but that doesn't fly.... Anyone out there that knows what I'm talking about??
I appreciate any help!!!
 
 
     Garrett Laska...
             Internet: AT595@cleveland.freenet.edu  Cleve, OH
-- 
	
	      
	     Garrett Laska...  
             Internet: AT595@cleveland.freenet.edu  Cleve, OH