New user: cannot format/erase

terrypin · May 2, 2006

I'm new to ImgBurn, although I have used DVDDecrypter for a few weeks and understand that was its predecessor? I'm getting very frustrated with the following problem, so hope someone can help me resolve it please. At the risk of including redundant stuff, I'll describe a specific example in detail, although this now affects several of my RW discs.

I successfully made an ISO from my video file folders with ImgToolClassic. I then tried to burn that with ImgBurn 1.3.0. The +RW Verbatim disc contained a previous DVD I made some time ago, which played fine in PowerDVD directly beforehand. ImgBurn advised me that 'This disc needs formating before you can write...'. I said Yes. It then started erasing, which is presumably part of formating? But it then stayed at 0% for hours! Occasionally '0% - Erasing Disc...' was replaced by 'Erasing Disc...', but then '0% - Erasing Disc...' would appear again. The drive ("BTC DVD +/-R 16x") LED was flashing, but as far as I coud see nothing significant was happening. There's no Abort or Cancel button, so I had to force termination via XP task manager.

In case it helps, here's the ImgBurn Log as it stood at 07:43

07:08:15 ImgBurn Version 1.3.0.0 started!

07:08:15 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 1)

07:08:15 Initialising SPTI...

07:08:15 Searching for SCSI / ATAPI devices...

07:08:16 Found 1 CD-RW, 1 DVD-ROM and 1 DVD+/-RW!

07:09:12 Operation Started!

