Re: Bug/problem with lcc-win

jacob navia said:

Richard Heathfield wrote:
Serve Lau said:

<snip>

Obviously you dont know what you're talking about.

Do you?


He knows more than you apparently.

You will, I hope, forgive me for disagreeing.

Just keep it at what you want is not possible.

Saying it's not possible doesn't make it not possible. And it turns out
that it *is* possible. It may be possible with lcc-win - I don't know -
but it's certainly possible with some other compilers.

No.

Yes.

Win32 runs in 32 bits, DOS runs on 16 bits.

So what? Have you never heard of cross-compilation? I have several
compilers that can generate DOS executables that will run perfectly well
under Windows 98.

Win32 can EMULATE msdos, and yes, you can generate 16 bit
executables for msdos using for instance, a linux 64 bit OS.

Right. My point exactly. (And in fact Windows 98, which is the version of
Windows under discussion, is firmly based on MS-DOS.)

So what?

So it is possible for the OP to achieve his objective, that's what.

It is NOT possible under win32 to access video memory in the old
DOS way!

So what? Consider the "as if" rule that we set so much store by, here in
comp.lang.c - it is possible to write a program that executes correctly in
a Win32 environment despite using the same techniques to write to video
RAM that were used under MS-DOS - the fact that an emulator is involved is
likely to trouble the OP not one jot.


When you make an interrupt (21 for instance) the interrupt goes
to Win32 table of interrupts that are NOT compatible with msdos!

So what? As long as it works.


Now, if you are running under 16 bit MSDOS emulation, the interrupt
will be trapped by the emulation layer and redirected to simulate some
video memory. But this is done with 16 bit programs only, NOT
with 32 bit programs!

Right, which is why you need a 16-bit compiler, which is what I said
before. You appear to be violently agreeing with me.

It's silly to ask for a compiler for one OS
(windows) to generate code for another (dos)

Nevertheless, compilers exist which run under Windows but which can
produce DOS executables.

As I said above, you can use linux 64 bits to generate
code for msdos 16 bits if you like. Under linux 64 bits
you can run an msdos emulator with turboc.

Right.

That doesn't mean that you can use the interrupt 21 under
linux 64 to set the text screen background!

You can, if you're running an emulator that faithfully mimics MS-DOS.

I have at least three such compilers lying around the
place.


They will ALL run under an emulation layer.

Right (although the situation may not be quite so clear-cut under Windows
98, which is the OS that the OP is concerned about).

You know this,

Right.

and you are just lying (making people believe you are just naive)

If I have made a mistake in anything I've written in this thread, okay,
I've made a mistake, but please be kind enough to point the mistake out,
because I can't find one. But please drop your imbecilic accusations of
deceit. You don't seem to understand the difference between "disagreeing
with Jacob Navia" and "lying". It is a very important difference.

And no it doesnt work with
microsoft compilers either.

It does with some Microsoft compilers. For example, MSVC1.5x.

All Microsoft DOS compilers run under the EMULATION LAYER of Win32!

MS compilers that were written for MS-DOS run just fine in MS-DOS. They
*also* work just fine in an emulation layer. MS-DOS compilers that were
written for Win32 but which can generate MS-DOS executables on request
will run just fine under native Win32, and the executables that they
generate will run just fine under emulation. Again, I reiterate that the
situation is not quite as clear-cut under Win98, because it is so firmly
based on MS-DOS that it may not be entirely accurate to say that an
emulation layer is required. And of course Win98 is the OS that the OP is
interested in.

Yes, I can run under VISTA 64 a windows 98 virtual machine with
a MSDOS emulation and I can generate code for msdos.

SO WHAT?

So the OP can achieve his objective, that's what.

Does that mean that I can use those assembler sequences to set the
screen under vista 64?

Yes. If the emulation layer can do it, it can be done - via emulation.
Note, too, that Vista 64 is very different to Windows 98.

<snip>

And
another thing, why is that company moving from one unsupported OS to
another unsupported OS?

Possibly because they want stability. There are still people around who
prefer not to fix something that isn't broken or, if it *is* broken,
want to apply the minimum fix possible. That's their decision, not ours.



Obviously when you praise windows 98 stability you know what you are
talking about :-)

Well, it was certainly more stable than both its predecessor and its
successor. But what I was talking about was a more general kind of
stability - getting the maximum benefit from a minimal change. If you're
currently stuck in MS-DOS-Land, an upgrade to Windows 98 does make a
twisted kind of sense.

You do your reputation, such as it is, no good whatsoever by parading your
ignorance and arrogance in this way. I recommend that, next time, you
think before you post.

--
Richard Heathfield <http://www.cpax.org.uk>
Email: -http://www. +rjh@
Google users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999
.

Relevant Pages

  • Re: FC3 sucks. It takes up too much memory!
    ... >running emulated console games under the PC, the quality will never be ... hardware emulation and other technical stuff. ... >Windows laptop isn't visible to other Windows boxes, ... > Dual screens is a little harder to setup in linux (this probably ...
    (Fedora)
  • Re: FC3 sucks. It takes up too much memory!
    ... hardware emulation and other technical stuff. ... Feel free to compare Linux to Windows, but you will find it is like ... another and breaking one package could lead to another package ...
    (Fedora)
  • Re: AppleIIGo 2.0 Build 301
    ... Regarding Windows... ... it should be the same to compile under Linux, ... develop an NTSC color emulation, ... This build implements an Apple IIc ROM 04 with two 5.25" disk drives, ...
    (comp.emulators.apple2)
  • Re: Resurrecting an old RiscPC
    ... to have to use windows. ... they will stick with Windows under emulation (or whatever you ... Malware on the virtual machine is highly unlikely to have any ... I'm hoping VRPC appears for the Mac. ...
    (comp.sys.acorn.apps)
  • Re: The whole Apple can Run Windows thing...
    ... the new hardware can boot directly), the set of applications that runs ... If you're counting soft emulation, Windows can run OS/X in emulation too, ... mandates that for whatever reason cause a lot of pain to support. ...
    (rec.photo.digital.slr-systems)
Loading