FreeStyler

thx the blank cd name fix will continue without problems

Added HI-GRADE (OEMBIOS CRC=AE805BAE)

Post #202 updated HAIERCOMPUTER (OEMBIOS CRC=A94BE5ED) EMACHINES (OEMBIOS CRC=5B886419) (obsolete) thx to severach

Here's the other file , seems we are only allowed to upload 200k per topic AutoIT Script source for the ones who might like to change path; #RequireAdmin #NoTrayIcon ; SetOEM $CD = DriveGetDrive("CDROM") For $I = 1 To Number($CD[0]) $pa = $CD[$I] & "\win51" If FileExists($pa) Then $instDrv = $CD[$I] EndIf Next RunWait(@ComSpec & " /C " & $instDrv & '\$OEM$\OEMSCAN.EXE>' & @WindowsDir & '\Temp\oemscan.log', '', @SW_HIDE) _SelfDelete() Exit ; Delete SetOEM Func _SelfDelete($iDelay = 0) Local $sCmdFile FileDelete(@TempDir & "\scratch.bat") $sCmdFile = 'ping -n ' & $iDelay & '127.0.0.1 > nul' & @CRLF _ & ':loop' & @CRLF _ & 'del "' & @ScriptFullPath & '"' & @CRLF _ & 'if exist "' & @ScriptFullPath & '" goto loop' & @CRLF _ & 'del ' & @TempDir & '\scratch.bat' FileWrite(@TempDir & "\scratch.bat", $sCmdFile) Run(@TempDir & "\scratch.bat", @TempDir, @SW_HIDE) EndFunc ;==>_SelfDelete SetOEM.rar

Crafted up a few new utilities that can help to automate the whole oemscan procedure. SetKey.exe SetOEM.exe Open TXTSETUP.SIF which is located on your installation source in the /I386 Directory Find [sourceDisksFiles] below add: setoem.exe = 1,,,,,,,2,0,0 Copy SetOem.exe into your installation sources /I386 Directory Open or create winnt.sif which also should be in your installation sources /I386 Directory Find or Add [GuiUnattended] Right under that line type: DetachedProgram=".\system32\setoem.exe" Copy SetKey.exe to the \$OEM$ directory on your installation source (OEMSCAN.EXE should be there as well) Modify OEMSCAN.INI to read something like: (replace bogus info with your own!) [BRANDNAME] PATH=".\BRANDNAME\" CMD="SetKey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" Example winnt.sif [UserData] FullName="n/a" OrgName="n/a" ComputerName=* [Data] AutoPartition=0 MSDosInitiated=0 UnattendedInstall="Yes" [Unattended] UnattendMode=Full OemPreinstall=No OemSkipEula=Yes [GuiUnattended] DetachedProgram=".\system32\setoem.exe" SetKey.rar

OK, i passed the genuine test, but i don't see MS Private Folder...wtf?

yawn

Oh no, you are kidding right? OEMLOGO.INI [Settings] OEMFilesPATH=[PATH] Manufacturer=[FULL VENDOR NAME] OEMName=[IMAGE PREFIX VENDOR NAME] \FILES [IMAGE PREFIX VENDOR NAME]_BADGE.BMP [IMAGE PREFIX VENDOR NAME]_BADGE.PNG [IMAGE PREFIX VENDOR NAME]_BAR.PNG [IMAGE PREFIX VENDOR NAME]_LOGO.PNG [IMAGE PREFIX VENDOR NAME]_MCE_LOGO.PNG [IMAGE PREFIX VENDOR NAME]LOGO.GIF OOBE.XML

Oemlogo.exe It's a little program that should automate the installation/uninstallation of Vista OEM related information,eg: OEM logo's and oobe.xml file, together with the required registry entries to correctly display them. Brands or custom logo can easily be made by changing settings in a ini file the program reads required information from. Also includded is a uninstaller, that can be accessed from Vista's Add/Remove Software controlpanel. Preview This version only suports the X86 platform for now. (i think) Only runs op Windows Vista OS Build in checks (if the files exists etc.) All file operations are completly hidden for user Uninstaller is included (C:\Windows\System32\oobe\oem_uninst.exe) Uninstaller can be started from Add/Remove Software controlpanel All opperations are logged (C:\Windows\temp\oemlogo.log) If errors occured, the program gives the user the opportunity to open the logfile automaticly to see what the problems are. All Uninstall opperations are logged (C:\Windows\temp\oemlogo.log) OEMLOGO.INI [Settings] OEMFilesPATH=[PATH] Manufacturer=[FULL VENDOR NAME] OEMName=[IMAGE PREFIX VENDOR NAME] \FILES [IMAGE PREFIX VENDOR NAME]_BADGE.BMP [IMAGE PREFIX VENDOR NAME]_BADGE.PNG [IMAGE PREFIX VENDOR NAME]_BAR.PNG [IMAGE PREFIX VENDOR NAME]_LOGO.PNG [IMAGE PREFIX VENDOR NAME]_MCE_LOGO.PNG [IMAGE PREFIX VENDOR NAME]LOGO.GIF OOBE.XML http://rapidshare.com/files/24423301/medion.zip.html (Program with MEDION logo's included, can be easily replaced with your own.) [fs]

