Windows 98 Boot Files

[Boyan Atanaschev]

Im dual booting Windows 10 (pre-Anniversary Update) and Fedora 24 on a Lenovo IdeaPad N580 (Intel Pentium B960 2.2GHz, 4GB RAM, UEFI with Secure Boot disabled). I originally had just Windows 10 and then installed Fedora 23 alongside it and everything worked fine - it worked as well when I upgraded to Fedora 24. A while back, I decided I wanted to try out Ubuntu, and installed it only overwriting the root, /boot and SWAP partitions and keeping my home partition. Windows 10 can still boot here. Then I decided I didn't like Ubuntu and reinstalled Fedora, with the 24 installer, trying to do exactly what I did with Ubuntu. The interface was a bit different, but I'm sure I did it correctly: after I did all the partition configuring, it gave me a popup saying "We will only touch these partitions," and the partitions it listed were root, /boot and SWAP. Nothing else.

As well, in the BIOS settings where Windows Boot Manager used to appear, it doesn't. It just has rEFInd and an entry with the model number of my hard drive - which I'm assuming just brings me to the GRUB menu. (I haven't actually tried bringing it to the top of the list and rebooting though - I'm a bit lazy :P)

UPDATE: Manoj identified the issue: by formatting the /boot partition I was getting rid of the Windows EFI files. So I need to reconstruct the files at /boot/efi/EFI/Microsoft.I think I've reconstructed the directory /boot/efi/EFI/Microsoft/Boot, but I need the other files in Microsoft.Could someone tell me what files I need there?

Now type list partition and make sure that there is a partition of type system (the efi partition). Select this partition by typing select partition # and assign a temporary drive letter to it, say G by typing assign letter=G.

If you hibernate windows (or purpose or because of power-saving), then use ubuntu to store files on the NTFS partition, and then boot up windows, Windows thinks the disk was corrupted while it was in hibernate and "fixes" anything different. After that loging back into ubuntu just confirms that the files have in-fact been deleted.

Also I have seen that windows 7 may do a chkdsk after it installs updates on shudown when you bring it back up windows does extra tasks related to installing updates, so be careful not to boot into ubuntu after shutting down from updates. -newbie-8/windows-chkdsk-deletes-files-written-by-ubuntu-on-an-ntfs-partition-913606/

Edit: I was looking through the widows site to try and find if they detailed the hibernate process, but this sounds interesting -us/library/dd143253(v=winembedded.5).aspx , It seems at best the write caching from the harddrive is being saved to memory, then being written after bringing the drive back up, this may mean that the files can't be recovered, because it's not "deleting" as in removing the first letter of the file so the system does not see it, but actually overwriting large areas of data that have been cached. Needs to be looked into more.

It happened to me as well. After reading a lot about this on internet I came to know that this happens when Windows is in Hibernate mode. There are already some related questions here on askubuntu and also on superuser.

The Boot.ini file is a text file that contains the boot options for computers with BIOS firmware running NT-based operating system prior to Windows Vista. It's located at the root of the system partition, typically c:\Boot.ini. The following sample shows the content of a typical Boot.ini file.

The [boot loader] section contains option settings that apply to all boot entries on the system. The options include timeout, the boot menu time-out value, and default, the location of the default operating system.

A boot entry is a set of options that defines a load configuration for an operating system or bootable program. The boot entry specifies an operating system or bootable program and the location of its files. It can also include parameters that configure the operating system or program.

The following sample shows the [operating systems] section of Boot.ini on a computer with two operating systems, Microsoft Windows XP and Microsoft Windows 2000. It has two boot entries, one for each operating system.

The location of the operating system. Boot.ini uses the Advanced RISC Computing (ARC) naming convention to display the path to the disk partition and directory where the operating system resides. For example:

A friendly name for the boot entry. The friendly name represents the boot entry in the boot menu. The friendly name is surrounded by quotation marks and represents the boot entry in the boot menu. For example:

Boot entry parameters, also known as boot parameters or load options enable, disable, and configure operating system features. Boot parameters resemble command-line parameters, each beginning with a forward slash (/), such as /debug. You can have zero or more boot parameters on each boot entry.

