Search Results for "system error 5121227"

XML was designed from the beginning to be intolerant of errors. This decision adversely affects MS Word's corruption recovery. With one error in the document.xml subfile where all the DOCX file's text is stored, instead of a partial recovery, Word will stop and throw an error. Savvy DOCX Recovery attempts to do precise surgery on corrupt Word documents to reorder or excise bad XML tags. If this doesn't work, it uses the command line app xmllint first to attempt to repair corrupt XML...

I recovered a hard disk which left me with a bunch of files (mostly .jpg files), some of which were duplicate. All the files were stored in a single directory, I needed a method to quickly identify duplicate files and confirm if the .jpg files could be opened. The DuplicateFileCheck application was created to simplify this process. You can select to either search the top-level directory or all sub directories (default action). All the files are enumerated with an md5 hash created, after this...

DOCX, XLSX and PPTX files are collections of conventionally zipped mostly XML sub-files. This program first attempts repair any zip based corruption. From there it engages in four different algorithmic attempts at repair or recovery. With the first method using validation, the location of the first XML error is sought. At that point the sub-files are truncated and repaired. The second method works the same way except the XML validation is more lax. With the third, the strict XML...

XML is intolerant of errors. This program will automatically salvage XML files by finding the first XML error, then truncating a configurable number of characters before the error and finally using the great xmllint to recover the xml file by automatically adding the correct end tags. The program starts with a default of 50 characters truncation. This truncation value may need to be changed if the truncation happens in the middle of a complex tag as xmllint may not know how to recover the...