Saved Bookmarks
| 1. |
Solve : Re: My big mission.? |
|
Answer» I know this TOPIC is extremely old, but to me it is the tip of an iceberg. I have found numerous hits when feeding a few of these file names into a search engine. It strikes me as very odd that the exact same files (whenever anyone takes the time to list them) have APPEARED over and over. I've seen responses on different boards suggesting to replace optical drives, that it might be the HDD going bad, you name it, but WHY this identical list of files? It strikes me as very odd that the exact same files (whenever anyone takes the time to list them) have appeared over and over. I've seen responses on different boards suggesting to replace optical drives, that it might be the HDD going bad, you name it, but WHY this identical list of files? I expect that the install routine copies files in a set order, in blocks. and that set of files that you listed are ones that are clobbered by a common problem (in many cases bad RAM ) Thanks for your response, Salmon Trout. What is intriguing to me is that it is the same set of files. If it were bad ram on all these different computers, don't you think the files might vary? Starting and stopping at different points, maybe? Have some different files names? And, Allan, thank you for moving the thread. I tacked it onto the old one because it was an example of what I was wanting to discuss, and the original poster's files matched the ones I listed. Quote from: Whirlaway on November 03, 2012, 02:35:44 PM Thanks for your response, Salmon Trout. What is intriguing to me is that it is the same set of files. If it were bad ram on all these different computers, don't you think the files might vary? Starting and stopping at different points, maybe? Have some different files names? I am only guessing here, but I wonder if a couple of things could be happening here: 1. The installer might copy files in blocks at a time, and if only a small amount of RAM is reported by the system, e.g. 256 MB, it copies a small number of blocks, and then gets the next set, and so on. If a larger amount of RAM is reported, say 1 GB, it copies more blocks in each phase. Possibly bad RAM after the first 1 GB is a common problem. I have read many stories of bad RAM causing this exact problem, including a forum thread of somebody who reported a very similar list of failed files as you and subsequently got a successful install after removing all but 128 MB of RAM. Another thing is you might have been Googling for that particular list of files and got lots of results. There might be other lists of files which give numerous search hits. Oh, wow. Now I see that there is no reference to the original thread at all and it was somewhat integral to my post. I'll try to connect the two, in concept, at least. It seemed to start around 2008 in which posts were being made, ASKING for help with a specific type of failed XP re-installation, ones that included a segment of the installation process that failed with the same result. A BSOD would appear and give a file name that Setup could not copy. Your choices were to Retry (Enter, which didn't work for any of us), Skip (apparently, all of us chose because we ended up with lists of the skipped files), and F3 to quit Setup. Now that a number of years have gone by, a lot more posts have been added to the search engines, all pretty much giving the same file list. (In addition, there are other posts that were probably related to this same issue, but included only a few of the names and don't show up in the search as readily.) It struck me as particularly strange that so many different people should be having the same issue, the same group of file names, over a period of years. Only common denominator that I can think of would be we were all recipients of software that had a flaw, regardless of the solution. I hope that ties my thread to the original poster's and makes it more understandable. ~ I definitely would have named it something else, had it been my original thread. Quote from: Whirlaway on November 03, 2012, 02:54:24 PM It struck me as particularly strange that so many different people should be having the same issue, the same group of file names, over a period of years. Only common denominator that I can think of would be we were all recipients of software that had a flaw, regardless of the solution. All the CDS have the same layout and the files are processed in the same order in every install process. The problem files might be all in the same compressed archive (CAB) file, which commonly gets clobbered by RAM trouble. Salmon Trout ~ Thanks again! I'm a fish out of water here (reference intentional, lol) so let me make sure I understand what you're suggesting. (I also messed up the Quoting feature, so this will be simple copy/paste.) The installer might copy files in blocks at a time, and if only a small amount of RAM is reported by the system, e.g. 256 MB, it copies a small number of blocks, and then gets the next set, and so on. If a larger amount of RAM is reported, say 1 GB, it copies more blocks in each phase. Possibly bad RAM after the first 1 GB is a common problem. Again, though, wouldn't it seem strange that so many of us, presumably with all sorts of different amounts of RAM, would get that same set? Another thing is you might have been Googling for that particular list of files and got lots of results. There might be other lists of files which give numerous search hits. As I was saying in my first post, I was lucky that one of the other people looking for help with this issue gave their list, because I only put in one file name, to start. I just saw that their list matched mine and clicked it. Perhaps theirs came up so close to the top because lots of other people with the same issue recognized their files, as well, and also clicked on it. Wouldn't number of hits drive that search result closer to the top of the first page, SEO and all that? In going back and forth between search results and the search main page, I started to see a commonality. It was later that I started entering more names and eventually the entire list, which brought me to this site. In the original poster's discussion with helpers here, I think using a different optical drive might have solved the problem. I don't have it to refer to at this point. There seem to have been different solutions that worked for different people. It's the root cause that grabbed my attention. Is it far-fetched to think a batch of Microsoft XP OS discs could have been sent out for an unknown period time with a flaw like that? Quote from: Salmon Trout on November 03, 2012, 02:59:55 PM All the CDS have the same layout and the files are processed in the same order in every install process. The problem files might be all in the same compressed archive (CAB) file, which commonly gets clobbered by RAM trouble. AHA!! That makes perfect sense. Perhaps the files are all in the same CAB file! That's why it's the same group, regardless of the solution. Finally, some sort of reasoning starts to dawn. I LOVE this feeling. LOL Thank you. I have another question, then, based on this. If it turns out that lots of those files might be something I don't actually need... for example, if all the usr*.* are for supporting USRobotics modems or something, and they turn out to be 1/2 of the missing files, couldn't I just locate the other files that are essential and import them, from another OS disc, into the area where this CAB file should be? Is it possible I could find that CAB file and see if the files are actually in there, just unattainable? |
|