AIF and automated installation

I have a bunch of machines to get installed. I am using the automated feature of AIF and so far I have two questions:
1 - Even selecting net as SOURCE and eth0="dhcp", I have to run the partial configuration of the network before the automatic installation. Is it a bug or a feature ?
2 - How can I add the configuration file in the same usb stick as the installer ? I am currently using two sticks or copying it through scp.
It is really a great tool.

tjpp wrote:
Thanks for your reply! It works with
worker_runtime_network () {
dhcpcd eth0
with dhcpcd rather than dhcpd.
sorry, i make this typo all the time.
tjpp wrote:1. the options I have in BLOCKDATA are not passed to the final /etc/fstab. Basically are ext4 performance options (data=writeback, for instance).
this is a bug that has been fixed in the meanwhile.
http://bugs.archlinux.org/task/18994
iirc the latest isos at http://build.archlinux.org/isos/ have the fix.
tjpp wrote:2. Is there a function like worker_intro () where I could put my scripts to run after core installation ? Is the worker_configure_system run after the packages installation ?
/usr/lib/aif/core/procedures/automatic should explain everything.

Similar Messages

I can not make a "Automated Installation of the Introscope Agent" (Managed System Configuration, p.7)

I can not make a "Byte Code Adapter Installation"
When I open meets both paragraphs in step Managed System Configuration is somewhat obscure situations that do not allow the automatic configuration Introscope agent and Introscope Manager
Please help to resolve a number of questions that might help me complete the setup :
1. Why has the status of Enterprise Manager : <No Enterprise Manager configured> ( see picture)
I set up Enterprise Manager in accordance with the installation instructions and complied with all the setting items . Since without any configuration can be associated with the appearance of this status ?
2 . Why Server Node is empty detail settings ?
JDK Location:
Enterprise Manager Host:
Enterprise Manager Port:
Introscope Agent Name:
Introscope Agent Profile:
Autoprobe Directives:
Wily Version:
Introscope Agent Version:
Introscope Agent Log Location:
3 . What a mistake ($ MC: DIAG_WILY_MSG: 032 : L), which appears when I click configuration "Configure Introscope Agent Setup ...", and what it can be linked ? ( see picture )
And the last question , which is also linked to the process of automatic configuration and refers to a phrase from the instruction (Introscope Version 9
Installation Guide For SAP July 2012) points out "Automated Installation of the Introscope Agent via SMD"
there is such an item:
2 . Deploy ISAGENTJ5 *. SCA which is the Introscope Java Agent 9 with SDM to Solution Manager. You may need to deploy also ISAGENT *. SCA which is Introscope Java Agent 8.
However, nowhere does it say where exactly ( on what the absolute path ) I must perform unloading and then what to do with this discharge

The problem was resolved a small manipulation - on stage Basic Configuration,
point 3 "Configure CA Introscope"
I forgot to add to the list of CA Introscope Enterprise Managers link to my manager.
Thus it is necessary to take into account that the path should be correct (usually for linux - /usr/sap/ccms/apmintroscope) and the directory should be applied appropriate privileges.
Then in paragraph "Byte Code Adapter Installation" - there are all the necessary data, and it starts to work correctly

Bridge and PS not communicating with scripts and automation.

CS4 PS and Bridge is not communicating correctly.
When opening an image from Bridge it opens whiteout any issues but when choosing Tools and PS and any form of automation or script it will not open and start the requested action.
Then when choosing same or another action from the tools/PS menu I get the message that PS is currently busy processing another task and it asks me if I wish to cue the action.
There is no difference if I chose cue or stop after this since nothing is happening how ever long I wait.
If PS is not started it will start up the application but nothing more after that. I have reinstalled and repaired permissions both after and before.
A colleague who also using PS CS4 is having the same hardware and is not having the same problem so I guess I am having a problem with some form of configuration.
CS3 is working correctly on the same machine and is having no issues at all.
Config is Macbook Pro 2.33Ghz 2gb ram OS 10.5.5 whit all the latest updates.
TIA for you help or crazy ideas.
Sven

As I wrote above I have already repaired the permissions but I have also rebooted several times, I have done that before and after installs and removals off the application and I used the Adobe script CS4 cleaner script to completely remove the apps.
The applications are all installed on their default locations and has not been moved at all and no names has been changed.
Does anybody know any more thorough way of removing all settings and preferences for CS4 then that script.
Maybe there are some remaining settings somewhere that I have not been able to remove.
Are there any sort of total remover of selected adobe apps rather then having to remove all adobe stuff on the machine that is more that can do more then that script.
Sven

Measurement and Automation explorer or the Instrument I/O Assistant is not installed correctly.

I am having difficulties getting Labview to work with my NI card. I have a PCI_6225 card running on a Win 7 64-bit install. I had to download all of the drivers and installers from the NI site and during the Labview install, I recieve a prompt asking for my hardware drivers. Since I only have the compressed hardware installer, Labview doesn't like what it sees and continues the installation of LABVIEW. I then attempt to open an analog input channel through the Instrument I/O Assistant which displays the error seen in the image attached.
I know the hardware works because in the Measurement and Automation client, I am able to observe the analog input I hope to collect in LABVIEW.
Is there a fix to get LABVIEW working? I have tried multple installs of LABVIEW and am on a administered computer through my University's IT people. I have 'full admin' rights. Thanks.
Attachments:
error.jpg ‏254 KB

Hello jbaxter,
When you download the Drivers from NI's website, make sure you unzip them (extract them) to a folder on your computer before you install them. If you use the NI Downloader it should prompt you to unzip and run the files after the download is complete. You need to either repair, or reinstall DAQmx and NI VISA. Make sure you download the latest versions of these first:
http://search.ni.com/nisearch/app/main/p/bot/no/ap/global/lang/en/pg/1/sn/catnav:du,ssnav:sup/1//en/...
Then go to Control Panel»Programs and Features»National Instruments Software and click Uninstall/Change then go to DAQmx and NI-VISA and click Repair. You can then point to folder that you downloaded from NI's website (make sure this is not a zip folder, but the folder that has been extracted). Or you could choose Remove, and then reinstall them both again. Also if you are using GPIB, reinstall or repair the NI-488.2 driver.
Here are some relevant links:
http://digital.ni.com/public.nsf/allkb/DC808866AF7D5C0986256FCE006E9BAB
http://forums.ni.com/t5/LabVIEW/Again-I-O-Assistant-not-installed-correctly/td-p/1024807
http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/quot-MAX-or-Instrument-I-O-Assistant-not-inst...
http://forums.ni.com/t5/LabVIEW/Install-Instrument-I-O-Assistant/td-p/1471516
Software Developer
National Instruments

Installing Solaris 11 on SunFIre T1000 With Automated Installer Server Fail

h4. Hi
h4. A few days i am try to intall solaris 11 11/11 on our server Sunfire T1000
h4. we first upgrade the firmware of the server to
sc> showhost
Sun-Fire-T1000 System Firmware 6.7.12 2011/07/06 20:03
Host flash versions:
OBP 4.30.4.d 2011/07/06 14:27
Hypervisor 1.7.3.c 2010/07/09 15:14
POST 4.30.4.b 2010/07/09 14:25
h4. And after we install Solaris 11 x86 on a laptop, in that we configure an AIS (Automated installer Server)
installadm list
Service Name Alias Of Status Arch Image Path
default-sparc s11-sparc on Sparc /install/images/s11-sparc
s11-sparc - on Sparc /install/images/s11-sparc
h4. We are using the default installations with a DHCP server in the Laptop
installadm list -m -p
Service Name Manifest Status
default-sparc orig_default Default
s11-sparc orig_default Default
h4. By the other side, in the sparc server (T1000) we use OBP for a WAN Boot Installation
boot net:dhcp - installl
2012-08-08 20:33:44,911 InstallationLogger DEBUG Starting Automated Installation
2012-08-08 20:33:44,913 InstallationLogger INFO Using XML Manifest: /system/volatile/ai.xml
2012-08-08 20:33:44,965 InstallationLogger INFO Using profile specification: /system/volatile/profile
2012-08-08 20:33:45,018 InstallationLogger INFO Using service list file: /var/run/service_list
2012-08-08 20:33:45,070 InstallationLogger INFO Starting installation.
2012-08-08 20:33:45,122 InstallationLogger DEBUG Registering Manifest Parser Checkpoint
2012-08-08 20:33:45,124 InstallationLogger DEBUG Engine registering:
2012-08-08 20:33:45,126 InstallationLogger DEBUG name: manifest-parser
2012-08-08 20:33:45,128 InstallationLogger DEBUG module_path: solaris_install.manifest.parser
2012-08-08 20:33:45,129 InstallationLogger DEBUG checkpoint_class_name: ManifestParser
2012-08-08 20:33:45,131 InstallationLogger DEBUG args: None
2012-08-08 20:33:45,133 InstallationLogger DEBUG kwargs: {'call_xinclude': True, 'manifest': '/system/volatile/ai.xml', 'validate_from_docinfo': True}
2012-08-08 20:33:45,135 InstallationLogger DEBUG insert_before: None
2012-08-08 20:33:45,136 InstallationLogger DEBUG log_level: None
2012-08-08 20:33:45,138 InstallationLogger DEBUG =============================
2012-08-08 20:33:45,142 InstallationLogger DEBUG Current checkpoint list:
2012-08-08 20:33:45,144 InstallationLogger DEBUG      manifest-parser
2012-08-08 20:33:45,146 InstallationLogger DEBUG Executing Manifest Parser Checkpoint
2012-08-08 20:33:45,148 InstallationLogger DEBUG Retrieving checkpoint list from manifest-parser to None+
2012-08-08 20:33:45,150 InstallationLogger DEBUG Executing Engine Checkpoints...+
2012-08-08 20:33:45,152 InstallationLogger DEBUG Retrieving checkpoint list from manifest-parser to None+
2012-08-08 20:33:45,154 InstallationLogger DEBUG Engine will be executing following checkpoints:+
2012-08-08 20:33:45,155 InstallationLogger DEBUG      manifest-parser
2012-08-08 20:33:45,157 InstallationLogger DEBUG Spawning InstallEngine execution thread
2012-08-08 20:33:45,160 InstallationLogger DEBUG Loading manifest-parser checkpoint
2012-08-08 20:33:45,213 InstallationLogger.manifest-parser DEBUG Initializing ManifestParser (manifest=/system/volatile/ai.xml, Validate_from_docinfo=True, dtd_file=None, load_defaults=True, call_xinclude=True)
2012-08-08 20:33:45,273 InstallationLogger DEBUG manifest-parser: prog est-1, prog ratio-0.95, total_ratio-1.00
2012-08-08 20:33:45,275 InstallationLogger DEBUG Last checkpoint, manifest-parser: prog ratio 0.95
2012-08-08 20:33:45,279 InstallationLogger DEBUG Snapshotting DOC to /var/run/install_engine/engine.MYk67H/.data_cache.manifest-parser
2012-08-08 20:33:45,286 InstallationLogger DEBUG Executing manifest-parser checkpoint
2012-08-08 20:33:45,288 InstallationLogger.manifest-parser DEBUG ManifestParser.execute(dry_run=False) called
2012-08-08 20:33:45,290 InstallationLogger.manifest-parser DEBUG ManifestParser.parse(doc=-> [DataObjectCache] (<solaris_install.data_object.cache.DataObjectCache object at 0xee1b90>)
     -> [persistent] (DataObjectCacheChild: persistent)
          -> [auto-install] (<solaris_install.ApplicationData object at 0xee1030>)
     -> [volatile] (DataObjectCacheChild: volatile)
          -> [apply_sysconfig_dict] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee1050>)) called
