- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,662
- Country
thanks.
it looks like it forces two things :
- if no partition is found, force a FAT partition anyway (why?, no partition present on the drive, but let's fake one?)
- if USB is not init or inserted, it "set device" anyway, instead of looping with "wait for device".
Maybe looking at "waitForDevice" and "setDevice" functions will be interesting to see what really happen, and for how long it waits for the drive to initialize.
USBLoaderGX waits 20 seconds per USB port (40 total!) and it's not enough?
it looks like it forces two things :
- if no partition is found, force a FAT partition anyway (why?, no partition present on the drive, but let's fake one?)
- if USB is not init or inserted, it "set device" anyway, instead of looping with "wait for device".
Maybe looking at "waitForDevice" and "setDevice" functions will be interesting to see what really happen, and for how long it waits for the drive to initialize.
USBLoaderGX waits 20 seconds per USB port (40 total!) and it's not enough?