John_m

Thanks for the reply. ffdshow does support flac (via libavcodec according to the audio decoder config. That's the thing that puzzles me. I've tried fiddling about to no avail. A puzzle. Cheers John

Hi All, I've been trying to get imgburn to create an audio CD using FLAC files. Initially I got the message that I was missing a DirectShow filter. I then installed madFLAC and all was well. However, I had ffdshow (x64) already installed. Now, here's question. Is it possible to use ffdshow (either x86 or x64) to perform the DirectShow duties? I don't have a problem with madFLAC but I use ffdshow anyway, and so it's just one more thing to remember when reinstalling. My machine specs are: Win7 x64, Imgburn 2.5.2.0, madFLAC 1.9 and a recent ffdshow. Cheers John

Ok, I think I've got it sorted. The value on both the iso file and on the dvd is 0xf1, which is the 2nd of the two values shown in the log. Just to confirm that I'm doing things right here is how I got the value: I put 93539 into the sector view and then counted forward 1094 (0x446) bytes into that sector. The resulting position contained the magic 0xf1. I suppose the question is where did the 0xd1 come from? By the way, it may be just my imagination but...the verify miscompares (as part of the burn) problem seems to go away if I restart imgburn between one burn to the next... Cheers John

Hi again. I can't seem to work out this sector thing. I just d/l isobuster, but I've never used it. How do I view the specific sector within isobuster? Sorry that I'm being a bit dense ;-) Cheers and happy new year! John

I have an ASUS P5K-E mobo (BIOS revision 1202) which includes the Intel P35 chipset. I have the latest chipset drivers (9.1.0.1007 WHQL) and "fakeraid" drivers (8.6.0.1007 WHQL). I tried the newer chipset drivers 9.1.0.1012 WHQL from station-drivers . com but with no change. memtest86+ v2.11 gives my memory a clean bill of health. I ran it from it's boot CD and let it do it's thing for a couple of hours after which it declared that everything was cool. I have tried looking at the specific sector, but I am unsure that I'm doing it right. I used a program called "Hex Editor Neo" to open the VIDEO_TS\VTS_01_1.VOB file on my HDD and then jumped to the specified offset 1094 (decimal, I presume?). However, the data at that offset is zero (00)! I assume that it's an absolute offset and not relative of something? What am I doing wrong? Suffice it to say: I'm confused. Cheers John

I'm getting miscompares. Sample log from today: As you can see I got a miscompare in the verify as part of the burn, but no miscopmpare when I verify as a separate operation. Cheers JohnM

Hi all. This is my first post to this forum although I've been using imgburn for a while now (a year or so) and it's great. Now, the reason for my posting. When I do a burn and verify in one step, the burn completes ok but the verify fails just as often as it succeeds. However, if I eject the disk, reinsert into the same drive and do the verify again against the same image I get no problems: it verifies clean. Interesting no? I'm running on Vista x64 SP1, C2D 8500, 6GB corsair RAM (no oc), 600GB RAID 0 HDD on Intel ICH9R. My burner is a Pioneer 215BK (upgrading the firmware to 1.22 made no difference). I'm using Verbatim 16x media but it doesn't seem to matter at what speed I burn at the symptoms persist (even at 1x burn). I even leave my machine completely alone after I click the big "burn now" button but that makes no difference either. So, to recap: burn and verify cycle I get mixed results on the verify (fails roughly 50% of the time). But if I burn and then verify separately, I get perfect verifications. This persists no matter what speed I burn at. Ideas anyone? Cheers John