2012-08-08 20:33:45,292 InstallationLogger.manifest-parser DEBUG loading manifest (dtd_validation=True)
2012-08-08 20:33:45,872 InstallationLogger.manifest-parser DEBUG Parsed XML document:
<!DOCTYPE auto_install SYSTEM "file:///usr/share/install/ai.dtd.1">
<auto_install>
<ai_instance name="orig_default" auto_reboot="false">
<target>
<logical noswap="false" nodump="false">
<zpool name="rpool" is_root="true" action="create">
<filesystem name="export" mountpoint="/export" action="create" in_be="false"/>
<filesystem name="export/home" action="create" in_be="false"/>
<be name="solaris"/>
</zpool>
</logical>
</target>
<software type="IPS">
<destination>
<image action="create" index="false">

<facet set="false">facet.locale.*</facet>
<facet set="true">facet.locale.en</facet>
<facet set="true">facet.locale.en_US</facet>
<facet set="true">facet.locale.es</facet>
<facet set="true">facet.locale.es_ES</facet>
</image>
</destination>
<source>
<publisher name="solaris">
<origin name="http://pkg.oracle.com/solaris/release"/>
</publisher>
</source>
h4. When the installation precess is in this part
13% target-selection completed.
17% ai-configuration completed.
19% target-instantiation completed.
19% Beginning IPS transfer
Creating IPS image
Installing packages from:
solaris
origin: http://pkg.example.com/solaris/
h4. in the install_log file show us this errors:
2012-08-08 20:51:39,653 InstallationLogger.generated-transfer-1184-1 DEBUG Download: text/doctools ...
2012-08-08 20:51:43,156 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/core-os ...
2012-08-08 20:52:03,704 InstallationLogger.generated-transfer-1184-1 DEBUG Download: text/less ...
2012-08-08 20:52:03,788 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/management/rad/module/rad-smf ...
2012-08-08 20:52:03,835 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/library ...
2012-08-08 20:52:30,609 InstallationLogger.generated-transfer-1184-1 DEBUG Cleaning up
2012-08-08 20:52:30,611 InstallationLogger ERROR Error occurred during execution of 'generated-transfer-1184-1' checkpoint.
Traceback (most recent call last):
File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", line 811, in executecheckpoints
checkpoint.execute(dry_run)
File "/usr/lib/python2.6/vendor-packages/solaris_install/transfer/ips.py", line 359, in execute
self._transfer()
File "/usr/lib/python2.6/vendor-packages/solaris_install/transfer/ips.py", line 639, in _transfer
self.api_inst.prepare()
File "/usr/lib/python2.6/vendor-packages/pkg/client/api.py", line 2021, in prepare
self._img.imageplan.preexecute()
File "/usr/lib/python2.6/vendor-packages/pkg/client/imageplan.py", line 2827, in preexecute
p.download()
File "/usr/lib/python2.6/vendor-packages/pkg/client/pkgplan.py", line 406, in download
mfile.wait_files()
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 2857, in wait_files
self._transport._get_files(self)
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 432, in wrapper
return f(instance, fargs, *f_kwargs)
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 1736, in getfiles
self._get_files_list(mfile, filelist)
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 1685, in getfiles_list
raise tfailurex
TransportFailures: 1: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 7558caebcb4a599c08c6a1b1591672f2b3b3cb06.
2: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: c8edd4ff7e100c83ad74ba75a9baeda47348800c.
3: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 91350cb5e1dc88dbbcf2e94e0a05b075f03ba35b.
4: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 85bec186fd71c8a072cb3261aac5a2d26e0bed01.
5: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: feaf36a0752e78974e4cdbd757a2af9dd5f94236.
6: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 93adf874561a2c2e383fa55da1f23cc93f1b24b5.
7: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 5c261f9705a8c604bf3f473f1d76c7f646cedc60.
8: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 81fa4733fa459a553001f8fdf30f49e35067a5ea.
2012-08-08 20:52:30,731 InstallationLogger DEBUG Checkpoints Completed: DOC:+
-> [DataObjectCache] (<solaris_install.data_object.cache.DataObjectCache object at 0xee1b90>)+
     -> [persistent] (DataObjectCacheChild: persistent)+
          -> [auto-install] (<solaris_install.ApplicationData object at 0xee1030>)+
          -> [Engine-DOC-Root-Node] (<solaris_install.engine.EngineData object at 0xecc930>)+
               -> [manifest-parser] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee10d0>)+
               -> [target-discovery] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1230>)+
               -> [target-selection] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee12f0>)+
               -> [ai-configuration] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1410>)+
               -> [var-shared-dataset] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1c30>)+
               -> [target-instantiation] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1750>)+
          -> [discovered] (<solaris_install.target.Target object at 0xee1330>)+
               -> [disk] (Disk: ctd=c2t0d0; volid=None; devpath=/pci@7c0/pci@0/pci@8/scsi@2/sd@0,0; devid=id1,sd@n5000cca334c724bf; prop:dev_type=scsi; prop:dev_vendor=HITACHI; prop:dev_size=148.99gb; keyword: key=boot_disk; is_cdrom=False; label=VTOC; whole_disk=False; write_cache=False)+
                    -> [0] (Slice: name=0; action=preserve, force=False, is_swap=False, tag=2, flag=0, in_use={'used_by': ['exported_zpool'], 'used_name': ['rpool']}; size=148.99gb; start_sector=4768)+
                    -> [2] (Slice: name=2; action=preserve, force=False, is_swap=False, tag=5, flag=1; size=148.99gb; start_sector=0)+
               -> [logical] (Logical: noswap=True; nodump=True)+
          -> [desired] (<solaris_install.target.Target object at 0xede3f0>)+
               -> [logical] (Logical: noswap=False; nodump=False)+
                    -> [rpool] (Zpool: name=rpool; action=create; is_root=True; vdev_list=['c2t0d0s0'])+
                         -> [export] (Filesystem: name=export; action=create; mountpoint=/export)+
                         -> [export/home] (Filesystem: name=export/home; action=create)+
                         -> [solaris] (BE: name=solaris; mountpoint=/a)+
                         -> [vdev] (Vdev: name=vdev; redundancy=none)+
                         -> [swap] (Zvol: name=swap; action=create; use=swap; size=1024m)+
                         -> [dump] (Zvol: name=dump; action=create; use=dump; size=512m)+
                         -> [var] (Filesystem: name=var; action=create; mountpoint=/var)+
               -> [disk] (Disk: ctd=c2t0d0; volid=None; devpath=/pci@7c0/pci@0/pci@8/scsi@2/sd@0,0; devid=id1,sd@n5000cca334c724bf; prop:dev_type=scsi; prop:dev_vendor=HITACHI; prop:dev_size=148.99gb; keyword: key=boot_disk; is_cdrom=False; label=VTOC; whole_disk=False; write_cache=True)+
                    -> [0] (Slice: name=0; action=create, force=True, is_swap=False, tag=2, flag=0; in_zpool=rpool; in_vdev=vdev; size=148.99gb; start_sector=4768)+
     -> [volatile] (DataObjectCacheChild: volatile)+
          -> [apply_sysconfig_dict] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee1050>)+
          -> [orig_default] (ai_instance: name='orig_default' auto_reboot=False; http_proxy='None')+
               -> [target] (<solaris_install.target.Target object at 0xee1d30>)+
                    -> [logical] (Logical: noswap=False; nodump=False)+
                         -> [rpool] (Zpool: name=rpool; action=create; is_root=True; vdev_list=[None])+
                              -> [export] (Filesystem: name=export; action=create; mountpoint=/export)+
                              -> [export/home] (Filesystem: name=export/home; action=create)+
                              -> [solaris] (BE: name=solaris)+
               -> [generated-transfer-1184-1] (<solaris_install.transfer.info.Software object at 0xee1f30>)+
                    -> [transfer] (<solaris_install.transfer.info.IPSSpec object at 0xecc050>)+
                    -> [destination] (<solaris_install.transfer.info.Destination object at 0xecc0b0>)+
                         -> [image] (<solaris_install.transfer.info.Image object at 0xecc130>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc150>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc1b0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc210>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc270>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc2d0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc330>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc390>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc3f0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc450>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc4b0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc510>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc570>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc5d0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc630>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc690>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc6f0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc750>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc7b0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc810>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc870>)+
                              -> [img_type] (<solaris_install.transfer.info.ImType object at 0xee1b70>)+
                    -> [source] (<solaris_install.transfer.info.Source object at 0xecc8b0>)+
                         -> [publisher] (<solaris_install.transfer.info.Publisher object at 0xecc8f0>)+
                              -> [origin] (<solaris_install.transfer.info.Origin object at 0xecc910>)+
          -> [transfer-zpool-cache] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee18f0>)+
          -> [transfer-ai-files] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee15b0>)+
