X86 installer

Hi all
I receive this when trying to build an installer containing the labview runtime (or any other built-in installer).
I have Win 7 64 bit, LV 2009 SP1 (copied dvd's to hdd, and installed from there).
I create a project with a blank VI, build an exe, then build an installer with the LV runtime, and I get this:
I've tried clearing the cache files, uninstall all of NI, reinstall all of NI - just cannot figure it out.
I definitely have .Net framework 2, so I just don't know.
Can anyone help, or point me in a new direction to look?
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
Loading product deployment information
*** Error: Internal error. (Error code -40)
There was a problem getting information about the source distribution for product 'NI .NET Framework 2.0 Language Pack x86 Installer'
*** End Error Report
*** WARNING ***
Skipping deployment information for an unidentified product because error code -40 occurred while loading file: C:\Program Files (x86)\National Instruments\Shared\MDF\Manifests\NI .NET Framework 2.0 Language Pack x86 Installer {F8ECD2D6-659C-49EB-8454-5F8F7B526FCF}.xml
Loading product deployment information
*** Error: Internal error. (Error code -40)
There was a problem getting information about the source distribution for product 'NI .NET Framework 2.0 Language Pack x86 Installer'
*** End Error Report
*** WARNING ***
Skipping deployment information for an unidentified product because error code -40 occurred while loading file: C:\Program Files (x86)\National Instruments\Shared\MDF\Manifests\NI .NET Framework 2.0 Language Pack x86 Installer {F8ECD2D6-659C-49EB-8454-5F8F7B526FCF}.xml
*** Error: Internal error. (Error code -40)
There was a problem getting information about the source distribution for product 'NI .NET Framework 2.0 Language Pack x86 Installer'
*** End Error Report
*** WARNING ***
Skipping deployment information for an unidentified product because error code -40 occurred while loading file: C:\Program Files (x86)\National Instruments\Shared\MDF\Manifests\NI .NET Framework 2.0 Language Pack x86 Installer {F8ECD2D6-659C-49EB-8454-5F8F7B526FCF}.xml
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
Copying files...
Updating files...
Creating merged database...
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
Done building deployment

longbow:
The issue is with the Application Builder looking for certain installer package dependencies. It's possible that the cached information on those external installers is either incorrect or corrupt.
You can test this by backing up and deleting the cache folders from the directory that it's looking in (Program Files (x86)\National Instruments\Shared\MDF\Manifests\). If the cache is no longer there, it should request the source installation media, and we can give it that instead. We may also be able to determine if the installation media is potentially at fault.
I believe there is a similar issue here that might be of some help.
Let me know if that helps!
Caleb Harris
National Instruments | Mechanical Engineer | http://www.ni.com/support

Similar Messages

  • Solaris 10 x86 Installation on Toshiba Tecra M1

    After a lot of trial and error, most of my own creation, I have successfully gotten Solaris 10 installed on my laptop!
    My question relates to SMF and creating a "non-networked" milestone. Mainly, umm, what should I leave out from the "all" level? Or more importantly, what should I add to the "multi-user-server" milestone to enable X?
    Some items that may help others doing S10 x86 installs:
    1) Tecra M1 needed "legacy floppy driver" support DISABLED in the Bios.
    2) Tecra M1 installation was done in text mode (option 4) and after installation ran /usr/X11/bin/xorgconfig with these settings -
    mouse=auto
    kbd=us, 104 key
    monitor=1280x1024@70hz
    vert sync was option "1" (forgot the values)
    video card=27 (trident)
    Works great!
    3) Onboard gigabit NIC was found perfectly.
    4) Sound works great
    5) Touchpad or USB mouse work fine.
    6) Disk setup issues -
    I had windows XP on the whole 40 gig disk. Purchased "Partition Commander" and resized XP down to 1/2 the disk. However it took the beginning of the disk (cylinder 1-20000). Solaris 10 would install but would lock up on subsequent reboots. Moving XP to the upper cylinder range fixed this issue (and giving Solaris cylinders 1-X.)
    7) Turn off Partition Commander before doing your solaris installation.
    I've now installed S10 on dell, toshiba, HP and Sun computers. Main issues have been with peripheral ID and driver installations but other than Wireless Drivers, nothing has failed! Way to go SUN!!
    D

    problem 1 is that it's looking for ../../s0.. Which I
    managed to
    fake out by creating the dir in the same mount
    point.
    Problem 2 is that it can't find .tmp_proto, which I
    must
    concur with. I can't find that on any of the b72 cd
    images.
    So, the setup_install_server fails.This seems to be the problem when you try to setup an install
    server on a Solaris SPARC system for Solaris x86 clients, using
    the Solaris 9 or Solaris 10/Express CD media.
    There's a Solaris x86 UFS filesystem on slice 0 on the CD media,
    and it's supposed to be mounted on the "s0" mount point,
    otherwise setup_install_server won't work. On a Solaris x86 box,
    vold mounts it automatically for you: /cdrom/cdrom0/s2 is the
    mount point for the platform independant ISO9660 part of the CD
    media, /cdrom/cdrom0/s0 is the UFS root filesystem.
    Problem is that Solaris SPARC:
    - does not understand Solaris x86 disk labels
    - does not allow mounting x86 UFS filesystems
    (and vice versa).
    AFAIK, Solaris 9 DVD media does not have this problem. I
    guess the same will be true when Solaris 10 DVD media is
    available in a few months. On the DVD media there's enough
    free space to include an extra copy of the files in the ISO9660
    filesystem.

  • Solaris 10 x86 installation problem on ProLiant DL380..

    I'm trying to put Sol10 b72 on a dual-proc ProLiant DL380 here, with the Compaq 5i array controller.
    I have the Solaris 9 drivers from HP; they seem to work just fine for the installation.
    The problem comes at the end of the first disc.
    Sidebar:
    For one thing (and this drove me NUTS until I got lucky and caught it during a reboot), at the end of the install, on the console, it asks for the driver diskettes..again.
    The problem is, it doesn't say this ANYWHERE else, only on the console..and if you're doing the installation in the X desktop, you just never know it. It doesn't write this to the xconsole window. I tried installing a good 5-6 times before, instead of hitting the power button out of frustration after the install just hung again, I actually opened up a terminal and typed 'reboot'..and caught the "Please insert the diskette and press Enter" as it killed X. If anyone at Sun is reading this..you may want to fix this, before someone gets very frustrated that their installations never seem to finish...
    End Sidebar.
    So...I'm doing the console text install (otherwise you'll never see the message to insert the driver diskettes for the Broadcom NIC and the Compaq array), and sure enough, at the end of the install, it asks for the diskette. I pop in the diskette it's specifically asking for (the Compaq array diskette in this instance), and hit enter. It chugs for a second and then says it can't find the driver on the diskette.
    Which is incorrect, because if it haden't found it on the diskette during the device configuration assistant phase during bootup, it wouldn't have even been able to install Solaris.
    So..what's up? Anyone have any ideas why Solaris finds it one time but can't find it later? Is this a bug or problem in the installation script?
    Thanks,
    Greg

    problem 1 is that it's looking for ../../s0.. Which I
    managed to
    fake out by creating the dir in the same mount
    point.
    Problem 2 is that it can't find .tmp_proto, which I
    must
    concur with. I can't find that on any of the b72 cd
    images.
    So, the setup_install_server fails.This seems to be the problem when you try to setup an install
    server on a Solaris SPARC system for Solaris x86 clients, using
    the Solaris 9 or Solaris 10/Express CD media.
    There's a Solaris x86 UFS filesystem on slice 0 on the CD media,
    and it's supposed to be mounted on the "s0" mount point,
    otherwise setup_install_server won't work. On a Solaris x86 box,
    vold mounts it automatically for you: /cdrom/cdrom0/s2 is the
    mount point for the platform independant ISO9660 part of the CD
    media, /cdrom/cdrom0/s0 is the UFS root filesystem.
    Problem is that Solaris SPARC:
    - does not understand Solaris x86 disk labels
    - does not allow mounting x86 UFS filesystems
    (and vice versa).
    AFAIK, Solaris 9 DVD media does not have this problem. I
    guess the same will be true when Solaris 10 DVD media is
    available in a few months. On the DVD media there's enough
    free space to include an extra copy of the files in the ISO9660
    filesystem.

  • Solaris 9 x86 installation problem on dell 600sc

    I am trying to install Solaris x86 on a Dell 600sc machine. But the installation always abort. It can boot from CDROM and perform hardware scaning. It then fails and reboots itself when loading kernel from CDROM. The error message is:
    Warning /pci@0,0/pci-ide@f,1/ide@0 (ata0)
    timeout: abort request, target=0 lun=0
    Any hint would be highly appreciated.
    Jon

    I am getting same error with Solaris 10.
    Does any one installaed Solaris on this machine.
    I am using latest BIOS from DELL.

  • Solaris 10 x86 Installation Fails to Start

    I am trying to install Solaris 10 x86 05/08 on a Sony PCG-K115S laptop. The issue I am having is that the installation hangs after printing the copyright information and does not go any further. I get no error message or status as to what the installation is doing.
    I downloaded the dvd iso from sun website and verified the md5 checksum before burning the dvd more than once but the issue occurred in both dvds.
    The laptop currently has XP installed but there is 30GB of free unallocated/partitioned space on the disk.
    Are there any options I can active to debug the installation and see where and why it is stalling.
    Thank you,
    F.
    Edit 1:
    After some forum reading I activated the Kernel Debugger and verbose mode:
    The installation hangs after this line is printed out:
    echi0 is /pci@0,0/pci104d,8175@c,2
    loaded modules: [uppc neti ufs unix krtld uhci hook genunix ip usba specfs pcplusmp cpu.generic sctp arp]
    Does this strike a cord with anybody??
    Edit 2:
    After some more reading and investigation, I read that this could be caused by my USB controller not being recognoized or some USB 2.0 issues with Solaris 10.
    I have tried to deactive the usb system with the options "-B acpi_user_options=2" and "-B acpi_user_options=8" but with no luck. (I got about these on some some forum, not sure if they are correct).
    Any help is appreciated!!
    Thank you,
    F.
    Edited by: Fergus on Jul 6, 2008 2:22 AM
    Edited by: Fergus on Jul 7, 2008 9:12 PM

    OK, got a little further. I entered the incorrect value for the acpi-user-options, the number should have been in hex.
    So with options "-k -v -B acpi-user-options=0x8 -B install_media=cdrom" I get the install menu
    1. Interactive
    On selecting "1" for interactive, the install begins be halts quickly with an error:
    NOTICE: rtls0 -- link down
    ERROR: Unable to configure network interface
       Exiting to shell.Is there any way to disable the configuration of the network interfaces?? I don't need them for installation...
    Thank you for any help,
    F.

  • Solaris 10 X86 Installation Struck after Loading Grub Stage 2

    Hi All,
    I am trying to install Solaris 10 X86 Platform on my intel system. I downloaded the iso DVD images from Sun site.
    sol-10-u8-ga-x86-dvd-iso-a.iso
    sol-10-u8-ga-x86-dvd-iso-b.iso
    When I boot with the Solaris DVD 1, I am getting the message "Loading Stage 2" and returned to grub> command line
    This is the message I am getting in my screen
    Loading Stage 2 ... ...
    GNU GRUB version 0.97 (639K lower/283584 upper memory)
    *[ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions os a device/filename. ]*
    grub> root
    *(hd1111): Filesystem type is iso9660, using whole disk*
    grub>
    Can some one help me on this, I tried in Google and other sun solve support forums but didnt find anything helpfull.
    Anybodys help is much appreciated..
    Regards, Sundar

    I'm getting the same thing with Solaris 10u8 in a VirtualBox. sol-10-u8-ga-x86-dvd.iso downloaded from cds.sun.com today.
    (I tried the pre-made VirtualBox image Sun provides, and it's horribly dysfunctional. So I thought I'd try a fresh installation. More fool me, apparently.)
    Edit: No, it's me. The problem is that the ISO I downloaded was incomplete - it cut off at precisely 2GB! The md5sum of what I downloaded is ea5a8606894d253e286861aaf4b5c50a; the official md5sum should be 9df7fd02d82976fd3ec38a18d1a57335. I guess tomorrow I try again with part A and part B ...
    So it looks like the answer is: check with md5sum that you actually have the full ISO.
    Edited by: DavidGerard on Feb 10, 2010 1:30 PM

  • No xwin on solaris 10 x86 installation

    hi,
    is it true, when we install solaris 10 for x86, all we got just text based OS, no graphical menu or something ?
    i've installed solaris 10 for x86(4 cd's) on my pc, it only came with text mode. is there something left ?
    thx
    -newbie-

    By accident, I found out that the graphics settings are remembered apparently only if a plug-and-play monitor is present (that reports its properties to the graphics adapter).
    Also, during installation, be sure to watch the screen at all times. The "kdmconfig" program is apparently run also during installation. There's a 4-second window (quite at the beginning of the installation) to view the graphics properties as detected by the installer. As soon as you see this screen, hit the SPACE key to stop the timer, then verify the settings if they match your monitor and graphics adapter type. If you have the manuals of these, it's easy to figure out if the settings are appropriate. Hit ESC to start kdmconfig, it'll go right into the XSun configuration (which is used ONLY by the installer with my version of Solaris 10). The installer automatically creates a XOrg configuration and switches to XOrg after reboot (if all went well).
    After successful installation of Solaris 10 (when the graphical subsystem is working), you can run "xorgconfig" (in the X binary directory) to create a "xorg.conf" file that you can place in "/etc/X11/" directory. I'm not sure if the file is actually parsed, but you can edit it to change settings if necessary.
    (BTW, it would be a good idea if "kdmconfig" would allow users to enter their own maximum/minimum/fixed horizontal and vertical frequencies, edit the mode table and set +/- hsync/vsync and interlace flags, and edit a monitor setting detected automatically. I was close to hair-pulling a couple of times. Also, the installer doesn't seem to save changes to the monitor setting.)

  • Solaris 8 x86: Installation on disk connected via IDE controller

    I have a PC with a Pentium 4 processor and the following IDE disks:
    Disk 1 and 2 at the primary IDE bus.
    Disk 3 connected via Promise Ultra 133 IDE controller.
    I want to install Solaris 8 Intel x86 edition on Disk 3, but the installation
    program only lists disks 1 and 2 as locations for install.
    Is there any method how to get Solaris 8 installed on Disk 3?
    Thank you very much for your help!

    Hello Michael,
    thanks for the information.
    There is no support for the Promise Ultra 133 IDE controller listed.
    Also, searching the internet for a private developed driver was not
    successful.
    Anyway, I have tried to make a test installation on a hard disk
    connected to the primary IDE controller and I detected a lot of
    further installation problems with my equipments because of
    missing or not properly identified drivers.
    So I think I have to make further investigations on concepts
    how to get Solaris 8 run in the best way.
    Thanks again for your help,
    Thomas

  • Solaris 8 x86 installation runs out of space

    I am installing Solaris 8 x86 on to a Dell PowerEdge Server with a 9.1 SCSI drive. Utilizing the Solaris installation process and choosing "Entire Solaris Software Group" the process completes successfully. When signed on as root and installing software from the "bonus software bundle" I simply run out of room. When reviewing the disk manager it shows that "/" is at 88% and "/usr" is at 0%. What am I doing wrong? What is the proper way to load ancillary software and to get it to load into the "/usr" and not the "/" partition?
    Thanks for the help!

    Hi,
    Suggest you can choose custom install option, where by you can define each partion size as you wish. You may create /opt as seperate partion where you can load all your required s/w.
    Or Increase size of root partion so as to accomodate /opt.
    I hope this helps to you.
    Thanks,
    Santosh

  • Java_es-5-websuite-ga-windows-x86 installation issue not setting JAVA_HOME

    looks like the installer from java_es-5-websuite-ga-windows-x86.zip is not setting the JAVA_HOME variable correctly.
    C:\Sun\JavaES5\DSEE\dscc6\bin>dsccsetup.exe initialize
    Failed to create child process ["1/bin/java.exe" -Dsun.directory.clip. [...]

    Sorry for the late response. Do you need the other components provided by JES? If not, I suggest installing DSEE from the zip installer which can be downloaded separately. If you have to use JES and the problem is still not resolved, please log a case with Sun.

  • Solaris 11 x86 installer hangs on boot

    I've downloaded both sol-11-1111-live-x86.iso and sol-11-1111-text-x86.iso, they both launch grub successfully, but thereafter they hang almost instantly.
    This is a photo of my monitor when the installer has died:
    [http://dl.dropbox.com/u/5487392/IMAG0073.jpg]
    I've installed ubunut and windows successfully on the machine, so the hardware should be ok.
    Is there some way I can launch the installer in verbose mode or something to more accurately pinpoint what fails during the boot?
    Any other suggestions that can get me closer to installing solaris are welcome as well.

    I am getting this on a Dell SC440.
    I thought it might be my lowly E2160 CPU, but I've just put in an Intel Q6600 (Core 2 Quad 2.4 GHz) and it still happens.
    The server previously had Red Hat Linux 6 on it (actually I reinstalled it today to test it), but I booted from a DOS USB stick and used fdisk to remove all partitions, so that the 3x 80 GB SATA disks I have in there are all blank.
    When I boot it goes through the initial screen with dots printing across and then displays a text line "Solaris Release 5.11 Version snv_151a 64-bit" then a copyright line and then it hangs.
    I've tried both the live and text install media, with the same result.
    I have used the same Solaris media to install onto another machine (an AMD powered Dell C521), and it is fine.
    Any ideas/pointers?

  • Solaris 11.2 x86 installation problem on GPT partitioned SSD

    I recently bought a new computer with Windows 8.1 pre-installed on it. I want to install Solaris 11.2 as dual-boot together with the pre-installed windows 8.1.
    The computer has a 128 GB SSD which is GPT partitioned. The SSD has 5 GPT partitions which are in use. I used a partition manager in Windows to shrink the size of the 5th partition (the windows system partition) so that i now have about 31 GB of unpartitioned, unused space after the 5 used partitions where i want to install Solaris into.
    For installation, I downloaded the Solaris text installer ISO and burned it onto a CD-R. Now, whenever the installation menu shows me the GPT partitions of my SSD and i choose "Use a GPT partition of the disk" it always goes back to the first menu screen where it says "Welcome to the Oracle Solaris installtion menu".
    Also, the installation menu shows the 5 used GPT partitions correctly, but then it shows me not one, but two partitions as "unused" with a size of 0.0 MB.
    What am i doing wrong?

    If you have support, then you will be better served by opening a support case.
    Assuming you don't, or you would have gone there already... There may well be bugs with supporting multiple OS's under GPT partitions.  I have no idea how much testing we did for such cases, and to be totally honest we put little effort into dual-booting systems these days, as using VM's in VIrtualBox or other VM managers is a better answer for 90i+% of people.
    That said, posting the output from prtvtoc for the disk would give someone a chance to see if there's an obvious bug.

  • X86 installation problems.

    Hardware: Asus motherboard MP NPV VM with Nvidea graphics, Amd x2 3600 processor
    Installed Version Solaris 10 11/06 update
    Problems: 1) Network card was not detected. So Internet can't be configured. 2) Display resolution problems with some monitors - some had maximum resolution that can't be changed at 480x600 in some the resolution was a little better but now on a samptron monitor the resolution is 1024x800. 3) The cursor of the mouse becomes invisible when logged out and logged back in or when restarted (instead of shut down) 4) Star office instalation started displaying errors - the installation progressed well upto 50% stage, but after that over a hundred files could not be installed
    The following is the output of the prtconf -v :
    System Configuration: Sun Microsystems i86pc
    Memory size: 479 Megabytes
    System Peripherals (Software Nodes):
    i86pc
    System properties:
    name='acpi-status' type=int items=1
    value=00000013
    name='relative-addressing' type=int items=1
    value=00000001
    name='MMU_PAGEOFFSET' type=int items=1
    value=00000fff
    name='MMU_PAGESIZE' type=int items=1
    value=00001000
    name='PAGESIZE' type=int items=1
    value=00001000
    name='biosdev-0x80' type=byte items=588
    value=01.eb.04.4d.33.2e.30.fa.fc.be.00.7c.bf.00.06.8c.c8.8e.d0.89.f4.8e.c0.8e.d8.51.b9.00.01.f3.a5.59.e9.00.8a.fb.b4.02.cd.16.24.03.3c.03.75.05.c6.06.61.07.01.bb.be.07.b9.04.00.80.3f.80.74.0e.83.c3.10.e2.f6.bd.75.07.b9.13.00.e9.e6.00.b4.00.cd.13.53.b4.41.bb.aa.55.b9.00.00.cd.13.72.3f.81.fb.55.aa.75.39.f7.c1.01.00.74.33.bd.a4.07.b9.03.00.e8.c8.00.5b.53.b9.05.00.66.6a.00.66.ff.77.08.66.ff.36.5c.07.6a.01.6a.10.b4.42.89.e6.cd.13.9f.83.c4.10.9e.73.7b.b4.00.cd.13.e2.dd.eb.6b.bd.a7.07.b9.03.00.e8.95.00.5b.53.8a.16.60.07.b4.08.cd.13.73.08.bd.62.07.b9.13.00.eb.79.88.c8.24.3f.a2.59.07.fe.c6.f6.e6.a3.5a.07.8b.47.08.8b.57.0a.f7.36.5a.07.89.c3.89.d0.f6.36.59.07.fe.c4.30.c9.88.fd.c1.e9.02.80.e1.c0.08.e1.88.dd.88.c6.8a.16.60.07.c4.1e.5c.07.be.05.00.b8.01.02.cd.13.73.12.b4.00.cd.13.4e.83.fe.00.75.ef.bd.88.07.b9.0e.00.eb.23.bb.00.7c.81.bf.fe.01.55.aa.74.08.bd.96.07.b9.0b.00.eb.10.8a.16.60.07.5e.66.ff.16.5c.07.bd.a1.07.b9.03.00.bb.4f.00.e8.0c.00.cd.18.80.3e.61.07.00.74.18.bb.1f.00.60.b8.01.13.ba.00.17.cd.10.b0.07.b9.01.00.cd.10.b4.00.cd.16.61.c3.00.00.00.00.7c.00.00.80.00.43.61.6e.27.74.20.72.65.61.64.20.67.65.6f.6d.65.74.72.79.4e.6f.20.61.63.74.69.76.65.20.70.61.72.74.69.74.69.6f.6e.43.61.6e.27.74.20.72.65.61.64.20.50.42.52.42.61.64.20.50.42.52.20.73.69.67.21.21.21.4c.42.41.43.48.53.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.80.00.01.01.bf.fe.ff.ff.c1.3e.00.00.00.4c.a1.12.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.55.aa.01.1e.00.00.00.ff.3f.00.00.10.00.00.00.3f.00.00.00.b0.9e.a1.12.00.00.00.00.00.02.b0.96.00.f0.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00
    name='kbd-type' type=string items=1
    value='US-English'
    name='ata-dma-enabled' type=string items=1
    value='1'
    name='atapi-cd-dma-enabled' type=string items=1
    value='0'
    name='ttyb-rts-dtr-off' type=string items=1
    value='false'
    name='ttyb-ignore-cd' type=string items=1
    value='true'
    name='ttya-rts-dtr-off' type=string items=1
    value='false'
    name='ttya-ignore-cd' type=string items=1
    value='true'
    name='ttyb-mode' type=string items=1
    value='9600,8,n,1,-'
    name='ttya-mode' type=string items=1
    value='9600,8,n,1,-'
    name='lba-access-ok' type=string items=1
    value='1'
    name='prealloc-chunk-size' type=string items=1
    value='0x2000'
    name='bootpath' type=string items=1
    value='/pci@0,0/pci-ide@e/ide@0/cmdk@0,0:a'
    name='console' type=string items=1
    value='text'
    name='bootprog' type=string items=1
    value='/platform/i86pc/multiboot'
    name='boot-args' type=unknown items=1
    value=00
    name='ramdisk_start' type=int items=2
    value=01034000.00000000
    name='ramdisk_end' type=int items=2
    value=055f1000.00000000
    name='mfg-name' type=string items=1
    value='i86pc'
    name='impl-arch-name' type=string items=1
    value='i86pc'
    name='whoami' type=string items=1
    value='/platform/i86pc/kernel/amd64/unix'
    name='mmu-modlist' type=string items=1
    value='mmu64'
    Hardware properties:
    name='bios-boot-device' type=string items=1
    value='80'
    name='stdout' type=int items=1
    value=00000000
    scsi_vhci, instance #0
    System properties:
    name='class' type=string items=1
    value='root'
    name='load-balance' type=string items=1
    value='round-robin'
    name='auto-failback' type=string items=1
    value='enable'
    Driver properties:
    name='pm-want-child-notification?' type=boolean dev=none
    name='initiator-interconnect-type' type=string items=1 dev=(174,0)
    value='SPI'
    name='scsi-selection-timeout' type=int items=1 dev=(174,0)
    value=000000fa
    name='scsi-options' type=int items=1 dev=(174,0)
    value=00107ff8
    name='scsi-watchdog-tick' type=int items=1 dev=(174,0)
    value=0000000a
    name='scsi-tag-age-limit' type=int items=1 dev=(174,0)
    value=00000002
    name='scsi-reset-delay' type=int items=1 dev=(174,0)
    value=00000bb8
    Device Minor Nodes:
    dev=(174,0)
    dev_path=/scsi_vhci:devctl
    spectype=chr type=minor
    isa, instance #0
    Hardware properties:
    name='bus-type' type=string items=1
    value='isa'
    name='device_type' type=string items=1
    value='isa'
    fdc, instance #0
    Driver properties:
    name='chip' type=int items=1 dev=none
    value=00082077
    Hardware properties:
    name='dma-channels' type=int items=1
    value=00000002
    name='interrupts' type=int items=1
    value=00000006
    name='reg' type=int items=6
    value=00000001.000003f0.00000006.00000001.000003f7.00000001
    name='acpi-namespace' type=string items=1
    value='\_SB_.PCI0.FDC0'
    name='model' type=string items=1
    value='PC standard floppy disk controller'
    name='compatible' type=string items=1
    value='PNP0700'
    Register Specifications:
    Bus Type=0x1, Address=0x3f0, Size=0x6
    Bus Type=0x1, Address=0x3f7, Size=0x1
    Interrupt Specifications:
    Interrupt Priority=0x5 (ipl 5), vector=0x6 (6)
    fd, instance #0
    System properties:
    name='mode_3D' type=int items=1
    value=00000000
    name='unit' type=int items=1
    value=00000000
    Driver properties:
    name='ddi-kernel-ioctl' type=boolean dev=none
    Device Minor Nodes:
    dev=(36,0)
    dev_path=/isa/fdc@1,3f0/fd@0,0:a
    spectype=blk type=minor
    dev_link=/dev/fd0a
    dev_path=/isa/fdc@1,3f0/fd@0,0:a,raw
    spectype=chr type=minor
    dev_link=/dev/rfd0a
    dev=(36,1)
    dev_path=/isa/fdc@1,3f0/fd@0,0:b
    spectype=blk type=minor
    dev_link=/dev/fd0b
    dev_path=/isa/fdc@1,3f0/fd@0,0:b,raw
    spectype=chr type=minor
    dev_link=/dev/rfd0b
    dev=(36,2)
    dev_path=/isa/fdc@1,3f0/fd@0,0:c
    spectype=blk type=minor
    dev_link=/dev/diskette
    dev_link=/dev/diskette0
    dev_link=/dev/fd0
    dev_link=/dev/fd0c
    dev_path=/isa/fdc@1,3f0/fd@0,0:c,raw
    spectype=chr type=minor
    dev_link=/dev/rdiskette
    dev_link=/dev/rdiskette0
    dev_link=/dev/rfd0
    dev_link=/dev/rfd0c
    asy, instance #0 (driver not attached)
    System software properties:
    name='interrupt-priorities' type=int items=1
    value=0000000c
    Hardware properties:
    name='interrupts' type=int items=1
    value=00000004
    name='reg' type=int items=3
    value=00000001.000003f8.00000008
    name='acpi-namespace' type=string items=1
    value='\_SB_.PCI0.UAR1'
    name='model' type=string items=1
    value='16550A-compatible COM port'
    name='compatible' type=string items=1
    value='PNP0501'
    Register Specifications:
    Bus Type=0x1, Address=0x3f8, Size=0x8
    Interrupt Specifications:
    Interrupt Priority=0xc (ipl 12), vector=0x4 (4)
    asy, instance #1 (driver not attached)
    System software properties:
    name='interrupt-priorities' type=int items=1
    value=0000000c
    Hardware properties:
    name='interrupts' type=int items=1
    value=00000003
    name='reg' type=int items=3
    value=00000001.000002f8.00000008
    name='acpi-namespace' type=string items=1
    value='\_SB_.PCI0.UAR2'
    name='model' type=string items=1
    value='16550A-compatible COM port'
    name='compatible' type=string items=1
    value='PNP0501'
    Register Specifications:
    Bus Type=0x1, Address=0x2f8, Size=0x8
    Interrupt Specifications:
    Interrupt Priority=0xc (ipl 12), vector=0x3 (3)
    lp (driver not attached)
    Hardware properties:
    name='interrupts' type=int items=1
    value=00000007
    name='reg' type=int items=3
    value=00000001.00000378.00000008
    name='acpi-namespace' type=string items=1
    value='\_SB_.PCI0.LPT1'
    name='model' type=string items=1
    value='Standard LPT printer port'
    name='compatible' type=string items=1
    value='PNP0400'
    i8042, instance #0
    Hardware properties:
    name='unit-address' type=string items=1
    value='1,60'
    name='interrupts' type=int items=2
    value=00000001.0000000c
    name='reg' type=int items=6
    value=00000001.00000060.00000001.00000001.00000064.00000001
    Register Specifications:
    Bus Type=0x1, Address=0x60, Size=0x1
    Bus Type=0x1, Address=0x64, Size=0x1
    Interrupt Specifications:
    Interrupt Priority=0x5 (ipl 5), vector=0x1 (1)
    Interrupt Priority=0x5 (ipl 5), vector=0xc (12)
    mouse, instance #0
    Driver properties:
    name='ddi-no-autodetach' type=int items=1 dev=none
    value=00000001
    Hardware properties:
    name='device-type' type=string items=1
    value='mouse'
    name='reg' type=int items=1
    value=00000001
    name='interrupts' type=int items=1
    value=0000000c
    name='acpi-namespace' type=string items=1
    value='\_SB_.PCI0.PS2M'
    name='model' type=string items=1
    value='PS/2 Port for PS/2-style Mice'
    name='compatible' type=string items=1
    value='pnpPNP,f03'
    Device Minor Nodes:
    dev=(116,0)
    dev_path=/isa/i8042@1,60/mouse@1:l
    spectype=chr type=minor
    dev_link=/dev/kdmouse
    dev=(116,1)
    dev_path=/isa/i8042@1,60/mouse@1:internal_mouse
    spectype=chr type=internal
    Device Minor Layered Under:
    mod=consms accesstype=chr
    dev_path=/pseudo/consms@0
    keyboard, instance #0
    Driver properties:
    name='ddi-no-autodetach' type=int items=1 dev=none
    value=00000001
    Hardware properties:
    name='device-type' type=string items=1
    value='keyboard'
    name='interrupts' type=int items=2
    value=00000001.0000000c
    name='reg' type=int items=1
    value=00000000
    name='_CID' type=string items=1
    value='PNP030B'
    name='acpi-namespace' type=string items=1
    value='\_SB_.PCI0.PS2K'
    name='model' type=string items=1
    value='IBM Enhanced (101/102-key, PS/2 mouse support)'
    name='compatible' type=string items=1
    value='pnpPNP,303'
    Device Minor Nodes:
    dev=(101,0)
    dev_path=/isa/i8042@1,60/keyboard@0:kb8042
    spectype=chr type=minor
    Device Minor Layered Under:
    mod=conskbd accesstype=chr
    dev_path=/pseudo/conskbd@0
    none (driver not attached)
    Hardware properties:
    name='interrupts' type=int items=1
    value=0000000a
    name='reg' type=int items=3
    value=00000001.00000330.00000002
    name='acpi-namespace' type=string items=1
    value='\_SB_.PCI0.MIDI'
    name='model' type=string items=1
    value='Audio MIDI interface (MPU401 UART)'
    name='compatible' type=string items=1
    value='PNPB006'
    joyst (driver not attached)
    Hardware properties:
    name='reg' type=int items=3
    value=00000001.00000201.00000001
    name='acpi-namespace' type=string items=1
    value='\_SB_.PCI0.GAME'
    name='model' type=string items=1
    value='Game port (Joy stick)'
    name='compatible' type=string items=1
    value='PNPB02F'
    motherboard (driver not attached)
    Hardware properties:
    name='reg' type=int items=45
    value=00000000.000f0000.00004000.00000000.000f4000.00004000.00000000.000f8000.00004000.00000000.000fc000.00004000.00000000.1def0000.00010000.00000000.ffff0000.00010000.00000000.00000000.000a0000.00000000.00100000.1ddf0000.00000000.1df00000.02000000.00000000.fec00000.00001000.00000000.fee00000.00100000.00000000.fefff000.00001000.00000000.fff80000.00001000.00000000.fff90000.00030000.00000000.fffed000.00003000
    name='acpi-namespace' type=string items=1
    value='\_SB_.MEM_'
    name='model' type=string items=1
    value='Motherboard'
    name='compatible' type=string items=1
    value='PNP0C01'
    pci, instance #0
    Driver properties:
    name='device_type' type=string items=1 dev=none
    value='pciex'
    Hardware properties:
    name='ecfga-base-address' type=int64 items=1
    value=00000000f0000000
    name='available' type=int items=145
    value=81000000.00000000.00000000.00000000.00000170.81000000.00000000.00000178.00000000.00000078.81000000.00000000.000001f8.00000000.0000017e.81000000.00000000.00000377.00000000.0000007f.81000000.00000000.000003f7.00000000.00000569.81000000.00000000.00000968.00000000.00000008.81000000.00000000.00000978.00000000.00000068.81000000.00000000.000009e8.00000000.00000008.81000000.00000000.000009f8.00000000.0000016a.81000000.00000000.00000b63.00000000.0000000f.81000000.00000000.00000b73.00000000.0000006f.81000000.00000000.00000be3.00000000.0000000f.81000000.00000000.00000bf3.00000000.0000400d.81000000.00000000.00004c80.00000000.00003380.81000000.00000000.0000c000.00000000.00000800.81000000.00000000.0000c808.00000000.000003f8.81000000.00000000.0000cc10.00000000.000013f0.81000000.00000000.0000e010.00000000.000013f0.81000000.00000000.0000f410.00000000.00000bf0.82000000.00000000.1df00000.00000000.00100000.82000000.00000000.20000000.00000000.c0000000.82000000.00000000.f4000000.00000000.07000000.82000000.00000000.fd000000.00000000.00800000.82000000.00000000.fd900000.00000000.00200000.82000000.00000000.fdd00000.00000000.00100000.82000000.00000000.fdf00000.00000000.00124000.82000000.00000000.fe028000.00000000.00003000.82000000.00000000.fe02e100.00000000.00000f00.82000000.00000000.fe030000.00000000.00bd0000
    name='bus-range' type=int items=2
    value=00000000.00000004
    name='compatible' type=string items=1
    value='pciex_root_complex'
    name='device_type' type=string items=1
    value='pciex'
    name='reg' type=int items=3
    value=00000000.00000000.00000000
    name='#size-cells' type=int items=1
    value=00000002
    name='#address-cells' type=int items=1
    value=00000003
    Register Specifications:
    Bus Type=0x0, Address=0x0, Size=0x0
    Device Minor Nodes:
    dev=(183,255)
    dev_path=/pci@0,0:devctl
    spectype=chr type=minor
    dev=(183,253)
    dev_path=/pci@0,0:reg
    spectype=chr type=minor
    dev=(183,252)
    dev_path=/pci@0,0:intr
    spectype=chr type=minor
    pci1043,81c0 (driver not attached)
    Hardware properties:
    name='reg' type=int items=5
    value=00000000.00000000.00000000.00000000.00000000
    name='compatible' type=string items=7
    value='pci10de,2f0.1043.81c0.a2' + 'pci10de,2f0.1043.81c0' + 'pci1043,81c0' + 'pci10de,2f0.a2' + 'pci10de,2f0' + 'pciclass,050000' + 'pciclass,0500'
    name='model' type=string items=1
    value='Ram'
    name='power-consumption' type=int items=2
    value=00000001.00000001
    name='66mhz-capable' type=boolean
    name='fast-back-to-back' type=boolean
    name='devsel-speed' type=int items=1
    value=00000000
    name='max-latency' type=int items=1
    value=00000000
    name='min-grant' type=int items=1
    value=00000000
    name='subsystem-vendor-id' type=int items=1
    value=00001043
    name='subsystem-id' type=int items=1
    value=000081c0
    name='unit-address' type=string items=1
    value='0'
    name='class-code' type=int items=1
    value=00050000
    name='revision-id' type=int items=1
    value=000000a2
    name='vendor-id' type=int items=1
    value=000010de
    name='device-id' type=int items=1
    value=000002f0
    pci1043,81c0 (driver not attached)
    Hardware properties:
    name='reg' type=int items=5
    value=00000100.00000000.00000000.00000000.00000000
    name='compatible' type=string items=7
    value='pci10de,2fa.1043.81c0.a2' + 'pci10de,2fa.1043.81c0' + 'pci1043,81c0' + 'pci10de,2fa.a2' + 'pci10de,2fa' + 'pciclass,050000' + 'pciclass,0500'
    name='model' type=string items=1
    value='Ram'
    name='power-consumption' type=int items=2
    value=00000001.00000001
    name='66mhz-capable' type=boolean
    name='devsel-speed' type=int items=1
    value=00000000
    name='max-latency' type=int items=1
    value=00000000
    name='min-grant' type=int items=1
    value=00000000
    name='subsystem-vendor-id' type=int items=1
    value=00001043
    name='subsystem-id' type=int items=1
    value=000081c0
    name='unit-address' type=string items=1
    value='0,1'
    name='class-code' type=int items=1
    value=00050000
    name='revision-id' type=int items=1
    value=000000a2
    name='vendor-id' type=int items=1
    value=000010de
    name='device-id' type=int items=1
    value=000002fa
    pci1043,81c0 (driver not attached)
    Hardware properties:
    name='reg' type=int items=5
    value=00000200.00000000.00000000.00000000.00000000
    name='compatible' type=string items=7
    value='pci10de,2fe.1043.81c0.a2' + 'pci10de,2fe.1043.81c0' + 'pci1043,81c0' + 'pci10de,2fe.a2' + 'pci10de,2fe' + 'pciclass,050000' + 'pciclass,0500'
    name='model' type=string items=1
    value='Ram'
    name='power-consumption' type=int items=2
    value=00000001.00000001
    name='66mhz-capable' type=boolean
    name='devsel-speed' type=int items=1
    value=00000000
    name='max-latency' type=int items=1
    value=00000000
    name='min-grant' type=int items=1
    value=00000000
    name='subsystem-vendor-id' type=int items=1
    value=00001043
    name='subsystem-id' type=int items=1
    value=000081c0
    name='unit-address' type=string items=1
    value='0,2'
    name='class-code' type=int items=1
    value=00050000
    name='revision-id' type=int items=1
    value=000000a2
    name='vendor-id' type=int items=1
    value=000010de
    name='device-id' type=int items=1
    value=000002fe
    pci1043,81c0 (driver not attached)
    Hardware properties:
    name='reg' type=int items=5
    value=00000300.00000000.00000000.00000000.00000000
    name='compatible' type=string items=7
    value='pci10de,2f8.1043.81c0.a2' + 'pci10de,2f8.1043.81c0' + 'pci1043,81c0' + 'pci10de,2f8.a2' + 'pci10de,2f8' + 'pciclass,050000' + 'pciclass,0500'
    name='model' type=string items=1
    value='Ram'
    name='power-consumption' type=int items=2
    value=00000001.00000001
    name='66mhz-capable' type=boolean
    name='fast-back-to-back' type=boolean
    name='devsel-speed' type=int items=1
    value=00000000
    name='max-latency' type=int items=1
    value=00000000
    name='min-grant' type=int items=1
    value=00000000
    name='subsystem-vendor-id' type=int items=1
    value=00001043
    name='subsystem-id' type=int items=1
    value=000081c0
    name='unit-address' type=string items=1
    value='0,3'
    name='class-code' type=int items=1
    value=00050000
    name='revision-id' type=int items=1
    value=000000a2
    name='vendor-id' type=int items=1
    value=000010de
    name='device-id' type=int items=1
    value=000002f8
    pci1043,81c0 (driver not attached)
    Hardware properties:
    name='reg' type=int items=5
    value=00000400.00000000.00000000.00000000.00000000
    name='compatible' type=string items=7
    value='pci10de,2f9.1043.81c0.a2' + 'pci10de,2f9.1043.81c0' + 'pci1043,81c0' + 'pci10de,2f9.a2' + 'pci10de,2f9' + 'pciclass,050000' + 'pciclass,0500'
    name='model' type=string items=1
    value='Ram'
    name='power-consumption' type=int items=2
    value=00000001.00000001
    name='66mhz-capable' type=boolean
    name='fast-back-to-back' type=boolean
    name='devsel-speed' type=int items=1
    value=00000000
    name='max-latency' type=int items=1
    value=00000000
    name='min-grant' type=int items=1
    value=00000000
    name='subsystem-vendor-id' type=int items=1
    value=00001043
    name='subsystem-id' type=int items=1
    value=000081c0
    name='unit-address' type=string items=1
    value='0,4'
    name='class-code' type=int items=1
    value=00050000
    name='revision-id' type=int items=1
    value=000000a2
    name='vendor-id' type=int items=1
    value=000010de
    name='device-id' type=int items=1
    value=000002f9
    pci1043,81c0 (driver not attached)
    Hardware properties:
    name='reg' type=int items=5
    value=00000500.00000000.00000000.00000000.00000000
    name='compatible' type=string items=7
    value='pci10de,2ff.1043.81c0.a2' + 'pci10de,2ff.1043.81c0' + 'pci1043,81c0' + 'pci10de,2ff.a2' + 'pci10de,2ff' + 'pciclass,050000' + 'pciclass,0500'
    name='model' type=string items=1
    value='Ram'
    name='power-consumption' type=int items=2
    value=00000001.00000001
    name='66mhz-capable' type=boolean
    name='fast-back-to-back' type=boolean
    name='devsel-speed' type=int items=1
    value=00000000
    name='max-latency' type=int items=1
    value=00000000
    name='min-grant' type=int items=1
    value=00000000
    name='subsystem-vendor-id' type=int items=1
    value=00001043
    name='subsystem-id' type=int items=1
    value=000081c0
    name='unit-address' type=string items=1
    value='0,5'
    name='class-code' type=int items=1
    value=00050000
    name='revision-id' type=int items=1
    value=000000a2
    name='vendor-id' type=int items=1
    value=000010de
    name='device-id' type=int items=1
    value=000002ff
    pci1043,81c0 (driver not attached)
    Hardware properties:
    name='reg' type=int items=5
    value=00000600.00000000.00000000.00000000.00000000
    name='compatible' type=string items=7
    value='pci10de,27f.1043.81c0.a2' + 'pci10de,27f.1043.81c0' + 'pci1043,81c0' + 'pci10de,27f.a2' + 'pci10de,27f' + 'pciclass,050000' + 'pciclass,0500'
    name='model' type=string items=1
    value='Ram'
    name='power-consumption' type=int items=2
    value=00000001.00000001
    name='66mhz-capable' type=boolean
    name='devsel-speed' type=int items=1
    value=00000000
    name='max-latency' type=int items=1
    value=00000000
    name='min-grant' type=int items=1
    value=00000000
    name='subsystem-vendor-id' type=int items=1
    value=00001043
    name='subsystem-id' type=int items=1
    value=000081c0
    name='unit-address' type=string items=1
    value='0,6'
    name='class-code' type=int items=1
    value=00050000
    name='revision-id' type=int items=1
    value=000000a2
    name='vendor-id' type=int items=1
    value=000010de
    name='device-id' type=int items=1
    value=0000027f
    pci1043,81c0 (driver not attached)
    Hardware properties:

    hi Sivasubramanian,
    as i'm on a vacation in San Francisco (i'm writing this on my Cingular 8525 Windows Pocket PC 5) I won't be able to take a look at the
    report...(my email is jags_fl at yahoo dot com) but after u ran installation check tool did u look at the results? check for those 'Y' & 'N' as showed on following page:
    http://www.sun.com/bigadmin/hcl/hcts/install_check.html
    u would be able to see urself if any hardware is not compatible (at the end of installation check tool)...
    - Jags Desai

  • Oracle database 10.2.0.2 x86 installation error

    Dear Oracle DB expert,
    i am not sure it has been answer before, as I have tried to search from historical question in this forum but could not have answer. The question is I have a testing database server, I have follow all the step from preparation to start installation. The installation database went well from checking to copy all file but fail at linking stage: The error is :
    Error in invoking target 'client_sharedlib' of makefile '/u01/app/oracle/product/10.2.0/db_1/network/lib/ins_net_client.mk'
    When I check the log the error for further infor is "
    INFO : genclntsh: Failed to link libclntsh.so.10.1
    INFO : *** Error code 1
    My environtment are :
    O/S windows 7 proffesional 32 bit
    Oracle VirtualBox
    Solaris 10 32-bit i386 kernel
    Oracle db : 10202_database_solx86
    I am not sure about the problem above, when I tried to get the answer from google some of them mention related with the not match between O/S with Oracle database. Is it because 10202_database_solx86 is for 64 bit? So the installation could not be happened?
    Or I have missed some steps of installation therefore get those errors?
    Please give me assistant on this matter about the problem I have. I am planning to move to Solaris 64 bit environtment but I could not affort to buy test environtment for 64 bit at the moment.
    Thanks and Regards,
    Buz

    Hi Helios,
    I have installed from the scratchs again from O/S to database and follow Database documentation that also ask the installer to look further:
    at /u01/app/oracle/product/10.2.0/db_1/install/make.log. And based on that log file here is the log it seems the problem at ntcontab.o etc: detail below;
    fatal: symbol 'ntcontab' in file /u01/app/oracle/product/10.2.0/db_1/lib/lib
    n10.a(ntcontab.o): section [3].data: size 0x60: symbol (address 0, size 0x70) li
    es outside of containing section
    ld: fatal: file processing errors. No output written to /u01/app/oracle/product/
    10.2.0/db_1/lib/libclntsh.so.10.1
    genclntsh: Failed to link libclntsh.so.10.1
    *** Error code 1
    Do you know what mean of this please assist me on this problem so I could fix it.
    Thank you Helios,
    Rgds, Buz

  • OEL 6 x86 : installation crash with virtualbox 4.0 ubuntu

    Hi all,
    I try to install the OEL 6 as VM on VirtualBox 4.0.
    Error occurs during installation of glibc-common package.
    I try it with VMware ESXi , no problem.
    Who have the same error? where found a solution ?
    Pierre

    I workaround the problem .
    upgrade in VirtualBox 4.0.2 last version. same pb
    configure memory less than 1GB OK
    shutdown , increase the memory to 1.7 GB startup OK
    Pierre

Maybe you are looking for