LIGHTNING UK!

Clearly disabling the AV isn't enough. Then again, maybe it's not even your AV program that's removing the file?! What other programs do you have running? Look in the system tray (near the clock) and see if you have icons for any other memory resident programs that would perform any sort of file checking. Oh and you didn't answer my questions about what's actually happening - i.e. the first things in my previous post.

These memorex ones use the ritek d01 dye. Just wanted to point that out before this turns into a cmc bashing thread (without reason!)

Just to be clear, you're saying that when you double click on the 'SetupImgBurn_2.1.0.0.exe' file, NOTHING happens? You don't get any sort of screen come up? Are you also then saying the SetupImgBurn_2.1.0.0.exe file vanishes from whatever location you downloaded it to (i.e. the dekstop) ? *Something* you're running, be it antivirus, spypware detection, firewall software etc MUST be causing this to happen. Check the logs of all such software and see what they're doing and why. There is no way it would just randomly delete itself, so find whatever software is causing the issue and fix it. It might be worth checking in eventviewer too. Although you say a few other tools have installed fine, that doesn't mean ImgBurn's setup is the issue. The setup itself is fine. You just have a program installed on your PC that's detecting something it doesn't like in the newer versions of the NSIS installer (which ImgBurn is using) and it's deleting the setup exe because of it. This is a 'false positive' detection and should be fixed by whoever makes the software.

Do a scan in CDSpeed 4.7.0.0 too. With the latest firmware I believe your drive (+ CDSpeed) will list jitter figures too.

It only shows it if the ISO is double layer sized - as that's when the .MDS is important - for the layerbreak info.

It scares me that you can go to install something and it just vanishes - either the bit you installed or the install program itself. You should at least get some sort of warning / message / SOMETHING! I'd love to find out what's really deleting it.

Ok, for bitsetting you first need to find out/work out who really makes your Sony drive (it's not Sony!). Previous models have been LiteOn so it makes sense to try LiteOn first. When you're in 'Write' mode you'll notice a little 'Book' type icon down the bottom right. Click it. Then switch to the LiteOn tab. Find 'DVD+R DL - EEPROM' in the drop down list and hopefully 'Current Setting' won't then say 'Failed' (if it does, it's not a LiteOn). Then in the 'New Setting' box, select DVDROM and hit the 'Change' button. The pray for a 'Success' message. Hopefully you now get the idea.

You're not doing any booktype / bitsetting. Maybe your standalone player doesn't support DVD+R DL and so you NEED to be doing it (so it looks like a DVDROM).

Encryption doesn't stop something from being physically read, it stops you from understanding what it says. All you're seeing there is a physical defect on the disc.

Erase is a sub function of the writing modes. There's no way to make it run on its own (via the /erase cli switch I mean) - and there won't ever be unless I actually make an 'Erase' mode (which is quite likely). Btw, you can right click the drive selection box for direct access to that same 'Drive' menu. Why would you need to 'just' erase a disc anyway? So you can put it away in the CD case all nice a 'clean' again?! To me anyway, it just makes more sense to erase a rewritable before you're about to write something else to it.

Press the red stop button and you'll find your pause button already there....where it has been since day 1! In what situation would you find the timers useful? You're at your pc when you start the build - no? So why would you not then be able to answer the prompts that follow (if any) ? I'm pretty sure the standard MessageBox API doesn't offer timeout functionality (although I believe it has been added in an advanced version of it in Vista). I have no intention of converting MessageBox calls into proper forms, so for that part, sorry it's a no go. I could do it on the volume label one though.

This is already built into the next version but thanks anyway

It's not about file extensions, it's about known / supported filesystems within the images. The file extension stuff is purely there for right clicking images within explorer. If your image only has HFS or whatever it's called in it, ImgBurn doesn't understand it (because I've never knowingly seen such an image!). I'm not sure if the filesystem in that ISO would be the same as other MAC images I've seen, but if you want to send me 5mb of the image I'll take a look and see if I can add support for it. There isn't a whole lot of call for burning MAC images on a PC.

Yes, and before you ask, no I won't just create a 3rd radiobutton You should notice that the log and queue options looks the same.... it's all about consistency

and don't cross post please, it's annoying. http://forum.imgburn.com/index.php?showtopic=2643

Being the ImgBurn forum, we only deal with burning here I'm afraid. There is a nice guide in the guides forum for building double layer DVD Video discs - so if your VIDEO_TS folder/files are correct and you follow that guide, there's no reason for your discs not to work (assuming you're using the good Verbatim DVD+R DL discs of course).

Thank you for your suggestions. Build mode is purposely designed how it is - i.e. where you can't do those things. It's really designed for quickly creating an image/burning a disc from an existing folder structure on your hdd. So if it's right on your hdd, it'll be right on the disc. If I ever decide to change that (which to be honest, is unlikely) it will no doubt do those things you're suggesting.

Nice of you to join up to the forum and share that with us

That's the thing, according to your log, the drive doesn't support anything other than 4x on that media. So even if you select 2.4x, it'll still burn at 4x.

Ritek DL media isn't really all that good and I don't really understand why your drive ONLY lists 4x as as supported write speed - especially when it doesn't even burn very well at 2.4x in most drives! All that's happened is the drive has produced a low quality burn... so low in fact that it can't then read it back. Your standalone is probably skipping the errors or is just a better reader.

Yup, if you have something, I'm happy to look at it for you.

It must have some special pattern that kills the ECC calculations the drive does. No matter what it calculates, they're wrong and so it produces read errors when you try and read it back.

Sorry, I cannot provide info on the MDS file, it is not mine to give.

lol yup, I quite like the look of the Dell stuff. I also normally buy Dell machines for work, they're quite reasonably priced really!

Windows Media Player. You just click on the 'Burn' tab, drag your songs into the list and then click 'Start Burn'.