It killed my pc at about noon today. I did what someone else did and renamed the program in the WD folder and that fixed it for now.
what is the change that NWS have made?
Not sure if this will help Brian, but this is what they changed for the rss feeds…
Code:
$RSS_URL = “http://www.weather.gov/alerts-beta/wwaatmget.php?x=$Zone”;
to:
Code:
$RSS_URL = “http://alerts.weather.gov/cap/wwaatmget.php?x=$Zone”;
just now need to figure out where they have put the list of counties, etc
Just testing. After michaelb posted the location of the settings, I set the auto updates off. Then using the links
ALITTLEweird1 posted I tried using both links with the …x=ORZ006. (which was what was in the Zone to use key in the registry— NOTE the trailing period/dot on the end!) both links returned “? invalid ugc ‘? ORZ006.’”
I then tried it without the trailing period/dot and it works just fine on either link!
I made the change in the registry, and undid the rename on WDXMLWARNING.exe, and turned it back on.
Been up for about 30 minutes now with no problems…
I kind of seem to remember seeing this movie a long time ago, but then we had to add the trailing period/dot. Maybe NOAA finally got around to fixing the first bug???
NOPE… About an hour after I turned it back on it loaded up one instance of wdxmlwarning.exe and started bogging done my cpu. I let it go for about 10 minutes, then had to turn it off via registry and kill the instance with task manager.
Mmmm. now my Forecast isn’t updating even with a force…
jp
Wonder if build 36 fixed this?
Forecast is working again, I changed the URL to the forecast in WD.
jp
My forecast is fine. However, the warning I am still generating through Interwarn. My only gripe about Interwarn, it is another program running. I had to make some changes in my web page urls, but right now things are working that way. I am confident Windy will fix this.
new version of wdxmlwarning.exe now included in the latest full install
Thanks, Brian. I will give it a shot.
Tony
let me know how it goes
needs testing for a state and county that has an actual warning
some improvements have been made to the program, like the fact the list of county codes has the county name next to it now when you select a state
Hmmm. Something seems amiss. I click the NOAA Warnings in Control Panel and it puts the icon down in the system tray but the configuration box doesn’t open. Each time I click it another copy of WDXMLWARNING starts but the configuration window never opens.
On one attempt I did somehow get the config window to open but when I searched for my area (Colorado) it was only finding the county’s, not the regular warning zones.
T
Same issue here.
fixed that problem
also fixed a major CPU bottleneck with the program
now works much faster and with much less cpu
update
http://www.weather-display.com/downloadfiles/wdxmlwarning.zip
Still seeing the same thing with the zip file - a WDXMLWARNING each time I click the button, it isn’t opening the config window.
Sorry. #-o
T
Same here.
when you click the button in WD
it runs the program, in manual mode
then , click on the wdxmlwarning program icon in the system tray to open it up
(single left click)
to have the program run visible instead of having to make it visible, after manually starting the program from WD (instead of letting it run auto once set to run atuo)
use this update
http://www.weather-display.com/downloadfiles/wdxmlwarning.zip
(these new updates are compiled with the new compiler)
That worked, But my county isnt showing up like it use too. Is that cause of the NWS?