Yesterday I created a new MediCat 18.04 USB drive using RUFUS. I'm still having the same problem with Spinrite, it stops at "FreeDOS".
Yesterday I created a new MediCat 18.04 USB drive using RUFUS. I'm still having the same problem with Spinrite, it stops at "FreeDOS".
Hi,
Sorry im new here. I can't install your program onto a usb stick using rufus it cuts out half way with this message in the log:
Unable to create file: [0x000000E1] Operation did not complete successfully because the file contains a virus or potentially unwanted software.
Created: F:\syslinux.cfg
My avast also picks up some viruses when I scan the image too.
I am unsure on how to proceed.
Thank you
Sorry im new here. I can't install your program onto a usb stick using rufus it cuts out half way with this message in the log:
Unable to create file: [0x000000E1] Operation did not complete successfully because the file contains a virus or potentially unwanted software.
Created: F:\syslinux.cfg
My avast also picks up some viruses when I scan the image too.
I am unsure on how to proceed.
Thank you
You might need to disable all of your anti-virus software first. It's usually called "real-time protection" or whatever.
Just discovered Medicat a few days ago and am thoroughly impressed. However the one thing keeping me from committing 100% to Medicat is the fact I just cannot get the included WinToHDD PortableApp working under MiniWindows10.
I brought the issue up at the Hasleo/EasyUEFI support forum (easyuefi(dot)com/forums/showthread.php?tid=466) but was informed by the dev that it's not guaranteed to work on any WinPE besides the custom WinPE created within WinToHDD itself (which must of course then be run from a normal copy of Windows, not PE, and which does not provide an option to output as a disk image but rather installs directly to a removable medium).
If this is a common issue, I think an adequate workaround would be to extract an ISO image of WinToHDD's self-authored PE to Medicat's ISO directory and add it to the menu in the same way as other WinPE-based images such as Active@ Bootdisk and the bootable MBAM (if there's a better way of doing this, I'm all ears).
If it works, it'd be a considerably more elegant solution than requiring users to edit Medicat's main_menu.cfg for each and every Windows installer they'd like to keep on the same disk as Medicat (or trying and failing to ensure YUMI or some other multiboot creator doesn't overwrite MiniWindows10 with a given Windows installer or vice versa, as has been my struggle) — and WinToHDD could still be included in the PortableApps suite as a full-featured copy of WinToHDD may still have its uses on PCs able to boot into normal Windows (i.e. the in-place "reinstall" feature, which is obviously absent from WinToHDD's self-authored PE, although I personally haven't been able to figure out how it's supposed to work anyway).
If free space on the medium containing Medicat is at a premium, this approach would retain WinToHDD's general advantage over certain multiboot solutions by allowing Windows ISOs to be sourced from media other than that containing the bootable installer itself (e.g. large external drives).
The inherent disadvantage in having to boot into WinToHDD's PE for it to work is that you must reboot to access all of Medicat's other utilities, and vice versa, but in some respects this is nothing new and is probably negligible — and while getting WinToHDD working within MiniWindows10 itself would be vastly preferable, that may simply be infeasible (as Hasleo/EasyUEFI leads me to believe).
I'll give extracting WinToHDD's PE and incorporating it into Medicat myself a go, but I've got no experience editing main_menu.cfg myself.
I brought the issue up at the Hasleo/EasyUEFI support forum (easyuefi(dot)com/forums/showthread.php?tid=466) but was informed by the dev that it's not guaranteed to work on any WinPE besides the custom WinPE created within WinToHDD itself (which must of course then be run from a normal copy of Windows, not PE, and which does not provide an option to output as a disk image but rather installs directly to a removable medium).
If this is a common issue, I think an adequate workaround would be to extract an ISO image of WinToHDD's self-authored PE to Medicat's ISO directory and add it to the menu in the same way as other WinPE-based images such as Active@ Bootdisk and the bootable MBAM (if there's a better way of doing this, I'm all ears).
If it works, it'd be a considerably more elegant solution than requiring users to edit Medicat's main_menu.cfg for each and every Windows installer they'd like to keep on the same disk as Medicat (or trying and failing to ensure YUMI or some other multiboot creator doesn't overwrite MiniWindows10 with a given Windows installer or vice versa, as has been my struggle) — and WinToHDD could still be included in the PortableApps suite as a full-featured copy of WinToHDD may still have its uses on PCs able to boot into normal Windows (i.e. the in-place "reinstall" feature, which is obviously absent from WinToHDD's self-authored PE, although I personally haven't been able to figure out how it's supposed to work anyway).
If free space on the medium containing Medicat is at a premium, this approach would retain WinToHDD's general advantage over certain multiboot solutions by allowing Windows ISOs to be sourced from media other than that containing the bootable installer itself (e.g. large external drives).
The inherent disadvantage in having to boot into WinToHDD's PE for it to work is that you must reboot to access all of Medicat's other utilities, and vice versa, but in some respects this is nothing new and is probably negligible — and while getting WinToHDD working within MiniWindows10 itself would be vastly preferable, that may simply be infeasible (as Hasleo/EasyUEFI leads me to believe).
I'll give extracting WinToHDD's PE and incorporating it into Medicat myself a go, but I've got no experience editing main_menu.cfg myself.
Last edited by saalkom,
I can look into getting a working solution going. Or see if I can learn from other multiboot utilities that include it, and see how it's done and what worked for them.
Too bad this doesn't boot from EFI and Legacy at the same time, would be perfect.
Either way I was just looking for this, I want to keep my pen drive around for any situation.
Either way I was just looking for this, I want to keep my pen drive around for any situation.
Yeah, I don't know how to setup efi booting. I don't understand how efi works, so my attempts at chainloading syslinux from efi boot always fails.
Last edited by Jayro,
Is the update .zip located somewhere weird? I can't seem to find it in either the Google Drive or Megaupload.
It goes like this.
To boot Windows 8/8.1/10 thro UEFI you need to have a signed .efi file. You can get those by getting an official .ISO from Microsoft (like Windows 10 Download Tool which is free and comes with those files already signed)
As far as Linux goes, you also need .efi files for those (signed or not it doesn't matter since you need to disable secure boot to boot it anyways), which need to go on its directory respectively.
Windows 8/8.1/10 - bootx64.efi and/or bootx86.efi (in case you wanna have both x86 and x64 versions of Windows)
Linux - grubx86.efi and/or grubx64 (again, respectively for x86 and/or x64 versions)
I can get you the files myself if you want, I'm also willing to test it on my machine.
Last edited by Yepi69,
If you can link me to the language packs I need to integrate, then I can try to integrate them on new releases going forward.@Jayro Can you please add some "keyboard layout" on the next release of Mini Windows 10? because at every new release we [europeans (Italian, German, Francais...)ecc...] have to use NLite to add our language keyboard layout and rebuild the iso
I'm a newbie (sort of
), but i managed to add Italian Keyboard Layout following this user (DPH) post on this thread (there's also a list of languages keyboard layout keys), but specially (step by step) this guide linked here:ht tps://ww w.tutos-inform atique.c om/windows-pe-clavier-aze rty/ (delete link spaces and use google translate)
Thank you for your work anyway!
Last edited by principealex1,
Thank you for this excellent toolkit.
I love it on Legacy boot, however, I now switched to using MS Surface Book 2 (a UEFI only device) and when I am booting it, it only loads Mini WIN10 with much less tools than the legacy version. I can't find tools such as ACRONIS TRUE IMAGE that I need etc. (I am booting through Easy2Boot)
Also, another major issue, there is a DPI problem and everything is so so tiny and barely readable (it's a UHD 15" screen). I tried to switch resolution via that icon near the clock at the bottom right of the status bar, but it doesn't switch and there is no place to change resolution and/or DPI.
I even tried to modify the registry, but that requires a reboot and the changes don't stick obviously.
Any way to fix these?
Thanks again
I love it on Legacy boot, however, I now switched to using MS Surface Book 2 (a UEFI only device) and when I am booting it, it only loads Mini WIN10 with much less tools than the legacy version. I can't find tools such as ACRONIS TRUE IMAGE that I need etc. (I am booting through Easy2Boot)
Also, another major issue, there is a DPI problem and everything is so so tiny and barely readable (it's a UHD 15" screen). I tried to switch resolution via that icon near the clock at the bottom right of the status bar, but it doesn't switch and there is no place to change resolution and/or DPI.
I even tried to modify the registry, but that requires a reboot and the changes don't stick obviously.
Any way to fix these?
Thanks again
Last edited by dr_lucas,
What native resolution is your Surface? And you probably just need the driver for it, which can be installed via Snappy Driver Installer in the PortableApps Menu. Alternatively, you could always inject the driver yourself into the boot.wim file, to get you the right resolution.
@Jayro
The Surface Book 2 - 15" screen comes with 3240 x 2160 resolution and by default, in regular windows it switches to the recommended 250% DPI, otherwise everything would look way too tiny.
I checked your build registry and it shows DesktopDPIOverride value as "-2", which explains why everything is so small.
As I wrote above, I tried to tinker with the registry but that requires a reboot and doesn't stick after a reboot.
I can try the driver installation suggestion, the laptop comes with 2 GPUs - Intel HD Graphics 620 integrated GPU & NVIDIA GeForce GTX 1060, so I will have to figure this out , but I am wondering if there is something you can do to improve this on the next Medicat release?
Also, is there anything that can be done to load the full Medicat USB build with all the goodies on UEFI?
Thanks again.
The Surface Book 2 - 15" screen comes with 3240 x 2160 resolution and by default, in regular windows it switches to the recommended 250% DPI, otherwise everything would look way too tiny.
I checked your build registry and it shows DesktopDPIOverride value as "-2", which explains why everything is so small.
As I wrote above, I tried to tinker with the registry but that requires a reboot and doesn't stick after a reboot.
I can try the driver installation suggestion, the laptop comes with 2 GPUs - Intel HD Graphics 620 integrated GPU & NVIDIA GeForce GTX 1060, so I will have to figure this out , but I am wondering if there is something you can do to improve this on the next Medicat release?
Also, is there anything that can be done to load the full Medicat USB build with all the goodies on UEFI?
Thanks again.
I have been trying to get UEFI booting, but I just don't understand it at all. I can't seem to get UEFI to chainloading into SYSLINUX no matter what I try. And I'm not opposed to help.
I wish there was something I could do to help, I am sure I know about SYSLINUX much less than you do. I guess the best place and people to check with are on syslinux.org
Since UEFI is here to stay and legacy is probably gonna be phased out in the near future, I sure hope you can find a solution.
Did I already say your Rescue disk is the best of the best? Keep up the great work!
Any comment/s on my GPU question would be appreciated.
cheers.
Since UEFI is here to stay and legacy is probably gonna be phased out in the near future, I sure hope you can find a solution.
Did I already say your Rescue disk is the best of the best?
Keep up the great work!Any comment/s on my GPU question would be appreciated.
cheers.
Last edited by dr_lucas,
Similar threads
-
- Portal
- No one is chatting at the moment.
-
@
Psionic Roshambo:
I wonder if I could recommend that to some emulation devs that perhaps the sound could use some smoothing out to simulate those old TVs -
@
Psionic Roshambo:
I think a few of the early systems could benefit from that, at least up to the 8 bit generation, by the 16 bit generation I think TVs had gotten a lot better in almost every way
-
-
-
-
-
-
-
-
-
-
@
Xdqwerty:
it says it only works for the original R4, R4i Gold (r4ids.cn), R4iDSN (r4idsn.com) and Acekard R.P.G. -
-
-
-
-
-
@
Psionic Roshambo:
Just give it a try, but honestly if you have a 3DS you can play DS games without a card just off the internal SD card
-
-
-
-
-
-
-
