Bug/problem with lcc-win

[Eddie]

Hi

I am using lcc-win on Windows 98. I'm writing a simple c console app, and
I need to set the background color to blue. Here's the code I've got at
the moment:

_asm ( "movb $2, %ah\n"
"movb $7, %dl\n"
"int $0x21\n"
);

But this doesn't work.

Does anyone have any suggestions?

Thanks.

[Lew Pitcher]

In comp.lang.c, Eddie wrote:

Hi

I am using lcc-win on Windows 98. I'm writing a simple c console app, and
I need to set the background color to blue. Here's the code I've got at
the moment:

_asm

[snip]

But this doesn't work.

Does anyone have any suggestions?

How about emailing your question directly to the authors of lcc-win? Since
your question doesn't relate to the features found in the C language, but
instead is about an lcc-win specific extension to the language, your best
bet is to take your question to the author.

--
Lew Pitcher

Master Codewright & JOAT-in-training | Registered Linux User #112576
http://pitcher.digitalfreehold.ca/ | GPG public key available by request
---------- Slackware - Because I know what I'm doing. ------

[jacob navia]

Eddie wrote:

Hi

I am using lcc-win on Windows 98. I'm writing a simple c console app, and
I need to set the background color to blue. Here's the code I've got at
the moment:

_asm ( "movb $2, %ah\n"
"movb $7, %dl\n"
"int $0x21\n"
);

But this doesn't work.

Does anyone have any suggestions?

Thanks.

This will not work under windows 98. You need to use the textbackground
library provided by lcc-win.

You will find the documentation for this function in the IDE (wedit) with:
Menu->Help->Standard Library->textbackground .

You should add the tcconio.lib library to the link step.
--
jacob navia
jacob at jacob point remcomp point fr
logiciels/informatique
http://www.cs.virginia.edu/~lcc-win32

[Eddie]

OK thanks.

But shouldn't it work as it is? I think on Microsoft it will work.

Could you provide some sample code of changing the color to blue with
textbackground?

Thanks.
On Tue, 03 Jun 2008 20:38:37 +0200, jacob navia wrote:

Eddie wrote:

>Hi

I am using lcc-win on Windows 98. I'm writing a simple c console app, and
I need to set the background color to blue. Here's the code I've got at
the moment:

_asm ( "movb $2, %ah\n"
"movb $7, %dl\n"
"int $0x21\n"
);

But this doesn't work.

Does anyone have any suggestions?

Thanks.

This will not work under windows 98. You need to use the textbackground
library provided by lcc-win.

You will find the documentation for this function in the IDE (wedit) with:
Menu->Help->Standard Library->textbackground .

You should add the tcconio.lib library to the link step.

[jacob navia]

Eddie wrote:

OK thanks.

But shouldn't it work as it is? I think on Microsoft it will work.

No it will NOT work under Microsoft. Under Win32 you can't access video
memory like that.

>
Could you provide some sample code of changing the color to blue with
textbackground?

#include <tconio.h>
......

textbackground( BLUE);

Please just read the doc for that function, available in the help
tab of the menu
--
jacob navia
jacob at jacob point remcomp point fr
logiciels/informatique
http://www.cs.virginia.edu/~lcc-win32

[Flash Gordon]

jacob navia wrote, On 03/06/08 19:38:

Eddie wrote:

>Hi

I am using lcc-win on Windows 98. I'm writing a simple c console app, and

<snip completely unportable code and solution>

You should add the tcconio.lib library to the link step.

You should also take any further discussion to comp.compilers. lcc as it
is completely implementation specific.
--
Flash Gordon

[CBFalconer]

Lew Pitcher wrote:

Eddie wrote:

>I am using lcc-win on Windows 98. I'm writing a simple c console
app, and I need to set the background color to blue. Here's the
code I've got at the moment:

_asm

[snip]

>But this doesn't work.

Does anyone have any suggestions?

