473,321 Members | 1,877 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,321 software developers and data experts.

lcc-win and windows 98

Hi

I have installed windows 98 in a virtual machine, and
I have been able to verify that the compiler runs perfectly
and compiles programs for widnows 98 without any problems,
contrary to what Mr CBFalconer says since several years.

Wedit (the IDE) will not run in windows 98. You should
use another editor (I would recommend vi.exe or
notepad) and everything will go on very smoothly.
--
jacob navia
jacob at jacob point remcomp point fr
logiciels/informatique
http://www.cs.virginia.edu/~lcc-win32
Jan 21 '08 #1
11 2000
jacob navia wrote:
Hi

I have installed windows 98 in a virtual machine, and
I have been able to verify that the compiler runs perfectly
and compiles programs for widnows 98 without any problems,
contrary to what Mr CBFalconer says since several years.

Wedit (the IDE) will not run in windows 98. You should
use another editor (I would recommend vi.exe or
notepad) and everything will go on very smoothly.

P.S. I retrieved an old source tree from my archives and got wedit
running (inclusive debugger) under windows 98.

--
jacob navia
jacob at jacob point remcomp point fr
logiciels/informatique
http://www.cs.virginia.edu/~lcc-win32
Jan 21 '08 #2
On Mon, 21 Jan 2008 22:51:10 +0100, jacob navia <ja***@nospam.com>
wrote in comp.lang.c:
Hi

I have installed windows 98 in a virtual machine, and
I have been able to verify that the compiler runs perfectly
and compiles programs for widnows 98 without any problems,
contrary to what Mr CBFalconer says since several years.

Wedit (the IDE) will not run in windows 98. You should
use another editor (I would recommend vi.exe or
notepad) and everything will go on very smoothly.
Jacob,

I remember, even if you don't, one version of lcc-win32 some years ago
(must be more than five years) that would not run on Windows 9x. I
know, because I had downloaded it and installed it over an earlier
version.

I also remember that you fixed it quickly.

So there is a kernel of fact behind what Chuck says.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://c-faq.com/
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.club.cc.cmu.edu/~ajo/docs/FAQ-acllc.html
Jan 22 '08 #3
jacob navia wrote:
>
I have installed windows 98 in a virtual machine, and
I have been able to verify that the compiler runs perfectly
and compiles programs for widnows 98 without any problems,
contrary to what Mr CBFalconer says since several years.

Wedit (the IDE) will not run in windows 98. You should
use another editor (I would recommend vi.exe or
notepad) and everything will go on very smoothly.
Did you set the virtual machine to emulate a 486? Note that you
are providing a system, which includes an editor, IDE, and a
debugger. The debugger fails. As I recall the message is 'invalid
instruction' or something similar.

A viable alternative test is to use a real live '486. Note that
W98 runs as well as ever.

--
[mail]: Chuck F (cbfalconer at maineline dX-Mozilla-Status: 0009tp://cbfalconer.home.att.net>
Try the download section.

--
Posted via a free Usenet account from http://www.teranews.com

Jan 22 '08 #4
CBFalconer wrote:
jacob navia wrote:
>I have installed windows 98 in a virtual machine, and
I have been able to verify that the compiler runs perfectly
and compiles programs for widnows 98 without any problems,
contrary to what Mr CBFalconer says since several years.

Wedit (the IDE) will not run in windows 98. You should
use another editor (I would recommend vi.exe or
notepad) and everything will go on very smoothly.

Did you set the virtual machine to emulate a 486? Note that you
are providing a system, which includes an editor, IDE, and a
debugger. The debugger fails. As I recall the message is 'invalid
instruction' or something similar.

A viable alternative test is to use a real live '486. Note that
W98 runs as well as ever.
Note that I am speaking about windows 98. Not a 486, a CPU that is out
of date more than 10 years ago.


--
jacob navia
jacob at jacob point remcomp point fr
logiciels/informatique
http://www.cs.virginia.edu/~lcc-win32
Jan 22 '08 #5
jacob navia wrote, On 22/01/08 18:24:
CBFalconer wrote:
<snip>
>A viable alternative test is to use a real live '486. Note that
W98 runs as well as ever.

Note that I am speaking about windows 98. Not a 486, a CPU that is out
of date more than 10 years ago.
Chuck, Jacob, this discussion does not belong in comp.lang.c. Chuck, if
you want to continue this subscribe to comp.compilers.lcc and continue
it there. I've even set follow-ups for you!

Jacob, just include anywhere you state W98 that it is W98 on a Pentium
or newer rather than only saying W98, then you are covered.
--
Flash Gordon
Jan 22 '08 #6
jacob navia wrote:
CBFalconer wrote:
>jacob navia wrote:
>>I have installed windows 98 in a virtual machine, and
I have been able to verify that the compiler runs perfectly
and compiles programs for widnows 98 without any problems,
contrary to what Mr CBFalconer says since several years.

Wedit (the IDE) will not run in windows 98. You should
use another editor (I would recommend vi.exe or
notepad) and everything will go on very smoothly.

Did you set the virtual machine to emulate a 486? Note that you
are providing a system, which includes an editor, IDE, and a
debugger. The debugger fails. As I recall the message is 'invalid
instruction' or something similar.

A viable alternative test is to use a real live '486. Note that
W98 runs as well as ever.

Note that I am speaking about windows 98. Not a 486, a CPU that
is out of date more than 10 years ago.
That has nothing to do with it. You claim your system runs on
W98. W98 runs on a '486. Therefore it obviously must run your
system. WRONG.

And there are a fair number of '486s (and '386s) running in the
wide world.

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

