UBCD4Win Forums: No Iso File Created - UBCD4Win Forums

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

No Iso File Created Directory name is invalid - error from mkisofs.exe

#1 User is offline   PCMouse Icon

  • Newbie
  • Pip
    • Group: Members
    • Posts: 3
    • Joined: 11-December 09

    Posted 11 December 2009 - 02:36 PM

    What is the solution to a failure to create an ISO file.
    The ending lines of my UBCD4WIN PE Builder v.3.1.10a are:

    Build ISO image
    Running external program
    C:\UBCD4Win\mkisofs.exe -iso-level 4 -volid "The Ultimate Boot CD for Windows" -b bootsect.bin -no-emul-boot -boot-load-size 4 -hide bootsect.bin -hide boot.catalog -o "C:\UBCD4Win\UBCD4Win.iso" "C:\UBCD4Win\BartPE"
    The directory name is invalid.
    Building ISO image done
    Building done...
    There where 0 errors and 1 warnings
    Use the [<<] and [>>] buttons to jump to Error/Warning.

    I do not get an ISO file created. However, the BartPE folder is fully populated.
    Should I burn a copy of this folder's contents to the CD or should I expect an ISO file to burn from?

    Any advice?

    TIA
    0

    #2 User is offline   KCarney Icon

    • Regular Member
    • PipPipPip
      • Group: BETA Tester
      • Posts: 231
      • Joined: 29-January 07
      • Location:New York

      Posted 11 December 2009 - 02:50 PM

      What was the warning?
      0

      #3 User is offline   PCMouse Icon

      • Newbie
      • Pip
        • Group: Members
        • Posts: 3
        • Joined: 11-December 09

        Posted 11 December 2009 - 02:56 PM

        The Warning line is at the top and I think it is not related:

        Warning: building from an OEM version of Windows can mean trouble...

        Any hints?

        Thanks.
        0

        #4 User is offline   KCarney Icon

        • Regular Member
        • PipPipPip
          • Group: BETA Tester
          • Posts: 231
          • Joined: 29-January 07
          • Location:New York

          Posted 11 December 2009 - 03:05 PM

          It means exactly what it says. Try to avoid using Dell or other OEM restore cd as your build source. If you do a search at this forum you'll find all the information you need.
          0

          #5 User is offline   rdsok Icon

          • rdsok
          • PipPipPipPipPipPipPipPip
            • Group: Admin
            • Posts: 6,037
            • Joined: 02-October 05
            • Gender:Male
            • Location:Norman, Ok. USA

            Posted 11 December 2009 - 05:50 PM

            Check your Comspec variable for your Windows you are building in... see http://support.micro....aspx/kb/164545
            Plan A is always more effective when the device you are working on understands that Plan B involves either a large hammer or screwdriver....
            0

            #6 User is offline   PCMouse Icon

            • Newbie
            • Pip
              • Group: Members
              • Posts: 3
              • Joined: 11-December 09

              Posted 11 December 2009 - 10:25 PM

              View Postrdsok, on 11 December 2009 - 10:50 PM, said:

              Check your Comspec variable for your Windows you are building in... see http://support.micro....aspx/kb/164545


              Thank you!
              This info offered exactly the correct fix for this problem. (The warning about OEM is not related.)
              I modified the Comspec system variable by deleting the parameter e:xxxx (whatever numbers you have).
              Windows does not need this param - it was on my system to make some DOS programs work.
              For anyone else with a similar problem, please note that you must reboot for the change to have an effect.
              After a reboot, UBCD4Win created an ISO file.

              :)
              0
              Page 1 of 1
              • You cannot start a new topic
              • You cannot reply to this topic

              1 User(s) are reading this topic
              0 members, 1 guests, 0 anonymous users