Will do..And also regarding security, make sure you have the latest BIOS installed, because it protects against CPU flaws, and generally more hardware stability and compatibility.
Will do..And also regarding security, make sure you have the latest BIOS installed, because it protects against CPU flaws, and generally more hardware stability and compatibility.
There's already there?hi
can I create MediCat with MiniWindows10?
Thanks..
Extract the boot.wim file out and save it to your desktop or whatever. Extract your Intel drivers to a folder. Use EasyDISM to mount the boot.wim file to a folder. Then use the drivers tab to add the Intel driver folder to the boot.wim. then you can put the boot.wim file back into the ISO (or back onto your USB stick) and it will boot up with the included I tell driver you installed. I use this exact process to install Wi-Fi and LAN drivers before release.Does anyone have a good guide to add drivers?
Tryied from W7 bit didn't work.
Wanting to add Intel HD3000 drivers or some kind of generic for 1366x786
Thanks you.
Redmi Note 7 Pro | Tapatalk
I believe I still have that version up on the pirate bay. But you'll have to find it yourself, I can't post Link's from that site in here. A quick search for "medicat" should find it.@Jayro
Hi,
Just seen 18.10 is not available.
It was the latest full edition:
* Live utilities
* Mini W10
* PortableApps
Right?
I keep it,
Would be useful to be also online?
I could upload it to Mega.
Redmi Note 7 Pro | Tapatalk
Extract the boot.wim file out and save it to your desktop or whatever. Extract your Intel drivers to a folder. Use EasyDISM to mount the boot.wim file to a folder. Then use the drivers tab to add the Intel driver folder to the boot.wim. then you can put the boot.wim file back into the ISO (or back onto your USB stick) and it will boot up with the included I tell driver you installed. I use this exact process to install Wi-Fi and LAN drivers before release.
I believe I still have that version up on the pirate bay. But you'll have to find it yourself, I can't post Link's from that site in here. A quick search for "medicat" should find it.
Many if the portable apps will still work on Windows 7, yes... But now that Windows 7 has been officially killed off by Microsoft, I will no longer be supporting it.Can we use this for windows 7?
Thanks!
--------------------- MERGED ---------------------------
Can we use medicat on windows 7?
Just copy and paste the menu entry inside main_menu.cfg from 18.10 into 19.10, extract your Mini Windows 10 ISO onto the root of the USB, and that should be all there is to it.Been using v18.10, love the integration with min win 10. How could I add min win10 to main USB image for v19.10?
Been using v18.10, love the integration with min win 10. How could I add min win10 to main USB image for v19.10?
MediCat USB
address of byte value downloaded from Google Drive value downloaded from Torrents
00000002EEEDEA91 64 E4
00000002EEEDEED1 88 08
MD5 checksum
emalware.c09 / Google Drive 32d37bc0f323f360c2ad85454c628eb4
emalware.c09 / Torrents b76f314f9d7a632ddc939c0bf56a4b9a
address of byte value downloaded from Google Drive value downloaded from Torrents
00022A91 64 E4
00022ED1 88 08
I was having issues uploading back then, and suggest that you trust the Torrent iso over the Google drive iso.Hello, this is my first post here and I would like to thank you for your work on this project.
I have some question about previous version of MediCat USB, 18.10.
medicat.v18.10.stable.iso file is still available to download from your Google Drive but it seems that file was originally uploaded with some errors. I tried to download it many times (at different days/nights, from different PCs and from different locations). Every time the MD5 checksum of downloaded file from Google Drive was the same: 098a29da811cfa0a40d1b64b3595bd70 but, to compare, MD5 checksum included in 18.10 hashes.txt file was 0d4daf7c31f80fe38a0cea5fdf8b8a0e and that's the MD5 checksum of medicat.v18.10.stable.iso file when it's downloaded from torrents.
I did file compare of these two iso files and here is the result, two bytes (in detail: two first bits of these two bytes) are different:
Code:address of byte value downloaded from Google Drive value downloaded from Torrents 00000002EEEDEA91 64 E4 00000002EEEDEED1 88 08
I do not know how important these two bytes are but their wrong values could lead to some errors when someone is using your project.
Could you please confirm / deny that this file on Google Drive was uploaded with errors? Or maybe it is some earlier version? If there were some errors during upload then maybe you should re-upload that file again, this time packed in 7z format to have this additional basic possibility to check the file after its download?
--------------------------------------------------
EDIT: I've just unpacked and compared all files inside both isos and I think I found the culprit of these differences:
\Programs\EmsisoftEmergencyKit\bin64\Signatures\BD\emalware.c09
Code:MD5 checksum emalware.c09 / Google Drive 32d37bc0f323f360c2ad85454c628eb4 emalware.c09 / Torrents b76f314f9d7a632ddc939c0bf56a4b9a
Code:address of byte value downloaded from Google Drive value downloaded from Torrents 00022A91 64 E4 00022ED1 88 08
Can you confirm this?
Now I presume that MediCat 18.10 on Google Drive can't be "some earlier version of this iso" and is damaged indeed.
I was having issues uploading back then, and suggest that you trust the Torrent iso over the Google drive iso.
Please can you add version changelog to the 1st post so we will know when there is an update without going through pages on this post? I know there is the text “edited...” down under that post but it’s almost not visible and it doesn’t necessarily mean the MediCat was updated.