Hello Gert!

13 Sep 13 09:59, you wrote to me:

 VC>> Regardless, the problem is with htick, heck it is very old code.

 > I have think a little over it and it can both be mbse and htick by
 > their conversion, like the file is 4806 bytes and i the tic is the
 > same size 4806 and hticks crc said it should be 00000000 so if the
 > mbse tic file read the size of 48060000 instead of 00004806.


You NEED to see what is being processed by htick however, I have NEVER heard 
of
a problem in this arena.

I still say it is related to htick but alnother small point is that is htick 
is
running under DOS or possibly Windows the actual file size could and no doubt
will be larger to match a cluster size which linux / OS-2 does not do.

Regardless the tick processor should NOT be using that size but the one
reported by the tic file along with the o/p from the crc check.

As I said I think it is an issue with htick using a poor API call to get the
file size and possibly along with the platform it is running on.


Vince

--- Linux/Mbse/GoldED+/LNX 1.1.5-b20120229