Browsers and Monitor resolutions
The following chart outlines support for key features across all major browsers. We designed our software to work with almost any browser released in the last 5-6 years that supports JavaScript 1.2 or above, Cascading Style Sheets (CSS), frames, and cookies.
What "Monitor Resolution Support" means?
Our software detects resolution of client's display and adjusts size of the fonts accordingly, so the application interface looks somewhat more presentable than the default browser settings. We recommend resolutions 1024x768 or higher because most pages contain just too much data to fit on a smaller screen.
Browser\Platform |
Win |
Mac |
Unix |
Linux |
OS/2 |
IE 7.0 |
Y |
- |
- |
- |
- |
IE 6.x |
Y |
- |
- |
- |
- |
IE 5.x |
Y |
U |
- |
- |
- |
IE 4.01 |
- |
- |
U |
- |
- |
IE 4.0 |
P |
U |
- |
- |
- |
IE 3.0, 2.0 |
N |
N |
- |
- |
- |
Mozilla 1.6 |
Y |
U |
U |
Y |
- |
Firefox 1.0+ |
Y |
U |
U |
Y |
- |
NS 7.1 |
Y |
- |
- |
- |
- |
NS 6 |
Y |
- |
- |
- |
- |
NS 4.7/4.5 |
Y |
U |
- |
Y |
- |
NS 4.61 |
- |
- |
Y |
- |
- |
NS 4.06 |
- |
P |
N |
- |
- |
NS 4 |
P |
- |
- |
- |
- |
NS 3.0- |
N |
N |
N |
- |
- |
Opera 4.02 |
P |
- |
- |
- |
- |
Opera 7.23 |
Y* |
- |
- |
- |
- |
Mosaic 3.0, 3.07 |
N |
N |
- |
- |
- |
AOL 8.0 & 9.0 |
Y |
- |
- |
- |
- |
|
Monitor Resolutions |
512x384 |
P |
640x480 |
P |
640x870 |
P |
800x600 |
Y |
832x624 |
Y |
848x480 |
Y |
1024x768 |
Y |
1152x864 |
Y |
1152x870 |
Y |
1280x958 |
Y |
1280x1024 |
Y |
1600x1024 |
Y |
1600x1200 |
Y |
1600x1344 |
Y |
1792x1344 |
Y |
1800x1440 |
Y |
1856x1392 |
Y |
1920x1080 |
Y |
1920x1200 |
Y |
1920x1440 |
Y |
2048x1536 |
Y |
3840x2400 |
Y |
|
Yes-supported |
Partially supported |
Not supported |
Unknown / not tested |
|
Third-party Software Compatibility
Norton AntiVirus and McAfee VirusScan may cause IIS to stops responding producing no error or warning messages.
This problem is caused by Script Blocking feature in Norton AntiVirus and Script Stopper in VirusScan. You can still use these software products to protect your server, but you must disable its Script Stopper/Blocker feature and it must be done in software configuration options since convenient Enable/Disable controls do not completely shutdown these antivirus products.
This problem is fully described here: http://support.microsoft.com/default.aspx?scid=kb;en-us;295375 (Article ID : 295375)
Remember, a single request to an .asp page, which uses FileSystemObject, could be enough to put IIS in unstable state. To recover from this you can use "Unload" button (see Properties -> Application Settings in IIS manager) although subsequent unloads will completely hang IIS process and you will have to reboot your server.
[System Requirements]
|