V/386 Release 3.0 Version 2.1 Bugs

[G Whiz]

I am posting my list of bugs, not because they are critical, but because
I have not received much support from Microport.

I am running Microport V/386 Release 3.0 Version 2.1 with DOSMERGE (Beta 0.2)
with the following equipment:

	- Everex Step 386/20Mhz with 2MB ram and 128K cache
	- Miniscribe 72MB & Seagate ST-251 Hard Disks
	- Telebit TrailBlazer modem
	- VEGA VGA
	- Sony Multiscan (cdp-1302) monitor

Problem 1 - DOSMERGE Documentation
----------------------------------
  On page ii under "Merge 386 Manuals", the following manuals are mentioned:
	- Getting Started with Merge 386
	- Merge 386 User's Manual
	- Merge 386 Advanced User's Manual
	- Merge 386 Administrator's Manual
	- Merge 386 Manual Pages
  I did not receive the "Merge 386 Advanced User's Manual" or 
  "Merge 386 Manual Pages".  I called Microport several times and they claim 
  these manuals do not exist.  Consequently, none of the other manuals
  document how to connect a SCANCODE terminal to the system, as well as the
  changes made to critical UNIX facilities like "getty() & gettydefs".  Last
  November at COMDEX, I happened onto the LOCUS booth and snooped enough to
  find out the magic trick is the "SCANCODE" gettydefs option.
  
  I hope other agree, that the changes made to standard UNIX should be
  documented.
  
Problem 2 - Printer Driver
--------------------------
  Under DOSMERGE, I have found out that the UNIX printer driver only supports
  132 column lines.  This is a fairly critical problem because most PC
  programs like WordPerfect insert printer control codes which rapidlly
  exceed the 132 column line limitation.
  
Problem 3 - SAR(1M)
-------------------
  Under DOSMERGE but not standard UNIX, SAR produces the following anomalies:
	- cpu idle% is drastically different
	- disk utilization is blank under DOSMERGE
	- a "floating exception - core dumped" error occurs during virtual
	  statistics under DOSMERGE
	  
Problem 4 - Support
-------------------
  Lastly, I am willing to accept the burdens and problems that come along with
  runing BETA release software.  However, I believe that companies put BETA
  software out to allow a selected public to help in debugging.  I believe
  that Microport could better realize this advantage if they provided monthly
  or quarterly BETA release upgrades, instead of waiting for a PRODUCTION
  release.
  
Comments (supportieve/contrasting views) are welcome and appreciated.


  -- 
                                            /**************************/
  Garon C. Yoakum (g_whiz at pedro.UUCP)      /*  Power Crazy 386 Owner */
  ..!uunet!iconsys!caeco!pedro!g_whiz     /**************************/