IFOUpdate 0.51 run-time error

[FamousPerson]

I downloaded IFOUpdate 0.51 tonight and get an error when I run it:

Run-time error '52':
Bad file name or number

I experience the error on two separate PCs - one running XP and one Win2K. Also, 0.49 runs fine on these PCs.

Is anyone else getting this error?

[jdobbs]

I obviously left an error check out somewhere. I'll take a look at it.

[jdobbs]

I can't seem to repeat this. Could you post the current contents of your .INI file? If possible let me also know what steps you take up until the run-time error occurs (assuming there are any).

The only file that IFOUpdate attempts to open at the offset is the original IFO when "Automatically Analyze Original IFO" is on. But I've tried every combination I can imagine of bad filename and path, and it doesn't crash for me.

[FamousPerson]

That was it - the ini included in the zip download referred to a non-existent file.

I deleted the ini and all is well.

[jdobbs]

That's still confusing. I have code that checks to see if the file exists first before trying to open it...

Anyway, at least I can look at the INI file and see why.

Thanks for helping out.

jdobbs

[jrg]

Not sure if this has been solved or not. I ran in to the same problme and found this thread on a search.

I get that runtime error on v54 and v55. I double click on the exe file and the error box pops up.

For some reason (and i am thankful for this) v53 works.

Any clues on how to get the newer verions working?

(WinXP, Athlon XP 2100)

[jrg]

sorry, need to get some sleep. After deleting the ini file, v55 appears to be working correctly.

[jdobbs]

If anyone else gets this... please put a copy of your .INI file in a ZIP and post it. I'd like to get this fixed. The error is occuring when trying to open a nonexistent file that is designated in the INI. But I've gone through the code, and even tried to force the error without success, I also can't find an area where I don't first do a check before attempting to open. I'm obviously missing something and I'd like to kill this error.

Thanks,
jdobbs

[FamousPerson]

jdobbs:

I believe you can eliminate the error by not including an ini in your zip file.

[jdobbs]

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.

[jrg]

jdobbs,

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

[TRILIGHT]

@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:

[Paths]
Original=D:\cd_image2\VTS_01_0.IFO
New=D:\cd_image2\VTS_09_0.IFO
Backup=D:\cd_image2\VTS_01_0_IFO.BAK

[Flags]
CellCopy=0
AutoCorrect=0


Apparently the program tries to open these files automatically. When it tries, it does not find them and then craps out. It's probably not doing on your system because those directories and files actually exist. Somehow you need to have it perform that check first off before trying to access those directories/files.

[jdobbs]

@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

[FamousPerson]

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...

[jdobbs]

I think you may be on the right track.

[TRILIGHT]

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

[jdobbs]

Me too.

[TRILIGHT]

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.

[jdobbs]

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!

[TRILIGHT]

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! :)