Jump to content

princenigma

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by princenigma

  1. Normally the drive that's burning would be 'locked' so no other program (or ImgBurn itself) will be able to access it - hence opening another instance of ImgBurn isn't a problem.

     

    The log from the failed burn might shed some more light as to why it failed but it's not a program bug.

     

    Thanks 4 fast reply.

     

    I will do more research

  2. Ah ok, I see the problem.

     

    When you save the MDS to the same folder as the files the path and file name gets stripped regardless (it's done outside of the code for that 'Create DVD MDS File' window in a generic function that creates all the MDS files).

     

    What you need to do (until I fix it) is save the MDS somewhere else other than in the same folder as the image data. That way the full path and file name get preserved as per the 'Preserve Full Pathnames' option.

    I see, Thanks for the tips .

     

    have a nice day :)

  3. The program would probably now use *.i00, *.i01 etc to make it easier to rename the files without then having to hex edit the mds file.

     

    Whatever the mds file is called (minus the file extension), that's what replaces the '*' when parsing the mds to load the actual data files.

     

    The ansi/unicode choices are totally unrelated.

    but that's make full path name option useless and i need that function for all time :(

  4. in 2.4.1 ,create dvd mds tool give me a mds that i can see "c:\file.i00" " c:\file.i01" ... in it

     

    in 2.4.2 , no matter i check us ansi or not , i can't get same result as 2.4.1

     

    is there a way to create 2.4.1 style DVD mds file ?

     

    best regards

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.