BJ> Ok....  Wes mentioned in a private e-mail to look at a _packed_ , or
 BJ> some other directive that forces a packed structure that then can be
 BJ> read and written out to disk.....  The structure used for the reading
 BJ> and writing of QWK packets probably needs this directive added to it,
 BJ> and appropriate padding added if needed.....  I'll have to switch to
 BJ> the machine my e-mail is on to look this up (if needed).

 BS> The problem is that the entries in the .NDX file isn't 
 BS> sepperated correctly.

Sounds like it could be solved with the info Wes passed on to me....  Let me dig....

Hmmmm.....  Ok, from an e-mail I got from Wes:

=== cut here ===
6. If he is declaring his own structures for reading squish 
bases, you might find this syntax helpful:

struct _mystruct
{
  int field;
} __attribute__((packed));


.that should give the same structure size as Scott was using on 
the DOS-based compilers. Of course, __attribute__((a)) gets 
#defined to spaces on non-__GNUC__ platforms..
=== cut here ===

So, I would recommend checking to see if the structure you are using has
the __attribute__((packed)); statement included.  If it does, then we had
some padding under DOS / OS/2 / Win32 environment that wasn't clean in the
old code.  If the attribute isn't there, then I'd try adding it for the
structure being read and/or written in binary format to the qwk file.... 
Since I haven't looked at the specific code you're dealing with, this may
not be the issue with the qwk code....

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01