LIGHTNING UK!

Whilst doing the scans for the media forum, I often had one that registered high PIF's or some POF's when the graph didn't show anything of the sort. For me though, it was normally just a case of closing DVDInfoPro down again, ejecting + reinserting the disc and then scanning again. It's hard to say where the fault lies as I would expect dvdinfopro to just display the info the drive is returning - there shouldn't really be any room for error. It is weird and very annoying though so hopefully one of them will fix it! I didn't try going between CDSpeed and DVDInfoPro as I knew a rescan in DVDInfoPro would probably fix the issue too - and therefore it wouldn't have been a fair test. If in doubt, submit it to the dvdinfopro 'mantis' bug tracking page and have a moan

Ignore the 'write protected' bit... that's my problem due to some bad memory copying on my part. The other two are yours though I'm afraid. The drive is reporting errors while it's off doing its own thing - in this case, closing the track and finalising the disc. ImgBurn simply issues those commands and then polls the drive to check it's status. The drive is then reporting those errors in the data it replies with. This could well be a problem with iSCSI.

You must be reading the size figures from somewhere weird. The image won't grow when you burn it - except by a max of 15 sectors (so 15 * 2048 bytes) if you burn to DVD+R and the filesize (in sectors) is not a multiple of 16.

I'll look into that multisession stuff, thanks pfeerick

DIP says that for mine too but that's just because thats what the drive reports. It CAN be flashed though.

If it won't burn DVDs and won't burn CDs.... time for a new external DVD writer!

Nah, that's not really 'funny', there are lots of times people could use & in path names etc and the same problem would appear.

It's up to the developer how to deal with DVD+RW. I don't have to make it want fully formatted media, I just chose to. The disc would actually burn fine with the format in the 'started' / 'in progress' states. I can't think of any reason why you want to leave the format in limo - hence why I've designed ImgBurn such that it doesn't do that. As I said earlier, if another program issues the 'format' command again (some probably do), it resets the format status and so to become fully formatted, you'll need to do a proper full erase (but it's a format really) in ImgBurn.

If it as an ISO image it would already work. You're just missing what's going on in the background.

ah, because the '&' symbol makes a keyboard shortcut type thing (accelerator) when displayed on the screen. I'd need to do a string replace on '&' with '&&' to get around that. I'll add it to my todo list.

If another program formats the disc again (and doesn't wait for it to finish), it'll reset the format status and you'll have to do it again.

The listview truncates long strings and puts '...' at the end of the line. If you hover over it with the mouse, the tooltip displays the full string. To change that behaviour i'd have to capture when the column header size changes and then basically make the listview custom draw, giving it my own modified text strings. I think that's a bit overkill to to be honest. The line in the information box is also truncated (in the method you require) and the tooltip on that displays the full line. Eject per queued item is an idea I guess.... but not high up on my priority list right now. Also, what happened to all the other options in that dialog?! Or perhaps you're still running 1.0.0.0?

nothing really, just the the firmware kinda matches with dells one. It's not a very common drive either and most post I looked at on other forums were from people with dell machines - or at least they were given the same info - to try the latest dell firmware.

For DVD you can just query the drive and it gives you a nice list. For CD you have to mess around trying to set the write speed to a given value, and then try to read it back. If it's the same, it supports that value. Just seemed a lot of messing around for very little gain - and it wouldn't be 100% reliable either.

Yes, it is supposed to burn them - and does. It doesn't however, report the write speeds supported for CD media.

Correct, they're not. They're not reported in the same way DVD ones are - or rather they're not reported at all!

If those messages are in the status bar, the log wont show anything and nor will the window on the right. Your drive must be failing to initialise the discs - and until it does that, no software can do anything with them. If you're on the latest firmware and have tried various discs (like you say you have)... chances are, the drive is faulty. Do try updating the firmware first though. It would appear yours is a Dell machine - yeah? http://ftp.us.dell.com/rmsd/NECND353_v104C.zip The above links to the latest firmware for the NEC ND-3530A

I did try burning an Audio cd to CDRW and seeing how my program reacted. It worked fine and asked if I wanted to erase before it would burn a normal data image. The erase happens before the disc space is checked so I'm not really sure where your initial problem is coming from.

I can't imagine sonic/prassi providing me with the specs for how to use it....so it's highly unlikely this will ever happen. Feel free to contact them on my behalf though! Lots of apps use the burning sdk from sonic/prassi, that's why it seems widespread. It's quite possible a version even comes built into windows.

That's actually my fault blu. The exe compression program has killed the one I made especially for file associations. This is fixed in the next release.

I 18:54:49 [2:4:0] IBM DVRM00203 A127 (P:) (SCSI) I 18:54:49 CDB: 51 00 00 00 00 00 00 00 20 00 I 18:54:49 CDB Interpretation: Read Disc Information E 18:54:49 SENSE: 70 00 05 00 00 00 00 0A 00 00 00 00 20 00 00 00 00 00 E 18:54:49 SENSE Interpretation: Invalid Command Operation Code I 18:54:49 [2:4:0] IBM DVRM00203 A127 (P:) (SCSI) I 18:54:49 CDB: 52 01 00 00 00 01 00 00 30 00 I 18:54:49 CDB Interpretation: Read Track Information E 18:54:49 SENSE: 70 00 05 00 00 00 00 0A 00 00 00 00 20 00 00 00 00 00 E 18:54:49 SENSE Interpretation: Invalid Command Operation Code That's your problem(s) right there. The drive doesn't appear to support the two most basic commands! In all honesty, that kinda sucks. I will try and build in a workaround.

ok, next thing to do for me.... Load ImgBurn without the disc in the drive. Press the F8 key to enable debug mode. Put DVDRAM disc in the drive. Wait until you get that 'Disc Not Empty' message in the status bar again. Press F8 to disable debug mode. Save the log - via 'File' -> 'Save'. Attach log to your next post. Once you've done that, I'll take a look and see why the drive is reporting the information that it is.

Hmm could you please copy + paste the info from the window on the right within ImgBurn. Oh and just confirm you're on 1.3.0.0 When I put a DVDRAM in my drive (one that already has data on it), it all works as it should do. The statusbar reads: 'Ready (Disc Not Empty)' and the big Write button is enabled. All it can really be is that your drive isn't recognising the disc as a dvdram disc - as will be shown in the 'Current Profile' text.

Disc not empty just gets put in the status bar when the programs finds a filesystem on the disc, but the disc supports 'direct overwrite' (i.e. can be written to without needing to erase it each time). It should still let you burn ok, it'll just overwrite whatever's already on there.

No it won't do it at the same time, nor do i see that happening any time soon. The queue (see the guide) provides the best alternative.