This question is published in the hardware section for the Samsung SE-S184M. Click here to view full specs.

I have the Samsung SE-S184M external burner and I can't seem to burn any DVD-Rs.  DVD Rs work just fine, but I cant burn any DVD-Rs.  I use ImgBurn.  Any ideas on what's wrong?

@ bballboi948,

Welcome to the Forum.

Have you ensured that your Samsung SE-S184M DVD Burner has the newest most current up to date available Firmware?

Are you receiving any Error Narrative Notifications or Error Codes when attempting to Burn DVD-R Media? If so provide all available information. Providing an IMGBurn Log of an attempted failed DVD-R Media Burn would be helpful.

What is the Media MID (Manufacture ID and Media Code) (Example: TYG02) of the DVD-R Media you are attempting to use? To obtain the Media MID of the DVD-R Media suggest using a software utility program similar to DVDInfo (http://www.dvdinfopro.com) or DVD Identifier (http://dvd.identifier.cdfreaks.com).

Regards,
bjkg

Hi and Welcome!could you please describe more detailled? Do you get any error message or is the burned disc not playableThese drives have problems with DVD-R, at least with stock Samsung SH-S182M firmwares. Apart from avoiding DVD-R, the only solution at the moment would be a different OEM firmware (TS-H652M KC03 from Samsung Korea) that has to be flashed by force. Any warranty of the drive is void then.

If the drive suffers from the lead-in bug, then even latest official Samsung firmware doesn't help. There are some OEM firmwares which are not affected.
SH-S182D --> TS-H652D KC03 or Philips SPD 2412T P1.5
SH-S182M --> TS-H652M KC03 (perhaps also Philips SPD6002T P1.3, but not yet verified)

Michael

Here is the log file from ImgBurn:

I 19:01:45 Operation Started!
I 19:01:45 Source File: C:\Documents and Settings\Tom\Desktop\Config.1.4.US.iso
I 19:01:45 Source File Sectors: 712,880 (MODE1/2048)
I 19:01:45 Source File Size: 1,459,978,240 bytes
I 19:01:45 Source File Volume Identifier: CDROM
I 19:01:45 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING
I 19:01:45 Source File File System(s): ISO9660 (Bootable), Joliet
I 19:01:45 Destination Device: [0:0:0] TSSTcorp CD/DVDW SH-S182M SB05 (G (USB)
I 19:01:45 Destination Media Type: DVD-R (Disc ID: MXL RG01) (Speeds: 2x)
I 19:01:45 Destination Media Sectors: 2,298,496
I 19:01:45 Write Mode: DVD
I 19:01:45 Write Type: DAO
I 19:01:45 Write Speed: 4x
I 19:01:45 Link Size: Auto
I 19:01:45 Test Mode: No
I 19:01:45 OPC: No
I 19:01:45 BURN-Proof: Enabled
I 19:01:46 Filling Buffer... (40 MB)
I 19:01:47 Writing LeadIn...
W 19:02:01 Failed to Write Sectors 448 - 479 - Reason: The semaphore timeout period has expired.
W 19:02:01 Retrying (1 of 20)...
W 19:02:04 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 19:02:04 Retrying (2 of 20)...
W 19:02:10 Retry Failed - Reason: The semaphore timeout period has expired.
W 19:02:10 Retrying (3 of 20)...
W 19:02:12 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 19:02:12 Retrying (4 of 20)...
W 19:02:14 Retry Failed - Reason: The semaphore timeout period has expired.
W 19:02:14 Retrying (5 of 20)...
W 19:02:16 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 19:02:16 Retrying (6 of 20)...
W 19:02:16 Retry Failed - Reason: The semaphore timeout period has expired.
W 19:02:16 Retrying (7 of 20)...
W 19:02:19 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 19:02:19 Retrying (8 of 20)...
W 19:02:19 Retry Failed - Reason: The semaphore timeout period has expired.
W 19:02:19 Retrying (9 of 20)...
W 19:02:21 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 19:02:21 Retrying (10 of 20)...
W 19:02:28 Retry Failed - Reason: The semaphore timeout period has expired.
W 19:02:28 Retrying (11 of 20)...
W 19:02:30 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 19:02:30 Retrying (12 of 20)...
W 19:02:32 Retry Failed - Reason: The semaphore timeout period has expired.
W 19:02:32 Retrying (13 of 20)...
W 19:02:34 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 19:02:34 Retrying (14 of 20)...
W 19:02:37 Retry Failed - Reason: The semaphore timeout period has expired.
W 19:02:37 Retrying (15 of 20)...
W 19:02:40 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 19:02:40 Retrying (16 of 20)...
W 19:02:43 Retry Failed - Reason: The semaphore timeout period has expired.
W 19:02:43 Retrying (17 of 20)...
W 19:02:45 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 19:02:45 Retrying (18 of 20)...
W 19:02:47 Retry Failed - Reason: The semaphore timeout period has expired.
W 19:02:47 Retrying (19 of 20)...
W 19:02:49 Retry Failed - Reason: Power On, Reset, or Bus Device Reset Occurred
W 19:02:49 Retrying (20 of 20)...
W 19:02:54 Retry Failed - Reason: The semaphore timeout period has expired.
E 19:03:07 Failed to Write Sectors 448 - 479 - Reason: The semaphore timeout period has expired.
I 19:03:07 Synchronising Cache...
W 19:03:07 Synchronise Cache Failed! - Reason: Logical Unit is in process of becoming ready
W 19:03:07 Retrying (1 of 3)...
W 19:03:07 Retry Failed - Reason: Logical Unit is in process of becoming ready
W 19:03:07 Retrying (2 of 3)...
W 19:03:07 Retry Failed - Reason: Logical Unit is in process of becoming ready
W 19:03:07 Retrying (3 of 3)...
W 19:03:07 Retry Failed - Reason: Logical Unit is in process of becoming ready
E 19:03:46 Synchronise Cache Failed! - Reason: Logical Unit is in process of becoming ready
I 19:03:46 Synchronising Cache (Last Attempt!)...
E 19:03:46 Synchronise Cache Failed! - Reason: Not Ready To Ready Change - Medium May Have Changed
W 19:03:47 User opted to skip the 'Close Track/Session/Disc' functions.
E 19:03:47 Failed to Write Image!
E 19:03:47 Operation Failed! - Duration: 00:02:01
I 19:03:47 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 0 KB/s (0.0x)

@ mciahel:

How would I go about flashing my firmware? I don't know much about this stuff @ all...but I'm pretty sure I have the latest firmware.

Thanks for the advice so for.

What are your system specifications?

I have a Compaq Presario V3000z laptop. It has an AMD Turion 64 X2 1.81 GHz, 2GB Ram, 80 GB HD. Window XP

Have you just recently tried DVD-R, or used it for a while with the error just now occurring?

A couple of things I suggest:

Try uninstalling and re-installing the USB port drivers. [In other words, remove the USB ports and hubs from the Device Manager].

Check your USB cable connection.

Make sure you are not using a power profile meant to save power, as this may interrupt USB transfer.

It may not be easy, but try removing the actual drive from the Samsung enclosure, install it into a desktop, and try burning from there.

No, DVD-Rs have never worked. I have been using DVD+Rs and have no problems. I recently tried a DVD-R and it didn't work and then I thought about it, and DVD-Rs never worked.

Hi,Have you tried other DVD-R media?
I am asking since there seems to be something wrong with media support for this particular disc (supported at only 2x, but write attempt at 4x).
At least, since the burn fails, this is not the Lead-In issue I mentioned before.
You might have a look into the FAQ I mentioned in my signature. Latest official firmware is SB06. But I am not sure if this will cure your problem. The Lead-In issue I mentioned previously is not solved with any official firmware yet (but with some OEM firmwares - go figure). But at the moment, this is of minor relevance.

Michael

Hi,I doubt this will help, since DVD+R seem to work without problems

I was just going on a quick search where, somehow, the user couldn't burn -R but could burn +R. At least one of those ended up solving the issue in some cases.