[syslinux] 5.00pre12 cat.c32 display

[Ady]

> 
> > 
> > > On Fri, 2012-11-30 at 16:10 +0200, Ady wrote:
> > > > When booting, are you able to see "LINE 1 OF HELP2.TXT"?
> > > 
> > > Yes.
> > > 
> > > > When manually running that "cat2" label from the boot prompt, are you 
> > > > able to see "LINE 1 OF HELP2.TXT"?
> > > 
> > > Yes.
> > > 
> > > > When pressing "F2", are you able to see "LINE 1 OF HELP2.TXT"?
> > > 
> > > Yes.
> > > 
> > > > Hopefully you can reproduce them now.
> > > 
> > > Nope. What machine are you using to test?
> > > 
> > 
> > VBox 4.1.22 (Windows host), booting with FAT12 1440KB floppy image, 
> > ldlinux.sys/.c32 installed with syslinux.exe (pre11 and pre12).
> > 
> > Also tested in VBox 4.1.22 booting with 1GB VHD fixed image in PATA 
> > primary master, ext3, ldlinux.sys/.c32 installed with EXTLINUX 
> > 5.00-pre12 and MBR from 5.00-pre12.
> > 
> > Using the same type of test, but with 4.06, I get:
> > 
> > LINE 1 OF HELP2.TXTboot:
> > 
> > So the only difference is that in 4.06, the "boot:" prompt is 
> > displayed after the end of the content, while in 5.00-pre12 the 
> > "boot:" prompt is displayed always at the beginning of the same line, 
> > covering the previously displayed text on that line.
> > 
> 
> I tested again, under VBox 4.2.4 and QemuManager 7.0 (qemu 0.11.1 and 
> qemu 1.1.2). In all cases the behavior is the same.
> 
> Is there anything I can do to correct this?
> Any change to the cfg file?
> Any suggestion (changing some setting in VBox or in qemu)?
> Am I the only one seeing this behavior? Anyone else testing 5.00?
> 
> I have seen other (unrelated) problems in 5.00-pre12, but I'm unsure 
> if the reports would be relevant if no VM I use can replicate other 
> (real) systems accurately enough.
> 
> Any advice?
> 
> TIA,
> Ady.

Tested again, this time using real hardware (UFD).

Version 4.06 in real HW behaves _exactly_ as described before under 
VM. Version 5.00pre12 behaves worse than before: I get to the boot 
prompt, but my keyboard doesn't react at all.

Unless someone else can replicate this behavior (in VM and/or in real 
hardware), I am stuck now.

In addition, I still have problems booting some ISO images with 
5.00-pre12 (while they boot with 4.06 correctly).

Any advice?

TIA,
Ady.