Review: "Air Force One"
W.J. Rayment / Conservative Bookstore -- The first president to get air-born was Franklin Delano Roosevelt. He found air travel to be quick, if not always convenient or comfortable. He was succeeded by Truman who made sure that there was a presidential plane that lived up to the dignity of the president. The press called it the "Sacred Cow", for obvious reasons, even though Truman had named it the "Independence". Then Ike became president in 1953. He scaled back some of the amenities that had been built into the "Sacred Cow" and dubbed the new presidential plane "The Columbine" (after the official flower of his wife's native state, Colorado).
The call sign for Ike's aircraft was "Air Force 610". When this was used on a flight to Florida it was briefly confused with "Eastern 610" a commercial flight. Although it caused no difficulties at the time the pilot, Col. Bill Draper, thought this could result in a dangerous misunderstanding in the future; so he quickly chose a call sign that would be confused with no other, "Air Force One". The press got wind of the new call sign and attached it to the presidential aircraft. So it has been called "Air Force One" in all its various manifestations ever since.
Kenneth T. Walsh's book "Air Force One" is loaded with fascinating stories about the famous aircraft and the men who flew in it. He has done a magnificent job researching each president, presenting anecdote after anecdote told by leading figures within each administration, including many of the past presidents themselves.
There are chapters covering each of the flying presidents telling how each used the plane and how the plane itself revealed the true personality of its most famous occupant. This is one of the major themes of the book. Mr. Walsh comments on the leadership style of each president, his accomplishments, his drawbacks. Each president had his good points as well as bad - in the tight quarters and sometimes long hours of travel in Air Force One this would be revealed to those who were not always close to him in the White House. Johnson was gruff and crude, Nixon reclusive and brooding, Kennedy polite and enthusiastic but sometimes ill and inconsiderate of his wife.
Famous incidents occurred on Air Force One like Johnson's swearing into office after Kennedy's assassination. Johnson prevailed upon the shocked and grieving Jackie Kennedy literally to stand beside him while he took the oath as the plane sat on the ground in Texas. She was still in her blood-spattered dress. Johnson wanted her to be prominent in the photos of the event so that the world would see him as the legitimate heir of the administration. The Kennedy clan never forgave Johnson for this callous act. After the swearing in, Jackie went to sit near the coffin containing her dead husband as "Air Force One" winged its way back to Washington D.C.
Many weighty decisions have been made in the air. This is where Nixon first considered bombing Cambodia during the Viet Nam War, and where he first learned of the Watergate break-in. This is where presidents have gotten closest to the press. This is where speeches have been written and critiqued, and where presidents have escaped from adoring or jeering crowds. All this is part of the "Air Force One" story, and it is a story well worth reading.
Mr. Walsh's writing style is fluid and engrossing. His analysis is cogent and pointed. What is more, his stories have a point, giving the reader insights into history and politics. When all is said and done, "Air Force One" is a fun and informative read.
Friday, August 13, 2004
Wednesday, August 04, 2004
(mathematics) googol - The number represented in base-ten by a one with a hundred zeroes after it.According to Webster's Dictionary, the name was coined in 1938 by Milton Sirotta, the nine-year-old nephew of American mathematician, Edward Kasner
(mathematics) googolplex - The number represented in base-ten by a one with a googol zeroes after it.
(mathematics) googolplex - The number represented in base-ten by a one with a googol zeroes after it.
Sunday, August 01, 2004
Advice to employees on the proper useof the System Administrator's valuable time
(In following examples, we will substitute the name "Ted" as the System Administrator)
Play with all the wires you can find. If you can't find enough, open something up to expose them. After you have finished, and nothing works anymore, put it all back together and call Ted. Deny that you touched anything and that it was working perfectly only five minutes ago. Ted just loves a good mystery. For added effect you can keep looking over his shoulder and ask what each wire is for.
Never write down error messages. Just click OK, or restart your computer. Ted likes to guess what the error message was.
When talking about your computer, use terms like "Thingy" and "Big Connector."
If you get an EXE file in an email attachment, open it immediately. Ted likes to make sure the anti-virus software is working properly.
When Ted says he coming right over, log out and go for coffee. It's no problem for him to remember your password.
When you call Ted to have your computer moved, be sure to leave it buried under a year-old pile of postcards, baby pictures, stuffed animals, dried flowers, unpaid bills, bowling trophies and Popsicle sticks. Ted doesn't have a life, and he finds it deeply moving to catch a glimpse of yours.
When Ted sends you an email marked as "Highly Important" or "Action Required", delete it at once. He's probably just testing some new-fangled email software.
When Ted's eating lunch at his desk or in the lunchroom, walk right in, grab a few of his fries, then spill your guts and expect him to respond immediately. Ted lives to serve, and he's always ready to think about fixing computers, especially yours.
When Ted's at the water cooler or outside taking a breath of fresh air, find him and ask him a computer question. The only reason he takes breaks at all is to ferret out all those employees who don't have email or a telephone.
Send urgent email ALL IN UPPERCASE. The mail server picks it up and flags it as a rush delivery.
When the photocopier doesn't work, call Ted. There's electronics in it, so it should be right up his alley.
When you're getting a NO DIAL TONE message at your home computer, call Ted. He enjoys fixing telephone problems from remote locations. Especially on weekends.
When something goes wrong with your home PC, dump it on Ted's chair the next morning with no name, no phone number, and no description of the problem. Ted just loves a good mystery.
When you have Ted on the phone walking you through changing a setting on your PC, read the newspaper. Ted doesn't actually mean for you to DO anything. He just loves to hear himself talk.
When your company offers training on an upcoming OS upgrade, don't bother to sign up. Ted will be there to hold your hand when the time comes.
When the printer won't print, re-send the job 20 times in rapid succession. That should do the trick.
When the printer still won't print after 20 tries, send the job to all the printers in the office. One of them is bound to work.
Don't use online help. Online help is for wimps.
Don't read the operator's manual. Manuals are for wussies.
If you're taking night classes in computer science, feel free to demonstrate your fledgling expertise by updating the network drivers for you and all your co-workers. Ted will be grateful for the overtime when he has to stay until 2:30am fixing all of them.
When Ted's fixing your computer at a quarter past one, eat your Whopper with cheese in his face. He functions better when he's slightly dizzy from hunger.
When Ted asks you whether you've installed any new software on your computer, LIE. It's no one else's business what you've got on your computer.
If the mouse cable keeps knocking down the framed picture of your dog, lift the monitor and stuff the cable under it. Those skinny Mouse cables were designed to have 55 lbs. of computer monitor crushing them.
If the space bar on your keyboard doesn't work, blame Ted for not upgrading it sooner. Hell, it's not your fault there's a half pound of pizza crust crumbs, nail clippings, and big sticky drops of Mountain Dew under the keys.
When you get the message saying "Are you sure?", click the "Yes" button as fast as you can. Hell, if you weren't sure, you wouldn't be doing it, would you?
Feel perfectly free to say things like "I don't know nothing about that boneheaded computer crap." It never bothers Ted to hear his area of professional expertise referred to as boneheaded crap.
Don't even think of breaking large print jobs down into smaller chunks. God forbid somebody else should sneak a one-page job in between your 500-page Word document.
When you send that 500-page document to the printer, don't bother to check if the printer has enough paper. That's Ted's job.
When Ted calls you 30 minutes later and tells you that the printer printed 24 pages of your 500-page document before it ran out of paper, and there are now nine other jobs in the queue behind yours, ask him why he didn't bother to add more paper.
When you receive a 130 MB movie file, send it to everyone as a high-priority mail attachment. Ted's provided plenty of disk space and processor capacity on the new mail server for just those kinds of important things.
When you bump into Ted in the grocery store on a Sunday afternoon, ask him computer questions. He works 24/7, and is always thinking about computers, even when he's at super-market buying toilet paper and doggie treats.
If your son is a student in computer science, have him come in on the weekends and do his projects on your office computer. Ted will be there for you when your son's illegal copy of Visual Basic 6.0 makes the Access database keel over and die.
When you bring Ted your own "no-name" brand PC to repair for free at the office, tell him how urgently he needs to fix it so you can get back to playing EverQuest. He'll get on it right away, because everyone knows he doesn't do anything all day except surf the Internet.
Don't ever thank Ted. He loves fixing everything AND getting paid for it!
(In following examples, we will substitute the name "Ted" as the System Administrator)
Play with all the wires you can find. If you can't find enough, open something up to expose them. After you have finished, and nothing works anymore, put it all back together and call Ted. Deny that you touched anything and that it was working perfectly only five minutes ago. Ted just loves a good mystery. For added effect you can keep looking over his shoulder and ask what each wire is for.
Never write down error messages. Just click OK, or restart your computer. Ted likes to guess what the error message was.
When talking about your computer, use terms like "Thingy" and "Big Connector."
If you get an EXE file in an email attachment, open it immediately. Ted likes to make sure the anti-virus software is working properly.
When Ted says he coming right over, log out and go for coffee. It's no problem for him to remember your password.
When you call Ted to have your computer moved, be sure to leave it buried under a year-old pile of postcards, baby pictures, stuffed animals, dried flowers, unpaid bills, bowling trophies and Popsicle sticks. Ted doesn't have a life, and he finds it deeply moving to catch a glimpse of yours.
When Ted sends you an email marked as "Highly Important" or "Action Required", delete it at once. He's probably just testing some new-fangled email software.
When Ted's eating lunch at his desk or in the lunchroom, walk right in, grab a few of his fries, then spill your guts and expect him to respond immediately. Ted lives to serve, and he's always ready to think about fixing computers, especially yours.
When Ted's at the water cooler or outside taking a breath of fresh air, find him and ask him a computer question. The only reason he takes breaks at all is to ferret out all those employees who don't have email or a telephone.
Send urgent email ALL IN UPPERCASE. The mail server picks it up and flags it as a rush delivery.
When the photocopier doesn't work, call Ted. There's electronics in it, so it should be right up his alley.
When you're getting a NO DIAL TONE message at your home computer, call Ted. He enjoys fixing telephone problems from remote locations. Especially on weekends.
When something goes wrong with your home PC, dump it on Ted's chair the next morning with no name, no phone number, and no description of the problem. Ted just loves a good mystery.
When you have Ted on the phone walking you through changing a setting on your PC, read the newspaper. Ted doesn't actually mean for you to DO anything. He just loves to hear himself talk.
When your company offers training on an upcoming OS upgrade, don't bother to sign up. Ted will be there to hold your hand when the time comes.
When the printer won't print, re-send the job 20 times in rapid succession. That should do the trick.
When the printer still won't print after 20 tries, send the job to all the printers in the office. One of them is bound to work.
Don't use online help. Online help is for wimps.
Don't read the operator's manual. Manuals are for wussies.
If you're taking night classes in computer science, feel free to demonstrate your fledgling expertise by updating the network drivers for you and all your co-workers. Ted will be grateful for the overtime when he has to stay until 2:30am fixing all of them.
When Ted's fixing your computer at a quarter past one, eat your Whopper with cheese in his face. He functions better when he's slightly dizzy from hunger.
When Ted asks you whether you've installed any new software on your computer, LIE. It's no one else's business what you've got on your computer.
If the mouse cable keeps knocking down the framed picture of your dog, lift the monitor and stuff the cable under it. Those skinny Mouse cables were designed to have 55 lbs. of computer monitor crushing them.
If the space bar on your keyboard doesn't work, blame Ted for not upgrading it sooner. Hell, it's not your fault there's a half pound of pizza crust crumbs, nail clippings, and big sticky drops of Mountain Dew under the keys.
When you get the message saying "Are you sure?", click the "Yes" button as fast as you can. Hell, if you weren't sure, you wouldn't be doing it, would you?
Feel perfectly free to say things like "I don't know nothing about that boneheaded computer crap." It never bothers Ted to hear his area of professional expertise referred to as boneheaded crap.
Don't even think of breaking large print jobs down into smaller chunks. God forbid somebody else should sneak a one-page job in between your 500-page Word document.
When you send that 500-page document to the printer, don't bother to check if the printer has enough paper. That's Ted's job.
When Ted calls you 30 minutes later and tells you that the printer printed 24 pages of your 500-page document before it ran out of paper, and there are now nine other jobs in the queue behind yours, ask him why he didn't bother to add more paper.
When you receive a 130 MB movie file, send it to everyone as a high-priority mail attachment. Ted's provided plenty of disk space and processor capacity on the new mail server for just those kinds of important things.
When you bump into Ted in the grocery store on a Sunday afternoon, ask him computer questions. He works 24/7, and is always thinking about computers, even when he's at super-market buying toilet paper and doggie treats.
If your son is a student in computer science, have him come in on the weekends and do his projects on your office computer. Ted will be there for you when your son's illegal copy of Visual Basic 6.0 makes the Access database keel over and die.
When you bring Ted your own "no-name" brand PC to repair for free at the office, tell him how urgently he needs to fix it so you can get back to playing EverQuest. He'll get on it right away, because everyone knows he doesn't do anything all day except surf the Internet.
Don't ever thank Ted. He loves fixing everything AND getting paid for it!
Change Background Image when installing Windows
The first thing you need before you do anything, is a program that can open up, and examine the innards of the WINNTBBU.DLL. The program i use is Resource Tuner. Most people use Resource Hacker (cause its freeware), but i find this one alot more user friendly.
Whilst that is downloading, you may wish to extract the WINNTBBU.DLL from your I386 Directory on your WindowsXP CD, and chuck it in a folder someplace. I recommend making a brand spanking new folder where you can store all your new setup screen goodies, so you have them all in the one spot when you need them.
Download is done? Excellent. Give Resource Tuner the good ol' install treatment, and when you're done, execute the application.
From there, you'd want to select File --> Open and then select your WINNTBBU.DLL file you extracted earlier. Since Resource Tuner is a 30 day trial program, it'll ask you to register blah blah, just smash continue.
Your screen should look like this:
If you expand the bitmap subfolder, you'll see lots of little enteries that start with 100, and go up to 192. Now all of them arent there, so dont be alarmed. It goes from 100 to 109, then skips straight to 150. This is normal. You're not missing any enteries, so take thoes fingernails out of your mouth.
If you have a little browse through the enteries in the bitmap subcategory by clicking on a few, you'll notice that each one holds a different bitmap image. These are what you will be editing, and replacing, in order to make your install screens look spiffy.
You will notice that there are several versions of each bitmap image. One set are for 1024 x 768 (high resolution) and the other set are for 640 x 480 (Low resolution). We will be editing the high resolution images.
Here is a brief explanation of where the bitmap files you will need are located:
100 - Windows Logo in the top left hand corner.101 - Windows Logo in the top left hand corner.102 - Windows Logo in the top left hand corner.103 - The main background image.104 - Image shown next to the task when it has been completed.105 - Image shown next to the task which has not been completed.109 - Image shown next to the task when it is being performed.181 - 192 - Little animating images in the bottom right hand corner of the setup screen.
Okay. From then on, all you need to do is Right click on the image you wish to edit, and select Save Resource As... and choose a location to save the image.
Once you've extracted an image, its time to edit it. Any graphics editing program will suffice. Change it how you wish. The only limits are, that the backdrop must be 1024 x 768, and all images must be in 256 colours. I find it easier to make the image, then convert it to 256 colours at the end.
So now you have your new image that you want to throw back into the WINNTBBU.DLL. This is how you do it.
Back in your resource tuner, select the key that you extracted the image from, right click --> edit resource. On the next screen, you need to press the Open Resource button, illustrated below.
From there, select your edited bitmap. Next, select Ok. Select Yes from the next dialog box.
Follow thoes last few steps to editing your bitmap files, for all the other bitmaps you wish to change, save your new WINNTBBU.DLL (File --> Save File As...) and bobs your monkey! But don't relax yet ... we're not done.
By this point, you should have all your bitmaps replaced in the WINNTBBU.DLL file.
You're almost done! Open up a command prompt (windows key + R, then type in cmd) and navigate to the directory where you saved your WINNTBBU.DLL. (If you dont know how to navigate directorys through dos, i suggest you find out)
Next, at the command prompt, type in this command.makecab winntbbu.dll
This will create a file called winntbbu.dl_ in the same directory.All you need to do now is throw that file you just created (winntbbu.dl_) into your i386 folder on your XP CD, and thats it!
Congratulations, you've just changed your XP Setup Screens! Give yourself a pat on the back and a chocolate eclair. You've earnt it.
Note: You do NOT need to put the new WINNTBBU.DLL file into your i386 directory. Only the winntbbu.dl_
The first thing you need before you do anything, is a program that can open up, and examine the innards of the WINNTBBU.DLL. The program i use is Resource Tuner. Most people use Resource Hacker (cause its freeware), but i find this one alot more user friendly.
Whilst that is downloading, you may wish to extract the WINNTBBU.DLL from your I386 Directory on your WindowsXP CD, and chuck it in a folder someplace. I recommend making a brand spanking new folder where you can store all your new setup screen goodies, so you have them all in the one spot when you need them.
Download is done? Excellent. Give Resource Tuner the good ol' install treatment, and when you're done, execute the application.
From there, you'd want to select File --> Open and then select your WINNTBBU.DLL file you extracted earlier. Since Resource Tuner is a 30 day trial program, it'll ask you to register blah blah, just smash continue.
Your screen should look like this:
If you expand the bitmap subfolder, you'll see lots of little enteries that start with 100, and go up to 192. Now all of them arent there, so dont be alarmed. It goes from 100 to 109, then skips straight to 150. This is normal. You're not missing any enteries, so take thoes fingernails out of your mouth.
If you have a little browse through the enteries in the bitmap subcategory by clicking on a few, you'll notice that each one holds a different bitmap image. These are what you will be editing, and replacing, in order to make your install screens look spiffy.
You will notice that there are several versions of each bitmap image. One set are for 1024 x 768 (high resolution) and the other set are for 640 x 480 (Low resolution). We will be editing the high resolution images.
Here is a brief explanation of where the bitmap files you will need are located:
100 - Windows Logo in the top left hand corner.101 - Windows Logo in the top left hand corner.102 - Windows Logo in the top left hand corner.103 - The main background image.104 - Image shown next to the task when it has been completed.105 - Image shown next to the task which has not been completed.109 - Image shown next to the task when it is being performed.181 - 192 - Little animating images in the bottom right hand corner of the setup screen.
Okay. From then on, all you need to do is Right click on the image you wish to edit, and select Save Resource As... and choose a location to save the image.
Once you've extracted an image, its time to edit it. Any graphics editing program will suffice. Change it how you wish. The only limits are, that the backdrop must be 1024 x 768, and all images must be in 256 colours. I find it easier to make the image, then convert it to 256 colours at the end.
So now you have your new image that you want to throw back into the WINNTBBU.DLL. This is how you do it.
Back in your resource tuner, select the key that you extracted the image from, right click --> edit resource. On the next screen, you need to press the Open Resource button, illustrated below.
From there, select your edited bitmap. Next, select Ok. Select Yes from the next dialog box.
Follow thoes last few steps to editing your bitmap files, for all the other bitmaps you wish to change, save your new WINNTBBU.DLL (File --> Save File As...) and bobs your monkey! But don't relax yet ... we're not done.
By this point, you should have all your bitmaps replaced in the WINNTBBU.DLL file.
You're almost done! Open up a command prompt (windows key + R, then type in cmd) and navigate to the directory where you saved your WINNTBBU.DLL. (If you dont know how to navigate directorys through dos, i suggest you find out)
Next, at the command prompt, type in this command.makecab winntbbu.dll
This will create a file called winntbbu.dl_ in the same directory.All you need to do now is throw that file you just created (winntbbu.dl_) into your i386 folder on your XP CD, and thats it!
Congratulations, you've just changed your XP Setup Screens! Give yourself a pat on the back and a chocolate eclair. You've earnt it.
Note: You do NOT need to put the new WINNTBBU.DLL file into your i386 directory. Only the winntbbu.dl_
Tuesday, June 22, 2004
Download details: Group Policy Management Console with Service Pack 1
Group Policy Management Console with Service Pack 1
The Microsoft Group Policy Management Console (GPMC) with Service Pack 1 (SP1) unifies management of Group Policy across the enterprise. The GPMC consists of a MMC snap-in and a set of programmable interfaces for managing Group Policy.
Quick Info
File Name:
gpmc.msi
Download Size:
5686 KB
Date Published:
6/15/2004
Version:
1.0.2
Overview
GPMC simplifies the management of Group Policy by making it easier to understand, deploy, manage, and troubleshoot Group Policy implementations. GPMC also enables automation of Group Policy operations via scripting.
GPMC can be used to manage Windows Server 2003 as well as Windows 2000-based Group Policy implementations. Customers who have at least one valid license of Windows Server 2003 or Windows 2000 Server can obtain and use an unlimited number of copies of GPMC. Please see the End User License Agreement (EULA) provided with the GPMC software for details on licensing terms.
Key features delivered via GPMC include:
A unified graphical user interface (GUI) that makes Group Policy much easier to use.
Backup/restore of Group Policy objects (GPOs).
Import/export and copy/paste of GPOs and Windows Management Instrumentation (WMI) filters.
Simplified management of Group Policy–related security.
HTML reporting for GPO settings and Resultant Set of Policy (RSoP) data.
Scripting of Group Policy related tasks that are exposed within this tool (not scripting of settings within a GPO).
Prior to GPMC, administrators were required to use several Microsoft tools to manage Group Policy. GPMC integrates the existing Group Policy functionality exposed in these tools into a single, unified console, along with the new capabilities listed above.
GPMC with SP1 contains the following updates:
Various bug fixes. GPMC with SP1 fixes customer-reported bugs found in GPMC sample scripts, GPO reporting, and in the Migration Table Editor (MTE). Furthermore, fixes have been provided to address bugs found from Dr. Watson crash data and to allow the GPMC RSoP wizard to properly function if Internet Connection Firewall (ICF) is enabled on the computer running GPMC.
New languages. GPMC with SP1 is now also available in French, German, Japanese, Simplified Chinese, Traditional Chinese, and Spanish.
Updated GPMC EULA. GPMC with SP1 includes an updated end-user license agreement (EULA) that allows GPMC with SP1 to be installed as long as you have a valid Windows Server 2003 or Windows 2000 Server license. For more information, see the GPMC EULA, which is shown during installation of GPMC with SP1.
Updated MSXML4. MSXML4 has been updated from MSXML4 SP1 to MSXML4 SP2.
Group Policy Management Console with Service Pack 1
English
--------------------------------------------------------------------------------
Change language
Chinese (Simplified)Chinese (Traditional)EnglishFrenchGermanJapaneseSpanish
Related Resources
Order the Free Windows Platform Manageability Kit
Enterprise Management with the Group Policy Management Console
Become a Microsoft Certified Desktop Support Technician
Group Policy in Windows Server 2003
System Requirements
Supported Operating Systems: Windows Server 2003, Windows XP
GPMC runs on Windows XP Professional SP1 and Windows Server 2003 computers and can manage Group Policy in either Windows 2000 or Windows Server 2003 domains.
For Windows XP Professional users, you must have the following installed prior to installing the GPMC:
Windows XP Service Pack 1
.NET Framework
Your domain controllers must be running Windows 2000 with Service Pack 2 or later. Windows 2000 Service Pack 3 is recommended. Domain controller(s) located in an external forest must have Windows 2000 Service Pack 3 or later installed if you will be accessing those domain controllers from a computer running GPMC, because GPMC requires signing and encryption of all LDAP communications. If do not have Service Pack 3 or later installed on the Windows 2000 domain controller(s) in an external forest, you can temporarily relax LDAP signing and encryption requirements by modifying the registry of the computer running GPMC, as described in Knowledge Base Article 325465.
When installing the GPMC on Windows XP Professional with SP1, GPMC Setup prompts you to install Windows XP QFE Q326469 if it is not already present. This QFE updates your version of gpedit.dll to version 5.1.2600.1186, which is required by GPMC. This QFE will be made available in Windows XP Service Pack 2.
If the language version of the GPMC doesn't match the language of your operating system, GPMC will not install the QFE. You will need to separately obtain and install this QFE. To obtain this QFE, please see Knowledge Base Article 326469.
Notes:
The GPMC does not run on 64-bit versions of Microsoft Windows.
Setup for GPMC with SP1 automatically removes the original version before installing the new version. However, if you have installed any pre-release versions of GPMC (such as beta or release candidate versions), you must first remove the pre-release version of GPMC before installing GPMC with SP1.
The sample scripts that shipped with the previously released version of GPMC will be replaced with new sample scripts included in GPMC with SP1. If you modified any of the sample scripts and you want to preserve those changes, rename your modified sample scripts to a different file name before installing GPMC with SP1.
Group Policy Management Console with Service Pack 1
The Microsoft Group Policy Management Console (GPMC) with Service Pack 1 (SP1) unifies management of Group Policy across the enterprise. The GPMC consists of a MMC snap-in and a set of programmable interfaces for managing Group Policy.
Quick Info
File Name:
gpmc.msi
Download Size:
5686 KB
Date Published:
6/15/2004
Version:
1.0.2
Overview
GPMC simplifies the management of Group Policy by making it easier to understand, deploy, manage, and troubleshoot Group Policy implementations. GPMC also enables automation of Group Policy operations via scripting.
GPMC can be used to manage Windows Server 2003 as well as Windows 2000-based Group Policy implementations. Customers who have at least one valid license of Windows Server 2003 or Windows 2000 Server can obtain and use an unlimited number of copies of GPMC. Please see the End User License Agreement (EULA) provided with the GPMC software for details on licensing terms.
Key features delivered via GPMC include:
A unified graphical user interface (GUI) that makes Group Policy much easier to use.
Backup/restore of Group Policy objects (GPOs).
Import/export and copy/paste of GPOs and Windows Management Instrumentation (WMI) filters.
Simplified management of Group Policy–related security.
HTML reporting for GPO settings and Resultant Set of Policy (RSoP) data.
Scripting of Group Policy related tasks that are exposed within this tool (not scripting of settings within a GPO).
Prior to GPMC, administrators were required to use several Microsoft tools to manage Group Policy. GPMC integrates the existing Group Policy functionality exposed in these tools into a single, unified console, along with the new capabilities listed above.
GPMC with SP1 contains the following updates:
Various bug fixes. GPMC with SP1 fixes customer-reported bugs found in GPMC sample scripts, GPO reporting, and in the Migration Table Editor (MTE). Furthermore, fixes have been provided to address bugs found from Dr. Watson crash data and to allow the GPMC RSoP wizard to properly function if Internet Connection Firewall (ICF) is enabled on the computer running GPMC.
New languages. GPMC with SP1 is now also available in French, German, Japanese, Simplified Chinese, Traditional Chinese, and Spanish.
Updated GPMC EULA. GPMC with SP1 includes an updated end-user license agreement (EULA) that allows GPMC with SP1 to be installed as long as you have a valid Windows Server 2003 or Windows 2000 Server license. For more information, see the GPMC EULA, which is shown during installation of GPMC with SP1.
Updated MSXML4. MSXML4 has been updated from MSXML4 SP1 to MSXML4 SP2.
Group Policy Management Console with Service Pack 1
English
--------------------------------------------------------------------------------
Change language
Chinese (Simplified)Chinese (Traditional)EnglishFrenchGermanJapaneseSpanish
Related Resources
Order the Free Windows Platform Manageability Kit
Enterprise Management with the Group Policy Management Console
Become a Microsoft Certified Desktop Support Technician
Group Policy in Windows Server 2003
System Requirements
Supported Operating Systems: Windows Server 2003, Windows XP
GPMC runs on Windows XP Professional SP1 and Windows Server 2003 computers and can manage Group Policy in either Windows 2000 or Windows Server 2003 domains.
For Windows XP Professional users, you must have the following installed prior to installing the GPMC:
Windows XP Service Pack 1
.NET Framework
Your domain controllers must be running Windows 2000 with Service Pack 2 or later. Windows 2000 Service Pack 3 is recommended. Domain controller(s) located in an external forest must have Windows 2000 Service Pack 3 or later installed if you will be accessing those domain controllers from a computer running GPMC, because GPMC requires signing and encryption of all LDAP communications. If do not have Service Pack 3 or later installed on the Windows 2000 domain controller(s) in an external forest, you can temporarily relax LDAP signing and encryption requirements by modifying the registry of the computer running GPMC, as described in Knowledge Base Article 325465.
When installing the GPMC on Windows XP Professional with SP1, GPMC Setup prompts you to install Windows XP QFE Q326469 if it is not already present. This QFE updates your version of gpedit.dll to version 5.1.2600.1186, which is required by GPMC. This QFE will be made available in Windows XP Service Pack 2.
If the language version of the GPMC doesn't match the language of your operating system, GPMC will not install the QFE. You will need to separately obtain and install this QFE. To obtain this QFE, please see Knowledge Base Article 326469.
Notes:
The GPMC does not run on 64-bit versions of Microsoft Windows.
Setup for GPMC with SP1 automatically removes the original version before installing the new version. However, if you have installed any pre-release versions of GPMC (such as beta or release candidate versions), you must first remove the pre-release version of GPMC before installing GPMC with SP1.
The sample scripts that shipped with the previously released version of GPMC will be replaced with new sample scripts included in GPMC with SP1. If you modified any of the sample scripts and you want to preserve those changes, rename your modified sample scripts to a different file name before installing GPMC with SP1.
Friday, June 18, 2004
Determine if you have the Enterprise Edition of Office XP
Only Enterprise Editions of Office XP CD's contain a folder called ORK.
Retail and OEM Windows Installer .MSI packages contain ret. Examples: proret.msi, sberet.msi.
Trial Windows Installer .MSI packages contain tri. Example: protri.msi
Enterprise Windows Installer .MSI packages do not contain ret or tri. Examples: pro.msi, proplus.msi.
Only Enterprise Editions of Office XP CD's contain a folder called ORK.
Retail and OEM Windows Installer .MSI packages contain ret. Examples: proret.msi, sberet.msi.
Trial Windows Installer .MSI packages contain tri. Example: protri.msi
Enterprise Windows Installer .MSI packages do not contain ret or tri. Examples: pro.msi, proplus.msi.
Extracting the OEM 9x Preinstallation Wizard from the CD (TTID #208)
Author: Kevin Views: 4,166 / Last Updated: October 26, 2002
If you have an OEM Windows 98fe, Windows 98se, Windows 95 CD you can extract the Installation Wizard from it.
--------------------------------------------------------------------------------
Open up a MS-DOS Prompt / Command Prompt
Change to your CD-ROM Drive Letter. Example if yout CD-ROM is drive letter is D: type:
D:
Press the key.
--------------------------------------------------------------------------------
Next, you will need to change to the proper directory on the CD. Type:
CD\TOOLS\ADMIN
Press the key.
----------------------------------------------------------------------------
Type in the command to extract the wizard using the following format:
mkcwrt /C:"command.com /C mkcwrt.bat {CD-ROM drive letter} {drive/path}"
Example:
If your CD-ROM drive letter is D: and you would like to extract the wizard to C:\wizard you would us the following command:
mkcwrt /C:"command.com /C mkcwrt.bat D: C:\wizard"
This will launch a second command prompt that extracts the wizard from the CD. It may take several minutes to complete depending on the speed of your CD-ROM.
Author: Kevin Views: 4,166 / Last Updated: October 26, 2002
If you have an OEM Windows 98fe, Windows 98se, Windows 95 CD you can extract the Installation Wizard from it.
--------------------------------------------------------------------------------
Open up a MS-DOS Prompt / Command Prompt
Change to your CD-ROM Drive Letter. Example if yout CD-ROM is drive letter is D: type:
D:
Press the
--------------------------------------------------------------------------------
Next, you will need to change to the proper directory on the CD. Type:
CD\TOOLS\ADMIN
Press the
----------------------------------------------------------------------------
Type in the command to extract the wizard using the following format:
mkcwrt /C:"command.com /C mkcwrt.bat {CD-ROM drive letter} {drive/path}"
Example:
If your CD-ROM drive letter is D: and you would like to extract the wizard to C:\wizard you would us the following command:
mkcwrt /C:"command.com /C mkcwrt.bat D: C:\wizard"
This will launch a second command prompt that extracts the wizard from the CD. It may take several minutes to complete depending on the speed of your CD-ROM.
This list will be updated as additional information becomes available.
If you find any errors or have additional Windows 2003 CD Labels,
Windows 2003 Server Standard Edition (Corporate/VLK | English)
CD Set: -
Windows 2003 Server Standard Edition
NRMSVOL_EN
Windows 2003 Server Enterprise Edition (Corporate/VLK | English)
CD Set: -
Windows 2003 Server Enterprise
NRMEVOL_EN
Windows 2003 Web Server Edition (Corporate/VLK | English)
CD Set: -
Windows 2003 Web Server Edition
NRMWVOL_EN
Windows 2003 Server Standard Edition (English)
CD Set: -
Windows 2003 Server Standard Edition
NRMSFPP_EN
Windows 2003 Server Enterprise Edition (English)
CD Set: -
Windows 2003 Server Enterprise
NRMEFPP_EN
Windows 2003 Web Server Edition (English)
CD Set: -
Windows 2003 Web Server Edition
NRMWFPP_EN
Windows 2003 Server Standard Edition (MSDN Academic Alliance | English)^
CD Set: -
Windows 2003 Server Standard Edition
MSDN Academic Alliance
NRMSFPP_EN
Windows 2003 Server Enterprise Edition Evaluation ISO
CD Set: -
Windows 2003 Server Enterprise Edition Evaluation
NRMEEVL_EN
May 25 2003
CDIMAGE 2.47 (10/12/2000 TM)
Windows 2003 Server Enterprise Edition (Italian)*
CD Set: -
Windows 2003 Server Enterprise Edition (Italian)
NRMEFPP_IT
ISO-9660
MICROSOFT CORPORATION
CDIMAGE 2.47 (10/12/2000 TM)
Data preparer: MICROSOFT CORPORATION, ONE MICROSOFT WAY, REDMOND WA 98052, (425) 882-8080
Boot Catalog at sector 19 Bootable disk
No emulation
load 4 at 0x7c0 from sector 253
Windows Small Business Server 2003 RC
CD Set: -
Windows Small Business Server 2003
RC Disc 1
Trial Software
180-Day Limit on Use
0703 Part No. X09-83616
Data CD Mode 1
ISO9660 (bootable)
NRCFRE1_EN
24 June 2003
MICROSOFT CORPORATION
CDIMAGE 2.47 (10/12/2000 TM)
Windows Small Business Server 2003
RC Disc 2
Trial Software
180-Day Limit on Use
0703 Part No. X09-83617
Data CD Mode 1
ISO9660
NRCFRE2_EN
24 June 2003
MICROSOFT CORPORATION
CDIMAGE 2.47 (10/12/2000 TM)
Windows Small Business Server 2003
RC Disc 3
Trial Software
180-Day Limit on Use
0703 Part No. X09-83618
Data CD Mode 1
ISO9660
NRCFRE3_EN
23 June 2003
MICROSOFT CORPORATION
CDIMAGE 2.47 (10/12/2000 TM)
Windows Small Business Server 2003
OUTLOOK 2003 Interim Build
Trial Software
180-Day Limit on Use
0703 Part No. X09-83619
Data CD Mode 1
ISO9660
OFFICE11
23 June 2003
MICROSOFT CORPORATION
CDIMAGE 2.47 (10/12/2000 TM)
Windows Small Business Server 2003
RC Premium Technologies
Trial Software
180-Day Limit on Use
0703 Part No. X09-83620
Data CD Mode 1
ISO9660
PREMTECH
23 June 2003
MICROSOFT CORPORATION
CDIMAGE 2.47 (10/12/2000 TM)
Windows Small Business Server 2003
Resource CD
Trial Software
180-Day Limit on Use
0703 Part No. X09-83620
Data CD Mode 1
ISO9660, Joilet
sbs03pre
1 July 2003
n/a
Prassi PrimoDVD 2.0 - Build 2.0.837
If you find any errors or have additional Windows 2003 CD Labels,
Windows 2003 Server Standard Edition (Corporate/VLK | English)
CD Set: -
Windows 2003 Server Standard Edition
NRMSVOL_EN
Windows 2003 Server Enterprise Edition (Corporate/VLK | English)
CD Set: -
Windows 2003 Server Enterprise
NRMEVOL_EN
Windows 2003 Web Server Edition (Corporate/VLK | English)
CD Set: -
Windows 2003 Web Server Edition
NRMWVOL_EN
Windows 2003 Server Standard Edition (English)
CD Set: -
Windows 2003 Server Standard Edition
NRMSFPP_EN
Windows 2003 Server Enterprise Edition (English)
CD Set: -
Windows 2003 Server Enterprise
NRMEFPP_EN
Windows 2003 Web Server Edition (English)
CD Set: -
Windows 2003 Web Server Edition
NRMWFPP_EN
Windows 2003 Server Standard Edition (MSDN Academic Alliance | English)^
CD Set: -
Windows 2003 Server Standard Edition
MSDN Academic Alliance
NRMSFPP_EN
Windows 2003 Server Enterprise Edition Evaluation ISO
CD Set: -
Windows 2003 Server Enterprise Edition Evaluation
NRMEEVL_EN
May 25 2003
CDIMAGE 2.47 (10/12/2000 TM)
Windows 2003 Server Enterprise Edition (Italian)*
CD Set: -
Windows 2003 Server Enterprise Edition (Italian)
NRMEFPP_IT
ISO-9660
MICROSOFT CORPORATION
CDIMAGE 2.47 (10/12/2000 TM)
Data preparer: MICROSOFT CORPORATION, ONE MICROSOFT WAY, REDMOND WA 98052, (425) 882-8080
Boot Catalog at sector 19 Bootable disk
No emulation
load 4 at 0x7c0 from sector 253
Windows Small Business Server 2003 RC
CD Set: -
Windows Small Business Server 2003
RC Disc 1
Trial Software
180-Day Limit on Use
0703 Part No. X09-83616
Data CD Mode 1
ISO9660 (bootable)
NRCFRE1_EN
24 June 2003
MICROSOFT CORPORATION
CDIMAGE 2.47 (10/12/2000 TM)
Windows Small Business Server 2003
RC Disc 2
Trial Software
180-Day Limit on Use
0703 Part No. X09-83617
Data CD Mode 1
ISO9660
NRCFRE2_EN
24 June 2003
MICROSOFT CORPORATION
CDIMAGE 2.47 (10/12/2000 TM)
Windows Small Business Server 2003
RC Disc 3
Trial Software
180-Day Limit on Use
0703 Part No. X09-83618
Data CD Mode 1
ISO9660
NRCFRE3_EN
23 June 2003
MICROSOFT CORPORATION
CDIMAGE 2.47 (10/12/2000 TM)
Windows Small Business Server 2003
OUTLOOK 2003 Interim Build
Trial Software
180-Day Limit on Use
0703 Part No. X09-83619
Data CD Mode 1
ISO9660
OFFICE11
23 June 2003
MICROSOFT CORPORATION
CDIMAGE 2.47 (10/12/2000 TM)
Windows Small Business Server 2003
RC Premium Technologies
Trial Software
180-Day Limit on Use
0703 Part No. X09-83620
Data CD Mode 1
ISO9660
PREMTECH
23 June 2003
MICROSOFT CORPORATION
CDIMAGE 2.47 (10/12/2000 TM)
Windows Small Business Server 2003
Resource CD
Trial Software
180-Day Limit on Use
0703 Part No. X09-83620
Data CD Mode 1
ISO9660, Joilet
sbs03pre
1 July 2003
n/a
Prassi PrimoDVD 2.0 - Build 2.0.837
Wednesday, June 16, 2004
Spymac World :: News
1 GB e-mail account, 350 MB combined storage, personal blog, forum, gallery, auctions and more
1 GB e-mail account, 350 MB combined storage, personal blog, forum, gallery, auctions and more
Bypassing the Windows 2000 Serial Check
First you want to copy your Windows 2000 setup files from your CD to your hard drive. You have to copy at least the I386 directory (I recommend copying all the files, so you can burn a complete CD later). Now go into the I386 directory you just copied onto your hard drive. Find the setupp.ini file. Right click it, select Properties, and remove the Read-only checkmark. Now open the file to edit it.
Your setupp.ini file should read something like this:
[Pid]
ExtraData=6166656C736263737373B2574A0581
Pid=51873XXX
Replace the 3 X's (generally it'll be three zeros) at the end with "270". It should now read something like this:
[Pid]
ExtraData=6166656C736263737373B2574A0581
Pid=51873270
That’s it! Now you can now install Windows 2000 without a serial number!
Note: After many emails, it's safe to say this works with all versions of Win2k; Professional, Server, and Advanced Server. If it's not working for you, email me letting me know exactly what you're trying this on. I won't be able to help you (there's only so many ways to replace 000 with 270), but I can let others know if a certain CD (ie Win2k Pro OEM) will not work. Also, this will NOT work on evaluation versions of Win2k. So don't waste your time.
First you want to copy your Windows 2000 setup files from your CD to your hard drive. You have to copy at least the I386 directory (I recommend copying all the files, so you can burn a complete CD later). Now go into the I386 directory you just copied onto your hard drive. Find the setupp.ini file. Right click it, select Properties, and remove the Read-only checkmark. Now open the file to edit it.
Your setupp.ini file should read something like this:
[Pid]
ExtraData=6166656C736263737373B2574A0581
Pid=51873XXX
Replace the 3 X's (generally it'll be three zeros) at the end with "270". It should now read something like this:
[Pid]
ExtraData=6166656C736263737373B2574A0581
Pid=51873270
That’s it! Now you can now install Windows 2000 without a serial number!
Note: After many emails, it's safe to say this works with all versions of Win2k; Professional, Server, and Advanced Server. If it's not working for you, email me letting me know exactly what you're trying this on. I won't be able to help you (there's only so many ways to replace 000 with 270), but I can let others know if a certain CD (ie Win2k Pro OEM) will not work. Also, this will NOT work on evaluation versions of Win2k. So don't waste your time.
Unlocking WinXP's setupp.ini
WinXP's setupp.ini controls how the CD acts. IE is it an OEM version or retail? First, find your setupp.ini file in the i386 directory on your WinXP CD. Open it up, it'll look something like this:
ExtraData=707A667567736F696F697911AE7E05
Pid=55034000
The Pid value is what we're interested in. What's there now looks like a standard default. There are special numbers that determine if it's a retail, oem, or volume license edition. First, we break down that number into two parts. The first five digits determines how the CD will behave, ie is it a retail cd that lets you clean install or upgrade, or an oem cd that only lets you perform a clean install? The last three digits determines what CD key it will accept. You are able to mix and match these values. For example you could make a WinXP cd that acted like a retail cd, yet accepted OEM keys.
Now, for the actual values. Remember the first and last values are interchangable, but usually you'd keep them as a pair:
Retail = 51882 335
Volume License = 51883 270
OEM = 82503 OEM
So if you wanted a retail CD that took retail keys, the last line of your setupp.ini file would read:
Pid=51882335
And if you wanted a retail CD that took OEM keys, you'd use:
Pid=51882OEM
Note that this does NOT get rid of WinXP's activation. Changing the Pid to a Volume License will not bypass activation. You must have a volume license (corporate) key to do so.
For screenshots of the Retail, OEM, and Volume License installs, click here.
http://www.thetechguide.com/misc/winxp.html
WinXP's setupp.ini controls how the CD acts. IE is it an OEM version or retail? First, find your setupp.ini file in the i386 directory on your WinXP CD. Open it up, it'll look something like this:
ExtraData=707A667567736F696F697911AE7E05
Pid=55034000
The Pid value is what we're interested in. What's there now looks like a standard default. There are special numbers that determine if it's a retail, oem, or volume license edition. First, we break down that number into two parts. The first five digits determines how the CD will behave, ie is it a retail cd that lets you clean install or upgrade, or an oem cd that only lets you perform a clean install? The last three digits determines what CD key it will accept. You are able to mix and match these values. For example you could make a WinXP cd that acted like a retail cd, yet accepted OEM keys.
Now, for the actual values. Remember the first and last values are interchangable, but usually you'd keep them as a pair:
Retail = 51882 335
Volume License = 51883 270
OEM = 82503 OEM
So if you wanted a retail CD that took retail keys, the last line of your setupp.ini file would read:
Pid=51882335
And if you wanted a retail CD that took OEM keys, you'd use:
Pid=51882OEM
Note that this does NOT get rid of WinXP's activation. Changing the Pid to a Volume License will not bypass activation. You must have a volume license (corporate) key to do so.
For screenshots of the Retail, OEM, and Volume License installs, click here.
http://www.thetechguide.com/misc/winxp.html
Tuesday, June 15, 2004
File Sizes and CRC Values of Builds,
Look here to verify your ISO download.
[Last Updated on April 28, 2004]
This information is provided to help you verify that your download of an ISO file for a Longhorn build is not corrupt.
Build 3683 (Betas original):
- File Size = 529 MB (555,421,696 bytes)
- CRC Value = 0x691DCE9B {Variation #1}
^ According to Betaguy9000. Thanks.
- CRC Value = 0xDA96240B {Variation #2}
^ According to horvath and confirmed by me. Thanks.
Build 3683 (with Werejag's bootable CD fix):
- File Size = 573 MB (600,844,288 bytes)
- CRC Value = 0x8035F855
Build 3718 (iNFLUENCE original):
- File Size = 511 MB (535,867,392 bytes)
- CRC Value = 0xCADF1F2A
^ According to EmoAddict15 and confirmed by me. Thanks.
Build 4008 (WinBeta original):
- File Size = 655 MB (687,116,288 bytes)
- CRC Value = 0xB3EF7A4C
Build 4015 (WinBeta original):
- File Size = 668 MB (700,616,704 bytes)
- CRC Value = 0xD41D6A48
Build 4015 (with Winbeta's bootable CD fix):
- File Size = 665 MB (698,259,456 bytes)
- CRC Value = 0xC9EF215F
^ However, ReflectiaX's fix is ten times better and it completely works. :-p
Build 4015 (with ReflectiaX's bootable CD fix):
- File Size = 665 MB (698,214,400 bytes)
- CRC Value = 0x8F6E9A57
Build 4029 (original):
- File Size = 687 MB (721,195,008 bytes)
- CRC Value = 0xF8C419C6
^ According to JoePacton and confirmed by me. Thanks.
Build 4051 (MSDN/PDC original):
- File Size = 694 MB (710,994 KB)
- CRC Value = 0xC9E08BF9
^ According to candyman123.
Build 4051 (WinBeta original):
Size = 659 MB (691,961,856 bytes)
CRC = 0x95220E35
^ According to Quantum Topology and confirmed by me. Thanks.
Build 4051 (with XBeta's fix pack):
- File Size = 660.10 MB (692,168,704 Bytes)
- CRC Value = 0xACDD8847
^ According to Jay16K. Thanks.
Build 4051 (with Betas' fix pack):
- File Size = 659 MB (691,853,312 bytes)
- CRC Value = 0xA51781C0
Build 4051 (with ReflectiaX's fix pack):
- File Size = 659 MB (691,867,648 bytes)
- CRC Value = 0xDF346283
^ According to Betaguy9000 and confirmed by me. Thanks.
Build 4051 (as mstest's "Lite Edition" with i386 folders):
- File Size: 585 MB (613,822,464 bytes)
- CRC Value: 0x900C5F9B
^ According to slammy_dunken. Thanks.
Build 4053 (BetasIRC original):
- File Size = 676 MB (708,933,632 bytes)
- CRC Value = 0xBB1F1B3F
^ According to candyman123. Thanks.
Build 4053 (WinBeta Proper version):
- File Size = 676 MB (708,943,872 bytes)
- CRC Value = 0xBD9DEF90
^ According to slammy_dunken. Thanks.
Build 4053 (with Flexbeta's bootable CD fix):
- File Size = n/a
- CRC Value = n/a
Build 4074 (MSDN/WinHEC original):
- File Size = n/a
- CRC Value = n/a
Build 4074 (with Betas original):
- File Size = 733 MB (769,388,544 bytes)
- CRC Value = 0xF0464B61
Build 4074 (with ReflectiaX's fix pack):
- File Size = 732 MB (768,567,296 bytes)
- CRC Value = 0x7144695C
NOTE: Unless otherwise stated, the CRC values for all of the "fixed" builds are based on ISO files that were re-generated using the ISO9660 file system and NOT the Joliet file system!
Of course, as more builds come out in the future, I'll go back and update this page accordingly.
These CRC (Cyclic Redundancy Check) values were generated using Microsoft's CRC Verification Utility v3.00 which can be downloaded from here. If someone else wishes to mirror the download, then be my guest.
To generate your value, place a copy of the previously mentioned EXE beside the ISO, open a Command Prompt, change to that location (i.e. cd downloads), and run the utility providing it the name of the file (i.e. crc). Afterwards it will report the resulting CRC value which you can then compare to the ones above. It will also tell you if your download is outright corrupt.
Hope it helps and here's to the future of Longhorn!
Look here to verify your ISO download.
[Last Updated on April 28, 2004]
This information is provided to help you verify that your download of an ISO file for a Longhorn build is not corrupt.
Build 3683 (Betas original):
- File Size = 529 MB (555,421,696 bytes)
- CRC Value = 0x691DCE9B {Variation #1}
^ According to Betaguy9000. Thanks.
- CRC Value = 0xDA96240B {Variation #2}
^ According to horvath and confirmed by me. Thanks.
Build 3683 (with Werejag's bootable CD fix):
- File Size = 573 MB (600,844,288 bytes)
- CRC Value = 0x8035F855
Build 3718 (iNFLUENCE original):
- File Size = 511 MB (535,867,392 bytes)
- CRC Value = 0xCADF1F2A
^ According to EmoAddict15 and confirmed by me. Thanks.
Build 4008 (WinBeta original):
- File Size = 655 MB (687,116,288 bytes)
- CRC Value = 0xB3EF7A4C
Build 4015 (WinBeta original):
- File Size = 668 MB (700,616,704 bytes)
- CRC Value = 0xD41D6A48
Build 4015 (with Winbeta's bootable CD fix):
- File Size = 665 MB (698,259,456 bytes)
- CRC Value = 0xC9EF215F
^ However, ReflectiaX's fix is ten times better and it completely works. :-p
Build 4015 (with ReflectiaX's bootable CD fix):
- File Size = 665 MB (698,214,400 bytes)
- CRC Value = 0x8F6E9A57
Build 4029 (original):
- File Size = 687 MB (721,195,008 bytes)
- CRC Value = 0xF8C419C6
^ According to JoePacton and confirmed by me. Thanks.
Build 4051 (MSDN/PDC original):
- File Size = 694 MB (710,994 KB)
- CRC Value = 0xC9E08BF9
^ According to candyman123.
Build 4051 (WinBeta original):
Size = 659 MB (691,961,856 bytes)
CRC = 0x95220E35
^ According to Quantum Topology and confirmed by me. Thanks.
Build 4051 (with XBeta's fix pack):
- File Size = 660.10 MB (692,168,704 Bytes)
- CRC Value = 0xACDD8847
^ According to Jay16K. Thanks.
Build 4051 (with Betas' fix pack):
- File Size = 659 MB (691,853,312 bytes)
- CRC Value = 0xA51781C0
Build 4051 (with ReflectiaX's fix pack):
- File Size = 659 MB (691,867,648 bytes)
- CRC Value = 0xDF346283
^ According to Betaguy9000 and confirmed by me. Thanks.
Build 4051 (as mstest's "Lite Edition" with i386 folders):
- File Size: 585 MB (613,822,464 bytes)
- CRC Value: 0x900C5F9B
^ According to slammy_dunken. Thanks.
Build 4053 (BetasIRC original):
- File Size = 676 MB (708,933,632 bytes)
- CRC Value = 0xBB1F1B3F
^ According to candyman123. Thanks.
Build 4053 (WinBeta Proper version):
- File Size = 676 MB (708,943,872 bytes)
- CRC Value = 0xBD9DEF90
^ According to slammy_dunken. Thanks.
Build 4053 (with Flexbeta's bootable CD fix):
- File Size = n/a
- CRC Value = n/a
Build 4074 (MSDN/WinHEC original):
- File Size = n/a
- CRC Value = n/a
Build 4074 (with Betas original):
- File Size = 733 MB (769,388,544 bytes)
- CRC Value = 0xF0464B61
Build 4074 (with ReflectiaX's fix pack):
- File Size = 732 MB (768,567,296 bytes)
- CRC Value = 0x7144695C
NOTE: Unless otherwise stated, the CRC values for all of the "fixed" builds are based on ISO files that were re-generated using the ISO9660 file system and NOT the Joliet file system!
Of course, as more builds come out in the future, I'll go back and update this page accordingly.
These CRC (Cyclic Redundancy Check) values were generated using Microsoft's CRC Verification Utility v3.00 which can be downloaded from here. If someone else wishes to mirror the download, then be my guest.
To generate your value, place a copy of the previously mentioned EXE beside the ISO, open a Command Prompt, change to that location (i.e. cd downloads), and run the utility providing it the name of the file (i.e. crc
Hope it helps and here's to the future of Longhorn!
Subscribe to:
Posts (Atom)