Skip to main content

FAQs

  • Updated

FAQs

These pages provide answers to frequently-asked and entry-level technical support questions.

System Requirements, Installation, and Licensing

  1. What Windows OS versions are supported?
  2. Are there 64-bit versions of your products?
  3. What are the licensing ramifications of using server virtualization?
  4. Will a Logi application run in a shared hosting environment?
  5. Can I use Logi products with .NET 3.x or 4.0?
  6. Do you have versions of your products that will run on Linux with the Apache web server?
  7. When I register my application, its virtual directory is created on IIS under an "OWA" web site. Why is this?
  8. Should I install Logi Server on the same web server I use for Outlook Web Access (OWA)?
  9. How are your products delivered after someone purchases them?
  10. Will your products work via a Citrix server?
  11. Will your products work with Microsoft SQL Server?
  12. I received this error message: Thread was being aborted
  13. Can I move my Logi v10 or v11 product to a different computer?
  14. It appears I need a copy of the Logi license file in every Logi app folder. Is a centralized file possible instead?


1. What Windows OS versions are supported?
Supported Windows OS versions include:

  • Windows Server 2012 R2, 2008, and 2003
  • Windows 8 (all editions except RT)
  • Windows 7 (all editions)
  • Windows Vista (Business, Enterprise, and Ultimate editions only)
  • Windows XP Pro

2. Are there 64-bit versions of your products?
Yes. We have 64-bit versions for all of our products, for use in both .NET and Java environments.

3. What are the licensing ramifications of using server virtualization?
Please see the Server Virtualization section of Product Licensing.

4. Will a Logi application run in a shared hosting environment?
Logi applications require a High Trust Level to run. Most hosting centers insist on Low or Medium Trust levels on shared web servers for security purposes. However, if the hosting center offers a dedicated server or virtualized server, they may allow a High Trust Level and Logi applications can then be used.

5. Can I use Logi products with .NET 3.x or .NET 4.0?
Yes. Logi products for the Windows environment, and Logi Studio, require the .NET Framework. Prior to v11.0.127, .NET v2.0 or 3.x was required; for v11.0.127 and later, .NET 4.x is required. If not already in place, with your consent, appropriate versions of the .NET framework are installed when Logi products are installed. They are also available for free from the Microsoft Download Center.

6. Do you have a version of your products that will run on Linux with the Apache web server?
Yes. Both Logi Report and Logi Info can create web applications that use Sun JDK 1.6, 1.7, or 1.8 or Oracle JRockit instead of .NET and run under Linux or other UNIX derivatives, on Apache and other open source web servers. For more information, see Introduction to Logi Reporting with Java.

7. When I register my application, its virtual directory is created on IIS under an "OWA" web site. Why is this?
By default, IIS is installed with a "Default Web Site" configured, which has an ID of #1. The Logi tools register applications (create their virtual directories) under the web site with ID #1. If your Default Web Site is missing and virtual directories are being created under "OWA" (which stands for Outlook Web Access and is used for remote email access) your IIS configuration has been highly customized. You need to get a trained IIS administrator involved in order to configure this server for use with Logi apps.

8. Should I install Logi Server on the same web server I use for Outlook Web Access (OWA)?
No. Microsoft recommends that, for reasons of security, performance, and scalability, you do not run other web sites or web applications on your OWA web server platform.

9. How are your products delivered after someone purchases them?
Product delivery is via download from our web site; documentation is available on this web site. We do not distribute our products on CDs or DVDs.

10. Will your products work via a Citrix server?
Yes. Logi applications, as web applications, can be served and browsed in a Citrix environment without any problem. Our Studio development tool, as a standard Windows client application, needs to be installed and published as a Citrix application. As is the case with many apps published this way, its performance will be a little less snappy than it would be if it was installed and run from a user's local machine.

11. Will your products work with Microsoft SQL Server?
Yes. Our products have been tested with and work with all versions of MS SQL Server, starting with SQL Server 2000.

12. I received this error message: Thread was being aborted
Depending on the availability of system resources, the IIS worker process may not have been able to acquire enough memory to process the request and recycled. If your web server is IIS 6, you may want to investigate how its Application Pools are being used. If you have a large number of web applications all using the Default Application Pool, you may want to isolate some, or all of them, in separate app pools.

