Frankenstien

I'm playing around with 'HAWKPE-42-CD.ISO' ... once burned (I used ImgBurn 2.5.0.0), you have a boot/utility CD that is a lot like BartPE ... my burned CD seems to work fine ... I have run into a snag however: while following The Hawk's instructions for making a bootable USB thumb drive, there is a step where the contents of the burned CD (above) need to be copied to the HAWKPE directory at the root of C:\. The Copy process fails with an error on a file called 'cookies.txt' from: <CD root>PROGRAMS\FirefoxPA\Data\profile I'm thinking the problem is because the files on the CD are Read Only or something along those lines. After reviewing the 'REMASTERING' and 'HAWKPE-USB' sections of 'README-HAWKEPE.txt' (attached, in case someone's interested in looking at it), I find that The Hawk likes a burning utility called 'mkisofs' but not Nero because it doesn't support '-boot-info-table'. I don't understand the described process of getting the contents of the ISO into the "hdrive" (home drive?) directory 'HAWKPE'. Can someone comment on '-boot-info-table' support in ImgBurn and also point out the error of my ways with respect to my attempt to Copy the contents of the burned CD to my 'C:\HAWKPE' directory? Thanks, FFF README-HAWKPE.txt

Hey LIGHTNING UK! ... thanks for helping out ... you must put in some serious time around here ... Yeah, I got to thinking about the CD driver ... but then I realized I'd probably have to tinker with 'autoexec.bat' and 'config.sys' in order to get things to actually work ... am out of my depth on that latter stuff, even more so these days due never having to mess with 386's & 486's, ect. I'll look into the WinImage suggestion (I've made lots of floppies created by / involving WinImage but am not too familiar with the s/w itself - I have versions 6.10 and a v.8.00 30-day trial) and I really like your idea of the USB pen. As to why I don't just use the floppies (for this particular Toshiba Satellite L300D laptop), disk 1 will boot the laptop to the expected prompt: "Insert Ghost boot disk 2 (containing Ghost.exe) Press any key to continue ..." Then, upon removing disk 1, inserting disk 2 and hitting the space bar, normally the program fininshes loading to a rudimentary Symantec Ghost GUI ... however, with the Syba USB FDD and Toshiba L300D, Ghost.exe won't load ... after some FDD physical activity, I am prompted again as above. Very strange ... I've tried all 3 USB ports on the L300D ... the FDD is always seen as a boot device but won't run disk 2 normally. I have my suspicions about the Syba USB FDD because I have had the experience where an IBM T40 laptop only sees the FDD intermittently ... sometimes the BIOS recognizes that a FDD is attached, sometimes not. If I can lose the need for the ext. USB FDD and floppies while using this version of Ghost, so much the better. FFF

Maybe someone can help me with this task: I tried to make a bootable CD using ImgBurn 2.5.0.0 from a set of 2 floppies that have Symantec Ghost 8.0 Corporate Edition on them and use PC DOS 7.1 on disk 1 to boot up initially. I tried to do this because I can't get a Toshiba Satellite L300D laptop to read the 2nd floppy disk and load 'ghost.exe' from the root folder 'GHOST' when using a Syba USB FDD (SY-USB-FDD)(disk 2 has to go in when prompted, after disk 1 is finished loading) .. yet disk 2 is fine and reads and loads properly in an older Toshiba Tecra 8000 laptop that uses a Toshiba proprietary USB drive / connector ... (?) So, I try the bootable CD I made and I wind up with a similar problem ... the L300D can't seem to see the contents of the 'GHOST' folder where 'ghost.exe' is ... the contents are there on the CD, but, aren't being loaded into memory. The CD/DVD drive is not being seen by PC DOS 7.1, presumably because I forgot to include CD driver(s) when I organized the contents to be burned. Here's how I made the CD: - I consolidated the contents of both floppies into a folder called 'CD'. The only identical features on both floppies were the root folders 'GHOST' (empty on disk 1, contain 4 objects on disk 2) and the 'autoexec.bat' files (absolutely identical, byte for byte). - I pointed ImgBurn's Build mode to the 'CD' folder and extracted a boot image from the disk 1 floppy, storing a copy of BootImage.ima in the 'CD' folder as well. -ImgBurn caught the 'CD' folder as a containing folder only and prompted me with a GUI dialog to Build (and Write) only the contents of said folder. I've attached a screenshot of the contents of the floppies and a copy of 'AUTOEXEC.BAT' (renamed 'AUTOEXEC.TXT') to help those who would help me. Thank you for any help with this ... FFF AUTOEXEC.TXT

LIGHTNING UK! ... thanks for looking at my thread and posting ... ... just thought you might be interested ... FFF

Topic title pretty much describes my question ... FYI - I have 'ElbyCDIO - Elaborate Bytes' specified in ImgBurn 2.5.0.0 Tools > Settings > I/O - Interface Would it be safe to say that when someone tries to 'Read' ('Create image file from disc') a Video DVD using ImgBurn while AnyDVD 6.5.9.5 is running and enabled in the systray, that, effectively, they are pretty much doing the same thing as issuing the 'Rip to Image...' command from the right-click menu off the AnyDVD systray icon? The reason I bring this up is that SlySoft has conceded that AnyDVD 6.5.9.5's 'Rip to Image...' command is having trouble with a certain commercially available title when ripping in said fashion. The alternative is to use AnyDVD's 'Rip Video DVD to Harddisk...', which does work ... presumably, I can then use ImgBurn to 'Build' an ISO image from the AnyDVD ripped files.

I searched this phrase and found a couple of threads dealing with "Write Speed Miscompare!". The experience of others and the advice given to them seems to indicate the issue is predominantly drive f/w-centric. Here's an example of an ImgBurn 2.5.0.0 Warning I am encountering at the beginning of a burn (log file excerpt): "Write Speed Miscompare! - Wanted: 1,385 KB/s (1x), Got: 8,310 KB/s (6x)" I'm wondering if my Plextor PX-716A's f/w (f/w V1.11, 03/23/07) & / or PlexTools Professional LE V3.13 s/w (supports up to 6X CLV with Verbatim DVD+R DL 2.4X media) is overriding the Write Speed setting I am selecting in ImgBurn 2.5.0.0 - I like to try to force the Write Speed down to 1X with ImgBurn but I think PlexTools seems to want to default to the maximum Write speed supported for the aforementioned media. I used to believe that PlexTools (FYI, previously was using PlexTools Professional V2.35) was varying the burn speed on-the-fly - maybe it still is, I'm not absolutely sure. Q. - Should I be able to override the PlexTools s/w Write Speed somewhere in its GUI (without disabling the beneficial calibration / write stategy features of the PlexTools s/w)? Thanks, FFF ImgBurn_172_.log

Thank you sir!

Belated thanks to mmalves for the help back in April '08 ... Again, somehow I missed taking note of the MD5 hash for 'SetupImgBurn_2.4.2.0.exe' and did not do a verification on that file. I realize Version 2.4.3.0 is out now, and checking 2.4.2.0 is kinda moot, however, just wondering if Lightning UK could include the MD5 hash info in the changelogs (or somewhere ... for reference later). Thanks, FFF

Somehow I missed taking note of the MD5 hash for 'SetupImgBurn_2.4.0.0.exe' and did not do a verification on that file. I realize Version 2.4.1.0 is out now, and checking 2.4.0.0 is kinda moot, however, just wondering if you could include the MD5 hash info in the changelogs (or somewhere ... for reference later). Thanks, FFF P.S. I sure like the EZ-Mode Picker feature!

Upon re-examining Deadwood - Season 3, Discs 1, 4 & 5 (using PlexTools Professional V2.35 --> CD/DVD Info - Type:), I find that they are: 'DVD-ROM ,2 layer(s) (PTP)' ... I wasn't positive about the disc type before, now I've confirmed the three titles mentioned above as PTP ... LUK, you called it from the get go ... Rather than get involved with cell-splitting, re-mastering or other more complex solutions, I've taken another approach with my PTP discs (suggested by Webslinger & Spanky over at SlxSxft's forum) ... to use CloneCD to 'Copy CD' (not on the fly but to & from [normally temporary] files) to DL+R media ... I don't understand why CloneCD can avoid the issue(s) encountered by ImgBurn Writing the same disc content from different file types (IMAGE.DVD [and multiple data files] vs. *.MDS/*.ISO) - is it because DVDD & ImgBurn are transcoding the info when they are Reading? Or?

