LIGHTNING UK!

ImgBurn writes those keys based on your settings when the application itself is closed. So you need to run ImgBurn as Admin for it to work.

That sure does sound like an odd bios option. Almost as if you're disabling / enabling the controller.

It all depends on what you have at the moment and what you want out the other end! When asking questions it really makes things easier if you include as much info as possible... otherwise it just means we have to keep asking for it and that gets a bit frustrating at times. As the saying goes, "Help us help you".

Have it burn what to a format the 360 can ready? The 360 plays DVD Video discs and ImgBurn can burn those just fine. Just remember that ImgBurn is NOT a conversion tool so it burns your file as-is (i.e. you must have a VIDEO_TS folder full of IFO/BUP/VOB files if you want to burn a DVD Video disc). With the latest dashboard updates, it can also play avi files that use the divx codec. (those can be burnt with ImgBurn too)

Put it back on SPTI too. You don't want / need to be using ASPI. The error gives you a clue as to where the error lies... CRC ERROR (ULTRA-DMA/32) So basically you have DMA issues - and the FAQ deals with those. Changing the cable, removing other drives from the channel and testing one a at time is all part of the fault finding process.

The crappy DL discs are always hit and miss. Just because it 'works' doesn't mean it's actually giving you a good burn. You could have been borderline for ages and only now (as the drive wears out or the media quality dropped a bit) are you having actual failures. Yes it says on the spindle where they're from. If you're buying online, check with the place to see what their current stock is (if it's not quoted anyway).

Glad you're happy it's working how I said it did FYI and in case I hadn't mentioned it before, the new version does it by branch (or by level, the choice is yours).

You're still not using Verbatim DVD+R DL 2.4x (MKM-001 Made in Singapore) discs. We recommend them because they work, not for the fun of it. Please at least give them a shot. If it still doesn't work after that then we'll try and help you some more.

CUE files are NOT (by default anyway, although it is possible) saved as unicode files (hardly any (if any?!) applications support them). ImgBurn DOES support them though

Why don't you have a VIDEO_TS.IFO file in your VIDEO_TS folder? Is it really not there if you look for it via explorer? What files DO you see in that folder? The logs can be found via the 'Help' menu within ImgBurn - but that's not really gonna help here.

Yes Please do as the big pink box at the top of this screen says and post the log.

The drive is just stuck. Try cleaning it or invest in a new one (that drive is super old now!). You should actually avoid rewritables unless you have good reason to use them. They're never anywhere near as good a write once media.

I did think you'd have disabled it seeing as you knew there was an issue with it, but thought I'd mention it anyway for anyone else reading this at a later date. That's just how Borland (Codegear) applications work. ImgBurn is written in C++ Builder. The panels within frmMain are the different screens you see when you click between modes and the controls should be children of them - I've never looked at it via winspector so you're on your own with that.

Playing them on a player means nothing. If the player supports playing AVI files then the order of actual file data doesn't matter. It looks in the file system to find start LBA of the file and then jumps to that location. It doesn't matter where on the disc that LBA is. To a DVD player, DVD Video VTS files aren't files at all, they're all just one long chunk of data - that's why the order is important with those files (and only those files). VIDEO_TS goes first, then the VTS sets. IFO goes before the VOB files, then the BUP comes after those (and then onto the next VTS). Now back to the program... Ok well basically what happens is that the program sorts the folders into alphabetical order, a level at a time (as shown above). It starts from the root dir in the internal tree structure and asks it for a list of it's folders (sorted alphabetically). That list is then worked though, repeating the same basic thing each time. i.e. Initial processing list.. -> Root Query Root's folders... List then looks like this... -> Root Folder 1 Folder 2 Finished with Root so we move onto next folder in list. Root -> Folder 1 Folder 2 This time we query Folder 1 for a list of folders... List then looks like.. Root -> Folder 1 Folder 2 Folder 1a Folder 1b Finished with Folder 1, move onto next folder in list... Root Folder 1 -> Folder 2 Folder 1a Folder 1b This time we query Folder 2 for a list of folders... List then looks like.. Root Folder 1 -> Folder 2 Folder 1a Folder 1b Folder 2a Folder 2b etc etc.. Once it's got that list of folders it goes through each one and assigns the appropriate LBA to files (also sorted alphabetically). Then when writing the files to the ISO they're sorted by LBA (as that's clearly how they need to be processed / written!). So normally, they'd all be in that same alphabetical order - but if you've got the optimisation option enabled, the fake LBA for duplicate files will of course mean the order can change from being alphabetical.

You realise the OP was talking about AVI files etc yeah? Why are you then talking about DVD Video stuff? The ordering of those files is handled differently to the rest. I already specified the order in which the file data is burnt in my previous post, I don't think you're actually seeing what you think you're seeing.

Well personally I'd keep the burn speed to 8x max. So long as the buffers are full all the time you shouldn't have any problems. Try it and see!

Yes what you've done there is correct. ImgBurn will build a new file system based on the files it finds on the disc - that's the whole idea behind Build mode. It's using the operating system to read the file data which is different to using Read mode and getting a sector by sector (1:1) copy of the disc. So yes, it is on-the-fly but it's not the same a doing a disc copy on-the-fly. The 2 discs will have identical file data but the file system data will be different. (you don't see file system data, it's used by the OS to figure out what's on the disc, that's all).

There's no on-the-fly disc copy mode, no. You need to Read it and then Write it. Stick with Nero if you really need a 1:1 disc copy option. You could work around it by using Build mode and pointing the 'Source' box at your source drive and (when 'Output' is set to 'Device'), select your destination drive. That's basically the same thing only the file system gets recreated.

Always burn at 4x in that drive. The 2.4x write strategy seems a bit dodgy... in fact, even 4x is a bit hit and miss (well, with my drive anyway). Hopefully the next firmware update will resolve these issues.

Start your own thread please Mohammad Atfan Iqbal.

ImgBurn see's my hddvd just fine, the issue here is that I perhaps don't detect HDDVD capabilities properly in 2.3.2.0. This is purely cosmetic and it should still work fine. The drive will only show up in Read / Verify modes as it's just a reader and not a burner.

You can't see the file system stuff, all you see is actual file data and that's not what I was talking about. The LBA of the file data is not important at all for the type of data the OP is burning. The (current version of the) program burns the actual files in alphabetical order within their respective folders. It does this one level at a time. i.e. root\1 root\2 root\3 root\1\1 root\1\2 root\2\1 root\3\1 root\3\2 root\1\1\1

It doesn't matter who the discs are branded by. If the dye they're using is rubbish then they'll still be rubbish.

The drive isn't showing any supported write speeds so I doubt it can handle them at all. If a firmware update doesn't fix it (or isn't available) then you're stuck. Buy Verbatims in future.

Look at the 'supported write speeds' text in the info panel on the right. It doesn't matter what you tell the program to write at, the drive will only ever write at those speeds. The program doesn't control the actual speed, the writer does. Please stop it with the abuse towards other member or I'll make sure the door slams behind you on your way out.