Intel LANDesk(TM)  Response
Release Notes for Version 1.0

These product release notes contain information about 
Release 1.0 of LANDesk Response.  In general, the 
information in these Release Notes supersedes 
information in the Intel LANDesk Response Installation 
and Administration Guide, the Intel LANDesk Response 
User's Guide, and the online Help.

IMPORTANT:
	In using LANDesk Response, a large and 
	valuable database of information is quickly 
	amassed.  This database is subject to 
	unplanned and untimely corruption because 
	of a power failure, crash of any user's 
	workstation, or other problems.  We recommend 
	that you back up the database immediately 
	after installation and configuration, and at 
	least daily thereafter.  Your backup scheme 
	should allow you to restore not only your most 
	recent backup, but also a few prior backups.

	Make sure that nobody is logged into LANDesk 
	Response while files are being backed up.  
	From the Menu Bar, select Admin, User Access, 
	List Login Register to open the Login Register
	where you can verify that no other users are 
	logged in.  Then select Admin, User Access, 
	Allow User Logins to remove the check mark 
	in front of the command, which disables 
	further logins to LANDesk Response.

For complete information on LANDesk Response, 
refer to the online Help:

 -	From LANDesk Response, press the F1 key to 
get context-sensitive online Help for the currently 
selected menu command, dialog box, or view.  Each 
dialog box also has a Help button;  choosing the 
Help button is the same as pressing the F1 key.

- 	If an error message box appears on your 
display screen, press the F1 key to get additional 
Help about the error.  Pressing the F1 key displays 
a description of both the cause and solution for the 
error.

- 	Once you're in Help, use the Search button at 
the top of the window to search Help for the text or 
topic of interest.


Installation Notes

SHARE.EXE:
	LANDesk Response uses Borland's Paradox Engine 
	(not Paradox or Paradox PAL).  Paradox Engine 
	requires that SHARE.EXE be loaded before you 
	start Microsoft Windows.  We recommend this be 
	done in your AUTOEXEC.BAT file.  If you allowed 
	the Setup program to do so, your AUTOEXEC.BAT 
	file was modified to run Share.

	Before Setup makes any changes to your 
	AUTOEXEC.BAT file, it creates a backup copy 
	named AUTOEXEC.000 (the extension may be 
	higher if a file by that name already existed).

WIN.INI:
	Paradox Engine has a section in the WIN.INI 
	file.  LANDesk Response requires that some of 
	these settings be set to specific values.  
	These settings were correctly set for you 
	by the Setup program if you let it modify 
	your WIN.INI file.

	If you already have a Paradox Engine section 
	in your WIN.INI file, you might have other 
	applications that use the Paradox Engine;  
	therefore, changing these settings for LANDesk 
	Response might cause problems with those 
	other applications.  We recommend you: 
	(1) allow Setup to make the changes to 
	your WIN.INI file, (2) save the backup copy 
	of your WIN.INI file made by Setup, 
	(3) start up LANDesk Response, 
	and (4) verify that your other Paradox Engine 
	applications function correctly while LANDesk 
	Response is running.

	If conflicts occur, they are usually with an 
	application installed to use shared files 
	on a network.  Check with the person who 
	installed the network version of Paradox or 
	Paradox Engine-based applications to 
	resolve any conflicts in your WIN.INI file.  

	The most common problems are with the 
	NetNamePath or PX35Locking entries in the 
	Paradox Engine section of the WIN.INI file.  
	These variables must be set to the same 
	values on all workstations, regardless of 
	where the actual database files for the 
	various applications reside. 

NOTE:
The next two discussions in these release notes 
explain the NetNamePath and PX35Locking 
entries in greater detail.

NetNamePath Issues:
	The Paradox Engine uses the NetNamePath 
	parameter to locate the directory in 
	which it will find its network control 
	files.  All users of Paradox Engine-based 
	applications must be able to read and 
	write to the directory specified by the 
	NetNamePath entry.  Because the Paradox 
	network control files are not application-
	specific, they can be placed in any location 
	accessible by all users of network Paradox 
	Engine-based applications.  The location of 
	this directory is typically determined 
	during the installation of the first Paradox 
	Engine-based application.

	When installing the Intel LANDesk Response 
	program, the default for NetNamePath is the 
	directory specified for the database files. 
	However, you may wish to change this 
	to some other directory set aside specifically 
	for the Paradox Engine network control files.  
	That way, if you install other Paradox 
	Engine-based applications at a later 
	date, users of that application will not 
	require read and write access to the LANDesk 
	Response database files.  

	The NetNamePath can be changed at a later 
	date, but it must be changed simultaneously 
	on all workstations when they are not using 
	Paradox Engine-based applications.  If you 
	already have another Paradox Engine 
	based-application, the NetNamePath parameter 
	should already exist in your workstation's 
	WIN.INI file.  In this case, when you install 
	LANDesk Response, the default for NetNamePath 
	will be its current value.  It will not 
	usually need to be changed as long as it 
	points to the same server directory on 
	all workstations.

