Sony DW-d26a, LiteOn 1673s Nightmare

Manju · February 14, 2017, 1:25am

My initial problem is that burning a DVD at 8x would result in hanging while burning or an error while cosing the DVD. I’ve pasted the Nero log below. I crossflashed to the LiteOn 1673S firmware using xflash_utility to mod it to work on my drive and it said it succeeded and showed up as a liteon in the dropdown. I figured everything went well. The drive disappeared after a reboot though. I’m going to try and put it back using mktflash. What’s aggravating is that I used EEPROM utility to dump the old firmware as a backup and it appears that it was invalid (only 1k dumped) despite saying successful.

I was going to flash back to Sony. I only found JYS2 online. Can anyone send me JYS3?

What’s going on with both the backup and flash saying successful and the drive being hosed?

After I reflash, I’ll try with the DVD-RW as master and CD as slave. Hopefully windows will put them both in DMA mode. I’ll try ASPI 4.6 as well. Any other suggestions?

Windows XP 5.1
IA32
WinAspi: -
ahead WinASPI: File 'C:\Program Files\Ahead\Nero\Wnaspi32.dll': Ver=2.0.1.74, size=164112 bytes, created 10/26/2004 5:35:34 PM 
Nero Version: 6.6.0.8
Recorder:             <SONY DVD RW DW-D26A>     Version: JYS3 - HA 0 TA 1 - 6.6.0.8
 Adapter driver:      <atapi>                   HA 0
 Drive buffer  :      2048kB
 Bus Type      :      default (0) -> ATAPI, detected: ATAPI 
CD-ROM:               <LITE-ON  CD-ROM LTN-489S >Version: 8DS2 - HA 0 TA 0 - 6.6.0.8
 Adapter driver:      <atapi>                   HA 0

=== Scsi-Device-Map ===
CdRomPeripheral      : LITE-ON CD-ROM LTN-489S          atapi Port 0 ID 0  DMA: On 
CdRomPeripheral      : SONY DVD RW DW-D26A              atapi Port 0 ID 1  DMA: Off
DiskPeripheral       : WDC WD400BD-75JMC0               atapi Port 1 ID 0  DMA: On 
DiskPeripheral       : ST3200822A                       atapi Port 1 ID 1  DMA: Off

=== CDRom-Device-Map ===
LITE-ON CD-ROM LTN-489S    R:   CDRom0
SONY DVD RW DW-D26A        W:   CDRom1
=======================

AutoRun : 1
Excluded drive IDs: 
WriteBufferSize: 74448896 (0) Byte
ShowDrvBufStat : 0
BUFE           : 0
Physical memory     : 510MB (522316kB)
Free physical memory: 116MB (119316kB)
Memory in use       : 77 %
Uncached PFiles: 0x0
Use Inquiry    : 1
Global Bus Type: default (0)
Check supported media : Disabled (0) 

10.7.2005
Burn DVD Image
4:16:20 PM	#1 Text 0 File Reader.cpp, Line 127
	Reader running
	
4:16:20 PM	#2 Text 0 File Writer.cpp, Line 122
	Writer SONY     DVD RW DW-D26A   running
	
4:16:20 PM	#3 Text 0 File Burncd.cpp, Line 3153
	Turn on Disc-At-Once, using DVD media
	
4:16:20 PM	#4 Text 0 File DlgWaitCD.cpp, Line 259
	Last possible write address on media:  2298495 (510:46.45, 4489MB)
	Last address to be written:            2286016 (508:00.16, 4464MB)
	
4:16:20 PM	#5 Text 0 File DlgWaitCD.cpp, Line 271
	Write in overburning mode: NO (enabled: CD)
	
4:16:21 PM	#6 Text 0 File DlgWaitCD.cpp, Line 2316
	Recorder: SONY DVD RW DW-D26A, Media type: DVD-R
	 Disc Manufacturer: CMC MA - G. AE1
	 Disc Application Code: 64, Disc Physical Code: 193
	
4:16:21 PM	#7 Text 0 File DlgWaitCD.cpp, Line 433
	>>> Protocol of DlgWaitCD activities: <<<
	=========================================
	
