All Questions & Answers for this product

• New!CD burning problem
Question by dendrikas, Tuesday 26th of August 2008 22:51
Hi. I have recently reinstalled windows and my cdrom reads cds but doesnt write them. In last windows it worked. I have changed cable, tested another cd rom with my computer, problem seems in configurations and drivers i think.

im using windows xp
samsung sh s182d cd-dvd rom
intel motherboard
40 pin ide cable from cd rom to motherboard
nero8 and sometimes windows explorer to burn data.

heres the log from nero8 with ANOTHER cd rom, but log is same as the one that was with my samsung rom.

1K22-0867-0795-66M4-5205-1567-****

Windows XP 5.1
IA32
WinAspi: -

NT-SPTI used
Nero Version: 8.3.6.0
Internal Version: 8, 3, 6, 0

Recorder: Version: NK0A - HA 1 TA 0 - 8.3.6.0
Adapter driver: HA 1
Drive buffer : 2048kB
Bus Type : default
CD-ROM: Version: 1.01 - HA 1 TA 2 - 8.3.6.0
Adapter driver: HA 1

=== Scsi-Device-Map ===
DiskPeripheral : ST3250620AS atapi Port 0 ID 0 DMA: On
ArrayPeripheral : MARVELL Virtual Device 1.00 mv61xx Port 4 ID 25 DMA: Off
CdRomPeripheral : LITE-ON COMBO SOHC-5232KNK0A mv61xx Port 4 ID 4 DMA: Off
CdRomPeripheral : YJ5874U UJA720H 1.01 acseo8wv Port 5 ID 0 DMA: Off

=== CDRom-Device-Map ===
LITE-ON COMBO SOHC-5232K E: CdRom0
YJ5874U UJA720H K: CdRom2
=======================

AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 83886080 (0) Byte
BUFE : 0
Physical memory : 2029MB (2078256kB)
Free physical memory: 1419MB (1453508kB)
Memory in use : 30 %
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

26.2.2008
CD-ROM (ISO)
9:19:39 AM #1 Text 0 File SCSIPTICommands.cpp, Line 450
LockMCN - completed sucessfully for IOCTL_STORAGE_MCN_CONTROL

9:19:39 AM #2 Text 0 File Isodoc.cpp, Line 6713
Iso document burn settings
------------------------------------------
Determine maximum speed : TRUE
Simulate : FALSE
Write : TRUE
Finalize CD : FALSE
Multisession : FALSE
Burning mode : TAO
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

9:19:39 AM #3 Text 0 File Burncd.cpp, Line 3238
LITE-ON COMBO SOHC-5232K
Buffer underrun protection activated

9:19:39 AM #4 ISO9660GEN -11 File Geniso.cpp, Line 3349
First writeable address = 0 (0x00000000)

9:19:40 AM #5 Text 0 File ThreadedTransferInterface.cpp, Line 1027
Removed 2 run-out blocks from end of track 0. Length: 253022 -> 253020.

9:19:40 AM #6 Text 0 File Burncd.cpp, Line 3568
Turn on Track-At-Once, using CD-R/RW media

9:19:40 AM #7 Text 0 File ThreadedTransferInterface.cpp, Line 1027
Removed 2 run-out blocks from end of track 1. Length: 253022 -> 253020.

9:19:40 AM #8 Text 0 File FilesystemSettingsValidator.cpp, Line 142
FS Settings: using validator 'CUDFSettingsValidatorCD'
ParamMode = 'automatic', changing UDF partition type from 'physical' to 'physical'
Changing UDF revision from '1.02' to '1.02'

9:19:40 AM #9 Text 0 File ThreadedTransferInterface.cpp, Line 1027
Removed 2 run-out blocks from end of track 1. Length: 253022 -> 253020.

9:19:40 AM #10 Text 0 File DlgWaitCD.cpp, Line 311
Last possible write address on media: 359848 ( 79:59.73)
Last address to be written: 253021 ( 56:15.46)

9:19:40 AM #11 Text 0 File DlgWaitCD.cpp, Line 323
Write in overburning mode: NO (enabled: CD)

