OEMSCAN_ADDON_MULTIOEM v1.8 [Archive] - Siginet Software Forums

View Full Version : OEMSCAN_ADDON_MULTIOEM v1.8

Pages : [1] 2

mr_smartepants

01-21-2009, 01:53 PM

Updated 23 Mar 2011
This is a major update to my previous multioem addon. Like before, it is modular and expandable to your needs.
Significant script code improvements. Script now compiled into .exe with x86/x64 source compatibility and logging functionality! It also now has multiple checks and cross-checks to prevent misuse with pirated/tainted sources. I've tested extensively with legal OEM versions of x86 XP Home/Pro/MCE as well as x86 Server 2003 Standard and all activated flawlessly.
This will not activate any Retail or VLK sources! OEM SLP only.
This addon does NOT include any OEMBIOS.* files to keep the filesize down (although empty placeholders are included to show you where to place them). OEMBIOS files can be downloaded for your OEM systems from http://www.oembios.net or here (http://forums.mydigitallife.info/threads/9795-The-Windows-XP-OEMBIOS-Archive).
OEMBIOS filesets are different between XP and 2003, be sure you put the correct fileset in the right folders. XP OEMBIOS files go in the \FILESETS\XP\blah\ directories. 2003 server OEMBIOS files go in the \FILESETS\2003\blah\ directories.

Here's a quote from xehqter:
Windows XP and Windows 2003 OEMBIOS files use a different key to encrypt the data, file sets aren’t compatible.

This addon also does not include any SLP product keys, you must provide your own SLP key. Do NOT ask for us to give you a key as that is against forum rules and the law in some countries. In this addon, the SLP key is represented by the string 11111-22222-33333-44444-55555.

I've tried to simplify this addon so that the only files you need to edit are the oemscan.ini file for each OS type (Home, Pro, MCE, W2k3) to add your keys and add your OEMBIOS.* files...that's it!
This addon should be 100% compatible with single-disc as well as multi-OS/multi-boot PowerPacker integrations. This addon should also now be fully compatible with RIS network installs as well as USB install sources. You do NOT need to specify a product key in WINNT.SIF, in fact any key that is present will be overwritten if a matching OEMBIOS fileset is used on the PC. This addon does NOT use the $OEM$ directory, but uses the OEM directory instead to make it compatible with PowerPacker.

OK, to customize your multioem addon, start by downloading the addon from this post.
(in the below instructions, just substitute "Sony Corporation" with your OEM name.
1. Decompress the addon to your desktop or other working directory.
2. Download all of the OEMBIOS files you will need from http://www.oembios.net or here (http://forums.mydigitallife.info/threads/9795-The-Windows-XP-OEMBIOS-Archive) (eg. 376E13C7 for "Sony Corporation")
3. Gather your SLP keys (do NOT ask here for these!).
4. In the addon, go to the FILESETS folder and open the folder using the same name as listed on the OEMBIOS.net website (eg. \FILESETS\XP\376E13C7)
5. Add the four decompressed OEMBIOS.* (bin, sig, dat, cat) files you downloaded to the Sony folder you just made (XP filesets go in FILESETS\XP\*, 2003 filesets go in FILESETS\2003\*.)
6. (OPTIONAL) Add any OEM logo files to the \Logos\blah\ folders (check the "readme.txt" file in each folder. See the \Logos\AcerSystem\ folder for a good example of the proper layout. A few can be downloaded from here: http://www.oemlogos.siginetsoftware.com/
7. Open the oemscan.ini file in the appropriate OS type folder (IE. KEYS\XP\XP_HOME for Home) with Notepad and make the following changes:
8. In the .ini text, change the CMD function as so:

[Sony Corporation]
PATH="..\..\..\FILESETS\XP\376E13C7\"
CMD="SetKey 11111-22222-33333-44444-55555"
9. Change the fake SLP key with your legitimate one (remember, different OS types require different product keys so you can't use a XP Pro key to activate a XP Home install).
10. Save and close the oemscan.ini file.
11. Recompress the Entries_OEMScan_MULTIOEM.ini file and all the folders with 7zip into a single archive so that it has the filename OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MULTIOEM_1.8x.7 z.
12. Integrate this addon using Siginet's RVMIntegrator only. Do NOT use nLite.
13. Enjoy.

You can see in the oemscan.ini where I have different variations of Acer, Dell, and Gateway. You can use a similar approach for other OEM makes as well if I missed any.

Integration instructions
1. Start with a clean UNBRANDED OEM CD (MSDN-OEM or System Builder OEM discs will do).
2. Integrate your favorite updatepacks/addons with either nlite or RVMI, your choice.
3. In a separate session, integrate this addon with ONLY RVMI.
4. DriverPacks, if desired, go last.
5. Build ISO.

Known issues:
1) For best results, integrate this addon AFTER nLite and with RVMI and separately from any updatepack integration to ensure all files are edited properly.
nLite will not integrate this addon properly because of the unsupported [DirMove] section; unless a new version of nLite is released that supports that function.
Also, because this addon modifies i386\winnt.sif, and nLite will overwrite winnt.sif if found, it's vital to run this addon AFTER nLite to preserve the added sections.
2) This addon will make additional entries to winnt.sif.
The following lines are added to winnt.sif:
[Data]
AutoPartition=0
MsDosInitiated=0
UnattendedInstall="Yes"

Thanks go out to xehqter, FreeStyler and Siginet for providing both the tools and inspiration for this project (my wife hates you all ;) )
They made the tools, I just repackaged them into a more usable form.

