Originally posted by harvardja:

---

When I connect my Lite-on, it is not detected as PLDS DG-162DS

Instead it is detected as:

HL-DT-ST
ram.cfm" class="forum_link" target="_blank">DVD-RAM GH22NP20

I looked at my drive, and it indeed says DG-162DS

What's going on?!

---

Originally posted by harvardja:

---

i'm seeing my computer's DVD drive, but not my lite-on drive

yes, i have installed the port i/o driver

Jungleflasher still isn't detecting my lite-on

Is it possible that it is because of my hard drive setting? My hard drive is plugged into the first SATA port, while my lite-on is plugged into the second one

My hard drive is currently in the "Master" Position
Is this effecting the second SATA port?

---

Quote:

---

Geremia's DvdKey method with DosFlash32 with the PC's psu
-----------------------------------------------------------
- disable CD-ROM boot option in BIOS
- connect LiteOn to your PC's power supply unit and SATA port
- power up PC, wait until bootup is finished
- eject tray of the LiteOn and shutdown PC completely
- push the LiteOn tray half in
- power up PC and boot into Windows
- run DosFlash32
- if you read the following:
MTK Vendor Intro failed on port 0x????.
If you choose to resend the command you should turn the drive off and on
after you pressed "Yes".
Do you want to resend the command until the drive responds?
- press 'No'
- choose "LiteOn DvdKey" as flashing task
- choose the COM port number
- press on "LiteOn DvdKey" button
- enter the names of inquiry.bin, identify.bin, key.bin and dummy.bin output files
- if you read the following:
To receive the drive key use Geremia's DvdKey method like follows:
- Connect your drive with a serial cable to the COM port
- Eject drive tray
- Power off drive
- Push drive tray in until it is half open
- Power on drive
- Press "Yes" if you are ready
Are you ready?
- simply press 'Yes' without doing anything of the above, because we
already did that before
- after this DosFlash32 displays your DVD-Key and saves your key and identify data

---

Originally posted by harvardja:

---

I downloaded DosFlash 1.7

In the readme, it states this:

Quote:

---

Geremia's DvdKey method with DosFlash32 with the PC's psu
-----------------------------------------------------------
- disable CD-ROM boot option in BIOS
- connect LiteOn to your PC's power supply unit and SATA port
- power up PC, wait until bootup is finished
- eject tray of the LiteOn and shutdown PC completely
- push the LiteOn tray half in
- power up PC and boot into Windows
- run DosFlash32
- if you read the following:
MTK Vendor Intro failed on port 0x????.
If you choose to resend the command you should turn the drive off and on
after you pressed "Yes".
Do you want to resend the command until the drive responds?
- press 'No'
- choose "LiteOn DvdKey" as flashing task
- choose the COM port number
- press on "LiteOn DvdKey" button
- enter the names of inquiry.bin, identify.bin, key.bin and dummy.bin output files
- if you read the following:
To receive the drive key use Geremia's DvdKey method like follows:
- Connect your drive with a serial cable to the COM port
- Eject drive tray
- Power off drive
- Push drive tray in until it is half open
- Power on drive
- Press "Yes" if you are ready
Are you ready?
Insert probe into R707 hole
- simply press 'Yes' without doing anything of the above, because we
already did that before
- after this DosFlash32 displays your DVD-Key and saves your key and identify data

---

Would that work?

Where does the CK3 probe come in, if at all?

---

Originally posted by harvardja:

---

i figured this might be possible :(
but the PLDS (lite-on) drive is detected in my bios!!! i figured it would still work...

I have a dell dimension e510, how do i find out if it is compatible or not?

Also, for some reason, in jungle flasher, the checkbox for the ck3 usb connector is grayed out! It wasn't earlier, but after multiple restarts it's now grayed out. did I screw something up? what could have caused this?

thanks for any help

---

Originally posted by harvardja:

---

so my chipset is incompatible?

---