IE Toolbar Help

http://www.15seconds.com/Issue/070208.htm

Windows XP service shortcut

Windows XP has a shortcut which can be activated by put it into “Run” menu.

example of service name which can be activated by through “Run” menu.

* Component Services – comexp.msc
* Computer Management – compmgmt.msc
* Device Manager – devmgmt.msc
* Disk Defrag – dfrg.msc
* Disk Managment – diskmgmt.msc
* Event Viewer – eventvwr.msc
* Group Policies – gpedit.msc
* Local Security Settings – secpol.msc
* Local Users and Groups – lusrmgr.msc
* Performance Monitor – perfmon.msc
* Resultant Set of Policies – rsop.msc
* Services – services.msc
* Shared Folders – fsmgmt.msc

What's a MOSS 2007 vs. WSS v3 Feature?

Have you installed the MOSS 2007 beta yet? If so, taken any time to understand what Features are?

If not, check out Ted Pattison's "What Are Features?" post... his first sentence nails it: "Features are awesome." I've got a few more links on features on my WCM linkfest: http://andrewconnell.com/blog/articles/MossWcmResources.aspx#Features

Let's say you've poked under the hood to see all the Features you get when you install MOSS. Where will you find them? In the 12 hive of course: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATES\FEATURES.

One thing to note is that Features aren't a MOSS-only thing... they are an inherit addition to the foundation of SharePoint: WSS. I'm guessing most people out there have installed the MOSS 2007 beta bits and not played with the WSS v3 beta bits without MOSS. So, if you've installed MOSS 2007, how do you know which Features are included with the free part of SharePoint (WSS) and which ones are added by MOSS (see Figure 1 below)? Some are easy to spot as MOSS only Features.. for example, the ExcelServer* Features are obviously part of Excel Services, a component to MOSS... the MySite* Features deal with My Sites, another MOSS-only thing... OSearch* Features are for the advanced search functionality in MOSS... and finally the Publishing* Features deal with Publishing Sites (aka: Web Content Management). But what about all the others?


Figure 1 (click for larger image)

Instead of having to always compare my MOSS Beta 2 Technical Refresh virtual machine & my WSS v3 Beta 2 Technical Refresh virtual machine, I decided to document them for my own reference and share them here, on my blog, for anyone else to use as a reference.

Windows SharePoint Services v3 Features:
33 Features in WSS v3 AdminLinks
AnnouncementsList
BasicWebParts
ContactsList
ContentLightup
ContentTypeSettings
ctypes
CustomList
DataSourceLibrary
DiscussionsList
DocumentLibrary
EventsList
fields
GanttTasksList
GridList
IssuesList
IssueTrackingWorkflow
LinksList
MobilityRedirect
NoCodeWorkflowLibrary
PictureLibrary
SiteSettings
SPSearchFeature
SurveysList
TasksList
TeamCollab
UpgradeLinks
WebPageLibrary
WikiWelcome
WorkflowHistoryList
WorkflowProcessList
XmlFormLibrary


Microsoft Office SharePoint Services 2007 Features:
107 Features Added in MOSS 2007* AddDashboard
Analytics
AnalyticsLinks
BaseSite
BaseSiteStapling
BaseWeb
BaseWebApplication
BDCAdminUILinks
BDR
BizAppsCTypes
BizAppsFields
BizAppsListTemplates
BizAppsSiteTemplates
BulkWorkflow
BulkWorkflowTimerJob
DataConnectionLibrary
DataConnectionLibraryStapling
DeploymentLinks
DMContentTypeSettings
EawfSite
EawfWeb
EnhancedHtmlEditing
ExcelServer
ExcelServerSite
ExcelServerWebApplication
ExpirationWorkflow
FeaturePushdown
GlobalWebParts
GradualUpgrade
Hold
ipfsAdminLinks
IPFSAdminWeb
IPFSDocumentConversion
IPFSSiteFeatures
IPFSWebFeatures
LegacyDocumentLibrary
ListTargeting
LocalSiteDirectoryControl
LocalSiteDirectoryMetaData
LocalSiteDirectorySettingsLink
MasterSiteDirectoryControl
MigrationLinks
MySite
MySiteBlog
MySiteCleanup
MySiteHost
MySiteLayouts
MySiteNavigation
MySiteQuickLaunch
Navigation
NavigationProperties
OffWFCommon
OSearchBasicFeature
OSearchCentralAdminLinks
OSearchEnhancedFeature
OSearchPortalAdminLinks
OSearchSRPAdminLinks
OsrvLinks
OsrvTasks
OssNavigation
OSSSearchSearchCenterUrlFeature
OSSSearchSearchCenterUrlSiteFeature
PageConverters
PortalLayouts
PremiumRootSite
PremiumRootSiteStapling
PremiumSite
PremiumSiteStapling
PremiumWeb
PremiumWebApplication
ProfileSynch
Publishing
PublishingLayouts
PublishingPrerequisites
PublishingResources
PublishingSite
PublishingStapling
PublishingWeb
RecordsManagement
RedirectPageContentTypeBinding
RelatedLinksScopeSettingsLink
ReportCenterCreation
ReportCenterSampleData
Reporting
ReportListTemplate
ReviewWorkflows
SearchAndProcess
SearchWebParts
SharedServices
SignaturesWorkflow
SitesList
SkuUpgradeLinks
SlideLibrary
SlideLibraryActivation
SpellChecking
SPSDisco
SpsSsoLinks
SRPProfileAdmin
StapledWorkflows
TranslationWorkflow
TransMgmtFunc
TransMgmtLib
UpgradeOnlyFile
UserMigrator
ViewFormPagesLockDown
WebPartAdderGroups


