Talk:Windows XP

Naming system of build pages when there is a revision number
I have a question. How will we handle the revision numbers in the build page names? -- AlphaBeta (talk) 14:08, 30 June 2013 (BST)


 * I don't understand what do you mean, but it shouldn't be a problem to use Windows:XP:2120:xp_client:Rev1 if needed. --JaGoTu (talk) 11:44, 1 July 2013 (BST)


 * I mean, for example, 2600.5512. How will we handle the revision number in the page name? --AlphaBeta (talk) 11:54, 1 July 2013 (BST)


 * Just "merge" it with the build number, it shoul do. --JaGoTu (talk) 17:09, 5 July 2013 (BST)

Windows Whistler PE
This Follows Windows Whistler PE are included Build 2296, 2462, 2526. That thing is Windows Whistler PE. --Preceding unsigned comment added by BillyHatcher2012 (talk) 05:27 BST, 5 April 2014
 * You mean what?
 * Offtopic: Please sign your post by typing ~ on end of your post.
 * --AlphaBeta (talk) 20:05, 8 April 2014 (BST)
 * Looks like he means the WinPE builds for Whistler are 2296, 2462, and 2526. I do not recall seeing or downloading a WinPE image with XP 2462 as a base. -wdn 93.41.178.31 15:52, 9 August 2014 (BST)
 * I've got record of a 2462 PE. Also a 2505 one. Hounsell (talk) 00:35, 10 August 2014 (BST)

Fake builds
These fake build tags: 2309.prebeta2.001047-1279 2429.idx03.010392-1900 2571.xpclient.011254-1551 should be removed IMO. It's illogical to compile a build with impossible time and date strings. I mean, who'd create a Windows build with the buildtag having date and time strings set to 92nd March 2001 or on 47th October 2000 at 12:79? Just saying. -wdn 93.41.192.184 12:55, 6 August 2014 (BST)

There was one Vista build that was legit but had an impossible build tag, an error of the build process iirc. But these are definitely fakes, I agree, and should be killed -Hounsell (talk) 12:32, 7 August 2014 (BST)