[C-200] Firmware 03-04-120607-21-POP-408 (Public RC) (6.7.2012)

[minty95]

Since the last firmware update and this beta update (which updated without any problems), Folder Shuffle Play (the only app I use )no longer works, and sadly this app is no longer worked on, Can I go back to before these two firmware updates and re install it, if so where can I get it from ?

I mainly use my C200 for listening to music as I have over 1 000 CD ripped on it (all CDs are mine, no illegal rips ...), thanks

[thEGA]

(07-19-2012 08:22 AM)minty95 Wrote:  Since the last firmware update and this beta update (which updated without any problems), Folder Shuffle Play (the only app I use )no longer works, and sadly this app is no longer worked on, Can I go back to before these two firmware updates and re install it, if so where can I get it from ?

I mainly use my C200 for listening to music as I have over 1 000 CD ripped on it (all CDs are mine, no illegal rips ...), thanks

You will probably need to recover to an earlier firmware.
support.popcornhour.com/article.aspx?id=1089

[accident]

Scroll down the recovery page, there's 2 sets of instructions and you need the second set after the --- to return to the stepstone firmware with the old music player.

[minty95]

Thanks guys I'll try this when I get home tonight

[Ruben Rocha]

call me stupid but what is a public RC?
What does RC stand for?

[accident]

release candidate.. It means it's still beta but might be ready to be released depending on what bugs are found in it. Another way to look at it... these are ready for proper testing.

In this case, it failed the proper testing for a couple problems, although it's a great improvement from the official release. The benefits were enough that when they delayed finishing it, they gave it so those waiting for what was already fixed could get the fixes.

[Ruben Rocha]

Thank you!
I guess I will wait on my c-200 for a official release.

[harnish]

Okay. This release candidate didn't fix the issue I was encountering in 03-04-120517-21-POP-408-000 so how does one file a bug report? Until someone mentions otherwise, I'll just assume pasting here works.

A quick summary of the problem is that it looks like the newest C200 firmware (at least production firmware onward) is only allowing one Network Share per Server NFS Export directory.


After upgrading to 03-04-120517-21-POP-408-000, I encountered a rather minor problem that I made much worse. Originally, this is the problem I had:
I have two nfs mount points home/pub/Video/Unsorted/ and home/pub/Video/Unsorted/Movie Night/
These were two were added to the Popcorn Hour as Unsorted & Movie Night. Movie Night is a YAMJ directory and I'm lazy (I don't want to click on index.html) so it was convenient to have it as another share. Anyway, when I opened Movie Night after upgrading, the links in YAMJ didn't work. After telneting in, I discovered the symlink for "Movie Night" wasn't created and it was still referred to as just share2. Unsorted (aka share1) had it's Unsorted symlink.

So I did a factory reset. I haven't done so after about 5 or so firmware upgrades so I figured it was time and made the problem much, much worse. This time around, I encountered a new problem. After recreating the Network Shares, I opened Unsorted (worked fine), then I tried to open Movie Night and it asked me to authenticate with the SAMBA share "Movie Night". Double checking, I confirmed it was set to type NFS. This obviously should not be happening.

So I upgraded to this RC and did another factory reset and setup the shares again. One of my other shares, which is off the same NFS export, is now encountering the same mistaken for a SAMBA share nonsense, and Movie Night (which specified as home/pub/Video/Unsorted/Movie Night/) opens to home/pub/Video/Unsorted/ instead. However, it only does that if I open Unsorted first (after boot). If I open Movie Night first, it is mistaken as a SAMBA share again until I reboot and select Unsorted. AND, if I use the network browser first and go to NFS export /home/pub, all my shares that link to directories down from that export open to /home/pub/.

All of my NFS shares that the C200 is accessing are off the same export: /home/pub/ so this is a rather annoying bug (especially since it didn't function like this before!)

[gurgenta]

it seems that i have given up to keep this version on my c200 since it`s too baggy to me. i think i should wait for public release..

could someone tell me how to go back to latest firmware version in 2011.

[SS.]

i also encounter those problems on NFS and Samba share after updated to latest firmware, then i try this RC but the problems still no fix.

please teach us how to roll back the old firmware.

[gurgenta]

i searched in the forum. all the ways show us how to recovery the firmware. but its not a recovery process. i just want to load old firmware belongs to 2011.

any solution?

thkns

[Markiee]

Hi,
don't know if this the right place to ask for help.

My C-200 was working fine until yesterday. Yesterdat i have upgraded online to a newer firmware (i think it was may2012).
Although i'm using NFS TCP it started to ask for user/pasw for 'samba server'. Checked this forun and installed the newer 03-04-120607-21-POP-408 (Public RC) (6.7.2012) firmware, hoping this would resolve the issue.
Reset to factory defaults. Configured again shares as before. Still same issue.

Any idea? Something to do with having blanks in map and share name? or with setting up a share to a map within a NAS share?

(NAS is WDC Sharespace, switched in past from NFS to NFS TCP because if problems caused by new D-link router)

[Martien]

I have the same setup and see this message if the WD Sharespace has been off to long (disks are not running) but after a while it works fine, after the disks have waked up.
Did you reboot again after your last settings?
And be sure to use 100 Mb not auto in network settings.

[Markiee]

(07-22-2012 11:57 AM)Martien Wrote:  I have the same setup and see this message if the WD Sharespace has been off to long (disks are not running) but after a while it works fine, after the disks have waked up.
Did you reboot again after your last settings?
And be sure to use 100 Mb not auto in network settings.

Yep, rebooted; even when disk were running same message still appears.

Seems also sharing of "nfs/Public/<map>" does not work. Is the <map> part causing issue since "Public" is the sharename on the NAS (because mapping "DataVolume/Public" seems to work, but further on YAMJ index page does not show??

Now reverted back to firmware of may2011 and everything works fine again.
(but there seems no way to go to a more recent fw version, except to the newest problematic may2012 one)

---

(07-22-2012 03:00 PM)Markiee Wrote:  

(07-22-2012 11:57 AM)Martien Wrote:  I have the same setup and see this message if the WD Sharespace has been off to long (disks are not running) but after a while it works fine, after the disks have waked up.
Did you reboot again after your last settings?
And be sure to use 100 Mb not auto in network settings.

Yep, rebooted; even when disk were running same message still appears.

Seems also sharing of "nfs/Public/<map>" does not work. Is the <map> part causing issue since "Public" is the sharename on the NAS (because mapping "DataVolume/Public" seems to work, but further on YAMJ index page does not show??

Now reverted back to firmware of may2011 and everything works fine again.
(but there seems no way to go to a more recent fw version, except to the newest problematic may2012 one)

Yep, rebooted; even when disk were running same message still appears. 




Seems also sharing of "nfs/Public/-map-" does not work.  Is the -map- part causing issue since "Public" is the sharename on the NAS (because mapping "DataVolume/Public" seems to work, but further on YAMJ index page does not show??




Now reverted back to firmware of may2011 and everything works fine again.
(but there seems no way to go to a more recent fw version, except to the newest problematic may2012 one)

[accident]

(07-22-2012 07:03 AM)gurgenta Wrote:  i searched in the forum. all the ways show us how to recovery the firmware. but its not a recovery process. i just want to load old firmware belongs to 2011.

The 2011 firmware was the online only update, you need to (and want to) do the recovery. It's does a little more than just install the firmware.