| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Hello I have a customer who has ALL-IN-1 V3.0 and a problem when printing/ reading mail messages. The customer has customised their system. They altered their MAILMEMO boiler plates and had problems. These problems disappeared when they removed another application from the CMTXL. When it was readded the problem came back. The application has nothing in common with the mail subsystem, so the customer says. The problem is that when printing/reading a mail there is a blank line before the bolierplate starts, that has spurious characters on it. The characters change on each new CMTXL, the CMTXL that he sent me, has the line just containing the letter 'a'. The customer is worried that such a problem can occur when the apparent cause is simply from some unassociated customisations being in the tixel. Is there a problem with the TXL compiler? Unfortunately he has deleted the product of their system as it was very old and not needed and he does not have another copy. However he does have a copy of the TXL when the spurious 'a' was appearing. I tried installing his tixel here and reproduced the problem. A copy of it is on: WAYOUT::CMTXL.TXL_PENNY Does this TXL hold any clues as to what was going on? Regards, Richard Simpson.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3880.4 | Could it be .IFs?? | AIMTEC::WICKS_A | Atlanta's Most (In)famous Welshman | Wed Feb 23 1994 07:58 | 14 |
Richard,
fwiw - we have seen a number of corrupt TXLs in recent weeks so there
must be something afoot in v3.0. all the calls are either still open
or SPrs have been raised but the only common thread appeared to be
complex .IF statements in use in the affected elements.
Not much to go on I realise but we have lots of MUP/TLC calls to
preoccupy our every waking (and sleeping) hour so I don't have time
to see if your trace is the same problem.
regards,
andrew.D.wicks
| |||||