Clicked on link via email notification and received black page/white letters that stated:
Did you really think I was gonna let you see what I have in here?
Love his sense of humor! Is this problem on my end?
"Missing Operating System"
#16
- Group: GeekU Senior
- Posts: 2,162
- Joined: 26-May 10
Posted 22 April 2012 - 12:04 PM
Clicked on link via email notification and received black page/white letters that stated:
Did you really think I was gonna let you see what I have in here?
Love his sense of humor! Is this problem on my end?
#17
- Group: Moderator
- Posts: 9,285
- Joined: 16-May 06
Posted 22 April 2012 - 12:18 PM
try this one...
noahdfear.net/downloads/bootable/NTBR_CD.exe
noahdfear.net/downloads/bootable/NTBR_CD.exe
#18
- Group: GeekU Senior
- Posts: 2,162
- Joined: 26-May 10
Posted 22 April 2012 - 12:51 PM
access is successful! Back with the results soon.
#19
- Group: GeekU Senior
- Posts: 2,162
- Joined: 26-May 10
Posted 22 April 2012 - 01:18 PM
Negative results. 
Rebooted to Gateway Splash screen then straight to Windows Error Recovery screen with Start Windows Normally as default choice. Clicked Start Windows Normally and the little download bar proceeded to take me to black screen with moveable cursor.
PS: I noticed that in the instructions above to create the disk you have to Browse to get the file to burn to disk. You'd be surprised to know that many may not know to do that. Thought I'd point that out for future reference.
Rebooted to Gateway Splash screen then straight to Windows Error Recovery screen with Start Windows Normally as default choice. Clicked Start Windows Normally and the little download bar proceeded to take me to black screen with moveable cursor.
PS: I noticed that in the instructions above to create the disk you have to Browse to get the file to burn to disk. You'd be surprised to know that many may not know to do that. Thought I'd point that out for future reference.
#20
- Group: GeekU Senior
- Posts: 2,162
- Joined: 26-May 10
Posted 22 April 2012 - 02:22 PM
Hi happyrock,
Any idea if the HD is bad at all? I do have a good friend who owns his own Computer repair shop and he told me yesterday he had a HD in stock if needed. I used Puppy Linux to retrieve all files not saved prior to this disaster and can drop the laptop off in the A.M. if you deem necessary. If you think the HD is good to go, I do have the factory recovery disks that Gateway sent me just after I purchased the laptop.
You make the call.
Donna
Any idea if the HD is bad at all? I do have a good friend who owns his own Computer repair shop and he told me yesterday he had a HD in stock if needed. I used Puppy Linux to retrieve all files not saved prior to this disaster and can drop the laptop off in the A.M. if you deem necessary. If you think the HD is good to go, I do have the factory recovery disks that Gateway sent me just after I purchased the laptop.
You make the call.
Donna
#21
- Group: Moderator
- Posts: 9,285
- Joined: 16-May 06
Posted 23 April 2012 - 09:00 AM
replace the drive then use the recovery disks would be my recommendation
#22
- Group: GeekU Senior
- Posts: 2,162
- Joined: 26-May 10
Posted 23 April 2012 - 06:28 PM
Then that is what I'll do.
I can't thank you enough for the time you offered to help me. Thank you so much!
Donna
I can't thank you enough for the time you offered to help me. Thank you so much!
Donna
#24
- Group: Member
- Posts: 7,232
- Joined: 13-March 10
Posted 26 April 2012 - 09:16 AM
DonnaB
I do not think chkdsk would have solved your problem.
However re your post 10
The command prompt accessed from the Vista DVD or on some occasions when pre-installed as on OEM systems from F8 Reapir Your Computer, is known as the command prompt at recovery environment.
It creates a ram drive lettered X
That is the reason your command
chkdsk /r
could not run
The report the drive could not be locked, is because that command was instructing chkdsk to run on the ramdrive.
This is the basic explananation
Also for your information, the recovery command prompt, sometimes changes the drive letters, not insofar as an actua change on the system is concerned bu simply at the prompt.
Therefore what was C may well now be D
So when running a command at the prompt it would be in this instance
chkdsk C: /r
Bearing in mind this, as mentioned above
It should be noted that when you boot into the Windows 7/Vista Recovery Environment the drive letter for your Windows installation may not be the same. For example, if your Windows installation is normally on the C: drive, it may be located at the D: drive. To determine what drive letter your Windows installation is located on, you can type this command press enter:
Personally I think it easier to simply go from X on the ramdrive to C:\ and explore C:
I do not know WHY, but the drive letter is NOT always changed.
I do not think chkdsk would have solved your problem.
However re your post 10
Quote
I boot to the Advanced Boot Options menu and choose Repair Your Computer feature, select a language, select a User name: and type password, select Command Prompt, I type chkdsk /r and the following is the results:
X:\windows\system32>chkdsk /r
The type of the file system is NTFS.
Cannot lock current drive.
Windows cannot run disk checking on this volume because it is write protected.
X:\windows\system32>chkdsk /r
The type of the file system is NTFS.
Cannot lock current drive.
Windows cannot run disk checking on this volume because it is write protected.
The command prompt accessed from the Vista DVD or on some occasions when pre-installed as on OEM systems from F8 Reapir Your Computer, is known as the command prompt at recovery environment.
It creates a ram drive lettered X
That is the reason your command
chkdsk /r
could not run
The report the drive could not be locked, is because that command was instructing chkdsk to run on the ramdrive.
This is the basic explananation
Quote
Working at the command prompt
To get to the command prompt, click Command Prompt on the System Recovery Options menu. You will land in the Sources subdirectory (folder) of a RAM disk identified by the drive letter X. From here, you have access to nearly 100 command-line tools, including disk-management utilities such as Chkdsk, Format, and DiskPart as well as file-management items such as Copy, Rename, and Delete.
The Windows Recovery Environment command prompt is a vastly more versatile replacement for the Recovery Console that was introduced in Windows XP. Unlike Recovery Console, which imposed stringent restrictions on your command-line activities, the Windows Recovery Environment command prompt permits you to do just about anything you need to do. Among other things, you can copy, delete, rename, move, and type document files; partition and format hard disks (using DiskPart); run diagnostic
To get to the command prompt, click Command Prompt on the System Recovery Options menu. You will land in the Sources subdirectory (folder) of a RAM disk identified by the drive letter X. From here, you have access to nearly 100 command-line tools, including disk-management utilities such as Chkdsk, Format, and DiskPart as well as file-management items such as Copy, Rename, and Delete.
The Windows Recovery Environment command prompt is a vastly more versatile replacement for the Recovery Console that was introduced in Windows XP. Unlike Recovery Console, which imposed stringent restrictions on your command-line activities, the Windows Recovery Environment command prompt permits you to do just about anything you need to do. Among other things, you can copy, delete, rename, move, and type document files; partition and format hard disks (using DiskPart); run diagnostic
Also for your information, the recovery command prompt, sometimes changes the drive letters, not insofar as an actua change on the system is concerned bu simply at the prompt.
Therefore what was C may well now be D
So when running a command at the prompt it would be in this instance
chkdsk C: /r
Bearing in mind this, as mentioned above
It should be noted that when you boot into the Windows 7/Vista Recovery Environment the drive letter for your Windows installation may not be the same. For example, if your Windows installation is normally on the C: drive, it may be located at the D: drive. To determine what drive letter your Windows installation is located on, you can type this command press enter:
bcdedit | find "osdevice"
This command will display output similar to : os device partition=D:. The drive letter after partition= is the drive that your Windows installation is located. To change to that drive letter you can then type D:, or whatever other drive letter it shows, and press Enter on your keyboardPersonally I think it easier to simply go from X on the ramdrive to C:\ and explore C:
I do not know WHY, but the drive letter is NOT always changed.
#25
- Group: GeekU Senior
- Posts: 2,162
- Joined: 26-May 10
Posted 01 May 2012 - 09:49 PM
Hi Macboatmaster,
Thank you for sharing the knowledge. I did have a new HD put in the laptop and picked it up just yesterday. The Tech Shop gave me the old HD to experiment with. When I get the time to focus I am definitely going to give it go to see if I can get it to boot into windows and see what happens.
Thank you for sharing the knowledge. I did have a new HD put in the laptop and picked it up just yesterday. The Tech Shop gave me the old HD to experiment with. When I get the time to focus I am definitely going to give it go to see if I can get it to boot into windows and see what happens.
