computer problem

[skysidhe]

My son has a Sony Viao. The description of your original post happened to his and it's new! ( ish) I asked him what he did to fix it. He said he had to buy reformatting c/ds

That's all I know... except I won't ever buy a Sony laptop.

[Undertoad]

Diagnostics would not be interesting in a case where the MBR is trashed.

[Undertoad]

If it was me at this point I would probably try booting the original install CD/DVD and doing a Repair install.

Repair for XP

Repair for Vista

Repair for 7

[Pete Zicato]

That's a good idea toad.


You might also try pming mbpark. It think he specializes in this kind of thing.

[BigV]

pm

[Pete Zicato]

We've got people coming tonight, but I'll try to check in if I can.

Sounds like BigV might be offering too.

[jinx]

I gotta get out of the house.

[BigV]

While I'm waiting, I'll think out loud about problems like this. I'm not trying to patronize anyone.

The computer has a cpu, the central processing unit. The "big" chip that gets all the headlines. It's like the engine in a car. It takes a lot of parts to make a car go, but the engine is the component that gets the badge with displacement or aspiration, etc. In the computer, the cpu can only run instructions, just as the engine can only run on gas. When the computer is **first turned on**, there are no instructions. Lots of stuff has to happen first.

The first thing that happens when the power's turned on is a chip(s) in the computer that has built into it just a few instructions is activated. These instructions are the barest minimum that are needed to tell the computer where the pieces and parts are. Where to find more instructions and where to put the result of those instructions. The input and output systems of the computer. This is the BIOS, the Basic Input Output System. Every computer has something like this.

It is this bios that we were all frothing about at the start (and well into the thread). It is activated at the very *very* beginning, and it is the part where the computer gets to learn what hardware is where, like... your drive C:. What's on the C: drive? More instructions of course, not to mention your data. This is why we wanted to find out if the bios could see drive C:. Turns out you could see C:, a very good thing.

Now, once the bios has id'ed all the parts in the system (more or less), it hands control off to the next part, usually drive C:. Usually, but not always. For example, lj was able to boot (btw, boot is short for bootstrap loader. A bootstrap loader is a program on a chip/disk that starts a system from essentially nothing, just as you would levitate yourself by lifting up on your own bootstraps.) the system from the cdrom drive. The bios knew enough to boot, then hand off control to the next system. C: drive in this case was not working so the cdrom was the next choice.

At this point, we've booted the system to the point when we can use the instructions on **some** disk (hd or cdrom). Now the process repeats itself kind of, just like you'd shift gears in a car as you accelerate. This boot (not power on boot, but from a disk boot) process also has a starting point. The beginning part is called the Master Boot Record. This is a bit like the first groove on a vinyl LP (children, seek out your parents or grandparents for information on "vinyl LP"). If this groove is functioning properly, it guides the needle and tonearm to the rest of the record where the music plays, and so it works on your hd (hard drive). If this groove (boot record) has a scratch, you're kind of screwed. The needle and tonearm will not get to the music. Same is true for the hd, if the boot record is messed up, like if it is expecting to see the next instruction in location 1 but is instead directed to location 33, trouble will result. Imagine trying to listen to the record from the first groove and then jumping to groove 33. You'd miss a lot, right? So would the computer.

Fixing this in the computer is best left to a program that can detect this trouble and using the repair commands in that program. One of the previous post described this process with the fixmbr command. This seems like good advice in this case.

This is a good place to stop for now.

[xoxoxoBruce]

After reading that explanation in plain English, I'm awaiting the next installment with bated breath.

[tw]

Originally Posted by BigV

Fixing this in the computer is best left to a program that can detect this trouble and using the repair commands in that program. One of the previous post described this process with the fixmbr command.

As BigV described, BIOS is a program that exists only in the motherboard. BIOS then loads other programs from the hard drive, from the CD-Rom, or from a memory stick.

Programs it can load are comprehensive hardware diagnostic (from hard drive, CD-Rom, or from what was downloaded from the Sony web site), Console Recovery program (from the Microsoft CD-Rom), PTDD (from that CD-Rom), disk drive manufacturer's diagnostic (downloaded from the disk drive web site), DOS, or Windows (from hard drive or Microsoft CD-Rom). You choose what BIOS will load and execute by what you put into the CD-Rom or memory stick. Or by pressing F2 to select what you want to execute from that menu (same menu that jinx choose to boot with or without network support).

Fixmbr is only one of many repair programs available on the Recovery Console (one a Microsoft and Sony provided CD-Rom). It will fix software on the disk drive.

However if a diagnostic does not first confirm disk drive hardware is OK, then fixmbr might cause permanent data damage. That is why more responsible computer manufacturers (ie Dell, HP) provide comprehensisve hardware diagnostics for free. And why everyone knows Gateway and E-machines are crap.

Provided are numerous options. Same thing is posted by so many with different words. Every post at layman's level.

All solutions load and execute only when the BIOS does so. You select what the BIOS loads either by installing the appropriate CD-Rom (or memory stick) or by using that F2 key to select what to load.

Everything you have posted implies the motherboard CPU is talking to the disk drive's CPU.

[classicman]

Very well written post BigV - understandable even! thanks. Oh and what that retired xoB said.

[mbpark]

Hi,

Please do the following:

1. From the ultimate boot CD, go to Start -> Run -> compmgmt.msc
2. go to Disk Management from there.
3. See if you have a Disk 0 hard drive.
4. If you do, then go Start -> Run -> cmd
5. Run chkdsk c: /f from the Command Prompt

That will fix any small HD issues and let you mount the drive.

[jinx]

Ok, I will [attempt to] do that right now. Thank you.

[jinx]

1. check
2. check
3. no - only thing there is the dvd drive

[Pete Zicato]

Originally Posted by jinx

1. check
2. check
3. no - only thing there is the dvd drive

Yeah, that's what I would have expected given what you already tested. It sounds like the bios (hardware level) sees the hard drive, but the OS level doesn't. mbpark will have the best idea of what to do next.

It would be interesting to know though, whether your windows install cd gives you the option to try to fix the os.