Summary
CrossTec Remote Control and CrossTec SchoolVue Clients have two methods of capturing the Video Output sent to the Clients screen.
1) Hooking into the Installed Video Driver This method provides the best performance and is the most efficient way to view a CrossTec Client. It involves the CrossTec Client hooking into the video driver on the Client machine and sending copies of the video instructions that the Video driver receives to the CrossTec Control, these instructions are used by the Control to display the Clients screen. This method may not display areas of the screen where the applications is bypassing the video driver and displaying to the Clients screen directly.
2) Screen Scrape This method captures the Client screen as if it where a bitmap. Although the data is compressed this method is marginally slower than hooking into the Video Driver and has a greater impact on the Network due to the slightly larger amounts of data being. This method however will provide a accurate representation of the Clients screen where hooking into the Video driver may sometimes fail. Details
In certain circumstances you may be advised by the CrossTec Technical Support Team to set a Client to use screen scrape to overcome a problem with a certain Video Driver.
For CrossTec Remote Control versions 8.1 and later, you can enable screen scrape from the CrossTec Configurator. To do this...
- Open your CrossTec Configurator
- Select the Advanced button and double-click on Master Profile
- Select Remote Control and then View.
- Put a check in the box for Enable Screen Scrape.
- Click OK and restart the Client service.
For versions of CrossTec Remote Control prior to 8.1:
- Find and open the file called Client32.ini, this file is found in the CrossTec Installation folder.
- Open the file in Notepad
- At the bottom of the [Client] section type the following parameter ScreenScrape = 1
- Save and Close this file.
- As the Client32.ini file is a Check summed file you will now have to re-apply the check sum to the file to do this see the following article: Manually editing the Client32.ini file.
|