...\60\TEMPLATE\1033\XMLWEBTEMPSPS.XML

Just as Microsoft's recommendation for creating  new site  definitions
was to copy  STS and modify the copy, I'm want to copy sps  and modify
that copy.

The WEBTEMPSPS.XML file refers to the SPS site definition  as
name "SPS", or ID of "20".

IF SharePoint is hardcoded to use the "SPS" site definition for new
portals, then I must modify the files  in in the SPS directory
directly, since the name is also the directory, and I would then be
prevented from modifying  the name or directory.

IF SharePoint was hardcoded to use ID of "20" for new portals, then
I would need to modify the WEBTEMPSPS.XML file to change the site
definition for "20". Then I could use my own site definition
name/directory.

Ideally, a configuration file somewhere would specify the portal
template is name of "SPS" or ID of "20". Then I could change it to
create portals with "QSPS" or ID of "10020". It seems arbitrary that
SharePoint portal  would use "20". If it always uses "SPS" then I'm
stuck renaming directories or modifying the files in place.

I'm still experimenting...

WEBTEMPSPS.XML:
<Template Name="SPS" ID="20">
<Configuration ID="0" Title="SharePoint Portal Server Site"
Type="0" Hidden="TRUE" ImageUrl="../images/spshome.gif"
Description="This web template provides a collaborative solution
that enables teams to create, organize, and share informatin faster
and easier than ever before. It includes a Document Library,
Announcements, Events, Contacts, Quick Links and other basic
lists."> <!-- _locID@Title="webtemp_title_sps0"
_locComment="{StringCategory=HTX}" --> <!--
_locID@Description="webtemp_desc_sps0"
_locComment="{StringCategory=HTX}" --> </Configuration>
</Template>

I understand. I'd have to experiment too because I haven't ever tried to
do this. I'm a WSS guy, remember.

If hardcoded, I hope that it is hardcoded to the ID (20) rather than
SPS. That way, you could associate another Site Definition with 20 and
the only change to the underlying built-in files  would be to modify the
existing WEBTEMPSPS.XML entry to point to your own Site Definition. Let
us know what you discover.

By the way, I converted my RevertToAppPool class to VB.NET for the class
I taught this week and tested it out. Lots of trial and error but in the
end I got it working. I love the way it works. Much better than my
previous SimulatedUser class. I did discover two things:

1. I can't have a different Namespace for the class. I think it must not
be marked as safe.
2. I had to bump the trust level to Full. Anyone know what specific
IPermissions are required for API calls?

The "SPS" name is used by SharePoint to locate site  definitions for
creating portals. The ID can be changed from 20 to other numbers and
SharePoint will continue to use the same SPS site definition.

That makes  sense but can you change the "SPS" to another directory  name
in the WEBTEMPSPS.XML file?

So, create  a new directory called QSPS as a sister to the SPS directory
containing a copy  of everything in the SPS directory. Alter something in
the QSPS directory so that we can know if the change is successful.
Create a new Portal.

I suspect that SharePoint Portal Server will use the new QSPS directory
rather than the SPS directory. The only alteration to Microsoft's own
site definition  files will be to the WEBTEMPSPS.XML file.