why wrote:
1. have to use ORDER BY in the above SELECT statements
2. don't use MINUS, which is inefficient

3. suppose we want to get from startNum to endNum from a table "t" with some ordering criteria "k"
3.1 Oracle has ROWNUM, I think the example in the link youlq provided will work after making necessary corrections.
3.2 MySQL and PostgreSQL has LIMIT
3.3 SQL Server, Access, and perhaps FoxPro has "TOP n", try something like
SELECT TOP (endNum-startNum+1) *
FROM (SELECT TOP endNum * FROM t ORDER BY k DESC)
ORDER BY k ASC
(only guess, not tested)

SELECT tRANGE.*
FROM (SELECT TOP (endNum-startNum+1) tTOP.*
      FROM (SELECT TOP endNum * FROM t ORDER BY k ASC) tTOP
      ORDER BY tTOP.k DESC) tRANGE
ORDER BY tRANGE.k ASC

MINUS operator - Not supported
Use NOT EXISTS clause in your SELECT statement to generate the same result.

The following example illustrates the simulation of Oracle's MINUS operator:

SELECT OrderID, OrderDate
FROM Orders O
WHERE NOT EXISTS
(
SELECT 1
FROM RefundsTable R
WHERE O.OrderID = R.OrderID
)

rownum pseudo column - No equivalent
Though there is no rownum or rowid in SQL Server, there are several ways in which a row number can be generated.

For some examples, read this article:
Q186133 INF: How to Dynamically Number Rows in a Select Statement

SELECT tRANGE.*
FROM (SELECT tTOP.*
      FROM (SELECT * FROM t ORDER BY k ASC FETCH FIRST endNum ROW ONLY) tTOP
      ORDER BY tTOP.k DESC
      FETCH FIRST (endNum-startNum+1) ROW ONLY) tRANGE
ORDER BY tRANGE.k ASC

SELECT tTOP.*
FROM (SELECT ROWNUMBER() OVER (ORDER BY k) AS rownum, t.*
      FROM t ORDER BY k ASC
      FETCH FIRST endNum ROW ONLY) tTOP
WHERE tTOP.rownum BETWEEN startNum AND endNum