Jump to content


Photo

Lite-on Problems


  • Please log in to reply
5 replies to this topic

#1 butterblum

butterblum

    X-S Enthusiast

  • Members
  • 3 posts

Posted 19 August 2009 - 03:25 AM

I am trying to flash a lite-on drive (old firmware) and am so far unsuccessful. Jungleflasher recognizes my lite-on, and my serial adapter's status is "ready". When I test my homemade probe in hyperterminal, it works. However, whenever i try to extract my dvd key, I am given a WARNING Serial Data is Bad. What is wrong here. Any help? Thanks

#2 postal worker

postal worker

    X-S X-perience

  • Members
  • PipPip
  • 484 posts
  • Xbox Version:v1.1
  • 360 version:unknown

Posted 19 August 2009 - 04:18 AM

invalid serial?

your tray half open?

i had this problem too

have you moved msinet.ocx into the system32/drivers folder?

i only ask because i had that problem and i finally did that and it worked but then. i was also reading the part in the ck3tool thing.

#3 sanel_

sanel_

    X-S Enthusiast

  • Members
  • 1 posts

Posted 19 August 2009 - 04:40 AM

I had the same error with mine, JungleFlasher shows up everything is reading and ready and everything done by directions and then this "WARNING Serial Data is Bad".. I gave up since there is no right solution yet that I found..


#4 butterblum

butterblum

    X-S Enthusiast

  • Members
  • 3 posts

Posted 19 August 2009 - 05:22 PM

Where is msinet.ocx? And how do i know that the tray is halfway in? I usually throw it in to some random position.

#5 postal worker

postal worker

    X-S X-perience

  • Members
  • PipPip
  • 484 posts
  • Xbox Version:v1.1
  • 360 version:unknown

Posted 20 August 2009 - 04:10 PM

on my half open it is usually right around when the circle becomes the long rectangle.

i guess if the program isn't asking for msinet.ocx you may not need it.

#6 hassle

hassle

    X-S Senior Member

  • Members
  • PipPip
  • 194 posts
  • Location:Fresno, CA
  • Interests:Games
  • Xbox Version:v1.0
  • 360 version:none

Posted 21 August 2009 - 06:52 AM

i noticed that when i was using jungleflasher 1.51 i never got that error. But ever since i upgraded to 1.6 i get it everytime, but the drive always works just fine.

just letting ya know.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users