1. PC boot from host-store2. Transfer control from bootmgr (host-store) to 'grldr/grldr.mgr' and/or bootmgr (vhd-store) inside VHD
grldr windows 7 setup 41
diskpartcreate vdisk file=c:\windows7.vhd maximum=25600 type=fixedselect vdisk file=c:\windows7.vhdattach vdiskcreate partition primaryassign letter=vformat quick label=vhdexit
Actually Yesterday I had used 'WinNTSetup v.3.6.3' in order to create, 'C:\WIMBoot.vhdx' , attche it , Deploy 'install.wim' and create the BCD configuration to boot from the VHD and then copy 'grldr' and 'BOOT.INI' within 'WIMBOOT.vhd;. But there is no effect of adding 'grldr' and 'BOOT.INI' . It still always boot 'Win 8.1 U1' ?
After completing above steps Should I also add 'grldr' and 'BOOT.INI' within 'E2B.vhd' ?Can/Should I not use 'WinNTSetu v.3.6.3' for creating VHD, Deploying WIM and adding VHD entry to BCD ?Does 'WinNTSetup v.3.6.3' not do exactly the same thing what we do with the help of cmd commands ?I think GUI (WinNTSetu v.3.6.3) is more simple and better than manually method (cmd commands)? Is it not ?Regards........
Go to post #2: Test with the added grldr and BOOT.INI inside the .vhd.What happens?If "nothing different", try adding to the root of the "host" a copy of grldr and this BOOT.INI:
I had the same problem when I installed Ubuntu 10.4 LTS and windows xp crapped out. I put in the Xp cd, then ran recovery console, then executed fixboot fixmbr, I booted to windows, downloaded grub4dos, and bingo! now I can boot ubuntu from grub.
didn't you make a backup? never mind. boot from a live windows. run bootice software, choose your hdd, click process mbr. choose the last option - windows nt 6.0. click install-save.secondly delete grldr, grldr.mbr and menu.lst files.finally format the drive that you have created for remixos.
People weren't really doing that back then.People started installing from USB in windows 7 days.A good way to install XP(and here I don't mean by USB) is either from a CD,or by making a little partition on the HDD, puttin the setup files on there, and installing from there.
It may be possible to install WinXP from USB but i'm just saying you should know it's a ludicrously unusual non-standard thing2 do. One could boot off a boot disk then run the setup off the hard drive, or make the little partition bootable eg sys c: and boot off there.
The involvement of USB I'd suggest is you can make a Win9X USB boot disk (in the past people may have done that or used a floppy), and you could have the installation files copied on there, that's the i386 directory on any windows xp cd. Then copy it from the USB, to your hard drive. And run the WinXP setup off the hard drive.
There is a situation regarding XP and SATA, thanks to keltari for his comment and some pictures on this page for reminding me -explained/software/1420-installing-windows-xp-3rd-party-sataraid-driver/ , XP doesn't have SATA drivers and does prompts you to press F6 to install SCSI or RAID drivers. SATA is not SCSI and you may or may not want RAID or want to use RAID, but you push F6 there, to install your SATA driver.
Then you could use a usb floppy drive or you could just copy the files into the correct directory within i386, so that the setup finds them automatically. Some people here have mentioned "slipstreaming" and nlite.. IIRC slipstreaming is rebuilding an ISO, you don't need to as you have the i386 directory on (easily!) writable media, so you can manually add the driver file(s) just by copying them in.
Despite doing all the things before this post, after doing this by booting into 9.10 Ubuntu, i was able to mark as flagged, boot, then boot into the system disc Windows 7 DVD install Disc, Startup Repair (1st time allows it to detect the the boot flag and correct, it will restart one time, do this and boot from CD/DVD again) ...When in the setup , choose the Startup Repair, your installation should now be shown in the List, click next and do startup repair, and VOILA, restart number 2 and it's working.
I've tried all of these so called solutions and my Vista is still coming up with: Bootmgr is missing. I've been working on this off and on for a few weeks. My laptop had an internal recovery setup and I can't get to that any longer. I downloaded a backup Vista and it gets me to the recovery portion, but each time I go through the cmd prompts nothing ever changes.
This all started when one of my 3 hard drives melted (had old windows 7 install and documents on it.) oh sweet mary that sucks!!! I have lost a lost of info but I still was able to read the other 2 hard drives. So I started by turning my computer on with the main HD I had with windows 7 installed. It didnt boot. It just said - insert boot media or boot from proper media etc...
I was doing some diagnosis on someones computer, when i plugged their SATA drive onto my chain of SATAs. This was the boot drive from the other computer, and since windows wouldnt load properly i wanted to check if the disk was faulty. Either way, i plugged it in, and obviously some nasty things happend. It tried to boot from the other computers boot sector, and that completely f-ed up my original boot. I was just getting "insert proper boot media and restart" or something like that. I almost threw my computer out of the window trying to fix this, but after doing this i was finally getting the "bootmgr.exe is missing", and i knew i was saved, because ive run into that one a couple times before.
Than go to Start Up Repair. First time Windows may ask you to reboot your machine. Boot your computer on Windows Installation DVD again. SelectRepair than Start Up Repair. Now Windows RE should be list your windows operation system. Highlight it and clickNext.
- Inserted Windows 2008 R2 DVD.- Proceeded with an install on the new, 2nd, replaced hard drive as a NEW install next to the one on the 1st hard drive.- As soon as the first step was done (Copying System Files....) and it had moved on to "Extracting Windows Files....", I did a physical reset with the reset button.- When booting again, I noticed it would now say "BOOTREC not found, press CTRL ALT DEL".- Booted in Server 2008 R2 DVD again, this time chose "Repair".- It did not find the installed windows, but this time I was able to use the command prompt, and follow instructions re: DISKPART and BOOTREC mentioned above, and behold: Windows 2008 R2 booted in its wonderful self again. :)- Reformatted the 2nd hard drive to wipe it clean of any remnants of a failed windows install, and my system is back in business.
Oh yes, the partition was "1" , not 0, but I think that's been pointed out before. Also, I had to reboot a few times more, going through the wonderful recovery cd "experience", but after the next reboot, I had hope as at least the Windows RE system _saw_ the windows 7 installation....
I was trying to dual boot ubuntu 12.04 with win 7 and after ubuntu failed to setup the MBR I installed plop bootmanager and after a couple of bootings to ubuntu live and win 7 and .... win 7 boot stopped working. Plop uninstall wasn't accessible because win 7 boot manager didn't start at all. First I used a win 7 usb installation (I have a netbook with no optical drives) to repair the MBR. And then I did exactly what Aklem described. Now win 7 boots like new!
I got about 80% through this thread before I observed that the partition I was trying to fix lacked ANY boot files on the root, so after trying EVERYTHING in this thread EXCEPT the 'Bcdboot C:\windows' suggestion, as I apparently missed it when first mentioned way above, I did this (oh yeah, be sure to set operating system files and hidden files as visible):
1. Start up windows 7 cd and go to recovery mode, if your harddisk is not detected that means it is not active and therefore it won't boot, open a command prompt and use diskpart to make your partition active. after it is made active reboot your computer
What I ended up doing was the re-install of windows until it finished the copying files stage, and then I did the diskpart fix and the computer starting working. Can't believe I finally got it working.
I found C:\Boot directory and C:\bootmgr file compressed by windows (i don't know why, probably inherited from C:\ because i'm using compression for my SSD globally.) So i changed it back to normal using Hirens CD. You can use totalcmd. It can be launched from your system disk under recovery console.
I my case I had two disks in laptop (ASUS UX32V with M2 and SATA drive), first disk with system reserved 100MB boot partition and second with windows partition. Something went wrong with boot paritition and I wasn't able to even boot to boot manager ... I always gets "The file is possibly corrupt. The file header checksum does not match the computed checksum." when I try to boot and "Element not found" if I tried bootrec.
1) I copied 100MB bootmanager partition from another computer (or you can put new harddrive and install new windows - you don't need to install drivers etc., just win to first reset in installation steps) over the old boot paritition
As for G4D and geometry, booting NTLDR from the CF, which loads boot.ini and selecting G4D from there, which loads grldr (v0.4.4) and menu.lst from the HDD (as it can't see them on the CF), "geometry (hd0)" gives
I noticed the grldr on the CF was from 2011, so updated it to the latest April 2012 one I had on my USB and now when selecting G4D from the boot.ini menu (whether with the HDD connected or disconnected) I get the following error: 2ff7e9595c
Comments