13. Can I move my Logi v10 or v11 product to a different computer?
Yes, the Logi v10 and v11 licensing scheme allows you to visit the License Management page on DevNet and reassign your license to a different machine. You then generate a new license file and install it along with the product on the new machine. You do not need to contact Customer Service to accomplish any of this.

14. It appears I need a copy of the Logi license file in every Logi app folder. Is a centralized file possible instead?
Yes, instead of distributing and maintaining many license files on a single computer, you place a one copy of the license file in a central location. In each Logi application, you modify the _Settings definition, configuring the General element's License File Location attribute to point the folder containing the license file. The account the web server uses to run your apps must have access permissions to that license file folder.

Application Configuration and Settings

  1. In Studio, the Application page shows a "Warning: Version Mismatch" message. What does this mean?
  2. How do I turn on debugging?
  3. How can I use switch between VBScript and JavaScript?
  4. Is there some way to assign a style sheet to an entire Logi application?
  5. I'd like to create a mailto: link in several reports. Is there a way to define the email address as a constant?
  6. What happens when you "register this application" using the Studio wizard?
  7. How can I browse my report from within Studio? Whenever I try to do it, the Default report is displayed.
  8. I noticed the Team Development element in _Settings. What does that do?
  9. Is it possible to use Logi report definitions that are stored in a database table?
  10. When I ran my report I received an "Access denied" error message.
  11. Can I configure my Logi application's document type declaration (doctype)?


1. In Studio, the Application page shows a "Warning: Version Mismatch" message. What does this mean?
This warning means that the application was created with a version of the Logi product that is older than the version of Studio currently installed on your computer. As a result, some application features available in the newer product may not be available. To upgrade your application to a different Logi product version, click the Change Version... link on Studio's Application page, or use the Server Manager utility, available on the Studio Tools menu. For more information, see Upgrade Logi Products and Apps.

2. How do I turn on debugging?
You can turn on debugging in Logi Studio for all your report definitions by clicking the Debug icon on the menu or toolbar and selecting DebuggerLinks from the selection list. Clicking the icon sets an attribute value in the _Settings definition, General element, and you can also turn debugging on by setting that value directly.

3. How can I switch between JavaScript and VBScript?
Support for VBScript has been deprecated - it continues to be supported but JavaScript is the recommended scripting language. Prior to release 10.0.101, VBScript was the default scripting language for a Logi application when creating a .NET app; after it, JavaScript became the default. The choice of scripting language is set in the _Settings definition, using the General element's Scripting Language attribute. When creating a Logi app for Java, JavaScript is the only scripting language choice.

4. Is there some way to assign a style sheet to an entire Logi application?
Yes. If you prefer to do that, rather than assign style sheets in each individual report definition, you can do so in the _Settings definition. Just add a Global Style element and assign the style sheet file to it, and it will then apply to every report definition.

5. I'd like to create a mailto: link in several reports. Is there a way to define the email address as a constant?
Yes. Constants can be defined in the _Settings definition and referred to from report definitions. This allows the value of the constant, in your case the email address, to change, if necessary, without requiring a change in every report definition. Constants are referred to using the @Constant token.

6. What happens when you "register this application" using the Studio wizard?
When using IIS as your web server, the registration wizard creates an IIS Virtual Directory for your web application. You must be logged-in with an account that has administrator privileges in order for the wizard to create and configure IIS virtual directories. You can also do this manually, if you prefer, using the IIS Management tool provided with Windows.

7. How can I browse my report from within Studio? Whenever I try to do it, the Default report is displayed.
In the _Settings definition, the Application element has an attribute that selects which report is considered the "default" report and is displayed when you select Browse from Studio's toolbar. You can quickly change this selection by selecting and right-clicking a report definition in Studio's Application panel, then selecting "Set As Default" from the pop-up menu that appears. You can also browse any individual report definition by selecting and right-clicking it and selecting "Run in Browser".

8. I noticed the Team Development element in _Settings. What does that do?
Team Development is a simple source code control system. It was designed to be used in an environment where there are multiple developers working on the same application and it's useful to control access to definitions and support files. When Team Development is enabled, application files are locked and developers must check them in and out to work on them. This prevents overlapping editing of the same file and creates an audit trail of who worked on which files. File History can also be enabled so that revisions can be rolled-back and undone.

