The message 'bootmgr missing' may come from either syslinux, grub4dos or the actual 'normal' bootsector/PBR/VBR of the windows (actually it is more likely from the last). Basically it should mean (I am assuming BIOS or UEFI/CSM booting since you mentioned grub4dos) that the file 'bootmgr' is missing from the root of the stick, but it may depend on a number of variables. It is likely that what happened is the following (but no way to know without more details): 1) the USB had a MBR invoking directly another bootloader (such as grub4dos, often installed this way) 2) during the repair the MBR was replaced with the standard Windows one (that chainloads the PBR of the active parittion) 3) the previous bootloader did not chainload directly the BOOTMGR in the root of the stick but mounted an image (or however used a different path). OR: 1) the USB had a normal MBR (chainloading the PBR of the active partition) 2) the PBR invoked Syslinux (this is the normal way Syslinux is installed, more rare that grub4dos was chainloaded by it) 3) during the repair the PBR was replaced by the standard Windows PBR code (invoking BOOTMGR) What was the actual FIRST menu you had before? Was it a Syslinux one or a grub4dos one? Do you have a 'bootmgr' file in root of the stick? (my guess is no) If you have a 'grldr' file on the stick (in root or elsewhere) you can try making a copy of it and place the copy in root, renamed as 'bootmgr'.

Requirement To Get Free Internet There are some basic requirements to get free internet on your Android device. • Opera Mini Handler Apk file. • An Airtel Sim card with a 2G/3G/4G sim slot. • Primarily all you need is an Android phone. Opera mini handler 7 apk download full. However, Opera Mini browser is developed to use the internet at low data consumption whereas the handler is used to change the setting of the network to access the internet for free. If the setting gets matched with the network provider, then Opera Mini Handler will start to access free internet, and you can use free internet through the app quickly.

However, whenever I start it up from Syslinux (chain boot from Linux), it doesn't like it because it wants bootmgr (and all files it refers to) to be in the root folder of the USB (because Windows loves being the center of attention).

This may or may not give you access to grub4dos (depends on a number of factors). If it does then we will find out a way to repair the setup. If you have either a syslinux.cfg or a menu.lst (or both) post its (their) contents, maybe we can understand from them how your stick was setup.

Thank you for the reply, It is likely that what happened is the following (but no way to know without more details): What was the actual FIRST menu you had before? Was it a Syslinux one or a grub4dos one?

Hard drive comes with Win7 with BIOS, it is fixed now, it works (using it right now). USB has been formatted and installed with Yumi and first menu was syslinux, then grub4dos from a menu entry, leading to win iso. Looking at the usb stick after my mistake, I saw that the win7 dvd repair tool installed a boot folder on it (wasn't there before), and editing the file BCD within with easybcd shown me the classical 'start windows 7' menu entry that normally should have been written on the hard drive.

Do you have a 'bootmgr' file in root of the stick? I guess it is this BCD? (was in boot, like windows) If you have a 'grldr' file on the stick (in root or elsewhere) you can try making a copy of it and place the copy in root, renamed as 'bootmgr'. Deleted boot folder of the stick and done as you said (grldr is in HBCD): it worked! Well, at least it is bootable again. Kirgizcha tuulgan kungo kuttuktoolor. I have several menu entries, as you can see in the files below, but now there is no more 'theme' applied (splash image, text color.) but more importantly, it shows directly the menu of hiren's bcd, that is the first entry of the syslinux file, as if I had choosen it (pressing 1). And strangely, without 'pre-' loading hiren's bcd (the embedded progs like dos, memtest, parted magic, etc of the cd are working) EDIT: in fact this menu comes from the default isolinux.cfg and menu.lst in HBCD where I took grldr from, that's why!

But there is no other grldr. All yumi and syslinux files are in multiboot.(I saw a file named 'wimboot', tried to do the same, but no effect). And that's the only two root folders. If you have either a syslinux.cfg or a menu.lst (or both) post its (their) contents, maybe we can understand from them how your stick was setup. So, your primary bootloader was Syslinux, and what was overwritten was the PBR (or bootsector) of the active primary partition. Now it is a matter of replacing the current one (which is the default Windows 7 one) with the Syslinux one.