Robert Spitzenpfeil

ocs-iso -x "ip=eth0:xxx..."

Installations works as expected now. Thanks.

I have this issue as well, just with LV2016 (32bit) I've managed to work around this by manually copying the h5labview2 files to .../vi.lib/addons and .../examples/ + a mass compile. The test suite passes. I haven't checked any further so far. Could it be that the VIPM package still has a dependency check for HDF5 enabled, which should not be needed anymore as it comes with the dlls?

I have this issue as well. I've managed to work around this by manually copying the h5labview2 files to .../vi.lib/addons and .../examples/ + a mass compile. The test suite passes. I haven't checked any further so far. Could it be that the VIPM package still has a dependency check for HDF5 enabled, which should not be needed anymore as it comes with the dlls?

What works most of the time is this: make a backup! use gparted to resize & move the partition(s) so they lie well within the smaller limit. create a disk image of the resized disk restore the image with "-icds" to the smaller disk It is a lot of hassle & takes quite a lot of time. It is much easier to just buy a bigger disk.

What works most of the time is this: make a backup! use gparted to resize & move the partition(s) so they lie well within the smaller limit. create a disk image of the resized disk restore the image with "-icds" to the smaller disk It is a lot of hassle & takes quite a lot of time. It is much easier to just buy a bigger disk.

You could do a secure erase on the bigger target disk. After that it should be as clean as can be. If the problem pops up again right after doing a fresh clone, that suggests the source may have issues.

You could do a secure erase on the bigger target disk. After that it should be as clean as can be. If the problem pops up again after doing a fresh clone, that suggests the source may have issues.