[phillpower2]

Hello gmcube

You would at present appear to have a rather jumbled up configuration on your HDD and the data on it

I would like to have a second pair of eyes look at this so if you will, please provide the details of the installation disk that was used to install the OS and where the disk was obtained.

[Advertisements]

My good colleague phillpower2, has asked if I would take a look and see if I MAY be able to assist you.

It is, as he has said, really a matter of just another pair of eyes looking at it.

I have read the whole topic, every post and I do not think I have missed anything, but if I have please tell me, and I apologise beforehand

May I make the following points.

Please do not be offended by any of them, they are ONLY my observations.

1. I am really struggling to follow the logic of your opening post and these two disks.. I do appreciate that it is a laptop and you cannot on that model connect two disks inside the computer. I use the word disk, rather than drive, as a disk numbered 0 by Windows, may be lettered C and D or whatever, but disk management etc will refer to it as Disk 0 and then Disk 1 and so on.

What I am struggling with is why did you not simply connect the less reliable disk, externally by USB in an enclosure. I do not think a damaged connection in the laptop for the hard disk is the cause - but it must be a possibility.



2. The reason SFC would not originally work from the cmd prompt opened in the recovery environment, is that, THAT cmd prompt is a on a ramdrive lettered X, created in ram and therefore of course it cannot recognise a system file check cmd.. I THINK you established that, but please bear it in mind for a later step.

3. services.msc CANNOT open from the cmd prompt in the recovery environment.

4. I gain the impression and again if I am wrong I apologise that the Windows 7 DVD you have referred to is a COPY. I am NOT suggesting it is not a copy of a legal, licensed installation, but as my colleague has mentioned if you have Windows 7 Home Premium with SP1, then the DVD used for either the repair or the custom install if we get that far, must be the SAME DVD

5. There are, as I see it NOW, two ways to try and progress.

A. Is to run a chkdsk /r on the hard disk from the recovery cmd prompt.

PLEASE remember that the X is the ram drive, so it is no use running it from there.

From the X prompt change to C: prompt and then type

chkdsk /r

press enter

and it will tell you that the chkdsk cannot be run, as the drive is in use, that is because of course, you have just placed it in use with the cmd.

Follow the instructions to run it regardless.

Do the same on the drive lettered D:

Now, this is where it gets a little technical - the ram drive X, often changes the drive letters. So that what was lettered C on Disk0 for instance may be changed to another letter.

It does not really matter in your case, as you are going to run it on both.

YOU MAY CHECK what is on the C, when you have changed to that drive letter by typing

dir.

You may of course do the same with D

I said there were two ways to progress this, I think we will try that way first and see if we strike lucky.

ONE LAST point, if you do not mind.

WHILE I am providing another pair of eyes, please do ONLY as I ask, otherwise, it confuses ME as to are the results from what I have asked you to do, OR are they now from something you have decided to run.

Please ensure you watch the chkdsk results - ANY BAD SECTORS, or file errors that could not be repaired are a sure sign that this topic may NOT result in a satisfactory conclusion.



FINALLY here is the explanation of the ramdrive and the possible letter change.

http://www.bleepingc...command-prompt/

and the guide for what I have explained.

YOU need not bother with the bcdedit at this stage

Edited by Macboatmaster, 06 April 2013 - 08:06 AM.

[Macboatmaster]

My good colleague phillpower2, has asked if I would take a look and see if I MAY be able to assist you.

It is, as he has said, really a matter of just another pair of eyes looking at it.

I have read the whole topic, every post and I do not think I have missed anything, but if I have please tell me, and I apologise beforehand

May I make the following points.

Please do not be offended by any of them, they are ONLY my observations.

1. I am really struggling to follow the logic of your opening post and these two disks.. I do appreciate that it is a laptop and you cannot on that model connect two disks inside the computer. I use the word disk, rather than drive, as a disk numbered 0 by Windows, may be lettered C and D or whatever, but disk management etc will refer to it as Disk 0 and then Disk 1 and so on.

What I am struggling with is why did you not simply connect the less reliable disk, externally by USB in an enclosure. I do not think a damaged connection in the laptop for the hard disk is the cause - but it must be a possibility.



