Subj : Mbse co tick + hatch
To   : Vince Coen
From : Gert Andersen
Date : Fri Sep 13 2013 09:59 am

* Reply to message originally in area CarbonArea

Hello Vince!

Thu Sep 12 2013, Vince Coen wrote to Gert Andersen:


>> There seem to be some bad by when mbse is hatch out files or something
>> other release files. When mbse hatch files out look it like that there
>> is some miss or error between .tic files and the file. I have checked
>> it out by hatch a file from my node 2 to my node 1. example is that
>> the files size is 444455 and in the tic have is the line size korrekt
>> with 444455, but when the file and tic is got to my node 1 and my
>> husky htick is trying import the file is the crc error between the
>> file and tic onfo. htick said that the zise of file wrong in the tic
>> file and it should be 00000000

>> The same is happen when I getting files from RJ Clay ad the file is
>> not been imported and processed.


VC>Having checked with my uplink (Janis) there is no problems with the
VC>files I
VC>have produced with mbse, e.g., the file size matches with the size
VC>given in
VC>the
VC>tic file along with the crc values.

VC>That includes rest of the tic file contents.

VC>I suspect that the issue is with htick so :

VC>1. Look at the files going into htick including the size and crc data
VC>2. Check what htick is reporting in the log file/s
VC>3. If needed increase the reporting level (full error data etc).
VC>4. Change your processor, mbse handles it fine.

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.


 Take care,
           Gert

     - Get the best with linux -

--- Msged/LNX 6.2.0 (Linux/2.6.39-gentoo-r1 (x86_64))
* Origin: The KofoBBS at http://www.kofobbs.dk (2:230/150)