Downloaded ISO, installed as LiveHDD, seems to run fine as such. Then I decided to do a test install to hard drive.
I set up a new 20 GB partition /dev/sda16, foramatted this ext4 then called
draklive-install, all from Phinx root terminal.
During process something fails, looks like towards the end. Here is the terminal record, from the second attempt,
[guest@localhost ~]$ su
Password:
[root@localhost guest]# draklive-install
/media/ user
Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion `width >= -1' failed at /usr/lib/libDrakX/fs/partitioning_wizard.pm line 390.
Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion `width >= -1' failed at /usr/lib/libDrakX/fs/partitioning_wizard.pm line 390.
Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion `width >= -1' failed at /usr/lib/libDrakX/fs/partitioning_wizard.pm line 322.
Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion `width >= -1' failed at /usr/lib/libDrakX/ugtk2.pm line 84.
mount: /dev/sdb19 already mounted or /root/.inspect_tmp_dir busy
mount: wrong fs type, bad option, bad superblock on /dev/sdb21,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
umount: /dev/sda16: not mounted
Setting up swapspace version 1, size = 4088504 KiB
LABEL=swap4000, UUID=061c4ede-3435-4b06-8be5-e07ba90e2191
Setting up swapspace version 1, size = 4088504 KiB
no label, UUID=6fdbb9bb-f52e-4f56-8c4b-844de0960066
tune2fs 1.41.14 (22-Dec-2010)
tar: ./var/run/gdm_socket: socket ignored
tar: ./var/run/acpid.socket: socket ignored
tar: ./var/run/uuidd/request: socket ignored
tar: ./var/run/saslauthd/mux: socket ignored
tar: ./var/run/dbus/system_bus_socket: socket ignored
tar: ./var/run/avahi-daemon/socket: socket ignored
Warning: syslog is needed by crond in runlevel 2
Warning: syslog is needed by crond in runlevel 3
Warning: syslog is needed by crond in runlevel 4
Warning: syslog is needed by crond in runlevel 5
Warning: syslog is needed by crond in runlevel 2
Warning: syslog is needed by crond in runlevel 3
Warning: syslog is needed by crond in runlevel 4
Warning: syslog is needed by crond in runlevel 5
Warning: syslog is needed by crond in runlevel 2
Warning: syslog is needed by crond in runlevel 3
Warning: syslog is needed by crond in runlevel 4
Warning: syslog is needed by crond in runlevel 5
Warning: syslog is needed by crond in runlevel 2
Warning: syslog is needed by crond in runlevel 3
Warning: syslog is needed by crond in runlevel 4
Warning: syslog is needed by crond in runlevel 5
mount: /dev/sdb19 already mounted or /root/.inspect_tmp_dir busy
mount: wrong fs type, bad option, bad superblock on /dev/sdb21,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
add_entry at /usr/lib/libDrakX/bootloader.pm line 604, <> line 9.
standalone::bug_handler() called from /usr/lib/libDrakX/bootloader.pm:604
bootloader::add_entry() called from /usr/lib/libDrakX/bootloader.pm:1109
bootloader::suggest() called from /usr/lib/libDrakX/any.pm:211
any::setupBootloaderBefore() called from /usr/lib/libDrakX/any.pm:135
any::setupBootloaderBeforeStandalone() called from /usr/sbin/draklive-install:308
main::setup_bootloader() called from /usr/sbin/draklive-install:73
main::install_live() called from /usr/sbin/draklive-install:42
[root@localhost guest]#
The reference to /dev/sdb19 the partition holds the Phinx LiveHDD and it is from here the install is taking place, there is probably about 6 other OS held here each in single directories and none of those have failed to install many times.
I have seen similar failure as above when the BIOS sequence for drives have been screwed up. At present I believe I am running a pretty stable pc handling 6+ systems pretty well.
Any suggestions where my problem can be

I have looked in partition /dev/sda16 and it appears that Phinx fielsystem is installed here, so that it is only the boot loader install that gives up.
Therfor I manually constructed a stanza in my menulist and ran this. The page with the spinning circle shows and the comet advances slowly at the bottom of the screen and reaches the end after about 3-5 minutes. At this stage I gave up and hit reset button.