From: Maxim S. Shatskih on
> Why? Even though Windows NT isn't in practice a portable operating
> system any more

Portable across 3 platforms - x86, x64 and IA64

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim(a)storagecraft.com
http://www.storagecraft.com

From: Skywing on
It currently runs on three processor architectures mainstream (x86, x64,
IA64).

"Jonathan de Boyne Pollard" <J.deBoynePollard-newsgroups(a)NTLWorld.COM> wrote
in message news:c1.01.31Gscz$5AJ(a)J.de.Boyne.Pollard.localhost...
>P> using of this one *.asm among other 20 *.c is in this case needed.
>
> Why? Even though Windows NT isn't in practice a portable operating system
> any more, it still retains all of the capabilities for being portable
> across CPU architectures, including the availability of processor-neutral
> functions, callable from the C and C++ languages, for performing all sorts
> of low-level things that would on other systems be the purview of assembly
> language code.
>
> <URL:http://perl.plover.com./Questions3.html>
>
> It's a fair bet that if you explained the actual problem that you are
> trying to solve, you'd be pointed in the direction of how to do it without
> need for any assembly language. Stop asking us about chocolate-covered
> bananas.
>


From: Jonathan de Boyne Pollard on
JdeBP> Why? Even though Windows NT isn't in practice a portable
JdeBP> operating system any more, it still retains all of the capabilities
JdeBP> for being portable across CPU architectures, including the
JdeBP> availability of processor-neutral functions, callable from the
JdeBP> C and C++ languages, for performing all sorts of low-level
JdeBP> things that would on other systems be the purview of assembly
JdeBP> language code.

MSS> Portable across 3 platforms - x86, x64 and IA64

Mars bars are advertized in some localities as containing "glucose,
sugar, and milk". Dieticians read this as "sugar, more sugar, and milk
(which also contains sugar)". Saying that the current version of
Windows NT is "portable across three platforms" is pretty similar. Like
the Mars bar slogan, "x86, x64, and IA64" reads as "Intel architecture,
Intel architecture, and more Intel architecture". In comparison to how
portable Windows NT *used* to be, this is not, in practice, portability,
as I said. It's the Henry Ford version of portability: "You can have
any platform that you like, as long as it's Intel."
From: Tim Roberts on
Peter <Peter(a)discussions.microsoft.com> wrote:
>
>But like I mentioned it seems that all these directives are sufficient, but
>I am not 100% sure about it, even if this part of code is really functional
>in result NDIS IM driver. In *.cod file are much more directives, I am not so
>good in MASM to know what of these I must to use also in *.asm source file.

..COD files cannot actually be passed directly into MASM. Unlike gcc,
Visual C++ doesn't create an assembly file and then assemble it. It
creates machine language more or less directly. The .COD files are
generated in a separate step, and are representative of what the MASM would
look like, but manual intervention is required.
--
- Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
From: Tim Roberts on
Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups(a)NTLWorld.COM> wrote:
>
>Mars bars are advertized in some localities as containing "glucose,
>sugar, and milk". Dieticians read this as "sugar, more sugar, and milk
>(which also contains sugar)". Saying that the current version of
>Windows NT is "portable across three platforms" is pretty similar. Like
>the Mars bar slogan, "x86, x64, and IA64" reads as "Intel architecture,
>Intel architecture, and more Intel architecture". In comparison to how
>portable Windows NT *used* to be, this is not, in practice, portability,
>as I said.

I don't think your assessment is fair, for two reasons.

First, x64 was NOT an Intel invention, much to their chagrin. AMD invented
it, and Intel licensed it. Sure, it's derived from x86, but there are
fundamental differences.

Second, ia64 is NOTHING like x86. Those two architectures are at least as
different as x86 and Alpha.
--
- Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: USBD_STATUS_XACT_ERROR
Next: passthru install???