LINUX AND CPU REQUIREMENTS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2BCD0.8370C360
Content-Type: text/plain;
	charset="iso-8859-1"

Hi Jeff,

   Thanks, Jeff. It sounds like it is my current CPU on which I'm coding
that's causing me this problem. 

   For the time being, I'll just accept that I have no compilation errors,
only run-time errors; that's a head-start anyway. 

   I'm studying assembly from a 1993 published text and expected some
problems. I'm not using a GCC assembler but a generic assembler I purchased
which handles Turbo and Microsoft assembly languages, as well as a generic
assembly language. The problem is finding a text which doesn't lean toward
either TASM or MASM. To reduce that problem, I've purposely started with an
old text and will be coming up to current usage. Next year, when I have my
PC up and going, I'll switch to the GCC assembler and C compiler.

Thanks for your help,

Walt


------_=_NextPart_001_01C2BCD0.8370C360
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: LINUX AND CPU REQUIREMENTS</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi Jeff,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; Thanks, Jeff. It sounds =
like it is my current CPU on which I'm coding that's causing me this =
problem. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; For the time being, I'll =
just accept that I have no compilation errors, only run-time errors; =
that's a head-start anyway. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&nbsp;&nbsp; I'm studying assembly =
from a 1993 published text and expected some problems. I'm not using a =
GCC assembler but a generic assembler I purchased which handles Turbo =
and Microsoft assembly languages, as well as a generic assembly =
language. The problem is finding a text which doesn't lean toward =
either TASM or MASM. To reduce that problem, I've purposely started =
with an old text and will be coming up to current usage. Next year, =
when I have my PC up and going, I'll switch to the GCC assembler and C =
compiler.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Thanks for your help,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Walt</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2BCD0.8370C360--





[Index of Archives]     [Linux Speakup]     [Fedora]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]