07:09:12 Device: [1:0:0] DVDRW IDE 16X A091 (Hsmile.gif (ATA)

07:09:12 Media Type: DVD+RW (Disc ID: MKM-A02-00) (Speeds: 2.4x, 4x)

07:09:12 Quick Erase: No

07:09:12 Erasing Disc...

Happy to provide any other information or try whatever is suggested. I'm very keen to sort this as I have had warm recommendations for the 2-stage ImgTool Classic plus ImgBurn combination as a more reliable way of burning than Nero (6) Express.

BTW, posted this in video.help forum (so far with no useful answer), before realising this specialist forum existed

--

Terry, West Sussex, UK

**LIGHTNING UK!** · May 2, 2006

DVD+RW formatting is a 2 stage process. The first is done in what's known as the 'foreground' (where the user can see things happening), the rest is done in the background. The foreground part takes about 1 minute usually, the background bit would take 15 - 25 mins. During this time, the drive may or may not flash the led to show the user that it's doing something.

So basically, if you've left it for hours and the media still reads 'Formatted: No' in the info panel on the right, your drive is having problems formatting the media.

terrypin · May 2, 2006

DVD+RW formatting is a 2 stage process. The first is done in what's known as the 'foreground' (where the user can see things happening), the rest is done in the background. The foreground part takes about 1 minute usually, the background bit would take 15 - 25 mins. During this time, the drive may or may not flash the led to show the user that it's doing something.

So basically, if you've left it for hours and the media still reads 'Formatted: No' in the info panel on the right, your drive is having problems formatting the media.

Thanks, appreciate the prompt reply.

I've just tried an identical burn in ImgBurn 1.3.0.0 with brand new disc of same type, Verbatim DVD+RW. ImgBurn gave same message but this time progressed steadily from 0%. However, it's now been 102 mins, of which about 75 has been at 99%. Looks like I'm going to have to forcibly terminate again, probably resulting in yet another coaster.

Also, if I load brand new disc into Nero Express, why does that not ask me to format or erase?

And, if PowerDVD plays the content of a previously-written disc directly before I load it into ImgBurn, how can it need formating?

What is the recommended method to terminate ImgBurn in this situation please? I get "Erasing Disc... Sorry, you cannot cancel this operation." And I cannot manually eject the disc. I have used Ctl-Alt-Del to forcibly close ImgBurn, but I still cannot eject the disc. So I'm going to have to reboot again

--

Terry, West Sussex, UK

**LIGHTNING UK!** · May 2, 2006

The program locks the drive so you can't eject the disc. Unless it shuts down nicely, it won't unlock it.

What you could do is terminate the program, then load it up again and hit the little 'E' button under where you select the drive.

ImgBurn will not write to DVD+RW media until the drive actually sees it as having been formatted.

Not all programs work that way, but mine does - and for people without hardware issues, that isn't normally a big problem.

You format once so it's done properly, then it won't need doing again.

As I said earlier, yours isn't formatting properly and so you'll never get to the stage where it actually works.

Next time you've left it for an hour or so formatting, eject + reinsert the disc and then copy + paste the info from the window on the right within ImgBurn.

terrypin · May 3, 2006

The program locks the drive so you can't eject the disc. Unless it shuts down nicely, it won't unlock it.

What you could do is terminate the program, then load it up again and hit the little 'E' button under where you select the drive.

OK, thanks. Could I also use Tools|Drive|Unlock Tray?

ImgBurn will not write to DVD+RW media until the drive actually sees it as having been formatted.

Good - that means my nervousness was unfounded. I'll go ahead and run another blank +RW.

BTW, can I just initiate the formating, or do I have to select a burn operation first as I have been doing? I'm wondering if Tools|Drive|Erase Disc|Full is identical to formating?

Not all programs work that way, but mine does - and for people without hardware issues, that isn't normally a big problem.
You format once so it's done properly, then it won't need doing again.

Understood. I suppose it's a matter of opinion, but I'd personally rather not have to wait 30-60 mins or whatever formating should take, before doing a 5 minute burn! Wouldn't it be possible to make that an Option setting?

As I said earlier, yours isn't formatting properly and so you'll never get to the stage where it actually works.

If true that's obviously worrying. But I have used a few DVD+RW discs successfully in the past, so either the software I was using (probably Nero Express, NeroVision Express and ConvertXToDVD) were more tolerant than ImgBurn, or didn't require formating at all, or a fault has developed with my BTC DVD drive since then. Or I suppose a software or driver issue has arisen. Any thoughts on how I might isolate the cause beyond any doubt please?

Next time you've left it for an hour or so formatting, eject + reinsert the disc and then copy + paste the info from the window on the right within ImgBurn.

OK, I'll get onto that right now and report back asap.

--

Terry, West Sussex, UK

**LIGHTNING UK!** · May 3, 2006

Yes, tools -> drive -> unlock is the same thing. The 'E' button just does that and then ejects the disc too.

Yes, you can use tools -> drive -> erase -> full to format the disc without having to burn anything.

Like I said, you only have to format a disc once. At 4x, that should take 15 mins. Once formatted, it'll read 'Formatted: Yes' in the info window on the right. When that is visible, the program allows for direct overwrite with no need for additional erasing / formatting.

So ok, lets get another format on the go (ensure your firmware it up-to-date first of course) and when it's been going a while and you consider it 'stuck', press the F8 key to enable I/O debug mode.

If you see lots of I/O stuff going into the log, it means the program is still checking with the drive to see what it's doing. Let me know what's being said.

If nothing is being put in the log it means your drive/drivers have stopped responding and you'll probably need to reboot.

This probably means you have a driver problem and will need to check your filter drivers etc.

btw, the 'WinXP SP2 Kills Everything' rumour is long gone now, you should probably upgrade!

terrypin · May 3, 2006

OK, it didn't need an hour. I used a fresh Verbatim DVD+RW and went through same procedure as before. The only thing I did differently was to change speed from MAX to 2.4x. Reached 16% of the erase in about 10 mins, but was still at 16% about half an hour later. So I terminated ImgBurn via Task Mgr and tried your method of ejecting by re-running. Took a couple of minutes to get to the stage when 'E' was accessible. After re-inserting, it then took another minute or so to 'Open Device'. Any thoughts on why all that is so slow please?

Here's the paste:

DVDRW IDE 16X A091 (ATA)

Current Profile: DVD+RW

Disc Information:

Status: Complete

Erasable: Yes

Formatted: No (In Progress)

Supported Write Speeds: 2.4x, 4x

Physical Format Information (ADIP):

Disc ID: MKM-A02-00

Book Type: DVD+RW

Part Version: 2

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 1

Track Path: Parallel Track Path (PTP)

Linear Density: 0.267 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 2,491,711

Last Physical Sector in Layer 0: 0

Physical Format Information (Last Recorded):

Disc ID: MKM-A02-00

Book Type: DVD+RW

Part Version: 2

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 1

Track Path: Parallel Track Path (PTP)

Linear Density: 0.267 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 2,491,711

Last Physical Sector in Layer 0: 0

Current Format Capacity:

Sectors: 2,295,104

Size: 4,700,372,992 bytes

Time: 510:03:29 (MM:SS:FF)

Maximum Format Capacity:

Sectors: 2,295,104

Size: 4,700,372,992 bytes

Time: 510:03:29 (MM:SS:FF)

Hope this helps. Please advise if there are any other tests that might be useful.

BTW, I ordered some more RW discs yesterday, and hope to be able to try those in a day or so.

--

Terry, West Sussex, UK

terrypin · May 3, 2006

Somehow missed your prompt reply, sorry. My last report was obviously sent before reading it.

I'll run another one now following the F8 approach.

I had a bad experience when I installed SP2 a years or so ago, and promptly reverted to SP1. But yes, I suppose I should bite the bullet again now

The only part of your post I don't understand is "...need to check your filter drivers etc." That whole area (amongst many!) is a black art to me. So, if it comes to exploring that, hope you can give me a pointer please?

FWIW, a week or so ago I had a message from Nero and other progs saying my ASPI was corrupted. Without really knowing what ASPI is, after much research I found and installed a recommended prog called Force ASPI (apparently OK for XP) which appeared to correct that issue. Its associated tool, Aspichk.exe, reports:

ADAPTEC ASPI WINDOWS NT

This utility has checked your current ASPI installation. Version information and

the operational status of ASPI are listed below.

Component Version Date Size

WNASPI32.DLL 4.60 (1021) 09/10/99 45056

WINASPI.DLL 4.60 (1021) 09/10/99 5600

ASPI32.SYS 4.60 (1021) 09/10/99 25244

WOWPOST.EXE 4.60 (1021) 09/10/99 4672

ASPI is properly installed and is fully operational.

A total of 6 host adapters have been detected.

BTW, one aspect of that which confuses me is that I also have that file WnASPI32.dll in my Nero Program folder, several times, all identical at 164,112 bytes in size. Yet the one above clearly refers to C:\WINDOWS\system32\WnASPI32.dll, a very old version that is a mere 45,056 bytes.

Sorry to throw in all these issues which are way OT to ImgBurn, but as you'll have seen I'm floundering here

--

Terry, West Sussex, UK

**LIGHTNING UK!** · May 3, 2006

You can't actually change the erase speed within ImgBurn, it will always do it at max, regardless of the speed setting.

If you insert a disc AND THEN load ImgBurn, ImgBurn is forced to wait until the OS thinks the drive is ready / not ready.

To be taking that long, I would say the drive is having problems initialise the disc. That would go hand in hand with it not being able to format them.

Please don't forget to get the 'debug' log before you terminate the program though. There is every chance it's still working perfectly fine - just that the drive isn't reporting any progress with the actual format.

**LIGHTNING UK!** · May 3, 2006

Don't worry too much about ASPI. It's not really recommended for use on XP and only programs with lazy authors still need it!

The programs that detect if it's ok or not do not take into account that not all files need to be present on XP. So even when it's fine, they'll still report files missing.

Nero's ASPI is self contained and doesn't use the system one. Under XP, it's just an SPTI wrapper anyway. That's why you're seeing different file sizes.

You can check your filter drivers by downloading the 'devfilter.exe' tool from here http://www.bustrace.com/downloads/free_utilities.htm

You basically just highlight your drive and see what it lists for upper and lower filter drivers. Click the 'clipboard' button and paste back in here.

terrypin · May 3, 2006

Don't worry too much about ASPI. It's not really recommended for use on XP and only programs with lazy authors still need it!

The programs that detect if it's ok or not do not take into account that not all files need to be present on XP. So even when it's fine, they'll still report files missing.

Nero's ASPI is self contained and doesn't use the system one. Under XP, it's just an SPTI wrapper anyway. That's why you're seeing different file sizes.

You can check your filter drivers by downloading the 'devfilter.exe' tool from here http://www.bustrace.com/downloads/free_utilities.htm

You basically just highlight your drive and see what it lists for upper and lower filter drivers. Click the 'clipboard' button and paste back in here.

OK, I'm sort of reassured by what you say about ASPI. However, composing my last post got me to thinking I'd screwed up by getting Adaptec into the scene, when I don't use any Adaptec stuff. And just now I saw a recommendation that another thing to try to recover from ASPI troubles (for Nero users) was to paste a copy of the Nero ASPI into C:\WINDOWS\system32\.

Anyway, that tool you recommended loks very handy. Here's what it reports:

Filter Position Filter Driver / Object

Upper Class Filter InCDPass

Upper Class Filter incdrm

Upper Device Filter redbook

Device Object DVDRW IDE 16X

Lower Class Filter MxlW2k

Lower Class Filter Pfc

Lower Class Filter PxHelp20

Lower Class Filter AnyDVD

Lower Device Filter imapi

Although all that is largely incomprehensible to me, I'm very surprised to see those references to inCD. I disabled inCD a week ago while doing all this DVD work, as I'd heard it could interfere. And I disabled the inCD Helper in Services too. So I was sort of assuming inCD was out of the equation. But that stuff above seems to imply otherwise, in which case maybe that's a possible cause of this formating problem?

I'll be back shortly with that 'F8 paste'.

--

Terry, West Sussex, UK

terrypin · May 3, 2006

Sorry, that paste was incomplete; here's the full Clipboard:

----------------------------------------------------

Filter Driver Load Order http://www.bustrace.com

----------------------------------------------------

Upper Class Filter: InCDPass

Upper Class Filter: incdrm

Upper Class Filter: Pcatip

Upper Device Filter: redbook

Device Object: DVDRW IDE 16X

Lower Class Filter: MxlW2k

Lower Class Filter: Pfc

Lower Class Filter: PxHelp20

Lower Class Filter: AnyDVD

Lower Device Filter: imapi

Driver Name: incdpass.sys

File Location: c:\windows\system32\drivers

File Description: Ahead RW Filter Driver

File Version: 4, 3, 20, 1 [4.3.20.1]

Product Name: InCD

Product Version: 4, 3, 20, 1 [4.3.20.1]

Company Name: Nero AG

Driver Name: incdrm.sys

File Location: c:\windows\system32\drivers

File Description: Ahead MRW Filter Driver

File Version: 4, 3, 20, 1 [4.3.20.1]

Product Name: EasyWrite Reader

Product Version: 4, 3, 20, 1 [4.3.20.1]

Company Name: Nero AG

Driver Name: pcatip.sys

File Location: c:\windows\system32\drivers

File Description: Patin-Couffin Autoplay support driver

File Version: 1.6.0.0 [1.6.0.0]

Product Name: Patin-Couffin Autoplay support driver

Product Version: 1.6.0.0 [1.6.0.0]

Company Name: VSO Software

Driver Name: redbook.sys

File Location: c:\windows\system32\drivers

File Description: Redbook Audio Filter Driver

File Version: 5.1.2600.1106 (xpsp1.020828-1920) [5.1.2600.1106]

Product Name: Microsoft? Windows? Operating System

Product Version: 5.1.2600.1106 [5.1.2600.1106]

Company Name: Microsoft Corporation

Driver Name: mxlw2k.sys

File Location: c:\windows\system32\drivers

File Description: MusicMatch Access Layer KMD

File Version: 1.1.0.121 [1.1.0.121]

Product Name: MusicMatch Access Layer

Product Version: 1.1.0.121 [1.1.0.121]

Company Name: MusicMatch, Inc.

Driver Name: pfc.sys

File Location: c:\windows\system32\drivers

File Description: Padus® ASPI Shell

File Version: 2, 5, 0, 205 [2.5.0.205]

Product Name: Padus® ASPI Shell

Product Version: 2, 5, 0, 205 [2.5.0.205]

Company Name: Padus, Inc.

Driver Name: pxhelp20.sys

File Location: c:\windows\system32\drivers

File Description: Px Engine Device Driver for Windows 2000/XP

File Version: 2.03.32a [2.3.32.0]

Product Name: PxHelp20

Product Version: [2.0.0.0]

Company Name: Sonic Solutions

Driver Name: anydvd.sys

File Location: c:\windows\system32\drivers

File Description: AnyDVD Filter Driver

File Version: 5.9.6.0 [5.9.6.0]

Product Name: AnyDVD

Product Version: 5.9.6.0 [5.9.6.0]

Company Name: SlySoft, Inc.

Driver Name: imapi.sys

File Location: c:\windows\system32\drivers

File Description: IMAPI Kernel Driver

File Version: 5.1.2600.1106 (xpsp1.020828-1920) [5.1.2600.1106]

Product Name: Microsoft? Windows? Operating System

Product Version: 5.1.2600.1106 [5.1.2600.1106]

Company Name: Microsoft Corporation

--

Terry, West Sussex, UK

**LIGHTNING UK!** · May 3, 2006

ok yeah I'd start by totally removing incd. You might need to uninstall nero and then reinstall doing a custom install with incd turned off.

Otherwise, you'll have to strip it out via regedit.

Not sure what mxlw2k is either. I don't recognise it as a typical filter driver. Seems to trace back to MusicMatch. See about removing it if you don't use it.

Same goes for the Pfc one - normally part of 'Padus'. If you don't use it, remove it.

This may help you: http://www.daemon-tools.cc/dtcc/t440-my-re...re-missing.html

terrypin · May 3, 2006

OK, thanks, very helpful.

InCD appeared as a discrete Add/Remove entry, so I uninstalled it.

So far I've not removed anything else, but I will probably get rid of that MusicMatch entry next. The revised report is now:

----------------------------------------------------

Filter Driver Load Order http://www.bustrace.com

----------------------------------------------------

Upper Class Filter: Pcatip

Upper Device Filter: redbook

Device Object: DVDRW IDE 16X

Lower Class Filter: MxlW2k

Lower Class Filter: Pfc

Lower Class Filter: PxHelp20

Lower Class Filter: AnyDVD

Lower Device Filter: imapi

Driver Name: pcatip.sys

File Location: c:\windows\system32\drivers

File Description: Patin-Couffin Autoplay support driver

File Version: 1.6.0.0 [1.6.0.0]

Product Name: Patin-Couffin Autoplay support driver

Product Version: 1.6.0.0 [1.6.0.0]

Company Name: VSO Software

Driver Name: redbook.sys

File Location: c:\windows\system32\drivers

File Description: Redbook Audio Filter Driver

File Version: 5.1.2600.1106 (xpsp1.020828-1920) [5.1.2600.1106]

Product Name: Microsoft? Windows? Operating System

Product Version: 5.1.2600.1106 [5.1.2600.1106]

Company Name: Microsoft Corporation

Driver Name: mxlw2k.sys

File Location: c:\windows\system32\drivers

File Description: MusicMatch Access Layer KMD

File Version: 1.1.0.121 [1.1.0.121]

Product Name: MusicMatch Access Layer

Product Version: 1.1.0.121 [1.1.0.121]

Company Name: MusicMatch, Inc.

Driver Name: pfc.sys

File Location: c:\windows\system32\drivers

File Description: Padus® ASPI Shell

File Version: 2, 5, 0, 205 [2.5.0.205]

Product Name: Padus® ASPI Shell

Product Version: 2, 5, 0, 205 [2.5.0.205]

Company Name: Padus, Inc.

Driver Name: pxhelp20.sys

File Location: c:\windows\system32\drivers

File Description: Px Engine Device Driver for Windows 2000/XP

File Version: 2.03.32a [2.3.32.0]

Product Name: PxHelp20

Product Version: [2.0.0.0]

Company Name: Sonic Solutions

Driver Name: anydvd.sys

File Location: c:\windows\system32\drivers

File Description: AnyDVD Filter Driver

File Version: 5.9.6.0 [5.9.6.0]

Product Name: AnyDVD

Product Version: 5.9.6.0 [5.9.6.0]

Company Name: SlySoft, Inc.

Driver Name: imapi.sys

File Location: c:\windows\system32\drivers

File Description: IMAPI Kernel Driver

File Version: 5.1.2600.1106 (xpsp1.020828-1920) [5.1.2600.1106]

Product Name: Microsoft? Windows? Operating System

Product Version: 5.1.2600.1106 [5.1.2600.1106]

Company Name: Microsoft Corporation

---------

OK, now to the 'F8 test;.

When I tried to do a Full Erase with ImgBurn, using another fresh DVD+RW, it got no further than 0% this time!

Using F8 I got what seemed to be fast scrolling repetitions containing something like this:

11:38:55 [1:0:0] DVDRW IDE 16X A091 (H:) (ATA)

11:38:55 CDB: 00 00 00 00 00 00

11:38:55 CDB Interpretation: Test Unit Ready

11:38:55 SENSE: 70 00 02 00 00 00 00 0A 00 00 00 00 04 04 00 80 0 00

11:38:55 SENSE Interpretation: Logical Unit not ready, Format in progress

11:38:56 [1:0:0] DVDRW IDE 16X A091 (H:) (ATA)

11:38:56 CDB: 00 00 00 00 00 00

11:38:56 CDB Interpretation: Test Unit Ready

11:38:56 SENSE: 70 00 02 00 00 00 00 0A 00 00 00 00 04 04 00 80 0 00

11:38:56 SENSE Interpretation: Logical Unit not ready, Format in progress

Eventually I restarted and tested the disc with various programs:

Nero Info Tool said:

General

Type: DVD+RW

Capacity: 4.38 GB

Extended Information

Layers: 1

Supported Speeds: 4.0 X - 2.4 X

Blank Capacity: n/a

Manufacturer ID: MKM A02

Copy Protection: n/a

Content

File System(s):

Title: n/a

Date: n/a

Publisher: n/a

Application: n/a

====================

IsoBuster said:

"During mounting of the disc only a session/track layout could be found.

No file-systems nor files and folders could be found."

====================

AnyDVD said:

Summary for drive H: (AnyDVD 5.9.6.0)

Drive (Hardware) Region: 2

Media is a Data DVD.

Booktype: dvd+rw (version 2), Layers: 1

Total size: 2295104 sectors (4482 MBytes)

====================

DVD Identifier said:

----------------------------------------------------------------------------

Unique Disc Identifier : [DVD+RW:MKM-A02-000]

----------------------------------------------------------------------------

Disc & Book Type : [DVD+RW] - [DVD+RW]

Manufacturer Name : [Mitsubishi Kagaku Media]

Manufacturer ID : [MKM]

Media Type ID : [A02]

Product Revision : [Not Specified]

Blank Disc Capacity : [2,295,104 Sectors = 4.70 GB (4.38 GiB)]

Recording Speeds : [1x-2.4x , 1.6x-4x]

----------------------------------------------------------------------------

And the 'log' section says (after the intro):

12:30:30 DVD+R/+RW Medium Detected. Starting Identification... .

12:30:30] ** Initiating ADIP Retrieval Method 1 (Original ADIP)