4:16:21 PM	#8 Text 0 File ThreadedTransferInterface.cpp, Line 830
	Setup items (after recorder preparation)
	 0: TRM_DATA_MODE1 (2 - CD-ROM Mode 1, ISO 9660)
	    2 indices, index0 (150) not provided
	    original disc pos #0 + 2286017 (2286017) = #2286017/508:0.17
	    not relocatable, disc pos for caching/writing not required/not required, no patch infos
	    -> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2286017 blocks [SONY     DVD RW DW-D26A]
	--------------------------------------------------------------
	
4:16:21 PM	#9 Text 0 File ThreadedTransferInterface.cpp, Line 1043
	Prepare recorder [SONY     DVD RW DW-D26A] for write in CUE-sheet-DAO
	DAO infos:
	==========
	 MCN: ""
	 TOCType: 0x00; Session Closed, disc fixated
	 Tracks 1 to 1:
	   1: TRM_DATA_MODE1, 2048/0x00, FilePos             0             0    4681762816, ISRC ""
	DAO layout:
	===========
	 __Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________
	       0 |  lead-in |   0 |    0x41 | 0x00
	       0 |        1 |   0 |    0x41 | 0x00
	       0 |        1 |   1 |    0x41 | 0x00
	 2286017 | lead-out |   1 |    0x41 | 0x00
	
4:16:21 PM	#10 Phase 24 File dlgbrnst.cpp, Line 1832
	Caching of files started
	
4:16:21 PM	#11 Text 0 File Burncd.cpp, Line 4040
	Cache writing successful.
	
4:16:21 PM	#12 Phase 25 File dlgbrnst.cpp, Line 1832
	Caching of files completed
	
4:16:21 PM	#13 Phase 36 File dlgbrnst.cpp, Line 1832
	Burn process started at 8x (11,080 KB/s)
	
4:16:21 PM	#14 Text 0 File ThreadedTransferInterface.cpp, Line 2609
	Verifying disc position of item 0 (not relocatable, no disc pos, no patch infos, orig at #0): write at #0
	
4:16:21 PM	#15 Text 0 File DVDR.cpp, Line 2194
	Recording mode: Sequential Recording Mode
	
4:16:21 PM	#16 Text 0 File Mmc.cpp, Line 21235
	Set BUFE: Power-Burn -> ON , Adapt writespeed to disc : ON
	
4:16:21 PM	#17 Text 0 File DVDR.cpp, Line 2340
	Start write address at LBA 0
	DVD high compatibility mode: Yes
	
4:16:21 PM	#18 Text 0 File Cdrdrv.cpp, Line 8430
	---- DVD Structure: Physical Format Information (00h) ----
	Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
	 Book Type: DVD-R   (2), Part Version: 5
	 Disc Size: 120 mm,      Maximum Rate: <not specified> (F h)
	 Number of Layers: 1,    Track Path: Parallel Track Path (PTP),  Layer Type: recordable
	 Linear Density:         0,267 um/bit,  Track Density:  0,74 um/track
	 Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
	 End Physical Sector Number of Data Area:      0 h
	 End Sector Number in Layer 0:                 0 h (LBN: FFFD0000 h, 4193920 MB)
	 Data in Burst Cutting Area (BCA) does not exist
	  Start sector number of the current Border-Out: 0 h
	  Start sector number of the next Border-In:     0 h
	 Media Specific [16..63]:
	      00 30 00 10 20 00 00 00 - 00 00 00 00 00 00 00 00    .0..............
	      00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00    ................
	      00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00    ................
	
4:16:21 PM	#19 Text 0 File DVDR.cpp, Line 5317
	Drive: SONY     DVD RW DW-D26A  
	Book Type request [LO]: DVD-ROM
	Book Type setting not supported for the loaded disc type
	
4:17:18 PM	#20 Text 0 File Cdrdrv.cpp, Line 1287
	16:17:18.578 - SONY DVD RW DW-D26A\H0 T1 : Queue again later
	
4:17:35 PM	#21 SCSI -500 File Cdrdrv.cpp, Line 1435
	SCSI Exec, HA 0, TA 1, LUN 0, buffer 0x049E0600
	Status:     0x02 (0x03, SCSI_ABORTED)
	HA-Status   0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
	TA-Status   0x00 (0x00, OK)
	Sense Key:  0x05 (KEY_ILLEGAL_REQUEST)
	Sense Code: 0x26
	Sense Qual: 0x02
	CDB Data:   0x5C 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x0C 0x00 0x00 0x00 
	Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00 
	            0x00 0x00 0x00 0x00 0x26 0x02 
	
4:17:43 PM	#22 SCSI -400 File Cdrdrv.cpp, Line 1435
	SCSI Exec, HA 0, TA 1, LUN 0, buffer 0x04470000
	Status:     0x04 (0x01, SCSI_ERR)
	HA-Status   0x00 (0x00, OK)
	TA-Status   0x02 (0x01, SCSI_TASTATUS_CHKCOND)
	Sense Key:  0x00 (KEY_NO_SENSE)
	Sense Code: 0x00
	Sense Qual: 0x00
	CDB Data:   0x2A 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x20 0x00 0x00 0x00 
	Sense Data: 0x70 0x00 0x00 0x00 0x00 0x00 0x00 0x0A 
	            0x00 0x00 0x00 0x00 0x00 0x00 
	
4:17:43 PM	#23 CDR -500 File Writer.cpp, Line 311
	SCSI command aborted
	SONY DVD RW DW-D26A\H0 T1
	
4:17:43 PM	#24 Text 0 File ThreadedTransfer.cpp, Line 228
	all writers idle, stopping conversion
	
4:17:44 PM	#25 Text 0 File ThreadedTransfer.cpp, Line 222
	conversion idle, stopping reader
	
4:17:44 PM	#26 Text 0 File DVDR.cpp, Line 2603
	EndDAO: Last written address was 31
	
4:17:44 PM	#27 CDR -1114 File WriterStatus.cpp, Line 167
	Reset occurred
	SONY DVD RW DW-D26A\H0 T1
	
4:17:44 PM	#28 TRANSFER -24 File WriterStatus.cpp, Line 167
	Could not perform end of Disc-at-once
	
4:17:44 PM	#29 Phase 38 File dlgbrnst.cpp, Line 1832
	Burn process failed at 8x (11,080 KB/s)
	

Existing drivers:
File 'Drivers\ADPU160M.SYS': Ver=v3.60a (Lab01_N(johnstra).010529-2218), size=101888 bytes, created 8/17/2001 12:07:32 PM 
File 'Drivers\PXHELP20.SYS': Ver=2.03.16a, size=20576 bytes, created 9/14/2004 6:50:10 AM (Prassi/Veritas driver for win 2K)
File 'Drivers\atapi.sys': Ver=5.1.2600.2180 (xpsp_sp2_rtm.040803-2158), size=95360 bytes, created 8/3/2004 8:59:44 PM (Adapter driver for rec)

Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)

