oktoberfest

alright I did a /sfc scannow and here is what the sfcdetails.txt log says 2009-02-09 14:31:29, Info CSI 00000006 [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:29, Info CSI 00000007 [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:30, Info CSI 00000009 [SR] Verify complete 2009-02-09 14:31:31, Info CSI 0000000a [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:31, Info CSI 0000000b [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:33, Info CSI 0000000d [SR] Verify complete 2009-02-09 14:31:33, Info CSI 0000000e [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:33, Info CSI 0000000f [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:34, Info CSI 00000011 [SR] Verify complete 2009-02-09 14:31:34, Info CSI 00000012 [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:34, Info CSI 00000013 [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:34, Info CSI 00000015 [SR] Verify complete 2009-02-09 14:31:35, Info CSI 00000016 [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:35, Info CSI 00000017 [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:35, Info CSI 00000019 [SR] Verify complete 2009-02-09 14:31:35, Info CSI 0000001a [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:35, Info CSI 0000001b [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:35, Info CSI 0000001d [SR] Verify complete 2009-02-09 14:31:36, Info CSI 0000001e [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:36, Info CSI 0000001f [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:36, Info CSI 00000021 [SR] Verify complete 2009-02-09 14:31:36, Info CSI 00000022 [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:36, Info CSI 00000023 [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:36, Info CSI 00000025 [SR] Verify complete 2009-02-09 14:31:37, Info CSI 00000026 [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:37, Info CSI 00000027 [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:37, Info CSI 00000029 [SR] Verify complete 2009-02-09 14:31:37, Info CSI 0000002a [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:37, Info CSI 0000002b [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:38, Info CSI 0000002d [SR] Verify complete 2009-02-09 14:31:38, Info CSI 0000002e [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:38, Info CSI 0000002f [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:39, Info CSI 00000031 [SR] Verify complete 2009-02-09 14:31:39, Info CSI 00000032 [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:39, Info CSI 00000033 [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:39, Info CSI 00000035 [SR] Verify complete 2009-02-09 14:31:40, Info CSI 00000036 [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:40, Info CSI 00000037 [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:40, Info CSI 00000039 [SR] Verify complete 2009-02-09 14:31:40, Info CSI 0000003a [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:40, Info CSI 0000003b [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:40, Info CSI 0000003d [SR] Verify complete 2009-02-09 14:31:41, Info CSI 0000003e [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:41, Info CSI 0000003f [SR] Beginning Verify and Repair transaction 2009-02-09 14:31:41, Info CSI 00000041 [SR] Verify complete 2009-02-09 14:31:41, Info CSI 00000042 [SR] Verifying 100 (0x00000064) components 2009-02-09 14:31:41, Info CSI 00000043 [SR] Beginning Verify and Repair transaction It could only get to 19% done since it said that "Windows Resource Protection found corrupt files but was unable to fix some of them." However, I don't seem to see anything wrong in the log file, so I have no idea what files it is talking about When my computer did the check disk before, it did it on its own, I didn't tell it to. I will try the /r /f thing now edit: that didn't really do anything so I decided to look at the CBS.log and it has a lot more info than the sfcdetails.txt file. Here is where the sfc scannow fails 2009-02-09 16:02:34, Error CSI 00000044 (F) STATUS_OBJECT_NAME_NOT_FOUND #898531# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (STANDARD_RIGHTS_READ|FILE_READ_ATTRIBUTES), oa = @0xe8e894->OBJECT_ATTRIBUTES {s:24; rd:NULL; on:[91]"\?? \C:\Windows\WinSxS\x86_dot4prt.inf_31bf3856ad364e35_6.0.6001.18000_none_6d3b23766cb698be"; a: (OBJ_CASE_INSENSITIVE)}, iosb = @0xe8e8b4, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = 0x00004000, eab = NULL, eal = 0, disp = Invalid) [gle=0xd0000034] 2009-02-09 16:02:34, Error CSI 00000045@2009/2/10:00:02:34.246 (F) d:\rtm\base\wcp\sil\merged\ntu\ntsystem.cpp(1817): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null) [gle=0x80004005] 2009-02-09 16:02:43, Error CSI 00000046 (F) STATUS_OBJECT_NAME_NOT_FOUND #898530# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034] 2009-02-09 16:02:43, Error CSI 00000047 (F) STATUS_OBJECT_NAME_NOT_FOUND #898529# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0xe8ec78->SIL_OBJECT_ATTRIBUTES {s:20; on:"x86_dot4prt.inf_31bf3856ad364e35_6.0.6001.18000_none_6d3b23766cb698be"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid) I had to edit the spacing because some lines would stretch for like three screens across I looked it over, and a C:\Windows\winsxs\x86_dot4.inf_31bf3856ad364e35_6.0.6001.18000_none_dc7405a5dc041870 folder does not exist for me. now I'm not sure what to do. I don't believe my Vista DVD has these files with regards to "d:\rtm\base\wcp\sil\merged\ntu\ntsystem.cpp(1817)," my D drive is my DVD drive, so that's real weird. My hard drive has always been my C drive (never had any separate partitions or anything)

I'm running Vista Ultimate 32-bit ok so when I pop in the Office Ultimate 2007 DVD and open up setup, it'll show the window saying "Please wait while setup prepares the necessary files..." Then that window will just close and give me an error message: "Description: Setup did not complete successfully. We are sorry for the inconvenience. Problem signature: Problem Event Name: Office12Setup Problem Signature 01: {10120000-0F00-0000-0000--0000000FF1CE} Problem Signature 02: 12.0.4518.1014 Problem Signature 03: X Problem Signature 04: MsiAPICallFailure Problem Signature 05: ULTIMATER\UltimaterWW.xml Problem Signature 06: X Problem Signature 07: X OS Version: 6.0.6001.2.1.0.256.1 Locale ID: 1033 Additional information about the problem: LCID: 1033 Read our privacy statement: [url="http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409"]http://go.microsoft.com/fwlink/?linkid=501...mp;clcid=0x0409[/url] I actually already have it installed, but now I wanted to go add Outlook 2007, which I didn't install when I first installed. So something happened. Another thing I tried is going to Programs and Features (add or remove programs) and selecting Office Ultimate 2007 and hitting Change. A similar "preparing files" windows shows up but it just closes shortly thereafter, with no error message. Because of this fact, I also don't think there is anything wrong with my DVD. One thing that did happen about a week ago was that my AOL Instant Messenger got screwed up. I would try to open AIM6.exe but windows said it couldn't find the it and it couldn't be opened or something (something also to do with like administrator... I forgot. But I did try running as administrator and it wouldn't work). I went to the AIM install folder and tried opening AIM6.exe and I got the same error message. I restarted my computer. I tried again, but this time the AIM6.exe was completely gone. OK, that's fine, so I reinstalled it, and was on my way. I believe I shut down my computer later, and when I booted it back up, my computer did a check disk, and it did a TON of stuff, like it was an endless stream of messages, correcting errors and deleting stuff and whatnot. I have a feeling that this is what is causing my problems somehow, but I'm not sure After doing the check disk, I didn't really notice anything wrong so I just went with it. Only when I tried installing Office Ultimate again a couple days ago did I think there was a problem. I tried a system restore to the day I reinstalled AIM, but for whatever reason, I got a message saying the system restore failed and I should try a system restore for another date (there were none that were from an earlier time). So that was no go So I'm really having trouble figuring out what the problem is, and how to fix it. Google hasn't provided any answers yet.. and just to make this post even LONGER.. here's the checkdisk log I found. Level Date and Time Source Event ID Task Category Information 2/2/2009 5:37:27 PM Microsoft-Windows-Wininit 1001 None " Checking file system on C: The type of the file system is NTFS. One of your disks needs to be checked for consistency. You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. The segment number 0x1a3000000000 in file 0x1a28 is incorrect. Fixing incorrect information in file record segment 6696. The segment number 0x1a3100000000 in file 0x1a29 is incorrect. Fixing incorrect information in file record segment 6697. The segment number 0x1a3200000000 in file 0x1a2a is incorrect. Fixing incorrect information in file record segment 6698. The segment number 0x1a3300000000 in file 0x1a2b is incorrect. Fixing incorrect information in file record segment 6699. The segment number 0x1a7c00000000 in file 0x1a2c is incorrect. Fixing incorrect information in file record segment 6700. The segment number 0x1a7d00000000 in file 0x1a2d is incorrect. Fixing incorrect information in file record segment 6701. The segment number 0x1a7e00000000 in file 0x1a2e is incorrect. Fixing incorrect information in file record segment 6702. The segment number 0x1a7f00000000 in file 0x1a2f is incorrect. Fixing incorrect information in file record segment 6703. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x73a427 for possibly 0x1 clusters. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x73a427 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x1a30 is already in use. Deleting corrupt attribute record (128, """") from file record segment 6704. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x1a9e64 for possibly 0x18 clusters. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x1a9e64 for possibly 0x18 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x1a33 is already in use. Deleting corrupt attribute record (128, """") from file record segment 6707. The segment number 0x1aa800000000 in file 0x1a38 is incorrect. Fixing incorrect information in file record segment 6712. The segment number 0x1aa900000000 in file 0x1a39 is incorrect. Fixing incorrect information in file record segment 6713. The segment number 0x1aaa00000000 in file 0x1a3a is incorrect. Fixing incorrect information in file record segment 6714. The segment number 0x1aab00000000 in file 0x1a3b is incorrect. Fixing incorrect information in file record segment 6715. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x298179 for possibly 0x1 clusters. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x298179 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x1a7d is already in use. Deleting corrupt attribute record (128, """") from file record segment 6781. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x1d6ae6 for possibly 0xe clusters. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x1d6ae6 for possibly 0xe clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x1a7e is already in use. Deleting corrupt attribute record (128, """") from file record segment 6782. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x7ae89d for possibly 0x1 clusters. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x7ae89d for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x1aa8 is already in use. Deleting corrupt attribute record (128, """") from file record segment 6824. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x1b06402 for possibly 0xd clusters. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x1b06402 for possibly 0xd clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x1aaa is already in use. Deleting corrupt attribute record (128, """") from file record segment 6826. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x303534 for possibly 0x18 clusters. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x303534 for possibly 0x18 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x1aab is already in use. Deleting corrupt attribute record (128, """") from file record segment 6827. The segment number 0x1e2c00000000 in file 0x1e20 is incorrect. Fixing incorrect information in file record segment 7712. The segment number 0x1e2d00000000 in file 0x1e21 is incorrect. Fixing incorrect information in file record segment 7713. The segment number 0x1e2e00000000 in file 0x1e22 is incorrect. Fixing incorrect information in file record segment 7714. The segment number 0x1e2f00000000 in file 0x1e23 is incorrect. Fixing incorrect information in file record segment 7715. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x3482f1 for possibly 0x9 clusters. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x3482f1 for possibly 0x9 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x1e2d is already in use. Deleting corrupt attribute record (128, """") from file record segment 7725. The segment number 0x325c00000000 in file 0x3168 is incorrect. Fixing incorrect information in file record segment 12648. The segment number 0x325e00000000 in file 0x316a is incorrect. Fixing incorrect information in file record segment 12650. The segment number 0x325f00000000 in file 0x316b is incorrect. Fixing incorrect information in file record segment 12651. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xa3eec for possibly 0xf clusters. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0xa3eec for possibly 0xf clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x325c is already in use. Deleting corrupt attribute record (128, """") from file record segment 12892. Attribute record of type 0x80 and instance tag 0x6 is cross linked starting at 0xa3efc for possibly 0x1 clusters. Attribute record of type 0x80 and instance tag 0x6 is cross linked starting at 0xa3efc for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x6 in file 0x325c is already in use. Deleting corrupt attribute record (128, OECustomProperty) from file record segment 12892. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x47e4d3 for possibly 0x9 clusters. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x47e4d3 for possibly 0x9 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x325e is already in use. Deleting corrupt attribute record (128, """") from file record segment 12894. Attribute record of type 0x80 and instance tag 0x8 is cross linked starting at 0x47e4dc for possibly 0x1 clusters. Attribute record of type 0x80 and instance tag 0x8 is cross linked starting at 0x47e4dc for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x8 in file 0x325e is already in use. Deleting corrupt attribute record (128, OECustomProperty) from file record segment 12894. The segment number 0x37f500000000 in file 0x3765 is incorrect. Fixing incorrect information in file record segment 14181. The segment number 0x37f600000000 in file 0x3766 is incorrect. Fixing incorrect information in file record segment 14182. The segment number 0x37f700000000 in file 0x3767 is incorrect. Fixing incorrect information in file record segment 14183. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x19c468 for possibly 0x6 clusters. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x19c468 for possibly 0x6 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x37f5 is already in use. Deleting corrupt attribute record (128, """") from file record segment 14325. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x8c9706 for possibly 0x15 clusters. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x8c9706 for possibly 0x15 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x37f6 is already in use. Deleting corrupt attribute record (128, """") from file record segment 14326. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x5fd8a0 for possibly 0x5 clusters. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x5fd8a0 for possibly 0x5 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x37f7 is already in use. Deleting corrupt attribute record (128, """") from file record segment 14327. The segment number 0x45e600000000 in file 0x44a6 is incorrect. Fixing incorrect information in file record segment 17574. The segment number 0x45e700000000 in file 0x44a7 is incorrect. Fixing incorrect information in file record segment 17575. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x620856 for possibly 0x1 clusters. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x620856 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x45e6 is already in use. Deleting corrupt attribute record (128, """") from file record segment 17894. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xbc5db4 for possibly 0xa clusters. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0xbc5db4 for possibly 0xa clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x45e7 is already in use. Deleting corrupt attribute record (128, """") from file record segment 17895. The segment number 0x476e00000000 in file 0x475e is incorrect. Fixing incorrect information in file record segment 18270. The segment number 0x476f00000000 in file 0x475f is incorrect. Fixing incorrect information in file record segment 18271. The segment number 0x477000000000 in file 0x4760 is incorrect. Fixing incorrect information in file record segment 18272. The segment number 0x477100000000 in file 0x4761 is incorrect. Fixing incorrect information in file record segment 18273. The segment number 0x477300000000 in file 0x4763 is incorrect. Fixing incorrect information in file record segment 18275. The segment number 0x479c00000000 in file 0x4764 is incorrect. Fixing incorrect information in file record segment 18276. The segment number 0x479d00000000 in file 0x4765 is incorrect. Fixing incorrect information in file record segment 18277. The segment number 0x479e00000000 in file 0x4766 is incorrect. Fixing incorrect information in file record segment 18278. The segment number 0x479f00000000 in file 0x4767 is incorrect. Fixing incorrect information in file record segment 18279. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x1e241a for possibly 0x2 clusters. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x1e241a for possibly 0x2 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x476e is already in use. Deleting corrupt attribute record (128, """") from file record segment 18286. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x14a54 for possibly 0x1 clusters. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x14a54 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x479c is already in use. Deleting corrupt attribute record (128, """") from file record segment 18332. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x15fef73 for possibly 0x9 clusters. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x15fef73 for possibly 0x9 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x479d is already in use. Deleting corrupt attribute record (128, """") from file record segment 18333. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x1a79801 for possibly 0xc clusters. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0x1a79801 for possibly 0xc clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x479f is already in use. Deleting corrupt attribute record (128, """") from file record segment 18335. Deleted corrupt attribute list entry with type code 128 in file 20069. Unable to find child frs 0x1e22 with sequence number 0x4. The segment number 0x54b400000000 in file 0x549c is incorrect. Fixing incorrect information in file record segment 21660. The segment number 0x54b500000000 in file 0x549d is incorrect. Fixing incorrect information in file record segment 21661. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x41154 for possibly 0xc clusters. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x41154 for possibly 0xc clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x549d is already in use. Deleting corrupt attribute record (128, """") from file record segment 21661. The segment number 0x54b600000000 in file 0x549e is incorrect. Fixing incorrect information in file record segment 21662. The segment number 0x54b700000000 in file 0x549f is incorrect. Fixing incorrect information in file record segment 21663. The segment number 0x54c000000000 in file 0x54a0 is incorrect. Fixing incorrect information in file record segment 21664. The segment number 0x54c100000000 in file 0x54a1 is incorrect. Fixing incorrect information in file record segment 21665. The segment number 0x54c200000000 in file 0x54a2 is incorrect. Fixing incorrect information in file record segment 21666. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x356438 for possibly 0xe clusters. Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x356438 for possibly 0xe clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x54a2 is already in use. Deleting corrupt attribute record (128, """") from file record segment 21666. The segment number 0x54c300000000 in file 0x54a3 is incorrect. Fixing incorrect information in file record segment 21667. The segment number 0x553500000000 in file 0x54a5 is incorrect. Fixing incorrect information in file record segment 21669. The segment number 0x553600000000 in file 0x54a6 is incorrect. Fixing incorrect information in file record segment 21670. The segment number 0x553700000000 in file 0x54a7 is incorrect. Fixing incorrect information in file record segment 21671. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xadbd72 for possibly 0x1 clusters. Attribute record of type 0x80 and instance tag 0x3 is cross linked starting at 0xadbd72 for possibly 0x1 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x3 in file 0x54b6 is already in use. Deleting corrupt attribute record (128, """") from file record segment 21686. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x1b1e590 for possibly 0x33 clusters. Attribute record of type 0x80 and instance tag 0x1 is cross linked starting at 0x1b1e590 for possibly 0x33 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x1 in file 0x54b7 is already in use. Deleting corrupt attribute record (128, """") from file record segment 21687. Attribute record of type 0x80 and instance tag 0x1 is cross l"