Burnt out from error error error! Time to go back to Paper.

[QUOTE=Elljay;2875398]

ICit2lol said:

Elljay said:

Me I am not clever or patient enough to tutorials and just put out my dittys as I call them:)

Ditty. I like that. I had to look it up. Lol.

LOL!! It is a term we used to use when I was much younger back in England where I come from. It was just our way of saying "I do this and it works for me - try it" in a short spiel >
noun
noun: spiel; plural noun: spiels

1. 1.
   an elaborate or glib speech or story, typically one used by a salesperson.
   "he delivers a breathless and effortless spiel in promotion of his new novel"
   synonyms:speech, line, patter, pitch, sales pitch; Moremonologue, rigmarole, story, saga
   "he launched into a big spiel about the merits of the product"
   
   
   
   
   
   
   

verb
verb: spiel; 3rd person present: spiels; past tense: spieled; past participle: spieled; gerund or present participle: spieling

1. 1.
   reel off; recite.
   "he solemnly spieled all he knew"
   
   
   
   

just in case you are wondering what that one is

Elljay said:

Waiting for your expertise...Where do we go from here Anak?

I'm still trying to figure this one out, but I'm fresh out of ideas Elljay.

So, I've sent a VM to gregrocker to take a look at your situation and see if he can help figure this one out for us.
You may see me answering some of his questions, if I'm incorrect don't hesitate to make clarifications.


EDIT:
Can you remember if you've ever gone into the BIOS using F10 and changed anything?

I understand you were trying to repair your Win7 following Troubleshooting Windows 7 Failure to Boot which first determines if there is infection to clear. You tried to run Kapersky Rescue disk but didn't appear to find out how to use it to scan for infection even though a tutorial was posted earlier showing exactly how this is done. Here is another: How to Use the Kaspersky Rescue Disk to Clean Your Infected PC

In such cases try using a different AV scan CD so that you get at least one good boot scan to determine if your PC is infected, then try starting in normal or Safe Mode to run a full Malwarebytes scan. If it won't start I would try a different boot scan.

The Troubleshooting Windows 7 Failure to Boot steps lead up to possibly running Factory Recovery or doing the vastly superior Clean Reinstall - Factory OEM Windows 7. HP's have the worst load of bloatware in the industry, making it the worst install of WIn7 once can possibly have even when freshly restored. So I'd strongly consider looking over the reinstall steps including the Special Note for HP Owners at the end so you can take this opportunity to do the best install of Win7 instead of the worst one.

Otherwise if you cannot run Perform an HP System Recovery (Windows 7) | HP® Support and have not made the Recovery disks earlier when Win7 was running, then make sure Recovery is the Partition - Mark as Active to see if it will then respond to the proper key. Anak gave you a picture of a typical HP disk configuration to help determine which is the Recovery partition to mark Active from Diskpart commands in the blue link.

If the F11 key will not respond then try booting with the ESC key to access F11. If that fails then try the ESC key to run Diagnostics to see if the onboard diagnostics will boot and run. This will tell you the condition of your hardware, and let's you know that the Tools partition is functional so is worth saving if you reinstall.

If Recovery cannot be made to boot then a way to salvage it is to do a rescue install of Win7 to C, afterwards add the Recovery partition to a Dual Boot to Boot Recovery Partition using EasyBCD which should run Recovery to reinstall to C.

But since you need to reinstall Win7 to C to do this, it's better to invest the time and effort in a Clean Reinstall - Factory OEM Windows 7 while deleting all partitions during the install to create/format New as shown in tutorial, unless Diagnostics will run in which case I would save the OEM Tools partition but delete all others.

Changing the boot order is okay.

Have you read over Greg's post; Read it carefully, is there anything there that you feel you've tried and didn't work?

In which direction do you think we should proceed?

Hi Elljay, haven't heard from you, this series of CMD's using DISKPART should get your netbook running again.

The capitalized CMD's are to make it easier for you to see, they do not have to be capitalized.

• Boot with the repair disk you made.

• At the Command Prompt type; DISKPART.

• After the prompt changes to DISKPART, type; LIST DISK. You should see a list with your optical drive, the hard drive, and card reader ports.

• In order to be sure we are working with the hard drive (HDD) only, type; SELECT DISK 0 (That is a zero not a letter O). You should see; “Disk 0 is now the selected disk”.

• At the next DISKPART prompt, instead of List Volume type; LIST PARTITION.

   Note

You should see a list of the partitions on the netbook's hard drive disk (HDD). What we're after is that Volume E – Recovery volume, if the partition is not labeled as Recovery then the only thing you can go by is the size of the partition.

In your pix of the volumes in post #46 select the one that matches the 15 GB size of the Volume 3 E Recovery. The pix is showing Volume 3 as the third partition in descending order.

But, when I do it on my machine, my recovery is named recovery and it is listed as partition "1". If you are unsure take a screenshot and post it so we can look at it to make sure which one you need to select.

• You would type in; Select PARTITION 3 or ? - You should see; Partition 3 or ? is now the selected partition.

• At the next Diskpart prompt, type; ACTIVE. - You should see; "Diskpart marked the current partition active".

• At the next Diskpart prompt, type Exit.

The CMD window should close and bring you back to the repair disk screen, close it out and remove the repair disk from the optical drive. If everything is already closed out remove the rescue disk.

• Restart your netbook, and observe.

Since you mentioned in earlier conversation that you have already gone through the recovery process, watch to see if this restart looks like the recovery process you are used to. If anything looks abnormal please take screenshots and post them in your next reply, with providence the recovery will take and you will have your netbook back.

Am now wondering if the hard drive is a suspect one myself and the failure of most things so far ie the running of the Kaspersky rescue disk has me foxed as it should just boot into the program with very little difficulty
In fact I would not be surprised if there were more than the hard drive being at fault