Download info:
v1.8.7
'Empty' version Download (http://www.mediafire.com/file/bst7o6sxsq40th6/OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MULTIOEM_1.8.7_ empty.7z) (has none of the OEM logo files)
Updated: 23 Mar 2011
File: OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MULTIOEM_1.8.7_ empty.7z
CRC-32: 89984e4c
MD4: edb9e8a4eff41da74025b3223d94f27b
MD5: cb2228087d3e8f90fda943e4efac957f
SHA-1: bb60b246e77a1462e89dfb5c3fa63a51e529964f
Size: 571 KB

'Full' version Download (http://www.mediafire.com/file/ap2f2jdm6jx3kms/OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MULTIOEM_1.8.7. 7z) (has most of the OEM logo files preloaded).
Updated: 23 Mar 2011
File: OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MULTIOEM_1.8.7. 7z
CRC-32: db689220
MD4: ae899c3d16fa1fcc752b894d306dfec2
MD5: 334278682aad912a14a041f30f4bda29
SHA-1: f8a890c05ecdfca54d8ba9b7377c2aa2a91221a4
Size: 38 MB

Changelog

v1.8.2: The mtee utility was added in the 1.8.2 branch for logging ability.
v1.8.5: The 1.8.5 branch saw vast speed improvements in code optimization.
v1.8.6: The 1.8.6 branch fixes alternate install method detection (RIS, USB, etc.) in both the oemauto utility and the .ini winnt.sif entry (will detect the oemauto in either the install drive root or a sub-folder.)
v1.8.6.1: Fixed USB source detection (changes to both addon .ini and .exe). Added significant code to include alternate method of detecting version of Windows (not tested).
v1.8.6.2: Added code to detect both Tablet & MCE editions (user choice) and includes alternate method of detecting version of Windows from standalone environment (OEM folder must be at root of drive).
v1.8.6.3: Fixed bug that would cause the MCE/Tablet choice screen to always be displayed.
v1.8.6.4: Fixed bug that would cause the MCE/Tablet choice screen to get stuck in a loop if certain MCE files were present.
v1.8.6.5: Fixed bug that would cause the MCE/Tablet choice screen to fail. Added over-ride choices for alternate scan methods.
v1.8.6.6: Fixed all bugs. Added partial detection code for Windows Home Server v1. Released code as open-source project.
v1.8.7: Final version. Added support for foreign XP PIDs
The 1.8.7 branch is the best by far and the most stable (and also the last).

Below are tools to help extract files from a running system. Included are tools to "Grab files" like oembios filesets, drivers, keys, etc.
Mediafire mirror for "Grab files": http://www.mediafire.com/?xu7oz7woh44m7a5

Siginet

01-21-2009, 02:00 PM

Tell your wife I am sorry! :(

My wife hates all of you too! ;) LOL!

Glad you got this released... now I am gonna test the $h!t out of it. ;)

Woops... guess I got in here too soon. I don't see a link to it. ;)

mr_smartepants

01-21-2009, 02:03 PM

This will probably be my last version. I'm going to post the code in the 2nd post of this thread and make the whole project open-source.
I really don't have the time to develop this further. But someone else can take everything and run with it if they want to.
As far as I'm concerned, XP has had it's glory days. This utility has limited usefulness now.
Source code for OEMAUTO.exe version 1.8.7
Logging code by kof94

@echo off
:: This batch file was created by mr_smartepants
:: Version 1.8.7 17 Mar 2011
:: No copyright laws were broken in the creation of this utility
title= OEMBIOS Autodetection Utility by Mr_Smartepants
echo Detecting Windows installation source, please wait

: quick_check
if exist %CDROM%\OEM\OEMAUTO.EXE goto VARIABLES
: quick_set
SET CDROM=%~d0
if exist %CDROM%\OEM\OEMAUTO.EXE goto VARIABLES
: RIS_scan
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST "%%i:\$win_nt$.~ls" SET CDROM=%%i:\$win_nt$.~ls
if exist %CDROM%\OEM\OEMAUTO.EXE goto VARIABLES
: CD_scan
FOR %%i IN (Z Y X W V U T S R Q P O N M L K J I H G F E D) DO IF EXIST "%%i:\WIN51" SET CDROM=%%i:
if exist %CDROM%\OEM\OEMAUTO.EXE goto VARIABLES
: USB_scan
FOR %%i IN (Z Y X W V U T S R Q P O N M L K J I H G F E D) DO IF EXIST "%%i:\WINSETUP\OEM" SET CDROM=%%i:\WINSETUP
if exist %CDROM%\OEM\OEMAUTO.EXE goto VARIABLES
:: Below code does final check for install CD. If disc not found then exit with error.
: DEFINE-CD
if defined CDROM (
goto VARIABLES
) else (
echo Windows source files not found. 2>&1 | mtee /+ %logfile%
echo Please insert Windows CD and restart 2>&1 | mtee /+ %logfile%
goto ERROR
)

: VARIABLES
:: Set variables
path %PATH%;%CDROM%\OEM\bin
set logfile=%systemdrive%\oemscan.log
if exist %logfile% del /q %logfile%

SET METH=0
SET KEYS="%CDROM%\OEM\KEYS"
SET HOME="%KEYS%\XP\XP_HOME"
SET MCE="%KEYS%\XP\XP_MCE"
SET TAB="%KEYS%\XP\XP_TAB"
SET PRO="%KEYS%\XP\XP_PRO"
SET XP64="%KEYS%\XP\XP64"
SET DATACENTER="%KEYS%\2003\DATACENTER"
SET DATACENTER64="%KEYS%\2003\DATACENTER64"
SET ENTERPRISE="%KEYS%\2003\ENTERPRISE"
SET ENTERPRISE64="%KEYS%\2003\ENTERPRISE64"
SET STANDARD="%KEYS%\2003\STANDARD"
SET STANDARD64="%KEYS%\2003\STANDARD64"
SET WEB="%KEYS%\2003\WEB"
SET WHS="%KEYS%\2003\WHS"

: START
echo OEMBIOS autodetection script by Mr_Smartepants 2>&1 | mtee /+ %logfile%
echo v1.8.7 17 Mar 2011 2>&1 | mtee /+ %logfile%
echo Do NOT pirate Microsoft software 2>&1 | mtee /+ %logfile%
echo .
echo It YOUR responsibility to perform due-diligence 2>&1 | mtee /+ %logfile%
echo Be certain you are installing this OS on properly licensed OEM hardware 2>&1 | mtee /+ %logfile%
echo Verify the OS type with the Certificate of Authenticity attached to this PC 2>&1 | mtee /+ %logfile%
echo .
echo Mr_Smartepants or SiginetSoftware will NOT be held legally liable 2>&1 | mtee /+ %logfile%
echo if YOU violate any copyright law by installing this OS on an unlicensed PC 2>&1 | mtee /+ %logfile%
echo No copyright laws were broken in the creation of this utility 2>&1 | mtee /+ %logfile%

: DOSPATH
:: Find install path and set variable
setLocal EnableDelayedExpansion
if exist %systemroot%\system32\$winnt$.inf (
FOR /F "skip=2 usebackq" %%a IN (`FIND "dospath" %SystemRoot%\SYSTEM32\$WINNT$.INF`) DO (
set str=%%a
for /f "tokens=2 delims==" %%a in ('echo !str!') do (
set dospath=%%a
echo Install-Path=!dospath! 2>&1 | mtee /+ %logfile%
)
:: The below is not really used for anything but user feedback
for /f "skip=2 delims=\ usebackq" %%a in ('echo !str!') do (
set drivepath=%%a
echo Drive-Path=!drivepath! 2>&1 | mtee /+ %logfile%
))
) else (
echo Error: `%systemroot%\system32\$winnt$.inf' file not found 2>&1 | mtee /+ %logfile%
echo Beginning alternate scan method... 2>&1 | mtee /+ %logfile%
goto EULAID
)

: ARCH
for %%a in (I386 AMD64) do if exist "%dospath%\%%a" set arch=%%a
if '%arch%'=='' (
echo Error: Windows installation directory not found 2>&1 | mtee /+ %logfile%
echo Beginning alternate scan method... 2>&1 | mtee /+ %logfile%
goto EULAID
) else (
echo ARCH=!arch! 2>&1 | mtee /+ %logfile%
)
SET METH=1

: PID
if exist %dospath%\%arch%\SETUPP.INI (
for /f "tokens=2 delims==" %%a in (%dospath%\%arch%\SETUPP.INI) do (
set pid=%%a
echo PID=!pid! 2>&1 | mtee /+ %logfile%
)
) else (
echo Error: `%dospath%\%arch%\SETUPP.INI' file not found 2>&1 | mtee /+ %logfile%
echo Beginning alternate scan method... 2>&1 | mtee /+ %logfile%
goto EULAID
)

: OEM
if not '%pid:~-3%'=='OEM' (
echo Error: Incorrect Windows type detected 2>&1 | mtee /+ %logfile%
echo Error: This utility only works with OEM Windows 2>&1 | mtee /+ %logfile%
goto ERROR
)

: Version
set version=%pid:~0,5%
:: Windows XP Professional / MCE
for %%a in (76481 76500 76392 76396 76413 76487 76440 76447 55375 55679 55274 55276 55285 55661 55639 76497
) do if '%version%'=='%%a' goto MCE-TEST
:: Windows XP Home Edition
for %%a in (76477 76475 76470 76460 76412 76381 55372 55373 55677 55277 76416 76434
) do if '%version%'=='%%a' goto HOME
:: Windows XP Professional x64
for %%a in (55034 76588
) do if '%version%'=='%%a' goto XP64
:: Windows Server 2003
if '%version%'=='69712' goto STANDARD
if '%version%'=='69713' goto ENTERPRISE
if '%version%'=='69754' goto DATACENTER
if '%version%'=='69753' goto WEB
:: Windows Server 2003 x64
if '%version%'=='69770' goto ENTERPRISE64
if '%version%'=='69769' goto DATACENTER64
:: Windows Home Server
if '%version%'=='78495' goto WHS
echo Error: Failed to identify Windows PID 2>&1 | mtee /+ %logfile%
goto ERROR2

: MCE-TEST
SET VERSION1=TAB
SET VERSION2=MCE
if exist %dospath%\CMPNENTS\TABLETPC\I386\TABLETPC.CAB set VERSION1=YES
if exist %dospath%\CMPNENTS\MEDIACTR\I386\MEDIACTR.CAB set VERSION2=YES
if '%VERSION1%'=='%VERSION2%' goto ASK

: MCE1
::SET VERSION2=MCE
::if '%VERSIONX%'=='%VERSION2%' goto MCE2
if not exist %dospath%\CMPNENTS\MEDIACTR\I386\MEDIACTR.CAB goto TAB

: MCE2
echo Windows XP Media Center Edition detected 2>&1 | mtee /+ %logfile%
ECHO Scanning for matching XP MCE BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
%MCE%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO OEMcopy

:::MCE2
::if '%VERSIONX%'== MCE goto MCE2a
::if not exist %dospath%\I386\EHOCGEN.DL_ goto TAB
:::MCE2a
::GOTO MCE1

: TAB
::SET VERSION1=TAB
::if '%VERSIONX%'=='%VERSION1%' goto TAB2
if not exist %dospath%\CMPNENTS\TABLETPC\I386\TABLETPC.CAB goto PRO

: TAB2
::if not exist %systemroot%\system32\TABLETPC.CPL goto PRO
echo Windows XP Tablet Edition detected 2>&1 | mtee /+ %logfile%
ECHO Scanning for matching XP Tablet BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
%TAB%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO OEMcopy

: PRO
if '%VERSIONX%'== PRO goto PRO2
if not exist %dospath%\win51ip goto ERROR3
: PRO2
echo Windows XP Professional Edition detected 2>&1 | mtee /+ %logfile%
ECHO Scanning for matching XP Pro BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
%PRO%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO OEMcopy

: HOME
if '%VERSIONX%'== HOM goto HOM2
if not exist %dospath%\win51ic goto ERROR3
: HOM2
echo Windows XP Home Edition detected 2>&1 | mtee /+ %logfile%
ECHO Scanning for matching XP Home BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
%HOME%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO OEMcopy

: STANDARD
if '%VER3%'== STD goto STANDARD2
if '%VER3b%'== ENT goto STANDARD2
if not exist %dospath%\win51is goto STANDARD64
: STANDARD2
echo Windows Server 2003 Standard Edition detected 2>&1 | mtee /+ %logfile%
ECHO Scanning for matching Server 2003 STANDARD BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
%STANDARD%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO OEMcopy

: STANDARD64
if not exist %dospath%\win51as goto ERROR3
echo Windows Server 2003 Standard x64 Edition detected 2>&1 | mtee /+ %logfile%
ECHO Scanning for matching Server 2003 STANDARD x64 BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
%STANDARD64%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO OEMcopy

: ENTERPRISE
if not exist %dospath%\win51ia goto ERROR3
echo Windows Server 2003 Enterprise Edition detected 2>&1 | mtee /+ %logfile%
ECHO Scanning for matching Server 2003 ENTERPRISE BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
%ENTERPRISE%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO OEMcopy

: ENTERPRISE64
if not exist %dospath%\win51aa goto ERROR3
echo Windows Server 2003 Enterprise x64 Edition detected 2>&1 | mtee /+ %logfile%
ECHO Scanning for matching Server 2003 ENTERPRISE x64 BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
%ENTERPRISE64%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO OEMcopy

: WEB
if not exist %dospath%\win51ib goto ERROR3
echo Windows Server 2003 Web Edition detected 2>&1 | mtee /+ %logfile%
ECHO Scanning for matching Server 2003 WEB BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
%WEB%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO OEMcopy

: DATACENTER
if not exist %dospath%\win51id goto ERROR3
echo Windows Server 2003 Datacenter Edition detected 2>&1 | mtee /+ %logfile%
ECHO Scanning for matching Server 2003 DATACENTER BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
%DATACENTER%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO OEMcopy

: DATACENTER64
if not exist %dospath%\win51ad goto ERROR3
ECHO Windows Server 2003 Datacenter x64 Edition detected 2>&1 | mtee /+ %logfile%
ECHO Scanning for matching Server 2003 DATACENTER BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
%DATACENTER64%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO OEMcopy

: WHS
if not exist %dospath%\win51il goto ERROR3
echo Windows Home Server detected 2>&1 | mtee /+ %logfile%
ECHO This version is not yet supported. 2>&1 | mtee /+ %logfile%
::ECHO Scanning for matching Server 2003 WEB BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
::%WHS%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO ERROR

: XP64
if '%VER3b%'== X64 goto XP64a
if not exist %dospath%\win51ap goto ERROR3
: XP64a
echo Windows XP Professional x64 version detected 2>&1 | mtee /+ %logfile%
ECHO Scanning for matching XP Pro x64 BIOS string and writing product key. 2>&1 | mtee /+ %logfile%
%XP64%\oemscan.exe 2>&1 | mtee /+ %logfile%
GOTO OEMcopy

: OEMcopy
:: This will scan oemscan.log for the OEM name, then match that name to the logos folder and set the variable.
:: Then copy all the files from that folder to their appropriate folders on the system drive.

endLocal
setLocal EnableDelayedExpansion

if not exist %logfile% goto ERROR4
echo Found oemscan log file

for /f "tokens=* delims= " %%b in (%logfile%) do (
echo %%b | find "Matched: " > nul
if not errorlevel 1 set str=%%b
)
for /f "tokens=1,2 delims= " %%b in ('echo !str!') do (
set oemvar=%%b
set OEMtype=%%c
echo OEMtype=!OEMtype!
)
set oemcopy="%CDROM%\OEM\Logos\%OEMtype%"
if not exist "%oemcopy%\*" goto ERROR5

echo Attempting to move OEM logo files from !oemcopy! 2>&1 | mtee /+ %logfile%
copy "%oemcopy%\*.ico" "%SystemRoot%\System32\*"
copy "%oemcopy%\oemlogo.bmp" "%SystemRoot%\System32\*"
copy "%oemcopy%\oeminfo.ini" "%SystemRoot%\System32\*"
copy "%oemcopy%\oobe\oobeinfo.ini" "%SystemRoot%\system32\oobe\*"
copy "%oemcopy%\oobe\oemeula.txt" "%SystemRoot%\System32\oobe\*"
copy "%oemcopy%\oobe\OEMLOGO*.*" "%SystemRoot%\system32\oobe\images\*"
MD "%SystemRoot%\Resources\Themes"
copy "%oemcopy%\themes\*" "%SystemRoot%\Resources\Themes\*"
MD "%SystemRoot%\Web\Wallpaper"
copy "%oemcopy%\walls\*" "%SystemRoot%\Web\Wallpaper\*"

ECHO Successfully activated using Method %METH% 2>&1 | mtee /+ %logfile%

: END
endLocal
EXIT

:: Numbered error codes follow for troubleshooting.
: ERROR
echo Script completed with errors. Logfile can be found in %systemdrive%\oemscan.log. 2>&1 | mtee /+ %logfile%
echo Please report errors to Mr_Smartepants. 2>&1 | mtee /+ %logfile%
echo Pirates need not bother asking for help, ye won't get any! Scurvy-Dogs. 2>&1 | mtee /+ %logfile%
echo http://siginetsoftware.com/forum/showthread.php?t=541 2>&1 | mtee /+ %logfile%
echo Post your oemscan.log file to the above forum with a summary of the problem. 2>&1 | mtee /+ %logfile%
pause
GOTO END

: ERROR1
echo "Error#1. OEMSCAN cannot continue. OEM version of Windows NOT detected." 2>&1 | mtee /+ %logfile%
goto ERROR

: ERROR2
echo "Error#2. OEMSCAN cannot continue. Could not find suitable SLP Product ID" 2>&1 | mtee /+ %logfile%
echo "This appears to be a pirated copy of Microsoft Windows" 2>&1 | mtee /+ %logfile%
GOTO ERROR

: ERROR3
echo "Error#3. Mismatch of PID# with disc ID. Unable to continue" 2>&1 | mtee /+ %logfile%
echo "This appears to be a pirated copy of Microsoft Windows" 2>&1 | mtee /+ %logfile%
GOTO ERROR

: ERROR4
echo "Error#4. OEM Logo copy failed. Could not find oemscan.log" 2>&1 | mtee /+ %logfile%
GOTO ERROR

:ERROR5
echo "Error#5. OEM Logo copy failed. Could not find any OEM logo files in" 2>&1 | mtee /+ %logfile%
ECHO !oemcopy! 2>&1 | mtee /+ %logfile%
GOTO ERROR

: ASK
color 06
cls
echo.
echo.
echo ************************************************** *******************
echo Both Tablet and Media Center detected
echo ************************************************** *******************
echo.
echo.
echo What would you like to do?
echo.
echo 1...Install XP Tablet Edition
echo.
echo 2...Install XP Media Center Edition
echo.
echo 3...Scan using alternative method
echo.
echo 4...Scan using 2nd alternative method
echo.
echo.
set /p option="Enter Option (1-4) "

IF %option%==1 set VERSIONX=TAB & GOTO TAB
IF %option%==2 set VERSIONX=MCE & GOTO MCE1
If %option%==3 GOTO EULAID
If %option%==4 GOTO OS-check
GOTO CONT

::ALTERNATE_METHOD_2
: EULAID
if not exist "%systemroot%\SYSTEM32\EULA.TXT" goto OS-check
SET METH=2
CLS
ECHO Beginning alternate detection method #2... 2>&1 | mtee /+ %logfile%
ECHO This method is NOT accurate, but I'll try my best.
ECHO Detecting Product ID (PID) by scanning EULA.txt... 2>&1 | mtee /+ %logfile%
FOR /F "skip=2 usebackq" %%a IN (`FIND "EULAID" %systemroot%\SYSTEM32\EULA.TXT`) DO SET EULAID=%%a
ECHO Found EULAID: %EULAID% 2>&1 | mtee /+ %logfile%
FOR /F "tokens=1,3,4 delims=_" %%a IN ("%EULAID:~7%") DO SET OS=%%a & SET VERSIONX=%%b & SET CHANNEL=%%c
ECHO %OS% 2>&1 | mtee /+ %logfile%
ECHO %VERSIONX% 2>&1 | mtee /+ %logfile%
ECHO %CHANNEL% 2>&1 | mtee /+ %logfile%

::EULAID OEM check
IF NOT %CHANNEL% == OEM goto ERROR1

::Prepare system files for replacement
attrib -s %systemroot%\system32\oembios.sig
attrib -s %systemroot%\system32\oembios.dat
attrib -s %systemroot%\system32\oembios.bin
attrib -s %SystemRoot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\OEMBIOS.CAT

::EULAID OS check
:: Windows XP Check
set OS2=%OS:~0,2%
for %%a in (MC) do if '%OS2%'=='%%a' goto MCE-TEST
for %%a in (XP WX) do if '%OS2%'=='%%a' goto XPVersionCheck
:: Windows Server 2003 Check
set OS4=%OS:~0,4%
for %%a in (WS03) do if '%OS4%'=='%%a' goto 2K3VersionCheck

echo Error: Failed to identify Windows using alternate method 2>&1 | mtee /+ %logfile%
goto ERROR2

::EULAID Version Check
: XPVersionCheck
:: Windows XP Professional / MCE
for %%a in (PRO MCE) do if '%VERSIONX%'=='%%a' goto MCE-TEST
:: Windows XP Home Edition
if '%VERSIONX%'== HOM goto HOME

echo Error: Failed to identify Windows PID using alternate method #2 2>&1 | mtee /+ %logfile%
goto ERROR2

: 2K3VersionCheck
set VER3=%VERSIONX:~0,3%
set VER3b=%VERSIONX:~-3%
:: Windows Server 2003
if '%VER3%'== STD goto STANDARD
if '%VER3b%'== ENT goto STANDARD
if '%VER3b%'== X64 goto XP64

echo Error: Failed to identify Windows PID using alternate method #2 2>&1 | mtee /+ %logfile%
goto ERROR2

::ALTERNATE_METHOD_3

: OS-check
CLS
ECHO Beginning alternate detection method #3...
ECHO Detecting Product ID (PID) by scanning registry... 2>&1 | mtee /+ %logfile%
::FOR /F "tokens=2*" %%A IN ('REG QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v ProductId') DO SET pid=%%B
::FOR /F "tokens=3 delims= " %%A IN ('REG QUERY "HKLM\SYSTEM\Setup\Pid" /v Pid') DO SET pid=%%A
FOR /F "tokens=2*" %%A IN ('REG QUERY "HKLM\SYSTEM\Setup\Pid" /v Pid') DO SET pid=%%B
echo PID=!pid! 2>&1 | mtee /+ %logfile%
if not errorlevel 1 (
SET METH=3
::Prepare system files for replacement
attrib -s %systemroot%\system32\oembios.sig
attrib -s %systemroot%\system32\oembios.dat
attrib -s %systemroot%\system32\oembios.bin
attrib -s %SystemRoot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\OEMBIOS.CAT
goto OEM
) else (
echo Error: Failed to identify Windows PID using alternate method #3 2>&1 | mtee /+ %logfile%
goto ERROR2
)

: EOF

I release this code under the Creative Commons license (http://creativecommons.org/licenses/by/3.0/) with the understanding that it will NOT be used for warez or other illegal purposes.

To quote Linus Torvalds: "Given enough eyeballs, all bugs are shallow".

Siginet

01-21-2009, 02:26 PM

OK... I took a quick lookover. Let's say I create a Multiboot 2k3 disk with Standard, Enterprise, and Web editions. Is it possible to use this? I don't see a way to add different product keys for all of them?

mr_smartepants

01-21-2009, 09:38 PM

SSX4life

01-22-2009, 08:13 AM

Something isn't right here, I can not install windows after slipstreaming you pack with RVM Intergrator.

Log

2009-01-22_09.54.01
Log Startup @ 09:54:01 On January 22, 2009

Running OS: WIN_XP Service Pack 3 X86
RVMIntegrator v1.5.3

"C:\Documents and Settings\Administrator\Desktop\RVM_Integrator_1.5. 3\RVM_Integrator_1.5.3.exe"

09:54:01 - Windows XP Professional - OEM SP2 Found
09:54:04 -
09:54:04 - Source Drive = C:\Documents and Settings\Administrator\Desktop\iso's\Windows XP Professional (OEM)
09:54:04 - Destination Drive = C:\Documents and Settings\Administrator\Desktop\iso's\Windows XP Professional (OEM)
09:54:04 - Destination Size = 252.75 GB
09:54:04 - Working Directory = C:\Documents and Settings\Administrator\Desktop\iso's\Windows XP Professional (OEM)\I386
09:54:04 - Temp Directory = C:\Documents and Settings\Administrator\Desktop\iso's\Windows XP Professional (OEM)\I386\rvmtemp
09:54:04 -
09:54:04 - Starting Integration
09:54:04 -
09:54:04 - Checking Destination For OS Type.
09:54:04 - Windows XP Professional - OEM SP2 Found
09:54:04 -
09:54:05 - Extracting OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MULTIOEM_1.8.7z
09:55:27 - MD5 Hash = 210BC6BF2965DE45CA64E83EE02093B9
09:55:27 - Clearing any Read Only Attributes.
09:55:27 -
09:55:27 - Gathering temp files
09:55:28 - Processing new .CAT files found in SVCPACK
09:55:28 -
09:55:28 - Shifting Stuff Around
09:55:28 - 199 Files Moved in 0 Seconds
09:55:28 - Analyzing 1 Entry Files
09:55:28 - Processing OEMSCAN 1.4.1 Addon for multi-system installs v1.8/mr_smartepants Build Date: 2009/01/20
09:55:28 - Gathering [DirMove] Entries
09:55:28 -
09:55:28 - Prepairing System Files...
09:55:28 - sysoc.inf
09:55:28 - svcpack.inf
09:55:28 - dosnet.inf
09:55:28 - txtsetup.sif
09:55:32 -
09:55:32 - Processing Sysoc.inf
09:55:32 - Processing svcpack.inf
09:55:32 - Processing dosnet.inf
09:55:32 - Processing txtsetup.sif
09:55:33 -
09:55:33 - Compressing Files ASMS...
09:55:39 -
09:55:39 - Processing [EditFile]
09:55:39 -
09:55:39 - Moving Files Found In OEMSCAN 1.4.1 Addon for multi-system installs
09:55:39 - Moving Directories
09:55:49 - Entire .ini Processing Completed in 20 Seconds
09:55:49 -
09:55:49 - Compressing and Moving Edited Files
09:55:49 - Cleaning Up.
09:55:49 - Integration Completed.
09:55:49 - Total Integration Time = 105 Seconds
09:55:49 - ================================================== ================================
09:55:49 -

Log Shutdown @ 09:55:50 On 22-01-2009

Here is the error I get - *see attachment*

I have been running into this recently and I don't know why.

XP Pro SP2 intergrated (untouched otherwise)
OEMSCAN 1.4.1 Addon (just modified the .ini files for proper slp keys and added oembios files)

Any ideas?

mr_smartepants

01-22-2009, 08:37 AM

Wow, that's a new one on me. Looks to me like your source is borked.
What is your OEM source? Is it from an OEM distributor like Dell/HP/etc with it's own $OEM$ & OEM folders? Or is it a clean system-builder OEM disc?
Can you post the contents of your \i386\setupp.ini & winnt.sif files?
The oemscan.cmd file isn't even launching which makes me suspect something else.
So you take this disc and ONLY integrate my addon? No updatepacks, no nlite tweaks?

*Edit
Crap, I found a bug in the entries.ini that Siginet referenced above. The Win2k3 directories don't get copied by RVMI. The fault only affects Win2k3 integrations.

SSX4life

01-22-2009, 09:20 AM

It's a clean install with a fresh oem source that has SP2 slipstreamed (not from dell / hp / etc.).

I have an .md5 and .sfv of the .iso I am using.

Here is the setupp.ini and winnt.sif (I had to zip the .sif)

I typically modify my winnt.sif file extensivly but due to the errors I have been running without it.

Let me delete my .iso's and re verify them on my box.

SSX4life

01-22-2009, 10:08 AM

Both .iso's were verified to be complete. I am trying again from scratch to see if it was a fluke.

1. Re-downloaded the latest .7z of oemscan
2. Reimported the XPH / XPP / XPMCE .ini's that include the SLP Keys
3. Reinserted the oembios files
4. Inserted oemlogo.bmp / oeminfo.ini to the proper folders
5. Re-zipped the files with .7z
6. Ran RVM_Integrator_1.5.3
7. Did not run any update pack / modifications / etc (it's straight SP2 slipstreamed... trying to remove possible problems)
8. Ran the .7z of oemscan
9. Made .iso
10. Threw the .iso into VMware and got the same error message! >_<

I did some digging and ran into this - http://support.microsoft.com/kb/238835

I'm gonna try to add that data tag and see what I get

SSX4life

01-22-2009, 11:25 AM

Yup that was the problem ^_^

I also noticed your script removes the previous winnt.sif file in place. Not sure if this was intended but it was just my experience.

Here is my final Winnt.sif

;SetupMgrTag
[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"
AutomaticUpdates=yes

[Unattended]
UnattendMode=ProvideDefault
OemSkipEula=No
OemPreinstall=No
TargetPath=\WINDOWS
WaitForReboot="No"
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore

[GuiUnattended]
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=20
DetachedProgram = CMD.EXE
Arguments="/Q /C FOR /F %? IN ('%SYSTEMROOT%\SYSTEM32\MOUNTVOL.EXE^|FINDSTR :\') DO IF EXIST %?WIN51 START %?.\OEM\OEMSCAN.CMD"

[UserData]
FullName=""
OrgName=""

[Display]
Xresolution=1024
YResolution=768

[Identification]
JoinWorkgroup=MSHOME

[Networking]
InstallDefaultComponents=Yes

[Components]
msmsgs=off
msnexplr=off
zonegames=off

Thanks for all the hard work on this, I think we have reached a nice completed script that does just about everything you can think of. The only other thing that needs to be done is make a Tablet version of this (I don't think you can do a multioem, so we may need to modify the pre-existing 1.4 model to run on tablet. I've gotten it to work with 1.4 and a custom winnt.sif call file.

I'll let you know how it goes ^_^

mr_smartepants

01-22-2009, 11:58 AM

I also noticed your script removes the previous winnt.sif file in place.
That should not be happening. The addon should only ADD the entries to winnt.sif. I've never had the addon replace the entire file.

I also had not anticipated someone using ONLY the addon. The article you referenced was for win2000 but I believe it still applies to XP. I'm not sure if adding an empty [data] flag will cause more problems than it solves.
I'll have to think about this more. I'm sure the RVMI has an option to add flags if and only if those flags do not exist. Siginet, is that possible?

The winnt.sif file must have at a minimum the following entries:
# UnattendedInstall=Yes - Value must be set to "yes"
# MSDosInitiated=No - Value must be set to "no" or Setup stops during the graphical portion of Setup
# AutoPartition=1 or 0 - If the value is set to 1, the installation partition is automatically selected. If the value is set to 0 (zero), you are prompted for the installation partition during the text portion of Setup.

SSX4life

01-22-2009, 12:51 PM

All I know is that the XP Setup is working properly with the winnt.sif file I am running now (that includes your edition). If you take a base XP disk with no modifications and run the oemscan.7z script it will either replace the file or it will only add

[GuiUnattended]
DetachedProgram = CMD.EXE
Arguments="/Q /C FOR /F %? IN ('%SYSTEMROOT%\SYSTEM32\MOUNTVOL.EXE^|FINDSTR :\') DO IF EXIST %?WIN51 START %?.\OEM\OEMSCAN.CMD"

Siginet

01-22-2009, 02:03 PM

It shouldn't replace winnt.sif. It would be best to test using the latest Beta of the integrator. There may be a flaw in 1.5.3 that is causing this. But I am not positive. Let me know. ;)

SSX4life

01-22-2009, 02:25 PM

I'll do a test compare after work today between 1.5.3 and the beta.

Also.... the oemlogo's did not load for my dell....at least not automatically, I had to insert them into the system32 directory. They oemscan.log file was absent from the %system%\temp folder as well so I had no way of telling what went wrong.

mr_smartepants

01-22-2009, 09:34 PM

The oemscan.log file was absent from the %system%\temp folder as well so I had no way of telling what went wrong.

Well, the batch uses oemscan.log to figure out which files to put where. If the log isn't being created, that would cause the logo file copy to fail for sure.
Can you add a 'PAUSE' immediately prior to 'END' in the oemscan.cmd file? That will hold the window open so you can see what happened up until around T-34 (when the video driver loads and the screen blanks). I need to know what error is given and where it's failing. I'm tempted to add error#'s to the batch so this would be easier.

SSX4life

01-23-2009, 06:38 AM

I was actually going to suggest adding a pause to the final version of your scripts. This way you see exactly what is being inserted.

SSX4life

01-23-2009, 08:39 AM

I decided to do a full capture of my xp pro oem install via vmware for you (see attached video). I sped the capture up by 400X to save time and compressed it down with xvid coded from 120mb to 4mb or so.

I also manually ran oemscan.cmd from my D: drive and here is the error message I got.

Detecting Windows XP type, please wait
dospath=D:\
WinXP OEM version detected
myvar=76487OEM
finalvar=76487
WinXP Pro version detected
Scanning for matching Pro OEMBIOS string
Found oemscan log file
OEMtype=Dell System
Attempting to move OEM logo files from
"D:\OEM\Logos\Dell System"
The syntax of the command is incorrect.
The syntax of the command is incorrect.
The syntax of the command is incorrect.
The syntax of the command is incorrect.
The syntax of the command is incorrect.
The syntax of the command is incorrect.
A subdirectory or file C:\WINDOWS\Web\Wallpaper already exists.
The syntax of the command is incorrect.
Press any key to continue . . .

I added a pause at the end of the script so I could view it. Something about a bad syntax.... /dunno

Hope it helps, let me know if there is any other testing I can do.

mr_smartepants

01-23-2009, 10:50 AM

OK, cool. Now I know where the failure lies. See, none of my notebooks have spaces in their detected names. I thought I had planned for this problem, but I got the tokens= syntax wrong. I was trying to lump all the Dell systems together with a single 'Dell' folder and the batch should have ignored the space, but didn't.
I'll fix the batch and add error #s for better future troubleshooting.

BTW, how are you capturing the video?

SSX4life

01-23-2009, 11:24 AM

In VM Ware it has a built in detection and capture tool that exports to a raw AVI file. ^_^ check the link*edit* Sigi.... WHY can't we upload .avi? /boggle

I also have Snagit 9 professional, it's another really helpful tool for capture as well, especially when doing walkthoughs

mr_smartepants

01-23-2009, 12:27 PM

I'm doing some tests of my own now with the new batch script just to make sure I didn't do something stupid. :p
Once it passes, I'll upload the new addon.

SSX4life

01-23-2009, 12:53 PM

May I make the suggestion of including all of the oemlogo.bmp / oeminfo.ini files in the final release? What is 500kb total in the long run anyway, we all have high speed internet here.

mr_smartepants

01-23-2009, 01:04 PM

Well, the logos I have are over 24MB (compressed) on their own.
Maybe in a future release.
1.8.02 online.
Changes from 1.8.01
Fixed OEM logo file copy from non-existent folder. All OEM logo folders have zero spaces. (ie, "Dell System" and "Dell Inc" will all match to the "Dell" OEM logo folder.)

SSX4life

01-23-2009, 01:29 PM

24 MB with themes and wallpapers included? I kinda meant just the logo's.

mr_smartepants

01-24-2009, 06:40 AM

May I make the suggestion of including all of the oemlogo.bmp / oeminfo.ini files in the final release?
1.8.03 is online now. I fixed one bug with 1.8.02 but broke something. It's now fixed, AND includes the OEMINFO.INI & OEMLOGO.BMP files for the OEMs I had. Not all folders are populated.

SSX4life

01-24-2009, 07:52 AM

here is a winnt.sif file that your addon created.

[GuiUnattended]
DetachedProgram = CMD.EXE
Arguments="/Q /C FOR /F %? IN ('%SYSTEMROOT%\SYSTEM32\MOUNTVOL.EXE^|FINDSTR :\') DO IF EXIST %?WIN51 START %?.\OEM\OEMSCAN.CMD"

It does not include the [data] tag or other needed information.

Here is my finalized winnt.sif file

;SetupMgrTag
[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"
AutomaticUpdates=yes

[Unattended]
UnattendMode=ProvideDefault
OemSkipEula=No
OemPreinstall=No
TargetPath=\WINDOWS
WaitForReboot="No"
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore

[GuiUnattended]
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=20
DetachedProgram = CMD.EXE
Arguments="/Q /C FOR /F %? IN ('%SYSTEMROOT%\SYSTEM32\MOUNTVOL.EXE^|FINDSTR :\') DO IF EXIST %?WIN51 START %?.\OEM\OEMSCAN.CMD"

[UserData]
FullName=""
OrgName=""

[Display]
Xresolution=1024
YResolution=768

[Identification]
JoinWorkgroup=MSHOME

[Networking]
InstallDefaultComponents=Yes

[Components]
msmsgs=off
msnexplr=off
zonegames=off

So the addon works great ^_^, just need to inform people to modify the associated file or you get that error message.

mr_smartepants

01-24-2009, 07:59 AM

I'm really hesitant to add these entries to winnt.sif
[Data]
AutoPartition=0
MsDosInitiated="0"
UnattendedInstall="Yes"
AutomaticUpdates=yes

I don't want to add them because not everyone will want them.
I also don't want to add them because I'm not sure how the RVMI will handle the additional entries without hearing from Siginet first.
I will add a note to the first post as a caution though.

SSX4life

01-24-2009, 09:05 AM

I understand being hesitant on that one. At least let ppl know they will need to modify the file prior to packaging the .iso and installing.

Siginet

01-24-2009, 09:53 AM

mr_smartepants

01-24-2009, 10:27 AM

Hmmm that is a difficult call to make. So you guys say that these OEMScan addons must have those changes to winnt.sif to work? Even the AutomaticUpdates?

Well, from the documentation I've read, a WINNT.SIF file is not considered valid unless it has at least these three lines as a minimum:
[Data]
AutoPartition=
MsDosInitiated=
UnattendedInstall=

But the problem is if you have the UnattendedInstall="Yes" entry, then you don't get the option of a 'repair' install (IIRC).

I just don't want to preload an addon with choices that should be made by the user.
(Except AutoUpdates, because that should always be on anyway).

Siginet

01-24-2009, 12:20 PM

I think in an upcomming release of the integrator we may need to concentrate on a simple part of the gui for selecting unattended options for winnt.sif. I think it would be a fairly simple thing to do. I have put it off for a long time now.

I'm thinking... if these addons do not work without those options in winnt.sif then maybe it wouldn't be a bad idea to do it. As it is users will need to repackage the addons once they place thie oembios files into them and also put product key info as well. So if a user does not wish to use the same options that are in the addon as default then they can simply edit the entries file with the correct information. I think it would be a good idea to add comments into the entries file explaining what each section is and what changes they should make, plus state which sections are optional to change and so on. ;)

mr_smartepants

01-24-2009, 12:30 PM

OK, I'll get to work adding those entries and making the appropriate comments in the .ini as instructions. I'll update/upload when I can (not for a few days anyway), but 1.8.03 will be it unless something else is broken.
Can someone verify the "name(space)name" problem has been solved?

SSX4life

01-24-2009, 05:23 PM

Can someone verify the "name(space)name" problem has been solved?

Working on it ^_^

user_hidden

01-24-2009, 06:12 PM

You're partially correct. For now, there is a single w2k3 oemscan.ini to house the keys.
I used the w2k3 PIDs id'd on this site: http://wiki.lunarsoft.net/wiki/Product_IDs
I could only find 4 disc identifiers for w2k3 (from the discs in my possession and from the web).
%CDROM%\win51aa
%CDROM%\win51ia
%CDROM%\win51ib
%CDROM%\win51is

Are there different keys between the subversions? (standard/enterprise/etc)?
This is easily corrected in the batchfile by adding more discriminators but I need info on each version (setupp.ini PID/disc id).

Windows 2003 STANDARD

[Pid]
ExtraData=786F687170637175716954806365EF
Pid=69712OEM

Windows 2003 ENTERPRISE

[Pid]
ExtraData=786F687170637175716954806365EF
Pid=69713OEM

standard and enterprise use different keys.
the DELL editions use CRC=C20D8FF5 for the OEMBIOS files

hopfully OemScan can be updated for the different versions.
sorry i don't have any info on the WEB version.

i think also that Windows Home Server has OEM for IBM / Dell / Compaq / HP.
they use the regular OEMBIOS files as XP but of course different SLP key.
would be great if there was a scan for that OS as well.
i unfortunately have none of the PID or DiscID info data.

mr_smartepants

01-24-2009, 11:46 PM

standard and enterprise use different keys.
sorry i don't have any info on the WEB version.
Thanks for confirming this. I'll have to change the layout of the addon to compensate.
Can you also verify the disc identifiers for each version?
%CDROM%\win51aa
%CDROM%\win51ia
%CDROM%\win51ib
%CDROM%\win51is

i think also that Windows Home Server has OEM for IBM / Dell / Compaq / HP.
they use the regular OEMBIOS files as XP but of course different SLP key.
That can't possibly be correct.:o I thought WHS uses a Server 2008 core and uses cert files matched with SLP2 keys (IIRC). OEMSCAN doesn't work with Vista/Server2008 certs.

mr_smartepants

01-25-2009, 04:24 AM

Updated to 1.8.04.
Changed folder layout to the following:
-OEM
--Key_2003 (Separate your keys for each subversion)
---DATACENTER
---ENTERPRISE
---STANDARD
---WEB
--Key_XP (Separate your keys for each subversion)
---XP_HOME
---XP_MCE
---XP_PRO
--Logos
---(various)
--OEMBIOS3 (Windows Server 2003 OEMBIOS filesets)
---(various)
--OEMBIOSX (Windows XP OEMBIOS filesets)
---(various)

user_hidden

01-25-2009, 06:01 AM

Can you also verify the disc identifiers for each version?
%CDROM%\win51aa
%CDROM%\win51ia
%CDROM%\win51ib
%CDROM%\win51is

That can't possibly be correct.:o I thought WHS uses a Server 2008 core and uses cert files matched with SLP2 keys (IIRC). OEMSCAN doesn't work with Vista/Server2008 certs.

it was late last night when i added the WHS stuff. you are correct that it uses vista cert. it was a looooong day yesterday.

WIN51IS: Win2k3 Standard
WIN51IS.SP1: Wink2k3 Standard SP1

WIN51ID: Win2k3 Datacenter
WIN51ID.SP1: Wink2k3 Datacenter SP1

WIN51IA: Win2k3 Enterprise
WIN51IA.SP1: Wink2k3 Enterprise SP1

WIN51IB: Win2k3 Web
WIN51IB.SP1: Wink2k3 Web SP1

WIN51AA: Win2k3 Standard

WIN51AD: Win2k3 Datacenter

SSX4life

01-25-2009, 08:48 AM

Ugh.... Win 2K3 confuses the hell outta me for OEM Scan.

'69712'
'69753'
'69713'
'69754'
'69770'
'69769'

Those are the only PID's that will work with oemscan right? The 2K3 versions boggle me.....

>_<

mr_smartepants

01-25-2009, 08:58 AM

Those are the only PID's that will work with oemscan right? The 2K3 versions boggle me.....

>_<

Correct. Both '69770' & '69769' are x64 though. I have no idea if the oembios sets are the same between x32 & x64 so I put it in anyway.

SSX4life

01-25-2009, 09:24 AM

Sorry to sound so dumb here..... but I've got 2 more questions

#1. Are oembios.ini files for XP / 2K3 interchangable? The reason I ask is I'm having a hard time finding 2k3 strings, and the folder names in your addon reflect the same xp strings with CRC folder names.

#2. I'm also having a hard time finding oemslp keys for Datacenter and Web >_<

mr_smartepants

01-25-2009, 10:55 AM

#1. Are oembios.ini files for XP / 2K3 interchangable? The reason I ask is I'm having a hard time finding 2k3 strings, and the folder names in your addon reflect the same xp strings with CRC folder names.
Well damn. I forgot to change the path in the XP oemscan.ini file to reflect the path \OEMBIOSX\
I'll have to fix that.
I don't know what the CRC hashes are for Win2k3 filesets.

Windows XP and Windows 2003 OEMBIOS files use a different key to encrypt the data, file sets aren’t compatible.

#2. I'm also having a hard time finding oemslp keys for Datacenter and Web >_<

I can't help you there. My 2003 sources are VLK only.
If you don't have access to those keys, then you can't legally install those versions. I know that the Datacenter OEM version is very rare since it's 90% distributed as VLK.

SSX4life

01-25-2009, 11:01 AM

The latest version needs some polish in my opinion.

OEMBIOSX should personally be set as OEMBIOSXP (X doesn't imply enough)

I would love to find a collection of 2K3 oembios files and add them to oembios.net. This means we need to find the CRC hashes for each set and have that reflect in the OEMBIOS3, without that we are up the creek without a paddle.

I'd also like to see the ability to open notepad.exe for oeminfo.ini after the script is run. That way you can enter your model information (just my personal opinion)

Let me know how I can help in any other way ^_^

p.s. do we have a single storage location for 2k3 oembios files yet?

*edit* Smart... do you have IM by chance?

SSX4life

01-25-2009, 11:09 AM

I have also been going though the oeminfo.ini files, they need to be updated / modified.

; OEMINFO18.INI
; 02/3/2005

[general]
Manufacturer=Acer Incorporated
Model= <====== we need to add a model= to each one personally.

[OEMSpecific]
;SubModel=456A0123 ;optional additional oem info
;SerialNo=12345678 ;etc.
;OEM1=Your private info ;etc.
;OEM2=More private info ;etc.

[version]
;Microsoft Windows Millennium Edition
;WinVer=4.90.3000 <===== Windows ME? /fail

[Support Information]
; Info appears staggered here, but is lined up in actual display
Line1 = Acer America Corporation Web
Line2 = http://www.acer.com/aac

mr_smartepants

01-25-2009, 11:27 AM

I have also been going though the oeminfo.ini files, they need to be updated / modified.

[version]
;Microsoft Windows Millennium Edition
;WinVer=4.90.3000 <===== Windows ME? /fail

LOL, epic fail

I only grabbed the logo files from Siginet's repository. It's a start...

I stuck with 8.3 file names because I think at that stage of install there's no long filename support.

I have no idea where to find 2k3 filesets.
I don't use any IM other than Skype.

user_hidden

01-25-2009, 03:00 PM

I don't know what the CRC hashes are for Win2k3 filesets.

win2k3 bios slp: Dell System,Dell Computer

c20d8ff5 oembios.cat
5751b143 oembios.bin
e9d12f4b oembios.dat
ebfb7ca5 oembios.sig

not very many oem vendors released win2k3 so the complete set like XP will not be available.

SSX4life

01-26-2009, 06:25 AM

I am going to modify all of the oeminfo.ini files to reflect the proper version of windows. More to come soon.

mr_smartepants

01-26-2009, 08:03 AM

Sweet! Thanks.

user_hidden

01-26-2009, 09:59 AM

I am going to modify all of the oeminfo.ini files to reflect the proper version of windows. More to come soon.

mine all have:

[Version]
Microsoft Windows XP and the Windows .NET Server family
WinVer=5.01

SSX4life

01-26-2009, 11:55 AM

I belive that is because when I uploaded my small script I changed them all.

mr_smartepants

01-27-2009, 10:06 AM

The latest version needs some polish in my opinion.

OEMBIOSX should personally be set as OEMBIOSXP (X doesn't imply enough)

You're right, it's messy. I've cleaned up the layout a bit. Now it's more logical.
Also, this is 32-bit only. I've read in M$ documentation that x64 doesn't support SLP preactivation.
1.8.06 (in testing now).
Created folders for 2003 OEMBIOS filesets.
Fixed 2003 oemscan.ini with proper CRC tags.
Fine tuned OEMSCAN.CMD
Changed folder layout to the following:
OEM
-FILESETS
--2003 (Windows Server 2003 OEMBIOS filesets)
--XP (Windows XP OEMBIOS filesets)

-KEYS
--2003 (Separate your keys for each subversion)
---DATACENTER
---ENTERPRISE
---STANDARD
---WEB
--XP (Separate your keys for each subversion)
---XP_HOME
---XP_MCE
---XP_PRO

-Logos
--(various)

I'm doing extensive testing with all the XP versions on both my notebooks to ensure it's solid. I hope to have this uploaded this weekend.

SSX4life

01-27-2009, 11:19 AM

you get my approval on this one ^_^

godofmonkeys

01-28-2009, 04:18 AM

I was just wondering...
I work in a repair shop, and format a ridiculously large number of pcs.
made a dvd with the 3 xp editions, oem. used powerpacker.
i'm testing in vmware with a bios mod, to make it look like an acer. the setup still asks me for a product key, and when install completes the install isn't activated.
the procedure is as follows:
copy the source from cd (duh)
run nlite to strip out uselessness
integrate mass storage dp with dpbase
integrate your addon
powerpack each of the 3 distros
iso and test.

don't quite know what i'm missing..

edit: Just checked the vmware pc for the acer name with debug s f000:0000 ffff "Acer"
returned: F000:34D3
so i know the addon should pick up vmware as an Acer...

edit2: also just realized i have an asus mobo... will burn and test outside of vmware
(working from home, it's a snow day for the kids. boss has 2, both in school, so no school=no work)

edit 3:tested on the asus, same thing.
also tested just the xp pro oem (used nlite to only build the iso) and no go.
don't know what i'm doing wrong, the mass storage dp decompresses itself @ t39

SSX4life

01-28-2009, 05:41 AM

I haven't had much luck in vmware with any oemscan addons.

Here are few things to think about oemscan / powerpacker / vmware / that I have noticed.

#1. the edits to the winnt.sif file are minor, you can simply add these two lines to your code to your pre-existing file.

[GuiUnattended]
DetachedProgram = CMD.EXE
Arguments="/Q /C FOR /F %? IN ('%SYSTEMROOT%\SYSTEM32\MOUNTVOL.EXE^|FINDSTR :\') DO IF EXIST %?WIN51 START %?.\OEM\OEMSCAN.CMD"

#2. Powerpacker works for me just fine with this addon. Make 3 separate configured folders (home / pro / mce) and throw em each into powerpacker.

#3. Vmware always finds [SM] as the build for me, I've never gotten a registered oemslp key to work with it (and that's not really the major issue with this anyway). We mainly want to see that there are no errors on install, and all of our tweaks work properly..... just look @ my quick vmware capture I did earlier.

Siginet

01-28-2009, 08:49 AM

The best way to test in vmware is on a system that will pre-activate normally. Then you can edit the vmware config file in a way to use the systems slp information in vmware.

SMBIOS.reflectHost = TRUE

mr_smartepants

01-28-2009, 09:59 AM

so i know the addon should pick up vmware as an Acer...

Are you looking for only "Acer"? Because there are only two possible matches in the addon:
[AcerSystem]
[TravelMate]

Can you post your oemscan.log? It's in C:\Windows\Temp\

I'll be posting an updated addon hopefully tonight. Testing so far is a resounding success.
I'll throw together a PowerPacker build to further test it, but I'm confident.

SSX4life

01-28-2009, 10:15 AM

just a heads up, I reformatted my acer laptop's hdd today and the oemscan build works great for oemlogo.bmp and oeminfo.ini ^_^

I look forward to a revamped version in the future! Keep up the good work, and let me know if there is anything else I can do.

mr_smartepants

01-28-2009, 01:47 PM

1.8.06 online.
Changes from 1.8.05
New folder layout.
Because of new layout, oemscan.ini pathway is changed. Do not just drag/drop old oemscan.ini over new one. Check out the pathway change, then do a find/replace to add the additional ..\..\ etc to path.

Individual integrations run perfect. Single-OS installs are flawless. I can't get PowerPacker to work right (blue screen before txtsetup.) so I can't verify that. I must be doing something wrong with powerpacker since even a raw XP isn't packing right. :(

I'm tired. If there's any errors in the first post let me know and I'll fix them in the morning.
'night all!

godofmonkeys

01-28-2009, 02:24 PM

Siginet

01-28-2009, 03:56 PM

you were right. searching for "Acer" provides a result, but "AcerSystem" Returns nothing. I'm retesting with sig's code in my vm config file. will post results. funny though, before i hosed the install, i checked c:\windows\temp, but it was empty.

That string will only work on a system that can be pre activated. Just because your motherboard is an acer board does not mean it can pre-activate. It must have the Acer SLP info in the motherboard as well.

user_hidden

01-28-2009, 04:13 PM

mr_smartepants

01-28-2009, 09:47 PM

one thing there are 2 DELL oembios sets for 2003.
the R2 version uses crc-99735910
the other uses crc-C20D8FF5

Sigh...
This would be so much easier if oembios.net listed OS with the sets and the tag name.
So which tag name goes with each oembios.cat CRC for 2003?

godofmonkeys

01-29-2009, 12:57 AM

So I finally figured it out.
Somewhere along the lines, either the winnt.sif didn't contain the commands to run the oemscan, or it only contained those commands, and not the rest of the answers i had specified. fixed it by just starting fresh, closing everything and deleting the ini files, and manually editing each instance of winnt.sif i found. including all the wXO**.sif files.
So, I'm burning what should be my final iso. I'm gonna format this pc one more time, and report back here shortly.
(good thing i have my primary install imaged... it takes me about 20 minutes to format, install the test, format, and copy my usable os back....)

EDIT: SUCCESS! It worked. Found "ASUS" in my bios and copied the proper files and key over. no more prompt for a key. It's just too bad the machine won't activate :) (it's a custom build, so no slp i guess) Thank you for all your help, and for this great addon.
And thank you too siginet... for power packer and integrator...

user_hidden

01-29-2009, 04:30 AM

Sigh...
This would be so much easier if oembios.net listed OS with the sets and the tag name.
So which tag name goes with each oembios.cat CRC for 2003?

from what i can figure is "Dell" & "Dell System" = C20D8FF5
when using the R2 version and SLP key "Dell" = 99735910
i am wondering if the 99735910 has to do with x64
win2003 info isn't as freely available like XP.

mr_smartepants

01-29-2009, 08:46 AM

i am wondering if the 99735910 has to do with x64

No, x64 isn't supported.

Abstract: SLP for Windows is anti-piracy technology that builds on previous OEM BIOS-locking solutions provided by Microsoft for the following Windows operating systems:
• Windows XP Home Edition
• Windows XP Professional (32-bit edition only)
• Windows Server 2003 family (32-bit editions only)

It's just too bad the machine won't activate :) (it's a custom build, so no slp i guess)
This addon was not intended to activate non-SLP machines (virtual or real). To do so would be illegal. If I find my addon is being used to break licensing laws, I'll pull my addon from distribution and cease any/all development of it (and discourage others from the same).
Don't break the law!
This addon was developed SOLELY for LEGALLY pre-activating OEM SLP machines easily by using the built-in Microsoft method (which is fully documented). Any other usage is not authorized.

Siginet

01-29-2009, 12:44 PM

No, x64 isn't supported.

I thought in the past someone stated that oemscan did work on x64 editions. But I could be wrong. I have never tried it myself.

But I think it will work as long as the correct oembios files are used. Plus if I remember correctly XP x64 used the same oembios files as x86 versions did. I'll have to do a file compair on the x64 oembios files vs the x86 versions.

godofmonkeys

01-29-2009, 04:22 PM

no, no... nothing like that. if the box dosn't have a coa, then i won't install a copy of xp on it. i was just using mine for testing as it happens to have an asus mobo, but not a royal one.
i work in a repair shop and will not even work with someone if they don't have a legal copy.
my machine was built at work, so i have an oem system builder copy of pro. at a deeply discounted rate.
oh, and the vmware stuff was just to test. it didn't work right for me, remember? had to make it see a match for an oem bios to make sure it was gonna copy the files and set the key.

SSX4life

01-30-2009, 12:53 PM

Well I'm in the process of building my Home / Pro / MCE releases with the latest version.

I'll have more updates soon along with a quick video or 2.

^_^

--ssx--

SSX4life

01-31-2009, 09:58 PM

I have tested my Home / Pro / MCE releases of your oemscan addon and they all work great ^_^.

Here is a short VM Ware install capture I threw together. Let me know what you think....

I plan on doing a complete walkthough from start to finish in the near future for this..

Download the .zip file.
Open the .swf with your web browser
??????
Profit

Enjoy.

--ssx--

mr_smartepants

01-31-2009, 10:20 PM

Thanks for the feedback. I've had good success with this as well.
One thing I'm working on is how to pass the %dospath% variable to oemscan.exe so I can ditch the stupid ..\..\.. in the .ini. Other than that, it's pretty solid.
Now, If I can only get powerpacker to work... :)

SSX4life

01-31-2009, 10:29 PM

let me know what you think of the short video... I love writing documentation on this sorta stuff, let me know what I can do to help out.

mr_smartepants

02-01-2009, 12:19 AM

let me know what you think of the short video... I love writing documentation on this sorta stuff, let me know what I can do to help out.

Well, the video is nice. But I spotted something I don't like in your usage.
You've modified the batch file to remove my info, which goes against my instructions for redistributing here. (http://siginetsoftware.com/forum/showpost.php?p=5478&postcount=132)

From wikipedia (http://en.wikipedia.org/wiki/Plagerism)
Plagiarism is the use or close imitation of the language and thoughts of another author and the representation of them as one's own original work.

Restore the contents of the batch file to it's original content, or stop using it.

Besides, why point users to msfn.org? "Please report errors to msfn.org" I rarely post there, and my references to my addon refer back to this post.

I have not tampered with the sources of xehqter, FreeStyler or Signet, and I have never failed to credit them for their work or contributions.
I expect to receive the same considerations.

Mandarin

02-01-2009, 03:19 AM

Mr Smartepants - I'm completely stumped on this after over 20 attempts to get this working. I used your earlier version (the one that is stickied) and I could see it run the batch script but I can't get the new version to run at all.

I think the problem may be my source - I'm using a Dell OEM version of XP SP1a, which I remove all the Dell branding from. I'm trying to get it to install on my Acer Aspire laptop which has a valid Home COA. I have another Aspire laptop and the correct recovery CDs so have managed to extract the SLP key from that one but I don't have the recovery CDs for the one I am trying to install on, which is why I am trying the OEMSCAN route.

Do you think the source is the problem? I can't see why though because the i1386 folder is basically the same. Everything seems to get copied over and integrated properly but it just doesn't get called during installation.

I've tried the latest beta of the Integrator and even dropped back a version to see if that would work, without success.

As far as I can see I am following all the steps exactly as they should be so have run out of ideas. The only thing I can see is that the Dell i1386 folder already includes 3 OEMBIOS type files and a WINNT.sif file - should I remove all of them first before integrating this - I was working on the assumption that they would be overwritten as part of the dirmove procedure?

mr_smartepants

02-01-2009, 05:38 AM

Do you think the source is the problem?

It's possible. Trying to use a branded OEM source can be problematic at best (and a failure at worst).
OEMs like Dell modify their discs and you may not spot any differences but they're there.
Their unattended files (winnt.sif, unattend.txt, or oobeinfo.ini) would definitely cause problems.
I use a 'system builder' OEM disc which is 'clean' of any branding. Basically it's what the OEMs get before they modify it.

First, I would try your Acer recovery disc on your other Acer PC and see if it works. Then we can move on. Any unbranded OEM source will work fine.

I think you're in for a long painful road to get a Dell source to work. It's possible, but you've set yourself up for dozens of tests and trial & error.

The only thing this addon will do for you is to copy the correct OEMBIOS files and set your key. An added bonus (if the first part works) is to copy any OEM logo branding to match your OEM maker.

Mandarin

02-01-2009, 07:17 AM

Unfortunately the way Acer package their recovery CDs mean that each recovery set is only useable on the laptop it is designed for. There are scripts and batch files all over the place that check the laptop and halt the recovery process right at the start if they do not match.

I have an Acer Aspire 1350 and recovery CD set, an Acer Aspire 1300 and Aspire 1310 and they all use the same method. It loads a recovery program first which then appears to load a customised version of Ghost 2003, which then copies the image file over to the laptop so the i1386 folder is hidden within that image. I did manage to take an Acer 1700 recovery set and replace some of the files so it installs on my Acer Travelmate 240 and that worked with no activation needed. However, when trying the same on my Acer 1363 it just won't work the same way.

That is why I turned to the Dell Home CD I have, which is the only other home version I have. I don't actually have a "clean" home CD.

The problem I am having is that the OEMSCAN addon isn't working for me at all, not that it doesn't work, it isn't being called at all. I think if I can get it to run it will work so I am going to go back to experimenting with the Acer recovery CDs I have and give up on the Dell one. At least that way I am probably going to have less problems.

The odd thing is that I did have more sucess with your 1.41.version with the Dell CD.

SSX4life

02-01-2009, 08:21 AM

Well, the video is nice. But I spotted something I don't like in your usage.
You've modified the batch file to remove my info, which goes against my instructions for redistributing here. (http://siginetsoftware.com/forum/showpost.php?p=5478&postcount=132)

From wikipedia (http://en.wikipedia.org/wiki/Plagerism)
Plagiarism is the use or close imitation of the language and thoughts of another author and the representation of them as one's own original work.

Restore the contents of the batch file to it's original content, or stop using it.

Besides, why point users to msfn.org? "Please report errors to msfn.org" I rarely post there, and my references to my addon refer back to this post.

I have not tampered with the sources of xehqter, FreeStyler or Signet, and I have never failed to credit them for their work or contributions.
I expect to receive the same considerations.

I was just tooling around w/the script a bit to see how it works, nothing more than that. I'll restore it.... sorry if I upset you.

mr_smartepants

02-01-2009, 08:48 AM

The problem I am having is that the OEMSCAN addon isn't working for me at all, not that it doesn't work, it isn't being called at all.

Are you integrating the addon with RVMI? I have both Dell SP1 and HP SP1a cds sitting on my desk and they've both been setup using sysprep (if you find any file on your CD with the name "sysprep*.*" then you're screwed.)
If your source has been "sysprep'd" then you'll need a new source.

sorry if I upset you.
It's OK, sorry for snapping. I just found out some of the nightly builds of the DriverPacks I built not two weeks ago are already circulating on a torrent site. It pisses me off when our hard work is used to propagate pirated warez.

SSX4life

02-01-2009, 08:55 AM

side question.... is it normal for the Windows Setup window to wait 2-3 min's or so when you do a mass storage install in text mode?

Just curious...

mr_smartepants

02-01-2009, 10:35 AM

side question.... is it normal for the Windows Setup window to wait 2-3 min's or so when you do a mass storage install in text mode?

Just curious...

Yes, the txtmode (blue screen) setup prior to the "format/partition" page is loading all the drivers you just slipstreamed. ;)

SSX4life

02-03-2009, 07:48 AM

Expect a full walk though in the near future ^_^

mr_smartepants

02-03-2009, 11:26 AM

Awesome.
I'm absolutely up to my eyeballs at work!

SSX4life

02-03-2009, 01:31 PM

Ok random question.......

Do you want it flash based like previously, you can select from the menu?

List of needed apps (from what I have noticed anyway)

Clean windows source
.net framework 1.1 and 2.0
SP2 / SP3 redistributable
RyanVM Update Packs (post SP2 and Post SP3) <===== you will need post sp2 for MCE2K5 due to M$ and not supporting SP3 intergrated.
RyanVM Integrator
BTS Driver Packs
Nlite
unattended.msfn.org ? <===== I use their guide for creating a winnt.sif file

I can't think of anything else needed... any ideas?

Mandarin

02-03-2009, 01:48 PM

Are you integrating the addon with RVMI? I have both Dell SP1 and HP SP1a cds sitting on my desk and they've both been setup using sysprep (if you find any file on your CD with the name "sysprep*.*" then you're screwed.)
If your source has been "sysprep'd" then you'll need a new source.

OK - given up on the Dell route, too many problems.

I now have a clean Home XP CD which will install perfectly and prompts for it to be activated as it should do. So I slipstream your addon and it still doesn't run properly - if I run OEMSCAN from the CD once XP is installed it says error#14 if that means anything - no matching OEM string found. Yet if I run it from within the Keys folder it successfully finds that it is an AcerSystem laptop and validates all 4 OEM files. It does copy over two folders - the AcerSystem folder and the Travelmate folder, which are the two systems I want to get this installed on.

Is there a log file generated and saved anywhere that I can look at - the command window pops up so quickly it is hard to read, even using the Pause/Break key? It looks like it copies the first 3 files over successfully but fails on the fourth saying the path cannot be found or similar.

The OEM logos and OEM.ini data are not copied over either.

At least it looks like it is now calling the batch file when it should but the file is failing, which in a way is progress from trying to use the Dell CD.

SSX4life

02-03-2009, 01:52 PM

mandrin I'll have a full working guide from start to finish up later this week or by this weekend for sure.

If you are still having problems go ahead and follow that ^_^

Mandarin

02-03-2009, 02:07 PM

SSX4life - I watched the other vid you put together which at least shows that I should be seeing the batch file.
I'll keep an eye out for the new one and carry on testing in the mean time as well - I don't give up easily.

SSX4life

02-03-2009, 03:04 PM

to make your life at least a LITTLE easier... I am going to upload the origional 1.3 oemscan addons made by Siginet.

Check for em here - http://www.oemlogos.siginetsoftware.com/

Sigi, feel free to move the addons back to your new host, and relink them on your site. I also plan on updating your addons for version 1.4.... and adding in new supported hardware vendors ^_^

mr_smartepants

02-03-2009, 09:33 PM

Sounds beyond the scope of this addon. Sounds like a start->finish OS build.

SSX4life

02-03-2009, 10:11 PM

Very true, but the links to his files were MIA after he moved hosting companies. Hopefully he can restore them now.

p.s. check your inbox, I sent you a message.

Mandarin

02-05-2009, 10:49 AM

Finally got a working home XP SP3 CD that doesn't need activating but I did the whole thing manually. I used my Acer 1300 and copied the necessary OEM files over together with pidgin.dll and another dll file which is apparently needed too. Compressed them with MakeCab and added the whole bunch to the i1386 folder, added a few wallpapers, oemlogo and oemini files and it worked perfectly on my Acer 1362 laptop.
It was actually quicker than integrating the OEMSCAN addon but I still want to get this working so I can have one CD that will install XP Home on either a Dell, Acer or Toshiba laptop so I am going to follow this thread further.

mr_smartepants

02-05-2009, 11:49 AM

New version uploaded. I ran into a bug where the batchfile couldn't be 'found' when installing on a drive with more than one partition. The fix is easy, and only involves the winnt.sif entry, nothing else.
Specifically;
Arguments="/Q /C FOR /F %? IN ('%SYSTEMROOT%\SYSTEM32\MOUNTVOL.EXE^|FINDSTR :\') DO IF EXIST %?OEM\OEMSCAN.CMD START %?OEM\OEMSCAN.CMD"

@Mandarin
Glad you got it working, although I want to fix my addon so it works for you and everyone else. Are you starting with a Pro version and converting to Home? Or a VLK then converting to OEM?

Mandarin

02-05-2009, 01:53 PM

@Mandarin
Glad you got it working, although I want to fix my addon so it works for you and everyone else. Are you starting with a Pro version and converting to Home? Or a VLK then converting to OEM?

After I dumped the Dell OEM CD route I tried it with what I thought was a retail home CD but actually turned out to be an upgrade home CD. That just didn't want to play ball at all.

I am now using an OEM version of Windows XP Home SP2. I use Autostreamer to slipstream SP3 then move on to use Ryan's Integrator to slipstream the post SP3 update pack, the NET updates and a few other addons, which all works perfectly, but fails to run the OEMSCAN addon.

If I only want to put together an Acer CD is it better to remove all the other folders? I only want to work with XP Home - should I remove the other folders (MCE + PRO)?

I recompress the addon with winrar, not 7zip simply because I don't have 7zip installed on the laptop I am currently using - does that matter?

mr_smartepants

02-05-2009, 09:37 PM

There are several files that determine what version of XP (Home/Pro/MCE) you have. One of them that my addon looks at is i386\setupp.ini, and it looks for 'OEM' on the PID= line. If it doesn't find those 3 letters, it stops and reports an error.
Sounds like you're not really using a clean source, because I've built so many checks into the addon it could be failing at any point. Does the batch file start at all?
It doesn't matter what you compress the addon with, so long as RVMI recognizes it.

Mandarin

02-06-2009, 09:47 AM

My setupp.ini file reads as

ExtraData=786F687170637175716954806365EF
Pid=76477OEM

So it is an OEM CD.

The batch file looks like it starts - there is a very quick flash on the screen right at the start of the gui phase of setup. Running it manually validates all the OEM files, correctly identifies the laptop type as AcerSystem then stops with the error message mentioned earlier.

mr_smartepants

02-06-2009, 10:09 AM

The batch file looks like it starts - there is a very quick flash on the screen right at the start of the gui phase of setup. Running it manually validates all the OEM files, correctly identifies the laptop type as AcerSystem then stops with the error message mentioned earlier.

Well, IIRC, there's two command windows, one very fast one just prior to mine. If mine doesn't run, you should get a popup error with an "OK" button that says something like "File not found".
Otherwise, I need to know the error # (1, 2, 3, etc) my batch file reports (the new batch file has error numbers.

Russtavo

02-19-2009, 06:29 AM

Hello mr_smartepants!

Firstly, thank you for creating this add-on, unfortunately it sounds like I'm having a similar problem to Mandarin. I used RVM 1.5.3 to integrate your latest 1.8.07 add-on. During installation on a HP 530 laptop, a DOS box briefly flashed on/off (too quickly to read). I didn't expect to have to input a key, but I was prompted. Once completed, XP was not activated and weirdly, system properties showed a Fujistu logo :confused:
I manually ran the OEMSCAN.CMD file from the CD and include the output here:

Detecting Windows type, please wait
dospath=D:\
Windows OEM version detected
myvar=55277OEM
finalvar=55277
WinXP Home version detected
Scanning for matching Home OEMBIOS string
Found oemscan log file
OEMtype=FSC
Attempting to move OEM logo files from
"D:\OEM\Logos\FSC"
1 file(s) copied.
1 file(s) copied.
The system cannot find the file specified.
The system cannot find the file specified.
The system cannot find the file specified.
A subdirectory or file C:\WINDOWS\Resources\Themes already exists.
D:\OEM\Logos\FSC\themes\*
The system cannot find the path specified.
0 file(s) copied.
A subdirectory or file C:\WINDOWS\Web\Wallpaper already exists.
D:\OEM\Logos\FSC\walls\*
The system cannot find the path specified.
0 file(s) copied.
Could not complete script.
Please report errors to mr_smartepants.

My source disc btw. was an official XP Home OEM SP2 disc that I slipstreamed SP3 into using the "official" method, so I don't see it as being a problem. The setupp.ini looks contains this:

[Pid]
ExtraData=786F687170637175716954806365EF
Pid=55277OEM

Update:
Ok so I figured out if I remove the [FSC] entry out of the OEMSCAN.INI, it correctly identifies "Compaq". Now I find I'm not the only one: http://www.siginetsoftware.com/forum/showpost.php?p=5417&postcount=120

Is simply changing the order the recommended course of action?

mr_smartepants

02-19-2009, 08:55 AM

Thanks for your report.
Yes, changing the order in your oemscan.ini should do the trick. If you could verify that for me, I'll change it here and upload a new version.

Russtavo

02-20-2009, 02:13 AM

Thank you, I can verify that changing the order worked - correctly identified and activated Compaq. :D

As an aside, I also tried activating this pc post installation using OEMScan, using the same source disk and oem key as above. It correctly identified brand, copies over the OEMBIOS files, I reboot - but not activated. Why would this be? :confused:

mr_smartepants

02-20-2009, 08:27 AM

As an aside, I also tried activating this pc post installation using OEMScan, using the same source disk and oem key as above. It correctly identified brand, copies over the OEMBIOS files, I reboot - but not activated. Why would this be? :confused:

That's normal behavior. XP is not like Vista activation. Once XP is at the desktop, you cannot PREactivate it with oemscan. The whole point of oemscan is to preactivate the OS before you are asked for a key at OOBE.

Siginet

02-20-2009, 09:30 AM

Russtavo

02-20-2009, 11:11 AM

Actually it should be possible to Activate Post install. I think my 1.7 Betas would actually Activate Post install since they detected the OS Type during the runonce phase. Once you rebooted it was activated.

Exactly, yes I did mean post install. It seems to work for a few Dell's I tried, just not HP 520/550 laptops - don't know why, just seemed odd.

SSX4life

02-20-2009, 11:14 AM

Exactly, yes I did mean post install. It seems to work for a few Dell's I tried, just not HP 520/550 laptops - don't know why, just seemed odd.

2 things to check

#1. Are you sure you have the proper OEM BIOS files placed in the proper CRC folder?

#2. Could your HP systems have a different CRC than what is previously mentioned (different hash?)

Russtavo

02-23-2009, 01:52 AM

2 things to check

#1. Are you sure you have the proper OEM BIOS files placed in the proper CRC folder?

#2. Could your HP systems have a different CRC than what is previously mentioned (different hash?)

1. Yes.
2. No.

Not to worry, so long as pre-activation works ;)

soo_smitty

02-24-2009, 05:56 AM

Getting post-install activation working could be useful for a universal Sysprep image...

mr_smartepants

02-28-2009, 12:37 PM

Updated to 1.8.08. Added many more OEM names/folders (thanks ssx4life).

SSX4life

02-28-2009, 08:56 PM

I gave the current version a fine tooth comb over and it looks good.

I did change one thing however for my personal release. It's a pain in the @ss to manually copy and paste the oembios files from the CRC based folders that were downloaded to the MANUFACTURER_CRC in this current release.

Because of that I wiped out all of the folders in the filesets directory and replaced it with the base CRC folder name. I then adjusted all of the oemscan.ini locations to reflect the change. This way I could take a step out for the end user.

#1. Simply download the needed files / unzip them to folders / plug them into the Filesets directory.

#2. No need to hunt and paste based off of CRC (or possibly get oembios.net to update to our current methods?)

I also noticed something else interesting... is it possible that instead of inserting the wallpaper / theme into the %systemroot% that we move it to the default user login location? That way when XP is installed on a Dell that all future accounts created on the system use the dell background? Just my 2 cents on that one.... same applies to default icons on the desktop. I use a .reg file currently to recreate them (by default we only get recycle bin)

Some future things to think about.

--ssx--

p.s. with all oembios files the current .7z sits around 700mb! ^_^

searchengine

03-09-2009, 09:04 AM

fantastic addon ;) ... I have xp pro sp3 to which I add an MCE addon.

Decided to give this a try to see if I could convert to OEM install ... worked perfectly ....I installed in my pc which has Asus Bios Type.

Since then I have tested this addon running in vmware for Asus; IBM; and Toshiba .... all three installed activated as required without a problem.

The only thing I had to do to test activation in vmware was modify vmware bios.

Many many thanks, multi-OEM disk now made and installing nicely.

tomatthe

03-23-2009, 06:37 AM

Where did you get the oem bios files from searchengine? oembios.net doesn't seem very updated anymore, and I don't really like using torrent files at work.

Ok managed to get ahold of one of the oembios filesets to test.

The xp cd I have to build from is a corporate version, not sure if that matters or not. Basically I downloaded oem act, added the oembios files and the slp key, compressed then use rvm to intergrate the package into the windows cd. Burned and started the install and ran into an error stating

"Unable to determine Windows Type" please contact signet.

Any idea on what I might be doing wrong here would be appreciated.

mr_smartepants

03-23-2009, 09:22 AM

You can't use an OEM SLP key (or this addon) to activate a corporate (VLK) version of windows. There are different files between the versions and my addon doublechecks to make sure it's running on a supported version.
Are you sure you're using my addon? Mine doesn't say "contact Siginet". :)

tomatthe

03-23-2009, 01:07 PM

Hmm, I was using OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MULTIOEM_1.8x

I can double check, i do have bunch of mess from trying to learn about this project so I might have accidentally used the wrong files.

Unfortunately the only XP install cd's we have are the vlk ones which sounds like that might be a stopping point.

We do have a few customer restore cds from a dell laying around, is it worth trying to pull the windows files from this?

It actually did say Please report errors to mr_smartepants. I was just mixing up what the error was.

mr_smartepants

03-23-2009, 10:20 PM

One addon that may help you specifically is RogueSpear's VLK to OEM converter addon: http://www.doitrightconsulting.net/forum/viewtopic.php?f=8&t=180
It's listed at the very bottom of the first post (after all the scriptpack addons).
I use this occasionally myself and works perfectly.

tomatthe

03-24-2009, 05:02 AM

Thanks for the link, waiting on the site admin to enable my account, then hopefully I can make some progress on this today.

I don't think the guy who runs that checks his email to often anymore or something, I signed up yesterday in the am and he still hasn't accepted my account. Is there any chance you could send me to files, or email a link to me or something if there are issues with posting his work elsewhere.

tks.

mr_smartepants

03-26-2009, 01:30 PM

1.8.0.9 online. Check first post. :)
Changed key order to Lenovo, IBM, Hitachi to alleviate false matches.
Updated oeminfo.ini files to reflect XP version and added Model=. as placeholder.

dolivas27

04-04-2009, 02:11 AM

mr_smartepants first thanks for your work on this and all the work you do over at Driverpacks. I was using this tonight on a compaq laptop I was reloading and received this error. I was able to fix the problem you are missing a Hewlett-P directory under Logos. just thought I would let you know and once again...... THANKS....

Detecting Windows type, please wait
dospath=D:\
Windows OEM version detected
myvar=76487OEM
finalvar=76487
WinXP Pro version detected
Scanning for matching Pro OEMBIOS string
Found oemscan log file
OEMtype=Hewlett-P
"Error#4. OEM Logo copy cannot continue. Could not find any OEM logo files"
Could not complete script.
Please report errors to mr_smartepants.
Press any key to continue . . .

mr_smartepants

04-04-2009, 04:58 AM

SSX4life

04-05-2009, 12:23 PM

We might also want to include the wallpaper / theme in the default user profile... just a thought.

pctcdc06

04-10-2009, 06:13 AM

First of all I want to say THANK YOU for all your hard work. I love this project and it's helped me out tremendously. I love your work and thank you so much for your continued support on this project.

Question:

I compiled everything and did a test install on a VM-WARE box with HP bios. It matches "OEMtype=Hewlett-P" At first I was getting the error above "#error #4" so I re-compiled and made a Hewlett-P directory in the logo location to pass that error. It says it matches the bios files and copies them using the HP_06D652A4 but it's still not activated. I then used a copy of your old "XP ALL OEM V1" disk back from the oink days and took the HPQ bios files from the directory HPQ and then it activated, so I made an entry for HPQ and pointed it to that directory. I am just afraid this might mess up other HP/Compaq installations? Thoughts?

Update: Instead I changed the Hewlett-P scan directory to use Hewlett_CD4E1902 instead of HP_06D652A4 and it worked.

mr_smartepants

04-13-2009, 12:02 AM

I then used a copy of your old "XP ALL OEM V1" disk back from the oink days

:confused:
I have no idea what you're talking about. I don't promote warez.

Siginet

04-13-2009, 10:10 AM

Thanks, I'm fixing those empty directories in my local copy. This is an unintentional side effect of depending on RVMI. RVMI won't 'DirMove' an empty directory. Not sure if that's a bug or a feature :p
The fix is to actually put files in those directories (.gif/.jpg/.ini etc.).
I'll be releasing a new/improved addon after I get back from my vacation in about a week.
I'll be adding XP/2003 x64 support in the next release! :)

I guess it could either be a bug or feature. ;)

Most of the time it should never be a problem.

If there is nothing in the directory then usually the folder wouldn't be needed anyways.

In your script you seem to look for the folder wether it is empty or not. Could you maybe skip the folder if it is not found? Or does the folder have to exist for the script to be able to finish?

I would think Logo's should be optional anyways. So if you don't need the logos you shouldn't need the logo's dir should you?

mr_smartepants

04-13-2009, 11:28 PM

It's not that big a deal. I added the error # in the script to aid in troubleshooting. I can take it out if it bothers people. Worst case would be an error during the script file-copy stage.

mchallis

04-26-2009, 06:13 PM

Thanks for the addon.

I found this while re-installing Win XP Home OEM on a HP Laptop and it would not activate...

Hewlett-P goes with OEMBIOS.CAT CRC32=CD4E1902, not OEMBIOS.CAT CRC32=06D652A4

I had to make this change in oemscan.ini

[Hewlett-P]
;PATH="..\..\..\FILESETS\XP\HP_06D652A4\"
; corrected files:
PATH="..\..\..\FILESETS\XP\Hewlett_CD4E1902\"

also the logo did not install until I made this change:
added a new folder /Logos/Hewlett-P
then copied the logo files from /Logos/Hewlett

mr_smartepants

04-26-2009, 09:51 PM

Thanks for your report. I'll fix this for the next release.
Although, it looks like you only need to delete this entire section from the .ini:
[Hewlett-P]
PATH="..\..\..\FILESETS\XP\HP_06D652A4\"
CMD="SetKey 11111-22222-33333-44444-55555"

The section [Hewlett] will then pick up the selection and the logo folder will work. :)