12:30:30] ADIP Read Method 1 Completed Without Errors

12:30:30] Disc Identification Completed Successfully

12:31:11] DVD+R/+RW Medium Information Copied To Clipboard

[ DVD Identifier V4.3.0 - http://DVD.Identifier.CDfreaks.com ]

====================

Then I loaded ImgBurn which said:

DVDRW IDE 16X A091 (ATA)

Current Profile: DVD+RW

Disc Information:

Status: Complete

Erasable: Yes

Formatted: No (Started)

Supported Write Speeds: 2.4x, 4x

Physical Format Information (ADIP):

Disc ID: MKM-A02-00

Book Type: DVD+RW

Part Version: 2

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 1

Track Path: Parallel Track Path (PTP)

Linear Density: 0.267 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 2,491,711

Last Physical Sector in Layer 0: 0

Physical Format Information (Last Recorded):

Disc ID: MKM-A02-00

Book Type: DVD+RW

Part Version: 2

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 1

Track Path: Parallel Track Path (PTP)

Linear Density: 0.267 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 2,491,711

Last Physical Sector in Layer 0: 0

Current Format Capacity:

Sectors: 2,295,104

Size: 4,700,372,992 bytes

Time: 510:03:29 (MM:SS:FF)

Maximum Format Capacity:

Sectors: 2,295,104

Size: 4,700,372,992 bytes

Time: 510:03:29 (MM:SS:FF)

---------

Now I'm stepping through as I continue to compose the post:

The status line says 'Ready (Disc Needs Formatting).

On clicking OK the now familiar message appears and I go ahead.

After a minute or so I feel confident it's again stuck on 0%.

I use F8. The fragment I was able to capture was:

12:50:21 BUFFER: 70 00 00 00 00 00 00 0A 00 00 00 00 04 04 00 80 02 7D 00 00 00 00 00 00

12:50:22 [1:0:0] DVDRW IDE 16X A091 (H:) (ATA)

12:50:22 CDB: 03 00 00 00 18 00

12:50:22 CDB Interpretation: Request Sense

12:50:22 BUFFER: 70 00 00 00 00 00 00 0A 00 00 00 00 04 04 00 80 02 7D 00 00 00 00 00 00

12:50:23 [1:0:0] DVDRW IDE 16X A091 (H:) (ATA)

12:50:23 CDB: 03 00 00 00 18 00

12:50:23 CDB Interpretation: Request Sense

12:50:23 BUFFER: 70 00 00 00 00 00 00 0A 00 00 00 00 04 04 00 80 02 7D 00 00 00 00 00 00

In the absence of any more elegant method, I now forcibly terminate ImgBurn via Task Mgr.

By way of a change I now open your DVD Decrypter 3.5.4.0. But it's tricky to get it running properly (just as it was when I used ImgBurn on the last similar test). The status line initially says 'Searching for SCSI/ATAPI deveices...' That looks set to take forever, so I try the manual tray Eject button. After a few seconds that seems to unlock whatever the blockage was, and the status line now says 'Ready'.

I now eject it and then reinsert it.

Status line now says 'Device Not Ready (Medium Not Present)', although that contradicts what ImgBurn and other info progs reported earlier.

I cannot now manually eject. And if I try clicking the 'E' I get:

I/O Error!

Device: [1:0:0] DVDRW IDE 16X A091 (H:) (ATA)

ScsiStatus: 0x02

Interpretation: Check Condition

CDB: 1B 01 00 00 02 00

Interpretation: Start/Stop Unit

Sense Area: 70 00 02 00 00 00 00 0A 00 00 00 00 04 04 00 80 02 7D

Interpretation: Logical Unit not ready, Format in progress

I now start to use Tools|Drive, but before I can complete my intention to use Unlock Tray, the tray opens!

I close DVD Decrypter and open Nero Info Tool, which now says: 'No disc inserted'.

That appears to be confirmed by DVD Identofier, which says:

ERROR : Unable To Initialize Disc : Not ready - Medium not present [02/3A/00]

====================

So the disc is now unreadable

--

Terry, West Sussex, UK

**LIGHTNING UK!** · May 3, 2006

Ok the 'Test unit ready' & 'Request sense' commands going into the log shows the drive is still accepting I/O request. That's a good sign in that the system hasn't actually frozen.

You're getting the correct status returned from the drive too - 'logical unit not ready, format in progress'. That's what I'd expect it to say.

The problem really is just that the drive won't write to those discs properly.

When you eject a disc during a format, it will attempt to end the format before it ejects the tray. That is all controlled by the drive. That's probably why you experienced a delay after pressing the manual eject.

The '80 02 7D' data in the sense area info is actually where the progress % comes from.

The 80 means that progress values are available and the '02 7D' (637) is the amount complete - where 'FF FF' (65535) is maximum - making 0.9% complete (would show as 0% probably).

If you're getting that same figure all the time, it means that's where the format is getting stuck - pretty much right at the start!

You're going to have to find some other RW's to try. Maybe some Ricoh ones or something.

terrypin · May 3, 2006

OK, thanks, will test on different discs asap.

You're still pretty sure that ASPI stuff isn't involved?

Thanks for your patience

--

Terry, West Sussex, UK

**LIGHTNING UK!** · May 3, 2006

Pretty much, yeah! Communication with the drive is fine.

ASPI just provides an alternative 'road' for the I/O stuff to drive down.

If you like, try setting the I/O Interface to one of the other ones and see if it makes a difference.

terrypin · May 3, 2006

OK, I've experimentally changed I/O from its default setting of SPTI (whatever that is) to WNASPI32.DLL. That refers to the smallish Adaptec file of that name I described. It's still not clear to me why I don't need to use the Nero one of same name. Or how I would do so, come to that! I suppose replacing the \Windows\System32 file with the one from \Progam Fles\ahead\Nero would be a possibility?

Anyway, I've started another format with that setting. As I've exhausted my stock of brand new +RW discs, I'm using an existing readable one. It's been stuck at 3% for 10 mins, so I assume that just reinforces your diagnosis. Have finally ejected it after the usual convolutions.

A short while earlier, using my very last fresh +RW disc, I tried using the Format/Full Erase facility in Nero CD-DVD Speed. That seemed to be going OK, but froze at some point when I wasn't looking. So that confirms that, whatever the cause is, it's not an ImgBurn issue.

While I'm clutching at straws I may as well try that 'Nero ASPI swap' I conjectured about above, but I'm not hopeful. Maybe I'll forget about +RW for the time being. That's about 4 days on trouble-shooting so far, and not a minute on authoring! But I just hate unsolved puzzles

--

Terry, West Sussex, UK

**LIGHTNING UK!** · May 3, 2006

By default, most programs that open and try to use DLL files will do so from their own folder before using the system one.

So when you use Nero, it's using the WNASPI32.DLL in it's own folder. All other programs would use the system one - ImgBurn included.

Yes you could put Nero's WNASPI32.DLL in the System32 folder but then again it would be better to just stick it in the applications folder - incase it screws up some application that relies on the real Adaptec one.

In theory you could tell ImgBurn not to wait for background format, but that's only going to push the problem to one side, not fix it.

You'd still be asked to format each time you try and burn because it'll never get to that 'Formatted' state.

Hopefully the Ricoh +RW discs will work where the Verbatim ones obviously did not.

terrypin · May 5, 2006

Still having problems, even with RICOH DVD+RW. So looks like either the BTC DVD drive, or some obscure software issue. I ordered a new drive (an NEC) on Wednesday, but the darn delivery hasn't included it. "Temporarily out of stock", despite nothing to that effect when I ordered online from SVP ;-(

One thing I still haven't really grasped (although I'm guessing it's something to do with this foreground/background stuff) is why Nero Express apparently formats a DVD +RW in a mere 14 seconds?

14:56:26 Burn process started at 4x (5,540 KB/s)

14:56:26 Start formatting disc before burning

14:56:40 Formatting disc was successful

--

Terry, West Sussex, UK

terrypin · May 5, 2006

And even a plain DVD-R failed.

FWIW, here is the log, in case it adds anything new to the diagnosis:

I 19:12:58 ImgBurn Version 1.3.0.0 started!

I 19:12:58 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 1)

