Current Status of Xbase++ and Windows 10 Creator's update.
Posted: Thu Dec 21, 2017 10:44 am
I'm trying to get a handle on the current situation with Alaska and Windows 10 Creators update.. As I understand it:
1. SMB1 is out...
2. SMB 2 is in, and the smbfix that alaska offered:
http://www.alaska-software.com/community/smb2.cxp
is no longer necessary.
3. Creators update caused xb2net applications to fail on a socket level. Boris issued a temporary
fix with version 3.5.04, and 3.6.
4. There is an Alaska problem with fonts >100% on 64 bit machines.
Open questions:
1. What about oplocks ?
2. What about if the oplocks fixes were put in, how does the new update affect that ?
3. Are there any other Windows 10 Creator problems that either:
A. Were addressed ?? (what were they)
or
B. Have yet to be addressed (what ARE they).
4. What (if anyting) needs to be implemented on the server, and what on the stations ?
Of course, it would be a good thing for Alaska to clarify things from a big picture overview, but that probably won't be coming out for a few years...
1. SMB1 is out...
2. SMB 2 is in, and the smbfix that alaska offered:
http://www.alaska-software.com/community/smb2.cxp
is no longer necessary.
3. Creators update caused xb2net applications to fail on a socket level. Boris issued a temporary
fix with version 3.5.04, and 3.6.
4. There is an Alaska problem with fonts >100% on 64 bit machines.
Open questions:
1. What about oplocks ?
2. What about if the oplocks fixes were put in, how does the new update affect that ?
3. Are there any other Windows 10 Creator problems that either:
A. Were addressed ?? (what were they)
or
B. Have yet to be addressed (what ARE they).
4. What (if anyting) needs to be implemented on the server, and what on the stations ?
Of course, it would be a good thing for Alaska to clarify things from a big picture overview, but that probably won't be coming out for a few years...