code65536 · February 14, 2017, 3:31pm

It “disappeared” after the reboot? If the drive showed up successfully as a 1673S immediately following the flash, then the flash was successful and the drive is probably okay and that the problem is probably on the OS side of things.

Does BIOS detect the drive?
Does Nero InfoTool detect the drive?

As for JYS3, there is no known copy of it floating around. The JYS2 that is available was sent to us by someone who dumped it from their drive. Sony almost never posts firmwares for its DW- line of drives (only its DRU- line of drives) and thus DW- firmwares are very rare and are obtained only by people backing up their firmware and sending them to us or to dhc014. As a reminder to others reading this thread, never assume that you can find a firmware on the Internet to use for a revert-flash! But in your case, I’m not sure that reverting to a JYSx firmware is the solution…

Manju · February 14, 2017, 3:31pm

Nero Info Tool doesn’t see it and neither does Windows.

After initial reboot neither my CDROM (master) nor my DVD writer (slave) showed up. I switched them so now the DVD is master and now my CDROM shows up, but not the DVD yet.

Now I get a message during boot that says “Drive 2 not found: Parallel ATA, PATA-0(PRI IDE MASTER)”

The channel is enabled in the BIOS. I might have to try this drive alone on the channel and dig up a different IDE cable too.

The fact that my BIOS backup using EEPROM Tool was only 1k instead of 1024k makes me wonder if there’s some communication problem with the drive or interference from the CDROM on the same chain. Also makes me wonder if the drive was flaky to begin with and needs to be RMA’d (after I get the original firmware back on there (or sneak the S2 version on there and hope they don’t notice)… please PM me anyone that might have it).

I crossflashed this drive specifically because it seems to be a Sony outcast. I wasn’t too happy about that. I figured it would live a happier life as a LiteOn.

code65536 · February 14, 2017, 3:31pm

