Please Help: DVD RW NOT RECOGNISED IN XP

I am really hoping someone can sort this one out for me! I'm pulling my hair out with this and have wanted to throw my pc out of the window several times over.
I am running xp on a Compaq Presario AMD Athlon(tm) XP 1800+
I have a Pioneer DVR 111D DVD RW.
I did have a VOM 48x12e which was working fine when creating a data disc on nero7.
However about 4 weeks ago my pc decided that when i put a blank disc in it would only recognise it as a cd rom and thus not burn anything.
It had been working fine for weeks but just decided to stop.
I borrowed an external pioneer drive from my friend and this burnt one disc and then did the same.
I then put in a pioneer dvr111d hoping this would resolve it - but it didn't.
I have removed nero7 on a clean unistall (registry delete etc) and reinstalled it. I have uninstalled the dvd drive, i have uninstalled the IDE channels, I have tried downloading the driver and aso firmware. The firmware update says that target cannot be found.
The other odd thing I have noticed is that itunes, which i use for all music, is now coming up with a message when I open it saying that 'the registry settings used by the itunes drivers for importing and burning cds and dvds is missing'
I really have had enough and I really hope tha someone can help me.
I have been very impressed with the peoblems I've seen resolved so far so I'm hoping i can be very impressed again.

Hi and Welcome!

please have a look into Device Manager, if there are any problem indicators present. Report back then.

Michael

I've checked device manager and there are no errors.

by the way... Thanks for replying so soon!

Does this happen only with DVD RW discs or with all DVD discs?

Google error 39 and go from there. Also, google upper/lower filters and try that.

Why should he?

Ok, you say you have Itunes installed? If so, remove that and see if this problem goes away.

Right, wipe itunes.

Ok....I've removed itunes and that doesn't make a difference.
I'd already done the upper and lower filter removal and that didn't work.
It reads dvd's and dvds with avi files.
It won't burn with dvd rw or dvd r (+ and -)

Thanks for all the suggestions so far........

Tr< again, this time with imgburn and post the logfile/results here.

If you have ImgBurn installed, post the log.

Here's the log....hope this means something to you!!!

Phil

1C82-A0K5-19E5-MAAX-400E-EAK6-****

Windows XP 5.1
IA32
WinAspi: -

NT-SPTI used
Nero Version: 7.10.1.0
Internal Version: 7, 10, 1, 0
( Nero Express)
Recorder: < Image Recorder> Version: Not available - HA -1 TA 0 - 7.10.1.0
Adapter driver: HA -1
Drive buffer :
CD-ROM: Version: 1.23 - HA 1 TA 0 - 7.10.1.0
Adapter driver: HA 1

=== Scsi-Device-Map ===
DiskPeripheral : WDC WD400EB-00CPF0 atapi Port 0 ID 0 DMA: On
CdRomPeripheral : PIONEER DVD-RW DVR-111D atapi Port 1 ID 0 DMA: On

=== CDRom-Device-Map ===
PIONEER DVD-RW DVR-111D E: CdRom0
=======================

AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 83886080 (0) Byte
BUFE : 0
Physical memory : 1247MB (1277424kB)
Free physical memory: 690MB (707580kB)
Memory in use : 44 %
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

29.5.2009
ISO compilation
20:29:24 #1 Text 0 File Isodoc.cpp, Line 6666
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

20:29:24 #2 ISO9660GEN -11 File Geniso.cpp, Line 3343
First writeable address = 0 (0x00000000)

20:29:24 #3 Text 0 File Burncd.cpp, Line 3508
Turn on Disc-At-Once, using DVD media

20:29:24 #4 Text 0 File DlgWaitCD.cpp, Line 307
Last possible write address on media: 4718591 (1048:34.41, 9215MB)
Last address to be written: 2767 ( 0:36.67, 5MB)

20:29:24 #5 Text 0 File DlgWaitCD.cpp, Line 319
Write in overburning mode: NO (enabled: CD)

20:29:24 #6 Text 0 File DlgWaitCD.cpp, Line 493
>>> Protocol of DlgWaitCD activities: <<<
=========================================