Incidentally, I'm still working on the next release, but it's slow going. My wife's got a "honey do" list as long as my arm. I am still working on this though!

mr_smartepants

04-27-2009, 02:01 PM

I'm putting the finishing touches on the next version. I rewrote quite a bit of the script. If anyone has 64-bit copies of 2003, please post the edition (datacenter, web, etc.) and the PID from $cdrom$\AMD64\setupp.ini and I'll include them in the next version.

mr_smartepants

04-28-2009, 10:21 AM

Does anyone have a running XP-64 or 2003 x64 install? I need to verify the location of a file. I don't have those OS so I can't verify.

I'm looking for the 64-bit location of this file:
(x86 path) %systemroot%\system32\$WINNT$.INF

Can someone report back with the 64-bit location (if different)?

5eraph

04-28-2009, 12:06 PM

You have the correct location, mr_smartepants. Your problem will be accessing it with a 32-bit program—it's not possible. Your requests will be passed through the Windows on Windows (WOW64) layer to %SystemRoot%\SysWOW64. The file won't be found.

mr_smartepants

04-28-2009, 12:48 PM

Just my luck! :rolleyes:
Well, I don't need to access it with a 32-bit program. I access it through a command batch file (16-bit?) during XP setup (at T-39 specifically), so no 64-bit operations should be present (or running). So if I'm correct, the batch file will treat the $winnt$.inf as a text file and 'peek' into it for a value, then 'poke' the value change.
Thanks for the info! If needed, I can alter the search routine to account for the WOW factor. ;)
Would you be willing to test? :D
I'm uploading v1.8.0.10 now.
*Edit
First post updated. v1.8.0.10 online now.
*Edit2
Oops. I encrypted the .exe. Reuploaded addon.
New hashes:
File: OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MULTIOEM_1.8.10 .7z
CRC-32: c8ae75bb
MD4: 4cb15569f6e14cf105105ded598b6f05
MD5: e25bb0dbbd5b09e1f6e09bd6481003db
SHA-1: dec6460fd05ce25dde833321a15be390ae726ece