9:19:40 AM #12 Text 0 File DlgWaitCD.cpp, Line 2948
Recorder: LITE-ON COMBO SOHC-5232K;
CDR code: 00 97 26 56; OSJ entry from: Lead Data Inc.
ATIP Data:
Special Info [hex] 1: D0 00 A0, 2: 61 1A 38 (LI 97:26.56), 3: 4F 3B 4A (LO 79:59.74)
Additional Info [hex] 1: 00 00 80 (invalid), 2: 00 80 00 (invalid), 3: 00 80 80 (invalid)

9:19:40 AM #13 Text 0 File DlgWaitCD.cpp, Line 497
>>> Protocol of DlgWaitCD activities: <<<
=========================================

9:19:40 AM #14 Text 0 File ThreadedTransferInterface.cpp, Line 754
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 ()
2 indices, index0 (150) not provided
original disc pos #0 + 253022 (253022) = #253022/56:13.47
relocatable, disc pos for caching/writing not required/ required
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 253020 blocks [E: LITE-ON COMBO SOHC-5232K]
--------------------------------------------------------------

9:19:40 AM #15 Text 0 File ThreadedTransferInterface.cpp, Line 956
Prepare [E: LITE-ON COMBO SOHC-5232K] for write in TAO
DAO infos:
==========
MCN: "
TOCType: 0x00; Session Closed, disc not fixated
Tracks 1 to 1: Idx 0 Idx 1 Next Trk
1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 307200 518496256, ISRC "
DAO layout:
===========
___Start_|____Track_|_Idx_|_CtrlAdr_|_____Size_|______NWA_|_RecDep__________
-150 | lead-in | 0 | 0x41 | 0 | 0 | 0x00
-150 | 1 | 0 | 0x41 | 0 | 0 | 0x00
0 | 1 | 1 | 0x41 | 253022 | 0 | 0x00
253022 | lead-out | 1 | 0x41 | 0 | 0 | 0x00

9:19:40 AM #16 Text 0 File ThreadedTransferInterface.cpp, Line 1027
Removed 2 run-out blocks from end of track 1. Length: 253022 -> 253020.

9:19:40 AM #17 Text 0 File SCSIPTICommands.cpp, Line 240
SPTILockVolume - completed successfully for FSCTL_LOCK_VOLUME

9:19:40 AM #18 Text 0 File Burncd.cpp, Line 4359
Caching options: cache CDRom or Network-Yes, small files-No (<64KB)

9:19:40 AM #19 Phase 24 File dlgbrnst.cpp, Line 1767
Caching of files started

9:19:40 AM #20 Text 0 File Burncd.cpp, Line 4481
Cache writing successful.

9:19:40 AM #21 Phase 25 File dlgbrnst.cpp, Line 1767
Caching of files completed

9:19:40 AM #22 Phase 28 File dlgbrnst.cpp, Line 1767
Speed measurement started

9:19:40 AM #23 Text 0 File ThreadedTransferInterface.cpp, Line 2673
Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0

9:19:40 AM #24 Text 0 File ThreadedTransfer.cpp, Line 269
Pipe memory size 590400

9:19:50 AM #25 Phase 29 File dlgbrnst.cpp, Line 1716
Speed measurement completed: 317.9x (47,694 KB/s)

9:19:50 AM #26 Phase 36 File dlgbrnst.cpp, Line 1767
Burn process started at 24x (3,600 KB/s)

9:19:50 AM #27 Text 0 File ThreadedTransferInterface.cpp, Line 2673
Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0

9:19:51 AM #28 Text 0 File MMC.cpp, Line 22530
Set BUFE: Buffer underrun protection -> ON , SMART-BURN : ON

9:19:51 AM #29 Text 0 File ThreadedTransfer.cpp, Line 269
Pipe memory size 83836800

9:19:58 AM #30 SPTI -1114 File SCSIPassThrough.cpp, Line 214
CdRom0: SCSIStatus(x02) WinError(0) NeroError(-1114)
CDB Data: 0x2A 00 00 00 00 00 00 00 20 00 00 00
Sense Key: 0x06 (KEY_UNIT_ATTENTION)
Sense Code: 0x29
Sense Qual: 0x00
Sense Area: 0x08 00 06 00 00 00 00 0A 00 00 00 00 29
Buffer x09c50040: Len x10000
0x00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

9:19:58 AM #31 CDR -1114 File Writer.cpp, Line 306
Reset occurred
E: LITE-ON COMBO SOHC-5232K

