biren

then... would the culprits be my CDs? their quality? they were sony and moser-baer. (btw, what is AFAIK?) b.

i am sorry, LUK. it's my syntax. and haste. i said first line said : "****... and second line said: ...... what i meant was, under both the files, these two messages showed up. both bootimages showed these 2 errors - of missing ntldr and mem overflow. but when compared (data compare and hex compare), there was no difference in the 2 files. rgds b.

thanks LUK. and... anything you can share about why beyond compare found errors, while the cds worked perfectly? and, BC said both are same (when i compared - data and hex) rgds/b.

i just finished preparing 4 different boot cds from my 2 OSes - xpsp2 home and pro - with sp3 slipstreamed: 2 simple slipstreamed, and 2 after updating original sp2 deploy.cab with sp3 deploy.cab (following some recommend on the net - i don't even know how or what use of the deploy.cab i m going to be making). since i am completely a moron at such things, i went ahead and booted my computer (installed with xpsp3pro) alternately with the 4 boot cds, to check if the project was a success. in 2 instances, the boot cds were recognised and i got to see the message of : 'hit any key to boot from cd'... in other 2 instances, after some flashing black screens, computer started from my installed OS. (instead of the boot cds) i remebered having read somewhere about keeping the name of the slipstreamed CDs same as the original CDs (VRMHOEM_EN for XP home [oem, english]; VX2PFPP_EN for XP Professional). so i went ahead and checked the name i had given. and it turned out that the 2 cds that had worked had names: VX2PFPP_EN and VRMHOEM_EN - XPhomeSP3deploy (the tail tag was a last moment idea, for me to identify which CD it was - and i presume, because of the space, it may not have been read and considered by the machine). the other 2 CDs were smartly named by me as XPproSP3deploy and XPhomeSP3. turned out, i was too smart for the comp to read my mind. but, this is not a pathos. it is purely and simply a comedy - at my expense. the saving grace was... i WAS able to use the 2 CDs to boot. all i had to do was, like a wild-west gun-slinger, be ready with my trigger-happy finger to push a key (actually, i fired a machine gun) the moment the screen went black after the first loading page that lists the primaries and slaves (sorry, i don't know what it is its 'proper noun'), i started pushing the keys.... and... well... i already TOLD you the story is a comedy, not a tragedy. probably all of you who come here, know this. and then, probably, some lost soul like me trips down and falls here. either way, whoever reads is going to be laughing.... i told you it is a comedy! ta! b. Addendum: i never considered the possibility that the wrong names i gave my CDs, actually could have coincided with something which could be the REAL cause of the booting problem, and not my naming. wouldn't hv realised that if it was not for LUK's statement below... sorry folks... thanks LUK.

i have xp pro and home with sp2. so i was preparing bootable CDS, slipstreamed with sp3. i got mixed up in the procedure about the image file i had extracted from xp home, and xo pro. don't laugh! i didn't know they are same. back to my mis(s)tory... i was concernes that i may hv used one (bootimage) in another (bootable cd). so, to check if i had used the right bootimage, i thought of re-extracting bootimages from both home and pro, and then check the initially extracted ones. when i loaded the 2 BIs in beyond compare, the message it gave was "CDBOOT: Couldn't find NTLDR" ........... in first line, and, "CDBOOT: Memory overflow error" .........in second line... first, i was terrified. (it had taken me 3 days to 'get' the whole procedure, and then its doing... so, now you know how green i am) so i searched the net a little and fell on this brilliant, and simply common-sensical advice: try and check to boot the computer from my boot cd. if it did... welllll... and thats what it did. it BOOTED. me. in the butt. i mean, it worked. so... the question is, what wrong did beyond comapre found in a file that worked where (and when) it was supposed to work? i would appreciate if you could 'write' into my head burner at the slowest speeds... (just trying to be brave about my embarassing follies...) regards. ta.

thanks lightnin' uk... i followed ur advice.... downloaded virtual clonedrive and beyond compare (can you suggest a similar, but free, utility, like BC?) generated and checked the image file against the original install files. check showed ok. so i once again burnt the RW cd (had bought a few cds, but none of them were even recognised being in the drive. so had to use my RW cd) as before, the log (attached here) showed miscompares (31) for the sectors corresponding to the langauge folder. so i thought of checking the cd using BC. i used "folder compare" thru new session... and then under actions, selected 'compare contents'... i did this twice - with binary option and then with CRC option. the report said "no differences". did i follow/do the correct process? is the cd usable, or the miscompares will hinder proper installation? regards b. ImgBurn(6).log

thanks mmalves... b.

hi, litnin' UK... i did as you suggested - turned on the error reporting for ISO9660. and i got a long string of yellow triangles... i hope you are able to help me out nab the culprit... i am attaching the logfile - since it is very long... regards biren ImgBurnfailreport.log