5eraph

04-28-2009, 01:55 PM

I'm willing to test, but I don't have an OEM WinXPx64 source. I build my own machines, so communicating with the system manufacturer (me) is pointless—though I do talk to myself more often than I'd like to admit. ;)

If I execute OEMScan.exe from a command prompt, what should I expect to see? Currently, I only get the following response from the program before it finishes silently.

Detecting Windows type, please wait
EDIT #1: The OEMScan.cmd from v1.8.09 (with some minor edits to ensure that it doesn't close the window upon completion) is more descriptive:

Detecting Windows type, please wait
dospath=D:\
"Error#1. OEMSCAN cannot continue. Unknown Windows type."
Could not complete script.
Please report errors to mr_smartepants.
Press any key to continue . . .
If OEMScan.exe is a compiled batch script based upon OEMScan.cmd then it is probably running 32-bit code.

EDIT #2: Looking more thoroughly through OEMScan.cmd has revealed the following: The script is looking in the wrong place for SetupP.ini on x64 sources. It should be looking for the file in "%dospath%\AMD64".

The following lines for Windows Server 2003 x64 should end in DATACENTER2 and ENTERPRISE2, respectively.

if '%finalvar%'=='69769' echo Windows Server 2003 Datacenter x64 Edition detected && goto DATACENTER2
if '%finalvar%'=='69770' echo Windows Server 2003 Enterprise x64 Edition detected && goto ENTERPRISE2

