CompuServe Messages

Pete, We understand, and it is also a bit more complicated than you know. I am sorry you lost work but it seems completely absurd that you would have done so. There is a simple way around the problem for now. Make the images and save them to a different drive, then simply copy them in mass over to the PAR drive, it works for me, I assume you knew that, and I also assume that this would have kept you from loosing any work. We will fix the problem in the RIGHT manner, not just some dumb fix that will break something else. And we will figure out some way of getting this fix to those who have the PAR, I trust this answer will suffice for the time being, we are aware of your problem, you have a workaround and also the knowledge that we are doing what we can. I do find it silly, as a side note, that DPS has not said, he we could make our code, look for a file format, if it aint right we will just wait for another cycle and see what happens, if it starts to render again, then we will wait for the next time out and maybe it will be right, no instead its easier for them to not communicate with Impulse and hope the problem will go away. Yeah that makes much more sense, while people who have purchased an expensive hardware product and who are loosing money not being able to use it, are told that Impulse has the problem and LW does not, that makes great business senese. Mike