Odf XP OOBE behavior

Discussion in 'Windows XP / Older OS' started by NonverbalMel, Jul 2, 2023.

  1. NonverbalMel

    NonverbalMel MDL Member

    Oct 11, 2021
    103
    39
    10
    Hi All

    I was stupid and installed a retail copy of windows XP in a VM, got it just the way I wanted, setup the Sysprep.inf and ran Sysprep. when that was done I took a snapshot and booted for the “first time” and during OOBE I get prompted for a CD Key (I entered it in Setup Manager during the preparation)

    see below:

    Windows XP Client Template-2023-07-01-15-46-50.png


    is this behavior to be expected when using Retail XP disc? what went up in smoke?

    in my collection I have all service packs of Home, Pro, and DME. within this collection I have retail, VLK, and OEM versions. I’m curious why on earth would they include the sysprep features in retail windows disc (you’d think someone eho’s an enthusiast would build a new machine, set it up, and image the sucker for easy restore. seriously… what gives?
     
  2. thetank18

    thetank18 MDL Member

    Oct 23, 2019
    102
    82
    10
    Can you send the ISO (or something that leads to the ISO on Google)? This looks pretty interesting, I've never seen this screen before.
     
  3. George King

    George King MDL Expert

    Aug 5, 2009
    1,961
    2,468
    60
    If you skip product key during setup, then it's normal.

    If you have not added product key to oobeinfo.ini when syspreping, then it's normal.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. NonverbalMel

    NonverbalMel MDL Member

    Oct 11, 2021
    103
    39
    10
    Thanks so much for reminding me of this :) With things like Vista and up, Syspreping has gotten so much easier that I forgot about the extra work involved in XP and Win 2k
     
  5. NonverbalMel

    NonverbalMel MDL Member

    Oct 11, 2021
    103
    39
    10
    so here is my oobeinfo.ini (product key shown is the sample from the help). I constructed it using all the examples in the ref.chm that comes with Windows XP deploy.cab, simply copy the example, put it into notepad and them modify to meet my needs (rinse and repeat until all sections are in and customized) then save as oobeinfo.ini to the same place as sysprep. Sad part is, even with this in place, I still get the above.

    Code:
     
    [Branding]
    OemName = "VMWare, Inc."
    
    [Options]
    ;show Admin Password Page Welcome
    AdminPW = 1
    ;Enable anti-aliasing
    FontSmoothing = 1
    ;Show Doin Domain Page in Welcome
    JoinDomain = 1
    ;Display OEM Eula in Welcome
    OemEula = 1
    ;Path To OEM EULA
    OemEulaText = "C:\Windows\Oemeula.txt"
    Show Auto-Update Page in Welcome
    SkipAutoUpdate = 0
    ;Show regional settings Page in Welcome
    INTL_Settings = 1
    ;Show time Zone Page in Welcome
    TimeZone = 1
    
    [StartupOptions]
    DesktopWindowHeight = 530
    DesktopWindowWidth = 640
    Offline = 1
    Registration = 1
    ScreenResolutionCheck = 0
    
    UserInfo]
    Country = "USA"
    
    [Version]
    ProductKey = "12345-ABCDE-67890-FGHIJ-12345"
    
    
    What am I missing here? Note in the ProductKey value, I use a key generated from a tool

    Thanks again for any help.
     
  6. George King

    George King MDL Expert

    Aug 5, 2009
    1,961
    2,468
    60
    Just place it in correct location
    Code:
    %WinDir%\system32\oobe\oobeinfo.ini
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. George King

    George King MDL Expert

    Aug 5, 2009
    1,961
    2,468
    60
    Btw, Thats why I created XP2ESD, to make it single click activity
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...