mr_smartepants

04-29-2009, 10:53 AM

Bugs found in 1.8.0.10. :mad:
I'll upload 1.8.0.11 after confirmed testing.

mr_smartepants

04-30-2009, 01:56 PM

First post updated with 1.8.1.0.
Significant script code improvements. Script now compiled into .exe with x86/x64 source compatibility! It also now has multiple checks and cross-checks to prevent misuse with pirated/tainted sources. I've tested extensively with OEM versions of x86 XP Home/Pro/MCE as well as x86 Server 2003 Standard and all activated flawlessly.
This will not activate any Retail or VLK sources! OEM only.

SSX4life

05-01-2009, 07:07 AM

Glad to see you are still working on this. Just curious about the "It also now has multiple checks and cross-checks to prevent misuse with pirated/tainted sources."

I'm curious what that entails (checking against a vlk source perhaps? I thought you couldn't activate on a vlk system to begin with due to the type of the media.

I'll give this a whirl and see what we end up with.

mr_smartepants

05-01-2009, 08:14 AM

Just curious about the "It also now has multiple checks and cross-checks to prevent misuse with pirated/tainted sources."

I anticipate that these new checks may break PowerPacker images. I can't seem to get PP to work anymore so I can't test it.
I'll keep playing with PP though. I'm sure it's something I'm doing wrong since it's worked previously for me.

Well, basically the first check is to see if a valid source CD/DVD is inserted in the drive.
My script requires the installation media to be available at the time the script is executed. This prevents someone installing without a key, modifying/hacking the installed files, then trying to activate after-the-fact.
Then it checks the source to make sure it's a valid OEM source (not VLK or Retail).
Then it uses two different methods to check what version of the OS is present and compares these two values. If there's any mismatch at all, pre-activation will fail.

I had to do this to cover my a$$. With M$ keeping a watchful eye on our progress. The command script I was using before made it too easy for pirates to abuse the system (I heard my addon was used on a TPB 9-in-1 disc once).
Maybe when Win7 is mainstream, I'll release the source code for everyone.

SSX4life

05-01-2009, 10:30 AM

Why must people take a good thing and turn it on it's head...

=/

mr_smartepants

05-01-2009, 01:10 PM

This is a very good thing. Folks who have legitimate OEM CDs with matching SLP keys will have nothing to worry about. :)

mchallis

05-02-2009, 01:56 PM

Using 1.8.09 on a Compaq Presario SR1738NX ...
It matched "Asus", then installed ASUS logos.
It did activate correctly.
It should have installed Compaq logos. Did you know this can happen? Maybe it should ask what logo you want, press 2 for "Compaq" or something.

mr_smartepants

05-02-2009, 02:52 PM

Sometimes that happens. It's because there are several text strings within the BIOS and OEMSCAN only matches the first string it finds, not always the correct string. This is a limitation within OEMSCAN itself, and there's nothing I can do about it directly. I can only juggle the .ini entries.
I've tried to make my addon as fully automatic as possible. Making the script 'attended' just defeats that purpose.
You can fix this yourself by moving the ASUS section in each oemscan.ini to follow after the HP/Compaq sections (or last). That way, Compaq will get selected before ASUS.

mchallis

05-02-2009, 03:03 PM

OK, thanks

SSX4life

05-04-2009, 08:38 AM

That's why the Fujitsu strings are at the end of all the oemscan.ini entries. Not much we can do to resolve the issue >_<

mr_smartepants

05-04-2009, 10:14 AM

BTW, the current version 1.8.1.0 works perfect in PowerPacker. I verified it now that I solved my separate issues with PP.

mr_smartepants

05-04-2009, 01:47 PM

1.8.1.1 online.
Minor string optimizations to ensure 100% PowerPacker compatibility regardless of source folder naming.

gospeed.racer

05-04-2009, 02:40 PM

I will be giving it a shot later tonight....unless you are going to tackle rebuilding PowerPacker too...then I can wait till morning LOL:p

mr_smartepants

05-04-2009, 09:29 PM

LOL, I don't work that fast! :D
Realistically, for PP builds, you only need to integrate my addon once into one of the OS. Then for the other OS, just edit the winnt.sif with the two lines.

cworkman

05-07-2009, 08:48 PM

Could Someone Plz Explain To Me How To Get This Working?

I have The Following XP Pro CD's

Acer XP Pro SP2
Dell XP Pro SP2

How Do I Make Them Into 1 CD?

Do I Have To Take The Dell Files From The XP CD and Add them?

For Example! The PIDGen.dll, The SETUPP.ini?

Or Is The Files For Acer OEM The Same As On The Dell CD?

plz Reply ASAP!!! Thanks!!!!

mr_smartepants

05-07-2009, 09:44 PM

I'm sorry if the first post wasn't descriptive enough for you. I'll have to fix that.
1. Start with a clean UNBRANDED OEM CD (MSDN or System Builder discs will do).
2. Integrate your favorite updatepacks/addons with either nlite or RVMI, your choice.
3. In a separate session, integrate this addon with ONLY RVMI.
4. DriverPacks, if wanted go last.
5. Build ISO.

If you start with a clean source, you won't need to copy system files from one disc to another. My addon checks for mismatched system files and will fail if they are found.

mr_smartepants

05-13-2009, 09:31 AM

Well I just installed on a Sony Vaio notebook today and my addon activated as a 'HP' :o. I moved the Sony key entries above the HP entry and it worked fine. Funny though, when it selected as HP, I got no activation prompt and M$ MGAdiag tool showed it as "Genuine". :p

gospeed.racer

05-13-2009, 05:12 PM

sounds like we need to just keep shuffling the deck :) Too bad we cant figure out a way to give an option when it finds more than one match.

gospeed.racer

05-14-2009, 03:40 PM

