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 and the file is
not been imported and processed.
Hmm, I will check with my uplink to see if she had a problem with files
I have
hatched however I must point out that I do NOT split them up as mbse
seems to
have problems dealing with multi rar files if the tic file for the .rar
file is not the lowest number in sequence.
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.
I suspect that the issue is with htick so :
1. Look at the files going into htick including the size and crc data
2. Check what htick is reporting in the log file/s
3. If needed increase the reporting level (full error data etc).
4. Change your processor, mbse handles it fine.
Regardless, the problem is with htick, heck it is very old code.
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.
Having checked with my uplink (Janis) there is no problems with the
files I
have produced with mbse, e.g., the file size matches with the size
given in
the
tic file along with the crc values.
That includes rest of the tic file contents.
I suspect that the issue is with htick so :
1. Look at the files going into htick including the size and crc data
2. Check what htick is reporting in the log file/s
3. If needed increase the reporting level (full error data etc).
4. Change your processor, mbse handles it fine.
Regardless, the problem is with htick, heck it is very old code.
I suspect that the issue is with htick so :
oh sure ? :)
if crc pass then file size is diff ?
1. Look at the files going into htick including the size and crc data
htick does imho not check size in tic files, why should it ?
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.
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.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,041 |
Nodes: | 17 (0 / 17) |
Uptime: | 13:20:39 |
Calls: | 501,715 |
Calls today: | 8 |
Files: | 104,421 |
D/L today: |
6,904 files (2,422M bytes) |
Messages: | 298,470 |
Posted today: | 2 |