CDRLabs.com

The infamous problem of the InCD dialog not opening when you insert a blank CD-RW into the burner doesn't seem to have been fixed with this newest version (4.0.1.21). Anyone had any success getting this to work?

Jeff

I'm curious about this as well, as it is working on the various sytsems I have here in the US lab.

Regards,

Craig

Jeff, helps if you provide a bit more info like OS, drive in question and media being used.

Was the disc used with the previous version of InCD or is it a fresh disc?

tazdevl,

O/S: Win XP SP-1 w/all updates

Burner: Lite-on LTR 52246S

Media: Various brands, e.g., Lite-on, Maxell, Sony HS. All are fresh discs or previously used but erased.

In the Drive "Properities" in the AutoPlay section, the "AutoRun empty CD with InCD" is enabled.

XP's Recording utility is disabled. And the IMAPi CD Burning COM Service is Disabled.

Thx, just helps the guys @ Ahead. If they have the same hardware, let's them test it out.

I think we have an idea here in Karlsbad of what's happening on XP machines with this trouble. One of our engineers is currently coding a additionnal detection code for XP autostart that we hope will solve this blank media issue.

David,

That's encouraging news! There are obviously other problems with InCD as well which need immediate attention. For example, I tried using "Copy Disk" in Nero Express and InCD caused the system to crash. I tried several different blank disks and other written media and got the same results each time. Here's a screenshot of the error message below. There were a couple of files written to my Temp folder in My Documents/Local Settings which it said would be used in a "report". What am I to do with those two files?

Does this build fix some of the slow speed problems the earlier builds had?

Pilgrim, if I correctly understand, the steps to reproduce this issue is:

- On Windows XP, install Nero Express (which version?) and InCD 4.0.1.21. What recorder? Does the recorder have an influence on the defect?
- (After reboot.) Launch Nero Express, insert a blank CD-RW, choose "Copy Disk" -> Incdsrv.exe crashes?

About what to do with the temp file for a report: Well, so far I think Microsoft OCA (Online Crash Analysis) program is working only for system crashes, for user-mode application crashes, the report is collected by Microsoft but not yet providing to software companies author of the concerned failing application. So maybe the best is to keep them in case in Ahead we've not able to reproduce the defect you have found (thus will need to debug from your report files).

Ian wrote:Does this build fix some of the slow speed problems the earlier builds had?

Some of them, yes. All of them, no. We still have 2 know performance issues we're working hard on. One of them, affecting only older computers, we have already found a way to "fix" it but the implementation will take some time (it's not really a fix, it's an optimization). The second one, concerning special access-patterns, we have several ideas likely to help to investigate.

But fixing crashes, format or write failures are still priority number 1 when some are found (just like Pilgrim did).

dburg wrote:Pilgrim, if I correctly understand, the steps to reproduce this issue is:

- On Windows XP, install Nero Express (which version?) and InCD 4.0.1.21. What recorder? Does the recorder have an influence on the defect?
- (After reboot.) Launch Nero Express, insert a blank CD-RW, choose "Copy Disk" -> Incdsrv.exe crashes?

Burner: Lite-on LTR 52246S
CD ROM: LG CRD-8522B
Nero 6.09

If I can be of any further assistance to you, e.g., supplying those log files which Nero cached, etc., please let me know. I'll be glad to do whatever is needed... okay, to a point!

Jeff

Ian wrote:Does this build fix some of the slow speed problems the earlier builds had?

Yeah, I see that. I'm currently running a test that should take about 25 minutes. Instead its taking more than 55 minutes with the latest build.

I'd like to continue to use InCD in our benchmarks, but the results I'm getting are not an accurate indicator of a drive's performance.

Can you describe what access pattern you are doing, and on which computer (CPU/ide controller)?

dburg wrote:Can you describe what access pattern you are doing, and on which computer (CPU/ide controller)?

CPU: AMD Athlon XP 1700+ 1.47GHz
Motherboard: AOpen AK77-333 with BIOS R1.16 (It has a VIA KT333 chipset. Using the onboard IDE.)

I'm not doing anything special. I have 4GB of randomly generated data and directories that I'm copying and pasting through explorer. The drive is the TEAC DV-W50D (Pioneer A06 clone?) and the media I'm using is Pioneer's 2x DVD-RW media.

This problem isn't limited only to the TEAC. I also had the same problems with the Sony DRU-510A. If you need more info, please let me know.

I was seeing the same problem with Win 2000 SP4 and different hardware.
For some details see my recent thread about my "UNpleasnt experienes attempting to install Nero 6".

However, I just tried again with an unused CD-RW and InCD did pop up it's format dialog.

Perhaps, I saw the problem while Easy Wrte Reader 4.0.0.10 was installed?

RATS! InCD 3.51.91 worked just fine. But v4.0.1.21 causes a BSOD after WinXP starts up. It doesn't matter if I'm using Nero 6 or 5.5 with it. Apparently, it doesn't like McAfee V7 very much because the stop error refers to naifltr.sys "most" of the time. Sometimes it's just a general stop error. Nero Clean and Gen Clean tools don't help. I put Nero 5.5 and InCD 3.51 back on to test, and they work just fine.

Hello.

Well, conflict when it's crashing in the filter driver of another product are very hard to fix as you don't have the debug symbols of the crashing product...

Although, can you detail the exact version/update of McAfee "7" you have installed? Is the blue screen gone if you de-install it? Have you send the error report to Microsoft (so they forward the defect to the driver's author)?

I've already sent an email to techsupport@ahead.de that details the errors and the troubleshooting measures I've tried. I can forward it to another address if needed. There was no error report generated. It just blue screened and I rebooted. Nothing more. And as I posted, it's not always the filter that crashes. And after 5 BSOD, I think my PC has had enough "testing" but thank you anyway. All I know is that my PC doesn't crash with InCD 4. So I'll just stick with v3.5 until there is a fix, or I'll just start using multisession burning in Nero.

It should not be necessary to send it again to another address. People from techsupport are collecting the information.

dburg wrote:It should not be necessary to send it again to another address. People from techsupport are collecting the information.

I just received an encouraging email from Al Valerio on this stating:

"Apparently there is a bug in the program…other users are experiencing similar Post-InCD4 problems. In the meantime, please stay with the old version until Our Engineers can resolve this issue."

Thanks for your efforts Ahead.