20:29:24 #7 Text 0 File ThreadedTransferInterface.cpp, Line 793
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 ()
2 indices, index0 (150) not provided
original disc pos #0 + 2768 (2768) = #2768/0:36.68
relocatable, disc pos for caching/writing not required/ required
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2768 blocks [Image Recorder]
--------------------------------------------------------------

20:29:31 #8 Text 0 File ThreadedTransferInterface.cpp, Line 995
Prepare [Image Recorder] for write in CUE-sheet-DAO
DAO infos:
==========
MCN: ""
TOCType: 0x00; Session Closed, disc fixated
Tracks 1 to 1: Idx 0 Idx 1 Next Trk
1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 5668864, ISRC ""
DAO layout:
===========
___Start_|____Track_|_Idx_|_CtrlAdr_|_____Size_|______NWA_|_RecDep__________
0 | lead-in | 0 | 0x41 | 0 | 0 | 0x00
0 | 1 | 0 | 0x41 | 0 | 0 | 0x00
0 | 1 | 1 | 0x41 | 2768 | 0 | 0x00
2768 | lead-out | 1 | 0x41 | 0 | 0 | 0x00

20:29:31 #9 Text 0 File Burncd.cpp, Line 4294
Caching options: cache CDRom or Network-Yes, small files-Yes (<64KB)

20:29:31 #10 Phase 65 File dlgbrnst.cpp, Line 1762
Burn process started

20:29:31 #11 Text 0 File ThreadedTransferInterface.cpp, Line 2721
Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0

20:29:31 #12 Text 0 File ThreadedTransfer.cpp, Line 269
Pipe memory size 590400

20:29:31 #13 Text 0 File WriterStatus.cpp, Line 113
******* Recorder> start writing Lead-Out at LBA 2768 (AD0h), length 0 blocks

20:29:31 #14 Phase 66 File dlgbrnst.cpp, Line 1762
Burn process completed successfully


Existing drivers:

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

Drive is properly recognized and working...

*cough*
Perhaps it's a good idea to use the physical drive instead of the Image Recorder


Michael

Hehe, LOL, didnt check that.

WHY did the OP use image burner???

I thought that 'Dialysis' asked for an image burn. Please let me know if I have done the wrong thing!

By the way....I didn't use the physical drive as it can't find the bloomin thing. Thats the whole reason for the thread!

Startup imgburn, post the logfile/log here.

I had said ImgBurn. Not image burn. ImgBurn is a burning application.
What I was looking for is to see if the burning software sees the drive as a burner.

@ Kangafeet,

To avoid any confusion install the ImgBurn (http://www.imgburn.com) software program. After installing the ImgBurn (http://www.imgburn.com) software program then burn some data to a Disk and then post the ImgBurn Log File.

For information on the use of the ImgBurn (http://www.imgburn.com) software program suggest viewing the below referenced Web Page Link and refer to the ‘Guides’ posted there ->

http://forum.imgburn.com/index.php?showforum=4

Regards,
bjkg

Thanks for givingme the info.
tried to write some data but came up with this message:

I 12:13:06 ImgBurn Version 2.4.4.0 started!
I 12:13:06 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 3)
I 12:13:06 Total Physical Memory: 1,277,424 KB - Available: 793,244 KB
W 12:13:06 Drive D:\ (FAT32) does not support single files > 4 GB in size.
I 12:13:06 Initialising SPTI...
I 12:13:06 Searching for SCSI / ATAPI devices...
E 12:13:09 CreateFile Failed! - Device: '\\.\CdRom0' (E
E 12:13:09 Reason: The maximum number of secrets that may be stored in a single system has been exceeded.
W 12:13:09 Errors were encountered when trying to access a drive.
W 12:13:09 This drive will not be visible in the program.
W 12:13:09 No devices detected!

You have a virus!

@ Kangafeet,

Forum Member Dialysis1 is totally correct – unfortunately you have a Computer Virus.

Suggest reviewing the below ImgBurn Forum posting ->

http://forum.imgburn.com/index.php?showtopic=9862

At the ImgBurn Forum there is another more detailed Forum posting concerning the same problem ->

http://forum.imgburn.com/index.php?s...88&#entry92788

Regards,
bjkg

This is why I was asking for the log 2 days ago.
This problem has been around for a long time but only recently this has been popping up all over and only recently has the solution been found.