View Single Post
  #16  
Old July 8th, 2005, 09:29 AM
George George is offline
Registered User
 
Join Date: Jun 2001
Posts: 5,299
Quote:
Originally Posted by Harryoke
But I did import the customers track, then tried to import the original track that held things up and it jammed up the works again, so I restarted hoster and the other track I imported for him was no longer in the queue.
I've been giving this a lot of thought and am ready to go out on a limb with a possible theory. I may be as wrong as rain, but it's been bugging me.

The program is designed to save any temp. KMA files in the event of a CRASH.

The program does not save those files if the program is SHUT DOWN.

So, what constitutes a crash as far as the program is concerned? I think that may be the answer to what Harry is experiencing.

When Hoster closes of it's own accord, and you get the Microsoft crash notice, that definately is a crash, and the temp files will be saved.

What happens though, if you get a multisession disc that won't read, hangs up, and the operator SHUTS DOWN?

Consider that Hoster was up and running, hung up or not, and was shut down by the operator. Does that place the unplayed temp files under the area where they are unprotected and lost?

If so, then the program is functioning as designed, and perhaps MTU needs to do some more work in that area.

I think we need MTU to define what a crash is where the program is concerned.

George
Reply With Quote