LIGHTNING UK!

I'm very open to good suggestion, I just don't think this is one of them. Sorry if that upsets you. I'm guessing you're still bitter from me not wanting to support .DAA files. Well I looked at DAA stuff a long time ago for/with someone and it just wasn't worth the hassle. They can actually be quite complex and so would be much better if you just made an ISO in the first place (if that's even possible) if you intend to burn it with a non DAA supporting tool. The mac has proper tools for converting DAA files to ISO and as they have all the specs, would do a much better job of it than I ever could. Now back to this topic... Write mode has, for the past 4 years or so (since DVD Dec days), been for burning ISO files. You can't just change long standing things because someone doesn't understand what they're doing. Learn the program, read the guides, that's what they're there for. No, I do not consider any sort of random files as being 'writable' thing. With an image I just read X amount of data from the image and write it. When I only have files to work with there's a WHOLE load of other stuff that must be done. The two things are very different (have been implemented as such) and that's why they will not be merged. It would be an absolute mess / nightmare. Do remember ImgBurn is a free tool. Everything I do (including forum) is done in MY free time. More so than anyone else, I think I have the right to decide what it gets spent on and I certainly don't appreciate people bitching at me because someone (I) told them 'No' - like it's something they'd heard for the first time in their lives. If it's an easy to implement suggestion and at least vaguely useful to someone other than the person that suggested it, I'll normally do it regardless. If it's going to take a few hours / days, I tend to hum and har a bit over it's TRUE advantages / disadvantages.

I've seen players want (need) an audio_ts folder but never a jacket_p one - so I fail to see what function this serves, sorry! To have the folder with no content (which is what this would do) could actually mess things up for certain players that expect to see files in the folder if the folder exists. And I don't really understand point 2. What is there to verify?! If you have an image file format that supports storing the LB, it will have been taken from the original disc in the first place. Please feel free to explain your suggestion so everyone other than yourself understands what you mean.

The program is called 'ImgBurn'. By the very nature of that, it burns disc images. If you have a bunch of files, they're NOT an image, hence you have to 'Build' one. Sorry but it stays as it is.

ok so play that bit of the movie and look at the times on your player and compare to the times listed. Then see where would be a nice spot for the layer break where you wouldn't notice it too much. Hmmm note to self, add 'Chapter' column to that window. I'd also like to add a preview button but I'm not really sure how to 'play' the content!

You can update the firmware to BYS3 if you do a bit of Googling. Then stop using CMC dye discs, they're useless. (Being branded 'Sony' means nothing). Get yourself some decent Verbatim (MCC dye) / Taiyo Yuden discs instead.

It really doesn't matter. But in any case, you have to take certain things into consideration. i.e. they'll all be different cells, possibly in different VTS sets / PGC's. They'll also have different '%' values. 50/50 being the best for read compatibility. That '%' is the number of sectors (as a percentage of the total!) on each layer. It helps to know what you're burning and what video goes with which pgc / vts set etc. If you can get away with having the LB at a proper scene change (and not a fast moving one) then that'll be more aesthetically pleasing.

Hahahaha the whole cup stacking thing is pretty big in schools here now (going from what I've seen at work). They even have people come round and do demostrations etc. It's pretty amazing to watch. The competitions must be full of hardcore stackers! I believe the one we have is called 'Speed Stack' or something similar.

Well clearly it was one of them or you wouldn't have made 2 coasters! It was probably just a fault in the dye on those discs.

If it's a home movie, regions don't come into it. What you need to check / possibly fix is that they can play NTSC on their TV (most modern ones do). If they can't, you need to convert it to the PAL TV system. You can use google to find out how to do that as it's not really anything to do with ImgBurn.

If the drive is 'ready' when the program loads etc, the /start cli switch will automatically (all be it virtually) hit the 'Write' button. If you have 'auto calculate' enabled, the program can get confused because calculate and write cannot happen at the same time. One will block the other or they'll both happen at the same time! That is a bug in v2.1.0.0 (we don't do much cli testing!) but has been fixed for the next version.

Ah, you should disable auto calculate, it doesn't work too well with the /start cli switch!

ImgBurn already supports MDS files. It's a Windows program and will never handle Apple's DMG format. DAA is some lame (compressed?) custom image format and I'll never support those either.

Well, so far as the program is concerned, your image isn't quite right. If you like, you can send me the first 5mb of it and I'll look into it. 5mb is enough for me to see the file system.

It can only ever be the drive/firmware/media. One of those isn't quite right and hence you're producing coasters. I know the Pioneer can overspeed to 8x but have you tried the media recommended speed of 2.4x?

Sorry, I can't really help with that. You'd need to run ImgBurn within a debugger (something like WinDbg from Microsoft - it's free) and see what's loading when it crashes. I'm guessing you don't even get to see the splashscreen yeah?

No there's not. If it was implemented anywhere, it would be at the shell extension end of things. Maybe Chris could allow the user to optionally add the /START CLI switch to what it already passes to ImgBurn.exe

Press F8 when you think it's stuck on the sync cache bit. The program simply issues the command to the drive and then polls it every second to see if it has finished. If it's polling ok, you'll see loads of entries going into the log - along with status / error codes. That also then means your drive still thinks it's busy and of course that's certainly not ImgBurn's problem and you only have your drive/firmware/media to blame.

I'm sure the burner *should* support that media, so basically it's a case of duff discs or your drive has had it. If there's a firmware update available, make sure you do that before doing anything else... then try again obviously!

As the error was during the finalisation stage (AFTER all the data has been written), that would explain why the verify worked. Verify also only took 19 mins, not 1 hour. I guess your friend wasn't at the machine when the error first popped up. He then did 1 retry before ignoring/cancelling it. There was a 45 minute period between the retries. As you said, the first and most obvious thing to do is update the firmware and try again. Your friend could have just been unlucky and got a dodgy disc.

Well the OCZ one I have is actually designed/made by FSP or something. There are a few companies that have rebranded this one particular model because it was so good - OCZ is one of them. It comes with a decent 3 year warranty and their customer service is very good - you go direct to OCZ. This is the one I have: http://www.ocztechnology.com/products/powe...am_power_supply Oh and yes it comes with all the connectors you could ever need.

Ok, I'll see what I can do

There's nothing wrong with Plextor, I'd personally take Plextor over Samsung any day of the week!

You'd be surprised at how many people can have successful burns and then failures during the verify stage. Drives just aren't very good at reporting write errors on dodgy discs whereby they then fail verify miserably and PIPO scans looks more like rainbows that grass (green = good, orange/red = bad !)

A disc will never burn faster than your drive has been tested / built for. The firmware controls the maximum speed allowed on certain media - and whether it can 'overspeed' on that dye type or not. That said, it could be kinda cool to have a user configurable table where he/she can say with X drive and Y media, set write speed to Z. I'd have to add an 'Auto' speed to the drop down box or something and when it's on that, it uses the custom speeds. If none has been configured for that drive/media combo, it would default to 'MAX'.

I've just got an OCZ 700w one for my new machine. Nice and quiet and is currently powering a pretty beasty machine no problem. I got mine from overclockers.co.uk when it was in the 'this week's specials' bit.