9. Is it possible to use Logi report definitions that are stored in a database table?
Yes. Logi report definitions are XML files and these can be stored in a table column. The External Definitions element can be used in the _Settings definition with a datalayer element to retrieve the stored report definitions and make them available to the application. See this blog, Think Outside the Box with External Definitions, for more information.

10. When I ran my report I received an "Access denied" error message.
In order to allow the account used by the web server to run Logi applications to write temporary cache files to the server's hard drive, you must give it permissions to do so. This is described in detail in Grant File Access Permissions.

11. Can I configure my Logi application's document type declaration (doctype)?
Yes, the _Settings definition's General element includes a Doctype Declaration attribute, that can be set to Html5, Xhtml Strict, Xhtml Transitional, Xhtml Frameset, or None. If left blank, the default is Html5.

Work with Data

  1. In Studio, when adding data table rows, do I have to add a datalayer for each row?
  2. Can I run a Stored Procedure? The DataLayer.SQL element only seems to accept SQL statements.
  3. My SQL query is returning DateTime values in this format "2008-08-07T14:20Z". How can I work with this?
  4. Do Logi products support the MS SQL Server 2005 XML data type? Can you search within the XML data?
  5. What formats can you export reports and/or data to?
  6. Do Logi products work with BLOBs stored in table columns?
  7. Do Logi products support the MEDIAN function?
  8. How can I parse the parts of date and time data values?
  9. Is there some way to get a list of the report definitions within a Logi application, as data?
  10. How can I create simple options for use with Input Select Lists? I don't want to build a table for only three options.
  11. My table contains dates entered as text, but I want to be able to sort by date in my Logi report. How can I do this?


1. In Studio, when adding data table rows, do I have to add a datalayer for each row ?
No. A datalayer, for example, that issues a SQL query will contain all of the rows and columns that were returned in the result set. Your report definition needs to contain data table column and label elements for each column you wish to display. When the report is browsed, the server will iterate through and display all rows in the datalayer automatically. See Data Table Tutorial - Manual for an example of how to create a definition that does this.

2. Can I run a Stored Procedure? The DataLayer.SQL element only seems to accept SQL statements.
In general, Stored Procedures should be run using the DataLayer.SP or Procedure.SP elements. Input and output parameters can then be used with stored procedures using the SP Parameters element.

3. My SQL query is returning DateTime values in this format "2008-08-07T14:20Z". How can I work with this?
DateTime-type data returned into a data layer by a query against a SQL data source is usually in ISO 8601 format. If you wish to use script functions to compare, manipulate, or format the date data, you need to convert it into a compatible format. Logi's intrinsic CXMLDate function has been provided for this purpose. See Special Functions and Attributes. We also offer the Time Period Columns element, which makes it easy to parse data, such as hours or months, from this format.

4. Do Logi products support the MS SQL Server 2005 XML data type? Can you search within the XML data?
Yes. Our products support any valid SQL statement, so queries that utilize XQuery functions and XPath expressions, used to search in and work with XML data in XML data type columns, are supported.

5. What formats can you export reports and/or data to?
Logi Info, Logi Report, and Logi Ad Hoc can export to .pdf, .csv, .xml, .xls/xlsx, and .doc/.docx files. In addition, Logi Info and Report can insert data into predefined PDF, Word, and Excel templates.

6. Do Logi products work with BLOBs stored in table columns?
Yes. The File Column element allows BLOBs and CLOBs stored in table columns to be retrieved and used. For more information, see The File Column.

7. Do Logi products support the MEDIAN function?
Once data has been retrieved from a datasource it can be manipulated using a the Aggregate Column element, which supports Average, Concat, Count, Distinct Count, Maximum, Median, Minimum, Mode, Standard Deviation, and Sum functions.

In prior versions, aggregations included columns with Null values by default. This behavior has been changed and Null values are now excluded by default. Create the constant rdCalculationsIncludeNulls and set it to True if you want to restore the old behavior.

8. How can I parse the parts of date and time data values?
Once data has been retrieved from a datasource it can be parsed using the Time Period Column element. This element will add a column to the datalayer that can contain parts of a DateTime value, such as: Year, Quarter, Month, MonthAbbreviation, MonthName, DayOfYear, DayOfMonth, DayOfWeek, DayOfWeekAbbreviation, DayOfWeekName, Hour, Minute, Second, and many more. For more information, see Time Period Columns.

