biren Posted February 5, 2010 Posted February 5, 2010 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.
LIGHTNING UK! Posted February 5, 2010 Posted February 5, 2010 They might both do the same job but it would appear they're slightly different. I don't know how to explain that, you'd have to ask Microsoft.
biren Posted February 5, 2010 Author Posted February 5, 2010 (edited) 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. Edited February 5, 2010 by biren
LIGHTNING UK! Posted February 5, 2010 Posted February 5, 2010 Sorry, you've lost me now. You just said beyond compare showed differences. They're binary files so displaying them as text never works very well. You could have just messed up the alignment.
biren Posted February 5, 2010 Author Posted February 5, 2010 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.
Recommended Posts