I kept getting a flurry of cloop errors when trying to run the r4v5 boot CD. Everything I read in the forums said cloop errors always (some posts said "almost always") result from a bad CD or ISO image. I was able to verfy with md5sum.exe that my ISO image was valid. It turned out that the CD-ROM drives I tried to install from were the problem. I tried 2 frives that didn't work: a Memorex CRW-1622 and a Kenwood Multi-Beam Zen drive (24X I think). I just wanted to document/archive the fact that I received cloop errors from a perfectly valid ISO image.

A good ISO image can still give you cloop errors if you get a bad burn. I've had this issue, reburned the CD from the same image, and been fine. if you encounter it, burning again at a lower speed is usually recommended.

Good point. I ended up burning the image three times to try to get it to install without cloop errors, first at max speed (52x), than at 4x, and again at 12x. All of the CDs I burned gave me cloop errors when I tried to install with the drives I mentioned above. I ended up pulling out the Lite-On CDRW (52x24x52 ) from my Windows computer and plugged it into the computer I was installing KnoppMyth and it it worked fine with all three CDs (even the one I burned at 52x).

Looking at the forum topics now, I guess this should be filed under problems and solutions... perhaps a mod can move it?

Just wanted to let you know, that I probably ran into the same issue right now when I wanted to install/setup my 2nd frontend with an ASUS DVD-E616 16x/48x drive.

Of course I started with the same CD previously burned and already successfully used for the 1st frontend (auto) install. Unfortunately this time I got a lot of cloop errors. That's why I burned up to 3 new ISO images using my CD-burner (a Sony CD-RW CRX140E). All 3 with correct MD5SUM and at different speeds beginning at 4x... no change, still the same amount of cloop errors, no installation possible!

However, I can boot from either of those CDs. The cloop errors arise after the hd was being formatted/partitioned. Before that, everything works fine. I'll now try to change the drive and see what happens. Will post results later.

The cloop errors I received occured before the KnoppMyth installation menu (Frontend, Auto-install, Manual install, etc) popped up. I haven't a clue as to why this problem occurs.

Well, here I am again... pulled out my new ASUS DVD drive and replaced it with an old CD-Rom drive (44x) that was laying around. Can't tell what manufacturer / model it is. Didn't find any meaningful label on it. But installation went fine with it, so it really seems to be something related to the drive, the speed or maybe some standards not supported or whatever. I've got no idea what's causing these cloop errors with some drives.

ohhhh... and by the way: MERRY CHRISTMAS TO ALL OF YOU OUT THERE!!!

I'm having the same problem with images burned as slowly as my burner software is allowing me (4x). Joy.

Sometimes the cheap-o "free after rebate" media aren't worth the problems they cause. I'd recommend getting some decent media and trying it out. Your CD writer problems may go away.

_________________
Do you code to live, or live to code?
Search LinHES forum through Google

I used the cheap-o CD media. Perhaps better media may work on more drives, but the cheap stuff worked fine burned at 52X with two of my 4 CD drives/writers. It would be helpful/interesting to nail down exactly how the interactions between media type and CD-ROM drive work, if their is an interaction at all. I don't have any other media to try on the two drives where I received cloop errors.

These were Fujis, not no-namers. Not the best name in the book but certainly not the worst.

I ended up pulling the CD burner from my system and putting it into my Myth box to do the install. Worked fine if a bit of a hassle.

I too had this issue until I switched the media I was using. Great Quality blank cds didn't work, but a blank by Sony did.