Hi,

On 2015-02-14 09:33:58, Nicholas Boel wrote to All:
  about: "htick":

 NB> The latest I-BINKD.TXT that was hatched out seemed to have a typo in
 NB> it:

 NB> Replaces I-BINKD,TXT (with a command rather than a period).

"command" ? ;)

 NB> It seems as though htick systems just kept processing it down the line
 NB> (with the typo still in every .tic) until it got to a non-Husky system that
 NB> finally errored on it, and renamed the .tic to .bad.

If both the filename, and the .tic file contained the comma, it's not a htick issue.

It's a bit odd, but a comma is a valid character in a filename both on
windows and linux. So if both the .tic and the filename contained the
comma, what htick did was the only thing it should do...

 NB> What I would like to know is if there is a "normal" way to handle
 NB> this? Does htick skip the typo, which in turn would *not* use that
 NB> "replaces" command, and continue processing it
successfully and pass
 NB> it on to downlinks with the same typo in the .tic? This seems to be
 NB> what occurred, and that doesn't seem like a good idea, IMO.

This depends on my remark above...

Bye, Wilfred.


--- FMail-W32-1.69.1.95-B20140716