Do the instructions on the very first post on page 1 not work on a 32GB? I too did mine on a 64GB i had laying around but the bin is under 32GB so I assume it should fit on most 32GB flash drives.
MediCat is not meant to be added to a multiboot drive, since it's already a multiboot drive. It needs it's own USB stick, and they're cheap... 64GB is less than $20 USD.
--------------------- MERGED ---------------------------
-Install Ventoy to the drive.
-Open Medicat's .bin file with 7-zip.
-Extract the ISOs you want.
-Extract all of the EFI files from the EFI partition.
-Put the ISO files you chose onto the FAT partition of your stick.
-Open MiniTool Partition Wizard (or Windows Disk Manager) and give the EFI partition of your stick a drive letter.
-Then overwrite all the stick's EFI files with the MediCat ones.
-Removing the drive letter of the EFI partition afterwards is completely optional, and doesn't affect the functionality of the drive in any way.
And thank you for your seeding!
Last edited by Jayro,
forgot to tell y'all, but the changelog is now live in the download folders.
--------------------- MERGED ---------------------------
--------------------- MERGED ---------------------------
The greatest thing about MediCat is customizability. I want everyone to be able to make their own personalized toolkit for themselves, as I have done for myself since 2014. Your needs differ from mine, and I fully encourage everyone to make this toolkit work for YOU!
Hello,
How to convert bin file to iso because I can no longer use medicat on my Vms only iso can be mounted on kvm or Esxi ?
Thank you
How to convert bin file to iso because I can no longer use medicat on my Vms only iso can be mounted on kvm or Esxi ?
Thank you
My thoughts on how to improve the Medicat installation method:
1. Create the primary partition's filesystem, in the case ExFAT, as small as possible, just enough to hold all Medicat files, thus making Medicat fit in the smallest USB stick possible (currently 32GB).
2. Get rid of this strange bin data format and make the Medicat image available on the already known dd backup format (raw disk copy), you can recommend the users to install it on the USB stick using balenaEtcher avaliable for Windows and Linux.
3. Teach users how to use GPARTED (also avaliable for Windows and Linux) to move the EFI partition to the end of the disk and then extend the size of the ExFAT primary partition, allowing them to use all available space on their USB stick
Now a request for users like me who already have Ventoy vanilla installed:
When extracting all files from the ExFAT partition of the bin file to the root of my primary partition (using OSFMount, 7zip reports an error at the end of the file data so neither I tried) I was able to use Ventoy to boot the Mini Windows 10 iso and the portable programs are loaded correctly, but I don't like to fill the root of my external HD with several random files, since I also use it to load personal files. Could you make the Mini Windows 10 look at the root of all available partitions for a medicat.cfg file that tells it where the root of the extracted medicat is? For example "medicat_path=ISOs/medicat".
Thank you for this excellent project!
1. Create the primary partition's filesystem, in the case ExFAT, as small as possible, just enough to hold all Medicat files, thus making Medicat fit in the smallest USB stick possible (currently 32GB).
2. Get rid of this strange bin data format and make the Medicat image available on the already known dd backup format (raw disk copy), you can recommend the users to install it on the USB stick using balenaEtcher avaliable for Windows and Linux.
3. Teach users how to use GPARTED (also avaliable for Windows and Linux) to move the EFI partition to the end of the disk and then extend the size of the ExFAT primary partition, allowing them to use all available space on their USB stick
Now a request for users like me who already have Ventoy vanilla installed:
When extracting all files from the ExFAT partition of the bin file to the root of my primary partition (using OSFMount, 7zip reports an error at the end of the file data so neither I tried) I was able to use Ventoy to boot the Mini Windows 10 iso and the portable programs are loaded correctly, but I don't like to fill the root of my external HD with several random files, since I also use it to load personal files. Could you make the Mini Windows 10 look at the root of all available partitions for a medicat.cfg file that tells it where the root of the extracted medicat is? For example "medicat_path=ISOs/medicat".
Thank you for this excellent project!
Last edited by KaMyKaSii,
I don't need the 30 GB free extra storage space on MediCat v20.05.1. Please tell me how to delete this unused space so that the content fits on a 32 GB USB stick. Just like it was on MediCat v20.05.
-Install Ventoy to the drive.
-Open Medicat's .bin file with 7-zip.
-Extract the ISOs you want.
-Extract all of the EFI files from the EFI partition.
-Put the ISO files you chose onto the FAT partition of your stick.
-Open MiniTool Partition Wizard (or Windows Disk Manager) and give the EFI partition of your stick a drive letter.
-Then overwrite all the stick's EFI files with the MediCat ones.
-Removing the drive letter of the EFI partition afterwards is completely optional, and doesn't affect the functionality of the drive in any way.
i'd add this to the faq and install instruction file
ps you can also mount the bin with OSFmount
Last edited by madbomb122,
[
You need to boot your PC in legacy BIOS mode for some ISOs to boot. The lower left corner of the menu will tell you which mode you're booted into, BIOS or UEFI. You'll need to pay attention to what the ISO needs. I've named them accordingly.
Good Day All. I am a huge fan of MediaCat for several years now.
I wanted to ask of the best way for upgrading Ventoy since the latest edition supports booting from WIM files.
Should I upgrade directly from the Ventoy application or is there a better method.
Thanks a lot and stay frosty.
I wanted to ask of the best way for upgrading Ventoy since the latest edition supports booting from WIM files.
Should I upgrade directly from the Ventoy application or is there a better method.
Thanks a lot and stay frosty.
@Jayro
First of all great job on MediCat toolkit.
I used a new 64GB Sandisk Ultra Flair USB 3.0 drive to make it, like the one you used and gives me always the following error:
15:32:18 - Program: imageUSB v1.5 Build 1001
15:32:18 - Date & Time: 06/08/20 15:32:18
15:32:18 - Application Path: "C:\Users\Administrator\Desktop\New folder\imageusb\imageUSB.exe"
15:32:18 - Getting list of eligible removable USB drives...
15:32:18 - Adding eligible USB Drive [SanDisk Ultra USB 3.0] to list.
15:32:18 - Ready...
15:32:42 - File C:\Users\Administrator\Desktop\New folder\medicat.20.05.01.bin selected.
15:33:31 - Selected - Disk SanDisk Ultra USB 3.0 (Serial: 05018ad53b92bdc82fd5 Disk: 2, Part. Type: MBR, Size: 57.31 GB, Volumes: F)
15:33:35 - Created 1 Write Threads. Imaging Starting Soon...
15:33:35 - Write Image Thread started on [SanDisk Ultra USB 3.0] (Disk 2)
15:33:39 - Writing image C:\Users\Administrator\Desktop\New folder\medicat.20.05.01.bin to SanDisk Ultra USB 3.0 (Disk 2)
17:29:50 - Error: Failed to write to \\.\PhysicalDrive2 at offset 61505273856 (0x52000000).
and doesn't finish the process.
The Medicat bin is good, the hash are correct and i have try it on a borrow usb 128gb and all went good.
Can you help, please!
Thanks in advance.
First of all great job on MediCat toolkit.
I used a new 64GB Sandisk Ultra Flair USB 3.0 drive to make it, like the one you used and gives me always the following error:
15:32:18 - Program: imageUSB v1.5 Build 1001
15:32:18 - Date & Time: 06/08/20 15:32:18
15:32:18 - Application Path: "C:\Users\Administrator\Desktop\New folder\imageusb\imageUSB.exe"
15:32:18 - Getting list of eligible removable USB drives...
15:32:18 - Adding eligible USB Drive [SanDisk Ultra USB 3.0] to list.
15:32:18 - Ready...
15:32:42 - File C:\Users\Administrator\Desktop\New folder\medicat.20.05.01.bin selected.
15:33:31 - Selected - Disk SanDisk Ultra USB 3.0 (Serial: 05018ad53b92bdc82fd5 Disk: 2, Part. Type: MBR, Size: 57.31 GB, Volumes: F)
15:33:35 - Created 1 Write Threads. Imaging Starting Soon...
15:33:35 - Write Image Thread started on [SanDisk Ultra USB 3.0] (Disk 2)
15:33:39 - Writing image C:\Users\Administrator\Desktop\New folder\medicat.20.05.01.bin to SanDisk Ultra USB 3.0 (Disk 2)
17:29:50 - Error: Failed to write to \\.\PhysicalDrive2 at offset 61505273856 (0x52000000).
and doesn't finish the process.
The Medicat bin is good, the hash are correct and i have try it on a borrow usb 128gb and all went good.
Can you help, please!
Thanks in advance.
I noticed that. This is an EFI prefixed ISO while I boot into UEFI mode as it stated as well in the down-left corner.
Sadly, not all flash drives are created equal. It's really a lottery. My .bin image is 57.3GB in raw size.
Do you know which ISO it was? I can try and help you from there.
I just uploaded the latest version, 1.0.0.12 with WIM support. But yeah, you can just upgrade using ventoy. Just make sure the EFI partition does NOT have a drive letter, or you could bork bork partitions. (I had it happen to me)
You don't happen watch King Frostmare on YouTube by chance?Thanks a lot and stay frosty.
Sorry no I do not I just loved the word long time ago.You don't happen watch King Frostmare on YouTube by chance?
I flashed the latest image on my 128 GBs Flash Disk and was unable to resize the main partition since the EFI partition is directly after and can't be moved. Do you know of a specific method of doing so or should I just create another partition after the EFI one. Thanks and again Stay Forsty.
DiskGenius is the only one that will allow me to move the partitions around. Slide the EFI partition to the right, and then resize the exFAT one. You CAN use NTFS if you prefer, or even Linux formats like EXT2/3/4.Sorry no I do not I just loved the word long time ago.
I flashed the latest image on my 128 GBs Flash Disk and was unable to resize the main partition since the EFI partition is directly after and can't be moved. Do you know of a specific method of doing so or should I just create another partition after the EFI one. Thanks and again Stay Forsty.
Similar threads
-
- Portal
- No one is chatting at the moment.
