Closed Thomas1029 closed 11 months ago
Hi. Tried asking this question prematurely earlier. I've included the full log and a picture of the Rufus window.
Why does Rufus change a period (.) to a underscore (_) in the Volume label. It shows correctly in the Volume Label box but then when it creates the media that period is changed to a underscore. Then I have to go back into File Explorer and change it back to a period.
Any help would be appriciated.
Thanks
It's designed that way, because, IIRC, some lookups for a volume label, which are commonly enacted by Linux distros, would fail otherwise, but mostly because labels are always going to be limited anyway, so if you want to free yourself of such limitations and have Windows display whatever you want, including exotic characters or super long labels, you should set the label in autorun.inf
anyway, which you can do by having something like:
[autorun]
label = 19045.3693
Please don't open a new issue, as this behaviour will not change.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.
<!-- PLEASE READ THIS CAREFULLY:
You MUST read and complete the steps from the checklist below, by placing an x into each [ ] (so that it shows '[x]', NOT '[ x]' or '[x ]'), BEFORE clicking on 'Submit new issue'.
Failure to perform these steps, WHICH ARE ONLY THERE TO HELP YOU, will usually result in your issue being dismissed without notice.
If you are reporting an issue when trying to run Rufus, or when trying to boot a media created by Rufus, you MUST provide a log, period. Please do not assume that the developer(s) will be able to "guess" the specifics of your environment, what image you used, what type of media you used it with or the many many other critical parameters that the log provides data for. To investigate an issue, a log from Rufus is ALWAYS required.
If you still choose not to provide a log when reporting a problem, you agree that your issue will be closed without any further investigation.
YOU HAVE BEEN WARNED. -->
Checklist
<FULL LOG>
below.Rufus version: x.y.z
- I have NOT removed any part of it.Additionally (if applicable):
(✓)
button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.Issue description