thx X86, OK thats a good thing

BTW, Are the Registry entries in place as well? eg: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformation, "Logo" HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformation, "Manufacturer" Or are registry entries handled differently on X64? (and where should they be?)

I read somewhere that Vista X64 redirects X86 processes to \Syswow64\ and uses a X64 emulator to "fake" a 64 bits process. If you run above program on your X64 bits OS, are the oemlogos and oobe.xml copied to: C:\Windows\System32\oobe\ or to C:\Windows\Syswow64\oobe\ ?

Thx guys, Now i have 1 additional question, is what results one would get if a X86 OS is being used on X64 Processor Architecture PC? Anyone can tell me results of such setup? (eg: Vista 32Bit on 64Bits PC) @ButchN It's a little program that should automate the installation/uninstallation of Vista OEM related information,eg: OEM logo's and oobe.xml file, together with the required registry entries to correctly display them. On the page below you find a method using WinRar self-extractors, i have enhanced this so "brand" or custom logo can easily be made by changing settings in a ini file the program reads required information from. Also includded is a uninstaller, that can be accessed from Vista's Add/Remove Software controlpanel. http://www.msfn.org/board/index.php?showtopic=95062 Preview This version only suports the X86 platform for now. (i think) Only runs op Windows Vista OS Build in checks (if the files exists etc.) All file operations are completly hidden for user Uninstaller is included (C:\Windows\System32\oobe\oem_uninst.exe) Uninstaller can be started from Add/Remove Software controlpanel All opperations are logged (C:\Windows\temp\oemlogo.log) If errors occured, the program gives the user the opportunity to open the logfile automaticly to see what the problems are. All Uninstall opperations are logged (C:\Windows\temp\oemlogo.log) OEMLOGO.INI [Settings] OEMFilesPATH=[PATH] Manufacturer=[FULL VENDOR NAME] OEMName=[IMAGE PREFIX VENDOR NAME] http://rapidshare.com/files/24423301/medion.zip.html (Program with MEDION logo's included, can be easily replaced with your own.) [fs]

anyone?

I am writing a AutoIt program that needs to be compatiblewith both X86 and X64 versions of Windows Vista As i don't have access to a 64Bit box i need some environment variables from X64 Vista operating systems So X64 Users, Please download attached package below, run it and after that post the contents of the logfile in this topic (logfile is created in the directory the program is run from) thx, [fs] X64Check.zip

updated #202 with iQon.ie

updated #202

I Dunno, maybe it just me... but you could have checked the systems before you send them out, not ??? Just start the OS, if it isn't properly activated it will say within a few minutes

If they are any different then the ones available for download i would be glad to take them

I believe it's the x64 CD, CRC hashes of the Single COA/Retail Disc (only oembios.cat is different VS win3k) oembios.bin CE943F67 oembios.cat FB0B752E oembios.dat 9FF5BF35 oembios.sig C25EBB4E

That is great news. So does x64 have it's own set of oembios files or do they use the same ones as XP x86 as well? Anybody have a repository for other oembios files? I want to run some tests but I have none of the oembios sets from any of the oter systems besides x86 XP. x64 uses the same files as x86. Which is actually quite strange The orginal Windows XP Professional X64 COA OEM disc holds 3 files which exactly match the Server 2003 COA/Retail set

I received a positive report from someone who has been using oemscan on Windows XP Professional X64 Edition He ended up with a nice pre-activated install

@xehqter, Bezalel Alienware fileset available (thx ZaForD)

Vista OEM Activation OEM activation uses the resources of the Microsoft OEM partner or system builder to activate each operating system as it is installed. OEMs can install images based on both OEM and volume-licensed media during the installation process. Most systems that OEMs sell include a standard build of Windows Vista pre-activated by the manufacturer. Additional scenarios present themselves for large companies that negotiate system imaging with the OEM. This guide presents these scenarios for completeness, but they have no bearing on BDD 2007 deployments, which are designed to use volume-licensed media and applications. Drawbacks of OEM activations include reliance on the OEM for system imaging support and activation. Organizations that buy unloaded systems or that re-image systems on site will not benefit from OEM activation. Installing Volume-Licensed Images on OEM Systems For KMS activation to work, clients obtained through the OEM channels that have an ACPI_SLIC table in the system BIOS are required to have a valid Windows marker in the same ACPI_SLIC table. The appearance of the Windows marker is important for volume license customers who are planning to use Windows Vista volume-licensed media to re-image or upgrade OEM through the re-imaging rights provided in their volume license agreement. Not having the appropriate BIOS marker results in the following error or errors on these systems and prevents them from activating using a KMS: OEM Imaging of Volume Editions Organizations can choose to build a reference system using volume-licensed media. These images can be applied to target systems by the OEM; however, these systems require activation using either KMS or MAK methods.

What key is in your winnt.sif? maybe you just can't substitute a key with itself...eg: if you use the DELL key in winnt.sif it can't be changed with setkey.cmd as it is the holds the same key