Disagree, at least for the columns "new added..." (or something, my interface is in Dutch).

Tommy, Andy, as i've stated in my previous post: indexing in the new firmware works with my config.
My newest files are showing up on the home-screen

Maybe Tommy means to use those exact names to let the files show up when you select one of the three first menu-options?

@Eddydibbink yes, using those 3 folders makes the 3 first menu options show the files, but doesn't the playon also look in those folders for the indexing?

Well, i would guess so Also a few steps less to the files
I'm gonna try *starts putty*

I'm unable to successfully mount at the start-up. The script does run and the mount command executes w/o errors (i put some echo's in the script) however the actual Samba shares are not mapped.

When I execute autorun manually after the box is started, everything mounts fine...

Any suggestions?

Did you chmod the automount file? See opening-post.

Well this seems to work. The mini is indexing all the mounted folders
I'm waiting untill it reaches my MP3-folders
So far so good

I removed the link to my MP3 folders, takes too long and i use the mini for videos only so no use in that, i'm planning on linking the movies menu item to my "new content" share so i'm 1 click away from watching my latest "video backups"

Thanks I'll give it a go
I did get it working using different code - at least the exact folder names were there and I could see the content from the command prompt - just no files visible in the GUI

Glad to hear that this is working for some people, unfortunately it's still not happening for me.
I have tried mounting to the Videos, Pictures and Music folders as suggested but still the Scanning/Index (can't remember the exact wording) C: message pops up for about 10 secs and then disappears.
As before, there is no problem with the mounts at all as I can access the shares via the USB mounts via Files Manager it just seems that the indexer has no interest at all!

Anybody, got any other ideas or even where the logs for the indexing task might be so I can try and get some idea of why this isn't working?

Cheers,

Rick

Yep the permissions are all good, as I mentioned before the automount script does run.

Turned out I was redirecting stderr into a wrong file so was not getting the errors. Now I can see that the mount returns error 128 when it is executed during the start-up.

Tried to google mount.cifs error codes but can't find any good reference. Some inderect reference (Solaris - http://opensolaris.org/jive/thread.jspa?threadID=123658) seems to relate to network broadcast issues, which leads me to a theory that this could have something to do with my wireless dongle not being ready at the time the scripts runs.

Any thoughts or suggestions would be really appreciated!