2012-08-08 20:52:30,747 InstallationLogger DEBUG Checkpoints Completed: DOC (xml_format):
<root>
<target name="discovered">
<disk whole_disk="false">
<disk_name name="c2t0d0" name_type="ctd"/>
<disk_prop dev_type="scsi" dev_vendor="HITACHI" dev_size="312461344secs"/>
<disk_keyword key="boot_disk"/>
<slice name="0" action="preserve" force="false" is_swap="false">
<size val="312456576secs" start_sector="4768"/>
</slice>
<slice name="2" action="preserve" force="false" is_swap="false">
<size val="312461344secs" start_sector="0"/>
</slice>
</disk>
<logical noswap="true" nodump="true"/>+
</target>+
<target name="desired">+
<logical noswap="false" nodump="false">+
<zpool name="rpool" action="create" is_root="true">+
<filesystem name="export" action="create" mountpoint="/export" in_be="false"/>+
<filesystem name="export/home" action="create" in_be="false"/>+
<be name="solaris"/>+
<vdev name="vdev" redundancy="none"/>+
<zvol name="swap" action="create" use="swap">+
<size val="1024m"/>+
</zvol>+
<zvol name="dump" action="create" use="dump">+
<size val="512m"/>+
</zvol>+
<filesystem name="var" action="create" mountpoint="/var" in_be="true"/>+
</zpool>+
</logical>+
<disk whole_disk="false">+
<disk_name name="c2t0d0" name_type="ctd"/>+
<disk_prop dev_type="scsi" dev_vendor="HITACHI" dev_size="312461344secs"/>+
<disk_keyword key="boot_disk"/>+
<slice name="0" action="create" force="true" is_swap="false" in_zpool="rpool" in_vdev="vdev">+
<size val="312456576secs" start_sector="4768"/>+
</slice>+
</disk>+
</target>+
<ai_instance auto_reboot="false" name="orig_default">+
<target>+
<logical noswap="false" nodump="false">+
<zpool name="rpool" action="create" is_root="true">+
<filesystem name="export" action="create" mountpoint="/export" in_be="false"/>+
<filesystem name="export/home" action="create" in_be="false"/>+
<be name="solaris"/>+
</zpool>+
</logical>+
</target>+
<software name="generated-transfer-1184-1" type="IPS">+
<software_data>+
<name>pkg:/entire@latest</name>+
<name>pkg:/group/system/solaris-large-server</name>+
</software_data>
<destination>
<image img_root="/a" action="create" index="False">
<facet set="false">facet.locale.*</facet>
<facet set="true">facet.locale.en</facet>
<facet set="true">facet.locale.en_US</facet>
<facet set="true">facet.locale.es</facet>
<facet set="true">facet.locale.es_ES</facet>
</image>
</destination>
<source>
<publisher name="solaris">
<origin name="http://pkg.oracle.com/solaris/release"/>
</publisher>
</source>
</software>
</ai_instance>
</root>
2012-08-08 20:52:30,749 InstallationLogger CRITICAL Failed Checkpoints:
2012-08-08 20:52:30,803 InstallationLogger ERROR
2012-08-08 20:52:30,855 InstallationLogger ERROR generated-transfer-1184-1
2012-08-08 20:52:30,907 InstallationLogger ERROR
2012-08-08 20:52:30,960 InstallationLogger ERROR Checkpoint execution error:
2012-08-08 20:52:31,012 InstallationLogger ERROR
2012-08-08 20:52:31,064 InstallationLogger ERROR 1: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 7558caebcb4a599c08c6a1b1591672f2b3b3cb06.
2012-08-08 20:52:31,117 InstallationLogger ERROR 2: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: c8edd4ff7e100c83ad74ba75a9baeda47348800c.
2012-08-08 20:52:31,169 InstallationLogger ERROR 3: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 91350cb5e1dc88dbbcf2e94e0a05b075f03ba35b.
2012-08-08 20:52:31,222 InstallationLogger ERROR 4: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 85bec186fd71c8a072cb3261aac5a2d26e0bed01.
2012-08-08 20:52:31,274 InstallationLogger ERROR 5: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: feaf36a0752e78974e4cdbd757a2af9dd5f94236.
2012-08-08 20:52:31,326 InstallationLogger ERROR 6: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 93adf874561a2c2e383fa55da1f23cc93f1b24b5.
2012-08-08 20:52:31,379 InstallationLogger ERROR 7: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 5c261f9705a8c604bf3f473f1d76c7f646cedc60.
2012-08-08 20:52:31,431 InstallationLogger ERROR 8: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 81fa4733fa459a553001f8fdf30f49e35067a5ea.
2012-08-08 20:52:31,484 InstallationLogger ERROR
2012-08-08 20:52:31,536 InstallationLogger INFO Automated Installation Failed. See install log at /system/volatile/install_log
2012-08-08 20:52:31,588 InstallationLogger DEBUG Shutting down Progress Handler
h4. Is something about:
2012-08-08 20:52:30,611 InstallationLogger ERROR Error occurred during execution of 'generated-transfer-1184-1' checkpoint.
Traceback (most recent call last):
File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", line 811, in executecheckpoints
checkpoint.execute(dry_run)
2012-08-08 20:52:30,749 InstallationLogger CRITICAL Failed Checkpoints:
2012-08-08 20:52:30,803 InstallationLogger ERROR
2012-08-08 20:52:30,855 InstallationLogger ERROR generated-transfer-1184-1
2012-08-08 20:52:30,907 InstallationLogger ERROR
2012-08-08 20:52:30,960 InstallationLogger ERROR Checkpoint execution error:
h4. Somebody knows about this error?

