CompactFlash corruption and EWF

  • Thread starter Thread starter lino
  • Start date Start date
HiRob,
it seams to be correct as we experienced this behavior on a particular P/N
range while newer CFs work fine till now.
I'm happy to know someone can take more information than us from PQI!
Do you know how can I check the firmware? ... I have a tool but it reports
only FW v. 1.01 and nothing else.
Thank you in advance
Paolo.

"Rob" <[email protected]> ha scritto nel messaggio






- Tekst uit oorspronkelijk bericht weergeven -
Click to expand...

I see the firmware version during the BIOS startup, but only for a
split second.
When in XP, I can get the firmware version from Control Panel (->
System,
-> Hardware, then select the disk and view its properties).

Rob
 
HiRob,

according to PQI devices, CF in our case, we finally have an official
report, directly from PQI that I report here as is:

I guess the customer used XPe on AC47

This solution "ra03" is not suit for XPe.
Its transfer mode PIO2 and EEC function 2 bit.
XP embedded 's booting will be loading a lot of files.
"ra03" can not handle such heavy loading well.
When ra03 works over its loading, it will let those good sectors which the
lots files on it become bad sectors.
There are appearing some mistakes let the XPe not booting abnormal and
running CHKDSK.
If your clean all partition then do format again, then perform scandisk a
gain, you will find all the bad sectors are gone

"Rob" <[email protected]> ha scritto nel messaggio






- Tekst uit oorspronkelijk bericht weergeven -
Click to expand...

Hi,

I got exactly the same response from PQI, but I'm still at a loss
why XP should have a problem and NT not. Someone suggested
that it has to do with the differences in NTFS, but I'm not
particularly
knowledgeable here. Or perhaps that MS' IDE-driver is to blame.

In the mean time, we've sawed one DOM open and saw that the
intelligence of the DOM is handled by a chip from TDK called
(appropriately) RA03, see datasheet at www.tdk.co.jp/tefe02/ew_002.pdf

I'm currently waiting for an answer from TDK about known issues with
the ra03.00e and ra03.00f versions, and what can be done about it.

Rob
 
Back
Top