Winsetupfromusb-1-9 Windows 10
Maybell Hughs
my plan is to do a cleanses out all of my USB flash sticks and to emptied them by moving all file to a safe place and then to formatting all of them .and I almost thinking to make an multi-boot windows into one of USB drive but how to make a multi-boot windows into USB drive ? is there any free tool or utility for it ? and I would like to know exactly how many GB needed to makes one windows 7 -32-bit and one windows 7-64-bit and one windows xp-32-bit and one windows 10-64-bit ! and also I want to make a back-up for the system into a 4 GB flash drive which is for recovery if it needed !
seems useful tutorials to be read it . I have an question . can I use an old USB flash drive which is incompatibility with windows 10 ? (I find this information about this USB by google it) it still work on windows 10 but not sure if it will boot the ISO from it or or not
I would like to know exactly how many GB space needed to makes for one windows 7 -32-bit and one windows 7-64-bit and one windows xp-32-bit and one windows 10-64-bit into a single USB drive ?
You can easily find out around how large it will be by downloading the ISO's for each OS and checking their size on disk then adding your required 4GB of backup space to that and then an extra 1GB or so for a buffer for the boot files/menus etc. (though honestly the boot files are really small so they shouldn't take up anywhere near that much space; I just like to overestimate to be on the safe side because it's better to have extra space than not enough).
Yep, you can click 'Run anyway', that's just Windows Defender being cautious since it doesn't recognize the file. It isn't malicious, and if you want to be safe you can upload it to VirusTotal to have it scanned.
it turns out to me that because of corrupt download of WinSetupFromUSB-1-9 .exe and WinSetupFromUSB-1-9 (1).exe even though by using IE web-browser and FIREFOX and download being corrupt with both web-browsers "and I got download failed in FIREFOX" so by removing both from the download folder which have the issue resolved by download it a fresh using Microsoft Edge/internet explore .
It's been a long time since I've done this, but back when I built multi-boot tools I used a utility called UltraISO that allowed extracting and editing ISO files. It makes things such as adding drivers and additional tools to your boot image much easier. You just need something to make the multi-boot menu for when the boot disc starts up to allow you to select which OS to boot into, but finding one that works with older BIOS loading operating systems like XP as well as modern UEFI based operating systems like Windows 10 might be tough. That WinSetupFromUSB tool was supposed to be the solution, but if it isn't working I don't know what else to use as it's been so long since I did anything like this, and back when I did it, UEFI wasn't really a thing yet so I only had to deal with standard BIOS based bootable ISOs. You might also find this information useful. It documents compatibility and requirements and there are some good discussions about some of the issues people have run into.
As for your system recover disc, if you aren't able to find/create one using any built in utility from the manufacturer, you could use an imaging tool like Macrium Reflect Free. You'd just need to get the system/OS into a state where you'd be comfortable restoring/reimaging your system to (i.e. no unwanted junk, up to date drivers and patches etc.) then create the image, though such an image would take up a lot of space so you might want to store it on a separate drive such as an external hard drive or external SSD rather than a USB flash drive, though you could keep the Linux based Macrium recovery utility that handles loading the image and restoring it on the USB itself as an option. There's a list of tools in this topic under the Snapshot and Imaging Backup section.
I haven't experienced any blue screens with Macrium and Malwarebytes and I've used both on several occasions including one time just a couple of months ago to create a backup image of my system. Obviously that doesn't guarantee that it won't happen in your case but I guess there's no way to know for certain unless you try. If need be you can temporarily disable Malwarebytes while you create your backup. That won't hurt anything and should avoid any potential BSODs.
I will do this when I gets some new USB flash drives , Maybe tomorrow or so on and I want to ask if should I make the backup thing on a flash stick or on an external hard drive ? currently the largest USB in size I have is only 16 GB !
yes . I have a few of external hard drives already but I need to work to checking them and free up some space in order to have one of them to be emptied for the backup thing in case an external hard drive media is needed for a backed-up purpose
any recommendation for the flash drive size and external hard drive size before buying ? this will be good , and if so any , I need to have a good and fast USB drive product and external hard drive product because I want to changing from a good and old storage media to anew one ,fast and more spaces and etc , of course .
Macrium will tell you when you run it how much space is required to create a backup of your drive, but I would imagine it would definitely be larger than 16GB since it backs up the entire system drive, including Windows itself, all files on disk and all installed programs and data so I would definitely recommend using an external drive rather than a flash drive unless you get a much larger flash drive than 16GB.
As for the size of your drives, that again all depends on how much data you have. If you're looking for fast then I'd recommend going with USB 3.x drives for either flash drives or external drives assuming your PC has any USB 3.x ports and for your external drives I'd go with an external SSD as that will be much faster than an external HDD.
That's not good. The drive could be failing, but just to make sure I'd suggest temporarily disabling any disk intensive applications (assuming you know that the drive is clean/not infected with any malware) such as your AV etc. to see if that corrects the problem. If it doesn't then you might be out of luck, but you could try removing the drive then restarting your system and trying to plug the drive in again to see if Windows sees the files this time. If it still doesn't work then I'd suggest trying it on a different computer if you have one just to determine if it is really a problem with the drive itself or with something in your Windows 10 installation causing the problem.
You could try some kind of data recovery software but I don't know how effective it would be. If the problem is due to the drive failing then I'd be cautious about doing anything with it until you have your critical data backed up.
I have using the latest driver you given,
For installation i using a rescue OS (windows PE3.1). Actually only 64 bit version work because of usb driver issue.
Need 32bit driver to finish it.
finnaly i did it, using this driver with acpi files from ogs + mcs9990 usb 2.0 to pcie adapter with driver.
installation done on sata thank to the ahci driver on the first post.
to install it i used WinSetupFromUSB-1-9 with drivers ahci in .ima file for F6 menu.
after installation i just put acpi files in drivers folder.
CPU QQLS AND ASRock B365M Phantom Gaming 4. I want to build a 32MB BIOS so that any me can use it. I use Intel (R) Flash Image Tool. Version: 11.8.86.3877 the system starts, passes the cpu check and the ram hangs on the boot, it is generally possible to do this and how.
@jafidos
Welcome to the Win-RAID Forum!
Since your problem has much more to do with the topic of this already existing thread than with your specific mainboard, I have moved your request here.
It is not enough to integrate a certain Intel AHCI driver into the demanded XP Image, you have to integrate the support of your currently active specific on-board Intel AHCI Controller and nothing else.
This is what I recommend to do:
Hi Dieter (Fernando), I forgot to mention I have done that. It Is VEN_8086 & DEV_2826. This is the closest I have found in your driver. I did not go further to SUBSYS_089515D9 & REV_31. Is there anything else I could try. Just to mention, when I tried on Hyper-V to load this driver from floppy via F6, I got the same error almost immediately. I was thinking to make image from Hyper-V, and load it to SSD drive, but also with no luck.
64591212e2