I stuck my customers drive into a test bed machine I have and it did what I expected any good drive to do that had been moved to a different system Started to boot windows then BSOD. This was much further in the boot process - so the boot sector and mbr where good. I stuck the test beds xp drive on the customer computer and it actually attempted to boot windows xp.
This actually through me I expected to get the same disk read error. This Drive as much smaller a 40 GB drive. I removed all extra add on card and removed all but the primary drive I check the jumpper setting as suggested here. They were set to cable select vs. Again after years of the machine running was not sure why this would have an effect but it does not take long. After years of the machine running and no hardware changes, with no issues, I do not know why flashing the Bios would make a difference Flashing the BIOS worked.
Now if someone could tell me why it worked, I might be able to sleep tonight. BTW on point 5 trying to getting into the recovery console but would only get a blank screen, after the BIOS flash the XP setup does get through loading the drivers and you do get the choice to press R to get to the recovery console.
I wanted to test it. Think it might help to have a little more detail. I wish I had documented the verision before the update. Sounds like your customer was pretty good about taking care of their machine, and kept up with current updates. I think what might have happened was, hardware drivers updated for something on their machine; drivers that assumed a more current version of the bios was present.
Machine attempts to boot, and voila, disk error. Hopefully that helps you sleep. What I am pointing out is that for those who thinks that they know it all, really don't have alot of experience as I do.
I have done my best to offer them my advice on how to resolve the issue that they are experiencing. It is nice for those that shared their own resolved issues with others, that's good. However, those being smarty-pants trying to "outsmart" me had forced me to use CAPS to warn them and I cannot assist them.
In the meantime, this is not an argument board. I have already offered my advices already that you can either take it or leave it. As a last resort to the current issues here, many computers are not the same because of the make and models of many different manufacturers.
These problems results in different solutions. As you mentioned about configurations from 19 or 20 years ago, yes I do remember that. Thank you for your input and your attention.
Im using HCL laptop My computer less than six months old was working last night. Three weeks ago had to create a new user account as the default user profile was corrupted. This also happened to me after a restart. I think this problem generally appears after new OS install, work with partition managers such as Partition Magic, gparted and so on. So try that and hopefully you should not get that error message again. This has resolved my issue and the Mini installation wizard was able to finish setting both machines up without any dramas.
Might be one to look at, Only if you get this error after installing a fresh copy of windows on the machine. Hi, After I finished my section D, it still cannot boot up. After that, I proceed to section E , but it stop in the black screen after "Setup is inspecting your Hardware configuration".
Any idea on this? Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows Vista Setup. For deployment issues, please use the Windows Vista Deployment and Imaging forum. Sign in to vote. Friday, September 7, PM.
The boot order should be placed in the following order: 1. CD-ROM 3. Monday, November 19, AM. Any ideas anyone? Proposed as answer by romneck Thursday, May 7, AM. Wednesday, October 31, AM. If anyone has any ideas to resolve this - please let me know Proposed as answer by j prince Thursday, May 14, PM. Friday, November 9, PM. Thursday, November 15, AM. Monday, January 7, AM. Wednesday, January 9, AM.
Saturday, January 12, PM. Sunday, January 13, AM. Update: Please see pages 3 and 5 for further info. Sunday, February 24, AM. Oh i had the hard drive first and the CD-Rom second. But now i cant go to neither because the only screen i'm stuck on is the "Invalid Boot diskette: Insert disk in A:" screen so i'm going to definitely need professional help. Monday, February 25, PM. Tuesday, February 26, AM. Wednesday, February 27, PM. Thursday, February 28, AM.
Saturday, March 8, AM. Tuesday, March 25, AM. Thursday, April 10, PM. Powhammer wrote: For those of you having this problem, Here's your answer. Saturday, April 12, PM. Completely Agree with you Stalk. Powhammer is just posting a link to AVG, and Grisoft,. If you are currious you can Google it yourself. Thursday, April 17, PM. Friday, April 18, AM.
This has nothing to do with the problem, how is this relevant to the fact that this problems appears for no reason on a machine that was previously working Hey, powhammer J-D Powers called they want to give you an award for the most useless "advise" on the net. Saturday, April 19, AM. Saturday, April 19, PM. Thursday, April 24, PM. Hi Ciara, Thank you for your input. Friday, April 25, AM.
Thanks, Ciara. I was suspecting a sick motherboard, so it was a pleasant surprise when I swapped out the sata cable and the thing booted right up! Back to doing better things Thursday, May 15, PM. I switched my computer on this morning and got this problem. Sunday, May 18, AM.
Powhammer wrote: If they had mentioned it, I would have that resolved for them in a snap. So far I have tried: 1. Checked the bios, everything is detected as normal. Tried a different IDE cable 3. Took the motherboard battery out and put it back in None of these things work. I think the last thing that was installed before this happened was Windows Malicious Software Removal Tool. This problem just happened when I switched it on this morning.
Very annoying, I have to say I suspect it's a Windows problem and Microsoft need to sort it out. Wednesday, May 21, AM. Thanks for any advice, Vince. Thursday, May 22, AM. I don't think the sata cable would just go bad on me if I wasn't tampering with it.
Friday, May 23, PM. I can't even boot the HDD. And when i press R for repairing the win xp using recovery console,the examine of the hard disk hangs.
I can't even repair. I need help here!!! Wednesday, June 18, PM. Thursday, June 19, AM. Thursday, June 19, PM. Sunday, June 22, PM. Monday, June 23, PM. Tuesday, June 24, AM. Look guys, I just don't have time for this talk or argue on this. Do you see my eyes peering in computers helping others out on here? I hear it by their words in description. There are many different problems that occurs with computers and NOT all computers are the same. And Ben, Check my post above again since you quoted it, ooopppsss, did you miss it?
Was that a mistake? Better in terms now. Depending on the severe conditions of Windows, sometimes you can do a repair through the Recovery Console and sometimes you HAVE to re-install Windows. Some newer hard drives are still the same as usual that have jumpers and there are others that are SATA drives that may not have jumpers. That's where people needs to mention about.
For multiple drives is pretty easy to do, but for some of those out there that don't have much experience, it is NOT easy for them. Now, I am NOT going to explain any further on how to fix anybody's computers as I have said enough that I posted above here. My best suggestion is for anyone to take their computers to their local professional computer technicians if they are unable to figure out what the problem is. That is what they are there for. I only help with just certain things that people are having issues with on their computers, NOT explain the entire "How-To-Do's".
Now, as I mentioned earlier above is this: Note: this information I have provided is completely accurate based on my performed experience successfully through professionalism and is in NO way as false information upon your attempt to repair on your own through failed results and lack of full knowledge. This is the bottom line that I tell anyone who tries to fix their computers on their own. If anyone happens to live in the same area as me, I would certainly fix it for them rather than having to explain to them of how to fix the problems and of course they're gonna get charged if they want me to fix it.
Enough said here. Saturday, June 28, AM. Friday, July 4, AM. Powhammer: Reported for trolling. Sunday, July 6, PM. Monday, July 7, AM. Monday, July 7, PM. Trolls use all caps. Powhammer uses all caps. Trolls threaten other forum members. Powhammer threatens other forum members. Trolls provide official sounding but ultimately questionable advice. Powhammer provides official sounding but ultimately questionable advice. Powhammer must be a troll.
Tuesday, July 8, AM. Superdave, My website is currently down for re-design. Tuesday, July 8, PM. You must be joking. Your "solutions" are potentially harmful. I am reporting you to Microsoft for dorkish behavior.
Wednesday, July 9, PM. Powhammer wrote: larue , No problem on the diagnosis larue. Tuesday, July 22, AM. Wednesday, July 23, AM. Try it mate lol oh and dont warn me, you have no right to do so now shutup No Thanks James Dartnell.
Thursday, July 24, AM. Powhammer wrote: Jaddie wrote: Try it mate lol oh and dont warn me, you have no right to do so now shutup No Thanks James Dartnell. I've had this problem for several months. In this forum string, I find FIVE pages of folks either having the problem or complaining about those trying to help. I never did find a cause or a 'fix for this Disk Read Error. About every other month it pops up on me, and my only recourse is the following: 1.
On a desktop unit it can be installed as a slave drive, or with a laptop PC you can purchase an external USB drive. When this 'Disk Read Error' pops up, I power off my desktop and swap the drives. I then power off my system, swap drives, and power-up with the newly formatted and Caspered drive!
And when things fail again, I do the same! It's a sure fix for a problem that I've not been able to resolved! Thank you!! Thursday, July 24, PM. Aztechie, I don't know why you are using the Casper software. If the BIOS shows this in the listing: 1.
FDD Floppy disk drive or vice-versa 2. CD-ROM or vice-versa 3. Friday, July 25, AM. Good Tips! I printed it out and will carefully read the details. It was for me a good work-around after I was unable to find the root cause of this error. It's run this way from day 1. Something else I've notice resulting in this error is if the PC hangs during a shutdown, and I have to hold the power off switch to kill it, next time I power on I see this error.
This is not always the culprit, but having to override a hung Windows shutdown has, on occasion, contributed to this error. Thanks again!
Friday, July 25, PM. I'd just like to point out that dells can in fact dual boot. I'm using one right now, stock motherboard. And no, it is not barebone. I mean I'm not meaning any disrespect, but if you are telling people that dells cannot dual boot, then I would be a little sketched out about taking any of your given advice. Like we understand that you are trying to help, but it's just going to be at the cost of peoples data and time.
You've been a computer technician for fifteen years you claim. I'm eighteen years OLD and can recognize errors in your posts. Like I don't mean to discredit your advice, but I feel like it's necessary as to prevent anyone from really screwing up their systems. Saturday, July 26, AM. Thanks James Dartnell.
This is just ridiculous and after reading this thread I have to respond. This forum is meant for people that are trying to solve problems, not a place where a simple problem such as PC not booting should be swept under the rug as being too complex. Contrary to what "professional PC techs" would like you to believe, it is possible for the average person to have success with PC repair and maintenaince, even if you have to go as far as running the recovery console to fix the problem.
It doesn't take any special training to type a simple "fixboot" command. All it takes is a set of instructions if you don't know what to do. It is perfectly o. It will not "fry out your motherboard and CPU. It is the constant turning off and on that is a problem because of the thermal stress placed on the components from heating up and cooling down constantly. Leaving it on all the time ensures a constant temperature so parts are not expanding and contracting which could cause things such as chip cases to split.
Obviously make sure your fans and heatsinks don't get too clogged with dirt and keep your computers off the floor if possible and you will have greatly reduced dust sucked into your machine. Also I have to second the notion that ensuring jumper settings are correct has no relevance to troubleshooting a previously working computer. Saturday, July 26, PM. Sunday, July 27, AM. Someone's tone has inexplicably changed. I wonder why. Oh well can't win here I guess. Monday, July 28, AM. Thanks James.
Monday, July 28, PM. Everyone is harping on the whole chip splitting thing, which is one example quoted out of the book. The point is of the enormous stress placed on solder joints due to thermal stress. Sorry its not something that you can look at and see. Of course not its called Its just part of being a power user. Besides as they say, "correlation does not imply causation" as in just because a whopping 3 people whose systems died left them on at the same time does not imply that leaving them on was the cause of the problem.
Try inadequate power supplies, leaking capacitors, etc, these could cause more problems. I am not going to go as far as "discrediting others for their mis-information" but check your facts. Also, Powerhammer. I'd recommend you familiarize yourself with how the boot loader works before you come out and say that the bios has nothing to do with finding the MBR. Most of your "facts" are just circular talk that doesn't have relevance to the problem at hand.
Tuesday, July 29, AM. Powhammer wrote: Alright, look it kids, I am not going to keep babbling on this old lousy story here. Why don't you both go and find something constructive to do instead of sitting in front of your computers rehashing this nonsense here, huh?
Thursday, July 31, AM. If anyone needs help ask and i will try to help Thanks James. The only thing on that IDE Bus ribbon cable are the two hard drives. However, I've heard a lot of discussion here on plugging Master and Slave, so I will follow your advice and do it! And I have run that Error Checking routine in the past -- possibly it's time to run it again to ensure the integrity of my hard drives! Tks PowHammer! AZ Techie! Friday, August 1, PM. Powhammer wrote: For those of you having this problem, Here's your answer: Make sure that the black jumper in the back of your main hard drive is set to "MA" MASTER as abbreviated according to the schematics shown on top of your hard drive.
Saturday, August 2, PM. Matt, I appreciate your concerns. Sunday, August 3, AM. I did not catch anyone say, but I could be wrong. Did you just make a system change, such as flash BIOS? Probably wont help anyone in the past, but for future reference - that was the fix for me.
I didn't lose any info, just changed those settings back and into the OS I went! Monday, August 4, PM. Hope it works. Tuesday, August 5, PM. Thank you Marley for your feedback. This can sometimes be a problem too as you mentioned. As you mentioned about to daisy chain the hard drives, at the same time, you can always back up your important files or data on the other hard drive before having to re-install the OS on the hard drive that caused a problem. It's important to partition the hard drive and format it completely before installing the OS.
Thanks again Marley. Wednesday, August 6, AM. Powhammer, You seem to have the right motivation, but lack the knowledge to help. Thursday, August 14, PM. Wight Man wrote: Powhammer, You seem to have the right motivation, but lack the knowledge to help. Thanks to everyone else for your time and information on the matter! Friday, August 15, AM. Thursday, September 4, PM. Monday, September 8, PM. Powhammer, am i right in thinking that if i have swaped the hdd round i have 3 in my comp 2 running from 1 ide cable and 1 from an expander ide card after getting the fault this thread is about and that the 2 drives that were my main 1's are now running from the expander card and the 3rd drive is now pluged into the main ide cable and is the only 1 not working that my problem could just be a faulty ide cable that is pluged into the mother bord?
Thursday, September 11, PM. Sunday, September 21, AM. Monday, September 22, AM. If your HD can be picked up by a friend's pc or maybe you have another pc of your own, connect this drive up and try to run the Windows defrag on the drive. I had this issue a while back and ran Windows defrag on it and seemed to fix it. May as well give it a try. Saturday, September 27, PM. Sunday, September 28, PM. In my case it was a bad Ribbon Cable. This despite the fact that I had just installed a new one.
Go figure. Just my luck. Monday, September 29, AM. Friday, October 3, PM. Dear guys. Wednesday, October 15, AM. Thursday, October 23, AM. Just a note, I first had Vista Ultimate bit installed, however then oddly enough no sound came out, so I repaired using Windows Vista, which didn't help, and then I also reformated the HD and installed Vista, but that failed as I received an error message during installation, x and so then I though maybe the cd itself is bad so I tried to install XP Pro Media Center but same error came up, and then this new error message came up, "system read error Thursday, October 23, PM.
Dear Mr. Powerhammer, Technician Guru Infinite Ah yes, 15 years experience. That is certainly a fine accomplishment and deserves a tip of the hat to you. Unfortunately your maturity and intelligence doesn't have the same years of experience. But at least you know how to find the CAPS key to blast people who have more sense of the right solution than you. You are absolutely right though, ANYONE can pose as a technician and obviously running your own computer business has obviously gone way too far to your head.
But I'm sure your loyal clients ie. Mom hold you in high esteem. If you had in fact "investigated further" you would find your Nuke-It-and-Reinstall-It-All tech strategy is the core philosophy of IT persons who are too proud and full of themselves to "investigate further," and subsequently ignorant of their ill advice. Anyone can be a technician if the answer to every problem is to reinstall. Let me say right now, I am not a technician.
But i do clearly remember cleverly tweaking my memory configs and autoexec. Think back some 19, 20 years ago. In Stalk's defence, my Disk Read Error came subsequently after one of two actions; 1 a Diskeeper MFT boot defrag, which is not unlikely seeing as the boot files couldn't be read properly afterwards, or 2 a Windows Vista Update. Of course, who really knows with Windows Vista. The solution? Now I'm here havin' fun, and still have all my precious data.
Friday, October 24, AM. Had this error happen today on my wife's laptop. Opted to do the recovery console and fixboot command. Laptop is up and running again. Sunday, October 26, AM. Monday, October 27, PM. Tuesday, October 28, AM. Tuesday, October 28, PM. All disk were detected fine. Wednesday, October 29, PM. Danny, Sounds like your customer was pretty good about taking care of their machine, and kept up with current updates.
Friday, October 31, AM. Tuesday, November 11, AM. Table of Contents:. How do I fix a read-only hard drive error in Steam? Update your drivers.
Delete the 0KB file. Delete corrupted files in the log file. Check the integrity of the game files. Run flush config. Set full security controls on the Steam folder. Hotmail had upgraded it back to FreeBSD for its efficiency and stability. So the system is more stable and can serve more customers at the same time and save more money on maintenece.
Regarding the Windows boot issue, many factors can cause it. I hope the following threads can help you efficiently. Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. Regarding the older HD issue, please try to verity it in Computer management.
Right click Computer and select Manage. Click on Disk Management. If drive do not have a letter, please right click the drive and select Change Drive Letter and Path, give the drive a letter and you are all set. Restart the computer to test this issue again. Regarding the forum suggestions, thank you for your feedback.
Microsoft is testing the new forum and will release it in future.
0コメント