3,463
edits
Windows XP Starter Edition: Difference between revisions
no edit summary
No edit summary Tags: Mobile edit Mobile web edit |
No edit summary |
||
| Line 10: | Line 10: | ||
|sku = Starter Edition | |sku = Starter Edition | ||
|based-on = [[Windows XP|Windows XP Home Edition]] | |based-on = [[Windows XP|Windows XP Home Edition]] | ||
|replaced-by = [[Windows Vista]] | |replaced-by = [[Windows Vista|Windows Vista Starter]] | ||
}} | }} | ||
'''Windows XP Starter Edition''' is an edition of [[Windows XP]], released on 11 August 2004. It is a stripped down version of Windows XP Home Edition that was released internationally for low-cost or low-end PCs in developing countries like Vietnam, Malaysia, Thailand and some Latin American countries. | '''Windows XP Starter Edition''' is an edition of [[Windows XP]], released on 11 August 2004. It is a stripped down version of Windows XP Home Edition that was released internationally for low-cost or low-end PCs in developing countries like Vietnam, Malaysia, Thailand and some Latin American countries. | ||
| Line 22: | Line 22: | ||
*It uses large icons and mouse cursor by default. | *It uses large icons and mouse cursor by default. | ||
*There is only one wallpaper that is used by default. However, international releases have different backgrounds. | *There is only one wallpaper that is used by default. However, international releases have different backgrounds. | ||
*It contains a very different File Protection, if there is any user modification in the registry or a few system files, then an "Unsupported state" error message will appear and then <code>winlogon.exe</code> will get terminated, more than likely leading to a system crash. Disabling some protection services may prevent this, however it has a very harsh File Protection system which restores the files and the registry settings upon changing them. | *It contains a very different File Protection, if there is any user modification in the registry or a few system files, then an "Unsupported state" error message will appear and then <code>winlogon.exe</code> will get terminated, more than likely leading to a system crash. This is mostly seen Disabling some protection services may prevent this, however it has a very harsh File Protection system which restores the files and the registry settings upon changing them. | ||
*Classic View in the Control Panel is missing, however it can be restored via logging in as a SYSTEM or NETWORKSERVICE account privilege. | *Classic View in the Control Panel is missing, however it can be restored via logging in as a SYSTEM or NETWORKSERVICE account privilege. | ||
*Attempting to logon as ''NT AUTHORITY\SYSTEM'' works, however it doesn't provide much advantages over the regular "Administrator" account, and much of the protected system components are controlled by a higher level. | *Attempting to logon as ''NT AUTHORITY\SYSTEM'' works, however it doesn't provide much advantages over the regular "Administrator" account, and much of the protected system components are controlled by a higher level. | ||
| Line 36: | Line 36: | ||
{{BLItem Leaked|Windows XP Starter Edition build 2600.2901|2600.2901.xpsp_sp2_gdr.060504-0312}} | {{BLItem Leaked|Windows XP Starter Edition build 2600.2901|2600.2901.xpsp_sp2_gdr.060504-0312}} | ||
=== Service Pack 3 === | ===Service Pack 3=== | ||
{{BLItem Leaked|Windows XP build 2600.5512|2600.5512.xpsp.080413-2111}} | {{BLItem Leaked|Windows XP build 2600.5512|2600.5512.xpsp.080413-2111}} | ||
==References== | ==References== | ||
<references /> | <references /> | ||