2. The reason SFC would not originally work from the cmd prompt opened in the recovery environment, is that, THAT cmd prompt is a on a ramdrive lettered X, created in ram and therefore of course it cannot recognise a system file check cmd.. I THINK you established that, but please bear it in mind for a later step.

3. services.msc CANNOT open from the cmd prompt in the recovery environment.

4. I gain the impression and again if I am wrong I apologise that the Windows 7 DVD you have referred to is a COPY. I am NOT suggesting it is not a copy of a legal, licensed installation, but as my colleague has mentioned if you have Windows 7 Home Premium with SP1, then the DVD used for either the repair or the custom install if we get that far, must be the SAME DVD

5. There are, as I see it NOW, two ways to try and progress.

A. Is to run a chkdsk /r on the hard disk from the recovery cmd prompt.

PLEASE remember that the X is the ram drive, so it is no use running it from there.

From the X prompt change to C: prompt and then type

chkdsk /r

press enter

and it will tell you that the chkdsk cannot be run, as the drive is in use, that is because of course, you have just placed it in use with the cmd.

Follow the instructions to run it regardless.

Do the same on the drive lettered D:

Now, this is where it gets a little technical - the ram drive X, often changes the drive letters. So that what was lettered C on Disk0 for instance may be changed to another letter.

It does not really matter in your case, as you are going to run it on both.

YOU MAY CHECK what is on the C, when you have changed to that drive letter by typing

dir.

You may of course do the same with D

I said there were two ways to progress this, I think we will try that way first and see if we strike lucky.

ONE LAST point, if you do not mind.

WHILE I am providing another pair of eyes, please do ONLY as I ask, otherwise, it confuses ME as to are the results from what I have asked you to do, OR are they now from something you have decided to run.

Please ensure you watch the chkdsk results - ANY BAD SECTORS, or file errors that could not be repaired are a sure sign that this topic may NOT result in a satisfactory conclusion.



FINALLY here is the explanation of the ramdrive and the possible letter change.

http://www.bleepingc...command-prompt/

and the guide for what I have explained.

YOU need not bother with the bcdedit at this stage

Edited by Macboatmaster, 06 April 2013 - 08:06 AM.

[phillpower2]

Thank you for coming in to assist Macboatmaster and promptly as is the norm

gmcube

You are in very capable hands with Malcolm and while he works with you I will only observe unless asked a question.

[iammykyl]

Nid wyf fi yma ond i gadw trefn

[gmcube]

You would at present appear to have a rather jumbled up configuration on your HDD and the data on it

I would like to have a second pair of eyes look at this so if you will, please provide the details of the installation disk that was used to install the OS and where the disk was obtained.

Its been long ago enough that I honestly can't remember clearly enough to give more info other than I downloaded and burned it. I think (key word) its the same disk I used to do a fresh install after the stock hard drive began showing signs of failing. My lap top did not include actual original disc so I had to resort to finding it elsewhere. It may not even be legit.

To make responding to this next one easier on me I'll be bolding my responses.

1. I am really struggling to follow the logic of your opening post and these two disks.. I do appreciate that it is a laptop and you cannot on that model connect two disks inside the computer. I use the word disk, rather than drive, as a disk numbered 0 by Windows, may be lettered C and D or whatever, but disk management etc will refer to it as Disk 0 and then Disk 1 and so on.


I'm not sure I understand the question. If your asking why I have a C and D disc, I think it had something to do with with the partitioning I did. When the drive was brand new and empty I felt like experimenting with dual booting to install ubuntu and windows 7. I wanted something of a sandbox to play in. Once I ran out of space, I moved the partition back down instead of deleting it outright fearing I'd would loose something important. The other disc could also be to set things up for a friend to use as their own computer. An idea that never panned out. Im probably not making any sense though. This would be so much easier if you were able to see what I see.


What I am struggling with is why did you not simply connect the less reliable disk, externally by USB in an enclosure. I do not think a damaged connection in the laptop for the hard disk is the cause - but it must be a possibility.

Well, I do not own an enclosure. I'm also not sure what purpose it would serve. I mean, I was able to back up the data already to a portable external drive. I was prepared for the stock drive to die on me (though it has yet to officially kick the bucket). I try not to rely on external ones too much.

2. The reason SFC would not originally work from the cmd prompt pened in the recovery environment, is that, THAT cmd prompt is a on a ramdrive lettered X, created in ram and therefore of course it cannot recognize a system file check cmd.. I THINK you established that, but please bear it in mind for a later step.

