jimmyjames Posted November 1, 2010 Posted November 1, 2010 Hi, I'm trying to use imgburn to capture a bootable dvd as an ISO from a command line with no luck, I can capture the DVD in full, but the bootable part doesnt work. i have used the gui to capture the boot image to a file and included that with a script IMGBurn.exe /MODE BUILD /SRC R: /DEST C:\BuildISO\CapturedISO /VERIFY YES /FILESYSTEM "ISO9660" /VOLUMELABEL "BUILD" /PRESERVEFULLPATHNAMES YES /RECURSESUBDIRECTORIES YES /INCLUDEHIDDENFILES YES /INCLUDESYSTEMFILES YES /BOOTEMUTYPE "Custom" /BOOTIMAGE C:\Scripts\BootImage.IMA /BOOTDEVELOPERID "Microsoft Corporation" /BOOTLOADSEGMENT 07C0 /BOOTSECTORSTOLOAD 8 /START /CLOSE can any one help? LOG FILE: I 15:41:41 ImgBurn Version 2.5.2.0 started! I 15:41:41 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 15:41:41 Total Physical Memory: 3,405,348 KB - Available: 2,292,380 KB I 15:41:41 Initialising SPTI... I 15:41:41 Searching for SCSI / ATAPI devices... I 15:41:41 -> Drive 1 - Info: HL-DT-ST DVD+-RW GT10N A105 (R:) (ATAPI) I 15:41:41 Found 1 DVD±RW/RAM! I 15:41:41 Operation Started! I 15:41:41 Building Image Tree... I 15:41:46 Calculating Totals... I 15:41:46 Preparing Image... W 15:41:46 ISO9660 File System: 258 folder/file names have been modified due to your current settings. I 15:41:46 Contents: 1,469 Files, 225 Folders I 15:41:46 Content Type: Data I 15:41:46 Data Type: MODE1/2048 I 15:41:46 File System(s): ISO9660 I 15:41:46 Volume Label: BUILD I 15:41:46 Size: 4,053,310,343 bytes I 15:41:46 Sectors: 1,979,874 I 15:41:46 Image Size: 4,055,302,144 bytes I 15:41:46 Image Sectors: 1,980,128 I 15:41:46 Operation Successfully Completed! - Duration: 00:00:04 I 15:41:46 Operation Started! I 15:41:46 Image Contents: 1,469 Files, 225 Folders I 15:41:46 Image Sectors: 1,980,128 (MODE1/2048) I 15:41:46 Image Size: 4,055,302,144 bytes I 15:41:46 Image Single Layer Profile: DVD-R/RW (Media Capacity: 2,297,888) I 15:41:46 Image Volume Identifier: BUILD I 15:41:46 Image Volume Set Identifier: UNDEFINED I 15:41:46 Image Application Identifier: IMGBURN V2.5.2.0 - THE ULTIMATE IMAGE BURNER! I 15:41:46 Image Implementation Identifier: ImgBurn v2.5.2.0 I 15:41:46 Image File System(s): ISO9660 I 15:41:46 Destination File: C:\BuildISO\CapturedISO.ISO I 15:41:46 Destination Free Space: 43,882,151,936 Bytes (42,853,664 KB) (41,849 MB) (40 GB) I 15:41:46 Destination File System: NTFS I 15:41:46 File Splitting: Auto
LIGHTNING UK! Posted November 1, 2010 Posted November 1, 2010 Sorry, that's totally my fault. The 'ReadMe.txt' has no useful info for what the program is expecting to be passed along with the /BOOT* switches! The '/BOOTEMUTYPE' one actually wants a number. 0 = None (Custom) 1 = Floppy Disk (1.20 MB) 2 = Floppy Disk (1.44 MB) 3 = Floppy Disk (2.88 MB) 4 = Hard Disk
jimmyjames Posted November 1, 2010 Author Posted November 1, 2010 Seems like it is all working, thanks for you help. P.S IMGBurn is amazing
jimmyjames Posted November 2, 2010 Author Posted November 2, 2010 I have a small request, that might be a nice feature. If you use the command line parameters, the app would display the GUI and write console output as well, that way when calling imgburn from say powershell, you can grab important information $si=new-object diagnostics.processstartinfo $si.filename="$env:systemdrive\program files\imgburn\imgburn.exe" $si.RedirectStandardOutput=$true $Si.UseShellExecute=$false $si.Arguments = "/MODE BUILD /SRC R: /DEST ""{0}"" /VERIFY YES /FILESYSTEM {1} /VOLUMELABEL {2} /PRESERVEFULLPATHNAMES YES /RECURSESUBDIRECTORIES YES /INCLUDEHIDDENFILES YES /INCLUDESYSTEMFILES YES /BOOTEMUTYPE 0 /BOOTIMAGE C:\Scripts\BootImage.IMA /BOOTDEVELOPERID ""Microsoft Corporation"" /BOOTLOADSEGMENT 07C0 /BOOTSECTORSTOLOAD 8 /START /CLOSE" -f ($ISOPath, "ISO9660", "Disc Name") $p=[diagnostics.process]::start($si) just a thought.
LIGHTNING UK! Posted November 2, 2010 Posted November 2, 2010 Sorry, I'm not interested in making it into anything more of a console friendly app than it already is. It's a GUI app, plain and simple. The CLI options I've added to manipulate the GUI options are just there because I'm nice
jimmyjames Posted November 3, 2010 Author Posted November 3, 2010 Can you tell me what exit code 255 is ??
Recommended Posts