You can have multiple boot entries for the same operating system, each with a different set of boot parameters. Windows creates a standard boot entry when you install the operating system, and you can create additional customized entries for an operating system by editing Boot.ini.

If using Windows Explorer (or similar file management tools using shell32.dll APIs) to "see" hidden/system files, you won't, the Windows XP "factory" defaults are such that System files + folders are hidden so the user won't be able to alter/move/delete them "by accident". ;-(

1. Windows Explorer/My Computer interface -> Tools -> Folder Options -> View tab -> check the box "Hidden files and folders" -> uncheck the box "Hide protected operating system files (Recommended)" -> confirm said actions in all nag dialog boxes -> Apply/OK.

2. Another solution, without modifying any of those "factory" defaults... is to use good ol' File Manager 32-bit (see the FM guide for details), modded to work properly with all WinNTx OSes [free from MS].

To be able to achieve this, first you need to run FM -> click View from the File menu -> click "By File Type" -> check *all* boxes including the "Show Hidden/System files" box -> click OK or hit Enter.

In case the user decides to install the recovery console (the "Windows XP Recovery Console" boot menu option, which points to C:\CMDCONS\BOOTSECT.DAT), CMLDR is also copied to C:\ root (default), and C:\CMDCONS created.

in particular: The Windows Boot Manager entry (Identifier bootmgr) manages the Windows 10 boot process. The entry specifies a boot manager called bootmgfw.efi, typically located in the ESP partition at \efi\microsoft\boot\bootmgfw.efi, loads a UEFI-based Windows loader which is located at

@ @tabrez Yes, because that copies the files from C:\Windows\Boot, as MCEStaff mentioned, is a backup location of the boot files. I was able to get that command to run because I copied the files from one laptop to this one and then ran the command.

In looking at the BCD file, the bootmgr device location was listed as \Device\HarddiskVolume3. This should have been \DeviceHarddiskVolume1. There was no volume 3 anywhere on the disk. I am not sure if that was what caused the BSOD, but I just could not get the thing to boot.

I've quit Boot Camp and re-opened it. I've restarted my computer. I have no updates available. I've reinstalled Maverics and also downloaded Boot camp from a third party. Nothing seems to work. I have a MacBook Pro (Retina Late 2013) and have OSX 10.9 installed.

If anyone is still on this thread then I found that you can view how far it really is done by going to Applications>Utilities>Activity Monitor>Disk then find Boot Camp Assistant among the list and under bytes written tab compare that to the iso size and for example it is a 4GB iso and the bytes written are 3GB then it would be 75% done the part of coping the windows files to the usb. This as expected takes ages so just be patient

I've done this process twice and both times it took 2+ hours but finally completed. It looks like it is not moving, but files are still transferring. I would recommend plugging in the power cord and letting it finish overnight. BTW, having both Windows and OSX installed has made this my favorite computer ever!

I came back after an hour since I started boot camp and it had finished. Sorry to waste your time mende1. For anyone who needs help I'd give it a while because windows is a big OS. (ISO is around 4GB and uncompressed is around 20GB) Good luck to anyone who had this problem.

The Late 2013 MacBook Pro needs special Boot Camp drivers that can only be downloaded from Boot Camp Assistant, so remove the drivers you downloaded, close Boot Camp Assistant, open it again and start the download again. This process may take up to an hour, depending on your Internet connection.

Can someone help me my bootcamp assistant is stucked at 75%. I waited for hours still no progress, I also cancel the progress, restart my mac and reprocess the download and it is still stucking at 75% after waiting for several hours.

I am installing Leap onto my Dell Laptop on to a separate Hard Drive so that I can use either Windows or Leap without dual booting from one hard drive. I have downloaded and made a bootable USB Drive using Rufus. My issue is that my Dell XPS laptop uses UEFI Bios and does not allow me to select the USB Drive itself. Instead it is asking for a specific file from the USB Stick. Can somebody please let me know which file I need to select to be able to boot and install Leap from? If you need any more infomation or if i am missing something please let me know and I will try to fill in.

Regards

Charles

3a8082e126