You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.
When NOOBS boots, if any kind of alert dialog comes up (e.g. warning about not being able to resize FAT32 correctly, not being able to access internet, etc), which requires clicking "OK" to dismiss, pressing "4" or another output mode to be able to see what's going on without an HDMI monitor isn't possible. If you're doing NOOBS for the first time with a composite monitor, you just simply can't see that that's what the issue is; it appears broken.
The workaround is to press Return to dismiss the dialog blindly, though then of course the user wouldn't see what the dialog had to say. If there's no clean fix to this, I'd suggest that this workaround be put in the usage notes, because it's a lot better than not being able to see what's going on at all.
Also, same issue issue applies during silentinstall. You can only see what's going on if you have an HDMI monitor attached.
The text was updated successfully, but these errors were encountered:
To help with testing this - an easy way to get a dialog at NOOBS boot-up (which blocks the 1/2/3/4 keypresses) is to boot a freshly-written NOOBS Lite without an ethernet cable connected :)
When NOOBS boots, if any kind of alert dialog comes up (e.g. warning about not being able to resize FAT32 correctly, not being able to access internet, etc), which requires clicking "OK" to dismiss, pressing "4" or another output mode to be able to see what's going on without an HDMI monitor isn't possible. If you're doing NOOBS for the first time with a composite monitor, you just simply can't see that that's what the issue is; it appears broken.
The workaround is to press Return to dismiss the dialog blindly, though then of course the user wouldn't see what the dialog had to say. If there's no clean fix to this, I'd suggest that this workaround be put in the usage notes, because it's a lot better than not being able to see what's going on at all.
Also, same issue issue applies during silentinstall. You can only see what's going on if you have an HDMI monitor attached.
The text was updated successfully, but these errors were encountered: