|
Portal Board index » .:: Firmware Flashing ::. » Firmware flashing help
All times are UTC [ DST ]
|
|
Page 1 of 1
|
[ 13 posts ] |
|
| Author |
Message |
|
|
Posted: Mon Mar 31, 2008 12:42 am |
|
Joined: Mon Mar 31, 2008 12:04 am Posts: 3
|
I'm having trouble burning data DVDs: when I put them in and try to burn, it sits there for a few minutes and the drive makes a lot of noise (you can sort of hear it go for a bit, then come to an abrupt halt, then start itself back up again) and then it tells me it's failed to write. It does this regardless of the speed I use. The drive is a sony DVD+-RW DW-Q58A, and the log provided by Nero for onesuch failure is replicated below, in case anyone can make enough sense of it to tell me what's wrong.
Code: 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 10:35:32 AM Nero Version: 6.6.0.8 (Nero Express) Recorder: <SONY DVD+-RW DW-Q58A> Version: UDS2 - HA 0 TA 1 - 6.6.0.8 Adapter driver: <atapi> HA 0 Drive buffer : 2048kB Bus Type : via Inquiry data (1) -> ATAPI, detected: ATAPI Connected to MMC as unknown drive with class-nr : 1 Drive is autodetected - recorder class: Std. MMC recorder CD-ROM: <FI2145T EYK483K >Version: 2.0B - HA 1 TA 0 - 6.6.0.8 Adapter driver: <acjbsu11> HA 1
=== Scsi-Device-Map === DiskPeripheral : SAMSUNG MP0804H atapi Port 0 ID 0 DMA: On CdRomPeripheral : SONY DVD+-RW DW-Q58A atapi Port 0 ID 1 DMA: On CdRomPeripheral : FI2145T EYK483K 2.0B acjbsu11 Port 1 ID 0 DMA: Off
=== CDRom-Device-Map === SONY DVD+-RW DW-Q58A D: CDRom0 FI2145T EYK483K E: CDRom1 =======================
AutoRun : 1 Excluded drive IDs: WriteBufferSize: 73400320 (0) Byte ShowDrvBufStat : 0 BUFE : 0 Physical memory : 503MB (515452kB) Free physical memory: 78MB (80028kB) Memory in use : 84 % Uncached PFiles: 0x0 Use Inquiry : 1 Global Bus Type: default (0) Check supported media : Disabled (0)
30.3.2008 ISO compilation 3:25:06 PM #1 Text 0 File Isodoc.cpp, Line 6172 Iso document burn settings ------------------------------------------ Determine maximum speed : FALSE Simulate : FALSE Write : TRUE Finalize CD : TRUE Multisession : FALSE Burning mode : DAO Mode : 1 ISO Level : 1 (Max. of 11 = 8 + 3 char) Character set : ISO 9660 Joliet : TRUE Allow pathdepth more than 8 directories : TRUE Allow more than 255 characters in path : TRUE Write ISO9660 ;1 file extensions : TRUE 3:25:06 PM #2 Text 0 File Reader.cpp, Line 127 Reader running 3:25:06 PM #3 Text 0 File Writer.cpp, Line 122 Writer SONY DVD+-RW DW-Q58A running 3:25:06 PM #4 ISO9660GEN -11 File geniso.cpp, Line 3293 First writeable address = 0 (0x00000000) 3:25:06 PM #5 Text 0 File Burncd.cpp, Line 3153 Turn on Disc-At-Once, using DVD media 3:25:06 PM #6 Text 0 File DlgWaitCD.cpp, Line 259 Last possible write address on media: 2295103 (510:01.28, 4482MB) Last address to be written: 2235807 (496:50.57, 4366MB) 3:25:06 PM #7 Text 0 File DlgWaitCD.cpp, Line 271 Write in overburning mode: NO (enabled: CD) 3:25:06 PM #8 Text 0 File DlgWaitCD.cpp, Line 2316 Recorder: SONY DVD+-RW DW-Q58A, Media type: DVD+R Disc Manufacturer ID: MBIPG101, Media Type ID: R05, Product revision number: 1 Disc Application Code: 0, Extended Information Indicators: 7 3:25:06 PM #9 Text 0 File DlgWaitCD.cpp, Line 433 >>> Protocol of DlgWaitCD activities: <<< ========================================= 3:25:06 PM #10 Text 0 File ThreadedTransferInterface.cpp, Line 830 Setup items (after recorder preparation) 0: TRM_DATA_MODE1 () 2 indices, index0 (150) not provided original disc pos #0 + 2235808 (2235808) = #2235808/496:50.58 relocatable, disc pos for caching/writing not required/ required, no patch infos -> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2235808 blocks [SONY DVD+-RW DW-Q58A] -------------------------------------------------------------- 3:25:06 PM #11 Text 0 File ThreadedTransferInterface.cpp, Line 1043 Prepare recorder [SONY DVD+-RW DW-Q58A] 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 4578934784, ISRC "" DAO layout: =========== __Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________ 0 | lead-in | 0 | 0x41 | 0x00 0 | 1 | 0 | 0x41 | 0x00 0 | 1 | 1 | 0x41 | 0x00 2235808 | lead-out | 1 | 0x41 | 0x00 3:25:06 PM #12 Phase 24 File dlgbrnst.cpp, Line 1832 Caching of files started 3:25:06 PM #13 Text 0 File Burncd.cpp, Line 4040 Cache writing successful. 3:25:06 PM #14 Phase 25 File dlgbrnst.cpp, Line 1832 Caching of files completed 3:25:06 PM #15 Phase 36 File dlgbrnst.cpp, Line 1832 Burn process started at 8x (11,080 KB/s) 3:25:06 PM #16 Text 0 File ThreadedTransferInterface.cpp, Line 2609 Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0 3:25:06 PM #17 Text 0 File Cdrdrv.cpp, Line 8442 ---- DVD Structure: Physical Format Information (00h) ---- Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050 Book Type: DVD+R (10), Part Version: 1 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: 26053F h End Sector Number in Layer 0: 0 h (LBN: FFFD0000 h, 4193920 MB) Data in Burst Cutting Area (BCA) does not exist Disc Application Code: 0 / 0 h Extended Information indicators: 7 h Disc Manufacturer ID: MBIPG101 Media type ID: R05 Product revision number: 1 Number of Physical format information bytes in use in ADIP up to byte 63: 56 Media Specific [16..63]: 00 00 07 4D 42 49 50 47 - 31 30 31 52 30 35 01 38 ...MBIPG101R05.8 23 54 00 10 FF FF 10 01 - FD F7 00 04 7F FF 08 04 #T.............. FF FF 00 01 FF FD 10 18 - FF EF 00 40 7F FF 81 00 ...........@.... 3:25:06 PM #18 Text 0 File DVDPlusRW.cpp, Line 638 Start write address at LBA 0 DVD high compatibility mode: Yes 3:27:14 PM #19 SCSI -1106 File Cdrdrv.cpp, Line 1435 SCSI Exec, HA 0, TA 1, LUN 0, buffer 0x03480000 Status: 0x04 (0x01, SCSI_ERR) HA-Status 0x00 (0x00, OK) TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND) Sense Key: 0x03 (KEY_MEDIUM_ERROR) Sense Code: 0x73 Sense Qual: 0x03 CDB Data: 0x2A 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x00 Sense Data: 0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x0A 0x00 0x00 0x00 0x00 0x73 0x03 3:27:14 PM #20 CDR -1106 File Writer.cpp, Line 311 Power calibration error 3:27:14 PM #21 Text 0 File ThreadedTransfer.cpp, Line 228 all writers idle, stopping conversion 3:27:15 PM #22 Text 0 File ThreadedTransfer.cpp, Line 222 conversion idle, stopping reader 3:27:15 PM #23 Phase 127 File dlgbrnst.cpp, Line 1832 Generating DVD high compatibility borders 3:27:15 PM #24 Phase 129 File dlgbrnst.cpp, Line 1832 Generating DVD borders completed successfully 3:27:15 PM #25 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=3.00.33a, size=36528 bytes, created 8/24/2006 10:33:36 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)
I suspect the problem is with firmware, and so I went to try and find the update. Nero tells me I'm using UDS2. The firmware page for my drive ( http://forum.rpc1.org/dl_firmware.php?download_id=2113) lists a variety of options, and I'm not sure which to pick. For one, I read in a different thread about someone who apparently had problems because he skipped an intermediate firmware, or something to that effect, so I don't know whether I should just pick the highest number or not. More importantly, they way they have them listed seems to indicate that the first three shouldn't be used with Dell computers (of note to me because my computer is a dell model), because they specifically point out Dell for UDS2, which seems to be the newest model for the Dell computers.
In sum:
1: Of the 5 firmwares on that page, which, if any, should I update to?
2: If firmware is not my problem, does anyone know what is?
|
|
| Top |
|
 |
