Contents
WPM Home
Introduction to WPM
WPM News
WPM FAQ
ASMS v0.0.5
Feedback
|
Have you ever been frustrated by an personal
computer application that suddenly stopped working? Have you ever
had to re-install an entire application to fix a problem? Have you
ever tried to remove an application and found out later that some of it's
components still exist on your hard drive? Have you ever looked
at a file on your hard drive and wondered which applications rely on it?
Have you ever installed an application, only to find out another application
no
longer works? After that, were you hesitant to install another software
package because you were nervous about what it would do to your computer?
Have you ever wiped out your entire operating system and re-installed
it because it got slower and slower as time went on?
If you can identify with any of these problems, you are not alone.
Managing applications is a huge headache for nearly every computer user,
and is getting larger as applications grow in size and complexity. Installing
an application such as an office suite can add thousands of new
files to your system. Currently there is no way to manage these files.
There is no way to:
-
determine which applications rely on a certain file
-
determine which components make up a certain application
-
determine which components are no longer used
This situation creates five real world problems:
-
applications cannot be removed from your system without relying on a third
party utility (like CleanSweep or Uninstaller) or with an uninstall program
packaged with the application or operating system. Your mileage will vary.
-
application problems cannot be easily diagnosed.
-
installing a new application can break other applications by overwriting
existing files. Problems may not be discovered until much later, making
troubleshooting very difficult.
-
applications cannot be easily moved from one system to another.
-
as applications are installed and deleted, unused components accumulate
and reduce system performance. This phenomenon has been referred to OS
Drift*
* a term first seen in a Ziff-Davis magazine, probably PC Week or
PC Magazine
The personal computer industry is stuck with these problems because
the internal structure of applications is unknown. When you install an
application, you don't know what the install routine is doing to your system.
If the setup program needs to overwrite a file, you may get to choose
whether to proceed or not. How do you make that decision? Of the thousands
of files on your computer, how do you know if the file the install program
wants to overwrite belongs to an application that you need? Currently,
there is no way to know, short of pulling out the vendor's documentation
on every single application and hoping this information is provided.
Windows Package Management (WPM) views an application as a single entity, or package, and allows applications to be managed as such. The Application Structure Modeling Standard (ASMS) is the component of WPM which documents the structure of an application. It identifies the files and settings that make up an application. This information is provided in a text file that can be read by any program. WPM allows for management throughout the
entire life of an application - installation, troubleshooting and removal.
WPM is based on a free and open standard, available for anyone to use without
payment of royalties or any other fees.
Windows Package Mangement only exists today as an 'early
beta'. It needs your help to come to fruition. Please look it over
and provide your feedback, no matter what your experience level is. WPM
depends on support from the user community in order to be successful. Please
send your feedback and tell someone about WPM today! |