How about emailing your question directly to the authors of
lcc-win? Since your question doesn't relate to the features found
in the C language, but instead is about an lcc-win specific
extension to the language, your best bet is to take your question
to the author.

He can also use comp.compilers. lcc. The point is that none of
those 'words' are defined in the C standard, and are thus off-topic
in c.l.c

--
[mail]: Chuck F (cbfalconer at maineline dot net)
[page]: <http://cbfalconer.home .att.net>
Try the download section.
** Posted from http://www.teranews.com **

[Eddie]

Thanks for the information, that seems quite simple. Is BLUE an integer
constant? Maybe I can save some space on my source files by just using the
integer value.

I think it would still be better if lcc-win supported writing directly to
video memory as well as using #tconio, this would make it much easier
when porting applications.
On Tue, 03 Jun 2008 22:39:37 +0200, jacob navia wrote:

Eddie wrote:

>OK thanks.

But shouldn't it work as it is? I think on Microsoft it will work.

No it will NOT work under Microsoft. Under Win32 you can't access video
memory like that.

>>
Could you provide some sample code of changing the color to blue with
textbackground ?

#include <tconio.h>
.....

textbackground( BLUE);

Please just read the doc for that function, available in the help
tab of the menu

[Walter Roberson]

In article <pa************ *************** *@nospam.com>,
Eddie <no****@nospam. comwrote:

>I think it would still be better if lcc-win supported writing directly to
video memory as well as using #tconio, this would make it much easier
when porting applications.

You are expecting that lcc-win, a *compiler*, would somehow detect
and intercept your assembler 'int' (interrupt) instruction, figure
out from historical patterns what the interrupt used to do, and
then rewrite the code to make the calls that the new operating
system requires instead ?? But then since you are down in the
assembler level, it would have to change the assembler code
generated to insert the new necessary calls, and that could mess
up any branch or load-relative offsets you had hand-coded.

Or are you expecting that lcc-win, a *compiler*, would hook itself
in to the interrupt vectors, figure out what the received interrupt
used to do, and make the new system calls instead? But then since
you are down in the assembler level, you might have specified your
own interrupt vector and your interrupt code might get bolluxed if
lcc-win front-ended your interrupt code.

In my opinion, what you are asking for is unreasonable to expect a
C compiler to do on a different operating system than the one
that the embedded assembler source was coded for.
--
"To all, to each! a fair good-night,
And pleasing dreams, and slumbers light" -- Sir Walter Scott

[jacob navia]

Walter Roberson wrote:

In article <pa************ *************** *@nospam.com>,
Eddie <no****@nospam. comwrote:

>I think it would still be better if lcc-win supported writing directly to
video memory as well as using #tconio, this would make it much easier
when porting applications.

You are expecting that lcc-win, a *compiler*, would somehow detect
and intercept your assembler 'int' (interrupt) instruction, figure
out from historical patterns what the interrupt used to do, and
then rewrite the code to make the calls that the new operating
system requires instead ?? But then since you are down in the
assembler level, it would have to change the assembler code
generated to insert the new necessary calls, and that could mess
up any branch or load-relative offsets you had hand-coded.

Or are you expecting that lcc-win, a *compiler*, would hook itself
in to the interrupt vectors, figure out what the received interrupt
used to do, and make the new system calls instead? But then since
you are down in the assembler level, you might have specified your
own interrupt vector and your interrupt code might get bolluxed if
lcc-win front-ended your interrupt code.

In my opinion, what you are asking for is unreasonable to expect a
C compiler to do on a different operating system than the one
that the embedded assembler source was coded for.

That is the main point. That assembler code worked on DOS. Now,
since DOS is gone, it doesn't work anymore and you just use C
instead of assembly. Somehow I find

textbackground( BLUE);

much clearer than the assembler instructions isn't it?

If you have further questions please go to the group
comp.compilers. lcc

This discussion is ot very topical here.
--
jacob navia
jacob at jacob point remcomp point fr
logiciels/informatique
http://www.cs.virginia.edu/~lcc-win32