Recent Posts

Yes, that's why I added the Donate button. If you mean something more mandatory like a licensing scheme then I disagree, it would require time to set it up, cost more than the 15$ a sale would bring, and means the program would no longer be free for those who can't afford it.

Mike, thanks for the info. Your assessment makes sense, since even the outside PC I tried to install Winpodder on had already installed the latest Windopes updates. Too bad you couldn't determine which Windopes update caused Winpodder to crash. If it's not a critical update, I could uninstall it to let Winpodder work.

Have you given any thoughts to maintaining Winpodder and then charging a small fee for us that want to use it (say, a one time fee of $15.00)?

I'm testing a post.

Spend some more hours testing and was finally able to reproduce the problem, must be caused by a Windows upgrade. As you know WinPodder is a free program that I wrote as a service to the podcasting community. I am currently very busy with other projects, most notably VidBlaster, so don't have time to work on WinPodder. At the same time I don't want to deprive you of the program. So I've added a Donate button to the Download page. I will use any donations to continue my work on WinPodder at cost price.

There's nothing in WinPodder that expires or something like that, so you'll have to look for an external source. Maybe you both share a program that updated recently, and is now interfering with WinPodder, an image restore may not always fix that. Another theory is you always start with trying a certain podcast, one that somehow upsets WinPodder?

It's working fine here. I did a clean install (remember to always uninstall properly) and clicked Catholic Insider and it plays fine.

I am receving the same access violation message. Winpodder has worked well until today. Any podcast I try to download gives me the same error message. I am running XP SP3. Any help would be appreciated.

The original symptoms indicated this was a hardware problem, but further testing suggests it's a problem with Winpodder itself. I went to a PC that's off my premises, downloaded Winpodder, installed it, and got the EXACT same Access Violation problem on that PC. Winpodder was working just fine on Saturday, September 5th, but crapped out on Monday, September 7th, and has not worked since.

Sorry, I just plain forgot about this post. I finally got it to work.

Exact message is Access violation at address 004044DD in module WinPodder.exe. Read of address 00000364.
Winpodder was working OK on Sept. 5th, but when I tried to use it on Sept. 7th, this notice started popping up. This same notice occurs no matter what OS I'm using (XP Home, Vista, and Win7). I did do an image restore back to a date that I know for sure Winpodder was working, but still am getting this notice. I did pull my memory modules and tested them, but that didn't fix the problem. I also cleaned the Registry using Crap Cleaner and Glary, but I already knew that was a waste of time because the restore would have fixed any Registry problems. This appears to be a hardware problem, since it's occurring across all OS platforms, but I wanted to post it just in case someone has run into this problem in the past.

THX