highroller152 Posted April 3, 2012 Share Posted April 3, 2012 (edited) Let me preface this with: This may not be an ImgBurn issue but I thought I would ask here to see if anyone can chime in with some good advice. We have a (working) WinXP boot CD that we use to that comes up with a custom XP boot disk menu to run (among other things) Ghost or PC Check or .... I am updating said disk and am having a *potential* issue with the burn phase. I followed the guide here but deviated in that I created my own IMA file from the extracted BIF (I had to modify some of the scripts). In the guide, you are to leave the File System options alone because the program changes based on whether it believes you are creating a boot disk or not but I never get the auto-correct messages. The settings I have manually tried are both ISO9660 + UDF and just UDF (since it's a WinXP boot image). When I create the boot disk the Content Type always comes up as "Data" although the the File System is displayed as xxxxx (bootable). I never receive any other messages (other than a successful burn) and my disk isn't booting up the new system. I have been mainly getting the "Remove disks or other media. Press any key to restart." message. Again, maybe I'm doing everything correct in ImgBurn and it's an IMA thing but I thought I would check. Thank you for any help. **EDIT** Oh, and I am using ImgBurn v.2.5.7.0 and below is the log (though since I get successful burns I don't know how much help it would be). I 09:32:40 ImgBurn Version 2.5.7.0 started! I 09:32:40 Microsoft Windows 7 Professional Edition (6.1, Build 7601 : Service Pack 1) I 09:32:40 Total Physical Memory: 3,143,224 KB - Available: 881,144 KB I 09:32:40 Initialising SPTI... I 09:32:40 Searching for SCSI / ATAPI devices... I 09:32:40 -> Drive 1 - Info: HL-DT-ST DVD-ROM DH20N A102 (D:) (ATAPI) I 09:32:40 -> Drive 2 - Info: TSSTcorp DVD+-RW TS-H653G DW10 (E:) (ATAPI) I 09:32:40 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (G:) (SCSI) I 09:32:40 -> Drive 4 - Info: ELBY CLONEDRIVE 1.4 (J:) (SCSI) I 09:32:40 -> Drive 5 - Info: ELBY CLONEDRIVE 1.4 (K:) (SCSI) I 09:32:40 Found 1 DVD-ROM, 1 DVD±RW/RAM and 3 BD-ROM/HD DVD-ROMs! I 09:40:24 Operation Started! I 09:40:24 Building Image Tree... I 09:40:25 Calculating Totals... I 09:40:25 Preparing Image... I 09:40:25 Checking Path Length... I 09:40:25 Contents: 120 Files, 16 Folders I 09:40:25 Content Type: Data I 09:40:25 Data Type: MODE1/2048 I 09:40:25 File System(s): ISO9660, UDF (1.02) I 09:40:25 Volume Label: [Not Configured] I 09:40:25 Size: 27,998,602 bytes I 09:40:25 Sectors: 13,734 I 09:40:25 Image Size: 29,032,448 bytes I 09:40:25 Image Sectors: 14,176 I 09:40:25 Operation Successfully Completed! - Duration: 00:00:00 I 09:51:23 Operation Started! I 09:51:23 Building Image Tree... I 09:51:24 Calculating Totals... I 09:51:24 Preparing Image... I 09:51:24 Checking Path Length... I 09:51:24 Contents: 120 Files, 16 Folders I 09:51:24 Content Type: Data I 09:51:24 Data Type: MODE1/2048 I 09:51:24 File System(s): ISO9660 (Bootable), UDF (1.02) I 09:51:24 Volume Label: BOOTER I 09:51:24 Size: 27,998,602 bytes I 09:51:24 Sectors: 13,734 I 09:51:24 Image Size: 30,507,008 bytes I 09:51:24 Image Sectors: 14,896 I 09:51:24 Operation Successfully Completed! - Duration: 00:00:00 I 09:51:27 Operation Started! I 09:51:27 Building Image Tree... I 09:51:27 Calculating Totals... I 09:51:27 Preparing Image... I 09:51:27 Checking Path Length... I 09:51:27 Contents: 120 Files, 16 Folders I 09:51:27 Content Type: Data I 09:51:27 Data Type: MODE1/2048 I 09:51:27 File System(s): ISO9660 (Bootable), UDF (1.02) I 09:51:27 Volume Label: BOOTER I 09:51:27 Size: 27,998,602 bytes I 09:51:27 Sectors: 13,734 I 09:51:27 Image Size: 30,507,008 bytes I 09:51:27 Image Sectors: 14,896 I 09:51:37 Operation Successfully Completed! - Duration: 00:00:10 I 09:51:37 Operation Started! I 09:51:37 Source File: -==/\/[bUILD IMAGE]\/\==- I 09:51:37 Source File Sectors: 14,896 (MODE1/2048) I 09:51:37 Source File Size: 30,507,008 bytes I 09:51:37 Source File Volume Identifier: BOOTER I 09:51:37 Source File Volume Set Identifier: 40834E6D00003A27 I 09:51:37 Source File Application Identifier: IMGBURN V2.5.7.0 - THE ULTIMATE IMAGE BURNER! I 09:51:37 Source File Implementation Identifier: ImgBurn I 09:51:37 Source File File System(s): ISO9660 (Bootable), UDF (1.02) I 09:51:37 Destination Device: [0:2:0] TSSTcorp DVD+-RW TS-H653G DW10 (E:) (ATAPI) I 09:51:37 Destination Media Type: CD-R (Disc ID: 97m15s17f, Ritek Co.) I 09:51:37 Destination Media Supported Write Speeds: 16x, 24x, 32x, 40x, 48x I 09:51:37 Destination Media Sectors: 359,843 I 09:51:37 Write Mode: CD I 09:51:37 Write Type: SAO I 09:51:37 Write Speed: MAX I 09:51:37 Lock Volume: Yes I 09:51:37 Test Mode: No I 09:51:37 OPC: No I 09:51:37 BURN-Proof: Enabled I 09:51:37 Write Speed Successfully Set! - Effective: 8,468 KB/s (48x) I 09:51:37 Filling Buffer... (40 MB) I 09:51:39 Writing LeadIn... I 09:52:00 Writing Session 1 of 1... (1 Track, LBA: 0 - 14895) I 09:52:00 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 14895) I 09:52:09 Synchronising Cache... I 09:52:16 Exporting Graph Data... I 09:52:16 Graph Data File: C:\Users\colin\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_DVD+-RW_TS-H653G_DW10_TUESDAY-APRIL-03-2012_9-51_AM_97m15s17f_MAX.ibg I 09:52:16 Export Successfully Completed! I 09:52:16 Operation Successfully Completed! - Duration: 00:00:38 I 09:52:16 Average Write Rate: 3,310 KB/s (22.1x) - Maximum Write Rate: 3,316 KB/s (22.1x) Edited April 3, 2012 by highroller152 Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted April 3, 2012 Share Posted April 3, 2012 That guide is for Windows Vista / 7, there's a different one for XP. That aside, if ImgBurn knows it's making a bootable disc (you haven't post a log so I can't tell) and the resulting disc isn't bootable, you must have made a mistake somewhere - either in ImgBurn's configuration or when you built the bootable image. Link to comment Share on other sites More sharing options...
highroller152 Posted April 3, 2012 Author Share Posted April 3, 2012 Wow, you must have been replying when I made my edits with the log file (having realized that the instructions in BOLD right in front of my nose clearly stated to include the log). I truly appreciate the nearly-instant response. I did read the XP guide. Again, where I deviate is that I used WinImage to pull the BIF off the original disk and modified the autoexec, config, and a few supporting script files to change designated drives for a new motherboard configuration. I then rebuilt the IMA and used it as the boot image. Maybe I'm hoarking up the IMA build process. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted April 3, 2012 Share Posted April 3, 2012 So what type of boot image is it? A floppy disc one? The log doesn't include that info so I can't tell if you've configured ImgBurn properly for the type of file you're using. If you extract the boot image from the original disc using ImgBurn you can tell it to populate the fields with the right info. Link to comment Share on other sites More sharing options...
highroller152 Posted April 3, 2012 Author Share Posted April 3, 2012 (edited) Yes, it is based on a floppy image. Ok, so it has to be something wrong with my IMA. I just extracted the IMA from the original disk w/ ImgBurn, got a notification to auto-set the properties, slipped my IMA back into the Boot Image field and I'm still getting the same result with the burned CD. I really appreciate the guidance Lightning. Thank you. **EDIT** Incidentally: if you are creating a custom boot disk, if you are using a SATA drive the old oakcdrom.sys file won’t work (it’s only compatible with PATA drives). Instead, include the ahci.sys v1.1 or higher (you can get it from HP here) and change your config.sys file like so: Device=ahci.sys /d:cd1 Edited April 3, 2012 by highroller152 Link to comment Share on other sites More sharing options...
Recommended Posts