MenuIfoUpdate: Run-Time error '9': Subscript out of range correct, details, related, folder, letter

andy

This error is related to a bad letter drive of folder path? or due to a IFO encoded menu problem

What is the correct sintax of Update_menu_ifo.bat?

More details of the error:

Procedure Name:CorrectIfos
Module Name:ExecuteProgram

Error Number:9
Error Description:Subscript out of range
Error Sourceroject1
Error Line:126
Call Stack:
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
ByteHandle--gt;GlobalFunctions
CorrectIfos--gt;ExecuteProgram
EnableUpdateIFO--gt;ExecuteProgram

Make sure that there are no spaces in the paths.

Edit: or any other bizarre characters, such as %, amp; or ?...

Thank you!
I'll check it
Hmmm, It doesn't happen with 2.0.23 version...
Before updating, had problem with VTS_01
No problems with menu before...

interesting - i don't recall changing everything in that area - i'll check it out.

hmm
Can't see anything- i am going to need all the relevant files. thanks

Ok! I found the problem.
I changed the Ifo file with Ifoedit and used the button quot;Delete Playbackquot; of an VobId 14 that has less than 0.4 seconds in order to avoid the error message of Scenarist.  This Vob-id contained the Layer Change... and then use the GET VTS SECTORS button of Ifoedit

Went to original Ifo, run Big3tools and then deleted this cell manually in Scenarist and all went ok.

A deleted playback in the main VTS movie or GOT VTS SECTORS with Ifoedit before using Numenu4U and Big3 was the case

Sorry for the inconvenience and thanyou for your support!  
(BTW, Spanish GUI 80%)  


Originally Posted by rmtaibo(BTW, Spanish GUI 80%)  Nice to know that numenu was not alt fault - but it seems the pre-processing didn't change everything it was supposed to within the ifo - which caused the confusion for numenu.