Jump to content

DarkFalc

Members
  • Content Count

    3
  • Joined

  • Last visited

About DarkFalc

  • Rank
    ISF Newbie

Profile Information

  • Location
    NZ
  1. DarkFalc

    Oversize ISO Files

    As per my previous thread I have automated iso creation for Visual Studio (Microsoft no longer offer an iso download). My script updates the VS layout directory, and then makes an iso of the directory. This seemed to be working fine for months until I realised that the iso being created is much much larger than it needs to be. I'm wondering if the block size or something similar in the iso is larger than my hard drive partition, causing the size on disk to larger (I am using FileSystem "ISO9660 + UDF"). The iso size seems to be this large as soon as the iso starts being built, its possible that ImgBurn is just over provisioning the size at the start. I have searched the forums before asking this question, I saw this thread which was a similar question but wasn't resolved. Below is the batch script I am running for creating the iso, the REM line is what a user can run (without REM) to execute the same command I am using without the variables. :CREATE_ISO ECHO Creating new VS2017 ISO ECHO %DATE% %TIME% >> "%LOGPATH%" ECHO CREATE_ISO Started >> "%LOGPATH%" "%IMGBURNPATH%" /MODE BUILD /BUILDOUTPUTMODE IMAGEFILE /SRC "%LAYOUTDIR%" /ROOTFOLDER YES /PRESERVEFULLPATHNAMES NO /RECURSESUBDIRECTORIES YES /INCLUDEHIDDENFILES YES /INCLUDESYSTEMFILES YES /VOLUMELABEL VS2017 /FILESYSTEM "ISO9660 + UDF" /DEST "%ISOPATH%" /START /CLOSE /NOIMAGEDETAILS REM IMGBURN.EXE /MODE BUILD /BUILDOUTPUTMODE IMAGEFILE /SRC "D:\TestInputDirectory" /ROOTFOLDER YES /PRESERVEFULLPATHNAMES NO /RECURSESUBDIRECTORIES YES /INCLUDEHIDDENFILES YES /INCLUDESYSTEMFILES YES /VOLUMELABEL VS2017 /FILESYSTEM "ISO9660 + UDF" /DEST "D:\TestOutputDirectory\test.iso" /START /CLOSE /NOIMAGEDETAILS ECHO %DATE% %TIME% >> "%LOGPATH%" ECHO CREATE_ISO Completed >> "%LOGPATH%" GOTO CREATE_CHECKSUM Before making this post I also tried changing the FileSystem modes and Folder/File restrictions but.. the output file always seems to be the same large size. Edit: I bought imgburn team a coffee since I have previously had support question answered.
  2. DarkFalc

    [Solved] Suppress Errors?

    Thanks for the suggestion, genius. At first it looked like it almost was going to work but not quite. The errors were now in the log window rather than blocking error dialogue boxes.. but the build button was greyed out so I couldn't even build the ISO. But after changing to another I/O mode and also disabling all the read error options I could find.. it works! Legendary hacking powers admin (bows). Edit 0: I can't see how to mark or edit my original posts title to SOLVED, so I shall leave that to you LUK! Edit 1: Never mind I figured it out - you have to edit, then select "Use Full Editor"
  3. DarkFalc

    [Solved] Suppress Errors?

    Is there anyway to suppress errors? I am automating the building of an ISO, I finally got the CLI command as I wanted for imgburn.. but... I can't run the command in a batch script unattended because imgburn hangs as it throws an IO error on launch. I have full admin access on my machine, EXCEPT - domain policy has disabled write to optical disk or USB. This isn't should be an issue as I only want to make an ISO, but imgburn throws errors at start up. These errors can be clicked past, but there doesn't seem to be a way to make my script function without hanging. I have looked for error suppression, but haven't found anything (only warnings). IMGBURN.EXE /MODE BUILD /BUILDOUTPUTMODE IMAGEFILE /SRC "D:\Junk\toDelete" /ROOTFOLDER YES /PRESERVEFULLPATHNAMES NO /RECURSESUBDIRECTORIES YES /INCLUDEHIDDENFILES YES /INCLUDESYSTEMFILES YES /VOLUMELABEL TEST /FILESYSTEM "ISO9660 + UDF" /DEST "D:\Junk\test.iso" /START /CLOSE /NOIMAGEDETAILS Is basically the command I am trying to execute in my batch script (names/paths changed), but it results in this (image attached). Is there a way to do this? Windows 10 Pro x64 ImgBurn 2.5.8.0
×

Important Information

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