Book-type for my drive?

[drfsupercenter]

OK, so my new laptop seems to have a drive that ImgBurn can't booktype.

The ID is this:
HL-DT-ST BDDVDRW CT10N WH05

I figure that's LG, right? But yet it gives me an error. I want to have it use DVD-ROM when I burn DVD+R, but it's refusing to let me apply the setting. Is the drive too new for ImgBurn, or what?

[UncasMS]

why do you think that -rom is the ultimate wisdom?

i have used -rom for ages, because it was said to be the most compatible but recently i was proved wrong

burning bd-9 with -rom to be used on a new samsung blu-ray player resulted in unplayable media

booktyped the dvd+r DL media from now with +r and my problems were gone

[drfsupercenter]

I dunno, but I like using -ROM when I burn movies.

So it'll work on old devices like the PS2. This isn't a Blu-Ray BURNER so I'd only be burning DVD... unless you meant a DVD-9?

But is it possible? I could try Nero, it seems to automatically booktype everything it does...

[UncasMS]

automatic booktype should result in the software setting the booktype which refers to the media; i.e. +R for a +r media

and a bd-9 is hd material burned to dvd+dl/dvd9 material btw

[drfsupercenter]

OK, well in my case I'm just burning standard DVD ISOs of video content.

It IS setting it to +R, but is there a way to set it to -ROM with ImgBurn?

[UncasMS]

if imgburn's option to change the booktype to whatever you define does NOT work, then no

i guess you have tried that option already

[LIGHTNING UK!]

What error message do you get if you try and do it manually via the 'LG' tab in the booktype window?

[drfsupercenter]

"Current setting: Unknown (FAILED!)
Reason: Invalid Command Operation Code"

Not sure what that means but it does that whether I have a DVD+R in there or not.

[LIGHTNING UK!]

That means the drive simply doesn't support/understand/know about the command that LG's normally use for the book type stuff. (This is common on laptops where OEM firmware is used in the drive rather than the retail versions)

i.e. it's playing dumb.

You can also run into that problem if your drivers filter the commands that get to the drive - this is more common with controllers running in RAID mode.

Do you see '(RAID)' next to the drive name in the disc info panel on the right when you're in Write mode or whatever? Or does it say '(ATA)' / '(ATAPI)' ?

[drfsupercenter]

It says ATAPI.

So is there any way to use the retail firmware on my drive instead of the OEM one? Would that fix the problem?

[soup]

You could look into a tool called MCSE, (Media Code speed Edit). If your drive is one of those supported.

[LIGHTNING UK!]

Ok and which chipset does your drive controller use?

An intel one?

If so, install the latest Intel Matrix drivers. That should solve the issue if it is indeed a driver one.

[drfsupercenter]

Yes, Intel.

I DO have the Intel Matrix drivers... but obviously that didn't do anything :/

[LIGHTNING UK!]

Assuming you know they're the very latest ones, I'd say you're just unlucky then and your OEM's firmware simply doesn't support it

[drfsupercenter]

Oh, darn it.

So there's no way to update the drive's firmware to non-OEM?