Kenwood HP 9000 manuals

Computer Equipment > Personal Computer

When we buy new device such as Kenwood HP 9000 we often through away most of the documentation but the warranty. Very often issues with Kenwood HP 9000 begin only after the warranty period ends and you may want to find how to repair it or just do some service work. Even oftener it is hard to remember what does each function in Personal Computer Kenwood HP 9000 is responsible for and what options to choose for expected result. Fortunately you can find all manuals for Personal Computer on our side using links below.

Kenwood HP 9000 Manual

Kenwood HP 9000 Manual

333 pages633.85 Kb

2Legal Notices
15Preface
- Printing History
191 What's New in Recent Releases
- 21PA-RISC Changes in Hardware Compatibility
  - PA-RISC 2.0 Compatibility
  - 22PA-RISC Architectures and Their System Models
- 2364-bit Mode Linker Toolset Compatibility with De Facto Industry Standards
- 2464-bit Mode ELF Object File Format
- 25New Features for 64-bit Mode Linking
  - 64-bit Mode Linker Options
  - 2664-bit Mode Linker-dened Symbols
- 2864-bit Mode Link-time Differences
- 3064-bit Mode Run Time Differences
- 32Changes in Future Releases
- 33Online Help for Linker and Libraries
  - Accessing Help with ld +help
  - Accessing Help with the HP CDE Front Panel
  - Accessing Help with the dthelpview Command
  - Accessing Help with the charhelp Command
352 What Happens When You Compile and Link a Program
- 36Compiling Programs on HP-UX: An Example
- 38Looking inside a Compiler
- 40What is an Object File?
  - Local Denitions
  - Global Denitions
  - External References
- 41Compiler-Linker Interaction
- 42Linking Programs on HP-UX
  - 43The crt0.o Startup File
    - The Program's Entry Point
  - 44The a.out File
    - Magic Numbers
  - 45File Permissions
- 46Linking with Libraries
  - Library Naming Conventions
  - Default Libraries
  - 47The Default Library Search Path
  - Link Order
- 48Running the Program
  - Loading Programs: exec
  - Binding Routines to a Program
  - 49Deferred Binding is the Default
- 50Linker Thread-Safe Features
513 Linker Tasks
- 53Using the Compiler to Link
  - Changing the Default Library Search Path with -Wl, -L
    - Example Using -Wl, -L
  - 54Getting Verbose Output with -v
  - Passing Linker Options from the Compiler Command with -Wl
    - Example Using -Wl
  - 55Renaming the Output File with -o
  - Specifying Libraries with -l
    - Linking with the crt0.o Startup File in 32-bit mode
  - Suppressing the Link-Edit Phase with -c
- 57Using Linker commands
  - Linking with the 32-bit crt0.o Startup File
  - Changing the Default Library Search Path with -L and LPATH
    - Overriding the Default Linker Search Path with LPATH
    - Augmenting the Default Linker Search Path with -L
  - 58Changing the Default Shared Library Binding with -B
    - Example Using -B immediate
    - 59Nonfatal Shared Library Binding with -B nonfatal
    - Restricted Shared Library Binding with -B restricted
  - 60Improving Shared Library Performance with -B symbolic
    - Example Using -B symbolic
    - 61Comparing -B symbolic with -h and +e
      - Case 1: Building a Shared Library with -B symbolic.
  - 63Choosing Archive or Shared Libraries with -a
    - 64Example Using -a
  - 65Dynamic Linking with -A and -R
    - Overview of Dynamic Linking
      - 66Step 1: Determine how much space is required to load the module.
      - Step 2: Allocate the required memory and obtain its starting address.
      - Step 3: Link the module from the running application.
      - Step 4: Get information about the module's text, data, and bss segments from the module's header.
      - 67Step 5: Read the text and data into the allocated space.
      - Step 6: Clear (zero out) the bss segment.
      - Step 7: Flush the text from the data cache before executing code from the loaded module.
      - Step 8: Get the addresses of routines and data that are referenced in the module.
    - 68An Example Program
      - 69The Build Environment.
      - 70Source for dynprog.
        Chapter 3 71
      - 71le1.o and le2.o .
      - 72Output of dynprog .
      - dynload.c .
      - The alloc_load_space Function .
        74 Chapter 3
      - 74The dyn_load Function .
        78 Chapter 3
      - 78The ush_cache Function .
  - 79Exporting Symbols with +e
    - Example Using +e
    - 80When to use -h versus +e
  - 81Exporting Symbols with +ee
  - Exporting Symbols from main with -E
  - Hiding Symbols with -h
    - Example Using -h
    - 82Tips on Using -h
    - Hiding and Exporting Symbols When Building a
    - 83Hiding Symbols When Combining .o Files with the -r Option
    - Hiding and Exporting Symbols When Creating an a.out File
  - 84Moving Libraries after Linking with +b
    - 85Specifying a Path List with +b
    - The Path List
  - 86Moving Libraries After Linking with +s and SHLIB_PATH
    - Specifying a Path List with +s and SHLIB_PATH
    - For More Information:
  - Passing Linker Options in a le with -c
  - 87Passing Linker Options with LDOPTS
  - Specifying Libraries with -l and l:
    - Specifying Libraries (-l)
    - 88Using the -l: option
    - Example Using -l:
  - 89Stripping Symbol Table Information from the Output File with -s and -x
