LIGHTNING UK!

1. Try the 1.29 firmware. http://forum.rpc1.org/dl_firmware.php?download_id=2220 2. Buy Verbatim DVD+R DL discs. They're more expensive because they actually work!

Google 'RITEK-S04-66' and you get 10 hits. There's no way that dye has been around for a year. You might well have been burning A RITEK dye but it wasn't that specific one. Get some media that's known to be decent - i.e. the Verbs I suggested earlier and try again. If they fail too then yeah it's your drive.

There's no issue with the burn / verify so it must be something else - i.e. you xbox - and I'm afraid that's nothing to do with us, you need to fix that on your own.

You've been burning RITEK-S04-66 for over a year? I can't say as I've seen that specific dye up until very recently.

You might find that media is newer than the drives firmware - as such, it won't burn it. Get yourself some Verbatim 2.4x DVD+R DL discs instead. btw, you can get the 47P9 firmware from here: http://www.benq.com.tw/support/downloads/d...fm?product=2346

No, it's just external. I'm sure the caddy itself could go into a 5.25 bay if you had the appropriate dock though. (That might be what lmao2k does?)

Build mode (well, the GUI for it) isn't designed to fit with the other stuff you asked for. If it ever changes, all that stuff will be there automatically.

You need to give a LOT more info. What are you trying to burn? Does it burn / verify ok? Can the PC play it back? Are the files on the DVD as you'd expect them to be - i.e. correct places/names etc? Where's the log file from ImgBurn?

http://www.raidsonic.de/en/pages/products/...e_objectID=4540 That's the one I've got.

lol why thank you Mr McFartfinger, sir!

Yup, if it's turned off (as it is by default) you not notice anything different. The flashing thing is totally safe, the only time it would kill your battlenet is if a window pops to the foreground and wants to have user input directed at it / be made the 'active' application/window.

There was a reason I removed the trailing '\' from directories when adding them to the box but I can't remember what it was now and it appears to work ok with them so I've put them back.

I'd never make the window active on purpose...besides, XP blocks such things from happening (soooo many people complained about windows making themselves the foreground app and disrupting what they were doing). All I've done (as an option) is add code to flash the taskbar button if a messagebox that's about to be displayed has the MB_ICONERROR flag set and the application isn't the foreground / active one at the time.

(I'm going to assume that an 'error' messagebox pops up for every error - that's not 100% true but it's pretty damn close) The thing with messageboxes is that they can pop up everywhere and anywhere and for all types of different reasons. That said, I actually have my own wrapper function for displaying them and I could easily do it on a global level so if it's an error box and the app isn't active, it'll flash the taskbar. If it's not done on a global level, forget about it because there's no chance in me doing it! Seems a bit lazy though because if you can see the bar you should be able to (get up and) check the program itself! You can tell if it's done or not because a) the drive won't be making loads of noise and the drive's light won't be flashing! It finishing due to an error or finishing successfully doesn't make much of a difference in my eyes - either way you have to go back to the machine to do the next bit, be that inserting the next disc to burn or repeating the one that failed.

lol wherever you can get the model you want from! Basically, checkout raidsonic's website, find the right one and then chuck the model number into google and see where's selling it.

You can talk about burning until the cows come home. It's getting around protection that isn't allowed.

The answer was NO.

you need to post the full log after you've pressed 'cancel' or whatever.

DT pro can do all sorts of things that ImgBurn won't support - i.e. compression / encryption. On a bog standard image, ImgBurn should have no problem loading it so something isn't quite right.

It's not a nice thing to hear but you really need to get another drive - that or hope there's a firmware update available to fix all your problems. Laptop drives are always useless so go for an external usb/firewire one.

The mds must have the wrong name in it - probably because you renamed the files? (or someone did) Just rename your image (mdf) and remove the extension, then it'll load it.

Raidsonic (ICY BOX) do loads of usb/esata boxes, you could just buy one of those and stick any old hdd you want in it (assuming it's sata of course!). I've got a couple myself I don't know how fast the pcmcia interface is but I'd hope it's fast enough to allow esata to easily beat usb/firewire.

What file doesn't exist? Read the actual message box. If you're not loading that file directly, it must be what's written in the .DVD file - so edit the .DVD in notepad and type in the correct name for the image or rename the image itself to match what the .DVD says.

No because you're obviously creating a new instance when you run ImgBurn (with or without command line parameters). To make it append to an existing instance I'd have to start looking around for others, querying their current status (more than 1 open at a time?) and then talk to that instance via special windows messages to tell it what to add before then closing the new instance without you ever actually seeing it load. (At least that's how I *think* it's done?!) Basically it's a big pain in the arse and I can't be bothered with it. Sorry!

http://svp.co.uk/product/verbatim_dvd_plus..._layer_3435_box http://svp.co.uk/product/verbatim_photo_pr...plus_r_3682_box Basically, anything you can find using the 'MKM' dye.