			Windows Server Package
		      --------------------------
		      known bugs and limitations


1. Installation program

	- setup sets the last installed protocol as a default instead
	  allowing user to select between ones available.
	  (will be corrected)
	- if installation fails for some reasons, setup may run
	  uninstall without notification.
	  (be careful when selecting setup parameters)
	- sometimes setup fails when selecting the target directory
	  in format other than old 8.3.
	  (workaround: always select old-style target directory)
	- under Win32s, installation program doesn't check the
	  existance of old "wserver.ini" file and may overwrite old
	  user entries and/or create duplicated entries.
	  (workaround: delete "wserver.ini" file before installation)
	- if more than one protocol selected to install, the default
          will be set to the last copied.
	  (will be corrected)
	- "uninstall" doesn't remove NT link driver and its registry
	  entries.
	  (workaround: remove the following key with subkeys manually)
	  HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\B004Drv

2. Windows Server

	- when running under Win32s, INI-file section size can't be
	  larger than 1024 bytes.
	- Sometimes Windows Server hangs on exit when there is an
	  active transputer task running.
	  (workaround: terminate the task before exit).
	- all dialogs and controls don't appear as 3D under Win32s
	  and Windows NT, even if CTL3DV2.DLL/CTL3D32.DLL installed.
	- when running server with the command line (or using "Boot"
	  command in Windows 95 Explorer), it doesn't detect the bootable
	  file format and tries to use the default protocol.
	  (will be corrected)
	- when trappable exception occurs, server should display it's 
          number end exit. However, in some cases it doesn't stop
          running after notification message.
	  (will be corrected)
	- in "Priorities" dialog, "Thread priority" doesn't
          meaningful, really - WSP is "almost" single-threaded
          application (second thread now could be created when using
	  buffered GDI output).

3. Windows Library

	- string parameters in almost all functions which accepts
	  (char *) limited to 256 chars.
	- SelectBitmapToDC function works correctly (as it should)
	  only under NT, because it uses call to (API) PlgBlt. Under
	  Windows 3.1 and Windows 95 it calls (API) StretchBlt
          instead.
	- SelectBitmapToDC function doesn't work with 24-bit images
	  and sometimes hangs when trying to load 16-bit image.
	  (will be corrected)
	- SaveBitmapFile function doesn't save the correct palette
	  with an image. Instead, it saves the uniform palette.
	  (will be corrected)
	- LoadIconIndirect function extract the first icon from the
	  resource file (with index = 0), regardless of screen and
	  cursor resolution and color depth.
	  (will be corrected)
	- LoadBitmapFile function tries to load the whole bitmap into
	  memory and fails if there is not enough memory.
	- Programmer's Guide refers (in Chapter 10.2.3) to function
          "Polygon", which actually doesn't exist in the library.
          (will be corrected)
	- Programmer's Guide refers (in Chapter 10.3) to function
	  "DeleteBitmap", which actually doesn't exist.
          (will be corrected)
	- Makefiles in "Exapmles" and "Guide" directories refer to
	  library "wlib.lib", which don't exist.
	  (workaround: rename "wlib4.lib" or "wlib8.lib" - depending
	  on type of your root transputer - to "wlib.lib", in "Lib"
 	  directory)
	- "Tab" key doesn't work in dialog windows created from
	  transputer application.
	  (will be corrected)
	- DDE examples don't work correctly under Windows NT
	  (will be corrected)
	- none of functions support UNICODE.

Please look at our WWW page at http://www.ecsc.mipt.ru/Elcom for the
latest information, workarounds, patches and updates.

If you'll find a (not listed here) bug or inproper functionality of
any Windows Server 95 component, please report your problem to Elcom
Technical Support at:

	Address:	2-171 generala Antonova st.
	  		Moscow 117279 Russia
	Phone/fax: 	(+7 095) 9732660
	E-mail:		kitten@transcom.mipt.ru

Please inform us about the following:

	- Windows Server Package version (note that different EXE and
	  DLLs may have different versions and build numbers)
	- Computer name and model
		- CPU (type, model, clock fq.)
		- RAM (type, amount)
		- HDD (model, interface - IDE, EIDE, SCSI etc.)
		- other hardware installed (video/network/SCSI adapters,
		  sound cards etc.), incl. the configuration - IRQ,
		  DMA, I/O address
	- Software (when applicable)
		- DOS version
		- Windows version and build
		- Win32s version
		- file system (FAT, NTFS, HPFS etc.)
	- Transputer hardware (as much detailed as possible)
	- Detailed instructions how to retrieve a problem

To solve your problem, we also might have to ask you about the following:

	- config.sys
	- autoexec.bat
	- win.ini
	- system.ini
	- Registry entries
