strange error pop up - file not found for script
-
- Senior Member
- Posts: 254
- Joined: Thu Feb 05, 2004 11:36 pm
- Location: Roanoke, VA
- Contact:
strange error pop up - file not found for script
Error message pops up saying "Digital Atmosphere encountered an error: file not found" after doing following script one line at a time. Actually, fronts ingest and they plot just fine, but curiously, the error box then pops up.
download,http://www.hamweather.net/weather/asus0 ... fronts.dat
ingest,d:\digatm\data\fronts.dat
product,wxp,0,fronts
Using version 0.6c I guess ... the patch install file says "c" but during the patch, the install box says "b", and the software says "b" at the top when running.
download,http://www.hamweather.net/weather/asus0 ... fronts.dat
ingest,d:\digatm\data\fronts.dat
product,wxp,0,fronts
Using version 0.6c I guess ... the patch install file says "c" but during the patch, the install box says "b", and the software says "b" at the top when running.
-
- Senior Member
- Posts: 223
- Joined: Sun Nov 07, 2004 6:38 pm
- Location: Gouda, Netherlands
- Contact:
This is one that has been puzzling me for a while. So I stumbled across what might be the cause.
Today I installed Fusion on my other PC, which runs Windows 2000 pro. Fusion runs alone on this, DAWS is not installed on it.
Well, just by chance I ran the same script I was having problems with on the other machine, low and behold the script runs flawlessly.
I can only assume this is either an issue with windows 98 which is on my main DAWS machine, or because the original DAWS is installed on the same hard drive.
I`m formatting my other machine removing windows 98, and installing windows 2000 as the OS. I`ll just install Fusion and nothing else and see how it goes.
Today I installed Fusion on my other PC, which runs Windows 2000 pro. Fusion runs alone on this, DAWS is not installed on it.
Well, just by chance I ran the same script I was having problems with on the other machine, low and behold the script runs flawlessly.
I can only assume this is either an issue with windows 98 which is on my main DAWS machine, or because the original DAWS is installed on the same hard drive.
I`m formatting my other machine removing windows 98, and installing windows 2000 as the OS. I`ll just install Fusion and nothing else and see how it goes.
-
- Senior Member
- Posts: 223
- Joined: Sun Nov 07, 2004 6:38 pm
- Location: Gouda, Netherlands
- Contact:
Well I`m absolutely puzzled by this one.
Both PC`s now have the exact same operating system. I`m running Fusion on my smaller PC which I was using to run scripts in DAWS 24/7.
In bouyant mood expecting to see my scripts running again, well that was a dissapointment
On my smaller PC I`m back to the `file not found` popup error as soon as the fronts have plotted.
I don`t get it because the same script runs perfect on my main pc. All the paths/directories are exactly the same for both machines. So why the heck will they not run on my other machine, which apart from the hardware is exactly the same.
FWIW, here`s a sample of the script
I would have thought a machine would run Fusion which ran DAWS fine.
Mmmm, not sure what else to try
This was reported several months ago a few folks, hopefully Tim can fix this up.
Both PC`s now have the exact same operating system. I`m running Fusion on my smaller PC which I was using to run scripts in DAWS 24/7.
In bouyant mood expecting to see my scripts running again, well that was a dissapointment

I don`t get it because the same script runs perfect on my main pc. All the paths/directories are exactly the same for both machines. So why the heck will they not run on my other machine, which apart from the hardware is exactly the same.
FWIW, here`s a sample of the script
Again, the above works fine on one machine but crashes on the other. It always fails after the fronts have plotted.load,C:\Documents and Settings\Bob\My Documents\DAWS\basemaps\canada800.dmf
download,http://www.hpc.ncep.noaa.gov/discussion ... \Documents and Settings\Bob\My Documents\DAWS\data\fronts.dat
download,http://www.atmos.albany.edu/weather/dat ... \Documents and Settings\Bob\My Documents\DAWS\data\synop.dat
download,http://www.atmos.albany.edu/weather/dat ... \Documents and Settings\Bob\My Documents\DAWS\data\synbouy.dat
ingest,C:\Documents and Settings\Bob\My Documents\DAWS\data\*.dat
product,wxp,0,fronts
ANALYZE,HILO CONT CINT=4 COLOR=64:64:64 LINE=1 SLPR
import,C:\Documents and Settings\Bob\My Documents\DAWS\basemaps\surfaceanaloverlay800.gif
stamp
export,C:\Documents and Settings\Bob\My Documents\DAWS\products\canada_surface.png
I would have thought a machine would run Fusion which ran DAWS fine.
Mmmm, not sure what else to try

