No, its only in English. Sorry for that.Is it possible to change the language? like in Hiren's BootCD
Windows at least...?
No, its only in English. Sorry for that.Is it possible to change the language? like in Hiren's BootCD
Windows at least...?
Yeah, if you hit TAB while "Mini Windows 10" is highlighted, you have to change the word "boot" into "BOOT", and it should work. A small oversight on my part, and will be fixed in the April release since my upload speeds are abysmal.
I don't know if its fixable or not. I just thought I'd include the option to choose the partition and disk you want to boot from.it seems that booting on a USB for me will cause the hard drive to be remapped? booting from kon-boot will prevent me from booting back to my hard drive, and choosing the first option will instead opt to boot to the USB drive. again.
using the hard drive partition boot menu is rather annoying because if i choose the wrong one i have to shut down the PC and start all over again.
i am unaware if this occurs with any other programs or options, but it's something i thought i'd mention. how do you fix this?
Gave up trying to get Win10PESE_x64.iso to boot of a USB flash drive. Used Rufus 2.12 and NTFS to create a flash drive. Booted off flash drive and it throws an error about Not a valid Index and made references to Easeus. Checksums matched those on the Google Drive file.
CdUSB.Y or ISO NOT found !
Win10PESE can not mount and access files of your CD/DVD, USB, ISO on drive Y:
Possible Reason and Solutions :
1) You are not using .iso boot (You are using RealCD/DVD, BCD BOOTMGR, grub4dos BOOTMGR, etc.).
---> Check that the flag file CdUsb.Y is at the root of your media.
---> Your drive remained to the state "Not Ready" (More than 30 seconds) for a hardware reason.
---> Your drive is not recognised (driver missing or whatever, check if you can see your CD or Usb drive letter on explorer).
2) You are using .iso boot (grub4dos, isolinux, etc.) but you changed the build .iso name or path of your iso (ex: Win10PE_x86.iso, \Images\Win10PE_x64.ISO).
* If you use all from ram (all inside .wim) ignore this warning ;).
+ If you need files in your .iso to access, read following.
A) This feature requires imdisk, else will not work.
---> Be sure you have imdisk on your Win10PESE (Enable at Win10PESE\Tweaks).
B) Change your .iso name to the build .iso name (ex: Win10PE_x86.iso ) and put it to the correct path of your bootdrive.
---> Look for the default build configuration in the internal ini file (X:\Windows\System32\MountPEmedia.ini section IsoInfo/IsoName).
---> Rebuild by giving your personal Iso file name\Subfolder in the script Finals\Create ISO.
C) Use Win10PESE.ini to specify your personal .iso file name and location (solution for without rebuilding your project with your custom .isoname/subfolder settings).
2b) You are using .iso boot (grub4dos, isolinux, etc.) but .iso file to mount not accessible.
(= you can not see your Win10PESE iso file with explorer).
---> Driver missing -> add driver for your disk.
---> Some windows settings or software which disables mounting drives at boot -> disable such setting/software.
---------------------------------------------------------------------------------------------------------------
MountPEmedia.exe : Mount files of your CD/DVD, USB, ISO on drive Y:
Ini File (MountPEmedia.ini) :
[Settings]
ProjectName=Win10PESE
MountDrive=Y:
SearchFlagFile=Yes
FlagFileName=CdUSB.Y
SearchExternalIniFile=Yes
ExternalIniFileName=Win10PESE.ini
DesktopWarningLabel=Win10PESE Warning
[IsoInfo]
IsoName=Win10PESE_x64.ISO
Program Imdisk found in : X:\windows\system32
Gave up trying to get Win10PESE_x64.iso to boot of a USB flash drive. Used Rufus 2.12 and NTFS to create a flash drive. Booted off flash drive and it throws an error about Not a valid Index and made references to Easeus. Checksums matched those on the Google Drive file.
Wow, this looks really promissing !
Unfortunately I'm trying since 4 hours to put it on my 16 gb 3.0 usb drive with etcher(a linux rufus) on Antergos, but when trying to boot it I get a message saying that my drive is not bootable, I would like to put it on my stick throught yumi but I can't install it with arch :/ (I tried wine :x) and easy2boot is too difficult on linux :/
In Gparted it's really weird .. I've never seen a stick like that...
btw: I extracted the 6.7zip files with the command "$ cat /mnt/steam/aranger/medicat/medicat.16.10.stable.7z.00* > /mnt/steam/aranger/medicat/medicat.16.10.zip" And I did not found an updated md5sum of your files :/
Thanks ;3
Edit: With "multibootusb" I finally got to launch the iso, but when I enter in "medicat.stable" It jumps straight to lubuntu, BUT (:3) I can edit the argument to launch somehing else than [/.../ubuntu.bs], and I don't know what I can choose .. x'D
Edit: Ok I've found that I needed to edit the syslinux.cfg of multibootusb, and I've added 2 entries (see 2 last picture) but while testing with qemu I think it doesn't update. Should I email Multibootusb ?
If you run Medicat DVD on USB you can uninstall and install any programs you want. I had and always worked for me.Hey! Nice tool, I really like it. I was though wondering if Clonezilla Live could be an useful addition for the next medicat dvd? It would add a really useful (and open source) software for disk cloning and imaging!
Cheers!
Adding your own stuff to it is easy after you make the USB. Just copy and paste another menu entry (changing its label of course) and point it to your ISO. The ISO cannot have spaces in the name, and is case-sensitive.is there anyway maybe you could give a tutorial of adding os's to the boot selector? @Jayro i was thinking of adding kali linux to the list and a few other boot cd's