Bezalel

You need to use an OEM CD for your source files. If you Don't have an OEM CD you need to use the sutupp.ini from an OEM CD.

The files I have have a valid MS signature Pleas check your SHA1 checksums for verification. BIN 066bef4fddc580ce48759e852f557e68de8b8a73 CAT 8e1fae9079ddb07f18d2d8f73cef4b7f44c90d39 DAT b1e9e2751b3eceaaf1bcc0494ddbe0503ab19ad8 SIG fa609577140e3d058b18791956443ec26e7607d3

hello, sorry for the long delay, yes i did get that one fixed. now i have another questain, i am trying to build a preactivated cd for my mate, he is using a hp laptop that has a oem insall of xp home the crc of the oembios.bin is 57DBAB59 would i beable to install xp pro with this method * he has a legit xp pro cd and key* You're getting too close to the fine line between legitimate and pirated software. Personally I'd do it on my own PCs but not someone else's PC.

You can join a domain during setup because because at that point it is running Pro and hasn't been converted to MCE Yet. The values under "HKEY_LOCAL_MACHINE\SYSTEM\WPA" only become readonly after the next boot so you can make the changes after the value is written (I'm not sure when this value is created but I'd guess it is during GUI mode but before cmdlines.txt is processed).

This is a strictly no warez site so you won't get any help on your first issue. This method only works on computers manufactured by a Royalty OEMs(at least 1000 PCs or 100 Servers anually), it won't work on homebulit or Mom&Pop brands. The target PC must be the same brand as the source PC for this to work.

The dllcache is created at T-37 and at T-9 there is a full WFP scan so anything that got changed will be restored.

I've added the OEMBIOS set for American Future Technology Corporation. This is the Parent company of IBuyPower. I've also reuploaded all the current sets that were dropped by RapidShare. There are currently 37 sets. http://rapidshare.de/users/LWN7M8

I know of 2 methods to accomplish what you want to do. The first method is to create a ramdrive, copy your HD image to the ramdrive and boot from the ramdrive. The Second method is to use the Embedded Write Filter from XPe to redirect all write actions to a RAM overlay. (This isn't exactly what you asked for but it may be a better solution is you are willing to leave the boot media mounted)

On a fresh install there will be CAT files in the dllcache folder. These files are just leftover from the install process and are not restored when rebuilding the dll cache. Any solution that replaces the OEMBIOS files should make sure that the loftover obsolete CAT in the dll cache is removed or replaced to avoid further confusion.

Computers that are Built to Order usually come with a Windows Install CD. It is cost prohibitave to master a Restore CD and have an Authorized Replicator cut dies and press a CD for a single system. (It would cost more to make the CD than the computer is worth.) Computers that are Ready to Ship usually come with a Restore CD. Dell CDs are slightly customized Install CDs.

This wouldn't comply with the licence terms. You can only sell the software to your friend if 1 of the following conditions are met: You preinstall it on a new (or refurbished) PC that you are selling to him. For OEM copies with the New (Yellow) COA, you sell him a sealed Single Pack. Note that the outer package (padded mailer) must be sealed and still contain the System Builder Licence Agreement (SBLA) sticker. For OEM copies with the Old (Purple, Green or Blue) COA, you sell the software along with non-peripheral hardware and maintain a record that he agreed to be bound by the SBLA. You may make any payment arrangement that works for you.

From MS it is 2 CDs (or 3 CDs if it comes with Update Rollup 2) but royalty OEMs with reproduction rights usually put it on 1 DVD.

The OEMBIOS sets contain records protected by multiple methods of encryption and validated with mutiple signatures. I'm not going to explain how it is encrypted or post the unencrypted records. Instead I will post the records from one of the sets with the SLP string masked. fe00,0010,7,XXXXX f000,ff00,0100,XXXXX f000,8000,6000,XXXXX f000,0000,FFFF,XXXXX Each entry represents a range to search in and a string to search for (in this case all the strings are the same). There exist versions of this set with only the first 2 and 3 entries. I beleive that the first entry contains an entry error (Offset FE00) and no systems were produced with just the first entry. You can see from this example that manufacturers just append information to existing sets so their newer sets would still work on older systems.

You can hide the player with CMDOW.

Or you could search for a string that appears in every BIOS. [SM] CMD=".\PromptForChange.exe"

The 23 SLP strings in the A04597C6 set are all "Gateway", "Gateway,Inc" does not appear in the set. Some of the addresses you listed are valid and some are not. The actual region scanned is whatever the set specifies. The A04597C6 set searches through 2 256B regions and 21 32B regions. Since the regions are specified as 16 bit addresses any set that searches both the E000 and F000 offsets will have the same string listed twice (000EFFFF+1=000F0000 but E000:FFFF+1=E000:0000).

Actually you should use one of the public generic keys listed at http://www.microsoft.com/technet/prodtechn...depl.mspx#EWFAC.

I've uploaded the Matsus***a set as well as the NEC and Equus sets. The eMachines set was already in RapidShare. (I'm using the names Matsus***a and NEC because these names are a closer match to the SLP Strings)

What methods are you all using to read from the BIOS. I'm keep getting an Access Voilation error with the following code. int CmpStrToMem(char* Str,char* Mem) { int i; if(!*Str) return 0; if(!isprint(*Mem)) return 2; /* This line is causing the Access Violation */ if(tolower(*Str)-tolower(*Mem)) return 1; i=CmpStrToMem(Str++,Mem++); if(i>1) i++; return i; }

From the fact that you started at F000:E840 leads me to beleive that it wasn't just trial and error.

I know it isn't case sensitive, Maybe it also treats all whitespace characters as it if were a space. 0x0D is considured whitespace. I have all non-obsolete filesets in my RapidShare folder. I will upload obsolete files upon request (if nobody downloads them, RapidShare will drop the files).

All the Fujitsu Seimens SLP String have a space at the beginning of the sting. You may have gotten lucky with tests 4 and 5 and already had a space in the prevois byte. (If you didn't have a space I'd like to know what charcter was in that byte.)

I try to keep my RapidShare folder complete but some of the less common files are getting dropped by RapidShare. There are actually 23 seperate memory locations searched for for Gateway and the Acer string has whitespace in it.

Yes it is still needed because of the ranges they look in. Each of those filesets have 23 entries, 21 of the entries are in both sets but there are 2 unique entries in each of the sets.

Every Socket 423 (P4) or later Dell activated for me. I've had mixed results on Socket 370 (P3) based Dells. (I never got a Dimension L Series to preavtivate.)