The chash failures indicate that either the repository you're using has corrupt content for those files, or the files are being corrupted on download. The latter is more likely, usually a result of badly-behaved http proxies.

Error 70025 in Measurement and Automation Explorer

After a clean reboot of the system I receive Error -70025 ("Return Buffer is not empty..") in the Measurement and Automation Explorer. When I click on "Clear RDB" which is supposed to solve the problem, it says "Error clearing the return data buffer". In the status tab, all LEDs are flashing (Error Code varying from 0xFFFF to 0x0182).
First, I simply tried to remove the motion controller (it's a NI PCI-7334) from the MAX tab which did not work. Then, I tried to repair the installation of all NI tools but this didn't help either.
I'm working with NI Motion 8.4 and MAX 5.4.0f0 on Windows XP.
Do you have any idea how to solve this problem? Currently, I cannot run the motor at all.
Thanks,
Jürgen
edit: I just realize that the controlller is listed as PXI-7334 in the Windows Device Manager but in fact it is a PCI-7334. Would this explain the problem?
update: Forcing the installation of the PCI-334 driver does not make any difference.

Hi Jürgen,
you can find the description of occurence and solution for this error here.
Please try it.
When it dosen't solve your issue please contact me again.
Kind Regards,
Philipp K.
Applications Engineer | NI-Germany

Enable Automated Installation Problems

I'm having trouble completing a NetRestore/NetInstall restore to computer. I have a Mac Mini that is firewired to a Mac Mini Server 10.6.2. I'm using the Mac Mini as the source.
Whenever I create either a NetRestore or NetInsall of the Mac Mini it installs fine to another Intel Mac without trouble as long as I either use the non-customized button or do a customize with only the following config...
Create image
type: Netinstall
Install Volume: graphics
Save to: NetBootSP0
Image Name:
Network Disk: Netinstall Graphics Erase
Image Index: 1580
Description: Netinstall Graphics Erase
But when I add in Enable Automated Installation...
Define Image Source: graphics
Enable Automated Installation: auto
Erase Before Installing: English
Create image
type: Netinstall
Install Volume: graphics
Save to: NetBootSP0
Image Name:
Network Disk: Netinstall Graphics Erase
Image Index: 1580
Description: Netinstall Graphics Erase
I'll get a big Yellow error message after a couple of minutes: Install failed: The Installer could not start up the computer from the disk, auto. Try selecting your disk using the Startup Disk utility.
This problem only happens when I use Enable Automated Installation. I've never had trouble with 10.5 Leopard Server doing this. At first I thought it was the workflows taken from 10.5 but then I created new ones though the same problem continued.
Also, even though I've included the Install Volume name the destination drive it never gets renamed that. It just keeps the original name, not that this matters that much to me. The big problem is I can't get the Enable Automated Installation to work.
I've tried both NetInstall and the NetRestore tab but neither work with using Enable Automate Installation
Any ideas? I've tried Apple Tech Support but no help so far.
Thanks,
Todd
(here are some other errors that show up in the log...)
Feb 23 13:29:18 localhost Unknown[91]: 2010-02-23 08:29:18.761 Mac OS X Installer[90:9703] no system packages found
Feb 23 13:29:18 localhost Unknown[91]: 2010-02-23 08:29:18.762 Mac OS X Installer[90:9703] No or Invalid system receipts found on /Volumes/auto
Feb 23 13:29:18 localhost Unknown[91]: 2010-02-23 08:29:18.764 Mac OS X Installer[90:9703] Attempting fallback using: /System/Library/PrivateFrameworks/SystemMigration.framework/Resources/FallbackS ystemFiles.plist
Feb 23 13:29:18 localhost Unknown[91]: 2010-02-23 08:29:18.889 Mac OS X Installer[90:9703] Finding system files...
Feb 23 13:29:19 localhost Unknown[91]: 2010-02-23 08:29:19.270 Mac OS X Installer[90:9703] Writing system path cache.
Feb 23 13:29:19 localhost Unknown[91]: 2010-02-23 08:29:19.276 Mac OS X Installer[90:9703] Error writing cache to /Volumes/auto/Library/Caches/com.apple.FindSystemFiles.plist
Feb 23 13:29:19 localhost Unknown[91]: 2010-02-23 08:29:19.291 Mac OS X Installer[90:9703] Failed to enumerate /Volumes/auto/Library/Caches, cannot prune (
Feb 23 13:29:19 localhost Unknown[91]: "com.apple.userpictureCache"
Feb 23 13:29:19 localhost Unknown[91]: )
Feb 23 13:29:19 localhost OSInstaller[90]: Initial free size : 79.61 GB
Feb 23 13:29:19 localhost OSInstaller[90]: Expected system size : 8 KB
Feb 23 13:29:19 localhost OSInstaller[90]: * No package reference found for com.apple.server.ASRPackage -- 1.0.0.4390000.0
Feb 23 13:29:19 localhost OSInstaller[90]: Reserving 1073741824 for extraction
Feb 23 13:29:19 localhost OSInstaller[90]: Reserving 0 for download
Feb 23 13:29:19 localhost OSInstaller[90]: Performing volume consistency check on 'auto'.
Feb 23 13:29:31 localhost OSInstaller[90]: Checking Volume
Feb 23 13:29:31 localhost OSInstaller[90]: Checking Journaled HFS Plus volume.
Feb 23 13:29:31 localhost OSInstaller[90]: Checking extents overflow file.
Feb 23 13:29:31 localhost OSInstaller[90]: Checking catalog file.
Feb 23 13:29:32 localhost OSInstaller[90]: Checking multi-linked files.
Feb 23 13:29:32 localhost OSInstaller[90]: Checking catalog hierarchy.
Feb 23 13:29:32 localhost OSInstaller[90]: Checking extended attributes file.
Feb 23 13:29:32 localhost OSInstaller[90]: Checking volume bitmap.
Feb 23 13:29:32 localhost OSInstaller[90]: Checking volume information.
Feb 23 13:29:32 localhost OSInstaller[90]: The volume auto appears to be OK.
Feb 23 13:29:33 localhost OSInstaller[90]: Volume repair complete.
Feb 23 13:29:33 localhost OSInstaller[90]: Updating boot support partitions for the volume as required.
Feb 23 13:29:33 localhost OSInstaller[90]: Volume passed consistency checks.
Feb 23 13:29:33 localhost OSInstaller[90]: Copying/Downloading selected packages locally
Feb 23 13:29:33 localhost OSInstaller[90]: Creating mutable product on /Volumes/auto/Mac OS X Install Data
Feb 23 13:29:33 localhost OSInstaller[90]: Using packages from product at /Volumes/auto/Mac OS X Install Data
Feb 23 13:29:33 localhost OSInstaller[90]: Linked to PackageKit-67
Feb 23 13:29:33 localhost OSInstaller[90]: Remote package size (0) : available size (79611281408)
Feb 23 13:29:33 localhost OSInstaller[90]: Copying remote packages (0) to mutable product.
Feb 23 13:29:33 localhost OSInstaller[90]: Configuring volume "auto"
Feb 23 13:29:33 localhost OSInstaller[90]: Preparing disk for Netbooted OS Install.
Feb 23 13:29:33 localhost OSInstaller[90]: Volume disk0s2 mounted at /Volumes/auto is ready
Feb 23 13:29:33 localhost OSInstaller[90]: Preparing disk for local booted OS Install.
Feb 23 13:29:33 localhost OSInstaller[90]: Physical memory statistics immediately before turning on virtual memory backing store:
Feb 23 13:29:33 localhost OSInstaller[90]: Physical Memory Allocation: 452 MB wired, 3 MB trapped, 76 MB active, 42 MB inactive, 2499 MB free, 2617 MB usable, 3072 MB total
Feb 23 13:29:33 localhost OSInstaller[90]: Activated virtual memory backing store at mount point '/Volumes/auto'
Feb 23 13:29:33 localhost OSInstaller[90]: Preparing disk for local booted install.
Feb 23 13:29:33 localhost OSInstaller[90]: Creating installation log on volume "auto"
Feb 23 13:29:33 localhost OSInstaller[90]: IFPKInstallElement (1 packages)
Feb 23 13:29:33 localhost OSInstaller[90]: PackageKit: ----- Begin install -----
Feb 23 13:29:33 localhost OSInstaller[90]: PackageKit: request=PKInstallRequest <1 packages, destination=/Volumes/auto>
Feb 23 13:29:33 localhost OSInstaller[90]: PackageKit: packages=(\n "PKJaguarPackage <file://localhost/System/Installation/Packages/ASRInstall.pkg>"\n)
Feb 23 13:29:33 localhost OSInstaller[90]: PackageKit: updatedyld_sharedcache -root /Volumes/auto/.OSInstallSandbox-tmp/Root
Feb 23 13:29:33 localhost OSInstaller[90]: updatedyld_sharedcache failed: /Volumes/auto/.OSInstallSandbox-tmp/Root/var/db/dyld/sharedregionroots/ does not exist, errno=2
Feb 23 13:29:33 localhost OSInstaller[90]: updatedyld_sharedcache exited with 1
Feb 23 13:29:33 localhost OSInstaller[90]: PackageKit: Shoving /Volumes/auto/.OSInstallSandbox-tmp/Root (0 items) to /Volumes/auto
Feb 23 13:29:33 localhost OSInstaller[90]: PackageKit: kextcache -update-volume /Volumes/auto
Feb 23 13:29:34 localhost OSInstaller[90]: kextcache: /Volumes/auto: no /usr/standalone/bootcaches.plist; nothing to do.
Feb 23 13:29:34 localhost OSInstaller[90]: Installed "Apple Software Restore Image" ()
Feb 23 13:29:34 localhost OSInstaller[90]: PackageKit: ----- End install -----
Feb 23 13:29:34 localhost OSInstaller[90]: Writing installation cookies
Feb 23 13:29:34 localhost OSInstaller[90]: Could not write configuration file /Volumes/auto/Library/Preferences/.GlobalPreferences.plist
Feb 23 13:29:34 localhost OSInstaller[90]: Unable to write InstallType cookie file for Setup Assistant to pick up.
Feb 23 13:29:34 localhost OSInstaller[90]: Finalize disk "auto" for OS Installation
Feb 23 13:29:34 localhost OSInstaller[90]: Finalizing Disk for OS Install
Feb 23 13:29:35 localhost OSInstaller[90]: Unable to set 'auto' as boot disk: The bless tool was unable to set the current boot disk
Feb 23 13:29:35 localhost OSInstaller[90]: Install failed: The Installer could not start up the computer from the disk ‚Äúauto‚Äù. Try selecting your disk using the Startup Disk utility.
Feb 23 13:29:36 localhost OSInstaller[90]: Allowing machine sleep.
Feb 23 13:29:36 localhost OSInstaller[90]: Memory statistics for 'Install Failed' pane:
Feb 23 13:29:36 localhost OSInstaller[90]: Physical Memory Allocation: 242 MB wired, 3 MB trapped, 287 MB active, 43 MB inactive, 2497 MB free, 2827 MB usable, 3072 MB total
Feb 23 13:31:02 localhost Unknown[91]: 2010-02-23 13:31 Mac OS X Installer[90] (CarbonCore.framework) FSEventStreamStart: ERROR: FSEvents_connect() => Unknown service name (1102)
Feb 23 13:31:04 localhost OSInstaller[90]: NetworkBrowser failed to launch "/usr/bin/nmblookup" (No such file or directory)

Still borked after all these months...ugh. I get the feeling this is a very low priority for Apple.
I'll include my latest log from my automated netrestore:
Mar 31 01:38:17 localhost Unknown[86]: Launching the Installer using /etc/minstallconfig.xml file with language English.
Mar 31 01:38:41 localhost configd[66]: subnetroute_ifindex: can't get interface name
Mar 31 01:38:43 localhost OSInstaller[87]: Folder Manager is being asked to create a folder (cach) while running as uid 0
Mar 31 01:38:43 localhost OSInstaller[87]: Mac OS X Installer application started
Mar 31 01:38:43 localhost OSInstaller[87]: 1 display(s) found.
Mar 31 01:38:43 localhost OSInstaller[87]: Display[1] is using OpenGL acceleration.
Mar 31 01:38:43 localhost OSInstaller[87]: @(#)PROGRAM:Install PROJECT:Install-574
Mar 31 01:38:43 localhost OSInstaller[87]: @(#)PROGRAM:Mac OS X Installer PROJECT:OSInstaller-255
Mar 31 01:38:43 localhost OSInstaller[87]: Hardware: Macmini3,1 @ 2.26 GHz (x 2), 4096 MB RAM
Mar 31 01:38:43 localhost OSInstaller[87]: Running OS Build: Mac OS X 10.6.2 (10C540)
Mar 31 01:38:43 localhost OSInstaller[87]: Env: DYLDNO_FIXPREBINDING=1
Mar 31 01:38:43 localhost OSInstaller[87]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin
Mar 31 01:38:43 localhost OSInstaller[87]: Env: PWD=/
Mar 31 01:38:43 localhost OSInstaller[87]: Env: SHLVL=1
Mar 31 01:38:43 localhost OSInstaller[87]: Env: _=/System/Installation/CDIS/Mac OS X Installer.app/Contents/MacOS/Mac OS X Installer
Mar 31 01:38:45 localhost OSInstaller[87]: Automated Install: Found requested target at /Volumes/Macintosh HD.
Mar 31 01:38:46 localhost OSInstaller[87]: Allowing machine sleep.
Mar 31 01:38:46 localhost OSInstaller[87]: Preventing machine sleep.
Mar 31 01:38:46 localhost OSInstaller[87]: InstallerStatusNotifications plugin loaded
Mar 31 01:38:46 localhost OSInstaller[87]: =============================================================================== =
Mar 31 01:38:46 localhost OSInstaller[87]: Choices selected for installation:
Mar 31 01:38:46 localhost OSInstaller[87]: Install: "Apple Software Restore Image"
Mar 31 01:38:46 localhost OSInstaller[87]: ASRInstall.pkg : com.apple.server.ASRPackage : 1.0.0.4420000.0
Mar 31 01:38:46 localhost OSInstaller[87]: =============================================================================== =
Mar 31 01:38:46 localhost OSInstaller[87]: It took 0.00 seconds to summarize the package selections.
Mar 31 01:38:46 localhost OSInstaller[87]: Memory statistics for 'Installing' pane:
Mar 31 01:38:46 localhost OSInstaller[87]: Physical Memory Allocation: 490 MB wired, 258 MB trapped, 72 MB active, 32 MB inactive, 3244 MB free, 3348 MB usable, 4096 MB total
Mar 31 01:38:46 localhost OSInstaller[87]: Remote Install Assistant found at 1024:(null)
Mar 31 01:38:46 localhost OSInstaller[87]: Memory statistics for 'Install Mac OS X' pane:
Mar 31 01:38:46 localhost OSInstaller[87]: Physical Memory Allocation: 493 MB wired, 258 MB trapped, 73 MB active, 32 MB inactive, 3240 MB free, 3345 MB usable, 4096 MB total
Mar 31 01:38:46 localhost OSInstaller[87]: -[IFPKGDerivedDocument sortedPackageLocations]: result = (\n "file://localhost"\n)
Mar 31 01:38:46 localhost runner[133]: Administrator authorization granted.
Mar 31 01:38:46 localhost OSInstaller[87]: PK will install package file://localhost/System/Installation/Packages/ASRInstall.pkg (0 b)
Mar 31 01:38:46 localhost OSInstaller[87]: Total install size including padding: 1073741824 b
Mar 31 01:38:46 localhost OSInstaller[87]: Starting installation:
Mar 31 01:38:46 localhost OSInstaller[87]: Calculating expected install size requirements
Mar 31 01:38:46 localhost Unknown[88]: 2010-03-30 18:38:46.808 Mac OS X Installer[87:a303] Looking for system packages
Mar 31 01:38:46 localhost Unknown[88]: 2010-03-30 18:38:46.933 Mac OS X Installer[87:a303] Finding system files...
Mar 31 01:38:48 localhost Unknown[88]: 2010-03-30 18:38:48.582 Mac OS X Installer[87:a303] Writing system path cache.
Mar 31 01:39:11 localhost OSInstaller[87]: Reserving additional 500MB for reaping SnowLeopard volume
Mar 31 01:39:11 localhost OSInstaller[87]: Initial free size : 155.12 GB
Mar 31 01:39:11 localhost OSInstaller[87]: Expected system size : 3.32 GB
Mar 31 01:39:11 localhost OSInstaller[87]: * No package reference found for com.apple.server.ASRPackage -- 1.0.0.4420000.0
Mar 31 01:39:11 localhost OSInstaller[87]: Reserving 1073741824 for extraction
Mar 31 01:39:11 localhost OSInstaller[87]: Reserving 0 for download
Mar 31 01:39:11 localhost OSInstaller[87]: Performing volume consistency check on 'Macintosh HD'.
Mar 31 01:39:23 localhost OSInstaller[87]: Checking Volume
Mar 31 01:39:23 localhost OSInstaller[87]: Checking Journaled HFS Plus volume.
Mar 31 01:39:23 localhost OSInstaller[87]: Checking extents overflow file.
Mar 31 01:39:23 localhost OSInstaller[87]: Checking catalog file.
Mar 31 01:39:26 localhost OSInstaller[87]: Checking multi-linked files.
Mar 31 01:39:26 localhost OSInstaller[87]: Checking catalog hierarchy.
Mar 31 01:39:33 localhost OSInstaller[87]: Checking extended attributes file.
Mar 31 01:39:38 localhost OSInstaller[87]: Checking volume bitmap.
Mar 31 01:39:38 localhost OSInstaller[87]: Checking volume information.
Mar 31 01:39:38 localhost OSInstaller[87]: The volume Macintosh HD appears to be OK.
Mar 31 01:39:38 localhost OSInstaller[87]: Volume repair complete.
Mar 31 01:39:38 localhost OSInstaller[87]: Updating boot support partitions for the volume as required.
Mar 31 01:39:39 localhost OSInstaller[87]: Volume passed consistency checks.
Mar 31 01:39:39 localhost OSInstaller[87]: Copying/Downloading selected packages locally
Mar 31 01:39:39 localhost OSInstaller[87]: Creating mutable product on /Volumes/Macintosh HD/Mac OS X Install Data
Mar 31 01:39:40 localhost OSInstaller[87]: Using packages from product at /Volumes/Macintosh HD/Mac OS X Install Data
Mar 31 01:39:40 localhost OSInstaller[87]: Linked to PackageKit-67
Mar 31 01:39:40 localhost OSInstaller[87]: Remote package size (0) : available size (155120869376)
Mar 31 01:39:40 localhost OSInstaller[87]: Copying remote packages (0) to mutable product.
Mar 31 01:39:40 localhost OSInstaller[87]: Preparing previous system for upgrade
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/Desktop DF to: /Volumes/Macintosh HD/Recovered Items/Desktop DF\nReason: The file “Desktop DF” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/Developer to: /Volumes/Macintosh HD/Recovered Items/Developer\nReason: The file “Developer” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/.com.apple.timemachine.supported to: /Volumes/Macintosh HD/Recovered Items/.com.apple.timemachine.supported\nReason: The file “.com.apple.timemachine.supported” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/Previous Systems to: /Volumes/Macintosh HD/Recovered Items/Previous Systems\nReason: The file “Previous Systems” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/.Archived_Directories^M to: /Volumes/Macintosh HD/Recovered Items/.Archived_Directories^M\nReason: The file “.Archived_Directories^M” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/Desktop DB to: /Volumes/Macintosh HD/Recovered Items/Desktop DB\nReason: The file “Desktop DB” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/Previous System to: /Volumes/Macintosh HD/Recovered Items/Previous System\nReason: The file “Previous System” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/.TemporaryItems to: /Volumes/Macintosh HD/Recovered Items/.TemporaryItems\nReason: The file “.TemporaryItems” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/mach.sym to: /Volumes/Macintosh HD/Recovered Items/mach.sym\nReason: The file “mach.sym” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/Shutdown Check to: /Volumes/Macintosh HD/Recovered Items/Shutdown Check\nReason: The file “Shutdown Check” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/Trash to: /Volumes/Macintosh HD/Recovered Items/Trash\nReason: The file “Trash” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/cores to: /Volumes/Macintosh HD/Recovered Items/cores\nReason: The file “cores” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/Backups.backupdb to: /Volumes/Macintosh HD/Recovered Items/Backups.backupdb\nReason: The file “Backups.backupdb” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/Network Trash Folder to: /Volumes/Macintosh HD/Recovered Items/Network Trash Folder\nReason: The file “Network Trash Folder” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/AppleShare PDS to: /Volumes/Macintosh HD/Recovered Items/AppleShare PDS\nReason: The file “AppleShare PDS” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/TheVolumeSettingsFolder to: /Volumes/Macintosh HD/Recovered Items/TheVolumeSettingsFolder\nReason: The file “TheVolumeSettingsFolder” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/Temporary Items to: /Volumes/Macintosh HD/Recovered Items/Temporary Items\nReason: The file “Temporary Items” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/automount to: /Volumes/Macintosh HD/Recovered Items/automount\nReason: The file “automount” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/Cleanup At Startup to: /Volumes/Macintosh HD/Recovered Items/Cleanup At Startup\nReason: The file “Cleanup At Startup” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/Previous Systems.localized to: /Volumes/Macintosh HD/Recovered Items/Previous Systems.localized\nReason: The file “Previous Systems.localized” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/TheFindByContentFolder to: /Volumes/Macintosh HD/Recovered Items/TheFindByContentFolder\nReason: The file “TheFindByContentFolder” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/AppleInternal to: /Volumes/Macintosh HD/Recovered Items/AppleInternal\nReason: The file “AppleInternal” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Did not move file from: /Volumes/Macintosh HD/VM Storage to: /Volumes/Macintosh HD/Recovered Items/VM Storage\nReason: The file “VM Storage” doesn’t exist.
Mar 31 01:39:40 localhost OSInstaller[87]: Configuring volume "Macintosh HD"
Mar 31 01:39:40 localhost OSInstaller[87]: Preparing disk for Netbooted OS Install.
Mar 31 01:39:40 localhost OSInstaller[87]: Volume disk0s2 mounted at /Volumes/Macintosh HD is ready
Mar 31 01:39:40 localhost OSInstaller[87]: Preparing disk for local booted OS Install.
Mar 31 01:39:40 localhost OSInstaller[87]: Physical memory statistics immediately before turning on virtual memory backing store:
Mar 31 01:39:40 localhost OSInstaller[87]: Physical Memory Allocation: 883 MB wired, 258 MB trapped, 77 MB active, 8 MB inactive, 2870 MB free, 2955 MB usable, 4096 MB total
Mar 31 01:39:40 localhost OSInstaller[87]: Activated virtual memory backing store at mount point '/Volumes/Macintosh HD'
Mar 31 01:39:40 localhost OSInstaller[87]: Preparing disk for local booted install.
Mar 31 01:39:40 localhost OSInstaller[87]: Creating installation log on volume "Macintosh HD"
Mar 31 01:39:40 localhost OSInstaller[87]: Reaping previous system
Mar 31 01:41:09 localhost OSInstaller[87]: System Reaper: free space before: 155.12 GB
Mar 31 01:41:09 localhost OSInstaller[87]: System Reaper: free space after : 158.54 GB
Mar 31 01:41:09 localhost OSInstaller[87]: System Reaper: free space diff : 3.42 GB
Mar 31 01:41:10 localhost OSInstaller[87]: System Reaper: Postflight ok (157.57 GB remaining)
Mar 31 01:41:10 localhost OSInstaller[87]: IFPKInstallElement (1 packages)
Mar 31 01:41:10 localhost OSInstaller[87]: PackageKit: ----- Begin install -----
Mar 31 01:41:10 localhost OSInstaller[87]: PackageKit: request=PKInstallRequest <1 packages, destination=/Volumes/Macintosh HD>
Mar 31 01:41:10 localhost OSInstaller[87]: PackageKit: packages=(\n "PKJaguarPackage <file://localhost/System/Installation/Packages/ASRInstall.pkg>"\n)
Mar 31 01:41:10 localhost OSInstaller[87]: PackageKit: updatedyld_sharedcache -root /Volumes/Macintosh HD/.OSInstallSandbox-tmp/Root
Mar 31 01:41:10 localhost OSInstaller[87]: updatedyld_sharedcache failed: /Volumes/Macintosh HD/.OSInstallSandbox-tmp/Root/var/db/dyld/sharedregionroots/ does not exist, errno=2
Mar 31 01:41:10 localhost OSInstaller[87]: updatedyld_sharedcache exited with 1
Mar 31 01:41:10 localhost OSInstaller[87]: PackageKit: Shoving /Volumes/Macintosh HD/.OSInstallSandbox-tmp/Root (0 items) to /Volumes/Macintosh HD
Mar 31 01:41:10 localhost OSInstaller[87]: PackageKit: kextcache -update-volume /Volumes/Macintosh HD
Mar 31 01:41:10 localhost OSInstaller[87]: kextcache: /Volumes/Macintosh HD: no /usr/standalone/bootcaches.plist; nothing to do.
Mar 31 01:41:10 localhost OSInstaller[87]: Installed "Apple Software Restore Image" ()
Mar 31 01:41:10 localhost OSInstaller[87]: PackageKit: ----- End install -----
Mar 31 01:41:11 localhost OSInstaller[87]: Writing installation cookies
Mar 31 01:41:11 localhost OSInstaller[87]: Could not write configuration file /Volumes/Macintosh HD/Library/Preferences/.GlobalPreferences.plist
Mar 31 01:41:11 localhost OSInstaller[87]: Unable to write InstallType cookie file for Setup Assistant to pick up.
Mar 31 01:41:11 localhost OSInstaller[87]: Finalize disk "Macintosh HD" for OS Installation
Mar 31 01:41:11 localhost OSInstaller[87]: Finalizing Disk for OS Install
Mar 31 01:41:11 localhost OSInstaller[87]: Unable to set 'Macintosh HD' as boot disk: The bless tool was unable to set the current boot disk
Mar 31 01:41:11 localhost OSInstaller[87]: Install failed: The Installer could not start up the computer from the disk “Macintosh HD”. Try selecting your disk using the Startup Disk utility.
Mar 31 01:41:12 localhost OSInstaller[87]: Allowing machine sleep.
Mar 31 01:41:12 localhost OSInstaller[87]: Memory statistics for 'Install Failed' pane:
Mar 31 01:41:12 localhost OSInstaller[87]: Physical Memory Allocation: 563 MB wired, 259 MB trapped, 192 MB active, 19 MB inactive, 3063 MB free, 3274 MB usable, 4096 MB total

Impossible de simuler avec measurement and automation version 4.6

Bonjour,
quelqu'un saurait-i me dire pourquoi je ne vois pas apparaître "Periphériques NI-DAQmx" dans la l'arborescence "Périphériques et interfaces" de Measurement and automation explorer (4.6).
Est-ce des modules de LabVIEW (7.1) que j'aurais hommis d'installer (comme des drivers DAQmx, ou autres), est-cer la version de Measurement and automation explorer qui me créé ce problème ???
Je n'arrive pas à comprendre sachant que sur mon PC portable je n'ai aucun problème de ce type. (Il est vrai que sur mon portable, j'ai la version LabVIEW 8.5 et la version Measurement and automation explorer 4.3.
Bonne journée à vous tous
Edouard
Résolu !
Accéder à la solution.

Bonjour, as-tu installé le driver DAQmx ? tu peux verifier sous MAX -> Logiciels -> NI-DAQmx
Luc Desruelle | Voir mon profil | LabVIEW Code & blog
Co-auteur livre LabVIEW : Programmation et applications
CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW

GPIB non reconnu par Measurement and Automation

Bonjour,
J'ai installe une carte "GPIB-PCI 12.002 (AMCC)" sur ma machine qui tourne sous Windows 2000.
Windows reconnait parfaitement le peripherique et pour lui la carte fonctionne correctement.
Cependant dans l'explorateur "Measurement and Automation" de labVIEW la carte n'apparait pas du tout.
(meme en actualisant l'explorateur plusieurs fois, la carte n'apparait pas).
Merci de bien vouloir m'aider.

National Instruments Corporate n'a malheureusement pas les ressources nécessaires pour répondre aux questions posées en français. Cependant, ces questions seront redirigées vers le bureau français, National Instruments France.
S'il vous plait contacter National Instruments France á Support Technique

Measurement and automation

hi to every one few days ago i had installed labview 7.0
and i have made serial vi to read and write data from comport1 ,
i used visa resource name to access the comport3F8 etc but thier is no
comport and others port is visible ,and when i run it then following message appear "measurement automation is not installled"

Make sure you have Measurement and Automation Explorer (MAX) and NI-VISA drivers installed. These should all be located on the device drivers CD.
If VISA is properly installed, you should see COM1, and whatever Com ports you have installed in your system, both in MAX and in a VISA resource constant or control. I'm not sure what you mean by comport 3F8. That sounds like one of the old ways of referring to serial ports by way of their hardware address. Its been years since I've seen that designation, I don't think it was information I ever really needed to know then, and I'm sure I've never seen it used in Labview.

Problems with Measurement and Automation Explorer (MAX)

Hello LabVIEWers,
I have been having a serious problem getting MAX to start and to remain stable. Here are the specifics:I am running LabVIEW 8.5 Full Development System on a Dell PC with 1GB of RAM and plenty of hard drive space. The OS is XP Pro and I also have McAfee Enterprise Virus Scan software. MAX will start-up and appear to run for a few minutes and then the software bombs out. I get a "Measurement and Automation Explorer has encountered a problem and has to close" pop-up message. To fix the problem, I have uninstalled all NI software using MSI Blast. I have wiped the registry clean of NI keys as per instructions in previous posts. I have deleted any remaining NI software on teh hard drive including C:\program files\national instruments and C:\Documents and Settings\All Users\Application Data\National Instruments. I have then restarted the machine and did a complete fresh install from CD's, DVD's, and the harddrive (CD's written to hardrive and DVD written to harddrive first). I installed first the LabVIEW and then I installed the Device Drivers. I restarted the machine between installs. I have even installed the updated NIDAQ 8.6. After which I set protections on the NI directories to read/write. Ok, basically I have done all these things numerous times and I still cannot get things to work correctly.
I was able to get into MAX for a little while (it is somewhat stable immediately after a fresh reinstall). I defined 4 Simulated DAQmx devices and none of them acted like they were simulated. I received various errors saying that the device was not found or could not be started. So I basically could not run my software with the simulated devices. LabVIEW sometimes seems to work ok but just now, I got a "Error loading nidmm_32.dll, initialization routine failed" error. I also get the same error for nilvaiu.dll. Both of these DLLs are in the C:\Program Files\IVI\Bin and c:\windows\system32 directories respectively and prior to the last time I started the software, all worked ok with LabVIEW.
Is my computer failing? Are there any other options to getting this installed without probems?
Please help.
Michael Froehlich

Duplicate Post
Keep discussion here
National Instruments
WSN/Wireless DAQ Product Support Engineer

I have installed the agent 10 or 15 times and one installation hasfailed, no error appeared during the installation but I am havinginconsistent issues with my ethernet card not working here and there. Werebooted and can log into Novell client but th

I have installed the agent 10 or 15 times and one installation has failed, no error appeared during the installation but I am having inconsistent issues with my ethernet card not working here and there. We rebooted and can log into Novell client but the login prompt did not appear for ESM client or the icon was not in the systray. Everything seems to work, besides at times (a couple times today) it terminates his ethernet card/connection. I would re-image his computer but he has several applications and it would take several hours, so I am hoping someone has an idea to fix this issue. So I was trying to figure out why he did not get the prompt to login and why it's not in the systray and it appears to not have completed the install? I checked the add/remove programs, its not listed within their, I also checked the registry and found nothing for endpoint within their, but the files are within c:\program files\novell\zenworks endpoint security.
I have also tried uninstalling it but that fails due to it "not being installed", and it will not reinstall over itself either.
I did notice that stuninstdrv.exe is running in task manager. Any help would be great...
Windows xp sp3
ESM 3.5.154
Thanks,
Andy

If you are searching the registry, check for the "Senforce" string. It should be at HKLM\Software\Senforce
Try running the install program for the ZSC with the following command line:
setup.exe /V"STUNINSTALL=1"
If you've specified an uninstall password, try this one instead:
setup.exe /V"STUNINSTALL=1 STUIP=password"" (please note the double quote at the end)
Let me know if that helped you.
Daniel
>>>
From: Andy_DeWees<[email protected] du>
To:novell.support.zenworks.endpoint-security-management
Date: 2/5/2009 12:52 PM
Subject: I have installed the agent 10 or 15 times and one installation hasfailed, no error appeared during the installation but I am havinginconsistent issues with my ethernet card not working here and there. Werebooted and can log into Novell client but the login prompt did not appearfor ESM client or the icon was not in the systray. Everything seems towork, besides at times (a couple times today) it terminates his ethernetcard/connection. I would re-image his computer but he has severalapplications and
I have installed the agent 10 or 15 times and one installation has failed, no error appeared during the installation but I am having inconsistent issues with my ethernet card not working here and there. We rebooted and can log into Novell client but the login prompt did not appear for ESM client or the icon was not in the systray. Everything seems to work, besides at times (a couple times today) it terminates his ethernet card/connection. I would re-image his computer but he has several applications and it would take several hours, so I am hoping someone has an idea to fix this issue. So I was trying to figure out why he did not get the prompt to login and why it's not in the systray and it appears to not have completed the install? I checked the add/remove programs, its not listed within their, I also checked the registry and found nothing for endpoint within their, but the files are within c:\program files\novell\zenworks endpoint security.
I have also tried uninstalling it but that fails due to it "not being installed", and it will not reinstall over itself either.
I did notice that stuninstdrv.exe is running in task manager. Any help would be great...
Windows xp sp3
ESM 3.5.154
Thanks,
Andy

How can I get all the options of Field Point Explorer 3.0.2 in Measurement and Automation Explorer 3.1?

I am a student using LabVIEW and Compact Field Point to implement a
senior design project in Electrical and Computer Engineering. We
have LabVIEW 7.1 and a cFP-2020 and additional modules. We are
trying to use the CTR-500 module to output a pulse train to drive a
stepper motor. We have found instructions online of how to do
this, but they all use Field Point Explorer. The instructions
make use of options in Field Point Explorer that are not included in
Measurement and Automation Explorer (the software included with the
cFP).
I have downloaded Field Point Explorer 3.0.2 and followed the
directions. Now, in LabVIEW, when I using the newly created .iak
file, I get a dialogue asking to find the SubVI: 'FP Read (Float Array
-IO).vi'. Included with LabVIEW are subvis for FP Read, but not
with the float array part. So I figure I cannot use Field Point
Explorer created .iaks with LabVIEW 7.1. So how cannot I access
the same options in Measurement and Automation that I was able to find
in Field Point Explorer?
Thanks

Hi,
FieldPoint Explorer is no longer used to configure FieldPoint systems. However, I do not think that the configuring your system in FieldPoint Explorer is causing the error.
FieldPoint systems are now setup in Measurement and Automation Explorer (MAX). Information on setting up FieldPoint systems in MAX can be found in the MAX help under: Installed Products>> FieldPoint. Also, I recommend upgrading to the latest FieldPoint driver and version of MAX. The FieldPoint VI's will be slightly different when you upgrade, so there is a good chance that this will eliminate the error.
Regards,
Hal L.

Is it possible to change the resolution of indivdual channels in measurement and automation explorer using a VI

Hi
I'm acquiring data on 8 analog input channels using a PCI-6052 E card. The data on channels 5 thru 8 is going to be between +1V and -1V. So for greater resolution I'm manually changing the range of these channels to +1V to -1V in the measurement and automation explorer. Is there a way by which I can make these changes directly using a VI ?
Thanks,
Shiv

Hi
Yes you can, but only if you use the "AI Config" VI. AI config allows different gains for different channels. The "channels" and "input limits" inputs of the VI accepts arrays. The first element of the input limits array corresponds to the first element of the channel array. Check the "cont acq&chart (buffered).vi" in the LV examples. There you see what I mean!
Regards,
Luca

Home Environment - How to set up Update Retriever (UR) and Thin Installer (TI) in a home environment

Serenityvalley wrote:
You need to go to This Page and download just about everything on it -espeically the System Update Deployment Guide and start reading. It'll take you a few hours to learn what you need to do and implement it if you are familar with editing system registeries and you have some luck and everything goes well.
You do NOT need to edit registry, just use Thin Installer instead of System Update on the clients. And there is no need to wade thru the deployment guide if you are setting this up in a home environment for just one or two clients.
Edit: Note that Thin Installer does not run on Vista SP2 (neither does System Update.)
Here are the few simple things you have to do:
1. Download Update Retriever (UR) and Thin Installer (TI) from here.
2. Install UR on one pc and TI on all clients you want to keep updated. UR installs into the Start -- All Programs -- Thinkvantage folder, TI installs into c:\program files\thininstaller.
3. To initialize Update Retriever:
a) specify the download folder, pick a place all clients can access. Create a new folder, TI will be confused if there is other stuff in it.
b) change the settings to Severity -- Optional (assuming you want to see critical, recommended and optional downloads in the list), License -- Do not display and Status -- Active. After clicking next you enter the machine type, the op system and its language for each client you need to keep updated. Note that unless you change status to active everything will download as "test" and thus not be installed by the Thin Installer.
4. Run the download, about 1 - 1.5GB for the first type, opsys and language combination and an additional 0.5 - 1GB for each additional type depending on amount of overlap. You can be selective what you download but if you are an average home user -- just download all the items for your type/opsys/language combination(s) -- Thin Installer is a stripped down version of System Update and will decide what to install on the individual client. This is a one-time download, next time you run Update Retriever it will just download new drivers.
5. To initialize TI on each client, copy the program from the Program Files directory and paste a shortcut to the desktop. Then rightclick on the shortcut and choose Properties, and in the target field of the shortcut tab after "C:\Program Files\ThinInstaller\ThinInstaller.exe" add the following: -repository your_UR_download_directory.
6. Run the Thin installer on each client, it will perform exactly as System Update did, down to making the same mistakes that System Update did.
7. As the date is getting close when Windows Update will start distributing Vista SP2 you may want to consider using Microsoft's SPBlockerTools preventing SP2 installation for up to 12 months.
8. Debugging Tips
TI ending with message An error occurred while gathering user information is reported when running under Vista SP2 -- TI will not run in SP2.
Getting TI to "see" the database downloaded by UR is the main problem. If TI ends with a message saying corrupt or not found database you probably made a spelling mistake in the directory specified in the -repository parameter. If TI ends with a message saying no applicable packages to install it can mean a number of things:
a) If you are unused to modifying the parameters in a shortcut you may have added -repository to the second field in the shortcut tab instead of the top field labeled Target, the two fields look very similar or you just made a typo in "-repository".
b) Open UR again and first choose Modify settings on the left and double check that the directory there is the same directory you specified in -repository. Then choose Manage repository -- Update view and double check that all packages have status Active. If they don't it's not necessary to download again, just select all and hit the modify button to change status from Test to Active.
c) In C:\Program Files\ThinInstaller\logs there are update logs from TI. Open one using Notepad and in edit menu search for the string
Message: 'Share name' to use:
This will tell you in which directory TI is searching for the updates. If it can't find a -repository parameter it uses an empty default databse
d) If you used System Update regularly up to when it stopped working on April 1 and if you have an older model with not so many new driver updates it may actually happen that there are no new updates for your machine (even though you downloaded a lot.) Go to here and enter all fields except model to see what Lenovo shipped after April 1. (Don't click on driver matrices, staying on the downloads and drivers pages will give you a list in chronological order with the ones after April 1 at the top.) Also be aware that the database UR downloads from is at least 2 weeks behind when the drivers first become available on the web. Right now, the only new download in the database applicable to most notebooks after April 1 is the Access Connections 5.22 driver. To check what release you have installed open Access Connections and go to help.
I just did a clean install of a Vista64 system on my T500 and after installing the first few drivers manually (including drivers for harddisk and ethernet) let Thin Installer install the remaining 36 items for me. The only item left to fix was the known bug in the Ricoh 4 in 1 card driver SU installation. (For a clean install you need to run TI or SU more than once, it doesn't find all drivers the first time.)
Message Edited by JaneL on 05-08-2009 10:30 PM
Message Edited by zilla on 2009-05-28 12:48 PM
T500: Vista 32, 2.8GHz, 4GB RAM, 15.4" 1680x1050, 500GB 7200rpm, ATI Radeon HD3650 + Intel 4500MHD. T42: XP, 1.7GHz, 2GB RAM, 14.1" 1024x768, 250GB PATA, ATI Radeon 7500.

koolzero wrote:
When I start TI after I pointed it to my repository I get a message that no packages applicable were found. I did not download all the updates just a few to test it, will it not work unless all updates are downloaded?
Did you change status from test to active in UR before downloading? If not you can change the downloaded items in the manage repository menu.
Assuming the items you did download were not already installed on your client with TI it should work.
Message Edited by zilla on 2009-05-06 10:23 PM
T500: Vista 32, 2.8GHz, 4GB RAM, 15.4" 1680x1050, 500GB 7200rpm, ATI Radeon HD3650 + Intel 4500MHD. T42: XP, 1.7GHz, 2GB RAM, 14.1" 1024x768, 250GB PATA, ATI Radeon 7500.

AIF and automated installation

Similar Messages

Maybe you are looking for