-
Notifications
You must be signed in to change notification settings - Fork 17
Expand file tree
/
Copy pathREADME.macWindowsIssue
More file actions
29 lines (19 loc) · 1014 Bytes
/
Copy pathREADME.macWindowsIssue
File metadata and controls
29 lines (19 loc) · 1014 Bytes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
In the process of using OMSI, we discovered a bug in Windows that
affected server operation, as follows:
Apparently if one creates a file on a Unix system (at least a Mac), and
then opens it on a windows system, the file may become an odd mixture of
Unix and Windows in terms of end-of-line characters. This is a known
issue; see
https://forum.unity.com/threads/inconsistent-line-endings.40671/
When this happened with the Questions.txt file, the result was that
students running the client on a Mac (but not Linux or Windows) had
severe problems with distorted line structure. See the file
Questions.txt.macWinIssue.SAVE in this package; run od -x and note that
some lines have 0x0a0d and some have just 0x0a.
Short-term fix: Avoid running the server on Windows.
Longer-term fix: Have the server check for, and fix this anomaly in the
Windows file.
If you suspect a problem and are running the server on a Unix machine
(Mac, Linux), simply open the file in vi, run
:set ff=unix
and save the file.