Jump to content

Bezalel

Member
  • Posts

    595
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by Bezalel

  1. Hey

    Back again.....

    I have used the dvd that I made on several different Pc's(HP,DELL), and they all worked fine.

    That was for the WinXp home edition.

    So I made the same thing for WinXp pro.

    I have read this; http://www.microsoft.com/technet/prodtechn...y/oempreac.mspx.

    As far as I understad it, I can use this key for Windows XP Professional.

    The OEMBIOS files are the same for Pro and Home..?, I have read something about that :angel

    Now I have a DELL PC that I have tried it on.It came with PRO pre. instaled.

    I have tried the MS key, the sticker key....but only the key that followed the org. cd works????!! in the

    oobeinfo.ini;

    [Version]
    ProductKey="MVF4D-W774K-MC4VM-QY6XY-R38TB"

    When winNt.sif prompts for key that's the one I enter, but it say's "Not Valid Key"

    Can someone help me???

    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.

  2. @Bezalel: The ASUS OEMBIOS Files on your share are corrupt. At least oemscan says that. I already double-checked my checksums with yours and they match, so there must be something wrong with the files on your share.

    Does anyone have correct ASUS_FLASH files?

    The files I have have a valid MS signature Pleas check your SHA1 checksums for verification.

    BIN 066bef4fddc580ce48759e852f557e68de8b8a73

    CAT 8e1fae9079ddb07f18d2d8f73cef4b7f44c90d39

    DAT b1e9e2751b3eceaaf1bcc0494ddbe0503ab19ad8

    SIG fa609577140e3d058b18791956443ec26e7607d3

  3. pauluk83, Did you get it fixed?

    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.

  4. I have succeeded in exporting the reg key responsible for allowing a Media Center 2005 install to join a domain, and I would love to be able to import it to the registry before it becomes read only. Is there a way to do this during Text Mode setup (just like SETUPREG.HIV), or early during GUI mode?

    Or is there another way to write to this READ ONLY key before it becomes so?:

    "HKEY_LOCAL_MACHINE\SYSTEM\WPA\MedCtrUpg\IsLegacyMCE" REG_DWORD from 0 to 1

    Any help would be greatly appreciated!

    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).

  5. Hey ive read almost every post in this topic, but didnt see an answer to my problem, or im just blind, lol.

    - I built my own computer

    - I presume I have a "Hacked" CD of Win XP Pro since the Windows Genuine Validation reports to me as having an illegal or pirated CD key when i update windows to a cetain point.

    - At that point i cannot get any more updates as i have an "Illegal" copy

    Would i be able to get the OEMBIOS files from another computer and use them with my "hacked" cd to get :

    - Preactivated install

    - Clean install without the Windows Genuine Validation reporting me having an illegal or pirated CD key

    If so, what computer should i use to get the OEMBIOS files from?

    A computer made by Dell, HP, Acer etc...

    Or, a computer with an OEM CD, also custom built...

    Or, a combination of both?

    And lastly would this cd that i create be able to be used on ANY computer i install it on, and would it work correctly on all different computers? My main concern is for it to work on custom built PC's, not so much PC's from Dell, Acer, HP etc.

    Sry for the long post, but thanks so much for any help i get that leads to the solving of my issue :thumbup

    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.

  6. i`ve got linux that i can boot into my computer memory (2 gb), it runs without the hd and is super fast.

    i know that there is usb stick version of windows, but is it possible to run xp just in memory?

    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)

  7. @FreeStyler: The dllcache directory doesn’t store .CAT files. After running sfc /scannow it only copies the BIN/DAT/SIG files. Weird, I checked it on multiple new installs and never saw an OEMBIOS.CAT file in that directory

    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.

  8. If Dell has provided you a real Windows install CD and not a crappy restore disk then you won't gain much by making your own.

    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.

  9. I've got an online friend who's only income is social security disability. One of his "friends" fixed up a cracked copy for him and it has a lot of problems. Getting $200 for a retail version is quite difficult for him. I was thinking about getting a copy for him and let him pay me of a little at a time.

    Joe

    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.

  10. @Bezalel

    Guess I’ll dig deeper into MGADiag’s code because the results you’re describing are different then mine. Sounds like you’ve been down this road before, any hint’s you’d like to throw?

    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.

  11. Sounds nice, right now I’m busy disassembling Microsoft’s Genuine Advantage code to better understand how OEMBIOS files work, I don’t have much time to add it.

    If you want a quick hacked solution.

    [AMI]

    CMD=".\PromptForChange.exe"

    [AWARD]

    CMD=".\PromptForChange.exe"

    [PHOENIX]

    CMD=".\PromptForChange.exe"

    put at the end of the oemscan.ini file will have the same effect as ELSE :)

    Or you could search for a string that appears in every BIOS.

    [SM]
    CMD=".\PromptForChange.exe"

  12. The SLP Strings for Gateway CRC set A04597C6 are ‘Gateway’ and ‘Gateway, Inc’

    I think multiple SLP entries refer to the number of different locations the string could be located. Here’s a partial list for gateway (CSI is on), I tested a few of them and they worked. Ohh and the region scanned is E000:0000 - F000:FFFF not F000:0000 - F000:FFFF

    These are the 32Bit addresses.

    000e46c0 = E000:46C0 (16bit address)

    000fe840 = F000:E840

    List of addresses removed

    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).

  13. Bezalel, please upload to Rapishare these obsolete files.

    eMachines 1B7F1F55

    Equus_Computer_Systems 397A095A

    NEC_&_Packard Bell 82D4D6A4

    >Have you got panasonic's OEMBIOS.

    Bezalel doesn't update Rapidshare right away. Panasonic will be there soon.

    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)

  14. 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;
    }

  15. Putting the word “Gateway” @ F000:E840 in my VirtualPC BIOS activates A04597C6 & C86378C7 OEMBIOS files.

    F000:E830											00 00				 ..
    F000:E840 47 61 74 65 77 61 79 00-00 00 00 00 00 00 00 00 Gateway.........

    Update:

    With allot of trail and error I found that you can put the word 'Gateway' anywhere between F000:E840 and F000:E85F and it will activate with C86378C7 and A04597C6.

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

  16. @Bezalel

    The previous character was CRLF so 0x0D, 0x0A, FSC SERVER, 0x20, 0x20, ....... 0x0D, 0x0A

    0x20 being SPACE.. perhaps it was reading all the spaces after the string.. hmm..

    I know it isn't case sensitive, Maybe it also treats all whitespace characters as it if were a space. 0x0D is considured whitespace.

    @Bezalel: I am asking about the rapidshare folder because you are also missing some common files. At least "Acer Travelmate" notebooks are sold very well and widely spread but your repository misses the files.

    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).

  17. I inserted the following strings into the bios to and used MGADiag to see if they pass, here are the results.

    CRC32: E161F004

    SLP: " FUJITSU SIEMENS, FSC SYSTEM, FSC SERVER, FUJITSU SIEMENS"

    Test 1: "FUJITSU SIEMENS" - FAILED

    Test 2: "FUJITSU FUJITSU" - FAILED

    Test 3: "FSC FUJITSU" - FAILED

    Test 4: "FSC SERVER" - Genuine

    Test 5: "FSC SYSTEM" - Genuine

    Test 6: "FUJITSU SIEMENS FUJITSU SIEMENS" - Genuine

    Test 7: "FUJITSU FUJITSU SIEMENS SIEMENS" - Genuine

    Test 9: "FUJITSUSIEMENS fujitsu siemens" - Genuine

    Test 8: "FUJITSUSIEMENSfujitsusiemens" - FAILED

    Test 9: "FUJITSUSIEMENS fujitsusiemens" - FAILED

    FUJITSU SIEMENS x 2 Works

    FSC SYSTEM x 1 Works

    FSC SERVER x 1 Works

    Interesting results

    BTW: E161F004 is listed with the wrong SLP

    <SLPBIOS> FUJITSU SIEMENS, FSC SYSTEM, FSC SERVER, FUJITSU SIEMENS</SLPBIOS>

    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.)

  18. OK We have bezalel' s rapidshare repository and Freestyler' s list of Strings (and missing files therefore). Could we establish a place where we can get everything together? I mean the files (including oemlogos), SLP Strings and Product-Keys? That would be great. Since bezalel is already a rapidshare user it would make sense to just complete his repository. :thumbup

    What do you think? :w00t:

    I also have another question: Why are there so many comma separated, same entries in the SLP Strings list? I mean, why is it 'Gateway,Gateway,Gateway...etc'? Or why 'AcerSystem ,AcerSystem' (whitespace)?

    OEMSCAN does only need one of these, nor? At least in the example ini.

    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.

  19. OK cool. As long as it wasn't our scripts that was the issue. That was my main concern. Thanks for the info. :D

    Another question...

    Is the Gateway fileset A04597C6 still needed? Since now we have a Gateway/Emachines fileset.

    My question is... if A04597C6 is still needed we may need to find the best way to have it implemented since both filesets look for the string "Gateway". Is there a different area of the bios it searches for the string then the emachines fileset?

    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.

  20. I found an old Dell Dimension that doesn't preactivate for me. I have tried with the old method and the new method I put together with the same results. :(

    Manufacturer: Dell Computer Corporation	  
    Model: L433c
    44656C6C 20436F6D 70757465 7220436F 72706F72 6174696F 6E202020 202020

    SLP=Dell Computer

    Debug.exe:

    -S F000:0000 FFFF "Dell Computer"
    F000:0EDF
    F000:0FE0

    With my new method it ends up finding a match and copying over the B6F0EEFD oembios.* set. Which is supposed to be correct right?

    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.)

×
×
  • Create New...