Calendaring and Scheduling Software
   calendaring and scheduling software scheduling software   support for calendaring and scheduling software Force Accounting FAQs demo calendaring and scheduling software purchase calendaring and scheduling software sitemap for calendaring and scheduling software
CyberScheduler Release 2.1

Release Notes

1. Introduction

This release contains the CyberScheduler 2.1 release for Windows.

2. Installation

The installation procedure for this release is essentially the same as for previous

releases.

Execute the self-extracting installation file from the

directory of your choice, and follow the prompted instructions. The installation

procedure will never overwrite or damage your existing data or configuration.

3. After Installation

After installation of the CyberScheduler component(s), you will need to

do the following things to get up and running:

a. Make sure your CrossWind calendar server is running and you

have set up any necessary user accounts. Help can be found at

http://www.crosswind.com/cybsprt2.htm.

b. During installation, if you chose the option that prevents the CyberScheduler Agent

from starting up automatically, start the CrossWind CyberScheduler Agent from

Control Panel|Services.

c. Users should now be able to access their calendars from their web browsers

4. Open CyberScheduler problems

The following are bugs still open in this release

Bug Number Priority

_______________________________________________________________________________

3236 2-High

Release Note Synopsis: Avoid the browser's reload feature when

submitting a form; duplicate changes to the database can occur.

2924 3-Medium

Release Note Synopsis: MS Internet Explorer 3.02a running under

Windows 3.1 exhibits problems with calendar server passwords. A user

can log in OK, but any attempt to use CyberScheduler after that causes

password error messages.

3212 3-Medium

Release Note Synopsis: Bogus dates can be entered for calendar items

(e.g. Feb. 31) through use of the list boxes and they are not checked.

However, CyberScheduler makes necessary date changes, i.e., April 31

will be translated to May 1.

3243 3-Medium

Release Note Synopsis: If a Synchronize name or a Sync alias has more

than one space in it, one cannot properly select that user's name from

within CyberScheduler (e.g., to include in meetings, to give

permissions to, etc.). Furthermore, other side effects can occur.

3288 3-Medium

Release Note Synopsis: Icons for popup notes created in a remote database

do not show up in the local calendar.

3246 4-Low

Release Note Synopsis: On rare occasion, Netscape Navigator 3.01 will load

CyberScheduler gifs in the wrong order. To fix this when it occurs, merely clear

both the browser's memory and disk cache.

2971 3-Medium

Release Note Synopsis: CyberScheduler hangs when used with Roxen web

server software.

3410 3-Medium

Release Note Synopsis: When in browse or proxy mode, you are sometimes

sent back to your own calendar after a screen redraw.

3399 4-Low

Release Note Synopsis: Printing the monthly calendar, the calendar shows

on page 2 of the print out (Navigator 3 only).

3400 4-Low

Release Note Synopsis: When resizing a dialog window the 'show help,' 'ok,'

and 'cancel' buttons disappear from the display (Navigator 3 only).

3416 4-Low

Release Note Synopsis: Netscape Navigator 4.x appears to hang when attempting

to draw a calendar view or In Box view that has a lot of events, or when the "Show

Busy Time" button is clicked. Given a little time, the page will finally draw.

3411 4-Low

Release Note Synopsis: The "Show Busy Time" grid starts on Sunday for users

with a Monday start of week.

Total count = 12

ADDENDUM TO RELEASE NOTES

Problem:

I get "file is in use" or "access denied" messages whenever I try to access or delete a file associated with CyberScheduler (e.g. dat.perm, userinfo, temporary installation files)

It has been observed that some files present in the directories accessed during the installation of CyberScheduler have occasionally ended up having their permissions changed to "System" only. If this happens they are no longer access able to any users; even those with Administration privileges. This is usually associated with an installation that has been abnormally aborted, but has been seen even with successful installations. The files can be restored to their original permissions through the Windows Explorer program.

Solution:

Log in as an administrator and open Windows Explorer. Highlight the offending file, and then from the "Files" menu, select "Properties". A dialog box will appear. Select the Security tab and click the "permissions" button. Another dialog box will appear with a list of the current permissions. Click the "Add" button and add whatever groups that you wish to have access privileges to the files you have chosen. Then under "Types of Access" select the access level you want to give them. Select "OK" and the files should be accessible once again.





BACK