- 90Using 64-bit Mode Linker Options
  - Using the 64-bit Mode Linker with +compat or +std
    - Using the Linker with +compat for Compatibility Mode
    - 91Using the 64-bit Linker with +std for Standard Mode
  - 93Linking Shared Libraries with -dynamic
  - Linking Archived Libraries with -noshared
  - Controlling Archive Library Loading with +[no]forceload
  - 94Flagging Unsatised Symbols with +[no]allowunsats
  - 95Hiding Symbols from export with +hideallsymbols
  - Changing Maples with -k and +nodefaultmap
  - 96Ignoring Dynamic Path Environment Variables with +noenvvar
  - Linking in 64-bit Mode with +std
  - Linking in 32-bit Mode Style with +compat
  - Controlling Output from the Unwind Table with +stripwind
  - 97Selecting Verbose Output with +vtype
  - 98Linking with the 64-bit crt0.o Startup File
- 99Linker Compatibility Warnings
  - 100Linking to Archive Libraries with Unsatised Symbols
1034 Linker Tools
1215 Creating and Using Libraries
- 122Overview of Shared and Archive Libraries
- 125What are Archive Libraries?
  - Example
- 126What are Shared Libraries?
  - The Dynamic Loader dld.sl
  - 127Default Behavior When Searching for Libraries at Run Time
  - Caution on Using Dynamic Library Searching
- 128Example Program Comparing Shared and Archive Libraries
- 131Creating Archive Libraries
  - Overview of Creating an Archive Library
  - 132Contents of an Archive File
  - 133Example of Creating an Archive Library
  - 134Replacing, Adding, and Deleting an Object Module
    - Replacing or Adding an Object Module
    - Deleting an Object Module
  - 135Summary of Keys to the ar(1) Command
    - Useful ar Keys
  - 136crt0.o
  - Archive Library Location
    - Using /usr/lib and /usr/lib/pa20_64
    - 137Using /usr/local/lib or /usr/contrib/lib
- 138Creating Shared Libraries
  - Creating Position-Independent Code (PIC)
    - Example Using +z
    - Comparing +z and +Z
    - Compiler Support for +z and +Z
  - 139Creating the Shared Library with ld
  - 140Shared Library Dependencies
    - 141The Order in Which Libraries Are Loaded (Load Graph)
      - For 32-bit mode.
      - 142For 64-bit mode.
    - 143Placing Loaded Libraries in the Search List
  - 144Updating a Shared Library
    - Incompatible Changes to a Shared Library
  - Shared Library Location
  - 145Improving Shared Library Performance
    - Using Prole-Based Optimization on Shared Libraries
    - Exporting Only the Required Symbols
    - 146Placing Frequently-Called Routines Together
    - 148Making Shared Libraries Non-Writable
    - Using the +ESlit Option to cc
- 149Version Control with Shared Libraries
  - When to Use Shared Library Versioning
  - 150Maintaining Old Versions of Library Modules
  - Library-Level Versioning
    - How to Use Library-Level Versioning
    - 151Creating a New, Incompatible Version of the Library
    - Migrating an Existing Library to Use Library-Level Versioning
    - 152The +h Option and Internal Names
    - File System Links to Shared Libraries
    - Using shl_load(3X) with Library-Level Versioning
  - 154Intra-Library Versioning
    - 155The Version Number Compiler Directive
    - Shared Library Dependencies and Version Control
    - 156Adding New Versions to a Shared Library
    - 157Specifying a Version Date
- 158Switching from Archive to Shared Libraries
  - Library Path Names
  - Relying on Undocumented Linker Behavior
  - 159Absolute Virtual Addresses
  - 160Stack Usage
  - Version Control
  - 161Debugger Limitations
  - Using the chroot Command with Shared Libraries
  - Proling Limitations
- 162Summary of HP-UX Libraries
- 164Caution When Mixing Shared and Archive Libraries
  - Example 1: Unsatised Symbols
  - 167Example 2: Using shl_load(3X)
  - 171Example 3: Hidden Denitions
  - 175Summary of Mixing Shared and Archive Libraries
- 176Using Shared Libraries in 64-bit mode
  - Internal Name Processing
  - 177Dynamic Path Searching for Shared Libraries
  - 178Shared Library Symbol Binding Semantics
    - Link-Time Symbol Resolution in Shared Libraries
    - 180Resolution of Unsatised Shared Library References
    - 181Promotion of Uninitialized Global Data Items
    - 182Symbol Searching in Dependent Libraries
  - 184Mixed Mode Shared Libraries
  - 18664-bit Mode Library Examples
    - Library Example: Creating a 64-bit Mode Compatibility Mode Shared Library.
    - 187Library Example: Creating a 64-bit Standard Mode
    - Library example: 64-bit Mode Dynamic Path Searching
      - 188 Chapter 5
      - Creating and Using Libraries Using Shared Libraries in 64-bit mode
    - 188Library Example: 64-bit Mode Compatibility Mode Link
      - You can usechatr +s to enable a.out in file1 and file2:
      - Chapter 5 189
      - Creating and Using Libraries Using Shared Libraries in 64-bit mode
    - 189Library Example: Using 64-bit Mode Compatibility and Standard Shared Libraries
    - Comparing Breadth-rst and Depth-rst Search in 64-bit Mode
      - For the following libraries, with the dependencies:
    - 190Library Example: Using RPATH with Standard Mode
    - Linking Libraries with +b pathlist
      - 191Library Example: Linking to Libraries with +b path_list in 64-bit Mode.
      - 192Library Example: Linking to Libraries with +b path_list in 32-bit Mode.
1956 Shared Library Management Routines
- 196Shared Library Management Routine Summaries
  - The shl_load Routine Summary
  - 197The dlopen Routines Summary
  - 198Related Files and Commands
- 199Shared Library Header Files
- 200Using Shared Libraries with cc and ld Options
- 201Initializers for Shared Libraries
  - Styles of Initializers
    - HP-UX-10.X-Style Initializers
    - 202Init/Fini Style Initializers
      - Init.
      - Fini.
  - 20332-bit Mode Initializers
    - Using HP-UX 10.X Style Initializers
    - Declaring the Initializer with the +I Option
      - Order of Execution of Multiple Initializers .
    - 204Initializer Syntax
      - Accessing Initializers' Addresses .
    - 205Example: An Initializer for Each Library
    - 207Example: A Common Initializer for Multiple Libraries
      - 208208 Chapter 6
      - Initializers for Shared Libraries C Source for _INITIALIZER (le init.c)
      - 209Chapter 6 209
      - Initializers for Shared Libraries C Source for libtwo.sl
      - Here are the commands used to build these libraries:
      - The following is an example program that loads these two libraries: C Source for testlib2
  - 21064-bit Mode Initializers
- 215The shl_load Shared Library Management Routines
  - The shl_load and cxxshl_load Routines
    - 218shl_load Usage
    - 219shl_load Example
    - 220BIND_NONFATAL Modier
    - BIND_VERBOSE Modier
    - BIND_FIRST Modier
    - 221DYNAMIC_PATH Modier
    - BIND_NOSTART Modier
    - BIND_RESTRICTED Modier
    - BIND_TOGETHER Modier
    - BIND_BREADTH_FIRST Modier
    - Binding Flags Examples
  - 222The shl_ndsym Routine
    - 225shl_ndsym Example
  - 226The shl_get and shl_get_r Routines
  - 230The shl_gethandle and shl_gethandle_r Routines
  - 231The shl_denesym Routine
  - 232The shl_getsymbols Routine
    - 235The shl_symbol Structure
    - shl_getsymbols Example
  - 238The shl_unload and cxxshl_unload Routines
    - 239Usage
- 240The dlopen Shared Library Management Routines
  - The dlopen Routine
  - 244The dlerror Routine
  - 245The dlsym Routine
    - 246Usage
    - 247Examples
  - 248The dlget Routine
    - Chapter 6 249
    - The dlopen Shared Library Management Routines
  - 249The dlmodinfo Routine
    - Retrieves information about a loaded module (program or shared library).
  - 252The dlgetname Routine
  - 253The dlclose Routine
- 256Dynamic Loader Compatibility Warnings
  - Unsupported Shared Library Management Routines
  - Unsupported Shared Library Management Flags
2597 Position-Independent Code
- 260What Is Relocatable Object Code?
- 261What is Absolute Object Code?
- 262What Is Position-Independent Code?
- 263Generating Position-Independent Code
  - 264For More Information:
  - PIC Requirements for Compilers and Assembly Code
  - 265Long Calls
  - Long Branches and Switch Tables
  - 266Assigned GOTO Statements
  - Literal References
  - 267Global and Static Variable References
  - Procedure Labels
2698 Ways to Improve Performance
- 270Linker Optimizations
  - Invoking Linker Optimizations from the Compile Line
    - See Also:
  - 271Incompatibilities with other Options
  - Unused Procedure Elimination with +Oprocelim
    - 272Complete Executables
    - Incomplete Executables
    - Shared Libraries
    - Relocatable Objects
    - Affects on Symbolic Debugging
- 273Options to Improve TLB Hit Rates
- 274Prole-Based Optimization
  - General Information about PBO
  - Using PBO
  - 275When to Use PBO
  - How to Use PBO
    - 276A Simple Example
  - 277Instrumenting (+I/-I)
    - 278The Startup File icrt0.o
    - The -I Linker Option
    - Code Generation from I-SOMs
  - 279Proling
    - Choosing Input Data
    - 280The ow.data File
    - 281Storing Prole Information for Multiple Programs
    - 282Sharing the ow.data File Among Multiple Processes
    - Forking an Instrumented Application
  - 283Optimizing Based on Prole Data (+P/-P)
    - The -P Linker Option
    - 284Using The ow.data File
    - Specifying a Different ow.data File with +df
    - Specifying a Different ow.data with FLOW_DATA
    - Interaction between FLOW_DATA and +df
    - Specifying a Different Program Name (+pgm)
  - 285Selecting an Optimization Level with PBO
  - 286Using PBO to Optimize Shared Libraries
  - 287Using PBO with ld -r
  - 288Restrictions and Limitations of PBO
    - Temporary Files
    - Source Code Changes and PBO
    - 289Prole-Based Optimization (PBO) and High-Level Optimization (HLO)
      - Example .
    - 290I-SOM File Restrictions
      - ld .
      - nm .
      - ar .
      - strip .
      - Compiler Options .
  - 291Compatibility with 9.0 PBO
- 293Improving Shared Library Start-Up Time with fastbind
  - Using fastbind
  - Invoking the fastbind Tool
  - 294Invoking fastbind from the Linker
  - How to Tell if fastbind Information is Current
  - Removing fastbind Information from a File
  - Turning off fastbind at Run Time
  - For More Information:
295A Using Maples
- 296Controlling Maples with the -k Option
  - Maple Example: Using -k lename (without +nodefaultmap Option):
    - 297Appendix A 297
    - Controlling Maples with the -k Option
    - 298 Appendix A
    - Changing Maples with -k lename and +nodefaultmap
- 298Changing Maples with -k lename and +nodefaultmap
  - Maple Example: Using -k maple and +nodefaultmap
    - 299Appendix A 299
    - Changing Maples with -k lename and +nodefaultmap
- 300Simple Maple
  - Appendix A 301
  - Default HP-UX Release 11.0 Maple
- 301Default HP-UX Release 11.0 Maple
  - The HP-UX Release 11.0 64-bit linker uses the following default maple:
- 303Dening Syntax for Maple Directives
- 304Dening Maple Segment Declarations
  - Segment Flags
  - 306Maple Segment Declaration Examples
- 307Dening Maple Section Mapping Directives
- 309Internal Map Structure
  - Placement of Segments in an Executable
  - Mapping Input Sections to Segments
  - 312Interaction between User-dened and Default Maple Directives
- 313Maple Option Error Messages
  - Fatal Errors
  - Warnings

Also you can find more Kenwood manuals or manuals for other Computer Equipment.

Kenwood categories

Automotive
Baby
Car Audio and Video
Cell Phone
Communications
Computer Equipment
- Microcassette Recorder
- Scanner
- Fax Machine
- Calculator
- Laminator
- Network Card
- Robotics
- Projector Accessories
- Network Router
- Flash Memory
- Surge Protector
- Laptop Docking Station
- Power Supply
- Mouse
- Label Maker
- Tablet Accessory
- Tablet
- Server
- Webcam
- Paper Shredder
- Network Cables
- Personal Computer
- Network Hardware
- Modem
- Laser Pointer
- Projector
- Switch
- Binding Machine
- Graphics Tablet
- Printer Accessories
- Printer
- Computer Drive
- Computer Monitor
- All in One Printer
- Computer Accessories
- Computer Hardware
- Copier
- Laptop
- Computer Keyboard
- eBook Reader
- Barcode Reader
- Cash Register
- Clock
- Electronic Accessory
- Credit Card Machine
- Electric Pencil Sharpener
- Postal Equipment
- Whiteboard Accessories
- Typewriter
- Noise Reduction Machine
- Time Clock
- Motherboards
- Components
- Accelerators
- Cooling Systems
- Data Center Solutions
- Desktops
- Handheld
- Point of Sale Systems
- Receiver
- Software
- Thin Clients
- SSD
Fitness & Sports
Furniture
Home Audio
Household Appliance
Kitchen Appliance
Laundry Appliance
Lawn and Garden
Marine Equipment
Mobile Devices
Musical Instruments & Equipment
Outdoor Cooking
Personal Care
Photography
Portable Media
Power Tools
Tools
TV and Video
Video Game