| Author | Message | ||
     Greg Martin Username: gmartin Registered: N/A |
When I open a disk (removable compact flash card) for the first time and WinHex reads the disk image, I get a host of Messages, such as: Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 8FE80. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 8FEC0. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 8FF00. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 8FF40. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 8FF80. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 8FFC0. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 90000. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 90040. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 90080. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 900C0. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 90100. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 90160. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 95F20. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 95F80. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 91EA0. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 91F00. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 91F40. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 91F80. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 91FC0. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset A1BF60. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset A0060. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset A00C0. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset E225340. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset E225380. Notices about directly following invalid entries have been suppressed. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset E2253E0. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset E225420. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset F513E40. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset CB88D20. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset CB88D60. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 10D23E80. Drive F: Invalid, corrupt or simply unexpected directory entry found at offset 10D23F80. Notices about invalid directory entries are no longer displayed. When I view the various memory locations that WinHex is complaining about, they correspond to the 1st letter of a file or directory name. The contents of this drive works fine when installed in our machine...it is used as the hard drive and boots up Window XP OS and our application. My question is: "How serious are these errors?" Is this something I need to be concerned about? Windows XP embedded OS doesn't complain about it. Please help as I don't understand what is going on here. | ||
| Stefan Fleischmann Username: admin Registered: 1-2001 |
Could you e-mail me 1 or 2 examples, please? I.e. 32 bytes from the specified offset each? (Select as block, then Edit | Copy Block | Into New File). If Windows can access these files, then there is no problem. Only the directory entries are not strictly compliant with the FAT specifications, at least not as WinHex understands them. | ||
| Antony Ambrose Username: antonyambrose Registered: N/A |
Hello, when I open a 1GB SD card (FAT16 formatted) with some data, I am getting a following message. Drive H: Invalid, corrupt or simply unexpected directory entry found at offset 252576. If I search for the particular file in windows explorer there is no such file are directory. and also if the card is formatted with FAT32 and the same data is copied into the card this problem is not seen. Please clarify. I am attaching the screen shot to you in an e-mail. Best Regards, Antony.A | ||
| Stefan Fleischmann Username: admin Registered: 1-2001 |
I think it's because of the space character in the middle of the filename, which is not permitted in FAT. | ||
| Antony Ambrose Username: antonyambrose Registered: N/A |
After some analysis , this particular file is a windows system file EA DATA.SF, which purposefully has space in it. I think in Winhex it is not handled. Please consider this. |