Hello world

I just try incd 4.0.5.6. It works better than previous versions. Now, i can format and use my CDRWs. Thanks a lot David (and all the incd staff...). BUT ...

After i used and ejected a cdrw, my explorer is very unstable. It freeze during 30-40s, then, re-works 10s, freeze 30s ... and again, and again.
I must reset my computer for working with another software

Malediction...

Ok, can you send me InfoTool.txt, plus InCD log files (both the error.log and other .log file)? ( dburg@nero.com )

(in reply to iznogoud_23)

of course ;-)

[url][/url]http://csd23.free.fr/Error.log[url][/url]
[url][/url]http://csd23.free.fr/SrvError.Log[url][/url]
[url][/url]http://csd23.free.fr/InfoTool.txt[url][/url]

but i think problem is located here ->
[url][/url]http://csd23.free.fr/system-events.txt[url][/url]

there is a lot of atapi error ! (sorry file is in french)

(in reply to iznogoud_23)

No problem - I am french. Yes, it looks like the device is taking unexpected long time to answer some request. Now the problem will be to find which one.

(in reply to iznogoud_23)

Well, the problem appears after i eject the cdrw (with rigth click->eject)
If i remove incd, problem disappear...

(in reply to iznogoud_23)

This could be a normal function (eject), due to the fact that the format could still be going on. Even though you may have formatted the cdrw, this is a quick format, and format is still really running in the background. Is this the only function that you say is "slow" to respond?

(in reply to iznogoud_23)

yes, but when i eject cdrw, all operations are finished (format, copy,...). It's like if incd, or explorer (i don't really know which..) try to access empty recorder... [B)]

(in reply to iznogoud_23)

ah, but they are not truely finished! This is a normal function!

(in reply to iznogoud_23)

Another developer of our team has found an error (under 9x/Me) in the ejection code in recently changed... Oups! Probably causing the issue you observe. Sorry! The other developer have kindly corrected my mistake and the fix will be included in next InCD web update.

(in reply to iznogoud_23)

David,

Does this apply to the NT/Win2k/WinXP systems as well? I see that he is Using WindowsXP. Also I did note that DMA is turned off for the drive!

(in reply to iznogoud_23)

don't worry, be happy David !
Maybe the fix will correct my problem.
Just a question : when the next version of InCD will be released ? [:p]

MP3Mogul -> yes, i'm under windows XP pro, and DMA is turned off because my drive don't really support DMA. If DMA is turned on, i've read errors

(in reply to iznogoud_23)

My error was on 9x/Me specific code, thus, it does not affect NT4/2k/XP/Server 2003.

I do not know yet when this version will be release. The qualification of the new version is still pending in QA.

(in reply to iznogoud_23)

That was my thought. He is using WinXP, therefore the eject problem does not apply to him. This is just a normal funtion of InCD, it is still formating in the background whether he realizes it or not, and if he ejects early, InCD will continue to format in the background when he reinserts the disc, until the actual full format is complete.

(in reply to iznogoud_23)

He is using MRW?

(Note: background format is managed by the drive, so it's not really InCD who's background formatting.)

Edit: Reading again the log files, I suspect more some read trouble to be causing the trouble:

01d8 03:09:08 20:59:10:04 e=2007. SCSI error : (Op 28h (Read10) => os=0h host=0h tgt=0h sns=03/11/00h Unrecoved read errror. Info=10Ch=268. @ ID=0_0_0_0 'RICOH CD-R/RW MP7163A' CDB bytes:[28h][00h][00h][00h][01h][00h][00h][00h][10h][00h][00h][00h])

01d8 03:09:08 20:59:10:04 e=0. Enqueing Notify: iDrive=49h u32Info=100h evt=Dh (kevtRetryRead)
01e0 03:09:08 20:59:10:04 e=0. Dequeued Notify: iDrive=49h u32Info=100h evt=Dh (kevtRetryRead)

01d8 03:09:08 20:59:11:13 e=2007. SCSI error : (Op 28h (Read10) => os=0h host=0h tgt=0h sns=03/11/00h Unrecoved read errror. Info=10Ch=268. @ ID=0_0_0_0 'RICOH CD-R/RW MP7163A' CDB bytes:[28h][00h][00h][00h][01h][00h][00h][00h][10h][00h][00h][00h])

01d8 03:09:08 20:59:11:13 e=0. Enqueing Notify: iDrive=49h u32Info=100h evt=Fh kevtHardErrorRead)
01e0 03:09:08 20:59:11:13 e=0. Dequeued Notify: iDrive=49h u32Info=100h evt=Fh (kevtHardErrorRead)

This LBA at the beginning of the disc should be readable without trouble. A media compatibility issue maybe?

(in reply to iznogoud_23)

Very good question David!!!! Iznogoud???? are you writing Mt.Ranier?

We are really trying to resolve your issue! Yes background formatting would be performed by the drive.... it's limitations, and speed......

You have the "BEST" support team ever here with "ahead" answering questions.... you will not find a more "dedicated" support team for ANY software in the world.... Please let us know...

(in reply to iznogoud_23)

hello everybody

No, i don't format with Mt-Rainer, simply because my recorder is too old, and don't support this feature.
And my problem is not specific at a special media, all my cdrw are affected. It's like if explorer tries accessing CDRW after I eject it.

Well, i think I will solve the problem by a new recorder [:p]

(in reply to iznogoud_23)