Is there way to use ImgBurn to create a complete back-up of my comp system (XP) - so that all i need to do is copy back to restore my system as it was? b.

sorry for that cheeky way of writing my questions/request. one more question? regarding: W 01:31:16 ISO9660 File System: 302 folder/file names have been modified due to your current settings. how do i avoid this? what settings do i need to take care of, and where? i tried a little bit of searching around in the forum and guides... but couldn't find it. did i have to change the file sys type to ISO + joliet... thanks biren

hello! the site (and your work) had me at the first "hello!" got here thru paul thurrott's article on slipstreaming XPwithSP3. THEN found your article/guide on slipstreaming - after having devoured tens of guides on it, and stored about 5 for detailed study and reference. your guide seemed so simple, at first it seemed simplistic. but having a look around here, i kinda fell in love. and love being blind, i just dived into the project with your guide open. *project completed* was it successful?.... well... thats what i want YOU to tell me? i am a pre-primary child, roaming wide-eyed in this 'halo-ed world of space-science' of yours. in short i am as green as the pre-historic algae in all these stuff here... i am attaching the log here - in case you need it. and to make it simpler, i am pasting a part of it here for easy reference - with the portions that made me stop, colored in red. (please give feedback, which is a better way - tells me what to do in future) here are the '????hooked sticks???' floating in my head... 1. is the cd usable - for a perfect reinstall? 2. will the modified file names have any bearing on the functioning of the patched cd (used licensed xpsp2)? 3. what does the lines 'miscompare at LBA...' mean, and the impact of those errors? 4. i wanted to run a verification latter; when i tried to do that, i was asked for an image file. where would that file be? (all i know is the bootimafe file was from the original CD, and so it cannot be the one to compare against) 5. since i didnot know the above, i ran verification without the image, and it said 'success' - which confuses me even more: do the errors (verified during the end of process) indicate error in the 'writing' of the data, or in the content of the data. meaning, would the correct data still be read - maybe with drive having to do a lot of 'whirring'? 6. i read somewhere here that CD-RW could be a source of 'problem generation'. and, that if instead cdr is used, the errors won't take birth. is it true? 7. the logfiles created, i saw, have the name 'imgburn.log'? does it mean, at any given time, i will have only the latest report - no past history record? any way to workaround that (excepting me going and changing the name of each log)? oh! and the last one... 8. has anybody asked you so many questions? (i m feeling a little red-in-the-face... how much greedy (and a pile-on) can i get?) thank you. a small word that - right now - is carrying a world in it: a world in a word... gracias! shukriya... biren (india) ; //****************************************\\ ; ImgBurn Version 2.5.0.0 - Log ; Monday, 01 February 2010, 02:10:32 ; \\****************************************// ; ; I 00:59:39 ImgBurn Version 2.5.0.0 started! I 00:59:39 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 00:59:39 Total Physical Memory: 515,568 KB - Available: 255,184 KB I 00:59:39 Initialising SPTI... I 00:59:39 Searching for SCSI / ATAPI devices... I 00:59:39 Found 1 DVD-ROM/CD-RW! I 01:06:24 Operation Started! I 01:06:24 Source Drive: C:\ I 01:06:24 Boot Image File: C:\XP-SP3\BootImage.ima I 01:06:24 Creating Boot Image... E 01:06:29 Operation Failed! I 01:07:15 Operation Started! I 01:07:15 Source Drive: C:\ I 01:07:15 Boot Image File: C:\BootImage.ima I 01:07:15 Creating Boot Image... E 01:07:20 Operation Failed! I 01:10:49 Operation Started! I 01:10:49 Source Drive: D:\ I 01:10:49 Boot Image File: C:\XP-SP3\BootImage.ima I 01:10:49 Creating Boot Image... E 01:11:05 Operation Failed! I 01:28:00 Operation Started! I 01:28:00 Source Drive: D:\ I 01:28:00 Boot Image File: C:\XP-SP3\BootImage.ima I 01:28:00 Creating Boot Image... I 01:28:00 Original Emulation Type: None (Custom) I 01:28:00 Original Developer ID: Microsoft Corporation I 01:28:00 Original Load Segment: 07C0 I 01:28:00 Original Sectors To Load: 4 I 01:28:00 Wrote 2,048 bytes to boot image file. I 01:28:00 Operation Successfully Completed! I 01:30:22 Operation Started! I 01:30:22 Building Image Tree... I 01:30:41 Corrected file system selection for Operating System installation disc. I 01:30:41 Corrected conflicting settings for Operating System installation disc. I 01:31:07 Calculating Totals... I 01:31:07 Preparing Image... W 01:31:16 ISO9660 File System: 302 folder/file names have been modified due to your current settings. I 01:31:16 Checking Path Length... I 01:31:16 Contents: 7,174 Files, 180 Folders I 01:31:16 Content Type: Operating System Installation I 01:31:16 Data Type: MODE1/2048 I 01:31:16 File System(s): ISO9660 (Bootable) I 01:31:16 Volume Label: VX2PFPP_EN I 01:31:16 Size: 668,653,520 bytes I 01:31:16 Sectors: 330,262 I 01:31:16 Image Size: 677,117,952 bytes I 01:31:16 Image Sectors: 330,624 I 01:31:49 Operation Successfully Completed! - Duration: 00:01:26 I 01:31:49 Operation Started! I 01:31:49 Source File: -==/\/[bUILD IMAGE]\/\==- I 01:31:49 Source File Sectors: 330,624 (MODE1/2048) I 01:31:49 Source File Size: 677,117,952 bytes I 01:31:49 Source File Volume Identifier: VX2PFPP_EN I 01:31:49 Source File Application Identifier: IMGBURN V2.5.0.0 - THE ULTIMATE IMAGE BURNER! I 01:31:49 Source File Implementation Identifier: ImgBurn v2.5.0.0 I 01:31:49 Source File File System(s): ISO9660 (Bootable) I 01:31:49 Destination Device: [0:1:0] TSSTcorp CDW/DVD SH-M522C TS01 (D:) (ATA) I 01:31:49 Destination Media Type: CD-RW (Disc ID: 97m17s01f, Moser Baer India) (Speeds: 4x) I 01:31:49 Destination Media Sectors: 359,847 I 01:31:49 Write Mode: CD I 01:31:49 Write Type: SAO I 01:31:49 Write Speed: MAX I 01:31:49 Lock Volume: Yes I 01:31:49 Test Mode: No I 01:31:49 OPC: No I 01:31:49 BURN-Proof: Enabled I 01:31:49 Filling Buffer... (20 MB) I 01:31:50 Writing LeadIn... I 01:32:39 Writing Session 1 of 1... (1 Track, LBA: 0 - 330623) I 01:32:39 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 330623) W 01:49:22 Waiting for buffers to recover... (LBA: 301152) W 01:49:28 Waiting for hard disk activity to reach threshold level... I 01:49:42 Writing Sectors... I 01:51:20 Synchronising Cache... I 01:52:05 Exporting Graph Data... I 01:52:06 Graph Data File: C:\Documents and Settings\biren\Application Data\ImgBurn\Graph Data Files\TSSTcorp_CDW-DVD_SH-M522C_TS01_01-FEBRUARY-2010_1-31_AM_97m17s01f_MAX.ibg I 01:52:06 Export Successfully Completed! I 01:52:06 Operation Successfully Completed! - Duration: 00:20:16 I 01:52:06 Average Write Rate: 590 KB/s (3.9x) - Maximum Write Rate: 922 KB/s (6.1x) I 01:52:06 Cycling Tray before Verify... W 01:52:14 Waiting for device to become ready... I 02:05:18 Device Ready! I 02:05:18 Operation Started! I 02:05:18 Source Device: [0:1:0] TSSTcorp CDW/DVD SH-M522C TS01 (D:) (ATA) I 02:05:18 Source Media Type: CD-RW (Disc ID: 97m17s01f) I 02:05:18 Image File: -==/\/[bUILD IMAGE]\/\==- I 02:05:18 Image File Sectors: 330,624 (MODE1/2048) I 02:05:18 Image File Size: 677,117,952 bytes I 02:05:18 Image File Volume Identifier: VX2PFPP_EN I 02:05:19 Image File Application Identifier: IMGBURN V2.5.0.0 - THE ULTIMATE IMAGE BURNER! I 02:05:19 Image File Implementation Identifier: ImgBurn v2.5.0.0 I 02:05:19 Image File File System(s): ISO9660 (Bootable) I 02:05:19 Read Speed (Data/Audio): MAX / MAX I 02:05:19 Verifying Session 1 of 1... (1 Track, LBA: 0 - 330623) I 02:05:19 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 330623) W 02:07:51 Miscompare at LBA: 267119, Offset: 0, File: \I386\LANG\IMJPLN.DI_ W 02:07:51 Device: 0x79 W 02:07:51 Image File: 0x81 W 02:07:51 Total Errors in Sector: 2,039 I 02:07:51 Verifying Sectors... W 02:07:54 Miscompare at LBA: 267120, Offset: 0, File: \I386\LANG\IMJPLN.DI_ W 02:07:54 Device: 0xEE W 02:07:54 Image File: 0x49 W 02:07:54 Total Errors in Sector: 2,042 I 02:07:54 Verifying Sectors... W 02:07:55 Miscompare at LBA: 267121, Offset: 0, File: \I386\LANG\IMJPLN.DI_ W 02:07:55 Device: 0x28 W 02:07:55 Image File: 0xFF W 02:07:55 Total Errors in Sector: 2,042 I 02:07:55 Verifying Sectors... ImgBurn1log.rtf