Why doesn't Windows recognise my DVD burner?

[Guest]

Very strange, Check to see if liteon has a firmware update for you burner
then. But on all three systems i have here, I can select my burner drive the
way i told you in the last reply. yours should be the same.

Start menu,
then computer,
right click on the drive icon,
slide down menu to proporties,
RIGHT click on proporties,
A menu will pop up with

General hardware sharing customize RECORDING

Select recording then chose your drive!!

 

[Ben]

Nope - first 4 options only: General, Hardware, Sharing & Customize.

cheers,
Ben

 

[Ben]

I know it works with 3rd-party apps as I've successfully burned with
DeepBurner. Computers, eh!? <Sigh>... why don't these things just *work*?

Ben

 

[Michael Solomon]

I know it works with 3rd-party apps as I've successfully burned with
DeepBurner. Computers, eh!? <Sigh>... why don't these things just
*work*?
Ben

Well, I suppose they would if the PC was a unified platform. There are so
many configurations, so much different hardware, chipsets, software
combintations, so many variebles and so many different ways of doing the
same thing.

 

[Ben]

Resolved! FYI I uninstalled the JMB363 device and allowed Windows to find
drivers online. After installation Device Manager featured an IDE ATA/ATAPI
controller, which was hosting my DVD-RW. Windows is now able to use the
burner as it should. thanks to those who helped here.

cheers,
Ben

 

[Michael Solomon]

Resolved! FYI I uninstalled the JMB363 device and allowed Windows to
find drivers online. After installation Device Manager featured an
IDE ATA/ATAPI controller, which was hosting my DVD-RW. Windows is
now able to use the burner as it should. thanks to those who
helped here.
cheers,
Ben

That's great, Ben, thanks for letting us know how you resolved the issue.

 

[Guest]

I'm having the exact same problem with a similar LITE-ON DVDRW on my 32-bit
vista ultimate system. My model is show in device manager as a:

LITE-ON DVDRW LH-18A1P SCSI CdRom Device

It definitely is the is a case of the device being recognized as a reader
and not as a writer it lists the device type as a "DVD/CD-ROM drive".
Everything Ben has said rings true for my situation as well so I'm assuming
it is the same exact issue. As an additional note this is an IDE drive
connected to the JMicron JMB363 controller on my Asus P5B Deluxe (which isn't
the same as Ben's but is pretty close).

I have flashed the drive with the latest firmware (which is less than a
month old) from LITE-ON, but this hasn't helped at all. I'm wondering if the
easiest solution here is to buy a different brand of drive given it seems
vista just doesn't want to recognize these things...

NOTE: the follow KB article for XP sounds like it is exactly for this type
of issue:
http://support.microsoft.com/kb/316529/

I went looking down the registry path mentioned in this article and once I
get down to the ...CD Burning\Drives sub-key I see (big surprise) no drives
listed. Is there no way to force vista into treating a drive as a DVD-RW
instead of a DVD-ROM?

 

[Guest]

I'm having the exact same problem with a similar LITE-ON DVDRW on my 32-bit
vista ultimate system. My model is show in device manager as a:

LITE-ON DVDRW LH-18A1P SCSI CdRom Device

I didn't see the rest of this thread before I wrote this. As it turns out
my problem was the JMB363 as well and updating its driver has fixed my issue
as well.

So I definitely had the same problem, but I'm fixed now too.

 

[Don]

Resolved! FYI I uninstalled the JMB363 device and allowed Windows to
find drivers online...

Hi Ben. I'm glad you fixed it, but I'm curious where the 'wrong'
drivers came from in the first place. Were they leftovers from a
prior XP, maybe?

 

[Guest]

I just wanted to add I have the same problem with Vista Premium. I installed
two different burners with the same result. Vista will not recognize either
and lists them as SCSI devices. So it looks to me this a common problem at
this point.

Michael,

Yes, I suspect it is just a case of a missing driver. I was hoping that I
had failed to to something obvious, and hence posted this thread.

The device isn't SCSI, it's a conventional ATA/IDE device that is connected
through the JMicron JMB36X controller of the Abit AB9 Pro motherboard.
Since that host can take IDE and SATA devices, perhaps that's the reason the
optical device is picked up as SCSI. If I recall correctly, storage devices
on PCI controller cards sometimes show up as SCSI even if they're not (?),
so perhaps this is the same.

FYI: I've also tried attaching the drive via USB2 (with an IDE->USB
converter) with exactly the same results.

The device itself is using the current firmware available from Liteon's
website although I've not yet contacted them about Vista support.

cheers,
Ben

 

[Guest]

I suspect that this is a much wider problem! I have also had the same
problems with Vista Ultimate. I have an MSI P965 Platinum motherboard with
the JMicron controller in a brand-new hiline system. The boot SATA HDD and
two PATA Pioneer DVD-RW drives were connected to the JMicron controller and
the other (raid 5) drives to the Intel ICHR8 controller. I had to fish
around to download the JMicron driver from MSI to get the system going but
everything seemed OK till I tried to burn a DVD in VideoStudio - no DVD
drives showed up! They were listed as the ubiquitous "SCSI Cd-rom" drives.
I could burn DVDs to them with Nero fine but not any Ulead products. So I
tried MS DVDMaker and same problem! I searched for updated JMicron drivers,
installed them and succeeded in crashing the system (twice) because it
removed the driver from booting. There are lots of threads all over the
internet on these issues - the common thread seems to be the JMicron
controller no matter what the motherboard. In desperation I bought new
Pioneer SATA DVD drives and shifted ALL HDDs and DVDs to the Intel ICHR8
controller, disabled the JMicron controller and suddenly everything came
good. The DVD-RWs are now recognised as such by Device Manager and all
programs. It would seem to me that the JMicron controller or its drivers
have some bugs that have not yet been addressed. Hope this helps others with
a similar problem and relieves some of the frustration.

 

[Guest]

Just as a little extra to my last post, changing the same bootup HDD to the
Intel controller and changing to 2 x SATA DVD-RWs instead of the PATA ones
caused Vista to de-activate my legitimate copy of Ultimate and I had to
explain at length to Microsoft what had happened to get my licenced
activation back. Got the impression that they didn't believe me! Thank you
Mr Gates for being so generous with my GENUINE copy of Vista when the
problems were fundamental issues of compatibility in a new operating system.