--
Posted via a free Usenet account from http://www.teranews.com

Jan 22 '08 #7
Flash Gordon wrote:
jacob navia wrote, On 22/01/08 18:24:
>CBFalconer wrote:

<snip>
>>A viable alternative test is to use a real live '486. Note that
W98 runs as well as ever.

Note that I am speaking about windows 98. Not a 486, a CPU that
is out of date more than 10 years ago.

Chuck, Jacob, this discussion does not belong in comp.lang.c. Chuck,
if you want to continue this subscribe to comp.compilers.lcc and
continue it there. I've even set follow-ups for you!
AFAIACS what I want is for Jacob to finally admit his foul-up. The
system used to work on the 486 - I know, because I was running it.
Then he made a revision, and it aborted the debugger on 'illegal
opcode'. I advised him, and he couldn't find the cause!!! Now,
years later, he continues the false claims and spouts garbage about
'obsolete'. The fact that he couldn't find the problem within
about a month of causing it is, to me, significant.

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

--
Posted via a free Usenet account from http://www.teranews.com

Jan 23 '08 #8
CBFalconer wrote, On 22/01/08 23:15:

<snip>
AFAIACS what I want is for Jacob to finally admit his foul-up. The
<snip>

I really don't give a monkeys. Whether and when any tool, whether
Jacob's or not, worked on a 486 and whether and when it broke is NOT
topical here. If you want to discuss win-lcc then do what you tell other
people to do and subscribe to the correct group, one you are fully aware
of, and discuss it there.

Remember, that if it is OK for YOU to discuss compiler specific issues
in comp.lang.c then it is OK for everyone. I say it is NOT OK for
anyone, including you.

Note that you are not discussing whether Jacob's compiler conforms to
the C standard, you are discussing the platforms it works on.
--
Flash Gordon
Jan 23 '08 #9
Jacob Navia wrote:
I have installed windows 98 in a virtual machine [...]
Is comp.lang.c your new blog?
Jan 23 '08 #10
Spoon wrote:
Jacob Navia wrote:
>I have installed windows 98 in a virtual machine [...]

Is comp.lang.c your new blog?
LOL !

I'm amazed at how many people I've added to my killfile for this group.

It is probably a sign of my intolerance, but on the other hand I haven't
done it in other groups.
Jan 23 '08 #11
Spoon wrote:
Jacob Navia wrote:
>I have installed windows 98 in a virtual machine [...]

Is comp.lang.c your new blog?
It was in direct response to CBFalconer's accusation that lcc-win32's
debugger fails under an 486 processor, running Windows98, which jacob
misunderstood. As Flash notes, we should stop contributing to this OT
thread, regardless of who started it.

Jan 23 '08 #12

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

4
by: Zeng Dinghao | last post by:
could anybody explain the term "in memory compilation" to me ? thanks
98
by: jacob navia | last post by:
<< QUOTE It is NOT a C compiler, because it doesn't conform to any commonly accepted C specification (K&R, C89, C99). You have no right to call it a C compiler until you get it to conform quote...
14
by: vittorio | last post by:
While I can compile the program below under freebsd via a simple: gcc prog1.c -o prog1 and it runs smoothly, I'm experiencing annoying problems with lcc-win32 under windows xp pro. In fact, under...
5
by: jacob navia | last post by:
Due to popular demand (specially from Mr Heathfield), I have introduced a -pedantic compiler flag, that will be as the -ansic option but stricter. This flag will make _stdcall
67
by: Nimmi Srivastav | last post by:
Apologies if my cross posting has offended anyone.... For a pure hobbyist C/C++ programmer, who wants to develop applications to run on Windows, what would be a better choice to install: Visual...
13
by: Albert | last post by:
Hi I'm using the lcc compiler for win32. I tried compiling a program but there's an error stating: "cpp: Can't open input file clrscr()" I don't get it - I've included <tcconio.h>. (strange why...
48
by: teapot | last post by:
If I compile this program int main(void) { return 0; // foo bar baz } with "lc -A -ansi89 foo.c"
15
by: Chris Peters | last post by:
Hello Group Can anyone confirm or suggest workrounds for the following bug in lccwin32. If an inline assembly statement immediately follows a for loop and you try to set a breakpoint on it, then...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
1
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.