I wrote: > I restarted and only get the 765 failure now (using the amended > code). I wonder if the 893 was to do with me amending the code > while > it was running. Anyway, replacing the one line of code with the > three (with the explicit close) hasn't helped. The split_*.png > files > remain locked on my XP and Vista machines until I exit [EMAIL PROTECTED] > client, > and prevent rmtree from unloading them.
The 765 failure is after each tile and the 893 is after encountering a stopfile (or in yesterday's example when finishing the one specified using "xy X Y 12"). I'm guessing that is when the cleanup code tries to remove the temporary folders if they are still there. > I've downloaded Perl Express and will see if that allows me to > use > breakpoints to trace when the file gets locked. Previously I'd > just > downloaded a java based editor which displayed the line numbers > (as > Windows notepad doesn't like the files much). I gave up on this idea. Perl Express wants perl 5.10 and doesn't like 5.8; updating the perl for the Windows [EMAIL PROTECTED] distribution then needs Win332/GUI updating to a newer version. Once I'd done this the debugging stepthrough didn't seem to work still, so I've reverted back to the as distributed version (and clicked update, to update). I may put some 1 second delays in and write the time(s) to the console window so I can match where the code is with the ProcessMonitor trace to work out when the files get read and not unlocked. Ed _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
