Re: [Vectorlinux-devel] New SOHO ISO's - 1.41txz

[Newt <gen...@gm...>]

Hello,

Notes from a test install on real hardware:

>> System: Intel Pentium D 2.8ghz (820), 3gb ram, dell deimension 9150, nvidia
>> gf7300le, Acer X213w 2.16/22" monitor, multiboot system (4 hard drives: 3
>> sata, 1 ide), installed to ide

-Attached is an image showing the sequence of what I saw when the initial screen
resolution option is made prior to the gambas2 installer. The resolution options
came up (left image), then a sequence of text spewed out leaving a garbled looking
mess (center image). Fortunately, it is only cosmetic and by pressing the down
arrow the options appeared in order and functional, but still garbled looking
(right image). As is shown, the "spewed text" is my Teac card reader which has
four slots thus the four devices (sdd/e/f/g). On the bright side, it does not
break functionality of the resolution selection. I have not tested this machine
since 1.15 but this did not happen back then.

-The partition sequence is much better however my swap (hda3) drops to the bottom
of the list, separated by several sdX devices. Again, only cosmetic -
functionality is fine.

-Bootloader Config: My windows partition /dev/sda1 is included as a boot menu
option but the 'Label' is left blank. This might actually be 'by design' but a
novice user might not know what this all means, and lilo won't allow an empty
label.

-Bootloader Config: LILO would not install. There was a duplicate '-cli' entry
appended to lilo.conf. After removing the duplicate entry I was able to install
lilo no problems. Is the duplicate entry because of the extra (windows) boot
entry? I did not test grub at all on this system.

-At the end of installation I rebooted, finished configuration using the
proprietary nvidia driver, and was headed into KDM when I got stuck in a
graphical/video problem. I would see the nvidia splash screen and then the screen
would blink in-and-out about three times, and then I would see the nvidia splash
screen again and the cycle repeated endlessly. I was never able to actually see
KDM. I ended up having to hard reboot.

I may give my other test system (nvidia 5200) a shot and see if it behaves the
same. I'll let you know how it goes.

Almost forgot: I notice that CD2 is still TLZ. I would have to say that I think
I'm noticing a significant boost in installation performance with TXZ packages
(i.e. a shorter installation time). It would be interesting to see if CD2 was any
quicker at installation if they were TXZ packages. I'm sure this is a lot of work
but thought I'd mention it. Lastly, when a TXZ package is installing I don't see
other supplementary process running in htop but when a TLZ package is installing I
see the unlzma process running alongside the tar process (I'm not 100% on this).

Cheers, newt