From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: '@' In blank space on Bochs.
Date: 29 May 2002 16:03:01 +0100
Sender: linux-8086-owner@vger.kernel.org
Message-ID: <1022684581.4124.224.camel@irongate.swansea.linux.org.uk>
References: <005e01c20712$aa075c10$6407070a@blue>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-8086-owner@vger.kernel.org>
In-Reply-To: <005e01c20712$aa075c10$6407070a@blue>
List-Id: <linux-8086.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: Nicholas Knight <nknight@pocketinet.com>
Cc: Linux 8086 <linux-8086@vger.kernel.org>

On Wed, 2002-05-29 at 14:13, Nicholas Knight wrote:
> ELKS apparently writes out blank areas of the screen with 0's
> (arch/i86/drivers/char/dircon.c, #define A_BLANK 0x00). This creates an
> issue with Bochs because, for some reason, Bochs has '@' there instead of
> null (as it happens, MINIX runs into the same problem). This may be specific
> to the Windows version of Bochs, as I've yet to use either MINIX or ELKS in
> Bochs in any other host OS.
> 
> Once I get my laptop back (grumble, stupid hdd) I can recompile ELKS to use
> 0x32 (ASCII's "space" character) instead of 0x00 on my personal systems, but
> I thought others might be interested in this.
> 
> Maybe a config option? CONFIG_BLANK_BOCHS?

Space ought to work on real hardware too, so you can avoid the config
option (which is good config options are just more and more overhead to
maintain)