Wally,
Running DA WS 1.1j3 and Fusion v0.6e2 at the same time, on the same hard drive does not cause this error (perhaps it was corrected in a Fusion patch after v0.6c?).
I just copied your script and everything worked perfectly as the data from HPC, via Hamweather, plotted the fronts, running both DA WS and Fusion from the same hard drive.
Maybe if you could post your entire script, Wally? I don't know if there is more to it or not, but maybe something else will show the error when I copy and run it on my computer.
Pat
Running DA WS 1.1j3 and Fusion v0.6e2 at the same time, on the same hard drive does not cause this error (perhaps it was corrected in a Fusion patch after v0.6c?).
I just copied your script and everything worked perfectly as the data from HPC, via Hamweather, plotted the fronts, running both DA WS and Fusion from the same hard drive.
Maybe if you could post your entire script, Wally? I don't know if there is more to it or not, but maybe something else will show the error when I copy and run it on my computer.
Pat
-
- Senior Member
- Posts: 223
- Joined: Sun Nov 07, 2004 6:38 pm
- Location: Gouda, Netherlands
- Contact:
I`m not Wally but as I`ve tried every else, this must be hardware related? Why else would the script fail on one machine, but run on another. Both machines running identical operating systems etc.
The failing machine is fairly old. 300mhz Pentium, 196mb ram but it should work as it handled DAWS for many months. For some reason my old machine has an issue after frontal depictions have been plotted in a script. If I remove the front command(s) from the script, all the maps then carry on to plot the isobars perfectly.
The failing machine is fairly old. 300mhz Pentium, 196mb ram but it should work as it handled DAWS for many months. For some reason my old machine has an issue after frontal depictions have been plotted in a script. If I remove the front command(s) from the script, all the maps then carry on to plot the isobars perfectly.
Bob,
I just ran this script from your earlier post (minus stuff that is irrelevent to my machine):
download,http://www.hpc.ncep.noaa.gov/discussion ... fronts.dat
download,http://www.atmos.albany.edu/weather/dat ... \synop.dat
download,http://www.atmos.albany.edu/weather/dat ... ynbouy.dat
ingest,C:\digatm\data\*.dat
product,wxp,0,fronts
ANALYZE,HILO CONT CINT=4 COLOR=64:64:64 LINE=1 SLPR
Fronts and isobars plotted without any error running the latest DA WS and Fusion from the same hard drive.
Maybe it is some odd sort of problem with older computers?
Pat
Edit: I added this last line to the script to exclude any imagery export problems (I use the \us directory for all exported charts):
export,C:\us\canada_surface.png
No errors were encountered after adding this line.
I just ran this script from your earlier post (minus stuff that is irrelevent to my machine):
download,http://www.hpc.ncep.noaa.gov/discussion ... fronts.dat
download,http://www.atmos.albany.edu/weather/dat ... \synop.dat
download,http://www.atmos.albany.edu/weather/dat ... ynbouy.dat
ingest,C:\digatm\data\*.dat
product,wxp,0,fronts
ANALYZE,HILO CONT CINT=4 COLOR=64:64:64 LINE=1 SLPR
Fronts and isobars plotted without any error running the latest DA WS and Fusion from the same hard drive.
Maybe it is some odd sort of problem with older computers?
Pat
Edit: I added this last line to the script to exclude any imagery export problems (I use the \us directory for all exported charts):
export,C:\us\canada_surface.png
No errors were encountered after adding this line.