Re: [Freedos-user] (no subject)

2012-01-24 Thread TJ Edmister
FYI this is v1agra spam. Probably sent by a malware infested PC. Curious  
combination of email addresses in the "to" field...

On Wed, 25 Jan 2012 01:11:08 -0500, Brad Woosley   
wrote:

>
> http://prolumia.eu/mor/184042.html
>
> --
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user



--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] (no subject)

2012-01-24 Thread Brad Woosley

http://prolumia.eu/mor/184042.html

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] int notation.

2012-01-24 Thread Ralf A. Quint
At 03:13 PM 1/24/2012, C. Masloch wrote:
>I've been out of the loop on development for a while. Bret, do you,
>incidentally, remember whether we came up with this one independently, or
>how did it develop? I honestly would have to search through old mail again
>to answer that myself.

The INT xx.yy notation has been around for a loong time, doubt 
that there is anyone who can put a claim on having invented this b now... ;-)

>I might slightly amend my (long!) description in that I prefer to use
>"Int" in that capitalization and no space between that abbreviation and
>the xx; whereas, say, Bret uses "INT" all-capitalized here, and a space
>before the xx.

That's as well a matter of preference here, at least as far as the 
capitalization is concerned, as all DOS assemblers are case-insensitive...
You could have pretty much a discussion like over the "one true brace 
style" in C over this... >:-}

Ralf 


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] the int thing.

2012-01-24 Thread kurt godel
Beautiful; thanks guys, and by the way Bret I tried unsucessfuly to use
your usbdos on an msi mobo with only uusb(no ps2 holes); any which way,
it's impossible!!.Richard.
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] int notation.

2012-01-24 Thread C. Masloch
> I don't remember where I saw it first -- it might in fact have been  
> something from you.  It seems to be a relatively common practice now,  
> though.

Certainly common enough to cause the OP question here!

> Personal preference.  As there is no formal definition, as long as the  
> reader can understand what you're trying to say I don't think it makes  
> much difference.

Yes, it's definitely a personal preference.

Regards,
C. Masloch

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] int notation.

2012-01-24 Thread Bret Johnson
> Somewhat amusing that Bret would describe this "shorthand" in a
> much shorter way than I did.

There is no formal definition of this, at least that I've ever seen.  It's just 
a convenient way of talking about code at a high/conceptual level in forums and 
e-mails, without actually needing to explicitly write sample code.

> I've been out of the loop on development for a while. Bret, do you,
> incidentally, remember whether we came up with this one
> independently, or how did it develop? I honestly would have to
> search through old mail again to answer that myself.

I don't remember where I saw it first -- it might in fact have been something 
from you.  It seems to be a relatively common practice now, though.

> I might slightly amend my (long!) description in that I prefer to
> use "Int" in that capitalization and no space between that
> abbreviation and the xx; whereas, say, Bret uses "INT"
> all-capitalized here, and a space before the xx.

Personal preference.  As there is no formal definition, as long as the reader 
can understand what you're trying to say I don't think it makes much difference.


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] int notation.

2012-01-24 Thread C. Masloch
Somewhat amusing that Bret would describe this "shorthand" in a much  
shorter way than I did.

I've been out of the loop on development for a while. Bret, do you,  
incidentally, remember whether we came up with this one independently, or  
how did it develop? I honestly would have to search through old mail again  
to answer that myself.

I might slightly amend my (long!) description in that I prefer to use  
"Int" in that capitalization and no space between that abbreviation and  
the xx; whereas, say, Bret uses "INT" all-capitalized here, and a space  
before the xx.

Regards,
C. Masloch

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] int notation.

2012-01-24 Thread C. Masloch
> Recently I have seen ints such as: intxx.yy; is this something new, or I  
> just don't get out much? Is the 'yy' just the selection within the int  
> function or what?

Yes, some use this still rather unusual/new notation to concisely refer to  
interrupt calls. I am among those; you might have seen me use it here. I  
might have in fact coined some of it. Read on if you are interested in the  
details of how I use it.

The xx and yy are both two-digit (8-bit) hexadecimal numbers; xx refers to  
the interrupt number, yy to the value in register AH. If the call requires  
a value in register AX, you can refer to it with Intxx. instead. (Note  
that the specified number of digits is always used to distinguish (AH)  
8-bit and (AX) 16-bit number specifications here; this implies that one  
always has to include the leading zeros.)


If other registers are to be set, I use, for example,  
Intxx.yy(yy).zz=ww(ww) where "zz" is the register's name (say: BX, DL,  
whatever else) and ww(ww) is the hexadecimal number that the register  
needs to be set to. The equals sign there is a literal.

The parenthesis here are not literals, for the yy(yy) they indicate that  
the second half is either present or absent to distinguish AH or AX values  
as specified above. This can be done with the ww(ww) part too, but isn't  
necessary because zz explicitly specifies the register. Thus I sometimes  
lazily leave off leading zeros in the ww(ww) part. (Arguably, consistently  
padding to a full 2 or 4 digits can help clarify that the number is  
specified in hexadecimal, as numbers specified in decimal seldom include  
leading zeros.)


In principle, there can be any number of .zz=w... suffixes to specify how  
additional registers are to be set.

As it is currently an entirely (so-to-say) theoretic notation only used to  
discuss and comment on code, you can invent arbitrary other suffixes to  
append; say, .CF=0 or .NC to indicate that the Carry Flag (CF) is to be  
cleared. Just make sure you either explain them to your readers or they're  
sufficiently self-explanatory!

This can be easily extended to 32-bit registers in the same manner as the  
extension from 8-bit registers to 16-bit registers when necessary.


Regards,
C. Masloch

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] int notation.

2012-01-24 Thread Bret Johnson
INTxx.yy is a "shorthand" notation people use to indicate an INT xx with 
subfunction yy.  The yy is usually put into one of the CPU registers before the 
call (AH in many cases).  In addition, the xx and yy are assumed to be hex.

Example:
  INT 21.4C would be coded as:
MOV AH,4Ch
INT 21h


--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


[Freedos-user] int notation.

2012-01-24 Thread kurt godel
Here's a quick question:
I have used software interrupts, mostly with int86/union regs; say int 34
for the mouse, with another integer loaded into a register to select within
that int. Recently I have seen ints such as:
intxx.yy; is this something new, or I just don't get out much? Is the 'yy'
just the selection within the int function or what? Tnx. Richard <
wb2...@gmail.com>.
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user