|
|
Posted: Mon Mar 31, 2008 5:37 am |
|
| dhc014 |
| Past Administrator |
 |
Joined: Sun Sep 02, 2001 1:34 am Posts: 12030
|
Quote: Disc Manufacturer ID: MBIPG101, Media Type ID: R05, Product revision number: 1 [...] Power calibration error
The media is probably of low quality, or not compatible with your burner. It is possible that a more recent firmware would improve the drive's ability to write to this disc.
The firmware version UDS2 is intended for drives in Dell computers. The UDS2 update, from Dell, is the only officially supported update for drives in Dell computers. Using any other firmware would void the drive's warranty in this case. If you do not care about the warranty or it has already expired, then you can try the UYS4 firmware which should be the most recent. Before flashing, you should make a backup copy of your drive's current firmware using mtkflash in DOS or the Flash Utility in Windows.I don't know if the UYS4 updater will let you flash your drive.
_________________ .: Dave | http://dhc014.rpc1.org | email :.
|
|
| Top |
|
 |
|
|
Posted: Mon Mar 31, 2008 7:21 am |
|
Joined: Mon Mar 31, 2008 12:04 am Posts: 3
|
Thanks! I'll give it a try and let you know how it works out.
Update!
I was able to back up my firmware correctly, but when I went to run the UYS4 from here it gave me an...interesting error message.
Are these actually different models, or is the installer program wrong?
(addendum) the 'E' drive it has listed there is virtual, if that would or could make a difference.
|
|
| Top |
|
 |