I cursed myself :( I just had an Averatec (tri-Gem) activate as a Toshiba. Going to have to shuffle the deck again! LOL

mr_smartepants

05-14-2009, 09:40 PM

I just had an Averatec (tri-Gem) activate as a Toshiba.

Good to know! Does that system have a Toshiba drive?
In my tests I've found that a system mismatch happens when oemscan detects the drive manufacturer before the system manufacturer.
Is that the problem in your case?

gospeed.racer

05-15-2009, 07:20 AM

funny enough, I had to stick a different dvd drive in it to load my DVD...it is a Toshiba. the drive that belongs is a Quanta...doh!

If I kept the Toshiba drive in it, and the Toshiba files it copied, everything was happy. When I swapped to the Quanta drive, WGA popped up. In order to swap out the correct files, I had to put the Toshiba drive back in it...once I loaded the correct tri-gem files, WGA popped up again. When I have the Quanta drive in it nothing will activate. So weird! I ran Severach's program and it correctly finds that the Tri-Gem should activate regardless of which drive I have in the machine, but with the Quanta drive, nothing will.

here it is, first with the original drive...and second with the Toshiba drive
http://img198.imageshack.us/img198/2909/oemscan.jpg

mr_smartepants

05-15-2009, 08:16 AM

Well, without access to the OEMSCAN source code, there's nothing I can do about it apart from juggling the key entries. I'll post a bug report over at MSFN.
It's good to know the cause of that particular issue though. Thanks for verifying.

mr_smartepants

05-16-2009, 06:38 AM

I wiped out all of the folders in the filesets directory and replaced it with the base CRC folder name. I then adjusted all of the oemscan.ini locations to reflect the change. This way I could take a step out for the end user.

#1. Simply download the needed files / unzip them to folders / plug them into the Filesets directory.

#2. No need to hunt and paste based off of CRC (or possibly get oembios.net to update to our current methods?)

I'm beginning to like this idea of yours! I'm planning to update the addon again with this layout in mind.
I'm also mulling over the idea of yours for copying the themes to the default user profile. Shoot me a PM with more info. You have some good ideas! :)

SSX4life

05-17-2009, 07:53 AM

I'm glad you like my ideas =)

In reality I invision this application working 2 ways

#1. Standalone

#2. Windows installation based

The standalone would allow you to activate windows xp on a system that has just had a fresh install using a generic oem disk.

The second would be where the script will auto insert the wallpaper and other modifications to the default user profile during the initial installation.

If you need more testing please let me know, I'm happy to help.

mr_smartepants

05-17-2009, 08:18 AM

The standalone would allow you to activate windows xp on a system that has just had a fresh install using a generic oem disk.

That's funny that you brought that up. I was just thinking that would be the next logical step for this addon. :)
#2 is about 99% done. I've already made more code refinements. The only item left is to insert a timer and a list for "manual over-ride" if oemscan matches the wrong OEM.
Once that is done, I have ideas for #1 and already have some snippets of code that will get us started.

gospeed.racer

05-17-2009, 10:26 AM

If I could make a recommendation, I like the timer setup IF only ONE is found....but if it scans and finds more than one, it would be best to let it sit until the user selects one.

I assume we would use the key provided by Microsoft (the one used during setup when you do not type in a key during install) to get it up and running all unattended, then use oemscan to patch in the correct files and change the key? If oemscan doesnt find a match, we would also need an easy option to key in the correct key off the sticker too. Is this what you guys are envisioning?

Thanks for all the hard work guys! I cant wait to see what happens next!

mr_smartepants

05-17-2009, 02:04 PM

If I could make a recommendation, I like the timer setup IF only ONE is found....but if it scans and finds more than one, it would be best to let it sit until the user selects one.

This I cannot do without access to the oemscan source code. This is the limitation of the current version of oemscan. It will match the first string it finds. It won't display a list under normal ops.

The timer/choices I have nailed in a batch. The problem is stripping out everything in the oemscan.ini EXCEPT the users choice. I'm making progress though.

My vision is to run my addon in full auto mode. If there's a problem, the user then will reformat and start over but select 'manual over-ride' mode and continue with manual choices in the batch.

I see your point though. If I can run oemscan with the /w (i think) switch, then read the output, if there's more than one choice default to manual otherwise go auto.
Hmmmm.

gospeed.racer

05-17-2009, 05:16 PM

I sure wish we could convince him to either release the code, or work with us. It doesn't sound like he even has much interest in the oemscan anymore (and hasn't for quite a while). Have you ever spoke with him about our interests? I sent him a PM a while back and he was confused as to why we would ever need to mess with oemscan, and I could not convey what I wanted it to do well anyway. I was asking for a version that looked for a renamed version of oemscan, so i could have all my oems together. I havent needed that since you and Sigi now have versions that work with multiple versions (home, pro, mce..) but still....I wonder if we just need to summon him over here and twist his arm a bit.

The program that I use (by Severach) to identify which will preactivate seems to identify all of the candidates. Isnt this what oemscan does, except it goes a step further and actually inserts the files and key? I wonder if we would be better off seeing if Severach would work with us? If one guy built oemscan, I dont see why someone else couldnt build something similar :p (says the guy that has no frickin idea how to code anything! LOL)

mr_smartepants

05-22-2009, 09:28 AM

I've hit a wall with the .ini extraction batch. I've asked for help here:
http://www.computing.net/answers/programming/batch-file-to-extract-lines-of-text-from-ini/19089.html
But the only response I got was in Python, not batch script. :(

I'm putting the finishing touches on the addon then I'll release. Changed include SSX4life's suggestion of putting the oembios filesets in their raw CRC directories, and other code refinements.
The major hurdle was not adding the timer or the manual-override but the oemscan.ini extraction routine (see above).

I'll be releasing the entire project as "open-source". I'll maintain the addon with my compiled OEMAUTO.exe but I'll include the entire batch script (with comments) in the first post for those who are interested.

Below is my progress with the timer/override functions:

@echo off
echo Do you want to enter manual override mode (Y/N)? Automatic mode in 10 seconds.
CHOICE /C YN /N /T 10 /D N>NUL
IF ERRORLEVEL 2 goto Auto
IF ERRORLEVEL 1 goto Manual
:Auto
echo Automatic mode selected
:: Put pointer to normal mode here.
goto end
:Manual
cls
echo Manual mode selected
echo Please choose from the following options.
echo A. HP
echo B. Sony
echo C. Fujitsu
echo D. Gateway
echo M. More choices
CHOICE /C ABCDM /N /M "Choose A, B, C, D or More?"
IF ERRORLEVEL 5 SET OEMPICK=More&& goto Manual2
IF ERRORLEVEL 4 SET OEMPICK=Gateway&& goto Pick
IF ERRORLEVEL 3 SET OEMPICK=Fujitsu&& goto Pick
IF ERRORLEVEL 2 SET OEMPICK=Sony&& goto Pick
IF ERRORLEVEL 1 SET OEMPICK=HP&& goto Pick
:Manual2
cls
ECHO You chose %OEMPICK%
:: More choices go here...
echo Sorry no more choices. Batch will now exit.
goto end

:Pick
ECHO You chose %OEMPICK%
Set OEMPICK=[%OEMPICK%]
echo Looking for header %OEMPICK%

Set FlOut="%~DP0oemscan.tmp"
Set FlIn="%~DP0oemscan.ini"
Set Count=0
Echo. >> %FlOut%
echo Created temp file
Echo %OEMPICK% > %FlOut%

:Extractini
:: This portion would extract the required elements from oemscan.ini and copy to oemscan.tmp
:: Then use the string from previous OStype subroutine to copy directory containing correct oemscan.exe, oemscan.ini and setkey.exe to temp dir.

:end
echo Done for now.
Set Count=
Set FlOut=

endlocal
pause

mr_smartepants

05-22-2009, 11:46 PM

First post updated with v1.8.1.2.
Third post updated with source code.

Go legit or go home. :)

Raoul90

05-23-2009, 03:33 PM

Hey,

Thanks for the update.

I have some old Dell Laptop here with Windows XP Home.
So I want to do a fresh install with this addon also.

But one questions:

; Begin Dell series
[Dell System]
PATH="..\..\..\FILESETS\XP\B6F0EEFD\"
CMD="SetKey 11111-22222-33333-44444-55555"

[Dell Computer]
PATH="..\..\..\FILESETS\XP\B6F0EEFD\"
CMD="SetKey 11111-22222-33333-44444-55555"

[Dell Inc]
PATH="..\..\..\FILESETS\XP\B6F0EEFD\"
CMD="SetKey 11111-22222-33333-44444-55555"

[Dell Quanta]
PATH="..\..\..\FILESETS\XP\87870F5A\"
CMD="SetKey 11111-22222-33333-44444-55555"
; End Dell series

What should I choose? (its a Dell Inspiron).
I think Dell Computer will work?

mr_smartepants

05-24-2009, 06:30 AM

What should I choose? (its a Dell Inspiron).
I think Dell Computer will work?

That's the beauty of this addon. You don't have to choose. It's automatic.
Just put your SLP Dell key for ALL the dell entries and you'll be fine.
Don't forget to put the oembios.* files in their respective folders (there's two) also.
:)

Raoul90

05-24-2009, 11:34 AM

That's the beauty of this addon. You don't have to choose. It's automatic.
Just put your SLP Dell key for ALL the dell entries and you'll be fine.
Don't forget to put the oembios.* files in their respective folders (there's two) also.
:)

Ah ok, Done! :)

I almost forgot the oembios files. :)
But I see 3 BIOS:
87870F5A "Dell Quanta"
B6F0EEFD "Dell System", "Dell Computer", "Dell System", "Dell System", "Dell Inc"
DD981F15 Dell.xrm-ms

I took the 2nd, good?? :)

Timbo

05-24-2009, 10:08 PM

I just tried out version 1.8.1.2 for the first time, and I didn't save the error, but the script failed because it was looking for Logos/SM. I looked in my source and in the original download of 1.8.1.2, and I don't see that.

This happened for WinXP Pro, SP3, OEM, where I had only two Dell filesets and testing in vmware. I havent tried this before and I don't fully understand, but I was trying. I was expecting it to go through install and then tell me the key needs to be changed, but having this error, I didn't find out.

Not sure if that error was caused because you can't do what I did, but I thought I'd report it in case you can prevent it in the future.

Thanks!

mr_smartepants

05-24-2009, 11:04 PM

the script failed because it was looking for Logos/SM.
...
testing in vmware.
This is normal. Unless you configure vmware to emulate the host bios, then you'll almost always get matched to "SM" which is in every bios. I only use SM for single-use systembuilder OEM keys (not SLP).
Let us know how it goes on your real hardware.
Thanks for the feedback.

SSX4life

05-27-2009, 10:25 AM

Any progress on inputting information into the default user profile.

mr_smartepants

05-27-2009, 12:19 PM

To be honest, no. I haven't looked into it yet. I've been swamped at work.
Weren't you working on something like that? If so, let me take a look at the code and I can add it in there. :)

xehqter

05-28-2009, 01:24 AM

Just checked my messages on MSFN, in regards to hardware devices triggering (ie: Toshiba DVD drive) the wrong SLP files, just hard code the search address.

By default OEMSCAN searches all of the BIOS, I believe on the MSFN forums (don't quote me) one the the users (maybe FreeStyler) posted the search addresses for many of the filesets.

If that's not the case let me know the OEMBIOS set and I'll give you the settings to use in oemscan.ini

mr_smartepants

05-28-2009, 09:01 AM

Sweet. Thanks for the info xehqter. I'll try and research it at MSFN. :)

*Edit
Found it. It's here:
http://www.msfn.org/board/Multi-Manufacturer-Pre-Activation-t71016.html&st=200&p=534097#entry534097

With a sample oemscan.ini here:
http://www.msfn.org/board/index.php?s=&showtopic=71016&view=findpost&p=783199

user_hidden

06-07-2009, 06:42 AM

found some others that i noticed were not in the package.

2003 + Home Server:
Acer - 9851DBEB
IBM - 36E95D7A

mr_smartepants

06-07-2009, 09:49 AM

Interesting...
I didn't know about those. Are you sure about Home Server? That was based on Vista SLIC I thought.
What versions of 2003? Can you post the contents of your I386\SETUPP.INI ?

mr_smartepants

06-08-2009, 12:48 PM

I added it, but I have no idea what the bios ranges are for those two. They're not listed on oembios.net so I guessed.

gospeed.racer

06-10-2009, 07:01 PM

For each version that is released, I have been re-running the integrator each time and it has finally occured to me that I should just ask....can I just insert the new oem folder in place of the old one and be done? When integrated, does it do anything other than placing the oem folder and writing the lines in winnt.sif?

mr_smartepants

06-11-2009, 01:14 AM

LOL, yes.
If you look at the entries file, the RVMI only copies the directories, then makes an entry in the winnt.sif file. If you feel you can perform those tasks manually, knock your self out! :D
I'm not planning on making major changes to how the integrator works on this addon. So for the future, just drag/drop the folders/files and you'll be perfectly fine.

Now if you start over with a clean source, run the RVMI.

mchallis

06-13-2009, 09:06 AM

This is probably a false positive....

Kaspersky 2009 is reporting Trojan-Downloader.Win32.Agent.cfhl virus in setkey.exe

F:\1download\OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MU LTIOEM_1.8.09_empty\KEYS\2003\WEB\setkey.exe//PE_Patch.UPX//UPX

It repeats for every setkey.exe in the folder, and every setkey.exe found on my computer.

Anybody else have this?

i found this in a search ...
UPX is just a compressor for executables and dynamic link libraries to make them smaller
some scanners detect UPX as backdoor, virus or malware but its just a packer
http://en.wikipedia.org/wiki/UPX

mr_smartepants

06-13-2009, 11:02 AM

Yes, it's already been reported as a false positive. You can report it to Kaspersky as a false positive if you like. It's perfectly safe. :)

svenby

06-14-2009, 10:03 AM

It's the same problems in AVG free

mr_smartepants

06-14-2009, 11:34 AM

That's great. ;)
But it's still a false positive.
SetKey.exe has remained unchanged since it was released over two years ago.
Symantec Endpoint Protection 11 shows it clean (as it always has been).

gospeed.racer

06-22-2009, 08:29 PM

Have you guys run across a problem where the oembios files chosen are correct (per both the ones chosen by oemscan and also the tool made by Severach) and the proper key is being used (dude, its a Dell LOL) but still no pre-activation? I have went through all the Dell oembios files on this Inspiron 1000, and none will pre-activate it. I have NEVER had that happen on a dell before! No biggie- just curious if this has happened much.

mr_smartepants

06-22-2009, 09:27 PM

I personally have never seen that, but I can see how that might happen.
If the bios slp string doesn't match (system has SLIC vista bios) or is a replacement board with a custom bios (unusual).

gospeed.racer

06-22-2009, 11:06 PM

yeah, neither of those are true which makes it very odd! I am trying to source the original disc so i can see what they used or oembios files and key. I have done stacks of older and newer Dell's without any issue- this one is odd!

ENU_user

07-20-2009, 04:09 PM

for none lap machiens this more of a debug message :

"OEMscan didnt find any oeminfo ..etc.. please report to mr_smartepants.. "

how different is this script from the cmd version you used before on the other thread ..anyways

maybe 2 versions:
1 with no debugging
a second 1 with just an OEMscan.log sent to the systemdrive hood ..

mr_smartepants

07-20-2009, 09:52 PM

Did it give an error #? Or were they just file copy errors?
The source for the .cmd is in the 3rd post of this thread. I just compiled it into an .exe.
I wasn't planning any further development in this project since it does everything I need it to.
I've released it as open source, you can do what you like with the code as long as you follow my wishes in the 3rd post. ;)

gospeed.racer

07-23-2009, 01:34 PM

Well, I have another card to shuffle into the deck! LOL
http://i27.tinypic.com/2hdm83q.jpg
It seems my HP machine wants to activate (and passes activation LOL) as a Tri-Gem:p

Any luck on that other method that was discussed earlier in the thread? I cant tell by the last post if you are done with this method, or all together:confused: Either way, thank you for everything!

mr_smartepants

07-23-2009, 09:39 PM

Lol :D

jimwatts

09-02-2009, 01:41 PM

When adding oembios files to oemscan util does anyone know do the oembios files have to be compressed or uncompressed also does it copy these over during install or overwrite installed ones after installation?

Many thanks

mr_smartepants

09-02-2009, 10:22 PM

When adding oembios files to oemscan util does anyone know do the oembios files have to be compressed or uncompressed

Read item #5 in the first post. ;)

This addon will copy the correct oembios set to the hard drive and overwrite the default set during XP setup (which is why they need to be decompressed first in the addon).

sansoo22

09-07-2009, 08:34 PM

I had a few quick questions if someone could clear them up for me that would be awesome. I've read through 3 entire multi-page posts about this subject but still had a few questions.

1. If I am creating a disc for a single computer like my Dell Laptop I could use Siginet's Add-on and then just put my SLP key in the winnt.sif where as mr_spmartepants method is better for creating a multi-oem disc for all the different laptops i maintain.

2. Considering legality. If say my Dell Laptop was given to me with an already hacked XP and no original media; is it still ok if i happen to "obtain" a Dell SLP and install the version of XP on the COA?

mr_smartepants

09-07-2009, 10:20 PM

1. If I am creating a disc for a single computer ... I could use Siginet's Add-on and then just put my SLP key in the winnt.sif ... mr_smartepants method is better for creating a multi-oem disc for all the different laptops i maintain.

2. Considering legality. If say my Dell Laptop ... install the version of XP on the COA?

1. Yes
2. Yes

sansoo22

09-07-2009, 10:48 PM

you guys F'n rock man. I've been trying to build a multi-oem disc for awhile now. So i can hand it to a family member and say stuff this in it and start over every time they don't take my advice and foul up their computer. Just so happens I stumbled across this page getting the new RVM integrator and you guys had the problem solved.

Thanks for all the hard work you guys have put in and the quick response to both of my questions.

mr_smartepants

09-08-2009, 12:18 PM

you guys F'n rock man.

Thanks for all the hard work

:D
You're very welcome.

kd6aaj

10-07-2009, 03:14 PM

Looks like you liked my OEMCOPY batch scripts! Well I "borrowed" the method from the MSFN forum (forget who posted it, sorry), but I had the Idea to copy the OEM logos and wall paper. :)

I've got other "Branding" ideas up my sleeves. I just need to start writing down my ideas, or I forget them...

Great work on the addon!!! I'll have to look at it to see how it works...

If I find the original poster of the batch I borrowed, I post his name.

Until later.

mr_smartepants

10-07-2009, 11:00 PM

If I find the original poster of the batch I borrowed, I post his name.

Awesome! I always give credit where credit is due. ;)

kd6aaj

10-14-2009, 08:13 PM

Wow, your OEMAUTO.EXE source make my batch look simple. Of course it's a combination of Siginet's OEMSCAN.INI, etc, but it is a thing of beauty!

OK, I figured out who I borrowed the code from when I wanted to copy the oem logos to the hard drive.

I borrowed the copy code from "FreeStyler"! He probably learned it from someone else, and so on...

So I give him credit, and everyone else here who helps. Thanks guys!

Awesome! I always give credit where credit is due. ;)

Here is the original poast from way-back-when...

09-20-2007, 08:48 AM

Quote:
Originally Posted by mr_smartepants
To copy a file to C:\ root, use %systemdrive%

Quote:
Originally Posted by mr_smartepants
BTW, I like your OEMCOPY.CMD. Do you know of a repository somewhere to get the oobe info/pics/eula and the oemlogo/themes?

Thanks, it's not originaly mine, I "borrowed" it from "FreeStyler" on the MSFN forum (POST # 213).

http://www.msfn.org/board/OEMScan_Au...54#entry610454

laddanator

10-16-2009, 12:52 PM

Hey guys just finished a beta version of my Vista scanner fully auto no menus to pick Manf PC from,sent mr_smartepants a beta copy to test before I release this on here also works for Win 7 been coding on this for months but I need to tweak it some to be used here my version has the slp keys and cert in the coding inside the program we are not allowed to give that stuff out here so my final will return value from a text file and folders to load keys and cert. This has been 100% affective with no false positive. Also working on a new XP scanner with same results

Pics below just finished loaded my buddy laptop on first log in activator went to work

mr_smartepants

10-16-2009, 11:25 PM

Yes, I've been going over the code and this looks good. This will be different from all those pirate loader/activator utilities because this one is 100% legal and uses M$ own pre-activation method, just like my oemscan addon. We need to work out the code to select the appropriate key based on the detected OEM and Vista/Win7 edition being installed. The detection code works, we just need to work on the "pluck" code to pull the key from a separate .txt file.

laddanator

10-17-2009, 05:18 AM

mr_smartepants wrote

Yes, I've been going over the code and this looks good. This will be different from all those pirate loader/activator utilities because this one is 100% legal and uses M$ own pre-activation method, just like my oemscan addon. We need to work out the code to select the appropriate key based on the detected OEM and Vista/Win7 edition being installed. The detection code works, we just need to work on the "pluck" code to pull the key from a separate .txt file.

Yes sir thats the part I am working on now need to recompile a few minor things but the key thing is not as easy but with your help mr_smartepants I think we could come up with something. Thanks and yes this way is 100% legal

mikemon

11-09-2009, 10:49 PM

I see you posted the source code for the oemauto.exe

I am very happy with your addon, i have a couple of issues. I work a pc repair shop, and preactivating windows saves us so much time, and effort when we have to get batches of computers ready to sell. The problem is sometimes our computers don't have cd roms or really exotic machines that need to be loaded via dos(hard drive install/winnt.exe). Basicly i was hoping you could be helpful and answer a couple of questions so i can modify or you can edit oemauto to support winnt.exe based installs

