Here is the scenario:

I am writing a web application, and need to make sure that I can deploy it
on NT4/IIS4, or W2K/IIS5, or win95/98/me/PWS. I will optimize for running
the app on W2K/IIS5.

I have followed Microsoft DNA (though not strictly in some cases), and
created DAL, and BLL, with ASP being PL.

My DAL is basically a number of classes that provide accesses to stored
procs (for SQL Server), and my BLL calls the stored procs provided by the
DAL. Now in terms of transactions, I do not need to use MTS because I have
yet to encounter a situation where a stored proc on a sqlserver couldn't
encapsulate the entire transaction or handle the business logic. Now I would
like to use MTS because it is capable of doing resource pooling for me. In
particular, the DAL and BLL components would be created and destroyed as
required by the PL, MTS can cache and preserve frequently used components,
thus optimizing performance.

Now here are the stumbling blocks:

(1) W2K uses COM+ rather than MTS, and a different type library is used. So
would components created for NT4 even run on COM+ under W2K, or vice versa,
can an COM+ component compiled on W2K run on NT4 MTS?

(2) Win95/98/Me do not have MTS at all, and the obviously question is,
whether an MTS enabled component can run at all?

(3) Note that I have marked all of my components to be able to participate
MTS transaction, but does not require a transaction (or new transaction)
because stored procs are completely self encapsulated when it comes to
transaction or business logic. Should I instead mark them as Not An MTS
object at all?

(4) I heard (unsubstantiated) news that IIS5 act as MTS server as well, and
thus I do not need to install MTS packages (as in not having to create an application in COM Service, and register the COM dlls). Is that true?

Thanks in Advance