| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | .tics from HTick |
ml>> it must be noted that there is a distinct difference ml>> between having CTRL-Z characters in the FILE_ID.DIZ ml>> and in the .TIC file... yes, same character, but ml>> different processing... it is likely that in your case, ml>> the CTRL-Z in the FILE_ID.DIZ is being taken care of by ml>> your filter... as to why you're not seeing the same ml>> problems that were described, that may be because ml>> someone downstream of you is correcting the problem ml>> unbeknownst to you... FR> No, they were in the .tic, and I was seeing the same problem FR> that's been reported (all the TICs were thrown into bad, FR> because ALLFIX stopped parsing after it hit the Ctrl-Z). FR> Research indicated the Ctrl-Z *originated* in the FR> FILE_ID.DIZ which is, I assume, where HTick picked it up and FR> inserted it into the TIC. ahhh, that explains the apparent confusion in terms... i knew that you had been talking about the FILE_ID.DIZ while the other discussion was about the TIC... even if the FILE_ID.DIZ does contain the CTRL-Z character, it is possible that soneone upstream from you can filter and correct a bad TIC file and still leave the FILE_ID.DIZ alone... that's what i was trying to say above... hummm, i note that i also used downstream rather than upstream, too > )\/(ark* Origin: (1:3634/12) SEEN-BY: 633/267 270 @PATH: 3634/12 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.