PX35Locking Issues:
	If the Paradox Engine section in the 
	WIN.INI file contains an entry for 
	PX35Locking, it is important that all users 
	of LANDesk Response have the same setting 
	for this entry (that is, all 'Yes' or all 
	'No').  If there is no entry in the section 
	for this value, it defaults to ‘No'.  The 
	installation process does not attempt to 
	correct for inconsistencies with this entry 
	across the user base.  Therefore, 
	whatever value this entry has (if it exists) 
	will not be changed.  Again, the important 
	point is that all users of LANDesk Response 
	have the same value for PX35Locking.

Using Paradox to Access the LANDesk 
Response Database:
	The database tables used by the Intel LANDesk 
	Response program are compatible with Borland's 
	Paradox 4.0 and Paradox for Windows 1.0 
	products.  You can use these products to 
	access the LANDesk Response tables.  Reading 
	the tables should cause no problems.  However, 
	do not use Paradox to modify the tables in 
	any way;  doing so can cause problems ranging 
	from incorrect behavior to a corrupt database.

Starting Over with a Fresh Database:
	We have provided you with a backup database 
	which can be used to "start over" without 
	having to reinstall LANDesk Response.  The 
	backup database is LDRDB.ZIP.  This file is 
	a PKZIP file which can be unzipped using 
	PKUNZIP.EXE version 1.1 or later.  The 
	LDRDB.ZIP file contains the shared database 
	files.  To start over with a fresh database, 
	delete all files except LDRDB.ZIP from your 
	database directory.  Then use PKUNZIP to 
	uncompress LDRDB.ZIP within the database 
	directory.  You now have an empty database 
	for use with LANDesk Response.

How To Uninstall Intel LANDesk Response:
	To uninstall LANDesk Response, you need to: 
	1) remove the execution directories and their 
	files, 2) remove the database, and 3) decide 
	whether or not to remove the Paradox Engine 
	section in the WIN.INI file.   Step 1 and 2 
	are straightforward.  Just remove the program 
	directory and database directory from the 
	server and all workstations on which it was 
	installed.  (Depending on the installation, 
	the database directory might reside within the 
	program directory.)  Step 3 is influenced by 
	whether or not you have other applications 
	which use Paradox Engine.  If you do not have 
	other Paradox Engine applications, you can 
	delete the section.  If you do have other 
	Paradox Engine applications, you should not 
	delete the section, but verify that the 
	NetNamePath entry does not point to a path 
	which was deleted in steps 1 or 2.


Usage Notes

Limited Actions:
	To avoid corrupting your database, the 
	following should only be performed when no 
	users are logged in to LANDesk Response.  
	(From the Menu Bar, select Admin, 
	User Access, List Login Register to open 
	the Login Register and verify that no users 
	are logged in.  Then select Admin, User Access, 
	Allow User Logins to remove the check mark 
	from in front of the command to disable 
	further logins to LANDesk Response.)

 -	Backing up the database should be performed 
	at least daily and while no users are logged 
	into LANDesk Response.  This ensures the 
	backup will run to completion without sharing 
	violations and that the data backed up is 
	consistent.

 - 	Import of Folders, Persons, and Tickets 
	should only be performed when no users are 
	logged into LANDesk Response.  Export of 
	these can be done at any time.

 -	Configuration changes should only be 
	performed when no users are logged in to 
	LANDesk Response.

RESPONSE.INI Contents:
	The RESPONSE.INI file contains information 
	required by LANDesk Response.  Entries that 
	you can change are "db_path", "priv_path" 
	and "editor".  The "db_path" entry specifies 
	the directory containing the database files 
	to be used by LANDesk Response and LANDesk 
	Response Quick Submit (unless the command-
	line option is used to override the db_path 
	setting), and the "priv_path" entry specifies 
	the directory containing the report 
	templates and temporary database tables.  
	The "editor" entry specifies the executable 
	file of your preferred editor (for use when 
	creating ticket and response descriptions).  
	Example entries are:
		db_path=c:\response\ldrdb
		priv_path=c:\response\ldrpriv
		editor=c:\windows\notepad.exe

Networks Supported:
	LANDesk Response supports and has been tested 
	on Novell NetWare 2.0A or later.  LANDesk 
	Response is based on Borland's Paradox Engine, 
	which supports a number of additional networks.  
	LANDesk Response should work on these networks 
	but it hasn't been tested on them and therefore 
	is not guaranteed to work on them. 
 
	The networks supported by Borland's Paradox 
	Engine are:

- 	IBM Token Ring or PC network with IBM PC 
	Local Area Network Program V1.12 or later

- 	Novell 2.0A or later

- 	3Com 3+ Share network 1.5.1 or later

-	DEC Pathworks 1.0 or later

- 	Microsoft LAN Manager 2.0 or later

- 	Banyan Vines 2.10 or later

- 	ATT SarGROUP for DOS 3.1 or later

