Hmm i experienced that the fw reacted a bit faster then 3582. , not perfect yet but faster.

I will report the zoom bug thnx for reporting

Drive mapping in windows still inconsistent (as per r3582).
As in playon powered down, power up and map hdd in windows in on path:
\\<IP of playon>\hdd1
Now playon into standy wait a few seconds and out of standby this drive mapping no longer works it's now
\\<IP of playon>\hdd2

Only way to get back to the normal mapping of \\<IP of playon>\hdd1 is power down completely (remove power) or plug-in to make the playon a usb drive and remove.
All previous firmwares stayed on the \\<IP of playon>\hdd1 mapping all the time.

Also may I ask why where the time settings removed? (yes I know they are posted as removed on purpose but it was a very useful feature)

Strange i did not exerpience problems with the drive mappings ?
i use a driveletter mapping in windows wich works fine and i can acces the hdd on the http:\\ adress ?

Maybe the hdd goes in sleep mode ???????????
Wich hdd is in the unit ?

hdd is irrelevent and not important to the issue any drive in the unit behaves the same way, and how can sleep mode possibly be affecting it?! The unit is simply powered on, and drive is there operation ready it's just the playon has decided to change it's internal drive mapping.

Yes you map a drive letter to a path, it's basic windows networking.
If you don't know how to do this, simply open up 'windows explorer' and select 'computer' your existing drives are displayed. Then (in vista at any rate) at the top select 'map network drive' and then put in drive letter and path to map, press ok and it's a drive attached to your pc.

You also never answered my question on the time issue.

I never mentioned http access, it's of no interest to me as I don't want to access it that way.
I simply want the unit to work properly how it did on all SDK 2.0 firmware builds.

sorry did read it incorrect.

You mean you have a mapping in windows to the pohd.

When the pohd goes on the mapping works fine.

When you out the pohd in standby mode (red light) and put it back on (Blue light) the mapping does not work.

Also i dont have this problem.

But i do know when the fw for whatever reason is not correct flashed, (Maybe download was not going well bad block in img file) The nas/samba module can be corrupted.

Try to reflash again and see if the problem still is present.

I will try to reproduce this.

To be continued.....

@Kraakie, please add this to the known bug list... It's mentioned a couple of times in the previous thread, but never mentioned as 'known error'.

Please can someone tell me about BTPD it is now stopping automaticly

Reflashing makes no difference, tried both normal and safe. As I have said this behaviour is the same on SDK 3.0, but on the SDK 2.0 firmwares (r2901 was the last I used for a long time) the mapping is conistent. So it's something that has been broken in the way it's been done for SDK 3.0

Update - flashed to r4318 and once again the playon is working correctly so my conclusion on SDK 3.0 has broken how samba advertises the internal drive seeems correct.
Flash back to r4090 again and it's busted.

Noticed the installation file "install.img" from both packages (Asian & European) are dated 9/17/2010. I wonder if this is the same version used for internal testing?! Does it mean that no changes/fixes made at all from the internal testers' feedback?

You can turn it off seperatly in the system menu