Thanks for the feedback fellas ... I'll post back once I've confirmed OTP vs. PTP ... my thinking is that my issues may have more to do with the use of (DVDD3540 &) the latest AnyDVD (v6167 could be the culprit) than with ImgBurn or the original media ... which will likely turn out to be OTP ... as forseen by blutach & fordman. FFF

I will get ImgBurn 2.3.2.0 and install forthwith - thanks for making me aware of the update. I have enjoyed using your program and these are really the first difficulties I've encountered using it in a long time. In the meantime, I have also searched the ImgBurn error dialog title at another forum and found this thread, which I have posted to and bumped (hopefully referencing the thread doesn't violate this forum's rules - if so, my apologies). 'chef' over there made the suggestion to the thread's author to "use Imgburn to fix and set the optimal LB". I have examined the ImgBurn Settings>Write tab, Options>Layer Break (For DL Media) and the 'Calculate Optimal' selection seems to be the programs' default installed configuration, however, my unfamiliarity with many of the Settings tabs and Options precludes my assumption of having homed in on the right setting as thorough or conclusive. I have copied the problem discs' file contents (with AnyDVD6167 enabled) to HDD (equivalent to 'ripped in file mode'?) so as to have an alternative set of the original disc files, as opposed to the MDS/ISO file sets created by DVDD3540 (correctly configured to work in unison with AnyDVD6167, enabled). Would it be possible to solicit some guidance (or link to appropriate ImgBurn online guide section) as to using ImgBurn to optimize the Layer Break Position and/or deal with the PTP to OTP issue(s)? I am not well versed with the meaning or dynamics of PTP vs. OTP or how to deal with the issue(s) I'm facing. TIA, FFF