1st question: I am wondering if your source code(1st page in this thread) is the current version(1.8), or was that from an older perhaps first version you released? Because i noticed in a couple of post from people showing their winnt.sif that oemauto.exe used to be oemauto.cmd? And im not sure how you made the batch into an executable, but that is pretty nifty(and no im not asking how to decompile it, i just want to make it winnt.exe compatable)

2nd question: From looking at your source code

FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST "%%i:\WIN51" SET CDROM=%%i:
:: Below code checks for install CD. If disc not found then exit with error.
if defined CDROM (
goto VARIABLES
) else (
echo Windows source CD not found.
echo Please insert Windows CD and restart
goto ERROR
)

I see the C drive isn't included within %i(variable for installation source), Can i just make the following changes:

FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST "%%i:\WIN51" SET CDROM=%%i:
:: Below code checks for install CD. If disc not found then exit with error.
if defined CDROM (
goto VARIABLES
) else (
echo Windows source CD not found.
echo Please insert Windows CD and restart
goto ERROR
)

and hopefully it would continue the code and find C:\OEM\ETC(which is where they are located in winnt.exe based installers due to lack of cd-roms) and then be compatable with winnt.exe based installs?

and if so, i'm assuming i can change oemauto.exe into a oemauto.cmd and changes dependancies within winnt.sif files that look for $i\oemauto.exe to $i\oemauto.cmd

Thank you for your time

mr_smartepants

11-10-2009, 10:07 AM

Yes! You are absolutely correct on all your assumptions. Well done! :)
The code snippet you posted only checks for the presence of the device that my addon was integrated to. You can safely delete that portion if you use alternate methods to activate because that code will definitely interfere with any alternate methods. Although you wouldn't want to include "C" in the variable range because the variable %cdrom% is usually set automatically by the OS, my code just redefines it based on the criteria specified. Your OS might cough up a hairball, might not.

So to recap, just copy all the source code in my 2nd post to oemauto.cmd, then rename "oemauto.exe" to "oemauto.cmd" in winnt.sif and you're all set.

Edit the code to your hearts content! :)

Oh, and I use bat_to_exe_converter (http://www.f2ko.de/English/index.php). Very handy...and free.

zzz

11-20-2009, 10:43 PM

I'm having problem with this addon that I don't know how to avoid or fix. I've made WXP SP3 ISO disk with only this addon and in a process of installation within VMware I'm getting message that "OEM version of Windows NOT detected. Could not complete script". See this picture:
http://yfrog.com/0ooemscan01p

Later on, when setup is completed I test oemscan.exe within installed VM it recognizes OEM SLP string without a problem, reporting "Matched: STAR. Checking Authenticity of OEMBIOS files..." See the picture:
http://yfrog.com/0ooemscan02p
Problem with missing OEMBIOS.CAT file that you see on the picture is expecting at this time, because I did not put OEMBIOS set of files in C: drive (they are on installation media though). It's just a test of oemscan.exe and how it can find proper SLP string in BIOS. And as you see - it can do it well.

The question is - why it fails at installation time and how to fix it?

Some additional details:
1. VMware VM is configured to use BIOS from host computer and it actually does it well. I've checked it many times.
2. Host computer is MSI with SLP string "STAR" and I have proper set of OEMBIOS files that will be installed just fine, unless something prevents script to do so...
3. Before this test I run oemscan.exe file on host computer. It recognized SLP string and copied all OEMBIOS files to proper destination. So, I don't think it's a problem with this program or with my modified oemscan.ini file.
3. To make the test clear I've used this addon only (no others were used here).

mr_smartepants

11-21-2009, 08:14 AM

The question is - why it fails at installation time and how to fix it?

Well an "Error #1" failure means the script can't find a key file in your installation media. Specifically, the script is looking in your ISO for:
%dospath%\I386\SETUPP.INI
or
%dospath%\AMD64\SETUPP.INI
If neither file exists in your ISO, the script will fail. You should ensure that the file exists and you didn't delete it or rename it accidentally.
The variable %dospath% is found in the installed file %systemroot%\system32\$WINNT$.INF.
Did you modify my addon in anyway?
Can you post the contents of $winnt$.inf & setupp.ini here (remove your key first)?
Is this an English install or another language/locale install?

zzz

11-21-2009, 10:58 AM

Thank you for looking at my problem! I'll put my answers in order you've asked.

File SETUPP.INI is in proper place. It contains:
Pid=76487270
As you see Pid ends with 270 (VOL). And here is why. I've used VOL media as a basis. The idea is - if oemscan.exe recognizes SLP string it will replace set of OEMBIOS files, SETUPP.INI (with Pid=76487OEM) and proper PIDGEN.DLL file (OEM version differs from its VOL version). If it doesn't, I'll have the option to use VOL setup.

I did modify addon in this way:
1. I added proper files (OEMBIOS.*, PIDGEN.DLL, SETUPP.INI) into corresponding folders (e.g. \FILESETS\XP\E0A0735C for MSI)
2. I removed folders that I will not need (e.g. \FILESETS\XP\0D59FC53, \Logos\AcerSystem)
3. I've modified the file \KEYS\XP\XP_PRO\oemscan.ini by adding SLP match string and action for MSI:
[STAR]
PATH="..\..\..\FILESETS\XP\E0A0735C\"
CMD="SetKey 12345-12345-12345-12345-12345"
The rest is the same. I've made a new 7z file and used to make new ISO.

Here is content of WINNT.SIF (is that what you mean under "$WINNT$.INF"?) file:
[GuiUnattended]
DetachedProgram = CMD.EXE
Arguments="/Q /C FOR /F %? IN ('%SYSTEMROOT%\SYSTEM32\MOUNTVOL.EXE^|FINDSTR :\') DO IF EXIST %?OEM\OEMAUTO.EXE START %?OEM\OEMAUTO.EXE"

[Data]
AutoPartition=0
MsDosInitiated=0
UnattendedInstall="Yes"

As you see it's unmodified.

It is English install.

Why do I need to run "OEM\OEMAUTO.EXE"? Why I can't just simply run "OEM\OEMSCAN.EXE" to recognize the installation? For example, by modifying the line in WINNT.SIF file to:
Arguments="/Q /C FOR /F %? IN ('%SYSTEMROOT%\SYSTEM32\MOUNTVOL.EXE^|FINDSTR :\') DO IF EXIST %?OEM\OEMSCAN.EXE"

mr_smartepants

11-22-2009, 02:43 AM

Well, my addon was designed to be used on OEM source, not VLK. It'll fail for sure with your PID value.
It sounds to me like you need a specialized batch file instead of mine.

First, $winnt$.inf is a special file that is created during XP setup and placed at the root of %windir%\system32\. The contents of winnt.sif (and other files) are added to this file and used by XP setup. You can see this file once Setup is complete and you're sitting at the desktop.
My code is failing because I believe it can't find %dospath% in your file. That's why I asked to see it.

As far as I know, oemscan.exe will only copy oembios.* files, nothing else. You'll have to use a batch file to copy other files.

My addon was specifically designed to preactivate any XP OEM type (pro, mce, home) by scanning the installed system, selecting the correct key type, then executing oemscan from the correct folder and it copies the right oembios files and sets the appropriate key.

Why I can't just simply run "OEM\OEMSCAN.EXE" to recognize the installation?
You can! But you'll lose the ability to have a single addon activate all OEM types because oemscan doesn't discriminate between Home/Pro/MCE. If all you use is Pro, then you don't need my addon. :)

Feel free to use my code to make your own addon. Sounds useful, but I'll never have a need for it. Mine does exactly what I want.
Be careful how you go. Where you want to go you're treading a fine line between normal activation and EULA/License violation.

kof94

11-22-2009, 11:46 AM

@ZZZ

I think your looking for this: www.doitrightconsulting.net/forum/viewtopic.php?f=8&t=180 (go down to "RogueSpear's Windows XP VLK to OEM Converter Addon")

@mr_smartepants

I decided to make a few edits to your script for my own purposes but ended up rewriting some large chunks of it.

I hope you don't mind but I thought I'd post it here. It requires mtee www.commandline.co.uk/mtee and sleep.exe www.microsoft.com/downloads/details.aspx?FamilyID=9D467A69-57FF-4AE7-96EE-B18C4790CFFD&displaylang=en

@echo off
title=OEMScan
echo Scanning for OEM BIOS string. Please wait...

set CDROM=%~d0

path %PATH%;%CDROM%\OEM\bin

set logfile=%systemdrive%\oemscan.log
if exist %logfile% del /q %logfile%

set MCE="%CDROM%\OEM\SLP\XP\MCE"
set PRO="%CDROM%\OEM\SLP\XP\PRO"
set HOME="%CDROM%\OEM\SLP\XP\HOME"
set XP64="%CDROM%\OEM\SLP\XP\XP64"
set STANDARD="%CDROM%\OEM\SLP\2003\STANDARD"
set ENTERPRISE="%CDROM%\OEM\SLP\2003\ENTERPRISE"
set DATACENTER="%CDROM%\OEM\SLP\2003\DATACENTER"
set WEB="%CDROM%\OEM\SLP\2003\WEB"
set STANDARD64="%CDROM%\OEM\SLP\2003\STANDARD64"
set DATACENTER64="%CDROM%\OEM\SLP\2003\DATACENTER64"
set ENTERPRISE64="%CDROM%\OEM\SLP\2003\ENTERPRISE64"

setLocal EnableDelayedExpansion

:: DOSPATH
if exist %systemroot%\system32\$winnt$.inf (
for /f "tokens=* delims= " %%a in (%systemroot%\system32\$winnt$.inf) do (
echo %%a | find "dospath=" > nul
if not errorlevel 1 set str=%%a
for /f "tokens=2 delims==" %%a in ('echo !str!') do set dospath=%%a
)
) else (
echo Error: `%systemroot%\system32\$winnt$.inf' file not found 2>&1 | mtee /+ %logfile%
goto END
)

echo DOSPATH=%dospath% 2>&1 | mtee /+ %logfile%

:: ARCH
for %%a in (I386 AMD64) do if exist "%dospath%\%%a" set arch=%%a
if '%arch%'=='' (
echo Error: Windows installation files not found 2>&1 | mtee /+ %logfile%
goto END
)

echo ARCH=%arch% 2>&1 | mtee /+ %logfile%

:: PID
if exist %dospath%\%arch%\SETUPP.INI (
for /f "tokens=2 delims==" %%a in (%dospath%\%arch%\SETUPP.INI) do set pid=%%a
) else (
echo Error: `%dospath%\%arch%\SETUPP.INI' file not found 2>&1 | mtee /+ %logfile%
goto END
)

echo PID=%pid% 2>&1 | mtee /+ %logfile%

:: OEM
if not '%pid:~-3%'=='OEM' (
echo Error: Incorrect Windows version detected 2>&1 | mtee /+ %logfile%
goto END
)

:: Version
set version=%pid:~0,5%
:: Windows XP Professional / MCE
for %%a in (76481 76500 76392 76396 76413 76487 76440
76447 55375 55679 55274 55276 55285 55661
) do if '%version%'=='%%a' goto MCE
:: Windows XP Home Edition
for %%a in (76477 76475 76470 76460 76412 76381 55372
55677 55277
) do if '%version%'=='%%a' goto HOME
:: Windows XP Professional x64
for %%a in (55034 76588
) do if '%version%'=='%%a' goto XP64
:: Windows Server 2003
if '%version%'=='69712' goto STANDARD
if '%version%'=='69713' goto ENTERPRISE
if '%version%'=='69754' goto DATACENTER
if '%version%'=='69753' goto WEB
:: Windows Server 2003 x64
if '%version%'=='69770' goto ENTERPRISE64
if '%version%'=='69769' goto DATACENTER64
echo Error: Failed to identify Windows PID 2>&1 | mtee /+ %logfile%
goto END

:MCE
if not exist %dospath%\CMPNENTS\MEDIACTR\I386\MEDIACTR.CAB goto PRO
echo Windows XP Media Center Edition detected
%MCE%\oemscan.exe 2>&1 | mtee /+ %logfile%
goto END

:PRO
if not exist %dospath%\WIN51IP goto ERROR
echo Windows XP Professional detected
%PRO%\oemscan.exe 2>&1 | mtee /+ %logfile%
goto END

:HOME
if not exist %dospath%\WIN51IC goto ERROR
echo Windows XP Home Edition detected
%HOME%\oemscan.exe 2>&1 | mtee /+ %logfile%
goto END

:XP64
if not exist %dospath%\WIN51AP goto ERROR
echo Windows XP Professional x64 detected
%XP64%\oemscan.exe 2>&1 | mtee /+ %logfile%
goto END

:STANDARD
if not exist %dospath%\WIN51IS goto ERROR
echo Windows Server 2003 Standard Edition detected
%STANDARD%\oemscan.exe 2>&1 | mtee /+ %logfile%
goto END

:ENTERPRISE
if not exist %dospath%\WIN51IA goto ERROR
echo Windows Server 2003 Enterprise Edition detected
%ENTERPRISE%\oemscan.exe 2>&1 | mtee /+ %logfile%
goto END

:DATACENTER
if not exist %dospath%\WIN51ID goto ERROR
echo Windows Server 2003 Datacenter Edition detected
%DATACENTER%\oemscan.exe 2>&1 | mtee /+ %logfile%
goto END

:WEB
if not exist %dospath%\WIN51IB goto ERROR
echo Windows Server 2003 Web Edition detected
%WEB%\oemscan.exe 2>&1 | mtee /+ %logfile%
goto END

:STANDARD64
if not exist %dospath%\WIN51AS goto ERROR
echo Windows Server 2003 Standard x64 Edition detected
%STANDARD64%\oemscan.exe 2>&1 | mtee /+ %logfile%
goto END

:ENTERPRISE64
if not exist %dospath%\WIN51AA goto ERROR
echo Windows Server 2003 Enterprise x64 Edition detected
%ENTERPRISE64%\oemscan.exe 2>&1 | mtee /+ %logfile%
goto END

:DATACENTER64
if not exist %dospath%\WIN51AD goto ERROR
echo Windows Server 2003 Datacenter x64 Edition detected
%DATACENTER64%\oemscan.exe 2>&1 | mtee /+ %logfile%
goto END

:ERROR
echo Error: Failed to verify Windows version 2>&1 | mtee /+ %logfile%

:END
sleep 10
endLocal
exit

mr_smartepants

11-22-2009, 10:32 PM

Oh wow! You got logging working! That's awesome. I've been struggling for a while trying to get logging working. I could only ever get single lines. :)
Would you mind if I incorporated your ideas/code into a new version?

kof94

11-23-2009, 02:26 AM

Oh wow! You got logging working! That's awesome.

Thanks... I use tee a lot in bash scripts for logging, that's where the idea came from!

Would you mind if I incorporated your ideas/code into a new version?

Feel free.

I'm half way through adding a section that reads the PID from the registry to select each version. I know this wont work during install (at least not a T-39) but could be useful post install. I have no idea how to set the key though so it could be totally useless. It's a shame these scripts (http://support.microsoft.com/kb/328874) wont work for OEM versions.

One last thing... I'm not too enamored with the whole oem logos thing but these would be a lot better archived in the correct directories and then extracted to %systemroot% (aka fakeroot :)). Just a thought!

gospeed.racer

11-24-2009, 11:56 AM

Whehew! Talk of a NEWER VERSION? I LOVE it! Let me know if you need any testing done, finally got my test box back up and going again:)

kof94

11-24-2009, 01:41 PM

I wrote a section that pulls the PID from the registry. The whole thing is can be done in just a few lines but without a tool to set the key it's all kind of academic so I scraped it.

mr_smartepants

11-24-2009, 10:49 PM

I wrote a section that pulls the PID from the registry. The whole thing is can be done in just a few lines but without a tool to set the key it's all kind of academic so I scraped it.

That would still be handy to have. :)

kof94

11-25-2009, 02:09 PM

If you find it useful it was something like this

@echo off
for /f "tokens=3 delims= " %%? in ('reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v ProductId') do (
if not errorlevel 1 set pid=%%?
)

echo PID=%pid%

:: OEM
if not '%pid:~6,3%'=='OEM' (
echo Error: Incorrect Windows version detected 2>&1 | mtee /+ %logfile%
goto END
)

:: Version
set version=%pid:~0,5%

:END

TxPaul

12-15-2009, 05:03 PM

I used the OEM add on tool developed by Mr Smartepants to make a SLP disc. I get the following error: "Error#5. OEM Logo Copy cannot continue. Could not find any OEM Logo files in D:\OEM\Logos\is. Could not complete script." As instructed in the directions for the tool, I added in my OEM bios files, zipped with 7z and integrated using the RVM integrator. Is this a known error? I've triple checked my 7z file and it does contain the four folders and the multi ini file, and there are logos in each of the folders. So I'm stumped....Any suggestions?

---------- Post added at 07:03 PM ---------- Previous post was at 05:10 PM ----------

And in case it helps anybody to offer some suggestions, some additional information:

I just read the instructions for the nth time:
“Place your OEM logo files in the following directories:
Theme files (*.theme) go in the "themes" folder
Wallpaper files (.bmp .jpg etc) go in the "walls" folder
Everything else goes in the root of this folder.”

Which one is “this” folder. When I open the tool, there are four folders: FILESETS, KEYS, LOGOS, SVCPACK and the multioem.ini file. Inside the LOGOS folder there is a folder for each vendor, such as IBM or Dell. Inside each vendor’s folder, there are folders for walls and themes, a readme .txt, a logo bmp (for some vendors) and an OEMInfo.ini file. It is this readme.tx that contains the instructions quoted above, so I assumed that meant leave the logo where I found it. I added any missing logos and left them right in this location. Should I have put them somewhere else? If yes, where? I admit it, I’m script and programming illiterate. Where’s the “root of this folder” ?????

mr_smartepants

12-15-2009, 05:33 PM

I get the following error: "Error#5. OEM Logo Copy cannot continue. Could not find any OEM Logo files in D:\OEM\Logos\is. Could not complete script."
This is corrected in the next version of my addon. I've rewritten the code to take advantage of the awesome ideas by kof94. Obviously not finding the logo files is NOT a show-stopper.
But I don't know what system you're installing on. "D:\OEM\Logos\is" means the system "is" was identified. I've never heard of that. :confused:
My next addon builds a logfile with more details. I'll clean it up and upload it for you to use.

I just read the instructions for the nth time:
“Place your OEM logo files in the following directories:
Theme files (*.theme) go in the "themes" folder
Wallpaper files (.bmp .jpg etc) go in the "walls" folder
Everything else goes in the root of this folder.”

Which one is “this” folder.?
LOL, I meant the D:\OEM\Logos\*your_OEM_vendor_folder* or the folder where you opened the readme.txt. :)
Basically anything other than wallpapers or theme files go "loose" in the vendor folders. So if we use Dell as an example, then the folder layout looks like this:
D:\OEM\Logos\Dell\oemlogo.bmp
D:\OEM\Logos\Dell\oeminfo.ini
D:\OEM\Logos\Dell\oobeinfo.ini
D:\OEM\Logos\Dell\oemeula.txt
D:\OEM\Logos\Dell\OEMLOGO.JPG
D:\OEM\Logos\Dell\themes\default.theme
D:\OEM\Logos\Dell\walls\default.jpg

Hopefully that makes a little more sense. :)

*Edit,
See first post for link to new 1.8.2 update download. :)

TxPaul

12-15-2009, 06:42 PM

