LIGHTNING UK!

Post the log please - as per the pink box up the top.

That's not something I can reproduce. If it's taking a while for the dmp file to appear, can you check to see if ImgBurn.exe is still running as a process in Task Manager for that period of time? It should vanish from it straight away. If it isn't, something else is wrong somewhere.

I'll do some testing and change the way it opens the volume when extracting the boot image if it works ok for all OS. You're lucky the program works at all really as I could also be opening devices (for all I/O) via their drive letters and SPTI requires read and write access. Your enterprise protection must only work at a certain level or something.

ImgBurn will create an image of the disc (probably a bin and cue file). They're meant for burning to new blank disc, not for being copied to a USB stick. It sounds like you may want to extract/rip the tracks from the disc and save them in mp3 format or whatever. You can use something like 'exact audio copy' (EAC) for that.

What do you now see listed in the IDE controller section of device manager? ImgBurn work ok with Linux if you run it via 'wine'. Not sure what you mean about xp. You can't run xp in Linux unless you're talking about a virtual machine? I guess you could try booting up an Ubuntu OS disc, installing Wine and then installing ImgBurn. You could also try buying a silicone image chipset based PCI card and attaching the drive to that instead of your nvidia nforce controller. Even a USB to Sata adapter might do the job- just for the sake of testing it. Try the drive in another PC too if you can.

Your disc is unreadable. Is it dirty / scratched? It may have been unreadable from the second it was burnt - that's where verifying is important. Your problem isn't related to drivers.

I was always a bit of an Alpine 'fan-boy' back in the day. They were never a 'cheap' brand though. Pop into a store that sells that kind of thing and ask their advice. You'll probably need some trim adapters too unless your current headunit is the exact same size as the one you end up buying. Lots of cars have weird shaped ones now and so fitting a generic headunit involves using some sort of adapter.

You only have 1 option. Continue burning your 80min audio cds. Well, I say 1 option... you could buy a new headunit for the car that supports mp3, usb sticks, Bluetooth, ipods etc. Or get an FM transmitter, connect it to an ipod and tune your radio to it.

But it's playing them because you're burning an Audio CD (they are no longer mp3s). If you've got any real mp3 data discs that work ok (so you can still browse the mp3 files on them on your PC), by all means confirm that and we'll work out what format those discs are in so we can copy / emulate it.

I think you must be confused... or I am. If you burn an audio CD, you aren't burning mp3 files. They're converted to the proper (and only) format used on CDDA disc and you're either then limited to 74 mins or 80 mins on a disc. That's unless you buy the 'extended' discs that can sometimes give you up to 99 mins but not all drives will burn them and not all drives will read them. If your player supports reading MP3 (data) discs then it'll probably have an mp3 logo on it somewhere. Only if it support mp3 data discs will you be able to fill a disc up with 700MB worth of mp3 files (each one taking up ~4MB or whatever).

Are you expecting your car CD player to play mp3 discs? Not all do... and especially not one that old. Does it specifically state anywhere that it does? Otherwise, you're stuck with the normal CD-DA format that's limited to the size of your discs (80 mins of audio in your case).

The 'iHASxxx W' drives don't use the MediaTek chipset and therefore will not work with kprobe.

They're cheapo / value verbatim discs if they're verbatim at all. You need the MKM-003-00 ones.

Your drive has probably developed a fault. You could try cleaning it with a cleaning disc but you may just want to invest in a new one.

You had the option to opt-out of installing whatever it was that you were offered by OpenCandy during the installation of ImgBurn. It only take a mouse click or two.

I was hoping safe mode would bypass some drivers in the I/O chain and at least give you a proper error (direct from the drive) if it actually ran into a problem doing something. FYI, Virtual Clone Drive is a program... what you actually mean is 'ElbyCDIO'. That's the driver you're using, not 'Virtual Clone Drive'. VCD just installs the ElbyCDIO driver. Sorry, I don't know what's causing all these problems for you. I'd be tempted to backup your entire hdd (as an image with a proper hdd tool) somewhere and try a fresh reinstall of Windows. You can restore the image later if it's no different - at which point it's probably safe to assume it's a hardware issue.

Ok but obviously you're going to run into problems when anything tries to play that file it kept erroring out on... it's corrupt.

Don't, you'll make me blush Does kprobe work with your ASUS drive? If so, scan one of the DL discs you've burnt (scan at 4x) and see what it looks like.

No, you should be using MKM-003-00.

The drives have a default behaviour/configuration. You're modifying the behaviour/configuration and it's causing problems. Stop modifying it. Seems pretty simple to me?

Use the recommended MKM-003-00 media. That's what those drives have been designed to use (and tested with) when overburning DVD+R DL media. It's just luck if other discs work.

As you can see from here... http://www.t10.org/lists/asc-num.htm#ASC_08# 'ASC: 08' is some sort of communication issue. That's why I mentioned changing the SATA cable in my first post - and you said you've now done that. Your 'Family Tree' info tells me you have an NVidia chipset on your motherboard - I'm not a fan of anything other than Intel myself... too many issues with the others! You could try uninstalling the NVidia driver for your sata controller and putting it back on the standard Microsoft one. Alternatively, see if you can find a newer one on the NVidia site.

You should be leaving the drive to performs as many retries as it wants to by default (i.e. after it has been switched on for the first time). By messing with that setting, you're changing how the drive does its job. Discs will always have errors on them (you'll never get a perfect disc/burn) but the drive's internal error correction routines get around all that. It would appear yours is unable to do so once you've messed with the 'set hardware retries' option and that's when you (as a 'user') start seeing errors being reported.

Your drive seems unable to read the disc. Is it dirty / scratched?

The conversion shouldn't take any time at all. It's all done on the fly as it reads the sectors from the disc. If it isn't making steady progress (a read speed of 8x or whatever), it's probably stuck somewhere.