ppc engine dowload problems

Glasgow, David David.Glasgow at cstone-tr.nwest.nhs.uk
Thu Jan 2 08:51:01 EST 2003


Thanks for the advice .
 
So far, I have sold *4* copies of v1.0, which was written in Visual Basic.  Version 2.0 is RR, and therefore cross platform.   Any Mac sales PPC or 68k are therefore entirely theoretical, and possibly non-existent.  I was just mulling over how to distribute it - whether to continue to use floppies or invest in in a CD burner and stick everything on the same disk.

(4 copies might not sound like much, but for the past 10 years my partner insisted she put up with my software development as a harmless but ultimately pointless hobby.  Ha!  ) 

As to the download, I tried several times, same result.  I am going to have another go in  a minute.

Best wishes,

David Glasgow

Courses HTTP://www.i-Psych.co.uk 




 >Subject: Re: ppc engine dowload problems
 >From: Richard Gaskin <ambassador at fourthworld.com>
 >To: <use-revolution at lists.runrev.com>
 >Reply-To: use-revolution at lists.runrev.com
 >
 >DVGlasgow at aol.com wrote:
 >
 >> I was wondering if a ppc only build would be much smaller 
 >than a 'fat' build.
 >
 >Yes, by nearly half.  This is true of all "fat" applications, 
 >since they
 >efectively contain two complete sets of object code (one for 
 >68k and one for
 >PPC).
 >
 >But as time goes by, I'm delivering to fewer and fewer 68k 
 >systems.  Aside
 >from some public schools and a handful of other specialized 
 >cases, it seems
 >few people who haven't upgraded machines in over 7 years also 
 >have the RAM
 >and other system resources to make effective use of the stuff 
 >I've been
 >building.
 >
 >What percentage of your audience requires 68k?
 >
 > 
 >> I selected ppc in the build distribution stack, and was 
 >duly invited to
 >> download the engine.  After a few seconds a dialog advised 
 >"there was an
 >> error trying to  decompress the engine. The file appears to 
 >be corrupt.".
 >> Anyone else get this?
 >
 >Such things are often transmission errors, worth retrying.
 >
 >-- 
 > Richard Gaskin 
 



More information about the use-livecode mailing list