|
|
Posted: Mon Mar 31, 2008 9:27 am |
|
Joined: Mon Mar 31, 2008 12:04 am Posts: 3
|
Quote: UDS is not UYS firmware. Both are different OEM firmwares. So I can't put a UYS firmware on this drive? Just checking to make sure I understand. Quote: and fix this too: Physical memory : 503MB (515452kB) [b]Free physical memory: 78MB (80028kB) Memory in use : 84 %
...you're saying I need to clear up hard disk space, here, right?
|
|
| Top |
|
 |
|
|
Posted: Mon Mar 31, 2008 3:08 pm |
|
| Puma |
| Administrator |
 |
Joined: Tue May 11, 2004 3:02 pm Posts: 10124 Location: UK
|
Malanis wrote: Quote: UDS is not UYS firmware. Both are different OEM firmwares. So I can't put a UYS firmware on this drive? Just checking to make sure I understand. Quote: and fix this too: Physical memory : 503MB (515452kB) [b]Free physical memory: 78MB (80028kB) Memory in use : 84 % ...you're saying I need to clear up hard disk space, here, right?
safer to leave the firmware as it is, crossflashing to UYS is not advisable, add more RAM to the system,
_________________ Read The FAQ Firmware Request Rules MCSE Thread Utilities
|
|
| Top |
|
 |
|
|
Posted: Tue Apr 01, 2008 1:27 am |
|
| dhc014 |
| Past Administrator |
 |
Joined: Sun Sep 02, 2001 1:34 am Posts: 12030
|
|
The drive is manufactured by Liteon, and Liteon drives will usually work with firmwares from different OEM's if you can get the firmware to flash. You'd probably have to get a binary copy of a UYS* firmware from someone who has it, then flash with the flash utility that you used to create the backup of your firmware.
Try burning those discs at a lower speed, like around 8x or so. I was reading a thread on CDFreaks about how that worked better for some people using the same media that you have.
_________________ .: Dave | http://dhc014.rpc1.org | email :.
|
|
| Top |
|
 |
|
|
Posted: Sun Jan 18, 2009 9:36 am |
|
| clodel |
| New Member |
 |
Joined: Sun Jan 18, 2009 1:31 am Posts: 1 Location: Romania
|
Here is how to update the drive to firmware UYS4. Took me some time to get all the tools but it worked after all. 1. get FlashFix from here http://digi.rpc1.org/flashfix.htm2. get firmware UYS3 from here http://www.opendrivers.com/driver/23588 ... nload.html , as UYS4 will not work in flashfix directly, it has diferent check bits arhitecture. FlashFix will make UYS3 work on any LiteON drive, so it will work on you UDS2 drive. 3. Patch UYS* with FlashFIX , burn the drive with it. Reboot, and now u can burn the drive with UYS4 , which is the newest for DW-Q58A. I have a back-up of my UDS2 firmware, if you need it just buzz.
_________________ "U don't have to be the best, just be better than the rest!"
|
|
| Top |
|
 |
|
|
Posted: Mon Jan 26, 2009 6:49 pm |
|
Joined: Fri Aug 15, 2008 7:30 pm Posts: 2
|
|
Any other place to download UYS3? Both links on the site your referenced don't work.
TIA
|
|
| Top |
|
 |
|
|
Posted: Mon Jan 26, 2009 7:21 pm |
|
Joined: Fri Nov 14, 2008 7:49 am Posts: 7
|
|
| Top |
|
 |
|
|
Posted: Mon Jan 26, 2009 7:25 pm |
|
Joined: Fri Aug 15, 2008 7:30 pm Posts: 2
|
JC Denton wrote: Nope, I'm looking for the UYS3 firmware, the link provided is for a different model and different firmware.
|
|
| Top |
|
 |
|
|
Posted: Wed May 27, 2009 4:41 pm |
|
Joined: Wed May 27, 2009 4:26 pm Posts: 1
|
|
Does anyone have this UYS3 firmware somewhere? Of someone can take a backup from his drive with firmware UYS3?
|
|
| Top |
|
 |
|
|
Posted: Wed May 27, 2009 5:18 pm |
|
| Puma |
| Administrator |
 |
Joined: Tue May 11, 2004 3:02 pm Posts: 10124 Location: UK
|
|
| Top |
|
 |
|
Page 1 of 1
|
[ 13 posts ] |
|
|