TIP: Click on subject to list as thread! ANSI
echo: meadow
to: JAN MURPHY
from: FAUSTO CARVALHO
date: 1996-08-29 08:45:00
subject: Re: checking your Opuses

 Hi Jan 
 
 > JM: OPUS     EXE    251824 10-06-91   1:38p 
       OPUS     EXE    251824 10-06-91   1:38p 
 
 Mine has exactly the same date and size. And it matches the one I  
 have in the distribution Zip - just checked :-) 
 
 > JM:  1) your unpacker screws up 
 > JM:  2) somebody else unpacked the archive and repacked it, and their 
 > JM:     packer screwed up 
 > JM:  3) damage 
 > JM:  4) sabotage 
 > JM: How likely are any of these possibilites?  No. 3 I would expect 
 > JM: a lot, the others seem not very likely. 
 
 I definitely remember a situation where my OPUS.EXE started to behave 
 erractly and it was clearly n.3 - although I can't guarentee you that 
 file size/date changed. In fact I'd say it didn't, although contents 
 had been "contaminated". 
 BTW, that was caused by Squish 1.0, who had the bad habit to go on his 
 own along my hard drive now and then... Can't complain - it is not 
 certified to go along with Opus :-) 
 Anyway, with versions 1.10/1.11 never happened again. 
   -FC- 
--- Opus-CBCS 1.73a
---------------
* Origin: Midi-Thru +351-34-313554 Aveiro Portugal (2:361/1.0)

SOURCE: echomail via exec-pc

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™.