9:19:58 AM #32 SPTI -1033 File SCSIPassThrough.cpp, Line 214
CdRom0: SCSIStatus(x02) WinError(0) NeroError(-1033)
CDB Data: 0x35 00 00 00 00 00 00 00 00 00 00 00
Sense Key: 0x02 (KEY_NOT_READY)
Sense Code: 0x04
Sense Qual: 0x01
Sense Area: 0x08 00 02 00 00 00 00 0A 00 00 00 00 04 01

9:20:10 AM #33 CDR -1033 File WriterStatus.cpp, Line 322
Drive not ready
E: LITE-ON COMBO SOHC-5232K

9:20:10 AM #34 TRANSFER -18 File WriterStatus.cpp, Line 322
Could not perform EndTrack

9:20:10 AM #35 CDR -201 File WriterStatus.cpp, Line 325
Invalid write state
E: LITE-ON COMBO SOHC-5232K

9:20:10 AM #36 TRANSFER -18 File WriterStatus.cpp, Line 325
Could not perform EndTrack

9:20:10 AM #37 Text 0 File MMC.cpp, Line 17306
start Close Track #2

9:20:10 AM #38 Phase 38 File dlgbrnst.cpp, Line 1767
Burn process failed at 24x (3,600 KB/s)

9:20:10 AM #39 Text 0 File SCSIPTICommands.cpp, Line 287
SPTIDismountVolume - completed successfully for FSCTL_DISMOUNT_VOLUME

9:20:13 AM #40 Text 0 File Cdrdrv.cpp, Line 11450
DriveLocker: UnLockVolume completed

9:20:13 AM #41 Text 0 File SCSIPTICommands.cpp, Line 450
UnLockMCN - completed sucessfully for IOCTL_STORAGE_MCN_CONTROL


Existing drivers:

Registry Keys:
HKLMSoftwareMicrosoftWindows NTCurrentVersionWinLogonAllocateCDROMs : 0 (Security Option)

Thanks for any help.
Answer the question right now!


 
Answer a question? Login first, or become a member here!


• Problema Firmware con Samsung SH-S182D
Question by cesc4, Wednesday 20th of August 2008 17:06
Salve ragazzi, ho putroppo un problema col mio masterizzatore dvd samsung sh-s182d e con dvd-r. Ho comperato online, un mese fa dvd-r ritek g05 da 8x visto il prezzo economico. Ne ho masterizzato finora una decina e senza problemi, dopo un paio di giorni ho cominciato a bruciarne parecchi tanto che ne sto perdendo un casino. Ho mandato una mail al negozio spiegandogli il problema e ovviamente loro non potevano dirmi altro che quei supporti sono di ottima qualità e che avrei dovuto provare ad aggiornare il firmware per "risolvere" il problema. Ho fatto come detto portandomi il firmware originale SB02 a quello aggiornato SB06, pochi giorni di scritture perfette e di nuovo stesso problema, metto il supporto, finisce la scrittura e mi ritrovo con i dati illegibili, masterizzo video, alcune anteprime le fa vedere, altre ci passano anni, il masterizzatore si pianta in caricamento e mi impalla windows. Ho letto su questo forum che c'era il firmware SB04 corretto dal bug del lead-in sui dvd-r e vedendo che le problematiche coincidevano col mio masterizzatore ho deciso di installare questo firmware patchato ma pochi minuti fa ne ho sfornato un altro bruciato, che devo fa'?
Vi prego di aiutarmi se potete, ho notato che in questo forum c'è più gente esperta di altri forum sparsi per la rete....

Vi ringrazio
Answer by geno888, Wednesday 20th of August 2008 18:15
Benvenuto nel forum

Fondamentalmente ci sono due problemi. Quello specifico modello di masterizzatore ha sempre avuto un difetto coi dischi -R, e tutti gli aggiornamenti del firmware non sono mai riusciti a risolverlo: il drive non scrive correttamente il lead-in durante la masterizzazione. Anche se il firmware "patchato" dicevano che aveva risolto il problema, in realtà il bug persiste e non è mai stato risolto.

Da notare che coi dischi +R il problema non esiste assolutamente e il masterizzatore funziona benissimo.

