Author Topic: Ongoing Issue with PDW  (Read 11093 times)

crodgers3092

  • Member
  • *
  • Posts: 2
    • View Profile
Ongoing Issue with PDW
« on: 09 Sep 2014, 09:26:28 »
I have an ongoing issue with PDW where it stops working after a few days of decoding. I receive my pages through a discriminator tap and it goes through the computers sound card. I'm receiving 100% on average up to 3 days. On that 3rd day or which ever day it is, the program just stops decoding any messages from that point on. It is not until I close and reopen the PDW program that it will decode properly again. When I do that it goes back to decoding 100% until 3 or so days goes by and it does it again.

Any clues, ideas, solutions? I assume it's a setting on my computer that I should fix.

Thanks

VidarParry

  • Top Member
  • ***
  • Posts: 126
    • View Profile
Re: Ongoing Issue with PDW
« Reply #1 on: 10 Sep 2014, 07:35:13 »
Hi,
I found that my XP machine also randomly stopped after a day or so. I worked around it by scheduling an automatic restart at 1am every day.
Cheers
...Steve

crodgers3092

  • Member
  • *
  • Posts: 2
    • View Profile
Re: Ongoing Issue with PDW
« Reply #2 on: 11 Sep 2014, 02:36:18 »
I'll give that a shot. Thank You

fmr

  • Member
  • *
  • Posts: 2
    • View Profile
Re: Ongoing Issue with PDW
« Reply #3 on: 25 Dec 2014, 22:00:13 »
Same issue here... Has anybody found a solution yet?

Thanks

gfdfortynine

  • Member
  • *
  • Posts: 9
    • View Profile
Re: Ongoing Issue with PDW
« Reply #4 on: 31 Dec 2014, 23:17:26 »
I restart mine weekly due to same issues. I assume some buffer or something like that fills up and causes it to stop decoding.

dudies69

  • Member
  • *
  • Posts: 7
    • View Profile
Re: Ongoing Issue with PDW
« Reply #5 on: 16 Mar 2015, 22:06:05 »
You can setup windows to do an automatic scheduled restart but you must make sure you have windows setup to automatically restart PDW as well.

fmr

  • Member
  • *
  • Posts: 2
    • View Profile
Re: Ongoing Issue with PDW
« Reply #6 on: 18 Jun 2015, 21:26:56 »
Does the "buffer overrun"-bugfix from v 3.12 help?