[EAS] EAS Digest, Vol 15, Issue 19

[Tom Spencer]

Er. would the legacy box following such a transferred location code even 
see an EAN with location code "000000", regardless of source?  If so (if 
the EAN will actually trigger regardless of location code), then what's 
all the shouting about?  It was my understanding that unless the EAS 
header contained the location code(s) enabled in the box, the box would 
ignore the alert.  If that's not the case, then there would be no need 
for the EAN to carry any location code at all... and the header could be 
filled with an ASCII space (CHR(32)) or something and still get the SAME 
(pun) results.

The second objection has more merit, though.  But at least my proposal 
is a start...

Harold Price wrote:

> Tom,
>
> Good thought, but it won't work. 

> The legacy box would see two different EANs, one from the converter 
> box, and one  or more over the air versions.  

> A further problem is if anyone is monitoring the converter/legacy 
> pair - they will also see the modified alert and could air more than one EAN.

-- 
Tom Spencer