Open PaulNevada opened 2 years ago
steve6375
commented
2 years ago Do you mean if you legacy boot the same ventoy usb drive on the same target system from the same usb port, from a power switch-on, sometimes setup sees the usb drive and on some boots it does not?
PaulNevada
commented
2 years ago The setup sees the drive always, but it starts to loose it when I proceed from the Step1, so to speak, and move to the next screens. Then I receive "The driver is missing...", but, again in some weird 50/50 cases...
steve6375
commented
2 years ago Well windows 7 is old. It does not contain usb drivers for modern systems and usb 3 had not even been invented! What do you mean by 50/50 cases? What cases do you mean? What is case A and what is case B?
PaulNevada
commented
2 years ago The same environment in everything - as you listed above. I use the Windows 7 iso that does include all the needed usb3.x drivers (modifies one). I see it as 50/50 in the behavior - random cases...
steve6375
commented
2 years ago So your answer to my original question is YES? Cold power on each time, same usb port, same system, same usb drive?
PaulNevada
commented
2 years ago "Cold power" needs to be checked. Maybe, it is the wanted resetter for these 50/50...
steve6375
commented
2 years ago If you are using a usb 3 drive in a usb 3 port then the added win7 usb drivers will be used to access the iso file on the usb 3 drive. Maybe the driver does not detect the drive quick enough? Ventoy injects code which finds the usb drive and then loads the iso as a virtual dvd drive when winpe is loaded. So there could be a timing problem?
PaulNevada
commented
2 years ago Wait, I said 50/50 because I'm pretty stuck with that. If I reboot the pc it works (all the?) time. If I cold start - dunno - will check it again. I thought it's kinda randomized here...
PaulNevada
commented
2 years ago I am pretty sure - yes, it is - this is a timing thing! Is there a way to extend this parameter for me and without the compiling the code?
steve6375
commented
2 years ago I don't think so. Not sure if the code has a retry algorithm or any built in delay. The developer will have to respond.
steve6375
commented
2 years ago Maybe using a usb 2 port or usb 2 extension cable will solve the issue?
PaulNevada
commented
2 years ago I do want to be fixed. Even by myself. I have some little programming knowledges...
PaulNevada
commented
2 years ago The comments form the developer would be very helpful - for sure. Thanks for the help!
PaulNevada
commented
2 years ago Tried rufus several times with the current environment - the same strange behavior...
steve6375
commented
2 years ago With Rufus, you may be able to remove the USB drive and re-insert it once running Setup. It may then re-detect the USB drive. With both Ventoy and Rufus you can press SHIFT+F10 once Setup is running to get a command console - then type NOTEPAD and use the File - Open dialogue to see if you can 'see' the USB drive - if not then the USB driver in the particular ISO that you are using is not working properly. This issue is not a problem with Rufus or Ventoy - it is a problem with the added USB drivers inside the ISO.
NewbieXvwu
commented
2 years ago You should install a USB 3.0 driver to use a USB disk that uses USB 3.0 on Windows 7. You can try to install Windows 7 in a PE(Preinstall Envirionment).Most of them are installed USB 3.0 driver.
csdvrx
commented
2 years ago There are a few such images around if you are in a hurry, google for Windows7U_x64_SP1_ZEN_v1 as the AMD Zen CPUs have similar issues.
BTW here's a link to a post explaining how to do that the legal way, with the official image and DISM: https://community.hwbot.org/topic/166612-windows-7-x64-sp1-with-integrated-drivers-for-zen/
Official FAQ
Ventoy Version
1.0.44
What about latest release
No. I didn't try the latest release.
BIOS Mode
Both
Partition Style
MBR
Disk Capacity
256GB
Disk Manufacturer
Samsung
Image file checksum (if applicable)
Yes.
Image file download link (if applicable)
No response
What happened?
Hi! I am not sure it's a Ventoy's bug really. But, please, explain to me - why does it happen with the 50/50 - sometimes my usb-drive(s - even!) doesn't see the usb-port and sometimes it does? It fails after I proceed to the Windows Edition Selection Menu in its typical installation process...