Yahoo Groups archive

Disklavier

Index last updated: 2026-04-28 23:20 UTC

Message

Re: download files :- ecompetition 2004

2004-09-19 by bin_kuei

Hi all, 

It is quite amazing that we need to struggle with 20Mb when each 
yahoo e-mail account sports 100Mb and Google has a 1,000Mb e-mail 
account under testing.  Is it possible for the list owners to 
petition to Yahoo?  Because it is such a shame that we have to work 
with such a small space.  Is the 2004 e-Competition files posted 
anywhere else? Does anybody know?  Thanks.

Best regards,
Bin


--- In disklavier@yahoogroups.com, "Danny" <simpsond@u...> wrote:
> From: "smcilwain2003" <smcilwain2003@y...>
> 
> > Can anyone help with this? In the download files section, :- the
> > folder for the ecompetition download files for 2004 doesn't 
contain
> > the music files at all, but just another copy of the .xml list? Is
> > it meant to be like that? Just got a bit confused and wondered if 
I
> > was doing something wrong? Thanks.
> 
> 
> Hi,
> 
> MIDI Magic was kind enough to post the Excel spreadsheet of the 
pieces played in 
> the 2004 competion a couple of months back. It would be nice to 
again use the 
> area to store the 2004 competition files as was done for the 2002 
competition.
> 
> Trouble is, we are currently totally out of space that Yahoo allows 
our group to 
> use to store files. Yahoo provides free user lists and limited 
storage space for 
> thousands of different user groups. They only allow a bit over 20MB 
of free 
> storage space for each user group list.
> 
> We were able to free up 4 or 5MB storage space several months back 
by clearing 
> out some older and copyrighted material that wasn't supposed to be 
there in the 
> first place. We could go thru that exercise again, but I don't 
believe we could 
> free up enough storage space to be able to place the 2004 
peformance files in 
> there at present...
> 
> 
> Danny

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.