Ichinisan

Thanks. I found out that the disc was all smudged because someone else had handled it. I was able to rip it just fine after cleaning the disc. Regarding the Intel RST driver... It seems to take just as long (more than 3 hours) to burn an hour-long show on my "performance" system (Core i7 860 CPU, GTX280 GPU, 4GB DDR3 RAM, ...), which DEFINITELY has Intel Rapid Storage Technology driver installed. However, I've always been concerned that something is wrong with the RST driver. Whenever I reboot the system, the icon shows a yellow punctuation symbol (don't remember if it's an exclamation point or a question mark). When I hover my mouse over it, the pop-up message says the service isn't running. I've tried waiting several minutes to see if it would go away on its own, but it only seems to update when I double-click on it to open the interface. After several seconds, the tray icon changes and the interface appears showing the status of each SATA connector. I downloaded the latest software directly from the Intel web site only about a month ago after a fresh install of Win7 64-bit.

Thanks, but I did go straight to the Intel site to get the latest chipset software when I built this performance system about a month ago.

My mother keeps burning episodes of Glenn Beck to DVD using Windows 7 Media Center. However, her TV tuner is a standard-def analog NTSC tuner. It bothers me that she expects to share these horrible-looking recordings with people, so I set up my own system to record the show. My cable company happens to offer a whole lot of cable channels in unencrypted ClearQAM HD, so I can record the show in high definition / digital. My PC has an LG HL-DT-ST BD-RE GBW-H20L (DVD writer, BD burner). It was cross-flashed to turn it into a GGW-H20L and enable reading of HD-DVD (it works!). Cross-flashing also allowed me to disable riplock so I can create images of DVD-ROM and BD-ROM discs without unreasonable speed restrictions. The drive never gives me any trouble reading. I've burned a few BD's on it. However, when I use the built-in burning function of Windows Media Center to convert / burn a TV show, it takes about 4-5 HOURS! I haven't thoroughly tested, but I don't believe I've had any problems playing discs that were burned on this system. It's not clear if the system is hanging while burning. I always assumed there's something wrong that makes the transcoding process take forever...but I never see any background process with significant CPU usage. Specs: HP Pavilion Elite m9300t CTO Intel Core2 Quad Q6600 -upgraded NVIDIA GeForce 9300 to PNY NVIDIA GeForce 9800GT EE 1GB ("Energy Efficient") -cross-flashed GBW-H20L drive to GGW-H20L and disabled riplock -Added Bluetooth 2.0 -upgraded 3GB DDR2 RAM to 4GB DDR2 RAM (dual-channel) -upgraded Vista Home Premium to Windows 7 Ultimate -replaced tuner with 2x Hauppauge HVR-2250 Because that system will be busy burning an episode for the next 4 hours, I needed to make a copy of another disc. I put it into my performance PC, which has a Samsung 22x drive (TSSTcorp CDDVDW SH-S223F SB00). I can't upgrade the firmware on the drive because the upgrade utility says I don't have a supported drive (probably doesn't like a 64-bit OS). IMGburn will not finish ripping the disc. After a minute or so, it slows to 0.0x-0.3x and keeps re-trying sectors over and over (check out the attached picture). I tested playing in Windows Media Player and skipped around a bit, and there didn't seem to be a problem. I can't conclude whether the problem is with the drive that burned it, or the drive that's trying to read it. [edit] Nevermind. I looked at the disc and it has some kind of permanent smudges. I always handle these correctly, so I think it would have happened while my mother was handling it.

I only recently decided to start using some of my DVD+R DL discs. I have a variety of different brands that I've purchased whenever there were deals on DL media, but I always tried my best not to use them. My HTPC's 1.5TB dedicated drive for movie backups is full of Blu-Ray rips, so I'm off-loading 1:1 backups of all my DVD images and single-layer BD images. I needed to make some loaner / beater backups anyway. All of my images were made with AnyDVD HD and I tried to make sure it was set to keep all protections so that the images were 1:1 for use with virtual drive software. I did find some cases of BD rips that somehow defaulted to removing protection, so I don't know if it might have happened with some of my DVD images. After finishing with all of my SL BD backups, I started burning "Penn & Teller: Bullshit! Season 1" on some cheap "WINDATA" DVD+R DL discs. The season is 3 discs. The first two went perfectly. The third one shows an error message every time: The error message is so confusing, I have no idea whether attempting to continue would waste a disc or not. Someone on the AnyDVD forum told me that the problem has to do with pressed discs allowing either PTP/OTP, but burned discs would only work with one method and not the other. I mounted the image in VirtualCloneDrive, used AnyDVD HD to rip it to files (stripping copy protection), then used ImgBurn to compose the files into an image and burn. If I recall correctly, ImgBurn only gave me one option for setting the layer-break position. I reviewed all of the content on the resulting disc and it seemed to be fine. I have no idea why only the third disc from the season gave me this problem. I tried to move on to my next backup, Seasons 1 and 2 of "The Venture Bros." I queued up all of the images and set the preferences, but now the very first image in the queue is giving me the same message as the last image I attempted to burn. Can someone tell me conclusively if I was making my images incorrectly? What is the best method to work around this with the least amount of tampering to the disc content? Log: (errors are only because I canceled after the vague error, then canceled the queue) Media Info: