Bezalel

Debug isn't scriptable but you can get around this limitation with a combination of AutoIT and redirecting stdout to a file. (I never tried this but in theory it should work.)

Run MGADiag and copy the results to the clipboard, the report will show the first 4 SLP strings. (The GUI doesn't show the strings.)

Take a look at Knowlegde Base article 326246 How to replace lost, broken, or missing Microsoft software or hardware.

The next version will be 8.3 compliant, the files will be in directories named according to the CRC32 hash of the CAT file at the same level as the program file. If I ever deside to make archive files of the directories I'd use CAB because it's the easiest format to implement.

There is a page on this topic on the System Builder site. http://oem.microsoft.com/script/contentPag...x?pageid=555866. I install the WSUS registry keys from my unattended CD and remove the keys using SysPrep. I don't run SysPrep until my WSUS Server reports that the PC is up to date.

Is it possible to run SysPrep at T-12? I want to have a fully unattended CD that reboots directly into the Mini Setup Wizard.

You will need to become a Royalty OEM before being allowed to distibute any Windows bits on external media. You are allowed to create a recovery partition and from my understanding of the SBLA you can also create an ISO of a recovery CD to allow the end user to burn their own CD.

No, You'll have to wait for the next version for a universal disk.

Rename them to match the hex string from the computer report (without the spaces).

The OEMBIOS files containg a encrypted list of strings and memory ranges. In the case of Dell, WPA searches a particular portion of the BIOS for "Dell Computer", "Dell Inc", or "Dell System". If you were to uses these files on a non-Dell the check would fail. The MGADIAG tool from MS will show you the first 4 strings in the list but will not show the memory locations.

The CD-Key is not Dell specific, you can use any Home SLP Key.

This thread explains how to make a Dell CD from an existing installation. This page contains a repository of manufacturer specific files (I've already cleared this link with one of the mods). You will need the SLP-WPA key for the installation.

It seems like as far as MS is concerned Dixon's is the manufacturer of both Advent and Philips PCs. I don't think Philips actually manufactures PCs, in the USA the computers that Philips sells to control their radiology equipment are made by Dell. Also I now have the correct "Dell Quanta" set in my RapidShare folder. http://rapidshare.de/users/LWN7M8

Everything I did was on Windows 2003. Windows XP might work differently. The fact that the key isn't documented doesn't seem to help. Try enabling Remote Desktop. I think this key was implemented for Terminal Server so it might have to be runnung for the key to work.

You can't disable the prompt but you can dismiss it after 1 millisecond. http://www.msfn.org/board/index.php?showto...mp;#entry462391

Wouldn't it make sence to check if there are any PendingFileRenameOperations and only prompt the user if they exist.

Bezalel, I am not trying to pirate, just test my cd without having to burn a bunch of cds. I was attempting to do the same thing as FreeStyle. I didn't just add the string randomly, i replaced a current string. But besides that, you must have missed the part where I said i tried it on a Dell Computer, and Inspiron 5100 to be exact. and it fails with the exact same problem, which is why i started working on vmware. so does the MGADiag tool show anything useful to you guys that may be able to point me in the right direction? originally i used regular oem media, with the slp key/oembios files, and then I was able to get my hands on a Dell XP Home SP1 cd, that had the correct OEMBIOS files/ original winnt.sif and $OEM$ directory, etc. I slipstreamed that to sp2. (I have not tried the original yet, to see if that would work). Try running the following lines in debug on the Dell and post the results. This should provide me with enough information to determine which oembios set you should be using. S F000:0000 FFFF "Dell Computer" S F000:0000 FFFF "Dell Inc" S F000:0000 FFFF "Dell System" S F000:0000 FFFF "Dell Quanta"

This thread may be of help since the structure is simular to MCE and TabpetPC. http://www.msfn.org/board/index.php?showtopic=72954

You can't just drop a SLP string into the bios, it needs to be within a specific address range. I will not elaborate further, this project is designed to allow you to use the same source on multiple machines that qualify for SLP activation it is not intended to bypass activation on systems that require activation.

I am planning to validate the files during the install process. I will be starting with the CAT and checking the CRC32 hash. Once I've validated the CAT I'll retreive the SHA1 hashes and validate the rest of the files. Since the CAT is the only file that can never be reused in another set it is the best source for a unique identifier. I'm not worried about someone hacking the CRC32 of the CAT because doing that would invalidate the CAT.

I think you will need both sets unless there is a set out there that has all 3 strings (Hewlett,Compaq,Pavilion) combined. If you remember my problem on a HP machine earlier in the thread.. it was fixed by using a HP PAVILION set instead. Any set that only included Hewlett or Compaq would install, but not activate. So far i have tested 4 OEM machines with success; 2 HP's with HP PAVILION 25330489 set 1 Compaq with CD4E1902 set 1 Sony with 376E13C7 set The only issue i had was using a "Hewlett" set on a HP that had HP PAVILION in the bios. I also tested a Abit NF7 retail board with HP PAVILION edited in and that worked as well, but failed testing the same process using Dell B6F0EEFD. The PC at 1st login screen would report the "Cant determine the license for the pc" and had a yes and no button to activate. Choosing NO would get you in a loop of the same error and choosing YES would load msoobe.exe which reported Windows was already activated, but the system would then just loop back to the login screen name and show the error all over and question to activate again. The determining question is: Does HP make a computer that does not have the string 'Hewlett' anywhere in the BIOS? I only care about official HP BIOSes not those that had their DMI tables edited by the und user. The SLP strings are not the least bit similar. There are many indications that HP is an OEM that does nothing more than insert the SLP String into Manufacturer field of the DMI so there's no reason to believe that they would always sprinkle Hewlett, Packard, or Compaq anywhere else. This is also the OEMBIOS set that HP & Compaq are using for all their Desktops and some laptops from 2005-. I was thinking logically not technically. There is a HPQ set that replaces all previous HP and CPQ sets. Wouldn't it make sence to also include the PAVILION strings if they were actually needed? I guess that end uses could test their BIOSes using debug S F000:0000 FFFF "HP PAVILION" S E000:0000 FFFF "Compaq" S F000:0000 FFFF "Compaq" S E000:0000 FFFF "Hewlett" S F000:0000 FFFF "Hewlett"If only the first line finds anything you need the Pavilion set If any of the other lines find anything you can use the HPQ set

With an OEM CD you can make a Manufacturer specific preactivated install by following this thread: http://www.msfn.org/board/index.php?showtopic=63258

i've been making some changes to http://rapidshare.de/users/LWN7M8. There are some important changes being made: 1) I'm using the CRC32 of the CAT file to name my filesets and not the CRC32 of the BIN file. It is possible for two different sets to use the same BIN file. (I haven't seen any examples but in theory it can occur). The CAT file contains the SHA1 hashes of the remaining files so any changes to any 1 file would result in a unique CAT file. 2) I'm listing each of the SLPBIOS strings instead of the manufacturer's name. (MGADIAG.EXE only lists the first 4 strings but some sets have more than 4 strings, Gateway has 22 strings.) 3) I'm listing which filesets are obsolete and what to replace them with. Any fileset that has been replaced by a newer set that includes all the strings in the origional set will not be included in this project. (From the 35 sets I have 9 are obsolete.) I currently have the following issues: The 'Dell Quanta' fileset I have has the wrong CAT file. (if cannot be included in this state) The A04597C6 'Gateway' and C86378C7 'Gateway,EMACHINES' filesets have 21 matching entries and 1 unique entry. Is there another set than includes all 23 entries? I need to know if there are any systems that require the 06D652A4 'HP PAVILION' fileset or can I replace it with CD4E1902 'Compaq,Hewlett'?

You should use a hologrammed OEM CD to start the project. To determine what went wrong in your case the best tool is the MGADIAG tool from http://go.microsoft.com/fwlink/?linkid=52012. just copy the report to the clipboard and post the results here. It also might help to run this tool on the Dell you got the key from. Also be prepared to provide the CRC32 hashes for the oembios files you have.

When they find your key on a warez site, until then you can activate by phone.