The firmware is 1024 KB, the EEPROM is 1 KB. They’re two different things.

Second, crossflashing was not necessary because the 1673S and D26A are the same drive. Crossflashing is necessary if you wanted to flash it to a 1693S, but not to a 1673S. But anyway, how did you do the flash? What did you use to do the flash? What firmware did you load? Did you flash the right file?

If the drive is not being detected by BIOS, then I guess the drive did misflash. But that shouldn’t have happened. If there was something wrong with your system setup, it simply won’t flash (instead of misflash). The only way I know of that it would’ve misflashed is if you loaded a corrupted firmware or if you loaded the wrong firmware (i.e., if you loaded a 1653S firmware instead of a 1673S firmware). In any case, you should do a MtkFlash recovery now. For this recovery, just use JS0B.BIN. There’s no reason why a 73S firmware shouldn’t work on the D26A, so you might as well recover using the latest 73S firmware. If you download JS0B from our site, it will include JS0B.BIN that you can use for recovery. In the future, just running JS0B.stock.exe from our website would probably be an easier (and less prone to error) way to flash.

Manju · February 14, 2017, 3:31pm

I ran the JS0B from LiteOn’s site through http://digi.rpc1.org/flashfix.htm and then ran LiteOn’s flasher and it didn’t complain about anything and it said it was a LiteOn drive after it was done. Wouldn’t it have just failed to even start if the flash were encrypted? I had downloaded the UPX unpacker so I think it decompressed ok. Weird. I didn’t realize that the flashes on the site were all ready for cross flashing. I’ll try mktflash with your JS0B.

What’s the EEPROM backup for? Do any tools erase that?

Thanks.

code65536 · February 14, 2017, 3:31pm

I ran the JS0B from LiteOn’s site through http://digi.rpc1.org/flashfix.htm and then ran LiteOn’s flasher and it didn’t complain about anything and it said it was a LiteOn drive after it was done.

That is so weird. When you mentioned the XFlash Utility earlier in the thread, I had thought that maybe you tried to do things the long way, but you did it the right way, all right. (JS0B.stock.exe on our website is more or less identical to what you did, so forget about my comment on that)

If a FlashFixed official LiteOn updater failed to update correctly, then the problem is probably with Windows. Windows is a harsh environment for working with hardware, but most of the time, it doesn’t cause problems. Now and then, it does. So just re-flash the drive with JS0B.BIN and MtkFlash, and things should be fine.

But I’m still scratching my head over this because

D26A->1673S is a perfectly fine and safe process… hundreds (perhaps more) of people have done this without incident, and this is the first and only one that I’ve seen
Usually, when there’s a misflash, the flasher will not report that the flash was successful. Instead, it will hang at the Inquiry phase. In order for it to pass the Inquiry phase, the flash had to be successful. This because right after a flash, the drive is reset (basically, the drive is rebooted, just like it gets rebooted when the computer itself is rebooted) and then after the drive is rebooted, the flasher does an inquiry to make sure that the drive rebooted fine. So if the drive rebooted fine right after the flash, then why did the drive fail to reboot correctly when the computer rebooted? That part doesn’t make any sense. Could there have been a freak power surge during the system reboot that killed the drive? That would’ve been one heck of a bad coincidence.

PS: Looking at the original log that you had with JYS3, it seems that the 8x burning problem that you had was because DMA was turned off for the drive. Turning DMA on would’ve solved your problem.

PPS: FlashFix and crossflash are not quite the same things, so when you said crossflash earlier instead of FlashFix, it caused some confusion

What’s the EEPROM backup for?

In the event of an accidental misuse of one of the EEPROM Utility’s other features. And there are a few other uses for EEPROM backups as well.

Manju · February 14, 2017, 3:32pm

Turns out that the IDE cable was marginal. Replaced it and the drive came up fine (and in Ultra DMA mode). Burned at 8x just fine. Thanks for your help. It was good just to have someone say the drive should be fine so I would troubleshoot other stuff.

code65536 · February 14, 2017, 3:32pm

Glad to hear that you got that sorted out!

I have to admit, the IDE cable is such a trivial component that it never even for a second crossed my mind that it might’ve been a problem, even though if I do a search for it on the forums, I see that you’re not the first to have had cable problems. I don’t think I ever would’ve found the solution if I were in your shoes. :o