- Timestamp:
- May 4, 2011 9:43:48 AM (14 years ago)
- Location:
- trunk/doc/manual
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/Makefile.kmk
r36033 r36952 5 5 6 6 # 7 # Copyright (C) 2006-20 07Oracle Corporation7 # Copyright (C) 2006-2011 Oracle Corporation 8 8 # 9 9 # This file is part of VirtualBox Open Source Edition (OSE), as … … 509 509 $(addprefix $(VBOX_PATH_MANUAL_OUTBASE)/$f/,$(VBOX_MANUAL_PNG_FILES_$(f)))) | $$(dir $$@) 510 510 # PDF generation via Latex: generate the .tex file 511 $(call MSG_L1,pdflatex $< ( threepasses) -> $@)511 $(call MSG_L1,pdflatex $< (four passes) -> $@) 512 512 $(QUIET)$(REDIRECT) -w+ti /dev/null -C $(@D) -- $(PDFLATEX) UserManual.tex 513 513 $(QUIET)$(REDIRECT) -w+ti /dev/null -C $(@D) -- $(PDFLATEX) UserManual.tex 514 514 $(QUIET)$(REDIRECT) -w+ti /dev/null -C $(@D) -- $(PDFLATEX) UserManual.tex 515 515 $(QUIET)$(REDIRECT) -w+ti /dev/null -C $(@D) -- $(PDFLATEX) UserManual.tex 516 $(QUIET)$(SED) -n \ 517 -e '/Warning: There were \(undefined references\|multiply-defined labels\)/{p; q 1}' \ 518 $(basename $@).log 519 516 520 ##@todo restore this when above has been converted to INSTALLS target. $(call MSG_L1,Fresh LaTeX-generated PDF is now at $@) 517 521 … … 554 558 $(QUIET)$(REDIRECT) -C $(<D) -- $(PDFLATEX) SDKRef.tex 555 559 $(QUIET)$(REDIRECT) -C $(<D) -- $(PDFLATEX) SDKRef.tex 560 $(QUIET)$(SED) -n \ 561 -e '/Warning: There were \(undefined references\|multiply-defined labels\)/{p; q 1}' \ 562 $(basename $<).log 556 563 $(QUIET)$(CP) $(<D)/SDKRef.pdf $@ 557 564 $(call MSG_L1,Fresh LaTeX-generated PDF is now at $@) -
trunk/doc/manual/en_US/SDKRef.xml
r36457 r36952 1746 1746 1747 1747 <para>As a real-world example of a method invocation, let's call 1748 <xref linkend="I VirtualBox__openRemoteSession"1749 xreflabel="I VirtualBox::openRemoteSession" /> which returns an1748 <xref linkend="IMachine__launchVMProcess" 1749 xreflabel="IMachine::launchVMProcess" /> which returns an 1750 1750 IProgress object. Note again that the method name is 1751 1751 capitalized.</para> … … 1753 1753 <screen>IProgress *progress; 1754 1754 ... 1755 rc = vbox->vtbl-> OpenRemoteSession(1756 vbox,/* this */1755 rc = vbox->vtbl->LaunchVMProcess( 1756 machine, /* this */ 1757 1757 session, /* arg 1 */ 1758 id, /* arg 2 */ 1759 sessionType, /* arg 3 */ 1760 env, /* arg 4 */ 1758 sessionType, /* arg 2 */ 1759 env, /* arg 3 */ 1761 1760 &progress /* Out */ 1762 1761 ); … … 3451 3450 <para>This version introduces the guest facilities concept. A guest 3452 3451 facility either represents a module or feature the guest is running or 3453 offering, which is defined by <xref linke d="AdditionsFacilityType"3452 offering, which is defined by <xref linkend="AdditionsFacilityType" 3454 3453 xreflabel="AdditionsFacilityType"/>. Each facility is member of a 3455 <xref linke d="AdditionsFacilityClass" xreflabel="AdditionsFacilityClass"/>3456 and has a current status indicated by <xref linke d="AdditionsFacilityStatus"3454 <xref linkend="AdditionsFacilityClass" xreflabel="AdditionsFacilityClass"/> 3455 and has a current status indicated by <xref linkend="AdditionsFacilityStatus" 3457 3456 xreflabel="AdditionsFacilityStatus"/>, together with a timestamp (in ms) of 3458 3457 the last status update.</para> … … 3461 3460 <listitem> 3462 3461 <para> 3463 In the <xref linke d="IGuest" xreflabel="IGuest"/> interface, the following were removed:3462 In the <xref linkend="IGuest" xreflabel="IGuest"/> interface, the following were removed: 3464 3463 <itemizedlist> 3465 3464 <listitem> … … 3474 3473 <listitem> 3475 3474 <para> 3476 The function <xref linke d="IGuest__getFacilityStatus" xreflabel="IGuest::getFacilityStatus()"/>3475 The function <xref linkend="IGuest__getFacilityStatus" xreflabel="IGuest::getFacilityStatus()"/> 3477 3476 was added. It quickly provides a facility's status without the need to get the facility 3478 collection with <xref linke d="IGuest__facilities" xreflabel="IGuest::facilities"/>.3477 collection with <xref linkend="IGuest__facilities" xreflabel="IGuest::facilities"/>. 3479 3478 </para> 3480 3479 </listitem> 3481 3480 <listitem> 3482 3481 <para> 3483 The attribute <xref linke d="IGuest__facilities" xreflabel="IGuest::facilities"/>3482 The attribute <xref linkend="IGuest__facilities" xreflabel="IGuest::facilities"/> 3484 3483 was added to provide an easy to access collection of all currently known guest 3485 3484 facilities, that is, it contains all facilies where at least one status update was … … 3489 3488 <listitem> 3490 3489 <para> 3491 The interface <xref linke d="IAdditionsFacility" xreflabel="IAdditionsFacility"/>3490 The interface <xref linkend="IAdditionsFacility" xreflabel="IAdditionsFacility"/> 3492 3491 was added to represent a single facility returned by 3493 <xref linke d="IGuest__facilities" xreflabel="IGuest::facilities"/>.3492 <xref linkend="IGuest__facilities" xreflabel="IGuest::facilities"/>. 3494 3493 </para> 3495 3494 </listitem> 3496 3495 <listitem> 3497 3496 <para> 3498 <xref linke d="AdditionsFacilityStatus" xreflabel="AdditionsFacilityStatus"/>3497 <xref linkend="AdditionsFacilityStatus" xreflabel="AdditionsFacilityStatus"/> 3499 3498 was added to represent a facility's overall status. 3500 3499 </para> … … 3502 3501 <listitem> 3503 3502 <para> 3504 <xref linke d="AdditionsFacilityType" xreflabel="AdditionsFacilityType"/> and3505 <xref linke d="AdditionsFacilityClass" xreflabel="AdditionsFacilityClass"/> were3503 <xref linkend="AdditionsFacilityType" xreflabel="AdditionsFacilityType"/> and 3504 <xref linkend="AdditionsFacilityClass" xreflabel="AdditionsFacilityClass"/> were 3506 3505 added to represent the facility's type and class. 3507 3506 </para> … … 4071 4070 4072 4071 <listitem> 4073 <para>The < xref linkend="IVRDPServer" xreflabel="IVRDPServer" />,4074 < xref linkend="IRemoteDisplayInfo" xreflabel="IRemoteDisplayInfo" />4075 and IConsoleCallback interfaces were changed to reflect VRDP server4076 ability to bind to one of available ports from a list of4077 ports .</para>4072 <para>The <computeroutput>IVRDPServer</computeroutput>, 4073 <computeroutput>IRemoteDisplayInfo"</computeroutput> and 4074 <computeroutput>IConsoleCallback</computeroutput> interfaces were 4075 changed to reflect VRDP server ability to bind to one of available 4076 ports from a list of ports.</para> 4078 4077 4079 4078 <para>The <computeroutput>IVRDPServer::port</computeroutput> 4080 attribute has been replaced with <xref linkend="IVRDPServer__ports"4081 xreflabel="IVRDPServer::ports" />, which is a comma-separated list4082 of ports or ranges of ports.</para>4083 4084 <para>An < xref linkend="IRemoteDisplayInfo__port"4085 xreflabel="IRemoteDisplayInfo::port" /> attribute has been added for4086 querying the actual port VRDP serverlistens on.</para>4079 attribute has been replaced with 4080 <computeroutput>IVRDPServer::ports</computeroutput>, which is a 4081 comma-separated list of ports or ranges of ports.</para> 4082 4083 <para>An <computeroutput>IRemoteDisplayInfo::port"</computeroutput> 4084 attribute has been added for querying the actual port VRDP server 4085 listens on.</para> 4087 4086 4088 4087 <para>An IConsoleCallback::onRemoteDisplayInfoChange() notification -
trunk/doc/manual/en_US/user_Networking.xml
r34606 r36952 63 63 manager. As an exception, the Intel PRO/1000 family adapters are chosen 64 64 for some guest operating system types that no longer ship with drivers for 65 the PCNet card, such as Windows Vista; see <xref 66 linkend="vista_networking" /> for details.<footnote> 67 <para>Support for the Intel PRO/1000 MT Desktop type was added with 68 VirtualBox 1.6. The T Server variant of the Intel PRO/1000 card was 69 added with VirtualBox 1.6.2 because this one is recognized by Windows 70 XP guests without additional driver installation. The MT Server 71 variant was added with VirtualBox 2.2 to facilitate OVF imports from 72 other platforms.</para> 73 </footnote></para> 65 the PCNet card, such as Windows Vista.</para> 66 67 <para>The Intel PRO/1000 MT Desktop type works with Windows Vista and later 68 versions. The T Server variant of the Intel PRO/1000 card is recognized by 69 Windows XP guests without additional driver installation. The MT Server 70 variant facilitates OVF imports from other platforms.</para> 74 71 75 72 <para>The <emphasis role="bold">"Paravirtualized network adapter -
trunk/doc/manual/en_US/user_Security.xml
r36007 r36952 2 2 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" 3 3 "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"> 4 <chapter id=" Troubleshooting">4 <chapter id="Security"> 5 5 <title>Security considerations</title> 6 6 -
trunk/doc/manual/en_US/user_Troubleshooting.xml
r35291 r36952 711 711 Intel E1000 card by default.</para> 712 712 713 <para>If, for some reason, you still want to use the AMD card, 714 VirtualBox ships a 32-bit driver for that card with the Windows Guest 715 Additions; see <xref linkend="vista_networking" />.</para> 713 <para>If, for some reason, you still want to use the AMD card, you need 714 to download the PCNet driver from the AMD website (available for 32-bit 715 Windows only). You can transfer it into the virtual machine using a 716 shared folder, see (see <xref linkend="sharedfolders" />).</para> 716 717 </sect2> 717 718
Note:
See TracChangeset
for help on using the changeset viewer.