 Orphan
join:2002-04-20 New York, NY
| [Word] Wife's Word docs randomly corrupt- Why?
Office 2003
about once a month or so my wife opens one her work often accessed Word docs & receives a message that a converter is required. Why?
today she opened a doc not used in a month. Received conversion request.
Then when conversion is attempted- it fails.
What might be happening.
Might the free auto backup app FBackup have anything to do with it. But if so, why so random? |
|
  GILXA1226 Premium,MVM join:2000-12-29 London, OH clubs: | How big are the docs? Do they have a lot of images/figures/embedded objects in them? |
|
  Cudni La Merma - Vigilado Premium,MVM join:2003-12-20 Someshire | reply to Orphan also, check event viewer for errors and or run chkdsk to rule out hardware issue |
|
  Oregonian Premium join:2000-12-21 West Linn, OR | reply to Orphan Are these docs that she alone has acccess to or could someone else have modified them between the times she opened them? If the latter, perhaps someone else is opening them in Word 2007 and saving them in that format? |
|
 Orphan
join:2002-04-20 New York, NY
| reply to Orphan Did SMART HD check with HD Inspector Pro -all is ok
She just hkeeps docs at home, which she daily backs up to home external drive.
No one has or had access to files.
I copied one of docs onto my pc with office 2007 & still unreadable & failed conversion. |
|
 Orphan
