I have a 7000 that I'm trying to download a file to - but the dumb remote locks up every time Edit tries to do a download, and I have to reset the remote to get it working again. It even locks up when I try to flash the firmware again. I've tried three different computers and the exact same thing happens with all three. I've had successful downloads before, it just decided to start doing this a few days ago. I have the latest firmware and PPENG from Philips' web site. I've tried all of the hints I could find in the download threads. If I try to keep the remote awake until the download starts, it freezes with the backlight on and stays that way until I reset the remote.

Any ideas? Am I going to have to send this thing in to Philips?

Is this always happening with the same PCF? If so, it may be corrupt. Though, you are having problems with firmware as well.

To go back to original configuration you need to download the default PCF which you can find in the PPENG install directory.

I tried downloading the default and the fancy .PCF in the Samples directory - the remote locks up when I'm trying to download those as well. Sounds like I may just be out of luck. Does pulling the battery pack for a period of time wipe out the programming on the remote?

No, it will not.

I am having the exact same problem as he described. I must have downloaded 50 versions of my PCF file into my unit without incident. Now I made one change and try to download again - nothing. Tried two PCs - "download process has failed" and the 7000 locks up hard.

I can't upload either - same problem.

I fear I am screwed here. Any help is appreciated. The thing worked FINE just a day ago with uploads and downloads, and the remote still works OK with a reset, but communicating with any PC just locks it up.

I fixed my own problem. I had to flash the firmware again. The firmware updater was able to rescue the dead remote, load the initial config, and then I was able to update it again.

I was able to change my PCF redownload it to the remote without problem.

The downside? I had to downgrade my firmware from 3.0.42.3 that it came with to 3.0.42.1 that is the latest available online.

I doubt the changes between 3.0.42.1 and 3.0.42.3 are significant, otherwise Philips would have released an updated firmware by now.

In any case, in case anyone has this problem (caused by a corrupt PCF maybe?) the firmware updater may fix the problem.

A P.S.: I didn't have to do that, apparently (though it was a valid fix). Philips wrote me back and said:

"Dear Sir,

Thank you for your enquiry.

Please try removing the batteries from the pronto, and leaving them out for about 20 minutes. After reinserting the batteries, please reset the pronto, and reconnect it to your computer. After reconnecting the pronto, it may require several minutes to establish a new connection.

Kind regards,

Gerard Feitsma


Philips Pronto European helpdesk

p.s. Please keep this message complete when replying."

I didn't try this, of course, since the firmware reload worked fine for me. But others with newer firmware might want to try this suggestion from Philips first.

-P

I have had all kind of download problems and upload problems. I have taken the batteries out, rebooted, reset the pronto, reflashed the firmware repeatedly, etc. etc. I have gone back two versions on my pcf now, and have no way of trouble shooting the current pcf.

I believe the problem started trying to convert ccfs to pcfs and getting bmps and not pngs. I have converted all of the bmps to pngs and the buttons are significantly more responsive for some reason.

But now it seems I have hit the wall. I do not know which page is corruped, etc. Short of restarting from the current page, I will probably back up 10-15 hours of work but ultimately run into this again.

If anyone has any idea how to trouble shoot a pcf file, it would be most helpful. The files run fine on the simulator.

Earlier Prontos had problems with IR codes that had not been assigned a non-empty name.

Have you done alot of learning lately? Renamed IR codes?
If you would like me to take a look...

If you would be so kind as to open your current PCF as a Zip file, extract the ConfigEdit.xml file, zip it, and email it to me, I'll have a quick look.

Thanks,
Lyndel

Lyndel, blank names could be the cause of the problem that some people have had with migrated CCFs.

Peter,

Agreed. I have not tested how PPENG or the remote handles this....

Lyndel