Official MediCat USB - A Multiboot Linux USB for PC Repair

[Jayro]

Thank you Jairo for your answer.
And again I congratulate you for this whole project of yours is very good.

1) NTFS partition , DOES NOT START IN UEFI-GPT .

UEFI-GPT -- FAT 32 OR EX FAT.

Thank you, but I'm not sure how to help here. It sounds like UEFI makers need to support NTFS, and there's nothing I can do about that.

 

[Trigger911]

Man this tool is getting better and better and its easier to mod now thanks so much for making it so easy no more grub edits!

 

[Jayro]

Man this tool is getting better and better and its easier to mod now thanks so much for making it so easy no more grub edits!

That was definitely a huge goal, since I encourage everyone to customize MediCat to their needs. The easier, the better. Ventoy delivered.

 

[Trigger911]

That was definitely a huge goal, since I encourage everyone to customize MediCat to their needs. The easier, the better. Ventoy delivered.

oh yes is there anyway to extend the main partions to add more boot media? The last edition I used you had a OSimages I used for some other bootable media. I think with the efi last I cant resize.

 

[Jayro]

oh yes is there anyway to extend the main partions to add more boot media? The last edition I used you had a OSimages I used for some other bootable media. I think with the efi last I cant resize.

DiskGenius can resize the main partition, but Tony change the size of the 32MB EFI partition, just slide it to the right.

 

[neofita]

first of all thanks @Jayro for his invaluable work

DiskGenius can resize the main partition, but Tony change the size of the 32MB EFI partition, just slide it to the right.

I did so, but lost the ability to boot in BIOS-mode, which I need to install Windows on old systems. is there a way to fix it?

regards

 

[KaMyKaSii]

Thank you Jairo for your answer.
And again I congratulate you for this whole project of yours is very good.

1) NTFS partition , DOES NOT START IN UEFI-GPT .

UEFI-GPT -- FAT 32 OR EX FAT.

Don't use a bug in your hardware as a universal truth. UEFI can boot NTFS (if not, Windows would not boot????). And Ventoy (and therefore Medicat) uses the MBR partition table (instead of GPT) to maintain compatibility with Legacy BIOS. If you are really sure that your computer does not boot from NTFS while running in UEFI mode (what I doubt very much), then back up all data of the NTFS partition, format to FAT32 / ExFAT and restore the files

first of all thanks @Jayro for his invaluable work



I did so, but lost the ability to boot in BIOS-mode, which I need to install Windows on old systems. is there a way to fix it?

regards

Show the current partition layout of your USB stick

 

[neofita]

Show the current partition layout of your USB stick

Thank you for your answer
partition layout after sliding EFI to right end and resizing MEDICAT to max size

 

[neofita]

seems DiskGenius changed the MBR, I fixed it by restoring the correct one
now it boots in legacy mode, but Windows installer ISO doesn't work

 

[dekuleon]

Thanks so much for your tool @Jayro

 

[Jayro]

Thanks so much for your tool @Jayro

You're welcome.

 

[neofita]

updated Ventoy, all works fine now, thanks again @Jayro


regards

 

[evanultra01]

This error message popped up when i tried to extract the 7z inside the 001 file.
Can not open file
'C:\Users\Evrab\AppData\Local\Temp\7zOC86C1B40\Copy of
medicat.20.06.1.7z' as archive
I am probably doing something wrong.

 

[Jayro]

This error message popped up when i tried to extract the 7z inside the 001 file.
Can not open file
'C:\Users\Evrab\AppData\Local\Temp\7zOC86C1B40\Copy of
medicat.20.06.1.7z' as archive
I am probably doing something wrong.

Do the file hashes match? and are the other 7z files in the same directory with it?

 

[evanultra01]

There are no 7z files in the same directory/archive with it, and i'm not sure what file to compare the garbled 7z to.
EDIT: Currently checking hashes against the one on google drive.
EDIT 2: The 001 files are the same (of course.) Since the .7z inside the .001 cannot be extracted, i can't compare the img files.
EDIT 3: Figured it out, im a TOTAL bone-head

 