* Two additional features are installed when you upgrade from MOSS 2007 Beta 2 to MOSS Beta 2 Technical Refresh: PublishingB2TRHop2SiteFilesUpgrade & PublishingB2TRSiteFilesUpgrade. These two Features, as their names imply, are used to upgrade some of the publishing files from Beta 2 to Beta 2 Technical Refresh. This also explains why you may have experienced some problems with your existing Publishing sites created in Beta 2 after upgrading to Beta 2 Technical Refresh, as outlined in this post. Because they are upgrade Features, and not likely to be present in the RTM release of MOSS 2007, I am not including them in the count.

.V01, .V02 files

It sounds like your USB drive is formatted FAT32, so that maximum file size
is 4GB, the .V01 and .V02 (and V03 ...) are just extensions of your VHD file
due to the maximum file size allowed by FAT32. You need to keep all of
them...

the .vsv's are from saved state sessions. (you closed a VPC session saving
the state, rather than shutting down the OS.) These would go away if you
just restored the session and then did a normal OS shutdown and the close
without saving state.

Creating New Page Layouts in SharePoint 2007

Major components of the SharePoint publishing architecture



Page layouts are templates that define content structure for a page and are always associated with a content type.

A content type contains a document template, data columns, workflows, and other information that completely define a document.

The publishing feature of MOSS uses a single root content type for publishing called Page. All of the page layouts inherit from this base.

Here’s how to create a new page layout in MOSS.

STEP 1: Define Site Columns
The individual content elements that appear in a page layout are derived from site columns. When you create a page layout, you can use any of the site columns already defined or define your own.

The following diagram illustrates the relationships between the content types declared by the publishing framework.



STEP 2: Define a Content Type
Page layouts have a direct relationship to a content type defined within the site.

The content type is a
collection of site columns,
a page template,
workflows,
and other information that determine the appearance and behavior of a page layout.

In order to create a page layout, you must create a new content type that derives from the existing Page content type.

Inheriting the Page content type allows the new page layout to function correctly within the MOSS content management Feature.

STEP 3: Create the Page Layout
Page layouts are stored in Master Page and Page Layout Gallery (SiteSettings/Modify All Site Setting/Gallaries/). From this gallery, you can create a new page layout and associate it with a content type.

This process makes the site columns that are defined for the content type available to the page layout as field controls that you can place on the page with the SharePoint Designer.

STEP 4: Edit the Page Layout in SharePoint Designer
Once you have created the new page layout, you must open it in the SharePoint Designer so that you can add the desired field controls.

The site columns you defined as part of the content type become available in the SharePoint Designer as field controls that you can place on the page layout.

STEP 5: Publish the New Page Layout
Once the page layout is created, you must publish and approve it so that it becomes available for content authors.

This process is essentially the same as publishing any item in MOSS. First the document is checked in, then it is published, and finally it is approved.

STEP 6: Create a New Page
Once the page layout is published and approved, content authors may use it to create new pages.

This is done in the normal way by selecting the Create Page item from the Site Actions menu.

After the page is created, the field controls may be edited to develop the actual page content.

How do I create a hyperlink to open an outlook new message?

I want to create a "contact us" section. I have seen other websites that when you click a hyperlink that opens up a new e-mail from your own outlook.
It is actually very simply. You could do it with the fallowing code:

Contact Us

This is a anchor tag with href attribute that contents mailto: to tell the mail client where to send the mail.

If your default mail program is outlook then outlook should open with a new email with the address written in the Mail to: bar ready for you to compose your mail.

Source(s):
To know more you could check the link below:

http://personalweb.about.com/cs/beginnin...

FIX: XML File Shows Cached Data When You Use ADO Recordset to Open the File over HTTP

CASE-1:
Issue: While browing the sites the xml changes are showed up in the browser.
Cause: The .xml file is chaed
Solution:
1) clear the temporary internet files (IE) (Tools/Internaet options / General/ Delete temporary internet files.)
2) Clear the browers's (Firefox) private data - Cache (Tools/Clear private data/cache)


CASE-2:

Problem:
When you use the Open method of the ActiveX Data Objects (ADO) Recordset object to open an XML file over HTTP, if you make changes within the XML file, the data that appears does not contain the new modifications. In other words, the browser only displays the data that is cached from the first time you opened the XML file.

The same behavior occurs if you delete the XML file completely and run the same code. In this case, you do not receive an error message, and the browser displays the same data from the first time the XML file was opened.

Cause:
The OpenURLBlockingStream method opens HTTP files. By default, this method always uses cached data if it is available. There is no way to customize this method.

Solution:
To work around this problem, use a straight file path, for example:
rs.Open "c:\testdata.xml"

Original URL:
http://support.microsoft.com/kb/293856