aspire 3680 serie /copy pre-installed xp actavation

Discussion in 'Windows XP / Older OS' started by dumble, Mar 8, 2011.

  1. dumble

    dumble MDL Member

    Jan 17, 2009
    119
    21
    10
    Hello,

    Im fixing up an old laptop.
    Acer aspire 3680 series.

    I just updated the bios to 3216 (latest version)

    The laptop is not running fine on the current winxp home install, and I think its better to make a clean install

    This laptop came with Winxp Home (dutch) pre-installed (I think anyway). On the back of the computer there is a winxp sticker with a product key.

    Because of only 512MB of ram memory I think its better to stick with windowsXP.

    I recently downloaded the msdn version of winxp home with sp3 (dutch edition)
    Can I install this version of windows with the product key from the back? Or is this not possible. Maybe I can copy the activation files from the current install and put it in the new one.
     
  2. dumble

    dumble MDL Member

    Jan 17, 2009
    119
    21
    10
    #4 dumble, Mar 8, 2011
    Last edited by a moderator: Apr 20, 2017
    (OP)
    MGADiag Report:
    Code:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Validation Code: N/A
    Windows Product Key: *****-*****-36J2P-HT3T3-QPMFB
    Windows Product Key Hash: +NNF346DA3Rr/gGjXZtwAv8AQuM=
    Windows Product ID: 76395-OEM-2111907-00100
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 5.1.2600.2.00010300.3.0.hom
    ID: {9851A91A-A127-4639-8731-78926ED1C2B9}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.7.69.2
    Signed By: Microsoft
    Product Name: N/A
    Architecture: N/A
    Build lab: N/A
    TTS Error: N/A
    Validation Diagnostic: 025D1FF3-230-1_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005
    Resolution Status: N/A
    
    Vista WgaER Data-->
    ThreatID(s): N/A
    Version: N/A
    
    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002
    
    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002
    
    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: B4D0AA8B-543-80070002_025D1FF3-230-1
    
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Documents and Settings\Dhr Knitel\Local Settings\Application Data\Google\Chrome\Application\chrome.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed
    
    File Scan Data-->
    
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{9851A91A-A127-4639-8731-78926ED1C2B9}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010300.3.0.hom</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-QPMFB</PKey><PID>76395-OEM-2111907-00100</PID><PIDType>2</PIDType><SID>S-1-5-21-147383901-649948567-1509825399</SID><SYSTEM><Manufacturer>Acer, inc.</Manufacturer><Model>Aspire 3680     </Model></SYSTEM><BIOS><Manufacturer>Acer   </Manufacturer><Version>v1.3216</Version><SMBIOSVersion major="2" minor="4"/><Date>20061027000000.000000+000</Date><SLPBIOS>AcerSystem ,AcerSystem </SLPBIOS></BIOS><HWID>84713707018400DE</HWID><UserLCID>0413</UserLCID><SystemLCID>0413</SystemLCID><TimeZone>West-Europa (standaardtijd)(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>2</stat><msppid></msppid><name>Acer Inc.</name><model>AcerSystem</model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  
    
    Licensing Data-->
    N/A
    
    Windows Activation Technologies-->
    N/A
    
    HWID Data-->
    N/A
    
    OEM Activation 1.0 Data-->
    BIOS string matches: yes
    Marker string from BIOS: 165F3:Acer Incorporated|110DB:Acer Incorporated
    Marker string from OEMBIOS.DAT: AcerSystem ,AcerSystem 
    
    OEM Activation 2.0 Data-->
    N/A
    
    
     
  3. 38956

    38956 MDL Member

    Jun 7, 2010
    130
    138
    10
  4. dumble

    dumble MDL Member

    Jan 17, 2009
    119
    21
    10
    #6 dumble, Mar 8, 2011
    Last edited: Mar 8, 2011
    (OP)
    he 3856,

    I read the guide, but I don't really get it. I created the vbs file from your thread. I run it, and it created this OEMBIOS folder with a i386 folder in it (with some 5 files.)

    As I said, I already downloaded the official msdn winXP home with SP3 (dutch edition) ISO. Can I use this ISO? Can I not just mount this msdn ISO, copy all file to a new dir on my HD, and copy the i386 folder (created from you script) over the msdn i386 folder and then burn it again? Would that be enough?
     
  5. 38956

    38956 MDL Member

    Jun 7, 2010
    130
    138
    10
    #7 38956, Mar 8, 2011
    Last edited: Mar 8, 2011
    The ISO you have downloaded is a Retail version which doesn't accept OEM Product Keys

    You need to download a XP Home OEM installation disc or I think you can modify the Retail disc to accept OEM Keys

    The OEMBIOS files are used to pre-activated windows with the SLP product key which is in the winnt.sif file (which you can open with notepad) these are place in the i386 folder of the windows xp OEM installation disc
     
  6. 911medic

    911medic MDL Guru

    Aug 13, 2008
    5,777
    504
    180
    change setupp.ini to to OEM

    You may also need the DPCDLL.DLL and Pidgen.dll from the oembios changer tool.

    Put the five files you got from the script into the iso /I386 folder. You may have to compress the OEMBIOS and DLL files. Some of the script versions do, some dont. I have a script to compress them all if you need. Or just use makecab command.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. dumble

    dumble MDL Member

    Jan 17, 2009
    119
    21
    10
    OK, I would like to convert the msdn retail ISO to an OEM ISO. But I am not really sure how to do this though.

    What iv got now is this:

    - I mounted the msdn retail ISO, copied all files to a new folder 'WinXPHome' (so now I can modify them...)
    - I got the I386 folder with the 5 files. (created with 38956's script)


    Now what do I need to do exactly? Which files to change/compress? And how?
     
  8. 38956

    38956 MDL Member

    Jun 7, 2010
    130
    138
    10
    #10 38956, Mar 9, 2011
    Last edited: Mar 16, 2011
    1. Open WinXPHome\i386\setupp.ini in notepad and change PID Entry to OEM (see 911medic's post)
    2. Place the 5 files you got using my script and place them in the WinXPHome\i386 folder (to pre-activate windows)
    3. Replace all the files in ISO image and burn image (note: if you just burn the files to disc it will NOT be bootable as you will not have the boot image)
     
  9. 911medic

    911medic MDL Guru

    Aug 13, 2008
    5,777
    504
    180
    Using an ISO editor, you would just open the iso, add (change) the files, and save it. It remains bootable.

    I think you are making this much more difficult than it needs to be by dumping the files from the ISO. Using RyanVM tool is another good option for adding updates to the ISO and not needing to update for hours...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. l2p2c2

    l2p2c2 MDL Member

    Apr 23, 2010
    204
    225
    10
    Are you sure you need to copy the DPCDLL.DLL and Pidgen.dll files?
    I thought it was only needed to copy those if you change from volume to oem.
     
  11. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,557
    3,832
    120
    @l2p2c2
    You are right,

    Retail vs OEM = Same , Retail/OEM vs VLK = Different
     
  12. dumble

    dumble MDL Member

    Jan 17, 2009
    119
    21
    10
    #14 dumble, Mar 9, 2011
    Last edited: Mar 9, 2011
    (OP)
    Ok Thanks, I created the ISO with UltraISO, so its still bootable (and edited all the files like you & 911medic said). I also added the DPCDLL.DLL and Pidgen.dll files. Do I have to remove those again?
     
  13. 38956

    38956 MDL Member

    Jun 7, 2010
    130
    138
    10
    The Retail and OEM versions of pidgen.dll and DPCDLL.DLL are the same.

    The windows installation disc needs these files so don't remove them (you just don't need to replace them as they are the same)

    see FreeStyler post above
     
  14. dumble

    dumble MDL Member

    Jan 17, 2009
    119
    21
    10
    OK, 1 more question now then.

    I can now just install my custom version of XP, during the setup I have to enter the product key from the sticker on the back of the laptop and then it will be activated?
     
  15. urie

    urie Moderator
    Staff Member

    May 21, 2007
    9,039
    3,388
    300
  16. 38956

    38956 MDL Member

    Jun 7, 2010
    130
    138
    10
    #18 38956, Mar 10, 2011
    Last edited: Mar 10, 2011
    The Disc you made should pre-activate windows and you shouldn't need to enter the product key because it's in the answer file (winnt.sif)

    Open WinXPHome\i386\winnt.sif in notepad to see
    if you have burn it to disc or mount the iso image you're create Open E:\i386\winnt.sif in notepad (where E is the drive letter of you opitical [CD/DVD] drive)

    the link on urie's post is the script i posted which you have already done.
     
  17. dumble

    dumble MDL Member

    Jan 17, 2009
    119
    21
    10
    Yeah, I saw that. I installed it yesterday and it worked perfectly!

    Next time I will figure out how it works to slipstream more updates because after the install I still needed to do alot of windows updates. Anyway, its all working fine. And like you said there was no need of entering the key during the setup.

    Thanks for all the help!
     
  18. l2p2c2

    l2p2c2 MDL Member

    Apr 23, 2010
    204
    225
    10