Right. Multiple installs on two different machines. This is becoming a bit confusing....
First, the lockups I've mentioned a couple of times. First install on the laptop ended up the same way - complete the first stage of the install, reboot, go through the final configuration, lockup before reaching the GUI login. This time I left it for 20 minutes before I powered off. I think I may have found a way to avoid the problem, though I have no idea why it is occuring.
On the second install to the T42, when it rebooted, I edited the Grub command line, changed it from splash=silent to splash=quiet (on the basis that I've noticed a couple of times that I don't seem to get the lockups if I can get to verbose splash screen mode before it goes through the final stage of the boot to GUI. I'll have to prove it with more installs, but it worked - straight through to GMD without any lockup.
Problems (sorry, but there are several...). First, on the T42, volume is set to 0 (I suspect due to the fact that it registering 'default' rather than the correct device. If I adjust the volume, next time I boot, it is back to 0. This does not happen on a TUI install, but in those circumstances, I have to option to select the correct device during Alsa setup. This is consistent on both the T42 and the old PIII machine.
ALT-F2 still doesn't work on the T42, but does work on the PIII. Not a hardware problem, since it does work on the T42 under Zenwalk 5.2, VL5.9 Standard and VL5.9 SOHO. I have no idea what is causing that problem...
Inconsistency. VasmCC launched from the toolbar uses vsuper. Launched from the menu, it uses kdesu.
Vsuper is also (for the first time in my experience), inconsistent in operation. In a number of instances, it starts, I get a flash of something, and it goes away. After which, I get a partial wait mouse cursor for 30 seconds or more. I've noticed this behaviour when using it from the Thunar right-click menu especially - installing a number of packages from a directory will have it fail if I try to do it too fast. Every time it fails, I get the partial wait cursor.
More Vsuper. IMHO it is an unforgivable breach of security to have it default to saving the root password for the 'session'. In my case, a 'session' can be months. This default really needs to be changed. On a less serious note, I'm not real sure I like the screen darkening effects - reminds me far too much of another OS. I also wonder if the load of going through that routine is what causing the unreliable operation I'm seeing.
I found an Elsa Synergy AGP card to drop into the old PIII, which works much better - I can now get the full 1280x1024 x 24 bit colour on that machine. It was able to go through the GUI install without problems. The only oddity is that it doesn't like the splash screen and defaults to verbose mode during boot.
There is a minor glitch in the TUI install - I'll have to check the message, but as it starts the configuration phase, there is an error regarding gsb desktop. I'll copy it down on my next test install... I also note that when I use the TUI install, there is an extra Lilo option - Linux, Linux TUI, and Linux GUI. The last one is not present when Lilo is installed by the GUI install.