- 	Or any other network 100% compatible with 
	above and DOS 3.1 or later

Import/Export:
	When importing, the maximum number of 
	columns the import file can have is 50.  If 
	the import file has more than 50 columns, 
	you will need to reduce the number.

	To add a folder, you must supply a unique 
	FOLDER_ID. You must also supply an existing 
	PARENT_ID.  This PARENT_ID can exist prior 
	to the current record in the CSV import 
	file, or it can exist in the database.  To 
	obtain the current Folder IDs that exist in 
	the database and that can be used as 
	PARENT_ID's, export the folders and 
	check the exported file.

	No notification events are generated while 
	tickets are being imported.

Starting LANDesk Response before 
LANDesk Alert Log:
	If you have LANDesk Manager installed 
	and if LANDesk Response is invoked before 
	LANDesk Alert Log, the notification engine 
	uses the configuration files in the 
	LANDesk Response program directory instead 
	of those in the LANDesk Control Panel 
	program directory.  This can cause unexpected 
	results unless the two sets of configuration 
	files are identical.  If you modify either 
	set of configuration files, be sure to 
	make the identical changes to the other set.


Known Product Problems

Video Cards:
	Not all possible combinations of resolution 
	and palette size are supported.  If you 
	experience difficulties, reduce the palette 
	size first, then try reducing the video 
	resolution.

Queries/Filters:
	When editing an existing query or filter 
	definition, LANDesk Response does not always 
	check your changes as they are made as the 
	program does when you are creating the query 
	or filter definition.  Therefore, use the 
	Query Building Box to directly edit the text 
	of the query or filter definition as 
	described in the online Help topics 
	"Modifying a Filter" or "Modifying a Query." 

	If you change a user's Login ID, or if you 
	change a folder's name, you need to modify 
	all existing queries or filters that refer 
	to the original Login ID or folder name.

Reports:
	In some printing environments, no report 
	header is printed.

	In some printing environments, when you 
	choose Print, a message box says that it 
	is 100% done, but nothing else happens and 
	the message box never goes away.  This can 
	occur with printers which are using  PCL.  
	Try using a printer which is in PostScript 
	mode.

	During the generation of a report, a 
	dialog box displays the number of records 
	read or printed.  This value does not 
	correspond directly to the number of tickets 
	or person records in the report;  rather, it 
	represents the number of records involved 
	with all the tickets or person records in 
	the report.

	Printing error 513:  If printing produces 
	error #513, exit LANDesk Response and 
	restart it.  If this does not correct the 
	problem, try restarting Microsoft Windows.

Charts:
	LANDesk Response's Printer Setup does not 
	effect the printing of charts.  Use 
	Microsoft Window's Printer Setup to effect 
	the printing options of charts.

	When a chart is printed, only part of the 
	printable area of the page is utilized.  If 
	you maximize the Chart window before 
	printing the chart, more of the printable 
	area of the page is used.

	Changes to chart attributes (such as colors 
	or fonts) are not stored as part of the 
	chart definition. They are only temporarily 
	in effect while viewing the chart.

Ticket Views:
	If either the View by Folder or the View by 
	Person window is displaying a sorted ticket 
	list and if one of the tickets is modified 
	in a way that changes it position, the 
	ticket list is not resorted.

	The View by Folder window does not correctly 
	preserve the expansion level of the Folder 
	tree.  For example, if the folder tree is 
	fully expanded with the root folder high-
	lighted and the view is then closed, when 
	it is subsequently redisplayed the folder 
	tree is not expanded.

Increase Max Table ... error:
	If a previous session of LANDesk Response 
	doesn't terminate normally, the Paradox 
	Engine PXENGWIN.DLL file might remain 
	loaded in memory.  If this happens and 
	you attempt to restart LANDesk Response, a 
	message box appears with the message 
	"Increase Max Table ...".

DBPath Invalid Error 99:
	If the database fails to initialize and 
	error 99 is issued, the problem may be the 
	NetNamePath is not accessible.  See the 
	discussion in these release notes for 
	"NetNamePath Issues."

DBPath Inaccessible Error 120:
	If the database fails to initialize and 
	error 120 is issued, the problem may be the 
	NetNamePath is not accessible.  See the 
	discussion in these release notes for 
	"NetNamePath Issues."

Toolbar Error 137:
	This error can occur when the user does 
	not have SHARE.EXE loaded.  See the 
	discussion in these release notes for 
	"SHARE.EXE".


Copyright © Intel Corporation 1993.  All rights 
reserved.

Intel Corporation
5200 N.E. Elam Young Parkway
Hillsboro, Oregon 97124-6497

Intel Corporation assumes no responsibility for 
errors or omissions in this document.  Nor does 
Intel make any commitment to update the 
information contained herein.

TRADEMARKS
The Intel logo is a registered trademark of Intel 
Corporation.
LANDesk is a trademark of Intel Corporation. 
Other brands and trademarks are the property of their
respective owners.

First Edition	October 1993

Part Number 400361-001

