Those familiar with the Microsoft browser capability component and browscap.ini will recognize the same format for the call you make from your ASP script in order to create the BrowserHawk object for your use. This is because BrowserHawk is 100% backward compatible with browscap which makes the migration path for those converting to BrowserHawk very simple.
The ActiveX version of BrowserHawk is recommended for use with Classic ASP.
Using the BrowserHawk ActiveX component from ASP:
<% set bhObj = Server.CreateObject("cyScape.browserObj")
if bhObj.frames = False then
response.redirect "/noframes_site.asp"
end if %>
<HTML> ... load frameset here ... </HTML>
For additional code snippets that demonstrate how to use the ActiveX version of BrowserHawk from classic ASP pages, see any of the properties in the ActiveX Property Reference Guide, such as Browser, Platform, JavaScriptEnabled, and Plugin_Flash.