9. Is there some way to get a list of the report definitions within a Logi application, as data?
Yes, the DataLayer.Definition List element will produce, as rows and columns, information about the properties of each report, process, widget, and template definition in the application. This data can then be used like any other data, for example, in reports, menus, and selection lists. For more information, see DataLayer.Definition List.

10. How can I create simple options for use with Input Select Lists? I don't want to build a table for three options.
There are two easy ways to do this. First, you can use a DataLayer.Static element beneath your Input Select List, then add one child Static Data Row element for each list option. Second, a slightly more flexible approach is to create a simple XML data file that contains your options and then use a DataLayer.XML File element beneath your Input Select List. This has the advantage that the options can be easily edited or expanded with having to run Studio and change the application.

11. My table contains dates entered as text, but I want to be able to sort by date. How can I do this?
Retrieve your data into a datalayer element, then add a Calculated Column element beneath it. In the Calculated Column element's Formula attribute use the Logi intrinsic CDATE( ) function to add a column to the datalayer that contains your text dates converted to proper DateTime data. The calculated column can appear in the data table in your report with a header link for sorting by date.

Report Design

  1. Why would I use Layout Positioning instead of Flow Positioning?
  2. I generated my first report in Studio using the New Application Wizard. Now how do I add a second report?
  3. Can end users create, generate, design, format and customize reports by themselves?
  4. Can Logi reporting products open/use Crystal Reports .rpt files?
  5. Can I include data entry fields in my report? Can I "write back" (update) my database using them?
  6. Is there some way to include common report parts, like headers and footers, from a single source?
  7. How can I hide certain sections of reports based on dynamic criteria, such as data values or a user profile?
  8. Some of my chart Labels are very long, requiring a big chart bottom border I don't want. What can I do?
  9. Can I have multiple Analysis Grids in my report definition?
  10. Does a user have to login to Logi Ad Hoc to use and create reports?
  11. Is there a way in Logi Info to format numbers using metric notation, such as 10K?
  12. It would be great if a chart legend could be clicked to show/hide different data series. Is that possible?


1. Why would I use Layout Positioning instead of Flow Positioning?
Layout Positioning allows you to place elements in absolute positions on the screen. However, the default Flow Positioning, which bases each element's location on that of previous elements, produces fewer browser and device compatibility issues. We don't generally recommend use of Layout positioning. Important Note: If you convert a report definition from Flow Positioning to Layout Positioning and then switch back, your report may not be perfectly converted back to its original state. This is due to certain attributes that Layout Positioning inserts, which become ambiguous in the reverse conversion.

2. I generated my first report in Studio using the New Application Wizard. Now how do I add a second report?
One Logi application can contain many report definitions. The New Application Wizard created both your Logi application and your first report definition. To add additional report definitions to your application, on the main menu click New File Report.

3. Can end users create, generate, design, format and customize reports by themselves?
Yes, using two methods. First, if you develop a report using Logi Info and include a "super element", such as the Analysis Grid (see Work with Analysis Grids), end users can significantly customize the report at runtime. Second, we also offer a product called Logi Ad Hoc that is a wizard-driven tool that allows users to create their own reports without any developer assistance.

4. Can Logi reporting products open/use Crystal Reports .rpt files?
No. Crystal Reports .rpt files are proprietary, binary files and completely unlike the simple XML text files used by Logi reporting products.

5. Can I include data entry fields in my report? Can I "write back" (update) my database using them?
Logi Info and Logi Report support HTML forms and standard user input controls, including text boxes, text areas, checkboxes, radio buttons, and selection lists. Data entered or selected by the user can be used to dynamically change reporting criteria and can also be used to insert new records or update existing records in database tables. Logi Info includes features (Process tasks), which Logi Report does not, that make this very easy.

6. Is there some way to include common report parts, like headers and footers, from a single source?
Yes. Logi products include a feature called "Shared Elements" which allows you to establish a set of elements, such as a report header with logo and date, as "shared". These can then referenced in all report definitions in an application. Any subsequent changes made to the single instance of the shared elements will then ripple through to appear in all reports that use them. For more information, see Shared Elements.

7. How can I hide certain sections of reports based on dynamic criteria, such as data values or a user profile?
One approach is to use the Division element, which acts as a "parent" container for parts of reports, and controls their visibility. For more information, see Work with Conditions.