join:2002-04-20 New York, NY
| reply to Orphan So, uninstalled office & reinstalled. But only had Office XP PRO
Was able to install converter, but after conversion, this is what a Human Resources file ended up looking like:
\SET58.tmp (6.0.2900.3527) 1.657: Destination:C:\WINDOWS\system32\wininet.dll (6.0.2900.2861) 1.657: Source:C:\WINDOWS\system32\SET59.tmp (6.0.2900.3527) 1.657: Destination:C:\WINDOWS\system32\urlmon.dll (6.0.2900.2870) 1.657: Source:C:\WINDOWS\system32\SET5A.tmp (6.0.2900.3527) 1.657: Destination:C:\WINDOWS\system32\shlwapi.dll (6.0.2900.2861) 1.657: Source:C:\WINDOWS\system32\SET5B.tmp (6.0.2900.3533) 1.657: Destination:C:\WINDOWS\system32\shdocvw.dll (6.0.2900.2877) 1.657: Source:C:\WINDOWS\system32\SET60.tmp (6.0.2900.3527) 1.657: Destination:C:\WINDOWS\system32\mshtml.dll (6.0.2900.2873) 1.657: Source:C:\WINDOWS\system32\SET99.tmp (5.1.2600.3466) 1.657: Destination:C:\WINDOWS\system32\gdi32.dll (5.1.2600.2180) 1.657: Source:C:\WINDOWS\system32\SETA0.tmp (8.100.1048.0) 1.657: Destination:C:\WINDOWS\system32\msxml3.dll (8.50.2162.0) 1.657: Source:C:\WINDOWS\system32\SETA7.tmp (5.1.2600.3462) 1.657: Destination:C:\WINDOWS\system32\netapi32.dll (5.1.2600.2180) 1.657: Source:C:\WINDOWS\system32\SETB5.tmp (5.1.2600.3494) 1.657: Destination:C:\WINDOWS\system32\winhttp.dll (5.1.2600.2180) 1.672: Source:C:\WINDOWS\system32\SETD2.tmp (5.1.2600.3394) 1.672: Destination:C:\WINDOWS\system32\mswsock.dll (5.1.2600.2180) 1.672: Source:C:\WINDOWS\system32\SETD3.tmp (5.1.2600.3394) 1.672: Destination:C:\WINDOWS\system32\dnsapi.dll (5.1.2600.2180) 1.672: Source:C:\WINDOWS\system32\SETD4.tmp (5.1.2600.2975) 1.672: Destination:C:\WINDOWS\system32\6to4svc.dll (5.1.2600.2180) 1.672: Source:C:\WINDOWS\system32\DllCache\SETD5.tmp (5.1.2600.3394) 1.672: Destination:C:\WINDOWS\system32\DllCache\tcpip6.sys (5.1.2600.2180) 1.672: Source:C:\WINDOWS\system32\DllCache\SETD6.tmp (5.1.2600.3394) 1.672: Destination:C:\WINDOWS\system32\DllCache\tcpip.sys (5.1.2600.2180) 1.672: Source:C:\WINDOWS\system32\DllCache\SETD7.tmp (5.1.2600.3394) 1.672: Destination:C:\WINDOWS\system32\DllCache\mswsock.dll (5.1.2600.2180) 1.672: Source:C:\WINDOWS\system32\DllCache\SETD8.tmp (5.1.2600.3394) 1.672: Destination:C:\WINDOWS\system32\DllCache\dnsapi.dll (5.1.2600.2180) 1.672: Source:C:\WINDOWS\system32\DllCache\SETD9.tmp (5.1.2600.3394) 1.672: Destination:C:\WINDOWS\system32\DllCache\afd.sys (5.1.2600.2180) 1.672: Source:C:\WINDOWS\system32\DllCache\SETDA.tmp (5.1.2600.2975) 1.672: Destination:C:\WINDOWS\system32\DllCache\6to4svc.dll (5.1.2600.2180) 1.672: Source:C:\WINDOWS\system32\_000006_.tmp.dll (5.1.2600.2180) 1.672: Destination: 1.672: Source:C:\WINDOWS\system32\SET102.tmp (6.0.2900.3402) 1.672: Destination:C:\WINDOWS\system32\shell32.dll (6.0.2900.2180) 1.672: In Function GetReleaseSet, line 1240, RegQueryValueEx failed with error 0x2 1.672: SetProductTypes: InfProductBuildType=BuildType.IP 1.672: SetAltOsLoaderPath: No section uses DirId 65701; done. 1.688: DoInstallation: FetchSourceURL for c:\windows\softwaredistribution\download\ab02de9444a68e46b9d94dbc7903bc14\update\update_SP2GDR.inf failed 1.688: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB958687$ 1.704: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102 1.750: BuildCabinetManifest: update.url absent 1.750: Starting AnalyzeComponents 1.750: AnalyzePhaseZero used 0 ticks 1.750: No c:\windows\INF\updtblk.inf file. 1.750: OEM file scan used 0 ticks 1.813: AnalyzePhaseOne: used 63 ticks 1.813: AnalyzeComponents: Hotpatch analysis disabled; skipping. 1.813: AnalyzeComponents: Hotpatching is disabled. 1.813: FindFirstFile c:\windows\$hf_mig$\*.* 1.829: KB958687 Setup encountered an error: The update.ver file is not correct. 1.829: KB958687 Setup encountered an error: The update.ver file is not correct. 1.829: KB958687 Setup encountered an error: The update.ver file is not correct. 1.829: KB958687 Setup encountered an error: The update.ver file is not correct. 1.844: KB958687 Setup encountered an error: The update.ver file is not correct. 1.844: KB958687 Setup encountered an error: The update.ver file is not correct. 1.844: KB958687 Setup encountered an error: The update.ver file is not correct" %c®âyÿ ë×
T15Ãàèá壨ݴëvõÿ xx¿a® B\´põ%¥ûÝïþE fPÍv$Ù@O ÿ ë×v[O(¡RµÆS«jò¥V?»Ý[úkcÞÊ(ä g|e ØÙE9ÑM{+ßáÝ»iwÔ
ª84E?f# µÐgóÞ¾Ú "ÀaãNQ|§ ®gµÓ¿à~
ÕIÿ cåôéÔP«J Ö´½î -ÔP%ÀHWq *ã5óÚX*xÅJ
9E]Ú\oécä³* ],Â4p¸: ÃV£B ®Ý-n¿$ÖÆ9* þxð9f »ç«BO£±¾_àñ çÃÆ-ï*QJÞI *^Cmov cê )]ÇÐ
ÕIÿ cåôéÔP«J Ö´½î -ÔP%ÀHWq *ã5óÚX*xÅJ
9E]Ú\oécä³* ],Â4p¸: ÃV£B ®Ý-n¿$ÖÆ9* þxð9f »ç«BO£±¾_àñ çÃÆ-ï*QJÞI *^Cmov cê )]ÇÐ
ÕIÿ cåôéÔP«J Ö´½î -ÔP%ÀHWq *ã5óÚX*xÅJ
9E]Ú\oécä³* ],Â4p¸: ÃV£B ®Ý-n¿$ÖÆ9* þxð9f »ç«BO£±¾_àñ çÃÆ-ï*QJÞI *^Cmov cê )]ÇÐ
¸÷® |
|
 Orphan
join:2002-04-20 New York, NY | reply to Orphan Could it be the auto backup application? |
|