Everyone and anyone,
I spent the last week working on a new ProntoPro configuration file for my HT in anticipation of purchasing the Pro (already own the 1000). I had invested nearly 24 hours of programming time when it happened. Although I had periodically saved the file while ProEdit was open, I had not created a copy of it yet. I closed the open session and then remembered I wanted to delete an empty panel before I made that copy. I tried to open the CCF again and was presented with "Not a Valid Pronto Configuration" !!!
I did nothing strange and I had previously closed and opened the same CCF many times. This SCREW UP has made me extremely angry because of the intense time I had spent on it.
Now my plea: Is there anyone out there who can suggest anything I might try? I am willing to email the CCF to anyone who thinks they could recover it. Particulars are as follows:
PC - Dell P800 - Win2000 - no other serial devices connected.
HEEEELLLPPP!

David Mayo

This is a beta release!

I posted a message last week reporting various ways to corrupt a pro CCF. One way is to program the two new buttons, then set the CCF to be write protected. However, I was able to remove the button actions and it was OK again.

Send me your corrupt CCF and I'll try and find out where it is corrupted.

Peter,

Tried several times to email you the CCF but came back "undeliverable". Please recheck your email address that is listed here.

If it is a problem on my side, maybe you could email me once and I can reply with the attachment.

Thanks again.

David

For some reason, the email on my previous post was wrong. This one should be right.

The address for the action list on the new far right button under system properties was corrupted.

This could be similar to the error I encountered when I set read only properties which resulted in my action list being corrupted.

David, I have fixed it and sent it back to you.

Just be careful to take a copy whenever you make changes.

Peter

Peter,

I have thanked you via email. However, publicly I would like to say to all that you are a kind, helpful person. The speed with which you fixed my CCF and the emails that kept me informed all attest to this. Once again, thank you for your efforts.

David

I'm all embarrassed!!

Actually, that was the firts time I changed a CCF. When I found what was wrong, I downloaded a copy of HexEdit and was able to zap the offending bytes. It was agood elarning experience from me.

Daniel, the three times I have seen corruption in a Pro CCF, it has been related to using the new Far left and right button action lists. The bytes where these are stored used to be used by other functions (such as attributes), and I suspect there is some code that still uses the old offsets, thus corrupting the action lists. By the way, is there a proper name for these new buttons?

Murphey decided to pay me a visit after Friday's news update -- that night I had a CCF corrupted. Lost an hour or so worth of work. When trying to fix the file I managed to corrupt it AGAIN. I was unable to do it a third time with the exact same changes.

1) I think this is happening after your system/ProntoProEdit has been running for a while and it's running out of resources. On the day this happened I had been working all day and my system resources were low. In addition, the panel-zoom option had stopped working (something that happens now and again with even plain ol ProntoEdit). I didn't bother to reboot when this first happened, so I made about 10 changes, saved the file, and bingo -- corrupt again. So I rebooted, made the changes, and the file was fine. I have no hex codes in my file -- just delays.

2) There seems to be a problem with storing functions on the far right hard button. Numerous times the delay I added has been mysteriously dropped. Numerous times TWO delays have been dropped down to one or zero. Many times a sucessfully added delay will show correctly, but the emulator will still default to the "scroll" function. This only seems to happen (with me) on the far right hard button -- the other three have been problem free.

David's problem was the far right button as well. I found if I set some device attributes it wiped out some of my far right actions.

It wiped 'em out here without requiring anything else -- they just disappear.

Must be the "missing sock in the dryer" syndrome.