James Mastros wrote:
> Um, this is considered correct behavior, if you're describing what I
> think you are. FreeDOS reacted as if you had pressed the phisicly
> corosponding key on a QWERTY keyboard? If so, you need to load the
> correct keyboard map in the guest OS. The same thing /should/ happen
> if you boot the floppy.
No, it's not like that. Indeed, when I boot FreeDOS on the real
hardware, it thinks I'm using QWERTY and shows 'q' when I press 'a'.
That is perfectly normal behaviour. But when I boot FreeDOS in plex86, X
is configured for AZERTY and FreeDOS is using its default QWERTY, it's
different: when I press 'a', it displays an 'a'. Idem for the rest of
the alphabet. But when I press '1' (without shift), it displays '7'. If
I press '1' with shift, it displays '!'. Etc. There was no way to get a
dot on the screen, or a backslash.
BTW, I noticed the same problem when I was trying out bochs a few weeks ago.
> If not, what FE were you running? From the screenshot, it looks like
> the X one.
Correct.
> How long did you give it? It might take a while -- the FAT16
> filesystem dosn't have a simple way to do it, you have to scan the
> whole FAT, and IO is still very slow (but it's probably going to
> speed up soon.
Indeed, it eventually comes trough.
> This is a LILO error -- according to
> /usr/share/doc/lilo/Manual.txt.gz, this is "'Controller error'. This
> shouldn't happen.". What's the config line for the file it's booting
> off of? Is it the right size? (a 1.44 floppy should be 1474560 bytes.)
bochs-opt floppya: 1_44=../../plexdata/tomsrtbflimg, status=inserted
I checked, it's 1474560 bytes.
The problem occured both when booting from a real floppy and when
booting from a floppy image. Booting on the real hardware was not a problem.
Perhaps a problem with the version of tomsrtbt I'm using? It is 1.7.185.
