<div class="gmail_quote">On Wed, Jul 29, 2009 at 9:54 PM, Walter Bender <span dir="ltr"><<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div><div></div><div class="h5">On Wed, Jul 29, 2009 at 7:55 AM, Bill Kerr<<a href="mailto:billkerr@gmail.com">billkerr@gmail.com</a>> wrote:<br> > On Wed, Jul 29, 2009 at 10:10 AM, Caroline Meeks<br> > <<a href="mailto:caroline@solutiongrove.com">caroline@solutiongrove.com</a>> wrote:</div></div></blockquote><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div><div class="h5">> 1) once I have created a stick can I upgrade just one program, such as the<br> > version of Physics which saves (if so how?), or do I have to wait until that<br> > version is officially released and then reformat all the sticks - I suppose<br> > both are time consuming since I have about 20 sticks to do - but the latter<br> > involves waiting for the official release<br> <br> </div></div>You can update individual activities from <a href="http://activities.sugarlabs.org" target="_blank">activities.sugarlabs.org</a>.<br> You can add new activities from the same site. One caveat: a handful<br> of activities are installed with .rpm instead of .xo. These cannot be<br> updated on the fly without jumping through several hoops. This will<br> change on the next release of SoaS. (See<br> <a href="http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap#Fructose_modules_.28F11.29" target="_blank">http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap#Fructose_modules_.28F11.29</a>).</blockquote><div><br></div> <div><br></div><div>the immediate issue is about updating physics - from reading gary's earlier comments physics2, which is the version currently available in activities, does not save - confirmed a few times now with our strawberry sticks</div> <div><br></div><div>best option might be to wait for official release of physics3 to activities, I probably will do that unless there is a reasonable quick update alternative</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im"> > 2)<br> > <a href="http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Strawberry#Windows_Users" target="_blank">http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Strawberry#Windows_Users</a><br> > For Window User point 5<br> ><br> > "Set the Persistent Storage slider to the maximum so you can save your Sugar<br> > work onto the USB device;<br> > (You may allocate as much storage as there is capacity on your device. You<br> > may allocate less than the maximum, if you want to use some of the device<br> > storage when not booting Sugar.)"<br> ><br> > I ended up setting the Persistent Storage to maximum. Now I'm wondering that<br> > if I had allocated less than the maximum then could a student copy a file<br> > from the journal onto the SoaS (rather than their own USB) and it would save<br> > in some of that non allocated storage. This is an issue because not all<br> > students bring their own USBs to class. Sometimes there is a need to swap in<br> > and out of the Sugar environment back to the Windows environment (found in<br> > most schools) so ability to easily save on a USB is an issue. Actually, this<br> > ended up being the first major thing I taught my students to do.<br> <br> </div>As far as I know, this should work, but I haven't tested it. That<br> said, in the long-term roadmap, we want the journal files more readily<br> accessible from outside of Sugar. (They are in a "squash" filesystem<br> right now, not easy to access.)</blockquote><div><br></div><div>I like the sound of making the journal files more readily accessible from outside sugar in the future - very desirable for teachers swapping back and forward from the dominant Windows school environments</div> <div><br></div><div>I just tried my suggestion above and could <b>**not**</b> save a test file onto the spare SoaS storage - pity</div><div><br></div><div><br></div><div> > 3) the information about failed sticks not rebooting is valuable - some</div> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"> > sticks have failed for me but I haven't worked out any real pattern yet,<br> > quite complex to keep track when teaching a class, just tell the kids to try<br> > a different stick and / or different computer - but the sticks are numbered<br> > and now each student uses the same one each lesson so patterns will become<br> > clearer soon<br> <br> </div>Failed sticks often get a second life, which also complicates things.</blockquote><div><br></div><div>We have been going for a couple of weeks now and failed sticks have not been a problem</div><div><br></div><div> A couple of times the screens have frozen - but only a couple of times - so at this stage it's pretty reliable</div><div><br></div><div>Rebooting has worked so far when screens freeze</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im">> 4) some of my sticks (about half) are card readers 2GB cards, they work fine<br> > 5) the brand of stick of stick makes a difference, LASERS are very slow (and<br> > cheapest), KINGSTON seem good<br> > 6) collaboration did not work out of the box - is it meant to? - I have a<br> > jabber server from last year which I have yet to setup but will do so soon<br> <br> </div>It should have worked. Is Internet access working out of the box?</blockquote><div><br></div><div>Collaboration without a jabber server did not work</div><div><br></div><div>I spoke to joel about this and he put forward the idea that proxy servers are used differently in Australia to USA and that perhaps the USA experience of collaboration working is because the jabber server there is not being blocked - the jabber server port is blocked in oz schools</div> <div>(adding joel to cc list)</div><div><br></div><div>cheers</div></div>