NetOp for Windows, version 5
============================

Welcome to NetOp for Windows a program for remote control of Windows, OS/2 
and DOS PCs. NetOp for Windows modules are compatible with NetOp for OS/2
modules with the same version number, furthermore NetOp for Windows guests
can remote control DOS RemPCs version 4.3x.


NetOp for Windows Files
-----------------------
The following is a list of all NetOp for Windows files


File name	Description	                Used by module	Location
-----------------------------------------------------------------------------
COMPROF.NDB     Communication profiles	Guest & Host	NetOp directory
DTLWIN.DLL                              Guest & Host    NetOp directory
KEYBHOOK.DLL                            Guest & Host    NetOp directory
KRNLGST.DLL                             Guest           NetOp directory
KRNLHOST.DLL                            Host            NetOp directory
LOMEM.COM                               Guest & Host    NetOp directory
LOMEM.DLL                               Guest & Host    NetOp directory
MISCFCT.DLL                             Guest & Host    NetOp directory
NDDHGST.DLL                             Guest           NetOp directory
NDDHHST.DLL                             Host            NetOp directory
NHSTCONF.NDB    Host configuration info Host            NetOp directory
NGUESTW.EXE     Main Guest program      Guest           NetOp directory
NHOSTNT.DLL     Used under Win NT       Host            NetOp directory
NHOSTNT.SYS     Used under Win NT       Host            system32\drivers
NOW.HLP	        Guest help file         Guest           NetOp directory
NOWBASE.DLL                             Guest & Host    NetOp directory
NOWCONF.NDB     Guest conf. info        Guest           NetOp directory
NHOSTW.EXE      Host program            Host            NetOp directory
NOWHOST.HLP     Host Help file          Host            NetOp directory
NOWHOSTM.EXE                            Host            NetOp directory
DWRT0.DLL                               Guest & Host    NetOp directory
PHBOOK.NDB      Phone book database     Guest           NetOp directory
README.TXT      Readme file             Guest & Host    NetOp directory
SECURITY.NDB    Security configuration  Host            NetOp directory
VNETOP.386      Virtual device driver   Host            NetOp directory


Setup
-----
Some slow PCs (20 MHz 386s) might have problems running SETUP.EXE. The
setup program can execute extremely slowly (taking minutes to display a
dialog). If you experience this problem please contact your vendor or
Danware.

Serial Communication
--------------------
If your PC hangs completely when doing serial communication, this could
be due to a problem with a buggy Super I/O chip (SMC '655), typically installed
on PCI-bus-based systems. The problem is described in Microsofts Knowledge
Base (article PSS ID Number: Q119853). To work around the problem you can
do one of the following:

 1) Disable FIFO buffering (this will reduce data throughput).
    FIFO is disabled by putting the following entry in the [386enh]
    section of your SYSTEM.INI:
       COMxFIFO=0
    Where x should be substituted with your COM port number (e.g. 1 or 2).

 2) Download an updated SERIAL.386 driver from Microsoft which works around
    the problem: Query Microsofts knowledgebase for WG1001.

Compaq QVision
--------------
If you experience trouble remotely controlling DOS boxes on a Windows 95 host 
with a Compaq QVision display adapter, please update your display driver.
You should use at least version 1.11.7M (available e.g. from Compaq's forum
on Compuserve).

Windows 95
----------
NetOp does not currently support on-line switching of graphics resolution on 
a host. After switching resolutions (e.g. 800x600 to 1024x768) you must hangup
and re-connect.

NetOp for Windows can remote control the Windows 95 graphical
logon process by placing the following value in the registry. (Most 
easily done by saving the following 4 lines in an ascii file with 
extension .reg and doubleclicking the new files icon, remember to to change 
the path to NetOp if you have installed in a different location).

Also remember to enable
Netop Host|Configuration|Options|Wait for call on startup.

-----><-------- Cut here ------------ Cut Here -----><-------
REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices]
"NetOp"="C:\\NETOP\\NHOSTW.EXE"
-----><-------- Cut here ------------ Cut Here -----><-------

Windows NT
----------
NetOp now supports serial communication when running under Windows NT.

Due to system limitations NetOp 5.2 cannot run on Windows NT unless
there is a logged on user.

How to make Windows NT logon at boot, so NetOp 5.2 kan run immidiately:
   

   1. Log on as administrator (no less)
   2. In Progman.exe: Place NHOSTW in group StartUp (common) (name is 
         different in non-US versions of NT). Turn on "seperate address 
         space".
   3. In NHOSTW.EXE Enable "Wait for call on startup" in the host Options
   4. Choose/create a (dummy) user who will always be logged on
         If the system is physically safe (e.g. in a locked room
         or with a locked keyboard & mouse) just use Administrator,
        otherwise create a user with only the following priviledges:
         Log on locally
         Read/execute Regedt32.exe, netop host and progman.exe
   5. MAKE SURE no users (inluding the dummy user) have a blank 
         password! (otherwise it wont work due to a system
         "feature"). (this really doesn't apply to users who
         don't log on with the registry trick).
   6. In regedt32.exe: Go to the following key: (the line feed is not 
        part of the name)
        \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
                Windows NT\CurrentVersion\Winlogon
   7. In regedt32.exe: On the Security menu, grant INTERACTIVE users 
       FULL access to this key (includes the dummy user etc.)! 
       (otherwise you will effectively lock the system and throw away
       the key...)
   8. Enter the following values, all of type REG_SZ
        (MAKE SURE AutoAdminLogon is NOT present until the other values
         are ok, removing that value (not just making it blank) disables
         autologon).
        LegalNoticeCaption ""
        LegalNoticeText ""
        DefaultDomainName "<put name of domain user is in here>"
        DefaultUserName "<put name of dummy user here>"
        DefaultPassword "<put users password here>"
        AutoAdminLogon "1"
   9. Whenever you log off or reboot, the dummy user is now logged on
        on and the Host starts (you may have other programs do the
        same, just be sure their rights are enabled too).
      This CAN be bypassed by holding down the shift key (if you haven't
        set IgnoreShiftOverride to "1" in the registry key).
  10. Verify that none of the remote control accounts ask stupid 
        questions during logon e.g. (please select a Netware server,
        please enter NetWare password etc.).

To remote control under a different user name:
   1. Call the machine.
   2. If the screen is garbage send CTRL+ALT+DEL and type the current
     users password (to unlock the host workstation).
     HINT: the 5.2 Guest has a hotkey for this, see under 
        Program Options.
   3. Use Regedt32 to change the username and password (beware: people 
     who can see the screen can see the password!). for details see step
     8. above.
   4. In program manager request a logoff and accept any confirmation
     prompts (the one from the NetOp itself last).
   5. Wait a few seconds while you are being logged on, then call
     again.


Incorrect Graphics
------------------
If you experience trouble remotely controlling a graphics adapter, please
make sure that you are using the latest version of the driver software for
the graphics adapter.


Danware Data A/S
February, 1996