Web Engine on Windows XP SP(latest):

This is old data being re-worked under a new file name. Data was published without ANY failures up until this point:i.e, this was the last successful publish prior to this post:

http://members.shaw.ca/rrsknox/ksmandte.svg

Subsequent to this I a) created two new objects with the polygon editor; edited both with the vertex editor; & shaded them & re-shaded them b) created one rectangle and rounded the corners with the vertex editor; re-scaled it with the dialog editor; shaded it; ....thus attempting to create a new candle on the left. It was saved and previewed several times; and prior to this had been published several times (15, 20?). Then it locked while trying to upload the background .jpg file. I ctrl,alt,deleted; ignored the saved file; re-saved the data-set and tried publishing again. And once again the exact same story.......which I am telling you hot of the press so I don't know the final answer yet.

The only generalization I can make is that this occurs on files which I have been working on for, say. over 6 hours with numerous saves, and numerous publishes and numerous previews. and, stems from copying an existing file to a new file name for renovation purposes. These are clean file copies; ie, not copying over existing files.

I am now going to clean copy to yet a new file name and try to publish again.

RC

Robert C. Smith

This is a one time data file for you guys. The work done between what you see in this URL and the last URL "was a factor" (I am not claiming causality, only correspondence) in the publishing lock.

http://members.shaw.ca/rrsknox/ksmandtt.svg

I created the new file; defraged; shut down the system and did a system file defrag; re-booted; saved the file for good luck, and it published without hesitation. (Too many changes of variable for good science.)

One gets the impression because of the "time" factor and number of operations that something is, shall we say, not cleaning its house properly???

Best I can do.

RC

Robert C. Smith

You have no doubt noticed that the two URLs are identical. That means, even though it locked, it still published. Yet it locked on the first .jpg file???? long before it reached the .ims and .svg files. I don't get it at all.

The Ghost in the Machine.

I don't know what to say. I am not even remotely embarrassed; just baffled; not to mention frustrated. All I expected you to see on the left in the first URL was the "flame."

It is what I said before, Derry. There does not appear to be one specific operation which triggers this locking business, but rather the cumulation of a sequence of several operations. Like lots of them. An "overloading" issue. It is as if the doggone thing is scratching its head and saying, "what do I do now?" Yet it actually published though locked. ...which may have occurred in a burst when I terminated the program.

RC

Robert C. Smith

Hi Muzzy,

OK, thanks for your help with this. If you do notice a sequence of events that might cause this let me know.

Also, hate to mention this once again but we are only getting SVG text with your posts. I know we were able to view them before.


- Derry