X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
DomainKey-Signature:	a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type;
	b=jiSY+5UOpc2YOK+uimapTIJ/G2Gi82QcGGpF1xjrWu4PIyDiPjr+1JbIZPvRhefFc1h15SL4KnIEdtgW8gxET4q7sD30muQArNwvP4wEp/kTcw0D2wmlHc5i/eT1AKeRmVhQrTr2AMxd6l0CqzrD7RssisKNPPppwIZeL0R1o50=
Message-ID:	<2497d9a20507311923652c1344@mail.gmail.com>
Date:	Sun, 31 Jul 2005 22:23:47 -0400
From:	Matthew Petricone <strstream AT gmail DOT com>
To:	djgpp AT delorie DOT com
Subject:	Problems writing to video memory
Mime-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

------=_Part_4417_18674516.1122863027634
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Since updating to a the latest version of djgpp Whenever i attemp to write
to video memory directly in the 0xb8000 range. gcc reports "error: asignmen=
t=20
of read-only location". I would guess that's so i don't mess up the actuall=
=20
video memory, but i am writing an OS kernel. The code itself should not be=
=20
responsible since it used to compile and link just fine. If anyone knows=20
what's going on i would appreciate some help.

------=_Part_4417_18674516.1122863027634
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div>Since updating to a the latest version of djgpp Whenever i attemp to w=
rite</div>
<div>to video memory directly in the 0xb8000 range. gcc reports &quot;error=
: asignment of read-only location&quot;. I would guess that's so i don't me=
ss up the actuall video memory, but i am writing an OS kernel. The code its=
elf should not be responsible since it used to compile and link just fine. =
If anyone knows what's going on i would appreciate some help.
</div>

------=_Part_4417_18674516.1122863027634--

- Raw text -