3. services.msc CANNOT open from the cmd prompt in the recovery environment.

4. I gain the impression and again if I am wrong I apologize that the Windows 7 DVD you have referred to is a COPY. I am NOT suggesting it is not a copy of a legal, licensed installation, but as my colleague has mentioned if you have Windows 7 Home Premium with SP1, then the DVD used for either the repair or the custom install if we get that far, must be the SAME DVD

5. There are, as I see it NOW, two ways to try and progress.

A. Is to run a chkdsk /r on the hard disk from the recovery cmd prompt.

PLEASE remember that the X is the ram drive, so it is no use running it from there.

From the X prompt [i]change to C[: prompt /i](What command does this?) and then type

chkdsk /r

press enter

and it will tell you that the chkdsk cannot be run, as the drive is in use, that is because of course, you have just placed it in use with the cmd.

Follow the instructions to run it regardless.

Do the same on the drive lettered D:

Now, this is where it gets a little technical - the ram drive X, often changes the drive letters. So that what was lettered C on Disk0 for instance may be changed to another letter.

It does not really matter in your case, as you are going to run it on both.
Wow, X is just trying to mess with me now isn't it? Thanks for clearing that up.

YOU MAY CHECK what is on the C, when you have changed to that drive letter by typing

dir.

You may of course do the same with D

I said there were two ways to progress this, I think we will try that way first and see if we strike lucky.

ONE LAST point, if you do not mind.

WHILE I am providing another pair of eyes, please do ONLY as I ask, otherwise, it confuses ME as to are the results from what I have asked you to do, OR are they now from something you have decided to run.

Sure thing.

Please ensure you watch the chkdsk results - ANY BAD SECTORS, or file errors that could not be repaired are a sure sign that this topic may NOT result in a satisfactory conclusion.



FINALLY here is the explanation of the ramdrive and the possible letter change.

http://www.bleepingc...command-prompt/

and the guide for what I have explained.

YOU need not bother with the bcdedit at this stage

I'll see if I can figure it out now and come back.

[Macboatmaster]

1. C & D are lettered partitions on the disk.

C is the 100MB system partition

D is the main partition with Windows installed, your programs etc.

X is the ram drive.

the other of course is the DVD drive.

2. I thought I had made it clear, I apologise if I had not. YOU SAID

I have this old hard drive that very unstable but will boot like 70 % of the time. I have a newer drive but I go back to the old one from time to time to grab a file or something. I did that yesterday but this time when I swapped my newer one back in, it no longer works

I took that to mean you had taken out the newer drive, inserted the older drive, grabbed something of it, so to speak and then when you put back the newer drive, it would NOT work.

The point I was making was, that it is NOT a very satisfactory way of doing things.

3. Is the Windows 7 DVD an original OR copy. Is it with SP1 or without. - cancel that question please see my post 37

4. You change to C: by typing C: at the X Prompt - it is on the link I sent

To change to that drive letter you can then type D:, or whatever other drive letter it shows, and press Enter on your keyboard.

Sending the link for you to read makes it so much easier for me than having to type out each and every instruction in full

Edited by Macboatmaster, 06 April 2013 - 04:35 PM.

[Macboatmaster]

I have posted separately so that you cannot miss it

IN VIEW of these comments, highlighted in red, and I admire the honesty of your admission

Its been long ago enough that I honestly can't remember clearly enough to give more info other than I downloaded and burned it. I think (key word) its the same disk I used to do a fresh install after the stock hard drive began showing signs of failing. My lap top did not include actual original disc so I had to resort to finding it elsewhere. It may not even be legit.

It is my opinion, that we cannot help you, other than to advise you to INSTALL a legitimate LICENSED version of 7, on the computer using the product key on the base of the laptop AND if that is NOT - Windows 7, then your choice is rather limited.

HERE is the download LINK to Windows 7 Home Premium 64 bit English.

http://msft-dnl.digi...3/X15-65733.iso

It is a legal download, but it is not a licence, that is granted by using the product key on the laptop. THAT product key must NOT be in use on any other computer.

The download is an ISO so you must make the DVD using ISO burning software.

PLEASE NOTE this is Home Premium 64 bit NOT Home Premium 64 bit SP1 - it makes a difference to if the product key will work. I think that laptop came with HOME PREMIUM 64 bit - without SP1

