IFOUpdate 0.51 run-time error

That may reduce the liklihood of it happening. But if the error can occur, then there has to be something wrong in the code itself, and it will eventually happen anyway.

jdobbs, Here is a copy of v53. It does not work on my system and brings up the runtime error.

@Jdobbs Take a look at what the code does when it is first kicked off. I ran into the same problem after downloading the 0.55 that was posted. The ini in the zip file is as follows: Code:

@TRILIGHT It definitely tries to open the original file at startup if the "Automatically Analyze Original IFO" flag is on -- but in following the code, it first checks to see if it exists. Unfortunately, I've tried it on 3 different computers, and only one of them have these directories... I also changed the names in the .INI to goofy names (like "jkljkajd\ddjl" and it wouldn't cause an error. I pointed to files that existed but weren't INIs --- and couldn't repeat it. I've since deleted the INI from the zip file for next release -- it really didn't need to be there and will get created at first use anyway. It just drives me nuts that I can't seem to repeat this, and several people have reported it... jdobbs

jdobbs: Not sure what development tool you use, but perhaps whatever Windows function you use to check for the existence of a file is varying. In other words, maybe some of us have a different version of the .dll containing the function...

I think you may be on the right track.

I didn't even think about that. Good idea though. FWIW, I am running Windows XP with Service Pack 1 installed.

Ok, I don't understand enough about the code to say exactly what you would need to change but I at least know the actual cause now, Jdobbs. Apparently, this only occurs when the drive letter corresponds to the CDROM drive. I can alter the ini file to point to the C: drive or even a drive letter that does not exist, and the program simply returns a "file doesn't exist" error. The same is true, of course, if the directory doesn't exist. The runtime error is only returned when the drive letter listed in the ini file refers to the CDROM drive. Sorry I can't provide an exact solution but hopefully this will point you in the right direction.

Nope. You hit it exactly. I can repeat it by pointing to my CDROM drive also. The program attempts to look in the directory of the specified drive to see if the path exists. If there is no CD in the drive, it encounters an error (no media...). Thanks TRILIGHT! This thing really had me wondering, and since my CD is drive "H:" it was unlikely I would have ever tried this!

Yeah, I wouldn't have caught it on my other system. The drives are X, Y, and Z there! hehe ;) It's drive D on my laptop though where I tried running it first. Hopefully I'll have all my stuff moved this week and can get my main system and servers up and running again. time to get off this laptop and get back to some heavy duty encoding! :)