Il secondo problema è che i dischi Ritek non sono affatto di così grande qualità, ma hanno il brutto difetto di degradarsi molto velocemente nel tempo (quando il drive riesce a scriverli correttamente senza bruciarli fin dall'inizio).

I suggerimenti che ti posso dare, quindi, sono tre.




• Utilizzare con quel masterizzatore solo dischi +R e non -R
  
• A prescindere dal + o - R, evitare comunque di usare dischi Ritek, vista la loro scarsa qualità
  
• Comprare un masterizzatore diverso se hai proprio l'esigenza di usare dei dischi -R
  
Answer by cesc4, Wednesday 20th of August 2008 19:20
ciao geno, grazie. tu cosa mi consigli di fare? il rimborso dei ben 150 supporti lo escluderei, maledizione a loro quando gli ho ordinati , quelli non rimborsano neanche una briciola se decido di comprarmi un altro masterizzatore, tu cosa mi consigli? un ottimo prodotto ovviamente.... che non abbia questi bug del cacchio, l'ho presa nel c**o troppe volte.
Answer by geno888, Thursday 21st of August 2008 18:45
La soluzione migliore secondo me è prendere dei dischi di qualità, ma di tipo +R, che il samsung 182 (io ne ho uno e quindi parlo per esperienza diretta) li masterizza senza problemi.

Purtroppo i Ritek non c'è nessun masterizzatore che li potrà rendere buoni, perché sono nativamente delle fetecchie

Li puoi sempre usare come dischi da esperimento o comunque per metterci dentro dei dati poco importanti sapendo però che al primo problema di lettura li dovrai rifare.

Se vuoi comunque prendere un nuovo masterizzatore, io suggerisco un Pioneer 112 o 115, e se poi vuoi testare i dischi masterizzati, allora la scelta deve ricadere necessariamente su un liteon.

Se ne hai la possibilità, poi, sia il Pioneer che il liteon sono una bella accoppiata e prenderli tutti e due potrebbe essere un'altra soluzione

Ma comunque la precendenza dovresti darla all'acquisto di dischi di qualità

I Verbatim sono i più facili da reperire
Answer by cesc4, Friday 22nd of August 2008 02:20
ascolta un'ultima domanda....

com'è possibile che di quei ritek alcuni sono riuscito a masterizzarli e gli altri no? gli ho persino verificati. non è che ora ci ho perso tutto? intendo i dati masterizzati su quei dvd sono andati persi....
Answer by geno888, Saturday 23rd of August 2008 00:39
Il problema dei ritek è che si rovinano molto velocemente nel tempo.

I dischi che sono venuti bene andrebbero verificati e rifatti appena danno segni di difficoltà di lettura. Il TRT di cd-dvd speed è un test sufficiente
Answer the question right now!


 
Answer a question? Login first, or become a member here!


• SH-S182D - Huge Pi layer break?
Question by TonyTi, Wednesday 20th of August 2008 13:59
I recently bought some DL discs for the first time and I did a scan and found the following result



As you can see the first layer is perfect, and the second is horrendous. I have always had good scans with SL discs. I burnt at 2.4x and read/burnt with SH-S182D.

Why am I getting such high Pi? Is it a drive that is no longer much use, or is it because of poor reading from the drive?

Thanks

Tony
Answer by Arachne, Wednesday 20th of August 2008 15:19
Welcome to the forum

I never use either of my 182D's for scanning, so I don't know how good they are at it, but that does seem bad, even allowing for some rise on the second layer.

Do you or a friend have a LiteOn or BenQ you can scan with?

Unfortunately, I don't have any MKM 001 to test with on my own Sammy.
Answer by TonyTi, Wednesday 20th of August 2008 15:32
Thanks for the warm welcome.

I did have another drive, an NEC one I believe. I had to remove it as it was burning and readly badly. I don't have access to another PC, so I guess I can't shed any more light on it?
Answer by Arachne, Wednesday 20th of August 2008 15:45
Most NEC drives are good for doing what's called a Transfer Rate Test in CD-DVDSpeed, but as it's not installed I guess that's not an option?

Does the disc playback (if it's a movie) OK, or can you read the data back to the HDD without error (if it's a data disc)? If yes to either one of these, I wouldn't worry too much.

But other members, who've perhaps used their 182Ds for scanning, may be able to shed more light, so hang in there
Answer by TonyTi, Wednesday 20th of August 2008 15:58
Arachne said:
Most NEC drives are good for doing what's called a Transfer Rate Test in CD-DVDSpeed, but as it's not installed I guess that's not an option?

Does the disc playback (if it's a movie) OK, or can you read the data back to the HDD without error (if it's a data disc)? If yes to either one of these, I wouldn't worry too much.

But other members, who've perhaps used their 182Ds for scanning, may be able to shed more light, so hang in there


I would install the NEC, but it was virtually in heaven when I removed it lol. I did complete a scan with another DVD with the same media, and I had surprising results. The first layer was a mess, but the second layer was virtually no Pi. So the opposite of the first screencap.

I'm completing a 'benchmark' test right now which is what I think you may be talking about? But with my Samsung.

And yes the DVDs I have burnt have always played fine on my standalone DVD player for films.

Thanks

Tony
Answer by Arachne, Wednesday 20th of August 2008 16:01
Yep, benchmark is fine

Save the Benchmark window as a .png file when it's done (little floppy shaped icon in the top right), and attach it to your post afterwards.

If it's a nice smooth upward curve, plus the fact that the discs play fine, I wouldn't worry too much (even though Samsung drives are pretty forgiving of some disc errors, as they're excellent readers)
Answer by TonyTi, Wednesday 20th of August 2008 16:13
Arachne said:
Yep, benchmark is fine

Save the Benchmark window as a .png file when it's done (little floppy shaped icon in the top right), and attach it to your post afterwards.

If it's a nice smooth upward curve, plus the fact that the discs play fine, I wouldn't worry too much (even though Samsung drives are pretty forgiving of some disc errors, as they're excellent readers)


Finished up and here is a capture of the scan:



I'm happy that the discs play on my DVD player but I just wondered if these kind of results mean the discs won't last long in the future for readability etc?
Answer by Arachne, Wednesday 20th of August 2008 16:28
I think they'll be fine for the forseeable future, but obviously scan them/benchmark them every now and then to check for any deterioration. Since you only have your Sammy to scan with, do any future scans of the discs on the same drive so you can easily compare.
Answer by TonyTi, Wednesday 20th of August 2008 17:43
Arachne said:
I think they'll be fine for the forseeable future, but obviously scan them/benchmark them every now and then to check for any deterioration. Since you only have your Sammy to scan with, do any future scans of the discs on the same drive so you can easily compare.


Sure, I will do that. I did another burn and scanned it, and this time it was the first layer that was high in Pi again, but the second layer would appear to be fine. Quite strange that its only one layer, and varies between which layer is bad and good.

I'm quite confused by all of this
Answer by Arachne, Wednesday 20th of August 2008 17:54
Variations between layers can often be normal, but since you're using a Sammy to scan, results maybe inconsistent.

If you're serious about scanning your media, I would heartily recommend fitting a LiteOn drive alongside your Sammy for scanning duties
Answer by vroom, Wednesday 20th of August 2008 17:57
I wouldn't worry much, 1st because it's MKM, and that's the best you can get for dual layer media, and 2nd you said it plays fine, and that's is the ultimate test.
Answer by TonyTi, Friday 5th of September 2008 17:12
I recently got hold of the MKM003 media, and burned at a few speeds, it seems 8x is the best? I wanted to burn at 4x for lifespan, but maybe 8x might be better.

4X



8X



The results do seem better than what I had with the MKM001, so I'm wondering if it is something to do with the burnspeed too.

As with every scan I have done, one layer is virtually free of errors, yet the other can be filled with them.


edit

I rescanned the initial 4x burnt disc, and got the following flawless scan (I'm guessing the disc had time to cool down after a burn, as I left it for a few hours):





I'm starting to wonder if the MKM001 2.4X discs don't work at all well with my drive. I actually burnt about 125 DVDs from that media too.
Answer by Albert, Friday 5th of September 2008 20:04
The SH-S182D could just be really fickle in its scanning. Make sure that you don't scan immediately after burning, so that both the drive and disc have time to cool down...if you don't, you might end up with results that aren't close to the truth about how well the drive can read the disc.

I know that my SH-S182M was OK with scanning as long as I didn't keep it scanning 1 disc after another, and if I didn't use it to scan discs written by certain writers.
Answer the question right now!


 
Answer a question? Login first, or become a member here!