I have just had my first occurrence of the ImgBurn 2.3.0.0 'Optimal L1 Data Zone Start LBA: None Found! (VTS_01)' dialog, and am unfamiliar with how to proceed. I have ripped plenty of my movie titles using DVDD3540 & AnyDVD (latest version, as of 01AUG07, 6.1.6.7) and then burned the MDS(/ISO) file (pair) to Verbatim DL+R media using ImgBurn (with AnyDVD exited or disabled) w/o any troubles of this nature in the past. Is this more of an idiosynchracy to do with the original commercially pressed discs and the way the layer breaks were set up? Can I expect a successful burn if I elect to click 'Yes' in the dialog and simply continue? P.S. answer (having gone ahead and tried burning the disc): the burned disc halts at 2540 (counter), mid-way through disc playback - unacceptable. The title in question is Deadwood - Season 3, Disc 1. Something else I've never been presented with in ImgBurn is the 'Select Layer Break Position' GUI pop-up (encountered with Deadwood S3 D2). Is this another idiosynchracy similar in causation to the above? FYI - for Deadwood S3 D2, the GUI pop-up is reporting an 'Average' layer break positional status and once the operative layer break info line is selected, 'OK' can be clicked in the GUI pop-up to carry on with the burn - the burned disc works acceptably, notwithstanding an awkward scene transition (momentary freeze) or two. TIF, FFF

I have a seemingly simple problem based on my unfamiarlity with ImgBurn 2.3.0.0's Verify functions(s) and/or inability to see encrypted DVD-9 commercial discs. I want to check the integrity of an ISO/MDS file pair on my HDD - created with AnyDVD6133 & DVDD3540 - against my original disc (THE_GOOD_SHEPHERD). Reason: my Diskeeper Professional 8.0.478.0 got stopped prematurely during defrag of the file(s) and behaved weird until it could be restarted and finish what it had begun earlier. The backup files show up and are now defragged, but, I'm a little skeptical of their integrity. I joined the forum and searched ImgBurn Support for 'how to Verify' and 'initiate Verify' and have yet to find the magic little piece of info I need to get the proggy to see the disc & start checking the exisitng MDS file (and related ISO file) against the disc (BTW - Happy 28th Birthday & thanks to LIGHTNING UK! for all his efforts, current and past [DVDD] ... I use ImgBurn to burn all my Verbatim DVD+R DL 2.4X discs with my PX-716A, f/w v1.10 [& with PlexTools Professional V2.35, supports up to 6X CLV with the Verbatim media] and it all works extremely well together - I like to try to force the burn speed down to 1X with ImgBurn but PlexTools Pro varies the burn speed on-the-fly). So, starting with AnyDVD6133 disabled & ImgBurn Mode > Verify selected, my PIONEER DVD-ROM DVD-106 drive with the aforementioned disc inserted & selected, (Verify Against Image File check-box pre-selected) and the correct MDS file browsed to & selected, the lower left 'Verify' main control icons are greyed out and the Status Bar says "Disc Not Supported (Audio)". Is there any way to get ImgBurn to 'see' the disc? Or some other way to perform an MD5 checksum test of the files against the original disc? TIA ... FFF