LIGHTNING UK!

Ignore the names the program gives the info, those names are taken from the MMC specs. The manufacturer id (on minus format media) and disc id (on plus format media) ARE the dye manufacturer/type.

Sorry to be a pain but can I just double check that the logs you're posting a from when you've opened AND THEN closed imgburn whilst it's running in windbg? WinDbg mentions the address 0040180a in the log, but your screenshot shows a very different address.

lol I only ever discard non existent things! I can see with my own eyes that *something* isn't working properly on your PC and I actually quite like the challenge of finding out what that is I've not even given the beta team a beta version since the final v2.1 release..... far too much testing for me to do first! Maybe once I give them a beta I'll PM you or something.

I'm amazed that even 'Test Mode' is failing! Are you sure there are no visible flaws on the outer edge of those discs?!

There seems to be far too many people making multiple backups these days! Sorry, no, ImgBurn cannot burn to 2 drives at the same time. The best alternative is to queue the image a couple of times, one to each burner.

Ok that says it's a first time exception, so what if you click 'debug' -> 'go' again? When it shows that stuff in the windbg window, has the error popped up properly in the messagebox like it did in the original screenshot?

Just to be clear... The created and modified date fields use the current time/date if not specified. The effective and expiration date fields are zeroed out if not specified.

I don't mind people commenting, I was just saying it's like that on purpose. I took my inspiration from my all time favourite burning program - cdrwin (from Goldenhawk), and not the newbie friendly Nero. ImgBurn's build mode was only ever supposed to be pretty basic, hence why I said if you want/need extra flexibility, stick with Nero.

Ok, you're loading 'ImgTool Burn' there, not ImgBurn. They're different programs too!

Ok so you open windbg yeah? Then File -> Open Executable. Browse to + open ImgBurn.exe Click 'Debug' -> 'Go' so it actually loads up. Then when you close ImgBurn down, it should crash as you say it does and hopefully write the error into the debugger window. Just copy + paste what it says / get a screenshot or something. EDIT: Oh, you might also want to click 'File' -> 'Symbol File Path' and enter the following: srv*C:\Windows\Symbols*http://msdl.microsoft.com/download/symbols then click ok. That'll mean the stack trace should show nice names for the functions being called.

The only thing is, multiple source files should be passed as 1 string but with a pipe (' | ') between then. The reg key thingy doesn't allow for that - hence why you'd need another program (dll) to take care of it and format it properly. For one folder / file, what you've put is ok though

Thinking about it, if you use build mode, it will attempt to add all the padding it can to all the cells in order to see if they'd be ok for a layer break cell. So if act 2 already fits on L1 ok but act 1 is smaller (and hence L0 smaller), then it'll apply padding before act 1 so that it grows to the same size as act 2. So you should really just need to find the first cell of act 2 (or maybe you've done it via chapter... I don't know that encore program) and select that. The layer break dialog box shows you the current time offset within the PGC etc so you could probably guess it from that. EDIT: lol that's pretty much what fordman just said in his first sentence!

It's probably the creation (first date) and then modified (second date) that you're seeing in the ISO9660 filesystem. Both of which are configurable on that same 'Dates' tab.

Hmm ok, maybe it's not failing then! I've just gone over the code again and have tweaked some of the API calls after having a bit of a re-think on how to interpret them! Basically I think one of them was returning 0 for the length of the hash and so it was never really calculated and put into string format - which would then be displayed in the log. Sorry but you'll just have to wait until v2.2.0.0 gets released and then test that one. (No date planned as yet)

No it's not possible. L0 must be bigger than (or equal to) L1. Why do you need to split exactly at the end of an 'act' ? I guess it's because it looks nicer! Sometimes you have to compromise though I'm afraid If the pgc has multiple cells, just use one that leaves L0 > L1. If it doesn't, you'll need to put some in so that you can!

Tools -> ISO -> Display IFO Layer Break Information. If that doesn't find one, you'll have to go back to the raw video_ts folder + files and use ImgBurn's 'Build' mode to make a decent new image.

There's a shell extension out for doing it with a video_ts folder but that's about it. I have no plans to make my own (beyond the existing right click on image files of course). The program itself keeps me busy enough without worrying about extra dll's too

ImgBurn is more simplistic and it was designed that way on purpose. The box represents the root folder, that's all you have to remember. If you want something more flexible, stick with Nero.

Rastus2, How did you get WMIDiag from my saying WinDbg?! They're two completely different programs.

bootsector, ImgBurn is already run using codeguard for a large portion of the beta stage. If there were memory errors to catch, it would find them. ....and not only do I test on XP and 2003, I test on all OS's dating back to 95! Never once have I had an error on closedown like that.

If it's not the discs its the drive / firmware. If the discs are ok and you can't update the firmware, give up and buy a new drive!

lol of course it might just be easier to enable the server service and do a test burn?! If you've got a firewall, you don't really need to worry about file and print sharing anyway. Most people have 2 levels of security, The 1st in their router (+ NAT), and then a 2nd on the actual pc.

This is not an ImgBurn problem, you'd be better off posting on a VSO forum, not here.

What you really need to do is attach a debugger to the exe and see what's going on when it crashes. Something like windbg from microsoft (it's free) would do the trick. Those addresses are not part of my exe so it's probably some extension not playing nicely.

If you're referring to this as the increased size... ... that value is in bytes, not MB. You can't just move the decimal point and call it 4.68GB, it's not. You have to divide by 1024 each time, not 1000. So it's actually 4.36 GB