Many thanks !!! I grabbed the download of the new version and will try that. I'm building the disc starting with a genuine Windows XP Pro SP2 OEM disc, if that helps you make any sense of the error. Integrated in the Post SP2 Critical update file from the Siginet downloads. Then integrated in the OEM add-on separately as the last step. I'll start fresh and see what happens (new copy of files from original CD, fresh download of the post SP2 updates, then the new OEM add-on version last). Thanks for posting the new version, and I'll let you know how it goes. I can't promise this will be my last "stoopid" qustion, but we'll hope - do you or don't you put the original COA product key for the disc in the winnt.sif file so that it can be over written by the OEM scan? Seems like I read somewhere that this overwrite change was now necessary to make everything appear genuine - I think on the Microsoft site in the section concerning unattended installs. So I have the product key from my COA in the winnt.sif file under User data. Should I have that there? Or use none at all? And I did have the logos in the right spot from what you said in your reply. But only a .bmp. Do I need .jpg's also?

urie

12-16-2009, 02:16 AM

@ mr_smartepants, download link is not working :(

kof94

12-16-2009, 02:36 AM

Just my two pence....

One last thing... I'm not too enamored with the whole oem logos thing but these would be a lot better archived in the correct directories and then extracted to %systemroot% (aka fakeroot ). Just a thought!

You could make them 7z archives then use un7zip from the DriverPacks to extract them.

mr_smartepants

12-16-2009, 04:37 AM

do you or don't you put the original COA product key for the disc in the winnt.sif file so that it can be over written by the OEM scan?

Well you could put whatever you want for a product key in winnt.sif and if oemscan finds a match it'll overwrite whatever is there with a key that you put in the oemscan.ini file. I usually put nothing in my winnt.sif. ;)
But a COA sticker key will never authenticate online. And you really should consider slipstreaming SP3 for security.
Also, the OEM logos are not required, but add aesthetic value to the install. ;)

@ mr_smartepants, download link is not working :(
Working fine for me. The link in the first post brings you to the site's download section. The actual download is linked to the big "Download" button in the upper right corner. :)

@kof94, while that's a good idea, the dependent file "un7zip.exe" was created specifically for us over at DriverPacks.net. I'd have to contact the author to arrange for rights to redistribute with this project.

kof94

12-16-2009, 03:53 PM

Fair enough but you could just use 7z instead... it's LGPL so you can distribute it.

kof94

12-20-2009, 03:38 AM

More suggestions...

Replace this

FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST "%%i:\WIN51" SET CDROM=%%i:

for this

for /f "tokens=1 delims=: " %%? in ('mountvol.exe ^|find ":\"') do (
dir %%?:\OEM > nul 2>&1 && set CDROM=%%?:
)

if not defined CDROM (
echo something informative
)

or this

set CDROM=%~d0

Stops "no disk" error messages generated by empty card readers!

King_Jay16

12-27-2009, 08:34 PM

Hey guys, I am getting an error when i use the RVM integrator it says " Error: No entries*.ini Found, Exiting". Any ideas on what would be cauisng that? and when i try installing xp, it asks for a key, I am using a clean non-branded OEM disc SP2. Can someone give me some tips plz,

mr_smartepants

12-28-2009, 01:00 AM

Hey guys, I am getting an error when i use the RVM integrator it says " Error: No entries*.ini Found, Exiting".

Can you post the RVMI logfile? The answer will be in there.

King_Jay16

12-28-2009, 08:02 AM

Can you post the RVMI logfile? The answer will be in there.

Here you go
833

mr_smartepants

12-28-2009, 09:00 AM

Hmm. Odd.
Can you try using the latest beta build of RVMI?
http://siginetsoftware.com/forum/showthread.php?t=601
It's solved many bugs.

King_Jay16

12-28-2009, 09:56 AM

Hmm. Odd.
Can you try using the latest beta build of RVMI?
http://siginetsoftware.com/forum/showthread.php?t=601
It's solved many bugs.

Oh ok, will try it and get back to you, thanks for the help so far

ENU_user

02-24-2010, 04:33 AM

if nothing worked simply delete RVM\Plugins\7zip\ folder
this can happen when the 7zdn.exe gets corrupted or locked all 7z, rar, zip - based addons won't extract.. thus rvmi is finding no entries.ini to work with..showing that error..

(@Dev.. note) a workaround is to make rvmi unfold this file to some other temp folder
@
- looking to kill the process if locked..then - copying it over to its needed location
- replacing the file under RVM\Plugins\7zip\ at every run..

jradomski

03-19-2010, 07:18 PM

the current version is having the program setkey.exe being flagged by a trojan by over 25 of 45 virus scanners... Any way to correct this for the next release..

gospeed.racer

03-19-2010, 10:55 PM

(from what I understand) only by submitting it to each of the virus scanners for testing. Since it is capable of doing...well, stuff that virus' could do...it is considered dangerous until proven otherwise. Hopefully i am wrong, but this was my understanding from other programs that have this same issue.

mr_smartepants

03-19-2010, 11:52 PM

setkey.exe is clean when I scan using Symantec Endpoint Security and ESET NOD32. setkey.exe is not mine. It was written by FreeStyler (I think).
Some low-quality A/V programs will flag programs compiled with autoit or cmd2exe as virus-like when no danger exists.
It's a false positive.

jradomski

03-20-2010, 09:44 PM

I am not really worried about being a virus, its more of a pain in the ass thing... I have had the files deleted more than once on me when I have hooked up an external drive to a machine that doesnt have an exception set.. Norton is the worse as it permanently deletes teh file, at least programs like avg quarantine it and it can be recovered..

mr_smartepants

03-20-2010, 11:52 PM

Wait a sec. What version of Norton are you using? How is it that your Norton A/V is flagging setkey.exe yet my Symantec A/V is not? Do you have Heuristics enabled?
I would definitely suggest submitting it to the A/V vendors for analysis/exclusion.

user_hidden

03-22-2010, 02:51 PM

File: setkey.exe
CRC-32: b0290bfb
MD4: 04b5d542bbe8c768cae72346ba6431c2
MD5: 81143d15f738ad0712be20cdfd1bc92f
SHA-1: fad4083d8ef68606ddc4e03dc35eb03f100da2ce

Symantec A/V Corp 10.1.8.8000 = no threat found !

RudeBoySes

03-31-2010, 03:24 PM

Great Info. and Sharing!

I was directed here for this particular post ...
i have been integrating OEMBIOS files individually for another site..
the problem is this is for individual brands and time consuming..

fortunately.. urie pointed this site out to me..

i appreciate the time you took to post this and share ..

i downloaded this ADDON posted on page 1 but there are files you describe in the instructions that are not included .. more than likely.. it's probably due to my noobness ..

but can you clarify this part for me?

4. In the addon, go to the FILESETS folder and open the folder using the same name as listed on the OEMBIOS website (eg. \FILESETS\XP\376E13C7)

i don't see the FILESETS folder .. or OEMSCAN.ini ?

all i see are "Drivers" and "OEMBIOS" folders .. ?

thanks

mr_smartepants

03-31-2010, 10:35 PM

LOL, you downloaded the extra 'tools'. The addon is linked right above that here (http://integrator.siginetsoftware.com/index.php?addons&id=224):D

RudeBoySes

04-01-2010, 08:26 AM

LOL, you downloaded the extra 'tools'. The addon is linked right above that here (http://integrator.siginetsoftware.com/index.php?addons&id=224):D

omg.. how silly of me .. now it makes sense :)

thank you very much for the prompt response ...

i will try this and hopefully i do not run into any problems :)

F.Y.I
Great Site & Tool

FreeStyler

04-02-2010, 01:54 AM

Attached you will find a new version of the SetKey program, False virus warning should be gone now for most virus scanners

mr_smartepants

04-02-2010, 06:14 AM

Attached you will find a new version of the SetKey program, False virus warning should be gone now for most virus scanners

Woohoo! Thanks FreeStyler. Always a pleasure to see you around these parts.

FreeStyler

04-02-2010, 09:23 AM

MSE got totally crazy when i tried opening the latest version of your OEMSCAN_ADDON... apparently the old autoit script packager i used on SetKey is flagged as a virus by quite a few virus scanners... The new version only is marked once using VirusTotal

Symantec 20091.2.0.41 2010.04.02 Suspicious.Insight

RudeBoySes

04-02-2010, 02:39 PM

thanks for your help Freestyler & Mr_Smartepants..

i got it to work :P
after much confusion.. my problem was the ISO i was using..
i am now going to test multiple OEMs via VMware to ensure it's not luck ..

thanks for this post and sharing your knowledge :)

mr_smartepants

04-05-2010, 05:13 AM

Updated addon to v1.8.5 using FreeStyler's SetKey.exe v1.0.0.1
No other changes.

mr_smartepants

04-15-2010, 12:58 PM

Source code on post #3 removed due to pirate abuse. Apparently, this addon is VERY popular now on common warez sites. Because of this, I'm removing the source code and only releasing the binaries.
Too many idiots are claiming ownership of my work. To those individuals..."Fuck You!" :mad:
Obviously, regular posters to these (and other) forums that I determine to operate within the law will be granted access to the source code freely upon request.
Version 1.8.5 had a minor bug. I'm updating to 1.8.5.1 to fix this as well as add additional OOBE file copy options.
To reiterate my intentions: I made this addon for legitimate use by professionals. This is NOT intended to circumvent M$ licensing provisions. Go legit or go home.

mr_smartepants

04-19-2010, 11:04 PM

gospeed.racer

04-20-2010, 06:31 AM

Updated script to 1.8.5.1 to fix OOBE filecopy bugs and other optimizations.
\Logos\*\oobe\ folder now exists for additional files.

I'm still working on a "manual over-ride" option for when the autoscanner fails. Real life keeps interfering though.

good to know you are still looking for ways to improve this 'ol program! It has worked very well for me in the past, and can only get better with that there manual override. If you need a tester let me know, I try to keep a couple oem manufactured pc's around just for this type of testing :p Real life (work) keeps interfering with my life too....sucks!

And +1 on the people stealing credit for your work, thats a bunch of crap:mad:

mr_smartepants

04-20-2010, 08:25 AM

And +1 on the people stealing credit for your work, thats a bunch of crap:mad:

Thanks. I thought about posting the links here to all the different versions I found with this addon rebranded with other names (to shame their users), but that would just encourage more piracy.
First post updated and fixed 'empty' addon. I still cannot upload the 'full' addon with all the OEM logos folders filled. The filesize is only 32MB but Siginet's addon web applet keeps choking on it.

user_hidden

04-20-2010, 11:07 AM

First post updated and fixed 'empty' addon. I still cannot upload the 'full' addon with all the OEM logos folders filled. The filesize is only 32MB but Siginet's addon web applet keeps choking on it.

you can upload it to mediafire for FREE :)

thanks for doing a great job with this addon.

mr_smartepants

04-20-2010, 01:38 PM

you can upload it to mediafire for FREE :)

Indeed! Mediafire link added!

gospeed.racer

04-20-2010, 08:59 PM

Nice:) Very helpful! I have mine already built up, but this is a real time saver for most new users:cool:

johnk963

04-21-2010, 01:50 PM

Has anyone gotten this addon to work with 1.0 betas of WinSetupFromUSB (http://www.msfn.org/board/install-windows-winsetupfromusb-t120444.html)? I've gotten it to work with v.23 by copyng the appropriate win51* media tag files to both the root of the USB drive as well as to the directory that the utility copies the install files to, but nothing I have tried makes it work with any of the newer versions. The benefits for the newest version are that you can have a shared OEM folder between different Windows installs and you only have to boot from the USB drive once in most cases. The old version requires booting from the drive twice to complete Windows setup.

mr_smartepants

04-21-2010, 11:30 PM

I've never heard of that utility. But it sounds cool! I'll try it out and maybe update this addon to support it (and other USB boot tools). My script looks for specific files/folders for disc-based installs. I just need to adjust the code to look elsewhere.
Thanks for the suggestion.

1337

04-22-2010, 07:36 PM

Hi sorry, tried posting this in the regular forum, but my message doesn't seem to be showing up for some reason. Anyway,

------------------------------------------------------------------------------

Ok, I followed the directions for using OEMscan to the T...exactly and precisely...using this: http://siginetsoftware.com/forum/showthread.php?t=541

Tried with both XP Home SP3 OEM source (not Dell or anything, true generic OEM disc) and an XP Pro SP3 slipstreamed OEM Dell disc source...Same error. The XP Home SP3 disc is untouched. Just ripped files from the ISO.

Tried integrating from a different PC running Windows XP, same error.
Checked md5 sums of all files (rvm integrator, oemscan addon) and all are good.

I can't seem to shake this problem, please help!

Logfile Contents:

2010-04-22_20.25.46
Log Startup @ 20:25:46 local time, on April 22, 2010.

Running OS: WIN_XP Service Pack 3 X86
RVMIntegrator v1.6

"C:\Documents and Settings\HP_Administrator\Desktop\RVM_Integrator_1 .6\RVM_Integrator_1.6.exe"

20:25:46 - English - Windows XP Professional x86 - OEM SP3 Found
20:25:52 - English - Windows XP Home x86 - OEM SP3 Found
20:26:02 -
20:26:02 - Source Drive = C:\ISOs\XP HOME SP3 CONTENTS
20:26:02 - Destination Drive = C:\ISOs\XP HOME SP3 CONTENTS
20:26:02 - Destination Size = 21.49 GB
20:26:02 - Working Directory = C:\ISOs\XP HOME SP3 CONTENTS\I386
20:26:02 - Temp Directory = C:\ISOs\XP HOME SP3 CONTENTS\I386\rvmtemp
20:26:02 -
20:26:02 - Starting Integration
20:26:02 -
20:26:02 - Checking Destination For OS Type.
20:26:02 - English - Windows XP Home x86 - OEM SP3 Found
20:26:02 -
20:26:02 - Extracting OEMSCAN_1.4.1_MR_SMARTEPANTS_ADDON_MULTIOEM_1.8.5. 1_empty.7z
20:27:10 - MD5 Hash = ce086ba7fb9048864667956559e0bd7b
20:27:10 - Clearing any Read Only Attributes.
20:27:21 -
20:27:21 - Gathering temp files
20:27:21 - Shifting Stuff Around
20:27:41 - 217 Files Moved in 19 Seconds

mr_smartepants

04-22-2010, 11:29 PM

1337, I replied in your original thread here: http://siginetsoftware.com/forum/showthread.php?t=740

TwoJ

05-10-2010, 01:41 PM

Hi smartepants

Each version gets better & better, i just put together a XP Home version, and the oemscan worked great, but it did have one problem that it validated the HP Pavilion as an ASUS, and although it did register it and pass the validation it still seems an issue with properly identifing the system if it has multiple hits.

I don't know whats the best solution, probably a dialog box if it determines there is more than 1 possible SLP OEM that will validate a system.

Do you have any ideas what the best way to avoid the mismatch of OEMs?

mr_smartepants

05-10-2010, 02:12 PM

One of the things I'm working on is to have the script document the available matches. If a single match exists, the script presses on as normal. If multiple 'hits' exist, then the user is presented a 'choice screen'. The problem I'm running into is the timing (among other things). If the user waits too long, the script misses a critical window and setkey.exe will not write to the correct file. The script must complete before T-37 passes or it will be too late.
At the moment, the script I'm working on does NOT work and is failing.
The main problem is HOW setkey writes the key and/or when the system reads the $WINNT$.INF.

Besides, my new job is taking a LOT of my free time. And with summer around the corner, I don't think I'll be able to spare much for the development of this project other than to say that there may be an update by the end of the year. ;)

TwoJ

05-12-2010, 12:07 PM

If i understand you, then you are saying that the windows installation continues starting at t39 (i'm guessing) and that setkey has to complete by T37 and setkey is an independantly run program that cannot stop (or hold) the installation program?

I wonder if there is a possibility of at what time was called fuzzy logic, where you assign a weight to a particular choice, for example in my case i has a positive result with ASUS & HP, and since asus is higher on the list it choose asus, but since the HP pavillion is using the asus motherboard we get the 2 choices. So in the logic we assign a weight of lets say HP=3 and asus=1, and if we have the 2 come up in a result like in my case a (HP or Asus) = boolean (HP or Asus) = (3 or 1) = 3, the higher numbers would represent OEMs who manufacture more 'complete systems' like HP & Dell, vs lower numbers that represent OEMs who manufacture Parts and systems, like asus & gigabyte.

The logic is that if you have a multiple OEM choice that there is more likely you have an OEM system like emachines that has a gigabyte motherboard than a Asus computer with a HP motherboard.

While i agree that having a dialog box where the installer can choose the OEM is ultimately the best choice, and granted the fuzzy logic is not a foolproof solution i think it would allow for a better hit ratio than with just doing in alphabetically or trying to play around with the list order.

gospeed.racer

05-12-2010, 10:11 PM

interesting thought..... :) Sounds like a good idea if it can be implemented

mr_smartepants

06-03-2010, 09:17 AM

One of the updates I'm working on now is actually a byproduct of the aforementioned timing problem.
I'm optimizing the code (ditching some excessive FOR-IF & Tokens= expressions) and I'm seeing a marked speed increase for the batch to complete. I'm working on the DetachedProgram call function to increase the speed there. No sense scanning all drives for a file when we can pull that from a single file. Should be about a 50%-200% speed boost depending on how many drives are attached at the time of install. :)

*Edit,
Yeah, changing a single line of code saved about 10 sec in the detection routine! :)
I'm sure there's more speed to be had, I'll keep plugging away at it when I get the chance.

gospeed.racer

06-05-2010, 06:24 AM

I was never unhappy with the speed! In fact it was sometimes nice to try and watch to see which flavor it was going to install so I could pull the plug if it went for the wrong one :p hahaha

Keep up the great work! :cool:

TheMAN

06-09-2010, 05:33 PM

I just ran a test install under vmware with a hacked bios... it works perfectly... I have a few hints to add:
-It is OKAY to delete extraneous directories you don't need (eg: disc is Home, so you can delete 2k3 and pro directories, and oemlogo directories that won't be used.... such as for a hp / compaq disc, delete acer, ibm, etc)
-Just like it's optional to use the oemlogos, it is also optional to use the themes/wallpapers... in this case for me, to save space, I deleted all the wallpapers and themes subdirectories but keeping the relevant oemlogo files I wanted
-In the oemscan.ini file, you can delete all the unused lines to prevent false detection (eg: hp / compaq disc, delete everything else but the hp lines)

It doesn't matter whether you make these tweaks before or after you integrate the pack. It will not break anything so long as you're using the disc for the specific system(s) you built the disc for.

I really appreciate the continuing efforts in improving and supporting this addon pack mr_smartepants! I do have one major thing to suggest:
if one manages to do the "full monte", the whole XP install disc becomes ridiculously bloated... while this isn't a problem as far as a working installation, it can be a problem in a practical standpoint. There's many older systems out there still that do not have DVD-ROM drives, and therefore requires the installation media to be on CD. From what I can tell, the oembios files on my slipstreamed dell discs (out of the real mccoys) are compressed (oembios.bi_, etc), while this addon pack does no compression on any of the files. This makes the footprint inefficient even though it works. Is there any possibility of compressing all of the files (in that funky microsoft LZSS format) so that it won't bloat the disc to over a gig? Even then, for ones like me who wanted to cut out most of the junk and make it for a few select manufacturers (I made an hp / gateway / toshiba disc), it was still difficult for me to make it all work into a >722MB ISO (I managed to do that after deleting all the extra crap I didn't need, such as wallpapers) after having to sacrifice real addons I had (such as all the .net frameworks, silverlight, windows defender, etc). Again, obviously the solution is to "get on with the times" and burn it onto a DVD, but this doesn't work very well with older systems you're trying to repair. :)