Welcome to SFU.ca.
You have reached this page because we have detected you have a browser that is not supported by our web site and its stylesheets. We are happy to bring you here a text version of the SFU site. It offers you all the site's links and info, but without the graphics.
You may be able to update your browser and take advantage of the full graphical website. This could be done FREE at one of the following links, depending on your computer and operating system.
Or you may simply continue with the text version.

*Windows:*
FireFox (Recommended) http://www.mozilla.com/en-US/firefox/
Netscape http://browser.netscape.com
Opera http://www.opera.com/

*Macintosh OSX:*
FireFox (Recommended) http://www.mozilla.com/en-US/firefox/
Netscape http://browser.netscape.com
Opera http://www.opera.com/

*Macintosh OS 8.5-9.22:*
The only currently supported browser that we know of is iCAB. This is a free browser to download and try, but there is a cost to purchase it.
http://www.icab.de/index.html

WebCT news at SFU

navigating SFU’s learning management system

« Spring 2008 notice
Section numbers now in WebCT Grade Book »

WebCT slow-down

WebCT has been slow for many this Friday, January 4th, 2008. Currently, the WebCT administrators at SFU are aware of this, and are working on allocating more memory for WebCT. They will also do some maintenance on the weekend that will improve performance. In the meantime, your best option is to try and logout and login again, or to wait until Sunday.

This entry was posted on Friday, January 4th, 2008 at 3:33 pm and is filed under SFU communications, known issues/ bugs, General. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

One Response to “WebCT slow-down”

  1. Logout And Login Again Or Just Stay Away? : Rants, Raves, and Rhetoric v4 Says:
    January 5th, 2008 at 9:56 pm

    […] Poor Simon Frasier. I am curious about the advice to logout and login. With our slow down a year ago, it was exactly the users doing this which worsened the issue. Our issue was partially with a script located on the page users reached immediately after login. […]

Leave a Reply

You must be logged in to post a comment.