I have noticed over the past few weeks a constant problem being posted. It appears that a lot of users are being plagued by their Liteon refusing to read some or all disks. The problem seems to appear over time and can be described in one of many ways:
1). The Liteon will will not recognize previously recorded disks that have not been finalized.
2). Certain recorded events do not show up in the thumbnail view.
3). No media seems to work except RW media.
4). The machine goes into a constant "reading" search and then delivers an "invalid disk" or some other undesirable message.
5). +R media that has been unfinalized goes into an endless "preparing" mode.
I'm sure there are other descriptions of essentially the same problem but these are the ones I can recall.
I am curious about who is having these problems and the configuration of their machines. The following are some observations I have based on reading the various posts.
1) It seems the 5005's that have the "newer" drive (DDW 813S) have more of these problems than machines with the older drive (DDW 451S). It would be good to know if this is true or not.
2). If the above is true, could it be due to the drive FW update that the DDW 813S recently had? Is anyone having this problem with a DDW 813s drive that has not updated their drive FW?
3). The problems seem to be more common on 5005 machines since the most recent machine FW update (1098 with the ES5 file) was released by Liteon. This leads to a logical question, is their a bug in 1098 ES5? Their were similar FW updates posted for other models but I don't know all the FW numbers.
4). Since many of us are hacking the FW, is this problem more common on hacked FW than on standard FW?
I would like to use this thread to gather information on machines having the disk reading problem. This may help us narrow down the issue. If you are having a problem reading previously recorded disks please describe your symptoms and provide the following information.
1). Liteon Model # (5005, 5001, 5006, 5007, 5045, etc)
2). Date of Manufacture
3). Drive model number
4). Drive FW updated? (yes or no)
5). Machine FW version with file extension (1098 ES5 for example)
6). FW Hacked? (yes or no)
7). Hacking method (IloHacker or Manual by Hex Editor or region free via remote control)
8). Hacks implemented (MV removal, 3 Hour mode, region free)
Finally if you are having some of the problems listed above one solution that has worked for a few posters has been to use "protection" for previously recorded programs. This is a limited workaround and does not solve all of the problems listed. You can read about it at the following link:
Let's see if we can't find a pattern to solve this problem for so many users.