LIGHTNING UK!

If what you've got won't fit on your media, yes it will need to be compressed so that it does.

1.2 isn't going to be anything major anyway. Just fixing a few bits here and there and adding some smaller new features. It's not going to have ISO building or anything big like that in it.

Then they use the Tools -> Drive -> Erase bit.

Added this lastnight actually - along with the advanced settings for BenQ drives! Damn my crystal ball is good! EDIT: Oh, it will need to be enabled/disabled everytime though if its not stored in the drives eeprom or wherever. I avoid sending custom commands before a burn because I'm forced to do them by device id strings - and these could change meaning newer drives wont work automatically etc. That just makes it into a bit of a headache supporting them all and updating for every new drive release.

ImgBurn 1.0.0.0 (and all versions of DVD Dec) didn't verify the data, just that the sectors were readable. I thought that had been made pretty clear already. I verify every single burn I do (more to test the program than check the media!) and I've never had a failure. As such, this isn't a global issue with some basic coding error - and therefore it's not one I can fix as quickly as I might like to.

If anything, you'd use the Ricoh tab as that's what old NEC firmwares with booktype setting support used. Failing that, you might find a patched firmware that allows for changing the booktype via the cdfreaks 'nec' forum.

Nope, that is actually quite helpful! Ok, I'm going to need some more details about the filesystem and stuff (locations of files within the image) and the easiest way to get that info is to actually get a chunk of the filesystem and do it myself! Use this little tool to grab 5 meg (hence the name 'Grab5m' !) of the image file in question and then email it to the address in ImgBurn's About box. Usage of the tool is simply, open a dos/command prompt window and just type: Grab5m your_image.iso output_image.iso I know dos based stuff is old but hopefully you're ok with that. If not, I can always help you. Can you also please provide the exact size of the image in bytes. Load the image in ImgBurn and get a screenshot of the main window, that'll do! Thanks and happy new year to you too grab5m.zip

Bloody hell, I really must scroll down the bottom of the forum once in a while! I always miss birthday reminders! Happy Birthday ya old git

Ah ok, I already had some debug code in there that may help us. Before you attempt to load the ISO PgcEdit made, press F6. You should/may then get some additional lines in the log. Just copy + paste it all. Thanks

Oh, my mate said the 800 has a special connector/wire that goes into the phone. The headphones then plug in to another socket (on the other end of that wire) that's up by your neck (once you've got the earphones in!) - kinda like where some have their digital displays or volume controls. He said it's just a normal 3.5mm jack plug - but didn't have the headphones infront of him to be 100% sure on that

Right click the drive drop down box. Or Tools -> Drive -> Erase. EDIT: Oh perhaps you're talking about explorers context menu? i.e. where you right click on a drive? I'm not sure windows is clever enough to have options depending on media type. I'd only ever seen the ability to know if a DVD disc is in the drive. Either way, I'm not looking to extend the explorer integration!

Happy fire/pirate year?!

When it's doing the Sync Cache thing, press F8 when you've decided it's stuck and see if commands are still being sent to the drive. This is a sure fire way of knowing if the drive just cant finish burning on that media (doesn't fully support it) or if your drivers crashed and the drive has stopped responding to commands. If the commands keep being added to the log, it's a drive/firmware/media issue. If they're not, your machine/drivers/drive died.

Great, thanks for that. If you can, please keep that image on your machine until I've had a chance to add some debug code to my routines that'll enable me to extract (and show in the log) some info about what ImgBurn is doing. I'll then send you a special version. I can't see anything that would cause an issue... but clearly something is!

Oooh rerun pgcedit.... If it's not too much trouble that would be excellent! Thanks!

I'd be interested to see where exactly PgcEdit put the layerbreak. Any chance of a screenshot from the window where you selected it? I can't really give you an answer until I know some additional info - not only that, I'd like to know why I couldn't get the LB from the IFO data!!!

Ahh the blue avatar is back! lol I'm pretty sure volvofl10's initial comment was very tongue in cheek... but of course that's hard to get across in plain text. The smilie at the end does go some way towards helping though. oh and I've (we've) no issues here about external links. Unless of course, they're blatently advertising a crummy program somewhere! Anyway, no harm done I hope. We're a nice bunch really... honest!

I know quite a few people with that white Sony one. I guess that's the 800i....but I only know the black k750i by number! Anyway, the phone itself is excellent. Nice menus, excellent camera and more features than you could ever hope to learn! We've had many side splitting times out in town of an evening getting pissed and mucking around with bluetooth to random peoples phones! (but you're probably a little more grown up than we are ) You can listen to those little mp3 players that run off a single AAA battery for hours on end so I don't see why it would die quickly on a phone. I'm sure the life of the battery in the phone would exceed that of a AAA.

hmmm I'd have expected pinnacle to allow you to output to and ISO file / or burn to disc / or output to video_ts files. If you files will fit on a DVD5 (single layer) disc, you can use 'ImgTool Classic' from www.coujo.de If they're bigger than that (i.e. DVD9 double layer), you have to use PgcEdit from http://www.videohelp.com/~r0lZ/pgcedit/index.html PgcEdit can cope with single layer and double layer so you could really just use that one all the time. Its the only one that will make a proper double layer image with a nice layer break though. btw, they're both FREE tools.

You can burn with any options selected and at any speed. The Write Speed Graph is totally separate from all that stuff. It's just from ImgBurn taking 'samples' of the current speed at regular intervals (defaults to ever 100 milliseconds). WOPC is just a drive thing so I don't think it's possible to have incompatibilities with it.

The original question wasn't exactly aiming towards 'how do i get imgburn to work with dvdshrink', or I'm sure Rotary would have seen the 'sticky' post at the top. Rotary, seems weird seeing you here without - what I remember as - a blue strange avatar?!

You should leave WOPC enabled. It basically checks the quality of the burn DURING the burn. If it notices the quality is sub-par, it'll slow it down until error rates are within acceptable limits. It really decent media, you can safely disable WOPC and then the drive will reach max speed (i.e. 16x). Sometimes it always falls short of that - even with proper 16x speed rated media. cdfreaks forum might be of use to you here. They talk about this sort of thing in the BenQ subforum quite a lot. If you're bored, perform another burn with WOPC enabled and then (within ImgBurn), click 'Display Graph Data Using DvdInfoPro' from within the File menu. You'll need DVDInfoPro installed of course - free version is fine. You can then see exactly how the drive is changing the write speed at the burn progresses.

Yeah but 2.4x isn't a real/valid speed for DVD-R. It's like the drive doesn't really support those discs. Mind you, my Pioneer 110 lists 3.4x, 6x, 8x as supported speeds for the new 8x Ricoh DVD+RW media! 3.4x ????!! WTF! lol

DVDShrink isn't capable (AFAIK) of building proper DL images. So basically, you need to output to a VIDEO_TS folder and then use PgcEdit to create the ISO file. You can have PgcEdit feed that ISO to ImgBurn, or just manually load ImgBurn and the file yourself.

hmmm well spotted corn! Seems that firmware doesn't like them 100% I've got a bunch on order from svp so I'll be able to test for myself soon enough.