[200] [CSI] Community Software Installer 2.7.2 ** UPDATED DEC 28th 2011 **

[Ger Teunis]

(09-14-2009 08:42 PM)dc11ab Wrote:  Ger,

I encountered the same or very similar issue as lundman, but the rm -rf of the ~/.local/share/Ger\ Teunis/ did the trick and I successfully installed CSI Gaya on my C-200! CSI over Mono (same version as you, but I have Mac OSX 10.5.8) is quite unstable on my Mac though, I must mind the steps and clicks I do or see the psychedelic rolling umbrella for eternity. (Mac joke, sorry).


On another note, (possible bug?) on CSI Gaya on C-200:
Changing between the "tabs" Apps-Themes-Menus-Wait Images-etc. goes into a loop that time-out and we are still on the same tab. But if pressing another tab, for instance "Installed" when on the Apps tab, and then press Stop on remote control - then it takes me to the Installed tab OK.

Hope that explanation makes sense.


The log from when I got the pop up error message saying something about not being able to download (even though the CSI Gaya tar clearly was downloaded):

Thanks for testing Daniel.
CSI has some stability issues on OSX's mono for some people.
As usual it's hard to reproduce here; but I might have an idea. Perhaps someday I'll add an additional Mono workaround.

Regarding CSI Gaya> yeah I saw that as well. It's weird because when I open CSI Gaya in my browser it is really really fast. I think there is an issue with the NMT's browser. I'll need to investigate further.

Your "download error" is one more mono issue, it is trying to download a support file but your configuration got corrupted again.
I'm thinking about creating an own configuration class and not to use the .net one anymore. Perhaps that will work better for Linux / OSX users.

---

(09-14-2009 08:51 PM)halfelite Wrote:  Will installed apps survive a reboot now? Also what happens when you stick in another drive? I noticed last night I had a 2.5" drive installed with nmt apps on. and it was called sata_disk. I put in a 3.5" for a test and kept the 2.5" also in and the 2.5" became sata_disk1. while the 3.5" took for the name sata_disk. Will this have any effects. Im not home right now to test.

It will survive reboots now.
The disks needs to be 'mounted' as SATA_DISK, I do not know what problems you might get if it doesn't. I always use the symbolic link of nmt itself (/share -> /opt/localhost.drives/SATA_DISK) so in theory changing the disk and have it correctly setup should work fine.