The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: RE: Does the world.....


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: receiver.arf file



All

 

I've been running that patch since yesterday.  It has the webserver and line-out hack so I presume it's the same patch as you all are using from http://empeg.dyndns.org/receiver/Feb_2002/.  My receiver.arf file is only 3.85Mb

 

Hope this helps those who are confused about there merged files being smaller than Stuarts 6.85..

 

Pedro

 

-----Original Message-----
From: Stuart Whyte [mailto:lists@xxxxxxx]
Sent:
09 February 2002 19:41
To: ukha_d@xxxxxxx Subject: RE: [ukha_d] receiver.arf file

 

Brian ,

 
 > Was I meant to have known how to do that? the last update I downloaded I
just renamed it and jobs a good un! or perhaps it was not an update...thanks
again...
 

The was a readme file on the same page as the patch download.

 
 > BUT it still don't work! it did try once and produced a grey rectangle but
only once!

 > Ho hum, Stuart why is your file so big? mine is only(!) 4 megs(ish) does
 > this contain all the track info? I have a dat file which is 18MB so I
 > thought the tracks were stored there? 

 

My original .arf file was about 4MB (3.85 to be exact), once merged with the patch, that makes it 6.85.  

thanks for letting me (us) for doing
  so. 
 

 

NP.  Glad to help

 

B.

 



Yahoo! Groups Sponsor
ADVERTISEMENT

For more information: http://www..automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.