8. Some of my chart Labels are very long, requiring a big chart bottom border I don't want. What can I do?
Our charts include a Max Label Length attribute that specifies the maximum number of characters that will be displayed for a label before the text is trimmed and the remainder replaced with an ellipsis (...).

9. Can I have multiple Analysis Grids in my report definition?
No, you can only have one "super-element", such as an Analysis Grid, per report definition. This is because of internal identifiers within the super-elements, which would cause confusion if multiple elements were allowed. You can, however, place Analysis Grids on several report definitions and then include them, as SubReports in IncludeFrame mode, in a single master definition.

10. Does a user have to login to Logi Ad Hoc to use and create reports?
Yes, Logi Ad Hoc is a web application and users do generally need to login to it in order to use it. Ad Hoc security is fully configurable, however, from none to fully-integrated with external security schemes.

11. Is there a way in Logi Info to format numbers using metric notation, such as 10K?
Yes. Starting in v10.2.424, the options available in Format attributes include "mp", which stands for Metric Prefix and which will automatically truncate numeric values and append appropriate characters, such as "K" or "M". For more information, see Format Data.

12. It would be great if a chart legend could be clicked to show/hide different data series. Is that possible?
Yes. In Logi Info and Logi Report v11, a new feature called "legend filtering" was introduced. It allows the user, at runtime, to click entries in the legend, toggling the inclusion of data in the chart, which is immediately redrawn. The feature is enabled using the Legend element's Legend Filter attribute, and applies to static Pie, Line, Area, Bar, Scatter, and Polar charts, and is automatically enabled in v11.2.040 in Chart Canvas charts.

Work with Support Files

  1. I tried to add an Excel template to my application and received an "Access denied" error message.
  2. I tried to save data in an XML data file and received an "Access denied" error message.
  3. Where did the files I saved in rdDownload go? They've been deleted.
  4. What kinds of image files can I use with Logi applications?
  5. Can #ID type class definitions be used in style sheets with Logi applications?
  6. Can external HTML files be embedded within Logi reports?
  7. Does Logi Studio include some kind of style sheet editor or do I need to get one of my own?
  8. How can I organize my support files in the _SupportFiles folder into sub-folders?
  9. Can I use URLs or tokens to refer to external images with the Image element?
  10. What happened to the _Images folder? I don't see it anymore in new applications.
  11. How can I organize files within the _SupportFiles folder?


1. I tried to add an Excel template to my application and received an "Access denied" error message.
This can occur if you still have the template file open in Excel while trying to add it to your application's Support Files. Close the file in Excel before trying to add it to your project.

2. I tried to save data in an XML data file and received an "Access denied" error message.
In order to allow the account used by the web server to run Logi applications to write to the server's hard drive, you must give it permission to do so. This is described in detail in Grant File Access Permissions.

3. Where did the files I saved in rdDownload go? They've been deleted.
Two folders, rdDataCache and rdDownload, in your Logi application folder are used by the server engine to store temporary files. Any files in these folders are automatically "cleaned up" (deleted) periodically. If you want to write data out to files or export reports and retain them, we recommend you create a new folder in the application folder and place them there.

4. What kinds of image files can I use with Logi applications?
Logi apps will work with image files in these formats: .gif, .jpg, .jpeg, .png, .bmp, .wmf, .xbm, .art

5. Can #ID type class definitions be used in style sheets with Logi applications?
Yes. For complete information about the class definitions that can be used with Logi apps, see Use Style Sheets.

6. Can external HTML files be embedded within Logi reports?
Yes. The Include HTML and HTML File elements can be used to embed HTML code and external HTML files, respectively, into Logi reports. For more information, see Insert HTML Into Reports.

7. Does Logi Studio include some kind of style sheet editor or do I need to get one of my own?
Logi Studio provides two ways to edit styles sheets. It includes a content-specific, internal style sheet editor, which opens in a tab inside the Studio Workspace panel, and the Class Selector tool which allows class editing and previewing within Studio. Menu options within Studio can also launch whatever external CSS editor you may own that's associated with the .css file extension.

