WinaXe is the pre-eminent X Windows environment for the MS Windows 9x/ME/NT4/2K/2K3/XP/Vista/Windows 7 platforms.WinaXe brings remote UNIX applications to your PC with each in a separate window. It enables easy access to different operating systems. WinaXe Windows X Server transparently connects different operating systems and their applications together.
v7.7 [Nov 8, 2009]
1. Ftp:
- any foreign SOCKS4 server may be used in "FTP via SOCKS4" mode (earlier - only own Telnet/SSH's ones)
- most IBM MVS filesystems are processed with file-/directory- attributes
- the "Auto" Server Type item is added. Applicable in most cases.
2. Ping:
- the IP- and Port- scanning is improved
- some TCP servers may be checked more carefully
(HTTP, SMTP, POP3, IMAP, SSH , SPOP3/asSSL)
3. NFS-Server and NFS-Server as NT Service:
- "export.xml" file is used from now instead of the "export.us".Automatical convertation is provided.
- standalone NFS-Settings facility with much more settings is implemented
- the exported name of share item may be vary to provide any external name for sharing resource (e.g. "/rfiles" for "C:\nfsexport")
- the "rwSizePref" and "topMaxbytes" settings are implementedto limit the rsize/wsize NFS buffers.
Actual for, say, VmWare ESX NFS-Client in NFS-3/TCP mode.
- the usage of NFS(2,3) version and/or transport (UDP,TCP) protocols
are controlled now by corresponding settings
- two assistant settings are implemented for CreateFile of NFG-2 protocol to provide NFS-3 - like modes for CreateFile request - Guarded and CreateAsCreOpen, which is useful for some especial NFS-Clients.
- the "Verbose" trace mode has the influence on the NFS_ss.exe/Service also
4. NFS-Client for MS Windows 2K/2K3/XP/Vista win32 and/or x64:
- the installation under Windows 7 and Server 2008 is available
- better process of the exports with very many files
- modified the ShortName generation method
- Shell Extention Property Sheet DLL (XWPSHELL.DLL) is available under Vista also
- our standard Network Provider Name "XwpNTrdr" may be changed to any ASCII.
Actual for applications with built-in processing of "net use" output.
- NFS-Client NFSDrive :
- the new CheckBox "Explore" controls the starting of Windows Explorer after drive mapping (earlier - always)
- NFS-Client Settings :
- "LDAP" tab - the prefix "CN=Users" removed to provide the global searching in DB
- the "Enable TCP Reconnection" settings allows the dynamic reconnections to NFS-Server after network restarting (actual for, say, unstable WiFi)
- "Network" tab - the "TimeOut Period" setting is in seconds now (earlier -in msec) with 1..50000 sec limits
5. NFS-Client for MS Windows/x64 :
- NFS-ClientX64 NFS-Client for Windows/x64 was built-in the package and is installed via usual Installation procedure.
- The NFS-ClientX64 may be installed under MS Server 2008 64bit
- The Shell Extention Property Sheet DLL (XWPSHL64.DLL) is implemented
6. XServer:
- the usage of MS Windows IME helper is blocked, because it is useless with XServer. To enter CJK text in an X client, you need to run any remote XIM server X-Client(e.g. "scim" or "gcin")
- Unicode titles of windows and icons in "Multiple" mode are provided if set as COMPOUND_TEXT lines or by "_NET_WM_NAME"/"_NET_WM_ICON_NAME"
properties.
- multi-monitor "21" combination is allowed from now in all modes
(including "FullScreen")
- xwp.ini/"[XSETUP]"/"PromptOnSuspend=1" implemented to control the transition to the "Suspend" PC mode.
- the FullScreen window can be created shifted using new mklShiftPriMonY0/X0 manual settings as default for mklFullScreenX0/Y0
- the mklFullScreenX0/Y0 manual settings allows to set the necessary position of the XServer/FullScreen window
- many operational X-Sessions may be run with the same Display Number
if you use separate local IP address for each X-Session.
Very actual for PC with many IP addresses.
7. Startup:
- "joblist.xml" file is used from now instead of the "joblist.ini".
Automatical convertation is provided.
- the Status bar shows your actual "DisplayName" value and"ini"-file specification.
- the specific name of joblist file may be set in each your "xwp.ini" file
- the new "Close Job" button implemented to dismiss the usage of the another "ini"-file (which was loaded because of "Open Job.." action)
- any foreign SOCKS4 server may be used (earlier - only own Telnet/SSH's ones)
8. NFS-Client SDK:
- the C "nfsc1_t" sample test which uses the "nfsc_ipp" sample XwpNFS-SDK toolkit classes is implemented.
Full sources of "nfsc1_t" sample test project are freely available.
- the C "nfsc_ipp" sample XwpNFS-SDK toolkit as interface to low-level NFSLib32.dll XwpNFS-SDK API with three XwpNFS-SDK toolkit classes (XWPNfsClConn, XWPNfsClDirList and XWPNfsClFile) are implemented.
The direct usage of low-level NFSLIb32.dll XwpNFS-SDK APi (nfslib32.h, nfslibex.h, nfslib32.lib) is obsolete now.
Full sources of "nfsc_ipp" sample XwpNFS-SDK toolkit project are freely available.
- more NFS operations (rm, rmdir, mkdir, rename ) are available in the limited free demo-version of low-level NFSLib32.dll XwpNFS-SDK API.
The limited free demo NFSLib32.dll XwpNFS-SDK API is freely available.
- directories with very many files and/or very long filenames are available for browsing now
- the sample libNFSC.cpr settings file are more useful and informational now.
9. Ftp/NFSViewer:
- more remote operations (rm, rmdir, mkdir, rename ) are available in the libNFSC.DLL NFS-Viewer, limited free demo-version of the full NFS-Browser plug-in, based on the XwpNFS-SDK API.
The limited free demo libNFSC.dll is freely available.
- directories with very many files and/or very long filenames are available for browsing now
- the sample libNFSC.cpr settings file are more useful and informational now.
10. Settings:
- The XStartup facility can be started from the
Run -> XServer tab.
Is actual if you use variable name of JobList file
in different "xwp.ini" - files.
11. XDK:
- the "XLOCALEDIR" env.var. may contain Windows drives.
The pathDelimiter=';' is used instead of standard ':'.
Actual if the network multi-user installation is used.
- useful XLib API entrance implemented for local convertation
of COMPOUND_TEXT strings to UTF8 strings (is used by Xserver for CJK titles) :
int __stdcall mklXWPXLibConvertCOMPOUND_TEXT_to_UTF8(const char *loc_,
char *utf_buf, const char *string, int max_utf)
Used by new XServer/Multiple to output CJK titles.
- the ".pdb" files for XDK are available (may be requested)
to debug your own X-program base on XDK
2.2. The following bugs have been fixed:
1. Ftp:
- the "HideDrives" settings may lead to crash if network drive(s) is presented in Windows list of drives.
2. NFS-Server and NFS-Server as NT Service:
- ReaddirPlus crashed sometimes with very long directories if rsize/wsize are too small, may take place the leaks of items or application crash.
- the "UselongReadDirPlus=1" mode is reanimated and significantly improved.
But for very long directories we recommend to use the "timeo=..." option
on the "mount" with reasonable timeout (say, 1000).
- many_f(30,5000,15000)/NFS3 is tested: tcp/udp, 1K/32K, Uselong...=0/1
- "super-long" filenames leaded to "RPC error:cannot transmit".
(now the Alrternate filename 8.3 is used)
- checks that the files are exist (important for volatile directories)
to prevent the empty reply on readdir[plus]
- the "RPC error: cannot transmit" message took place
if RPC READDIR[plus] or read requests contained auth "verifier" item
- the "RPC error: cannot transmit" message took place
on some NFS-3 read requests (with very short and very long rsize/wsize attributes)
- the rsize/wsize lehgths in replies are more correct now
- the full local DOS(!) path returned sometimes (instead of clear file name)
on NFS rename request
- more correct processed the "violent files' life",
when any file/directory may be created/changed locally as well as via NFS
(including active local removing of deep subdirectories)
- more correct NFSERR code is sent on Errors after :
CreateDirectory, RemoveDirectory, CreateFile and ReadFile
- correct processing of V3/EXCLUSIVE CreateFile (return NFSERR_NOTSUPP)
- nfs_create supports now the size/atime/mtime attributes
Actual for some VmWare ESX NFS-Client to set correct date for files.
- nfs_write/NFS-3 and nfs_setattr/NFS-3 provide the "before_attr3" now.
- restarting the NFS server, sometimes confuses the vxWorks NFS client,
by having the exports in a different order.
- CreateFile locked the processing file even it opened only for shareable reading
as result, local access to such as files was blocked
(e.g. cygwin's "tail -f file" watching was impossible).
3. NFS-Client for MS Windows 2K/2K3/XP/Vista win32 and/or x64:
- sometimes the leaks in the listing of export took place
- the clearing of pending TDI requests is more correct now
(the BSOD took place if very many files on export)
- BSOD took place if the NFS-Server did not send the file ShortName in reply
- under Vista the NPDLL's trace file was not copied on reboot
- incorrect returning Error codes of NPGetConnection() and NPCancelConnection()
requests leaded to problems(even BSOD) for other Windows Network Providers.
E.g., LanMan's mappings were marked by the red cross in MyComputer explorer
and could not be unmapped sometimes
- fixed the wrong execution from DOS the rename command with the "*" in the
target
- fixed the wrong execution from DOS the copy.. command
if the current directory was not the root one
- undocumented requests to driver (unedr Vista SP1) are processed.
- the BSOD under Vista SP1 took place in DOS after Ctrl C
in intensive copy-fc-del commands loop
- was no unmapping after the UNC access, i.e. new settings did not have
any influence on such as mapped exports (up to Windows reboot).
- the result of UNC execution of "NET USE", w/o local name,
e.g."NET USE \\Srv\ShNam", was invisible in the "NET USE" output
and could not be dismounted by "NET USE /DELETE \\Srv\ShNam" command
or via Windows Explorer
- sometimes (depends on the filename length) some EXE- file cannot be
started from Explorer under Vista/UAC with the wrong message
"the specified path does not exist".
- file was not copied using the "Copy" item of Explorer pop-up menu
(by the right mouse button) in the same directory with the standard
"Copy of " name prefix.
- unexpected(by Windows) driver registration prevented to run some
MSI files under Windows 2003 Server with
the wrong error message "Windows Installer Not Accessible".
- the mapping by "Reconnect at Logon" mode (during the next Logon)
could provide the deadlock(under Vista) and BSOD(WinXp SP3)
while the earlier Authorization dialog box is on Desktop.
- NFS-Client NFSDrive :
- the horizontal scrolling is added to wotk with long names of exports
4. NFS-Client for MS Windows/x64 :
- installing this under Win2003R2/x64 server killed the Windows RPC service.
As result, disabled a lot of network related services and protocols.
5. XServer:
- the default position of creating windows in "Multiple" mode was wrong sometimes
6. Startup:
- the actual DisplayNumber is used in starting telnet/SSH
(earlier "X11 Forwarding" used only DisplayNumber=0);
- the correct toggling of the "iniSpf" attribute of creating jobs is provided after each "Open Job.." action
7. Ftp/NFSViewer:
- the mount connection was not closed after mount operation completion
- was not operational if non-single network card presented
- mount used non-reserved (>1024) local port number,as result, some mount-servers rejected the connection as non-trusted
- LOOKUP requests were wrong sometimes
- the incorrect FreeSize calculation in ReadDir[Plus] reply was fixed
- some settings (XWPBroadTime, XWPRetryNumber, XWPTimeOut and XWPTraceLevel) are loaded from selected ".cpr" file more correct.
8. Settings:
- Was not refreshed the state of buttons on the
after Run -> NFS-Server servive -> Start service
- On the Troubleshooting tab
the "IP address to access to XServer" setting
was processed incorrectly (reversed).
9. NFS-Client SDK:
- the mount connection was not closed after mount operation completion
- was not operational if non-single network card presented
- mount used non-reserved (>1024) local port number,as result, some mount-servers rejected the connection as non-trusted
- LOOKUP requests were wrong sometimes
- the incorrect FreeSize calculation in ReadDir[Plus] reply was fixed
- some settings (XWPBroadTime, XWPRetryNumber, XWPTimeOut and XWPTraceLevel) are loaded from selected ".cpr" file more correct.
10. XDK:
- X-Client can load xwpwsock.dll non-only times without crash.
11. Telnet:
- In the file telnet.out password and user-id were logged unencrypted.
Pocket Controller-Professional
