kenpreno, While I certainly would not say to NOT contact Panasonic about this problem, truthfully I cant say that I think anything will be done about it.
If you contact them I would think you will get the same runaround that both myself and Digado got. The person who you talk to may plead that they "have never heard of this problem". They will have you power cycle the machine, they will have you download, or send you out a firmware update disc, etc. etc.
If you do as I did, and probably Digado did, spend 10's of hours trying to figure it out, and in my case I found a workaround which, for me, works 100% of the time. Granted powering up/down the machine at least once every morning is going to sound ridiculous to some, it does work.
I even have 2 events that if you program them, and they should work(worked on all my other Panny's)they will fail every time. For the life of me, I could not get Panasonic to try my test
At that point I kind of gave up on trying to get it corrected by Panasonic, and tried spreading the word on forums like this one. I figured if Panasonic was not going to fix it, at least people in the know would have workarounds.
What really put me over the edge with the whole timer bug thing was what Digado said. He said apparently Panasonic has had a similar timer bug on a previous generation DVDR. Two before the EZ series. Apparently they never even fixed that generations bugs!
Like I said, I don't really know what personally you should do. To me, the PQ of the Panny's make the bug (which I have found a workaround for) ok to live with. Would I like it fixed, FOR SURE, but I guess the WS and PQ make it worth keeping the EZ-17.
P.S. not sure if there's still time to return your Panny, but if you like the PQ of the Philips 3575, $299 Walmart. It has no bugs I've found. It has a HDD which is very handy, but as noted it's probably ~$100 more than the Panny. I hate to turn you away from Panny's, I have liked mine of the past, but if you don't like screwing around, and want to be able to program in something and actually have it work, I guess I might look to other brands.
Note as Digado noted, and I have as well, if you just don't use DAILY or WEEKLY events, I don't think you will experience this bug. Again I don't know everything about this bug, but that's what I have found. Maybe that's an acceptable workaround for you?