8. How can I organize my support files in the _SupportFiles folder into sub-folders?
If you create a new sub-folder, such as "images", under Support Files in Studio's Application panel, and give your support files names that begin with the sub-folder name, such as "images.logo.png", they will appear in Studio's Application panel organized into virtual sub-folders, for example, as "logo.png" beneath the "images" folder. You can also drag files into the folders and have Studio rename them automatically (see #11 below).

9. Can I use URLs or tokens to refer to external images with the Image element?
Yes. Generally, if you just supply a file name in the Image element's Caption attribute, it assumes your image file to be in the _SupportFiles folders. If you supply a complete URL ("http://somesite/myImage.gif") instead, this assumption is overridden. However, using a token in the Caption to supply a URL can be problematic, due to the timing of token evaluation. The solution is to force the Caption to be considered as a URL, by entering "http://" and then the token, like this: "http://@Data.myURLToken~". Naturally, your token must not contain the (now redundant) "http://" itself.

10. What happened to the _Images folder? I don't see it anymore in new applications.
After the release of Logi Info and Logi Report v9.2.76, files formerly stored in individual folders named _Images, _Stylesheets, _IncHtmls, _DataXMLs, and _Scripts were consolidated into the _SupportFiles folder, with backward compatibility provided (as long as file paths are not specified using tokens).

11. How can I organize files within the _SupportFiles folder?
Files can be organized within the _SupportFiles folder by adding sub-folders from withinStudio's Application panel (right-click the SupportFiles folder) and dragging files into them. This automatically adds a prefix to the file name. For example, if you created a sub-folder in Studio called "images", a file named "myLogo.png" dragged into it would be renamed "images.myLogo.png". Note that using external OS file system tools to create a sub-folder under _Support files will not work correctly; the sub-folder must be created within Studio. After that, you can add files to _SupportFiles externally, manually including the prefix in the name, if desired. When working with these organized files you must provide the complete file name; for example, an Image element's Caption attribute value would be "images.myLogo.png".

Other

  1. Is it possible to schedule Logi reports to run and be distributed on a regular basis?
  2. How can I continue to manage older reports that are scheduled through the Windows Task Scheduler?
  3. Can I store the schedules that the Logi Scheduler uses in a SQL database?
  4. Can I use more than one instance of the Logi Scheduler, in a clustered-server set up?
  5. Is there some way to find out at runtime what the file system path is to my application on the web server?
  6. Is there some way to find out at runtime what the URL of my application is?


1. Is it possible to schedule Logi reports to run and be distributed on a regular basis?
Yes. Logi products include the Logi Scheduler, a special Windows service or daemon, that manages and executes scheduled events (as of release 9.5 our products no longer use the Windows Task Scheduler). For more information, see Introduction to Logi Scheduler.

2. How can I continue to manage older reports that are scheduled through the Windows Task Scheduler?
Prior to release 9.5, scheduled reports were managed using the Logi Server Manager as an interface for the Windows Task Scheduler. The Server Manager no longer includes this ability and reports are scheduled using the Logi Scheduler, but you can run the Windows Task Scheduler from the Windows Start Menu and still manage older scheduled tasks.

3. Can I store the schedules that the Logi Scheduler uses in a SQL database?
Yes. Beginning in v11, it's possible to configure the Logi Scheduler to use a MySQL, Oracle, or MS SQL Server database to store scheduled task data, rather than using the default embedded database files. This is discussed in detail in Introduction to Logi Scheduler.

4. Can I use more than one instance of the Logi Scheduler, for example, in a clustered-server set up?
Yes. Beginning in v11, and if you're storing scheduled task data in one of the supported database servers (see #3 above), you can configured multiple Logi Scheduler instances on different servers, creating a fault-tolerant arrangement.

5. Is there some way to find out at runtime what the file system path is to my application on the web server?
Yes. The @Function.AppPhysicalPath~ token will provide a fully-qualified path that includes your application folder. You can use this token as part of a file path to other folders within your application for exports, data, etc. For more information, see Token Reference.

6. Is there some way to find out at runtime what the URL of my application is?
Yes. One approach is to add a Session variable in your application's Global.asax or rdPage.aspx file, using the following code:

<% Session("webpath") = Request.ServerVariables("URL") %>

then reference it in your report as @Session.webpath~, and another is to add this to a Label formatted as HTML:

<*script*> document.write(document.location.href); <*/script*>

(remove the asterisks which were added here to prevent the example from being interpreted as script in this document).

keywords: 64bit

Related articles