I 19:12:58 Initialising SPTI...

I 19:12:58 Searching for SCSI / ATAPI devices...

I 19:12:58 Found 1 CD-RW, 1 DVD-ROM and 1 DVD?RW!

I 19:13:19 Operation Started!

I 19:13:19 Source File: D:\My Pictures\MOVIES\ImgToolClassic OUTPUT\MoT-Erd6-43-latest.iso

I 19:13:19 Source File Sectors: 990,392 (MODE1/2048)

I 19:13:19 Source File Size: 2,028,322,816 bytes

I 19:13:19 Source File Volume Identifier: STANDARD

I 19:13:19 Source File Implementation Identifier: mkisofs

I 19:13:19 Source File UDF Revision: 1.02

I 19:13:19 Destination Device: [1:0:0] DVDRW IDE 16X A091 (H:) (ATA)

I 19:13:19 Destination Media Type: DVD-R (Disc ID: MCC 03RG20) (Speeds: 4x, 8x, 12x, 16x)

I 19:13:19 Destination Media Sectors: 2,298,496

I 19:13:19 Write Mode: DVD

I 19:13:19 Write Type: DAO

I 19:13:19 Write Speed: MAX

I 19:13:19 Link Size: Auto

I 19:13:19 Test Mode: No

I 19:13:19 BURN-Proof: Enabled

I 19:13:19 Filling Buffer...

I 19:13:20 Writing LeadIn...

W 19:17:36 Failed to Write Sectors 608 - 639 - Write Error

W 19:17:36 Retrying (1 of 20)...