[user4]

A new version of Ventoy has been released: v1.0.14
https://www.ventoy.net/en/index.html

 

[evanultra01]

it now says:
|---------------------------------------------------|
| Couldn't mount file |
|---------------------------------------------------|
| |
| The disc image file is corrupted. |
| |
----------------------------------------------------
when trying to mount. (for testing to see if it worked)
Should i be scared?
Ill check the hashes for the image.
EDIT: Checked image and it was fine

 

[Ruxos]

it now says:
|---------------------------------------------------|
| Couldn't mount file |
|---------------------------------------------------|
| |
| The disc image file is corrupted. |
| |
----------------------------------------------------
when trying to mount. (for testing to see if it worked)
Should i be scared?
Ill check the hashes for the image.
EDIT: Checked image and it was fine

Don't try and mount the img file. That's the mistake I did too. The previous bin file was at least mountable but this new version can only be opened via 7zip (winrar doesn't work and I didn't try any other archiver. I saw that from the 7zip's menu that the only compatible mode that it opened was C#. I am guessing this has to do with the way the img was made using imgusb and any other software used.) Anyways, there's no other way that I found to open the img and the NTFS file inside, as stated on the main page under spoilers (it was for bin file, but the method still works)

The whole project thrives through ventoy. As much as the work is appreciated, the stubbornness and unwillingness to adapt is not. Not everyone has the need for 22gb worth of various amount of tools that they might not even come to use. It's also not versatile for people who only want to use one or two of the tools present. It would have been better if the images were distributed solely instead of the whole 22GB package. But someone doesn't has that in their mind to think on the advantages for it. Anyhows, I'll be working on a new project myself. If it comes to thrive and I feel that others might benefit from it and like it, I might post it around. Along with a tutorial on how to make ventoy compatible images (I think they already have one on their GitHub), if they are not already, on your own instead of relying onto others. That way anyone is free to choose whatever tools they want and to use and implement into the usb. I like this project. But I don't like to waste a huge amount of time bandwidth and various other resources for the sake of getting one distro out of this project anymore. It's absurd, redundant and just insane at this point.

 

[Jayro]

Don't try and mount the img file. That's the mistake I did too. The previous bin file was at least mountable but this new version can only be opened via 7zip (winrar doesn't work and I didn't try any other archiver. I saw that from the 7zip's menu that the only compatible mode that it opened was C#. I am guessing this has to do with the way the img was made using imgusb and any other software used.) Anyways, there's no other way that I found to open the img and the NTFS file inside, as stated on the main page under spoilers (it was for bin file, but the method still works)

The whole project thrives through ventoy. As much as the work is appreciated, the stubbornness and unwillingness to adapt is not. Not everyone has the need for 22gb worth of various amount of tools that they might not even come to use. It's also not versatile for people who only want to use one or two of the tools present. It would have been better if the images were distributed solely instead of the whole 22GB package. But someone doesn't has that in their mind to think on the advantages for it. Anyhows, I'll be working on a new project myself. If it comes to thrive and I feel that others might benefit from it and like it, I might post it around. Along with a tutorial on how to make ventoy compatible images (I think they already have one on their GitHub), if they are not already, on your own instead of relying onto others. That way anyone is free to choose whatever tools they want and to use and implement into the usb. I like this project. But I don't like to waste a huge amount of time bandwidth and various other resources for the sake of getting one distro out of this project anymore. It's absurd, redundant and just insane at this point.

By all means, make your own fork. I encourage derivative work!

 

[user4]

Info to user Ruxos:

IMG files are mountable with OSFMount.

A good alternative to 7-Zip is PeaZip. PeaZip is also a file archiver utility, comparable with and compatible to 7-Zip, but with more functions and it is more comfortable.

--------------------- MERGED ---------------------------

OSFMount: https://www.osforensics.com/tools/mount-disk-images.html
PeaZip: https://www.peazip.org/