Updated to version 1.172

Please keep in mind that this is still a development version and might surprise you (not necessarily in a good way).

Do not let me discourage you to build and test this version, although there will be some risks involved such as data corruption or loss of data.
This commit is contained in:
Olaf Barthel
2018-07-26 10:31:20 +02:00
parent a2431211ff
commit 81723de458
4 changed files with 477 additions and 412 deletions
+19 -1
View File
@@ -2412,6 +2412,24 @@ smbfs 1.169 (22.7.2018)
smbfs 1.170 (22.7.2018)
- Path name processing failed to deal properly subdirectories of
- Path name processing failed to deal properly with subdirectories of
directories which were located in the root directory. Thanks go
to Hubert Maier who reported the problem.
smbfs 1.171 (24.7.2018)
- Calling Info((BPTR)NULL, parameterBlock) would trash memory. Fixed.
- Replaced all the various checks for valid locks and files with
common code.
smbfs 1.172 (26.7.2018)
- SetFileSize() never checked if the volume was write-protected. Ouch.
- ExAll() now checks if the type of records it should return is valid,
which in this case means if it is > 0. Previously, it treated 0
just like it would treat values > ED_OWNER. Now it rejects 0 with
the error code ERROR_BAD_NUMBER.
+452 -405
View File
File diff suppressed because it is too large Load Diff
+5 -5
View File
@@ -1,6 +1,6 @@
#define VERSION 1
#define REVISION 170
#define DATE "22.7.2018"
#define VERS "smbfs 1.170"
#define VSTRING "smbfs 1.170 (22.7.2018)\r\n"
#define VERSTAG "\0$VER: smbfs 1.170 (22.7.2018)"
#define REVISION 172
#define DATE "26.7.2018"
#define VERS "smbfs 1.172"
#define VSTRING "smbfs 1.172 (26.7.2018)\r\n"
#define VERSTAG "\0$VER: smbfs 1.172 (26.7.2018)"
+1 -1
View File
@@ -1 +1 @@
170
172