I have also referred the topic back to my good colleague phillpower2, to ensure he is acquainted with the prevailing situation.

Edited by Macboatmaster, 06 April 2013 - 04:05 PM.

[gmcube]

(currently typing from my phone, so I'll keep this brief)

I ran chkdsk on both C and D, I didn't see any bad sectors. This is what it gave me. At least a good portion of it.



I think you are correct, it was likely windows 7 home premium without sp1. I was merely reading off what I had running. I do think I remember having to do a service pack 1 update so that would make sense.

As for whether or not it's licensed, I do remember having to use the product key from a label on my laptop itself for what it's worth.
That URL looks familiar, it may have been exactly what I used.

If it is indeed licensed, can we continue?

Edited by gmcube, 06 April 2013 - 05:59 PM.

[Macboatmaster]

exit out of the cmd prompt

by typing exit.

Shut down.

Take out the DVD

reboot is anything different.

If not reboot again and this time key F8

on the options select Low Resolution Mode

anything different now.

[gmcube]

No, still the same.

[Macboatmaster]

I am in UK

signed off goodnight

Post again when I return

THANK YOU

[Macboatmaster]

1. Referring to my last on your post 30, on the screenshot, there is a Load Drivers - click

IT JUST MAYBE, although I doubt it, that it, from the sequence of events, that it MAYBE the graphics driver.

That is why we tried the Low Resolution Mode, which uses your driver but in VGA mode

However as Safe Mode, which uses the generic Windows graphics driver did not work either, that is why I have a doubt - this is the cause.

It will do no harm to have that driver, for the graphics - ready downloaded onto a flash pen, click the Load drivers and install.

2. The system reserved partition allocated letter C - depending on what changes have been made since Windows was installed contains the boot files for Windows 7 and that partition must be active for windows to boot. See my screenshot please



I cannot now remember if that point has been covered and I do not have the time to read all the topic again.



3.. That all said, I think it more likely, looking at the chkdsk results from the check on C drive, - that the cause lies elsewhere. The check found errors in the USN journal, this is a record of all changes made to all file systems, folders etc. on the disc and USN is the Update Sequence Number - applications, programs etc. consult the USN journal to establish any changes to their file systems.

I therefore believe that the cause is either registry problems, or something related to the boot configuration data. The latter can be relatively easily rebuilt - using the cmd prompt.

3. Returning to your expressed doubt about the disc used to install this Windows 7, although you now say you think it may have been from the link I provided, I have decided, after these suggestions, that it is best as I mentioned before for me to leave the topic, at least whilst staff members here, make a decision, as to IF Geeks to Go can properly proceed with attempts to repair THIS installation of 7.

Edited by Macboatmaster, 07 April 2013 - 07:44 AM.

[phillpower2]

Thank you for your continued assistance Macboatmaster

gmcube

As has been mentioned previously by colleague Macboatmaster where there is any doubt about the legitimacy of software we cannot offer any assistance, please refer to the GTG TOU (Terms of Use) that we must all abide by;

p.The posting of links or references to warez or any other type of illegal software is strictly forbidden. By doing so you risk having your user account terminated without warning. We will NOT help anyone we suspect of having obtained their software or services illegally.

As Macboatmaster also stated as long as you have a Windows 7 product key for the specific computer with the issue you can download a legitimate ISO to use, more at the attached link http://www.w7forums....ads-t12325.html

[Macboatmaster]

I agree - link to download my post 37

[gmcube]

So that's it? You guys are pulling the plug on this installation because I expressed a little bit of doubt? I would have taken the simplest route,seeking out warez is anything but. And often it gets accompanied by malware. I also did not fully understand whether or not using a copy I burned myself counted as a legit licensed installation so I said wasn't sure. The only reason I can think of to use a non licensed install is if I didn't know or realize I had the product key. But I do and I know I used it during the install. I don't disagree with the sites policies, I just think there's been a misunderstanding. If the problem is what Macboatmaster thinks it could be, we could be close a solution if I understand right.

But if this is it, I do at least have access to my data so if nothing else I'm grateful for that. If you guys are really done with helping me with this installation, I guess I'll move forward with a fresh install. I'll wait a bit for a final answer though, if either of you change your minds.