I downloaded the update, installed it, then ran it. It locked up, as the PC stated the update was complete, about 30 seconds. It was still locked up 5 minutes later. I removed batteries, put them back in. It doesnt power up. I pushed the hidden reset button, tried new batteries. Nothing. Is it dead? or is it possible to do a firmware reset...?

Have you tried doing the Firmware update again?
I had no problem updating mine. The firmware took and using the new softwaer, just did an upload of my learned codes.

I was able to reset it. I restarted the update, and got numerous error re: not being to comunicate, but once it started to try and download the update, I reset the unit, and let it sit. It worked, and rebooted.

What was the OS you were useing and the Com port settings? Might be of a good point to let others know, as I had no problems with the updateed Firmware.

Maybe best to revert the Neo and Download the "Default.ncf" first? I'm not sure. I didn't try to upload with the new software first, so I'm not sure of this, but can you Upload first with the new software, before the Firmware update, or, does the Firmware have to happen first, before one can upload?

If the latter is the case, alot of people are going to have to relearn the codes of there devices!

But, if you can upload first, the best to do that!

I actually did a revert before messing with it. So I dont think that is a problem. Admittedly my machine is a bit exotic, but maybe the spces will help anyone with the problem in the future.
Looking at ,y settings, I will try a flow control scheme in the future. These are just the defaults on this install of xp.
Daul PIV 2Ghz Xeon
WinXP Pro
Com1 9600 8-none-1 flow control:none

Well, atleast we know that the Software works with XP,
now I know I don't have to worry about that when I upgrade!

In WinMe I have the Flow Control set to "Xon/Xoff"
the rest is same.

Deepcover,

How did you get your remote working again? I tried performing the update and now the remote is completely dead. A hard reset doesn't have any effect. It's as if there are no batteries in it. When I did the update, the screen froze (like you said) then after a hard reset, I achieved this 'dead' state.

Tech support told me to take it back to the store. How did you get it working again? I'm getting desparate here.

Thanks,
Trynyty

I started the update. 3 times it said it couldnt talk to the remote, and then came up with a retry or cancel screen. I selected retry which brought up the firmware update screen, started it, andpushed the reset button by the batteries, and waited. It took maybe 2.5 to 3 minutes, while nothing showed any response, and the remote rebooted with a beep. The first time I tried this scenario without the remote reset, after clicking the Start update button, it instantly said update finished. I just tried again. Hope this helps...

Thank you, thank you, thank you. That worked. This should be added to the list of bugs and errors that is being compiled in another thread.

[Link: remotecentral.com]

I'll let you do it. You deserve the credit. You saved me from returning yet another remote. There is no telling how many remotes are going to be returned to Philips because of this issue.

Thanks again, now to see if I can download to it,
Derek

OS: Win 95
NCF File: Customized
# of tries before firmware was updated: 4

So I'd say if you get the corrupt flash problem, don't panic...just keep running the update until you get it.

What happens is that the first three attempts wait for a confirmation from the remote. When it is in this seemingly 'dead' state, it does not reply to the packets. After the third attempt, a dialog informs you of the lack of communication and lets you 'retry' anyway. This time, the update does not expect any confirmations. It just sends the update down the wire and hopes for the best. That is why it works on the fourth attempt. This is something that I hope they improve on future flash updates.

-Trynyty