|
RDMMI -> InCD4 "Suspected firmware defect" error (6/3/2004 10:28:44 AM)
|
I found the "InCD 4517 locking Windows XP Home up" by Googling for the type of errors that G.M. posted.
After upgrading from InCD3 to InCD4 (4.2.4.1), the drive was "not accessible / Incorrect function" but only if an InCD3 disk was in the drive. If an ordinary CD-ROM disc or CD-R was in there the drive was accessible.
As an experiment, I put a totally fresh CD-RW disc right out of the package, and was able to format it via the Explorer right-click InCD4 format item.
So the actual problem is that InCD4 cannot "see" discs formatted with InCD3(?)
Even though I had read the manual and FAQs carefully, this reality was not spelled out.
I am running with NT4SP6a, and my CD-RW drive is the second drive in the system, with the first being a CD-ROM drive.
Though, I wonder if the errors logged mean that I really shouldn't trust the newly formatted InCD4 disc, and should revert to InCD3?
(My drive, the LG GCE-8320B is on the Nero supported list.)
Error.log shows errors like:
SCSI error: (Op 5Ah (ModeSense10) => os=0h host=0h tgt=0h sns=05/24/00h Invalid field in CDB Info=0h=0
CDB bytes:[5Ah][00h][2Ch][00h][00h][00h][00h][01h][08h][00h][00h][00h]
Suspected firmware defect: media capacities returned by command 37 and command 81 do not match.
Format Unit command failed when sent with 336076 blocks to format. Apparently firmware reports a capacity it can't handle.
InCD will retry with alternative value.
Suspected firmware defect: assumed that command 35 has illegaly reported service blocks.
SetEnumErrLevel: errorlevel was 1 [Dflt], is now 2 [Fine]
Though, after that formatting with InCD4, Explorer shows a "file" with the "hs" attributes and the name "Non-Allocatable Space". And in the InCD Properties tab it shows "UDF v1.50".
I can copy files to the CD-RW, but how "safe" are they?
|
|
|
|
