LIGHTNING UK!

You answered your own question then

Padding means nothing to the video buffer, it's before the video_ts files even start.

Ugh.... times were recently changed and I guess we didn't test this fully! Basically it's applying the daylight savings time bit twice. It's taking your system time as the 'local' time (which already included DST) and then adding DST onto it again, hence you're 1 hour fast. I guess I need to check if DST is already active and then add the appropriate offset in hours. IsoBuster is handy to see what timezone bits are being applied.

Someone already emailed me saying fsecure picks it up as a virus. I believe they were going to mention it to the fsecure peeps that it's not. PECompact is indeed just a compression program.

There are still cli commands you can use for Build mode. Take a look in the readme.

Details, downloads etc on the main website. http://www.imgburn.com Big thanks to the Beta Team for all their hard work with testing / support / ideas / guides. I couldn't do it without you guys!

CloneDVD's newer version of my .dvd file is supported in the up coming v2. That should sort the issues you're currently facing.

That only work / is visible if you have the 'auto export graph data' options enabled in the settings of course

The code for program update stuff is all in it's own thread. There's nothing in there that would stop the GUI from responding because it's totally unrelated. The program update thread could hang all day (as it often does if the servers are busy!) and the program will still work just fine. It'll only hang when you try to close the app down and it waits for the update thread to terminate. Something weird is obviously going on but I'm not that it's 100% that.

and that's why I never do give out dates... except for the other day! What can I say, I'm done with what I wanted to add but something has come to light that 'might' be a potential problem and I need to check it out. People testing are often in different time zones (i.e. 10 hours difference) so it's a real pain in the arse working through stuff. So latest update, it'll be out when it's out. END OF STORY.

Someone else asked me this the other day! Nope, sorry, it's nothing to do with me.

lol, I can't even begin to imagine how it was messing ImgBurn up, care to elaborate?!

Sorry chaps, it would have been today but I've been busy with other stuff and I really can't be arsed to sort it out now... I need sleep! Best I can do is probably tomorrow afternoon/evening when I'm finished at work. So that's approx 16 - 20 hours from now.

Yup, already does all that.

Well it's no extra clicks to just close ImgBurn before turning off the drive. The next version might actually cope ok with it anyway. It has in my testing.

It has never burnt mpeg files. You need to get that mpeg into an image... THEN it can burn it.

If ImgBurn sees a VIDEO_TS folder, the 'Fix Common Problems' option will add an AUDIO_TS folder to the root. It does that regardless of your answer to those prompts - as it's in a totally different part of the program. I'm sure it was just for testing purposes but I don't get why you were burning anything to that +RW in ImgBurn anyway. If it was going to work with anything, it would be with a clean/formatted disc. Unlike hdds, you're not supposed to put an empty filesystem in place before burning this stuff. The device itself always does that. Surely there has to be an option to prepare / wipe an already formatted disc? They can't expect people to use new ones all the time. They always have options for clearning memory cards and I'd have thought they'd do the same for +RW now that they use that media rather than the miniDV tapes. Kinda glad I went for the DCR-HC96 (still miniDV) the other day when I got one for work. I didn't like the idea of burning to disc whilst moving a camera around - the two just didn't seem to fit together very well!

The discs are just normal 8cm discs aren't they? There's nothing on them, and as you can use non-rewritable discs, there never could be!

No, the camera would put the filesystem in place when it initialises the disc or starts the recording. Maybe there's an option in the menu somewhere to wipe / prepare a 'used' disc for recording onto? Traditional formatting just erases all the data and puts zero's on all the sectors. IsoBuster is only useful AFTER you've actually got it recording something to the media - and if windows can't read it.

So if you do a full format in ImgBurn the camera then won't burn to the disc?! Surely it can't expect brand new unformatted media each time?! If it does let you burn again, don't worry too much if window can't read it. Try the disc in ISOBuster or something.

run chkdsk on the hdd via the command prompt. something like: chkdsk C: /R Then download + run 'memtest+' to check your ram is ok. It'll make you a floppy disc to insert when the computer reboots. That error message looks like it's something the kernel is doing. It's certainly in the right region of memory. Is your OS fully patched up on service pack 2?

Indeed, the detection of device arrival/removal probably won't help with that. If it's in the middle of something and you remove the drive, it will error out. If you'd done as you're supposed to and removed it via the system tray icon first, you would have been told it's not possible to do it.

Put the disc in the drive and see if ImgBurn can see it. So long as you don't see 'Device Not Ready' in the status bar you should be able to perform a full format on them.

Nope, not really, there's only 1 way of doing it! Just one quick question though... when you burn, does the Device Buffer progress bar (and the 2 text labels above it) look greyed out (disabled) ?