History of Microsoft Windows and MS-DOS
Author: TACKtech Corp.
1975
11/29/1975 "Micro-soft" name used by Bill Gates in a letter to Paul Allen.
11/26/1976 The tradename "Microsoft" is registered.
08/25/1980 Microsoft XENIX OS was announced. XENIX was an enhanced version id the UNIX operating system.
--/--/1981 Microsoft began work on Windows (originally termed the Interface Manager)
08/12/1981 MS-DOS 1.0 shipped with the new IBM Personal Computer
03/--/1983 MS-DOS 2.0 shipped
11/10/1983 Microsoft Windows was announced
11/--/1984 MS-DOS 3.1 is available
11/20/1985 Microsoft Windows 1.0 released
(It was pathetic compared to Apple's Macintosh. It's interface the looked similar to DOS Shell. It contained a few Windows Applications which were able to be cooperatively multitasked.)
04/--/1986 MS-DOS 3.2 ships
1987
04/02/1987 Microsoft Operating System/2 (MS OS/2) announced, as part of a joint agreement between Microsoft and IBM.
04/02/1987 MS-DOS 3.3 announced.
04/02/1987 Microsoft Windows 2.0 announced.
04/02/1987 Microsoft Windows/386 announced.
It was designed to take advantage of the Intel 80386.
Fall/--/1987 Microsoft Windows 2.0 was introduced.
This new version added overlapping windows. PIF files (These told Windows how a DOS application should be run) were added to Windows 2.0.
Late/--/1987 Microsoft Windows/386 released.
Multiple DOS virtual machines was added which allowed the running of multiple DOS applications at the same time in extended memory.
Late/--/1987 Microsoft renamed Windows 2.1 to Win/286.
1988 http://www.tacktech.com
06/28/1988 Microsoft Windows/286 and Windows/386 versions 2.1 announced
07/--/1988 MS-DOS 4.0 released
10/31/1988 David Cutler, formerly of Digital and now working for Microsoft, begins work on Windows NT.
11/--/1988 MS-DOS 4.01 shipped to correct 4.0 problems
1990 http://www.tacktech.com
04/09/1990 Microsoft MS-DOS 4.01 (Russian Version) introduced
05/22/1990 Microsoft releases Windows 3.0. First version of Windows to allow use of memory beyond 640Kb, up to 16MB of RAM with 386 enhanced mode, support for color palettes with more than 16 colors, hierarchical menus, "Program Manager" and "File Manager", private INI files, network support, and API support for combo boxes.
(Over 10 million copies of Microsoft Windows were sold.)
1991 http://www.tacktech.com
10/--/1991 Windows NT is displayed publicly at a demo at COMDEX.
10/20/1991 Microsoft Windows 3.0 with Multimedia Extensions released
06/--/1991 MS-DOS 5.0 shipped. This was the first version of MS-DOS that featured a retail upgrade.
1992 http://www.tacktech.com
04/06/1992 Microsoft Windows 3.1 was released.
TrueType scalable fonts support, Object Linking and Embedding (OLE), mouse trails, and API multimedia and networking support were added.
10/11/1992 Microsoft Windows NT beta program shipped
10/27/1992 Microsoft Windows for Workgroups 3.1 released. It added easier, integrated networking.
1993 http://www.tacktech.com
03/--/1993 Microsoft Windows NT 3.1 Beta
03/30/1993 MS-DOS 6.0 upgrade shipped.
This version included DoubleSpace
05/24/1993 Microsoft Window NT formally launched. It was scheduled for release in 60 days.
06/--/1993 Microsoft begins the development of the successor to Windows 3.x which will later be title Windows 95 (code-named Chicago")
08/--/1993 Microsoft Windows NT 3.1 released after five years in development. It consists of over 6 million lines of code.
11/--/1993 MS-DOS 6.2 released.
11/08/1993 Microsoft Windows for Workgroups 3.11 was shipped.
This version corrected some network-related problems.
1994 http://www.tacktech.com
03/02/1994 MS-DOS 6.21 ships with drive compression removed due to a law suit.
04/11/1994 MS-DOS 6.22 ships with new DriveSpace drive compression.
Q1/--/1994 Microsoft is planing to release a new version Windows the second half of 1994.
09/06/1994 Microsoft Windows NT 3.5 (code-named Daytona") released. It consists of over 9 million lines of code.
09/08/1994 Microsoft Windows 95 becomes the official name of the new version of Windows code-named "Chicago".
1995 http://www.tacktech.com
06/--/1995 Microsoft Windows NT 3.51 released. Minor release is to support upcoming Windows 95 programs.
08/24/1995 Microsoft Windows 95 released. It include MS-DOS 7.0 v4.00.950
The upgrade consisted of 17cabs. The full version had 28 cabs.
12/--/1995 Microsoft Windows code-named "Nashville" v4.10.999
This was often referred to as Windows 96. It was never release. Windows 98 later included it's features.
1996 http://www.tacktech.com
08/24/1996 Microsoft Windows NT 4.0 released. It consists of over 16 million lines of code.
09/--/1996 Microsoft Windows 95 SR2 released v4.00.950B or v4.00.1111
Microsoft Windows 95 is scheduled for a major overhaul in 1997, code-named Memphis (Windows 98 1st ED).
11/--/1996 Microsoft Windows CE 1.0 released, supporting handheld-PCs
12/--/1996 Microsoft Windows 95 SR2.1
1MB supplement for SR2 named usbsupp.exe. Partial USB support includes host controller and hub drivers, and the HID and Imaging classes. AGP support. Recommended for SR2 users wanting USB.
12/--/1996 Microsoft Windows 95 code-named Detroit (SR3) v4.10.1525.3
This development line attempted to give Windows 95 integrated Internet components. It buggy and unstable. The planned release was Dec. 1996. Microsoft scraped it.
1997 http://www.tacktech.com
07/--/1997 Microsoft Windows 98 (Beta 1), code-named "Memphis" released. v4.10.1525.3 (Also, referred to as Windows 9x and Windows 97) Consisted of 47 cabs with IE4 build 4.71.0913.5. NT kernel and speedier registry handling. Curiously, the version# lines up with W96 (4.10.999). Included Winsock2, multiple display support, a DVD player, DirectX5, USB support, Memphis specific Tweak UI additions, System Optimizer, System Troubleshooter and TV listings software (MS CDF).
09/27/1997 Microsoft Windows NT 5.0 (Beta 1) released. Later known as Windows 2000
11/--/1997 Microsoft Windows CE 2.0 released
12/--/1997 Microsoft Windows SR2.5 v4.00.950C
OEM only release. Mostly identical to SR2, but adds SR2.1 USB/AGP update along with IE4 and DirectX 5. Contained the second USB supplement.
12/--/1997 Microsoft Windows NT 4.0 Option Pack released
1998 http://www.tacktech.com
06/25/1998 Microsoft Windows 98 released. v4.10.1998.6
Consisted of 69 cabs with IE4 version 4.72.3110. Features: Some NT kernel and speedier registry handling, FAT32.
07/--/1998 Microsoft Windows CE 2.1 released, supporting palm-sized PCs
08/20/1998 Microsoft Windows NT 5.0 (Beta 2) released (code-named "Cairo)
10/27/1998 Microsoft announces that Windows NT 5.0 will be renamed "Windows 2000"
12/16/1998 Microsoft Windows 2000 (RC0) release
1999 http://www.tacktech.com
01/--/1999 Microsoft Windows 98 SP1 (Beta 1) v4.10.2120
Contains Internet Explorer 5 & DX6.1 Delay of beta 2 caused by bugs in IE5 and a memory leak. Microsoft discontinued SP1 in favor a smaller 41MB patch. Microsoft thought it too big for downloading. Microsoft may release an upgrade CD (SP1) which it would sell for a nominal price from it's Webster.
04/29/1999 Microsoft Windows 2000 (Beta 3) released v5.00.2031
05/05/1999 Microsoft Windows 98 SE (second edition) released v4.10.2222.
Contained bug fixes, security fixes, Internet Explorer 5 & DirectX6.1 Also, new functionality and hardware capabilities were added.
07/02/1999 Microsoft Windows 2000 (RC1) released
07/23/1999 Microsoft Windows Millennium Developer Preview 1 released
07/26/1999 Microsoft Windows Millennium Offically Announced
08/--/1999 Microsoft Windows 98 SE update CD available. This CD will upgrade your Windows 98 4.10.1998 to Second Edition. You can order it from Microsoft. (The Windows 98 Customer Service Pack CD just fixes bugs and Y2K issues, )
08/25/1999 Microsoft and Compaq discontinue all Windows NT/2000 development for the Alpha processor
09/15/1999 Microsoft Windows 2000 (RC2) released build 2128
09/23/1999 Microsoft Windows Millennium (Beta 1) - build 4.90.2380.2
Windows Millennium Beta 1 - TechNet Dec. 1999
Build 4.90.2380
IE 5.50.3723.1301 56-bit cipher
OE 5.00.2919.5600
Explorer 5.50.3723.1301
Media Player: 7.00.00.0093
File Dates 09/20/1999 10:00AM
CD Label: WinMil B1
Files on CD Date: 09/22/1999 12:20PM
11/11/1999 Microsoft Windows 2000 (RC3) released v5.00.2183
11/23/1999 Microsoft Windows Millennium (Beta 2) - build 4.90.2419.5
Windows Millennium Beta 2 - TechNet Jan. 2000
Build 4.90.2419
IE 5.50.3825.1300 56-bit cipher
OE 5.50.3825.400
Explorer 5.50.3825.1300
Meda Player: 6.4.07.1028
File Dates 11/17/1999 05:00PM
CD Label: WinMil Beta
Files on CD Date: 11/17/1999 05:00PM
Folder on CD Dates: 11/17/1999 05:00PM
Included CD Sampler
12/15/1999 Microsoft Windows 2000 RTM released (i.e., coding completed)
12/--/1999 Microsoft Windows Whistler build 5.01.xxxx (Later Windows.NET)
Microsoft had three Windows consumer version development lines running. Windows Neptune was the codename for the operating system to follow Windows ME. Windows Odyssey was yet another OS that would follow Windows Neptune. Both have since been cancelled in favor of Whistler which will the first consumer version of the NT code.
2000 http://www.tacktech.com
01/19/2000 Microsoft Windows 2000 MSDN released
01/20/2000 Microsoft Windows Millennium (Beta 2 refresh) - build 2452
02/10/2000? Microsoft Windows Whistler build 5.01.2200
02/17/2000 Microsoft Windows 2000 Professional, Server, and Advanced Server released. v5.00.2195
02/18/2000 Microsoft Windows Millennium - build 2470
02/25/2000 Microsoft Windows Millennium - build 2476
03/--/2000 Microsoft Blackcomb is now being developed which will be the follow up to Whistler .
03/03/2000 Microsoft Windows Millennium - build 2481
03/10/2000 Microsoft Windows Millennium - build 2487
03/17/2000 Microsoft Windows Millennium - build 2491
03/27/2000 Microsoft Windows Millennium - build 2499
03/20/2000? Microsoft Windows Whistler build 5.01.2211.1 leaked on the Web
03/30/2000 Microsoft Windows Millennium - build 2499.3
04/07/2000 Microsoft Windows Millennium (Beta 3) - build 2499.7 completed
04/11/2000 Microsoft Windows Millennium (Beta 3) - build 2499.7 released
Windows Millennium Beta 3 - TechNet Jun. 2000
Build 4.90.2499
IE 5.50.4030.2400 128-bit cipher
OE 5.50.4029.2901
Explorer 5.50.4030.2400
Meda Player: 7.00.00.1153
File Dates 04/04/2000 05:00PM
CD Label: WinMEB3
Files on CD Date: 04/04/2000 10:00AM
Folder on CD Dates: 05/11/2000 3:47PM 3:47PM 3:34PM 3:40PM 3:41PM 4:11PM
Included CD Sampler
04/18/2000 Microsoft Windows Millennium - build 2509
04/21/2000 Microsoft Windows Millennium - build 2513
04/25/2000 Microsoft showcased 'Whistler' at the Windows Hardware Engineering Conference (WinHEC)
04/26/2000? Microsoft Windows Whistler build 5.01.2XXX leaked on the Web
04/28/2000 Microsoft Windows Millennium - build 2516
05/09/2000 Microsoft Windows Millennium Edition (RC0) - build 2525
05/17/2000 Microsoft Windows Millennium Edition (RC1) - build 2525.6
06/06/2000? Microsoft Windows Millennium Edition (RC2) - build 2535
06/18/2000? Microsoft Windows Millennium Edition when gold (v4.90.3000.2)
Internet Explorer 5.5 is included. New Icons and color scheme like those found in Windows 2000.
Microsoft Windows Whistler Build 2223.1
07/11/2000 Microsoft Windows Whistler Build 2250
07/31/2000 Microsoft Windows 2000 SP1 released
08/31/2000 Microsoft Windows 2001, code-named "Whistler" invites sent to previous beta testers. It is rumored the build 2257 of the Personal and Professional releases are bugged so they will sent the internal, Washington. This feature is currently not included in the Server and Advanced Server versions.
09/14/2000 Microsoft Windows ME to be offically released
10/01/2000 Microsoft Whistler Beta1
12/06/2000 Microsoft Whistler Beta2
2001 http://www.tacktech.com
02/14/2001 Microsoft Whistler RC1
03/21/2001 Microsoft Whistler RC2
04/18/2001 Microsoft Whistler Final Build
2003 http://www.tacktech.com
03/28/2003 Microsoft Releases Windows XP 64-Bit Edition Version 2003 to Manufacturing
Friday, February 11, 2005
DVD File/Folder Structure
Explanation:
. BUP = Backup files of the IFO files.
. IFO = The IFO files includes information such as chapters, subtitle tracks and audio tracks.
. VOB = The VOB files contains the actual video,audio,subtitles and menus.
Folder Files Explanation
AUDIO_TS (undefined) DVD Audio
VIDEO_TS VIDEO_TS.BUP
VIDEO_TS.IFO The first video play item, IFO, usally a copyright notice or a menu
VIDEO_TS.VOB The first video play item, VOB
VTS_01_0.BUP
VTS_01_0.IFO Title 01, IFO, usually the main movie
VTS_01_0.VOB Title 01, VOB 0, the menu for this title
VTS_01_1.VOB Title 01, VOB 1, the video for this title
VTS_01_2.VOB Title 01, VOB 2, if larger than 1 GB it will be splitted into several vobs
VTS_01_3.VOB Title 01, VOB 3
VTS_01_4.VOB Title 01, VOB 4, up to 10(0-9) VOB files if necassary
VTS_02_0.BUP
VTS_02_0.IFO Title 02, IFO, usually movie extras
VTS_02_0.VOB Title 02, VOB 0, the menu for this title
VTS_02_1.VOB Title 02, VOB 1, the video for this title
VTS_xx_x.BUP
VTS_xx_x.IFO And so on
VTS_xx_x.VOB
VTS_xx_x.VOB
VTS_99_9.VOB Up to 99(1-99) titles with max 10(0-9) VOB files each
Explanation:
. BUP = Backup files of the IFO files.
. IFO = The IFO files includes information such as chapters, subtitle tracks and audio tracks.
. VOB = The VOB files contains the actual video,audio,subtitles and menus.
Folder Files Explanation
AUDIO_TS (undefined) DVD Audio
VIDEO_TS VIDEO_TS.BUP
VIDEO_TS.IFO The first video play item, IFO, usally a copyright notice or a menu
VIDEO_TS.VOB The first video play item, VOB
VTS_01_0.BUP
VTS_01_0.IFO Title 01, IFO, usually the main movie
VTS_01_0.VOB Title 01, VOB 0, the menu for this title
VTS_01_1.VOB Title 01, VOB 1, the video for this title
VTS_01_2.VOB Title 01, VOB 2, if larger than 1 GB it will be splitted into several vobs
VTS_01_3.VOB Title 01, VOB 3
VTS_01_4.VOB Title 01, VOB 4, up to 10(0-9) VOB files if necassary
VTS_02_0.BUP
VTS_02_0.IFO Title 02, IFO, usually movie extras
VTS_02_0.VOB Title 02, VOB 0, the menu for this title
VTS_02_1.VOB Title 02, VOB 1, the video for this title
VTS_xx_x.BUP
VTS_xx_x.IFO And so on
VTS_xx_x.VOB
VTS_xx_x.VOB
VTS_99_9.VOB Up to 99(1-99) titles with max 10(0-9) VOB files each
Non-standard special DVD formats:
DVD-VCD
is basicly a VCD authored on a DVD. DVD supports the VCD resolution but the audio has to be resampled to 48 khz. If the audio is resampled to 48 khz it is standard DVD-Video. Read more here how to make a such.
DVD-SVCD
is basicly a SVCD authored on a DVD. DVD do not supports the SVCD resolution but it may anyway work and the audio has to be resampled to 48 khz like the DVD-VCD. Read more here how to make a such and download a DVD Sample including a DVD-SVCD here.
DVD-MP3
is MP3s burned on a DVD but very few MP3 capable standalone DVD Players supports it because most Players verify DVD as DVD-Video only. Check our DVD Players list for compatibility.
DVD-ISO
is MPEG ,MPG, VOB files burned on a DVD without any DVD Authoring(making the vob,ifo files) but very few standalone DVD Players supports it because most Players verify DVD as DVD-Video only. Check our DVD Players list for compatibility.
DVD-VCD
is basicly a VCD authored on a DVD. DVD supports the VCD resolution but the audio has to be resampled to 48 khz. If the audio is resampled to 48 khz it is standard DVD-Video. Read more here how to make a such.
DVD-SVCD
is basicly a SVCD authored on a DVD. DVD do not supports the SVCD resolution but it may anyway work and the audio has to be resampled to 48 khz like the DVD-VCD. Read more here how to make a such and download a DVD Sample including a DVD-SVCD here.
DVD-MP3
is MP3s burned on a DVD but very few MP3 capable standalone DVD Players supports it because most Players verify DVD as DVD-Video only. Check our DVD Players list for compatibility.
DVD-ISO
is MPEG ,MPG, VOB files burned on a DVD without any DVD Authoring(making the vob,ifo files) but very few standalone DVD Players supports it because most Players verify DVD as DVD-Video only. Check our DVD Players list for compatibility.
DVD Write and read speeds
Single Layer(4.7GB) write speeds
1x (CLV) = about 58 minutes
2x (CLV) = about 29 minutes
2.4x (CLV) = about 24 minutes
4x (CLV) = about 14.5 minutes
6x (CLV/ZCLV) = about 10-12 minutes
8x (PCAV/ZCLV) = about 8-10 minutes
12x (PCAV/ZCLV) = about 6.5-7.5 minutes
16x (CAV/ZCLV) = about 6-7 minutes
Dual/Double Layer(8.5GB) write speeds
1x CLV = about 105 minutes
2.4x CLV = about 44 minutes
4x CLV = about 27 minutes
Single Layer (4.7GB) read speeds
6x CAV (avg. ~4x) read speed is max 7.93MB/s = ~14 minutes
8x CAV (avg. ~6x) read speed is max 10.57MB/s = ~10 minutes
12x CAV (avg. ~8x) read speed is max 15.85MB/s = ~7 minutes
16x CAV (avg. ~12x) read speed is max 21.13MB/s = ~5 minutes
* write speed time and read speed time is not the same because writing requires some extra steps and also does the faster writing above 6x usually use lower write speeds for some parts of the dvd. 4x DVD speed = 36x CD speed. See section 4.2 in the DVDDemystified FAQ here.
Single Layer(4.7GB) write speeds
1x (CLV) = about 58 minutes
2x (CLV) = about 29 minutes
2.4x (CLV) = about 24 minutes
4x (CLV) = about 14.5 minutes
6x (CLV/ZCLV) = about 10-12 minutes
8x (PCAV/ZCLV) = about 8-10 minutes
12x (PCAV/ZCLV) = about 6.5-7.5 minutes
16x (CAV/ZCLV) = about 6-7 minutes
Dual/Double Layer(8.5GB) write speeds
1x CLV = about 105 minutes
2.4x CLV = about 44 minutes
4x CLV = about 27 minutes
Single Layer (4.7GB) read speeds
6x CAV (avg. ~4x) read speed is max 7.93MB/s = ~14 minutes
8x CAV (avg. ~6x) read speed is max 10.57MB/s = ~10 minutes
12x CAV (avg. ~8x) read speed is max 15.85MB/s = ~7 minutes
16x CAV (avg. ~12x) read speed is max 21.13MB/s = ~5 minutes
* write speed time and read speed time is not the same because writing requires some extra steps and also does the faster writing above 6x usually use lower write speeds for some parts of the dvd. 4x DVD speed = 36x CD speed. See section 4.2 in the DVDDemystified FAQ here.
DVD Sizes
The DVD sizes can be a bit confusing. There are basicly 4 different DVD Sizes,
DVD-5, holds around 4 700 000 000 bytes and that is 4.37 computer GB where 1 kbyte is 1024 bytes* . DVD+R/DVD+RW and DVD-R/DVD-RW supports this format. Also called Single Sided Single Layered. This is the most common DVD Media, often called 4.7 GB Media.
DVD-10, holds around 9 400 000 000 bytes and that is 8.75 computer GB. DVD+R/DVD+RW and DVD-R/DVD-RW supports this format. Also called Double Sided Single Layered.
DVD-9, holds around 8 540 000 000 bytes and that is 7.95 computer GB. DVD+R supports this format. Also called Single Sided Dual Layered. This media is called DVD+R9, DVD+R DL or 8.5 GB Media.
DVD-18, holds around 17 080 000 000 bytes and that is 15.9 computer GB. DVD+R supports this format. Also called Double Sided Dual Layered.
* In the computer world is 1 KB data = 1024 bytes so 4 700 000 000 bytes / 1024 = 4 589 843KB / 1024 = 4482MB / 1024 = 4.37GB. See section 3.3 in the DVDDemystified FAQ here.
DVD+R/DVD+RW/DVD+R DL and DVD-R/DVD-RW exact sizes
DVD-R/DVD-RW = 4 706 074 624 bytes ( 4488 MB )
DVD+R/DVD+RW = 4 700 372 992 bytes ( 4482 MB )
DVD+R DL = 8 547 993 600 bytes ( 8152 MB )
The DVD sizes can be a bit confusing. There are basicly 4 different DVD Sizes,
DVD-5, holds around 4 700 000 000 bytes and that is 4.37 computer GB where 1 kbyte is 1024 bytes* . DVD+R/DVD+RW and DVD-R/DVD-RW supports this format. Also called Single Sided Single Layered. This is the most common DVD Media, often called 4.7 GB Media.
DVD-10, holds around 9 400 000 000 bytes and that is 8.75 computer GB. DVD+R/DVD+RW and DVD-R/DVD-RW supports this format. Also called Double Sided Single Layered.
DVD-9, holds around 8 540 000 000 bytes and that is 7.95 computer GB. DVD+R supports this format. Also called Single Sided Dual Layered. This media is called DVD+R9, DVD+R DL or 8.5 GB Media.
DVD-18, holds around 17 080 000 000 bytes and that is 15.9 computer GB. DVD+R supports this format. Also called Double Sided Dual Layered.
* In the computer world is 1 KB data = 1024 bytes so 4 700 000 000 bytes / 1024 = 4 589 843KB / 1024 = 4482MB / 1024 = 4.37GB. See section 3.3 in the DVDDemystified FAQ here.
DVD+R/DVD+RW/DVD+R DL and DVD-R/DVD-RW exact sizes
DVD-R/DVD-RW = 4 706 074 624 bytes ( 4488 MB )
DVD+R/DVD+RW = 4 700 372 992 bytes ( 4482 MB )
DVD+R DL = 8 547 993 600 bytes ( 8152 MB )
DVD
DVD stands for Digital Versatile/Video Disc, DVDR stands for DVD Recordable and DVDRW for DVD ReWriteable. If you're familiar with regular audio/music CDs or regular DVD-Video discs, then you will know what a recordable DVD looks like. A recordable DVD stores up to 2 hours of very good quality DVD-Video, including several audio tracks in formats like stereo, Dolby Digital or DTS and also advanced menu systems, subtitles and still pictures that can be played by many standalone DVD Players and most computer DVD-ROMs. If you choose to lower the video quality it is possible to store several hours video on a recordable DVD using low bitrates and low resolution with video quality more like VHS, SVHS, SVCD, CVD or VCD. It is also possible to have up to 4.37* GB ordinary data or mix DVD-Video and data on a recordable DVD that can be played by most computer DVD-ROMs.
There are three competing DVD Recording standards, DVD-R/DVD-RW and DVD+R/DVD+RW have pretty similiar features and are compatible with many standalone DVD Players and most DVD-ROMs while DVD-RAM has less DVD Player and DVD-ROM compatibility but better recording features.
DVD-R and DVD-RW
DVD-R was the first DVD recording format released that was compatible with standalone DVD Players.
DVD-R is a non-rewriteable format and it is compatible with about 93% of all DVD Players and most DVD-ROMs.
DVD-RW is a rewriteable format and it is compatible with about 80% of all DVD Players and most DVD-ROMs.
DVD-R and DVD-RW supports single side 4.37 computer GB* DVDs(called DVD-5) and double sided 8.75 computer GB* DVDs(called DVD-10).
These formats are supported by DVDForum.
DVD+R and DVD+RW
DVD+R is a non-rewritable format and it is compatible with about 89% of all DVD Players and most DVD-ROMs.
DVD+RW is a rewritable format and is compatible with about 79% of all DVD Players and most DVD-ROMs.
DVD+R and DVD+RW supports single side 4.37 computer GB* DVDs(called DVD-5) and double side 8.75 computer GB* DVDs(called DVD-10).
These formats are supported by the DVD+RW Alliance.
DVD+R DL
DVD+R DL or called DVD+R9 is a Dual Layer writeable DVD+R. The dual layered discs can hold 7.95 computer GB* (called DVD-9) and dual layered double sides 15.9* computer GB (called dvd-18).
DVD-RAM
DVD-RAM has the best recording features but it is not compatible with most DVD-ROM drives and DVD-Video players. Think more of it as a removable hard disk. DVD-RAM is usually used in some DVD Recorders.
This format is supported by DVDForum.
DVD stands for Digital Versatile/Video Disc, DVDR stands for DVD Recordable and DVDRW for DVD ReWriteable. If you're familiar with regular audio/music CDs or regular DVD-Video discs, then you will know what a recordable DVD looks like. A recordable DVD stores up to 2 hours of very good quality DVD-Video, including several audio tracks in formats like stereo, Dolby Digital or DTS and also advanced menu systems, subtitles and still pictures that can be played by many standalone DVD Players and most computer DVD-ROMs. If you choose to lower the video quality it is possible to store several hours video on a recordable DVD using low bitrates and low resolution with video quality more like VHS, SVHS, SVCD, CVD or VCD. It is also possible to have up to 4.37* GB ordinary data or mix DVD-Video and data on a recordable DVD that can be played by most computer DVD-ROMs.
There are three competing DVD Recording standards, DVD-R/DVD-RW and DVD+R/DVD+RW have pretty similiar features and are compatible with many standalone DVD Players and most DVD-ROMs while DVD-RAM has less DVD Player and DVD-ROM compatibility but better recording features.
DVD-R and DVD-RW
DVD-R was the first DVD recording format released that was compatible with standalone DVD Players.
DVD-R is a non-rewriteable format and it is compatible with about 93% of all DVD Players and most DVD-ROMs.
DVD-RW is a rewriteable format and it is compatible with about 80% of all DVD Players and most DVD-ROMs.
DVD-R and DVD-RW supports single side 4.37 computer GB* DVDs(called DVD-5) and double sided 8.75 computer GB* DVDs(called DVD-10).
These formats are supported by DVDForum.
DVD+R and DVD+RW
DVD+R is a non-rewritable format and it is compatible with about 89% of all DVD Players and most DVD-ROMs.
DVD+RW is a rewritable format and is compatible with about 79% of all DVD Players and most DVD-ROMs.
DVD+R and DVD+RW supports single side 4.37 computer GB* DVDs(called DVD-5) and double side 8.75 computer GB* DVDs(called DVD-10).
These formats are supported by the DVD+RW Alliance.
DVD+R DL
DVD+R DL or called DVD+R9 is a Dual Layer writeable DVD+R. The dual layered discs can hold 7.95 computer GB* (called DVD-9) and dual layered double sides 15.9* computer GB (called dvd-18).
DVD-RAM
DVD-RAM has the best recording features but it is not compatible with most DVD-ROM drives and DVD-Video players. Think more of it as a removable hard disk. DVD-RAM is usually used in some DVD Recorders.
This format is supported by DVDForum.
Default Password List Website Links
http://www.phenoelit.de/dpl/dpl.html
CIRT.Net
http://www.cirt.net/cgi-bin/passwd.pl
http://www.phenoelit.de/dpl/dpl.html
CIRT.Net
http://www.cirt.net/cgi-bin/passwd.pl
System Preparation Tool (Sysprep) Script File Keys
Article ID : 196667
Last Review : September 9, 2002
Revision : 1.0
This article was previously published under Q196667
On this page
SUMMARY
MORE INFORMATION
REFERENCES
SUMMARY
When you use the Microsoft System Preparation (Sysprep) tool, a wizard runs the next time the computer is started after the tool prepares the computer and copies an image to the computer. You can automate this process by creating a script file. To use Sysprep with a script file, use the following syntax
sysprep.exe
where is the name of the script file.
Note that the script file must contain one section called [NT4Preinstall].
MORE INFORMATION
Script File Keys
You can use the following keys in the Sysprep script file:
Key name: OemSkipEula
Values: Yes | No
Description: This key disables the display of the End User License
Agreement (EULA) when the value is set to Yes. The default
value is No.
Key name: ProductID
Value: xxx-xxxxxxx OR xxxxx-OEM-xxxxxx-xxxxx
Description: This key specifies whether the Product ID screen should be
displayed. The Product ID key is displayed by default.
Key name: FullName
Value:
Description: This key specifies the user's name. If this key is not
specified or the string value is blank, the User Name And
Organization screen is displayed.
Key name: OrgName
Value:
Description: This key specifies the user's organization or company name.
If this key is not specified or the string value is blank,
the User Name And Organization screen is displayed, unless
the FullName key is specified with a valid string value.
Key name: ComputerName
Values: | "Auto"
Description: This key specifies the computer name. If this key is not
specified or the string value is blank, the Computer Name
screen is displayed. The string value must be a minimum of 1
non-white-space character and a maximum of 15 non-white-space
characters.
If this string value is set to "Auto," Setup automatically
generates a unique computer name based on a random number.
This provides a mechanism to install multiple computers with
a unique computer name.
Key name: AdminPassword
Value:
Description: This key specifies the password for the administrator
account. If this key is not specified or the string value is
blank, the Administrator Password screen is displayed. The
string value must be a minimum of 1 non-white-space character
and a maximum of 15 non-white-space characters. To specify a
blank or NULL password use "*".
Key name: OEMBannerText
Value:
Description: This key specifies a string to be displayed in the upper-left
corner of the screen. The text must contain the "Windows NT"
sub-string or it is ignored. You can specify multiple lines
by using the "*" character as a separator.
Key name: OEMLogoBitmapFile
Values: [, ]
Description: This key specifies a bitmap to be displayed in the upper-
right corner of the screen. If this key has only one field,
it is assumed to be a bitmap (.bmp) file located in the
folder in which the System Preparation tool resides. If two
fields are specified, the first field is the name of a
dynamic-link library (DLL) and the second field is a decimal
number that represents the resource ID of the bitmap in the
DLL. The DLL should be located in the folder that contains
Sysprep.exe.
Key name: OEMBackgroundBitmapFile
Values: [,]
Description: This key specifies a background bitmap to display. If this
key has only one field, it is assumed to be a bitmap (.bmp)
file located in the folder in which Sysprep.exe resides. If
two fields are specified, the first field is the name of a
dynamic-link library (DLL) and the second field is a decimal
number that represents the resource ID of the bitmap in the
DLL. The DLL should be located in the folder that contains
Sysprep.exe.
Key name: OEMSkipWelcome
Values: 0 | 1
Description: If this key is set to 1, the Welcome page is skipped. If the
key is set to 0, the Welcome page is displayed.
Key name: OEMNoWaitAfterGUIMode
Values: 0 | 1
Description: If this key is set to 1, the Finished page is not displayed
and the computer is automatically restarted when the wizard
is finished. If the key is set to 0, the Finished page is
displayed and the computer does not automatically restart.
Key name: NoSidGen
Value: Yes | No
Description: This key disables the Security Identification (SID)
modification code. Set this key to Yes to disable the SID
modification code. You might use this value if the computer
is to be preconfigured with system services and access (ACL)
permissions. This allows a system integrator or administrator
to preconfigure a computer and set the computer name,
administrator password, and other settings at the final
location.
NOTE: Do not use this key if you plan to duplicate the
system.
Sample Script File
The following sample file is an example of a Windows NT 4.0 Mini-Setup wizard script:
[NT4Preinstall]
OemSkipEula = Yes
ProductID = 123-4567890
FullName = "Sample Company User"
OrgName = "Sample Company Inc."
ComputerName = "auto"
AdminPassword = "password"
Sysprep.exe Command-Line Switches
Sysprep supports the following command-line switches:
Switch:
Description: Instructs the Windows NT 4.0 Mini-Setup wizard to use the
settings in the specified script file automatically. For
example, the following command specifies that the Mini-Setup
wizard should use the settings in the Nt4setup.inf file:
sysprep nt4setup.inf
NOTE: There is no dash preceding the script file name.
Switch: -quiet
Description: Instructs Sysprep to run without displaying a warning dialog
box. For example, the following command specifies that only
the license information screen should be displayed:
sysprep -quiet
The warning message stating that the computer is going to be
prepared for disk imaging and automatically shut down is not
displayed, and the computer shuts down automatically.
NOTE: The preceding dash is required.
Switch: -reboot
Description: Instructs Sysprep to automatically restart the computer. For
example, the following command specifies that the computer is
restarted automatically instead of being shut down after
Sysprep has finished:
sysprep -reboot
You should not use this switch if you are preparing the
computer for disk imaging. This switch may be useful if you
plan to automate a test process designed to run after Sysprep
has finished.
NOTE: The preceding dash is required.
Switch: -defeat
Description: Instructs Sysprep to run on a computer that has retail
versions of Windows NT 4.0 Workstation or Windows NT 4.0
Server and Microsoft Office 97. Normally, Sysprep requires
a Microsoft Select Volume CD-ROM or an OEM (Original
Equipment Manufacturer) CD-ROM installation to run.
The following sample Sysprep command uses all the command-line switches:
sysprep setupscript.inf -quiet -reboot -defeat
REFERENCES
For additional information about Sysprep, please review the Sysprep.doc file that is included with the Sysprep tool.
Article ID : 196667
Last Review : September 9, 2002
Revision : 1.0
This article was previously published under Q196667
On this page
SUMMARY
MORE INFORMATION
REFERENCES
SUMMARY
When you use the Microsoft System Preparation (Sysprep) tool, a wizard runs the next time the computer is started after the tool prepares the computer and copies an image to the computer. You can automate this process by creating a script file. To use Sysprep with a script file, use the following syntax
sysprep.exe
where
Note that the script file must contain one section called [NT4Preinstall].
MORE INFORMATION
Script File Keys
You can use the following keys in the Sysprep script file:
Key name: OemSkipEula
Values: Yes | No
Description: This key disables the display of the End User License
Agreement (EULA) when the value is set to Yes. The default
value is No.
Key name: ProductID
Value: xxx-xxxxxxx OR xxxxx-OEM-xxxxxx-xxxxx
Description: This key specifies whether the Product ID screen should be
displayed. The Product ID key is displayed by default.
Key name: FullName
Value:
Description: This key specifies the user's name. If this key is not
specified or the string value is blank, the User Name And
Organization screen is displayed.
Key name: OrgName
Value:
Description: This key specifies the user's organization or company name.
If this key is not specified or the string value is blank,
the User Name And Organization screen is displayed, unless
the FullName key is specified with a valid string value.
Key name: ComputerName
Values:
Description: This key specifies the computer name. If this key is not
specified or the string value is blank, the Computer Name
screen is displayed. The string value must be a minimum of 1
non-white-space character and a maximum of 15 non-white-space
characters.
If this string value is set to "Auto," Setup automatically
generates a unique computer name based on a random number.
This provides a mechanism to install multiple computers with
a unique computer name.
Key name: AdminPassword
Value:
Description: This key specifies the password for the administrator
account. If this key is not specified or the string value is
blank, the Administrator Password screen is displayed. The
string value must be a minimum of 1 non-white-space character
and a maximum of 15 non-white-space characters. To specify a
blank or NULL password use "*".
Key name: OEMBannerText
Value:
Description: This key specifies a string to be displayed in the upper-left
corner of the screen. The text must contain the "Windows NT"
sub-string or it is ignored. You can specify multiple lines
by using the "*" character as a separator.
Key name: OEMLogoBitmapFile
Values:
Description: This key specifies a bitmap to be displayed in the upper-
right corner of the screen. If this key has only one field,
it is assumed to be a bitmap (.bmp) file located in the
folder in which the System Preparation tool resides. If two
fields are specified, the first field is the name of a
dynamic-link library (DLL) and the second field is a decimal
number that represents the resource ID of the bitmap in the
DLL. The DLL should be located in the folder that contains
Sysprep.exe.
Key name: OEMBackgroundBitmapFile
Values:
Description: This key specifies a background bitmap to display. If this
key has only one field, it is assumed to be a bitmap (.bmp)
file located in the folder in which Sysprep.exe resides. If
two fields are specified, the first field is the name of a
dynamic-link library (DLL) and the second field is a decimal
number that represents the resource ID of the bitmap in the
DLL. The DLL should be located in the folder that contains
Sysprep.exe.
Key name: OEMSkipWelcome
Values: 0 | 1
Description: If this key is set to 1, the Welcome page is skipped. If the
key is set to 0, the Welcome page is displayed.
Key name: OEMNoWaitAfterGUIMode
Values: 0 | 1
Description: If this key is set to 1, the Finished page is not displayed
and the computer is automatically restarted when the wizard
is finished. If the key is set to 0, the Finished page is
displayed and the computer does not automatically restart.
Key name: NoSidGen
Value: Yes | No
Description: This key disables the Security Identification (SID)
modification code. Set this key to Yes to disable the SID
modification code. You might use this value if the computer
is to be preconfigured with system services and access (ACL)
permissions. This allows a system integrator or administrator
to preconfigure a computer and set the computer name,
administrator password, and other settings at the final
location.
NOTE: Do not use this key if you plan to duplicate the
system.
Sample Script File
The following sample file is an example of a Windows NT 4.0 Mini-Setup wizard script:
[NT4Preinstall]
OemSkipEula = Yes
ProductID = 123-4567890
FullName = "Sample Company User"
OrgName = "Sample Company Inc."
ComputerName = "auto"
AdminPassword = "password"
Sysprep.exe Command-Line Switches
Sysprep supports the following command-line switches:
Switch:
Description: Instructs the Windows NT 4.0 Mini-Setup wizard to use the
settings in the specified script file automatically. For
example, the following command specifies that the Mini-Setup
wizard should use the settings in the Nt4setup.inf file:
sysprep nt4setup.inf
NOTE: There is no dash preceding the script file name.
Switch: -quiet
Description: Instructs Sysprep to run without displaying a warning dialog
box. For example, the following command specifies that only
the license information screen should be displayed:
sysprep -quiet
The warning message stating that the computer is going to be
prepared for disk imaging and automatically shut down is not
displayed, and the computer shuts down automatically.
NOTE: The preceding dash is required.
Switch: -reboot
Description: Instructs Sysprep to automatically restart the computer. For
example, the following command specifies that the computer is
restarted automatically instead of being shut down after
Sysprep has finished:
sysprep -reboot
You should not use this switch if you are preparing the
computer for disk imaging. This switch may be useful if you
plan to automate a test process designed to run after Sysprep
has finished.
NOTE: The preceding dash is required.
Switch: -defeat
Description: Instructs Sysprep to run on a computer that has retail
versions of Windows NT 4.0 Workstation or Windows NT 4.0
Server and Microsoft Office 97. Normally, Sysprep requires
a Microsoft Select Volume CD-ROM or an OEM (Original
Equipment Manufacturer) CD-ROM installation to run.
The following sample Sysprep command uses all the command-line switches:
sysprep setupscript.inf -quiet -reboot -defeat
REFERENCES
For additional information about Sysprep, please review the Sysprep.doc file that is included with the Sysprep tool.
Wednesday, January 12, 2005
Cannot Start Windows XP After You Install Windows 2000
Article ID : 283433
Last Review : November 18, 2003
Revision : 1.0
This article was previously published under Q283433
On this Page
SYMPTOMS
CAUSE
RESOLUTION
STATUS
MORE INFORMATION
SYMPTOMS
When you attempt to start Windows XP after you install Windows 2000, you may receive the following error message:
"Starting Windows...
Windows 2000 could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM.
You can attempt to repair this file by starting Windows 2000 Setup using the original Setup floppy disk or CD-ROM.
Select 'r' at the first screen to start repair."
If the Windows XP install was an upgrade from Windows 2000, you may instead receive the following error message on a blue screen while attempting to start Windows XP:
BAD_SYSTEM_CONFIG_INFO
STOP 0x00000074
CAUSE
This issue occurs because Windows XP did not exist when Windows 2000 was released. The Windows 2000 bootstrap loader files are not aware of the changes that have been made in Windows XP. The computer needs these changes to load Windows XP.
NOTE: If you attempt to install Windows 2000 in a different partition while the computer is running Windows XP, you may receive the following error message:
This CD-ROM is from an older version of Windows than the one you are presently using. Setup functionality from this disk will be disabled.
RESOLUTION
To work around this issue, start the computer in Windows 2000, and then copy the NTLDR and Ntdetect.com files from the I386 folder on the Windows XP CD-ROM to the root of the system drive.
Even though a workaround for this issue is described in this article, you can only perform a dual Startup when you install Windows XP in a different partition after you install Windows 2000.
STATUS
This behavior is by design. In general, products are not forward compatible with future products because the design updates of future versions are unknown.
MORE INFORMATION
If you want to start multiple operating systems, install each operating system in a different partition in the following order: 1. Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows Millennium Edition (Me)
2. Microsoft Windows NT 4.0
3. Microsoft Windows 2000
4. Microsoft Windows XP
If you do not want to start the computer in all the operating systems that are listed, skip the ones that you do not need. NOTE: Do not convert the hard disk from Basic Disk to Dynamic Disk until you install all of the operating systems that you intend to use. Once you convert the hard disk from Basic Disk to Dynamic Disk, you may be unable to install any other operating systems on that hard disk.
For additional information about dynamic disks, click the article numbers below to view the articles in the Microsoft Knowledge Base:
175761 Dynamic vs. Basic Storage in Windows 2000
114841 Windows NT Boot Process and Hard Disk Constraints
Article ID : 283433
Last Review : November 18, 2003
Revision : 1.0
This article was previously published under Q283433
On this Page
SYMPTOMS
CAUSE
RESOLUTION
STATUS
MORE INFORMATION
SYMPTOMS
When you attempt to start Windows XP after you install Windows 2000, you may receive the following error message:
"Starting Windows...
Windows 2000 could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM.
You can attempt to repair this file by starting Windows 2000 Setup using the original Setup floppy disk or CD-ROM.
Select 'r' at the first screen to start repair."
If the Windows XP install was an upgrade from Windows 2000, you may instead receive the following error message on a blue screen while attempting to start Windows XP:
BAD_SYSTEM_CONFIG_INFO
STOP 0x00000074
CAUSE
This issue occurs because Windows XP did not exist when Windows 2000 was released. The Windows 2000 bootstrap loader files are not aware of the changes that have been made in Windows XP. The computer needs these changes to load Windows XP.
NOTE: If you attempt to install Windows 2000 in a different partition while the computer is running Windows XP, you may receive the following error message:
This CD-ROM is from an older version of Windows than the one you are presently using. Setup functionality from this disk will be disabled.
RESOLUTION
To work around this issue, start the computer in Windows 2000, and then copy the NTLDR and Ntdetect.com files from the I386 folder on the Windows XP CD-ROM to the root of the system drive.
Even though a workaround for this issue is described in this article, you can only perform a dual Startup when you install Windows XP in a different partition after you install Windows 2000.
STATUS
This behavior is by design. In general, products are not forward compatible with future products because the design updates of future versions are unknown.
MORE INFORMATION
If you want to start multiple operating systems, install each operating system in a different partition in the following order: 1. Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows Millennium Edition (Me)
2. Microsoft Windows NT 4.0
3. Microsoft Windows 2000
4. Microsoft Windows XP
If you do not want to start the computer in all the operating systems that are listed, skip the ones that you do not need. NOTE: Do not convert the hard disk from Basic Disk to Dynamic Disk until you install all of the operating systems that you intend to use. Once you convert the hard disk from Basic Disk to Dynamic Disk, you may be unable to install any other operating systems on that hard disk.
For additional information about dynamic disks, click the article numbers below to view the articles in the Microsoft Knowledge Base:
175761 Dynamic vs. Basic Storage in Windows 2000
114841 Windows NT Boot Process and Hard Disk Constraints
Monday, January 10, 2005
Read-Only USB Storage
If you've been concerned about the possibility that users in your Windows XP environment might plug in a USB storage key and walk away with hundreds of megabytes of proprietary corporate information, XP Service Pack 2 (SP 2) lets you make USB storage devices read only, removing the possibility of leaking data via a USB key. To configure USB storage for read only, perform the following steps:
1. Launch the registry editor.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. You should see a key called StorageDevicePolicies. If it doesn't exist, create a new key with that name.
4. In the StorageDevicePolicy key, create a REG_DWORD value called WriteProtect.
5. Set the data value of WriteProtect to 1.
6. This value will make USB storage read only. To enable read/write over USB, set the value to 0.
7. Exit the editor.
Make sure that you aren't using other USB storage devices such as hard drives or a CD/DVD writer before you set this registry value.
If you've been concerned about the possibility that users in your Windows XP environment might plug in a USB storage key and walk away with hundreds of megabytes of proprietary corporate information, XP Service Pack 2 (SP 2) lets you make USB storage devices read only, removing the possibility of leaking data via a USB key. To configure USB storage for read only, perform the following steps:
1. Launch the registry editor.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. You should see a key called StorageDevicePolicies. If it doesn't exist, create a new key with that name.
4. In the StorageDevicePolicy key, create a REG_DWORD value called WriteProtect.
5. Set the data value of WriteProtect to 1.
6. This value will make USB storage read only. To enable read/write over USB, set the value to 0.
7. Exit the editor.
Make sure that you aren't using other USB storage devices such as hard drives or a CD/DVD writer before you set this registry value.
Wednesday, December 01, 2004
Daily News
Planet Alignment Could Crash Net
By Martin Stone, Newsbytes.
February 03, 2000
Doomsday forecasters have shifted their attention from the Millennium Bug, which proved to have little bite, to an extraterrestrial occurrence destined to take place May 5, when a cluster of planets will align with the Earth.
Some say the phenomenon has the potential of creating colossal cosmic forces which could severely impact our planet.
Occurring only once every 6,000 years or so, the rare alignment of Mercury, Venus, Mars, Jupiter, Saturn, the Earth, the Sun, and the Moon could cause a magnetic surge with the potential to crash power grids, blind satellites, and seriously disrupt radio and landline communications, taking the Internet down in the process.
However, not all astronomers agree that the so-called "grand alignment" will have an effect on terra firma. According to a Canadian newspaper report this week, John Mosely, an astronomer at the Griffith Observatory in Los Angeles, has proclaimed, "There will be no effect whatsoever. It's just complete nonsense." An astronomer at St. Mary's University in Halifax was blunter, calling the fears, "Just a load of crap."
But the same article, filed by the Canadian Press wire service and carried by Monday's Montreal Gazette newspaper, quoted Georgia-based futurist Richard Noone as saying the alignment could trigger a massive magnetic flux and a huge solar storm. "We're talking about a solar mass ejection in which a billion-tonne wave of super-hot, electrically charged gas is discharged from the Sun and crosses space like a giant tidal wave. It would crash into Earth's electromagnetic field at 620 miles a second."
As well as the communications systems wipeout, Noone predicts the cosmic event could produce a spectacular display of northern lights, which he said might be visible as far south as Florida.
Survival Center Website operator Craig Smith told Newsbytes, "Yes, the potential does exist. The big question is - but will it?" He refers to Noone's article "Are We Approaching the Abyss?" and quotes, "Past solar storms have caused incredible damage, including disruptions of radio, television, telephone, satellites, radar, power lines, power company grids and other sophisticated electronic technologies. These past solar storms will be mere blips of inconvenience to us, compared to The Storm of the Millennium coming this spring."
More of Noone's predictions can be found at http://rnoone.com .
However, Philip Plait, operator of an astronomy-focused Website, told Newsbytes, "There will be no natural ramifications whatsoever from this alignment. The gravitational and tidal effects are so puny that they will be unmeasurable. Last December's full Moon was unusually close. I did a quick calculation and showed that the gravity of that full Moon was much larger than the Moon and planets in this upcoming alignment. We weren't destroyed on Dec. 22, and we won't be in May.
"There won't be any electromagnetic effects either. The Sun is the only real contributor of these kinds of effects to the Earth. The sunspot cycle and therefore solar activity will be at a maximum this year. However, this has nothing to do with the alignment."
Plait has posted a wealth of grand alignment information on his site at http://www.badastronomy.co/bad/misc/planets.html .
Other doomsayers fear an extraordinary gravitational pull on our planet, which would wreak havoc in many ways, including causing the Earth's tilt to change, not to mention earthquakes and floods.
Many scientists anticipate a major solar disturbance this year but most insist the grand alignment will have no effect on solar storms, which occur in predictable 11-year cycles. Major storms and eruptions on the Sun's surface have been known to affect communications systems and are blamed for a province-wide blackout in Quebec in 1989.
Plait summed up the controversy by declaring, "There will be a lot of people trying to tell you something different than what I am saying here. Chances are, they're trying to sell something."
Reported by Newsbytes.com
Planet Alignment Could Crash Net
By Martin Stone, Newsbytes.
February 03, 2000
Doomsday forecasters have shifted their attention from the Millennium Bug, which proved to have little bite, to an extraterrestrial occurrence destined to take place May 5, when a cluster of planets will align with the Earth.
Some say the phenomenon has the potential of creating colossal cosmic forces which could severely impact our planet.
Occurring only once every 6,000 years or so, the rare alignment of Mercury, Venus, Mars, Jupiter, Saturn, the Earth, the Sun, and the Moon could cause a magnetic surge with the potential to crash power grids, blind satellites, and seriously disrupt radio and landline communications, taking the Internet down in the process.
However, not all astronomers agree that the so-called "grand alignment" will have an effect on terra firma. According to a Canadian newspaper report this week, John Mosely, an astronomer at the Griffith Observatory in Los Angeles, has proclaimed, "There will be no effect whatsoever. It's just complete nonsense." An astronomer at St. Mary's University in Halifax was blunter, calling the fears, "Just a load of crap."
But the same article, filed by the Canadian Press wire service and carried by Monday's Montreal Gazette newspaper, quoted Georgia-based futurist Richard Noone as saying the alignment could trigger a massive magnetic flux and a huge solar storm. "We're talking about a solar mass ejection in which a billion-tonne wave of super-hot, electrically charged gas is discharged from the Sun and crosses space like a giant tidal wave. It would crash into Earth's electromagnetic field at 620 miles a second."
As well as the communications systems wipeout, Noone predicts the cosmic event could produce a spectacular display of northern lights, which he said might be visible as far south as Florida.
Survival Center Website operator Craig Smith told Newsbytes, "Yes, the potential does exist. The big question is - but will it?" He refers to Noone's article "Are We Approaching the Abyss?" and quotes, "Past solar storms have caused incredible damage, including disruptions of radio, television, telephone, satellites, radar, power lines, power company grids and other sophisticated electronic technologies. These past solar storms will be mere blips of inconvenience to us, compared to The Storm of the Millennium coming this spring."
More of Noone's predictions can be found at http://rnoone.com .
However, Philip Plait, operator of an astronomy-focused Website, told Newsbytes, "There will be no natural ramifications whatsoever from this alignment. The gravitational and tidal effects are so puny that they will be unmeasurable. Last December's full Moon was unusually close. I did a quick calculation and showed that the gravity of that full Moon was much larger than the Moon and planets in this upcoming alignment. We weren't destroyed on Dec. 22, and we won't be in May.
"There won't be any electromagnetic effects either. The Sun is the only real contributor of these kinds of effects to the Earth. The sunspot cycle and therefore solar activity will be at a maximum this year. However, this has nothing to do with the alignment."
Plait has posted a wealth of grand alignment information on his site at http://www.badastronomy.co/bad/misc/planets.html .
Other doomsayers fear an extraordinary gravitational pull on our planet, which would wreak havoc in many ways, including causing the Earth's tilt to change, not to mention earthquakes and floods.
Many scientists anticipate a major solar disturbance this year but most insist the grand alignment will have no effect on solar storms, which occur in predictable 11-year cycles. Major storms and eruptions on the Sun's surface have been known to affect communications systems and are blamed for a province-wide blackout in Quebec in 1989.
Plait summed up the controversy by declaring, "There will be a lot of people trying to tell you something different than what I am saying here. Chances are, they're trying to sell something."
Reported by Newsbytes.com
Friday, November 26, 2004
Windows Server 2003 10 in 1 CD
The Windows Server 2003 family builds on the proven reliability,
scalability, and manageability of Windows 2000 Server while improving
essential services. Now with enhanced security and better performance,
the Windows Server 2003 family offers the best server infrastructure
for increasing IT efficiency, developing applications quickly, and
enhancing productivity.
This release includes both corporate (VLK) and Retail versions of:
Microsoft Windows Server 2003, Enterprise Edition (32-Bit)
Microsoft Windows Server 2003, Datacenter Edition (32-Bit)
Microsoft Windows Server 2003, Small Business Edition CD1
Microsoft Windows Server 2003, Standard Edition
Microsoft Windows Server 2003, Web Edition
This is the all-in-one release of Windows Server 2003,
with the Datacenter, Enterprise, Small Business, Standard and Web
Editions. Also this is a Volume License ISO, which never needs to be
activated. This version also includes the patched uxtheme.dll in every
version so no patching is required. Use the included Reset 5.02 to bypass
activation for non-vlk installations. CD-Keys are automatically entered
in each setup. Download Small Business CD2/3 to complete the install of
Windows Server 2003 Small Business.
o------------------------ I N S T A L L N O T E S ------------------------o
1. Instert CD and install your favorite flavor of Windows 2003 or boot
from CD and install.
2. CD Keys: illegal to provide this info
Enterprise/Datacenter: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
Small Business: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
Standard: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
VLK: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
Web: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
The Windows Server 2003 family builds on the proven reliability,
scalability, and manageability of Windows 2000 Server while improving
essential services. Now with enhanced security and better performance,
the Windows Server 2003 family offers the best server infrastructure
for increasing IT efficiency, developing applications quickly, and
enhancing productivity.
This release includes both corporate (VLK) and Retail versions of:
Microsoft Windows Server 2003, Enterprise Edition (32-Bit)
Microsoft Windows Server 2003, Datacenter Edition (32-Bit)
Microsoft Windows Server 2003, Small Business Edition CD1
Microsoft Windows Server 2003, Standard Edition
Microsoft Windows Server 2003, Web Edition
This is the all-in-one release of Windows Server 2003,
with the Datacenter, Enterprise, Small Business, Standard and Web
Editions. Also this is a Volume License ISO, which never needs to be
activated. This version also includes the patched uxtheme.dll in every
version so no patching is required. Use the included Reset 5.02 to bypass
activation for non-vlk installations. CD-Keys are automatically entered
in each setup. Download Small Business CD2/3 to complete the install of
Windows Server 2003 Small Business.
o------------------------ I N S T A L L N O T E S ------------------------o
1. Instert CD and install your favorite flavor of Windows 2003 or boot
from CD and install.
2. CD Keys: illegal to provide this info
Enterprise/Datacenter: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
Small Business: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
Standard: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
VLK: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
Web: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
Thursday, November 18, 2004
Generic Product Keys
Deploying Windows XP Using Windows Product Activation
All of the examples provided above used a beta key for illustration purposes. The product keys listed in this section can be used with any of the answer files and scripted examples. They are blocked at the Microsoft clearinghouse and therefore cannot be used to activate any systems. They provide a number of days (assume 14 days) for you to complete the activation process.
It is absolutely essential that you use the correct type of key, which is a function of the platform type and the media. Choose the key and corresponding sequence number for your scripts from the following table:
Generic Product Keys
Applicability
Product Key
Sequence Number
Whistler Tech Beta Program
(All Platforms)
PXRQ3-7VPMV-CQWXR-8Y4KX-RD786
010053298
Windows XP
Home Edition
Full product
JKTVX-HCRXC-J2YC9-MX3K4-G9X26
005037750
Windows XP
Home Edition
Upgrade
C84VB-JYVFD-P7HF4-6KKRJ-7M6XH
010000182
Windows XP Professional
Full product
DR8GV-C8V6J-BYXHG-7PYJR-DB66Y
005072760
Windows XP Professional
Upgrade
FKTW8-Q7MJ7-JK6GW-9J9RV-HC3C2
010000212
Windows XP
Home Edition
System Builder (Full)
KGVXT-F9HVW-XGW9X-QVYVX-HQ9RD
120000613
Windows XP Professional
System Builder (Full)
TTGHK-3RC33-BT9DR-3BVYV-BTQ98
120000607
Original Link : http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/wpadepl.mspx
Deploying Windows XP Using Windows Product Activation
All of the examples provided above used a beta key for illustration purposes. The product keys listed in this section can be used with any of the answer files and scripted examples. They are blocked at the Microsoft clearinghouse and therefore cannot be used to activate any systems. They provide a number of days (assume 14 days) for you to complete the activation process.
It is absolutely essential that you use the correct type of key, which is a function of the platform type and the media. Choose the key and corresponding sequence number for your scripts from the following table:
Generic Product Keys
Applicability
Product Key
Sequence Number
Whistler Tech Beta Program
(All Platforms)
PXRQ3-7VPMV-CQWXR-8Y4KX-RD786
010053298
Windows XP
Home Edition
Full product
JKTVX-HCRXC-J2YC9-MX3K4-G9X26
005037750
Windows XP
Home Edition
Upgrade
C84VB-JYVFD-P7HF4-6KKRJ-7M6XH
010000182
Windows XP Professional
Full product
DR8GV-C8V6J-BYXHG-7PYJR-DB66Y
005072760
Windows XP Professional
Upgrade
FKTW8-Q7MJ7-JK6GW-9J9RV-HC3C2
010000212
Windows XP
Home Edition
System Builder (Full)
KGVXT-F9HVW-XGW9X-QVYVX-HQ9RD
120000613
Windows XP Professional
System Builder (Full)
TTGHK-3RC33-BT9DR-3BVYV-BTQ98
120000607
Original Link : http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/wpadepl.mspx
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.
Just some random screenshots:
Here we have an OEM version of WinXP letting us know we can't upgrade:
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.
Just some random screenshots:
Here we have an OEM version of WinXP letting us know we can't upgrade:
Remove Saved Passwords
Windows XP offers the ability to save passwords for web sites and network resources. This can be very convenient as opposed to remembering and entering the username and password each time you need access, but it poses a security risk because anyone who has physical access to your computer would also be able to log into those sites using your saved credentials. While biometrics and other user authentication methods have become more widely used and accepted in recent years, the prevailing method of user athentication remains the username and password. Users have passwords to access their computer, shared network resources, web sites, business applications and other resources.
Different sites and applications have different policies regarding how to create the passwords and standard security practices suggest that users should use a different and unique password for each login. For many users it becomes unruly to recall the various usernames and passwords and they may write them down on a notepad in their desk drawer or put it on a sticky note on their monitor so they can remember them all. Of course, anyone else can also come along and read the passwords as well.
Windows XP offers users the ability to retain passwords so that the authentication information required to login is automatically pre-populated when the different sites or resources are accessed rather than the user having to enter them each time. Because this requires being logged into the computer in the first place it provides some convenience for the user while remaining more secure than writing everything on a sticky note on the monitor. Unfortunately, it is still counter-productive from a security perspective because anyone who sits down at the computer while it is logged in or gains access to your computer user account will subsequently be able to access all of the various sites and resources as if they were the user because of the cached login credentials.
Windows XP does not offer a very easy way to review or remove the saved passwords though. If you follow the steps below though you can access a graphical interface to add, remove or edit the saved passwords on a given system.
1. Click Start and select Run
2. In the Open field type "rundll32.exe keymgr.dll, KRShowKeyMgr"
3. Once the Stored Usernames and Passwords interface opens you can select any of the entries and select Properties to view the existing information
4. To remove a saved password you can select one of the entries and select Remove. A confirmation screen will appear. Click on OK and the account will be removed
5. You can add additional saved passwords as well by clicking on the Add button and entering the appropriate information
6. Repeat the steps above as needed to add, remove or edit saved passwords
7. When you are done using the interface click the Close button
Tony Bradley is a consultant and writer with a focus on network security, antivirus and incident response. He is the About.com Guide for Internet / Network Security (http://netsecurity.about.com), providing a broad range of information security tips, advice, reviews and information. Tony also contributes frequently to other industry publications. For a complete list of his freelance contributions you can visit Essential Computer Security (http://www.tonybradley.com).
Windows XP offers the ability to save passwords for web sites and network resources. This can be very convenient as opposed to remembering and entering the username and password each time you need access, but it poses a security risk because anyone who has physical access to your computer would also be able to log into those sites using your saved credentials. While biometrics and other user authentication methods have become more widely used and accepted in recent years, the prevailing method of user athentication remains the username and password. Users have passwords to access their computer, shared network resources, web sites, business applications and other resources.
Different sites and applications have different policies regarding how to create the passwords and standard security practices suggest that users should use a different and unique password for each login. For many users it becomes unruly to recall the various usernames and passwords and they may write them down on a notepad in their desk drawer or put it on a sticky note on their monitor so they can remember them all. Of course, anyone else can also come along and read the passwords as well.
Windows XP offers users the ability to retain passwords so that the authentication information required to login is automatically pre-populated when the different sites or resources are accessed rather than the user having to enter them each time. Because this requires being logged into the computer in the first place it provides some convenience for the user while remaining more secure than writing everything on a sticky note on the monitor. Unfortunately, it is still counter-productive from a security perspective because anyone who sits down at the computer while it is logged in or gains access to your computer user account will subsequently be able to access all of the various sites and resources as if they were the user because of the cached login credentials.
Windows XP does not offer a very easy way to review or remove the saved passwords though. If you follow the steps below though you can access a graphical interface to add, remove or edit the saved passwords on a given system.
1. Click Start and select Run
2. In the Open field type "rundll32.exe keymgr.dll, KRShowKeyMgr"
3. Once the Stored Usernames and Passwords interface opens you can select any of the entries and select Properties to view the existing information
4. To remove a saved password you can select one of the entries and select Remove. A confirmation screen will appear. Click on OK and the account will be removed
5. You can add additional saved passwords as well by clicking on the Add button and entering the appropriate information
6. Repeat the steps above as needed to add, remove or edit saved passwords
7. When you are done using the interface click the Close button
Tony Bradley is a consultant and writer with a focus on network security, antivirus and incident response. He is the About.com Guide for Internet / Network Security (http://netsecurity.about.com), providing a broad range of information security tips, advice, reviews and information. Tony also contributes frequently to other industry publications. For a complete list of his freelance contributions you can visit Essential Computer Security (http://www.tonybradley.com).
Subscribe to:
Posts (Atom)