diff options
| author | Javier <dev.git@javispedro.com> | 2023-02-19 17:49:28 +0100 |
|---|---|---|
| committer | Javier <dev.git@javispedro.com> | 2023-02-19 17:49:28 +0100 |
| commit | 4091173cceea8f2c3b0cdbc19a1adb6bd87c0a94 (patch) | |
| tree | d0d5cdb0e2e0e68f7d3bc20fc1f2fef72c1b77da | |
| parent | 37c2320920bf2de11749370396da23cab0aafa77 (diff) | |
| download | vbados-4091173cceea8f2c3b0cdbc19a1adb6bd87c0a94.tar.gz vbados-4091173cceea8f2c3b0cdbc19a1adb6bd87c0a94.zip | |
fix typos in README
| -rw-r--r-- | README.md | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -314,13 +314,13 @@ and a 3 letter hash of the filename. For example, `LONG FILE NAME.TXT` will become `LONG~20B.TXT`. These behave like normal files otherwise. The use of hashes allow the short file names to be consistent between reboots -of the guest OS, even if the host OS does not have support to store long these +of the guest OS, even if the host OS does not have support to persist these short file names. If your host OS does have support for storing persistent -short file names and want to use those instead of the autogenerated ones, +short file names and you want to use those instead of the autogenerated ones, consider using the option `/host` when mounting a shared folder. If you have a directory with lots of similarly names files, it may help to reduce -the chances of a hash collision by increase the number of letters dedicated to the -hash portion of the short file names. For that, use the `/hash <n>` option. +the chances of a hash collision by increasing the number of digits dedicated to the +hash portion of short file names. For that, use the `/hash <n>` option. In addition, there is support for translation of extended characters from the host filesystem into the guest DOS' codepage. |