1. Ruxos

    Ruxos Member
    Newcomer

    Joined:
    Jun 13, 2020
    Messages:
    19
    Country:
    Singapore
    I know you sure do, but no I'm not going to make a fork where I'll just be posting your image files separately, it's not even a fork at that point. Which shouldn't be hard for someone certain to do. I respect your work, but not the way of doing it.

    Tried and tested multiple times. Doesn't work. The previous bin file mounted correctly but this one doesn't. Only the efi partition mounts correctly not the actual medicate (NTFS) partition. I tried the torrent. I tried the Google drive.

    Tell me for a fact. What's more versatile for everyone (and I mean everyone), both intermediate to advanced users into all this shmitz. This whole distro is based and made through ventoy. The aio bootloader, giving the ability to boot multiple types of OSes and tools, as long as they are ventoy compatible. Once an OS or tool is compatible with ventoy users can just download that image file in the form of wim or iso download ventoy and make their own USB. If they want to add more to it, all they need to do is download more ventoy compatible distros or make them ventoy compatible themselves. And I know, some of the various tools in this release need to be made after installing some software or the other or you could download a bootable from some not-so-shady site. Regardless, all of that work only consumes time. It can all be done easily. Which is what Jayro has done, for herself first and foremost. Now once all of that has been done, she decided to distribute her entire usb turning it into an image. Which is all good and fine to an extent as an initial release.

    But it's goddamn freaking big still. Contains a lot of tools not your everyday Joe might be needing. Or would have heard of them or would ever use them. Yeah they can be useful, and are useful for a lot of people but not for everyone. So is it necessary for everyone to download this huge file considering all that? Let's say, I'm only interested in her work Medicat Winpe. If I am correct her initial work/project started as a continuation of Hiren or Gandalf's, and continue to distribute the winpe. We are all aware of the various tools there are, there isn't a need to redistribute them into a huge file when all you can do is just post the links to them to the original source, or if there was a need to make them compatible with ventoy, all that needed was to post those links separately (host those files individually) and not make a giant mess just because you find it catered to your needs and think that you need every tool at your disposal. Yes, you are a technician working for 16 years in some company and you might need all those tools. How hard can it be to simply host the individual files instead, like what you've done with Malwarebytes, Jayro?

    Let me just list some of the advantages to both you and everyone else.
    - No need to download a full 22 GB file. Which will save time and bandwidth for a lot of users who don't have the privilege of fast internet.
    - No need to be hosting a 22 GB file or host them in parts on torrent, because as per someone, they can get corrupted and whatnot. Hosting the individual image files will not get them corrupted hopefully, and even if they get one can easily remedy it with less upload bandwidth once again. (which should be a better option for the original uploader). You won't need to upload the 4gb split archive files and instead, the smaller image files can be easily uploaded. This would help to seed it back too, nobody has the storage to keep the 22gb file hosted. And then have another 22 GB to make their USB and all.
    - People using these images can easily customise their ventoy with what they need. For ex, someone is interested in WinPE and some other tool They don't need to download everything, extract from it and then create their own version. Easily saving a step or two in the process.
    - People also don't necessarily need a 22 GB usb either just to use her tools. The way I saw it, the NTFS partition can't be changed. It's either you extract what you need from it and then create your own (for people who don't have a 22gb usb) or use a 22+ gb usb to burn it first, then remove what you don't need or add more to it. Not to mention people who aren't all that knowledged will end up buying a new usb if they don't own a huge usb or just don't have it at that moment.
    - People don't also have to stick to ventoy. From what I saw that these images can be used easily with other tools and simply your own bootloader too. Giving people more freedom and options.

    In fact, the part about having a rescue disk is supposed to be portable and small. You're not selling a whole usb with your self created patented software like some multi millionaire company. It's all open source. So I don't understand, why or for what reason does this option seems that bad to you that it can't be done. I'm leaving this task to you because you're the original source of this distro, you can update the links faster than anyone else whenever it is updated. It would also help you in a lot of ways, you wouldn't need to create an entire image, split it up and then host it over the torrent. Taking the entire 22 GB of storage just for that. Updates would be easier too. In case half of the tools might not need any update and people won't need to download the whole 22GB file again.

    Anyways. This is just my opinion. If people don't see the point in it, then that's fine with me. Needless to say it just shows their narrow minded vision and thinking that everything can be solved with more resources/money if their suggestion is to adapt to having or buying a large storage USB. Let me just tell you that I own multiple usb but alas, I don't need a whole ass huge usb just to rescue my own system. A simple windows portable suffices me enough with a Linux distro to boot, so a 8gb or 16gb usb is good enough for me.
     
  2. TeBo

    TeBo Newbie
    Newcomer

    Joined:
    Jun 26, 2020
    Messages:
    1
    Country:
    United States
    As I understand it This tool is not intended to be a rescue disc it's intended to be a technicians toolkit, and imo it's pretty good for technicians.
     
    neofita and Jayro like this.
  3. Ruxos

    Ruxos Member
    Newcomer

    Joined:
    Jun 13, 2020
    Messages:
    19
    Country:
    Singapore
    So a continuation of Gandalf's/Hiren's work which was simply a rescue disk has evolved into a tool for technicians? Yet people seem to fail and understand why the heck it can't be both? All this supposed tool has is a compilation of others work coupled with 2 of her personal works. 2. In comparison to the numerous tens of tools that the image has. Technicians tool my ass when it can simply be anything and everything. Calling it a tool for technicians is by far the best joke I heard when it's nothing more than just a compilation of other open/closed source works. I can see where this conversation is going. I'm out. I admit my defeat, people here are hopelessly narrow minded. Well I shouldn't take everyone into account just because of one's comment, hopefully there are still some sane people left around here.

    ‍♂️
     
  4. Amantefurtivo

    Amantefurtivo Member
    Newcomer

    Joined:
    Feb 12, 2019
    Messages:
    17
    Country:
    Uruguay
    [QUOTE = "KaMyKaSii, post: 9106951, member: 529838"] No se puede usar un error en su hardware como una verdad universal. UEFI puede arrancar NTFS (si no, Windows no arrancaría ????). Y Ventoy (y, por lo tanto, Medicat) usa la tabla de partición MBR (en lugar de GPT) para mantener la compatibilidad con el BIOS heredado. Si está realmente seguro de que su computadora no arregla desde NTFS mientras se ejecuta en modo UEFI (lo que dudo mucho), haga una copia de seguridad de todos los datos de la partición NTFS, formatee en FAT32 / ExFAT y restaure los archivos

    First of all, thank you for trying to help.

    1) Please read carefully, I didn't mean UEFI, but UEFI-GPT.

    NOTE : There is no universal truth to what I wrote, this is in several serious internet forums, even at microsoft .

    And luckily for now I don't have any error in my hardware .

    2) Regarding Ventoy , from my point of view it's an excellent tool , but from what I understand it only accepts or recognizes .iso files , it doesn't recognize .img files .
    On the other hand, we have what Mr. Jairo already answered, it cannot transform .img to .iso .

    By default, Ventoy creates 2 partitions, one of which is generated in EX FAT. (Partition where the .iso files go) .

    I could format this partition in Ntfs (As I wrote, my system does not boot if the usb partition is formatted in Ntfs.
    And if I format it in fat 32 (I have the file size limitation, Max 4 gb) .

    NOTE: I would like to know how you incorporate medicat into Ventoy when it does not detect .img?

    My machine is a SONY VAIO ALL IN ONE , UEFI -GPT , where my bios is manufactured but you can change the option to start in LEGACY , or BIOS , DOES NOT START FROM THIS OPTION.

    The secure boot, already deactivated from the factory, I have no option in the bios to activate or deactivate it.


    If you are really sure that your computer doesn't boot from NTFS while running in UEFI mode (which I doubt very much), make a backup of all the data on the NTFS partition, format in FAT32 / ExFAT and restore the

    You can see that you didn't understand what I wrote, my computer starts up perfectly.

    What it doesn't start, are usb drives (formatted in ntfs ) and this, is because of the restrictions of the GPT.

    Greetings.
     
    Last edited by Amantefurtivo, Jun 26, 2020
  5. KaMyKaSii

    KaMyKaSii Member
    Newcomer

    Joined:
    Jun 6, 2020
    Messages:
    11
    Country:
    Brazil
    Please elaborate the difference between "UEFI" and "UEFI-GPT", I am curious
     
  6. Jayro

    OP Jayro MediCat USB and Mini Windows 10 Developer
    Developer

    Joined:
    Jul 23, 2012
    Messages:
    7,991
    Country:
    United States
    Does it mean booting from a GPT partition from UEFI? That's all I can think of. I still use MBR for most everything.
     
  7. user4

    user4 Member
    Newcomer

    Joined:
    May 3, 2020
    Messages:
    11
    Country:
    Austria
    To user Ruxos:

    Nobody is forced to use MediCat. There are several other bootable rescue/emergency systems, for example: All in One - System Rescue Toolkit (683 MB), Bob.Omb's Modified Win10PE (2.86 GB), DLC Boot (3.26 GB), FalconFour’s Ultimate Boot CD (697 MB), Gandalf’s Windows PE (3.91 GB), Hiren's BootCD WinPE10 Premium (1.51 GB), WinPE 10 Sergei Strelec (4.12 GB), ...

    MediCat is certainly the most comprehensive software collection. This has many advantages, but also a few disadvantages. I'm excited about MediCat and I thank Jayro for the excellent work on this project.
     
    Last edited by user4, Jun 30, 2020
    Jayro and neofita like this.
  8. Jayro

    OP Jayro MediCat USB and Mini Windows 10 Developer
    Developer

    Joined:
    Jul 23, 2012
    Messages:
    7,991
    Country:
    United States
    I would just like to point out that while Bob.omb makes a great disc, I do believe he's discontinued his work. I may be wrong, but I can't even find the Facebook page that I had bookmarked. And Gandalf locks all his distros behind a $20 donation paywall. So they're not really doing us any favors anymore.
     
    John69 and neofita like this.
  9. Spiren

    Spiren Member
    Newcomer

    Joined:
    May 30, 2020
    Messages:
    11
    Country:
    Netherlands
    I've tried to get the Mini Windows 10 to get past the rotating dots on my PC but so far no success.

    - UEFI and BIOS boot gives the same result also with MEMDISK
    - Enabling Fast Boot didn't do anything.
    - Removed all USB devices, no difference
    - Disabling all SATA ports. No difference
    - Disabling all NICs also has no difference
    - Removing one Memory stick of 16GB (so i run at 16GB of RAM instead of 32GB) also has no difference
    - Disabling IOMMU also does nothing to solve the issue
    - Any USB 3.0 / USB 2.0 port regardless of location gives me the same issue
    - Using an USB drive instead of my IODD hard drive also gives me the same issue
    - Removing all third party drivers using EasyDISM also gives no difference
    - Unplugging all my monitors except one also doesn't do a difference
    - Secure Boot is disabled as CSM boot is enabled
    - CSM boot and Secure Boot disabled also doesn't do anything different.
    - Using Rufus with UEFI GPT with either FAT32 or NTFS partitions to write the Windows 10 Mini Disc on an USB drive also doesn't give me a difference.

    It might be something NVMe / GPU / Motherboard driver related. I use a SX8200 Pro 1TB NVMe SSD, an MSI Radeon R9 390 GAMING as my GPU and the Gigabyte X570 Aorus Master as motherboard.
     
    Last edited by Spiren, Jun 29, 2020
  10. Amantefurtivo

    Amantefurtivo Member
    Newcomer

    Joined:
    Feb 12, 2019
    Messages:
    17
    Country:
    Uruguay
    UEFI- refers to the bios firmware, the startup mode of the machine.

    Gpt - refers to the disk style.



    You can find Mr. Gandalf's penultimate compilation of 7/6/2020.

    But I already tried to start it in Ventoy , it starts correctly on my UEFI -GPT machine.

    But when I run the programs, they don't open.


    Bob.omb works perfectly for me.

    At this moment I have tried more than 30 isos inside Ventoy, most of them successfully.

    Too bad MEDICAT, maybe in future updates from Mr. Jairo you can get a Uefi -Gpt compatible iso file.
    This Medicat is big, but a very complete disk.
    New congratulations to Mr. Jairo for his great effort and generosity in giving us his work for free.

    I hope that Mr. RUXOS can also give us his compilation.

    Thank you.

    — Posts automatically merged - Please don't double post! —

    UEFI -GPT machine.

    But when I run the programs, they don't open.


    Bob.omb works perfectly for me.

    At this moment I have tried more than 30 isos inside Ventoy, most of them successfully.

    Too bad MEDICAT, maybe in future updates from Mr. Jairo you can get a Uefi -Gpt compatible iso file.
    This Medicat is big, but a very complete disk.
    New congratulations to Mr. Jairo for his great effort and generosity in giving us his work for free.

    I hope that Mr. RUXOS can also give us his compilation.

    Thank you.
     
  11. user4

    user4 Member
    Newcomer

    Joined:
    May 3, 2020
    Messages:
    11
    Country:
    Austria
    To Jayro:
    From my list the only rescue/emergency system that is active is Sergei Strelec. All other systems mentioned appear to have been discontinued.
    Gandalf's homepage (http://windowsmatters.com/category/windows-pes/) hasn't been updated in seven months and I don't think people are willing to pay $20 for a WinPE.

    To Amantefurtivo:
    Please note: Jayro is a woman, not a man. And her name is Jayro, not Jairo.
    Where did you find the download of Gandalf from June 2020?
     
    Last edited by user4, Jun 30, 2020
  12. Ruxos

    Ruxos Member
    Newcomer

    Joined:
    Jun 13, 2020
    Messages:
    19
    Country:
    Singapore
    Their favors maybe lost now, but correct me if I am wrong about the part where Medicat was simply supposed to be a continuation of theirs or some other WinPE project. Scrolling through the torrent I realised that this wasn't the first attempt at such a large compilation (I can only assume from the size of the torrent file reported by the torrent). There were attempts utilising Yumi too.

    This "supposed technician" image is now made for "supposed technicians" as per one of the users here. I am guessing normal users can go to hell from now on. Again. This whole supposed image can be created via ventoy easily. All anyone would want to download was the wim/iso files (as long as someone distributed those images separately). From there on, whether some so called technician wants a technicians disk or whether a simple user simply want a Medicat Winpe etc etc, should be easily done than current process.

    Note: http://theoven.org/index.php?topic=3012.msg36207#msg36207 Gandalf might be a lost cause here, and Bob'omb's might have not been updated. Your work is all good and fine, but doesn't necessarily mean that you have to make it an utter waste of time and effort for some users just because of your tendency to neglect constructive feedback.

    And my god, @Spiren you're going through some dark times mate, eh? I would suggest you to ditch ventoy, give Rufus a try first. Extract Medicat Winpe iso and simply try to make a bootable usb via Rufus. See if that works or not. I saw ventoy is compatible with uefi but not on older systems, where the drivers responsible to detect uefi via NTFS is missing. The winpe works fine. I haven't tried the ventoy shmitz at all so far so can't say how well it works.
     
  13. didus69

    didus69 Newbie
    Newcomer

    Joined:
    Jun 28, 2020
    Messages:
    1
    Country:
    France
    Hello,
    thank you for your good and big work with medicat, you speek of Sardu but it is not realy free for UEFI or linux distrib, you can use ventoy for that job, easy to built, easy to use and free...
    best regards and sorry for my poor english
     
  14. Amantefurtivo

    Amantefurtivo Member
    Newcomer

    Joined:
    Feb 12, 2019
    Messages:
    17
    Country:
    Uruguay

    Thank you user 4 for letting me know that JAYRO is a woman, my apologies to Mrs. Jayro.


    2) I made a mistake with the dates on Gandalf , the last compilation is from November 2019 , and it is very difficult to get it online.

    The compilation that can be found is the one that dates from June 2019.

    I repeat the test 3 times in Ventoy , the compilation starts correctly , but when I want to run some program , it does not open , an error appears .

    Greetings.
     
  15. Spiren

    Spiren Member
    Newcomer

    Joined:
    May 30, 2020
    Messages:
    11
    Country:
    Netherlands
    I had this issue also on Medicat 19.12 with the separate Windows 10 mini disc. So i'm not sure it will fix it with Rufus. but i can try.

    On my old laptop it does boot fine tough.

    EDIT: I tested a Rufus-written Mini Windows 10 USB drive and it still doesn't past the rotating dots on my PC.
     
    Last edited by Spiren, Jun 28, 2020
  16. Ruxos

    Ruxos Member
    Newcomer

    Joined:
    Jun 13, 2020
    Messages:
    19
    Country:
    Singapore
    Can you show me what you select in Rufus? Because I tried with uefi gpt myself and it worked flawlessly. What windows version are you on currently and what's the architecture?

    Edit: By any chance is your secure boot enabled? If it is, disable it. On modern mobos the setting might be under advanced boot settings or something, which might be either set to CMS or UEFI. By default cms has secured boot disabled so just move on from that.
     
    Last edited by Ruxos, Jun 29, 2020
  17. Spiren

    Spiren Member
    Newcomer

    Joined:
    May 30, 2020
    Messages:
    11
    Country:
    Netherlands
    I also used GPT UEFI as seen here:
    [​IMG]
    I also tried NTFS GPT UEFI but that didn't worked either.

    My Windows 10 version is 2004 Education. The architecture is X64 (64-bit X86)

    Secure Boot is disabled since CSM support is turned on.
    Disabling CSM and Secure Boot also didn't work to get past the rotating dots.
     
    Last edited by Spiren, Jun 29, 2020
  18. Ruxos

    Ruxos Member
    Newcomer

    Joined:
    Jun 13, 2020
    Messages:
    19
    Country:
    Singapore
    At this point, I can only suggest you to try the iso in virtual box or VMware. Also, post your mobo. Try other WinPE such as bob'omb's or strelec. Or create your own WinPE (just basic build, nothing more) using either winpese or winpexpe. You can find both projects over at theoven.org

    Also, please specify the laptop manufacturer and model, if it's a desktop then specify the Mobo and ram. Does normal windows 10 usb boot successfully? Or try a windows-to-go edition (you can easily make one via Rufus and windows 10 iso)

    See if that boots or not. I can't say what's the issue at this point, I tried the winpe with 2 different usb on both my desktop and laptop, it worked fine.

    I can suggest you one other thing which you could try. Extract the wim file out and put it somewhere in C or D drive (or anywhere easily accessible)
    Use easybcd and create a boot menu as winpe using the wim file. Try that out first. I'd say try this one first before going to the other things I listed above.
     
    Last edited by Ruxos, Jun 29, 2020
  19. Spiren

    Spiren Member
    Newcomer

    Joined:
    May 30, 2020
    Messages:
    11
    Country:
    Netherlands
    I will try it in a VM. I can confirm that the Sergei Strelec WinPE works as i'm using that now for backupping my PC.

    My laptop is an ASUS N53SV-S1827V laptop with an Intel Core i7-2670QM (6M Cache, 2.20 GHz), 6GB DDR3, 750GB HDD, 15.6" 16:9 Full HD (1920x1080) LED Backlight, NVIDIA GeForce GT 540M 2GB DDR3, 802.11 b/g/n, Gigabit Ethernet. This machine works fine with the Windows 10 mini disc.

    My PC where the issue occurs has an Gigabyte X570 Aorus Master motherboard with 2 Crucical Ballistix LT Sport 16GB 3200mHz DDR4 RAM sticks. The CPU is an AMD Ryzen R7 3700X.


    Will try.

    Will try.
     
    Ruxos likes this.
  20. Spiren

    Spiren Member
    Newcomer

    Joined:
    May 30, 2020
    Messages:
    11
    Country:
    Netherlands
    UPDATE:
    Booting the Mini Windows 10 ISO works on a VMware Workstation virtual machine. It has 4 cores, 8GB of RAM and a 100GB Hard Drive allocated to it that's on my NVMe SSD (ADATA SX 8200PNP 1TB).

    Cant do it since this feature has been removed in Windows 10 version 2004. Source: https://docs.microsoft.com/en-us/windows/deployment/planning/windows-to-go-overview

    I've tried it and it still gets stuck at the rotating dots.
     
  21. Ruxos

    Ruxos Member
    Newcomer

    Joined:
    Jun 13, 2020
    Messages:
    19
    Country:
    Singapore
    I see. Hmm, I think there's some driver issue at work then. Did you try a different port? 2.0 one, preferably. Perhaps try to boot Medicat Winpe in legacy mode instead of uefi. Try the back ports maybe.

    From your PC specifications I wouldn't put it past it being not able to run it or taking too much time, considering the cpu mobo and ram are certainly high end. I can only think of some driver issue. Either the usb one or something else, something that's preventing it from booting.

    From the looks of it, it'll be super hard to find the conflicting driver it would have been helpful if it threw an error. Perhaps if Jayro took enough consideration into ridding the windows off unnecessary drivers and utilising a different method of injecting the drivers, but alas, she's too busy making gag compilations for "technicians" and "specialists".

    It would be hard to narrow down the issue, I can give you general tips to solve it, but it would take a lot of time and testing. It's a time of waste, considering that if she doesn't take these into account and don't remove them from her next build, you'll be stuck removing them again and again in case of updates. I'd rather suggest you to stick to strelec. I found it really good and used to use it too, I only chose Medicat due to it's likeness to bob'omb's WinPE. In fact, I'm thinking of using strelec as a model to compile my winpe too.

    Edit: I should say it before, the usb driver is merely a guess, since the wim file itself refuses to boot as per you. At best, I think it's either the cpu drivers or the hdd ones in your case. Could be done other driver too, but let's just say it's critical for the system and since it's malfunctioning, that's why you're having it in that state.
     
    Last edited by Ruxos, Jun 30, 2020
  22. Amantefurtivo

    Amantefurtivo Member
    Newcomer

    Joined:
    Feb 12, 2019
    Messages:
    17
    Country:
    Uruguay

    I hope it's okay.

    1) Check that your iso image is UEFI bootable.
    To do this, extract the iso into a folder and check for an EFI or UEFI folder.

    2) Check that the iso name does not contain spaces, and that it does not have a very long name either.
    You can use underscores to avoid leaving spaces in the name, or put everything together.

    3) Try different usb , 2.0 and 3.0 ports.
    I agree with Ruxos , it can be a driver issue .

    4) When it shows RUFUS , THE CLUSTERS ARE AT 8192 , I would try to put it at 4096.

    5) A very difficult UEFI-GPT calibration, I started it from a NTFS formatted USB drive.
    In 99 percent of the cases the motherboard of the machines
    do not present the controller for this.
    Perhaps if you use a boot loader or boot manager , you can do this.
    But not by a conventional method.

    WELCOME.
     
  23. Spiren

    Spiren Member
    Newcomer

    Joined:
    May 30, 2020
    Messages:
    11
    Country:
    Netherlands
    The folder exist and i had booted that ISO in UEFI from Medicat and from Rufus a couple of times and it never didn't let me boot in that mode.

    Since the ISO comes straight from medicat, there are no spaces or long names. The file name is: "[UEFI]_Mini_Windows_10.iso".

    Already done this and it didn't work. The back USB ports also don't let me pass through the rotating dots. Since the front and back USB port controllers are the same (AMD USB controller) and the Mini Windows 10 OS also didn't boot straight from it's WIM file from a SSD, i doubt it's an USB issue.

    Can try but i doubt it will work.

    Both NTFS and FAT32 made no difference. They boot but they don't get past the rotating dots. It doesn't matter it comes from Ventroy, the Windows bootloader or mounted as an disc from an IODD hard disk enclosure, it doesn't let me past the rotating dots.

    I haven' tried the back USB 2.0 ports but i do had tested it on the front ones. The USB controller is the same so i don't think it will make a difference. I did try the back USB 3.0 ports and these didn't made a difference. I also booted in both UEFI as legacy and it didn't made a difference.

    I also think this is the case. I think it's either motherboard or SSD related.

    I also don't think it will be worth it to spend much time as i have Strelec anyway. I can mount both technical tools thanks to the IODD enclosure i got so it's not a big deal for me. But in the past i relected to send a bug reports to get stuff fixed and instead switch to something else. There's not a lot of WinPE's that are getting updated at the moment so i would like to have alternatives if Strelec quits updating the english version again.

    I also tested the Windows to Go function thanks to the older version of Windows 10 on my laptop. This worked and i can work with the portable Windows on my PC.
     
    Last edited by Spiren, Jun 30, 2020
    Ruxos likes this.
Draft saved Draft deleted
Loading...

Hide similar threads Similar threads with keywords - Multiboot, MediCat, Repair