The Weather Forecasting Forum

You said you're using DAWS 1.0i, so I guess the first step would be to download the 1.1 patch and see if that fixes the problem.
http://www.weathergraphics.com/download.htm

Ben

I've had this problem since the first verion of DAWS, and none of the patches seem to have fixed it. My local and UTC times both show the local time. I'm running 1.0p on WinXP home. My system clock is set to Eastern Standard (Indiana time). The "time" special diagnostic button gives this: ...

BUFKIT is supposed to work fairly well on WINE, but I've never been able to put this to the test as I could never successfully build wine on my RH9 box.


Ben

It looks like the vote is overwhelming and the decision has been made. Glad to see PDF is the winner. Windows help files have always been, IMO, alarmingly useless. DA has the best help files I've seen, and even then the WinHelp interface is a pain-in-the-ass.


Ben

I'm using V1.0f and I'm having the same problem. The plots are the same regardless of whether or not the omit box is checked.


Ben

Well Carl, I've never tried to play with the map on BUFKIT, but I'll nose around and see if I can figure anything out for you.


Ben

In that case, my next best solution is going to your style menu, and changing the font size for highs and lows to something smaller. I shrunk mine down to 18pt font from 30 and it cleaned things up nicely.


Ben

Try this... File --> Preferences. Select the 'Analysis' tab. In the lower right corner, make sure the 'Use NMC font' box is checked. I just unchecked it and got the same problem you guys did, so I think that's your solution. If it works, be sure to check the 'Save as default preferences' box before ...

Oh, don't worry, I never stray too far from my computer.... One thing I use BUFGET for is a quick grab of web images. My Aviation Meteorology class is 2 hours on Monday afternoon, so my friends and I generally do our forecasts instead of listening to Beechjet stories. I use BUFGET to grab all of the...

Rochelle,

What version are you using? If this has been a problem in previous versions, it appears to have been fixed by 1.0e.


Ben