aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEli Zaretskii2014-07-12 12:08:41 +0300
committerEli Zaretskii2014-07-12 12:08:41 +0300
commita5a8e250d5fc17b3e4a7955f2c896f2b050b2960 (patch)
treedd04ed686606f0fc999821b902bf93c87410c890
parent114ce4b8797206221febb0ac0f19872855e9b151 (diff)
downloademacs-a5a8e250d5fc17b3e4a7955f2c896f2b050b2960.tar.gz
emacs-a5a8e250d5fc17b3e4a7955f2c896f2b050b2960.zip
etc/PROBLEMS: Update problems specific to MS-Windows.
-rw-r--r--etc/PROBLEMS12
1 files changed, 11 insertions, 1 deletions
diff --git a/etc/PROBLEMS b/etc/PROBLEMS
index a1df7eebd18..1f9200febbf 100644
--- a/etc/PROBLEMS
+++ b/etc/PROBLEMS
@@ -1917,6 +1917,16 @@ MSDN:
1917includes a short description of MSLU and a link where it can be 1917includes a short description of MSLU and a link where it can be
1918downloaded. 1918downloaded.
1919 1919
1920** Emacs refuses to start on Windows 9X because ctime64 function is missing
1921
1922This is a sign that Emacs was compiled with MinGW runtime version
19234.0.x or later. These versions of runtime call in their startup code
1924the ctime64 function, which does not exist in MSVCRT.DLL, the C
1925runtime shared library, distributed with Windows 9X.
1926
1927A workaround is to build Emacs with MinGW runtime 3.x (the latest
1928version is 3.20).
1929
1920** A few seconds delay is seen at startup and for many file operations 1930** A few seconds delay is seen at startup and for many file operations
1921 1931
1922This happens when the Net Logon service is enabled. During Emacs 1932This happens when the Net Logon service is enabled. During Emacs
@@ -2084,7 +2094,7 @@ The function set-time-zone-rule gives incorrect results for many
2084non-US timezones. This is due to over-simplistic handling of 2094non-US timezones. This is due to over-simplistic handling of
2085daylight savings switchovers by the Windows libraries. 2095daylight savings switchovers by the Windows libraries.
2086 2096
2087** Files larger than 4GB report wrong size 2097** Files larger than 4GB report wrong size in a 32-bit Windows build
2088 2098
2089Files larger than 4GB cause overflow in the size (represented as a 2099Files larger than 4GB cause overflow in the size (represented as a
209032-bit integer) reported by `file-attributes'. This affects Dired as 210032-bit integer) reported by `file-attributes'. This affects Dired as