Jump to content

Multi Manufacturer Pre-Activation


Recommended Posts

it is a key of my old laptop ( that is no longer in use, as i broke it )

i used

the following files and here is there crc values

OEMBIOS.SI_ - 3F656CBA

OEMBIOS.BI_ - DAA84E49

OEMBIOS.DA_ - 8C103EDD

OEMBIOS.CA_ - A6E560DE

and the winnt.sif file i modded anyway

hope this helps

Link to comment
Share on other sites


it is a key of my old laptop ( that is no longer in use, as i broke it )

i used

the following files and here is there crc values

OEMBIOS.SI_ - 3F656CBA

OEMBIOS.BI_ - DAA84E49

OEMBIOS.DA_ - 8C103EDD

OEMBIOS.CA_ - A6E560DE

and the winnt.sif file i modded anyway

hope this helps

Nope, doesn't help.

we need the uncompressed CRC32 for OEMBIOS.CA_

run "expand oembios.ca_ oembios.cat" from the command prompt and post the hash for OEMBIOS.CAT

Link to comment
Share on other sites

it is a key of my old laptop ( that is no longer in use, as i broke it )

i used

the following files and here is there crc values

OEMBIOS.SI_ - 3F656CBA

OEMBIOS.BI_ - DAA84E49

OEMBIOS.DA_ - 8C103EDD

OEMBIOS.CA_ - A6E560DE

and the winnt.sif file i modded anyway

hope this helps

Nope, doesn't help.

we need the uncompressed CRC32 for OEMBIOS.CA_

run "expand oembios.ca_ oembios.cat" from the command prompt and post the hash for OEMBIOS.CAT

ahhh wel the crc is 2B9D18CF if that helps

Link to comment
Share on other sites

>ahhh wel the crc is 2B9D18CF if that helps

That is the generic CRC for Single User License non preactivated CD's. A SLP key will be accepted if it's an OEM copy but it will demand activation and you won't be able to get it. Those files need to be overwritten with 4 files that are appropriate for your system. Have you followed these instructions to build a new CD?

http://www.msfn.org/board/index.php?showtopic=63258

The 4 OEMBIOS files do not need to be pulled from a running system. You can obtain the necessary files from Bezalel's Rapidshare

http://rapidshare.de/users/LWN7M8

NEC & Packard Bell E32D3612 looks like a good choice.

Google Packard Bell's PID to find a key.

0011903-00109

Link to comment
Share on other sites

New version of my OEMScan util

http://www.msfn.org/board/index.php?showtopic=82638

New Features in V1.3

Fixed bug in BIN/SIG/DAT hash check

Removes unused dllcache\oembios.cat file

Allows you to pass a custom argument to your script

Allows you to specify an exact range to search

Changed scan range from 0xF0000-0xFFFFF to 0xE0000-0xFFFFF

Dry Run parameter to validate OEMBIOS set. run oemscan.exe /d

Link to comment
Share on other sites

Looks like this project is slowing down a bit. ;) I guess that is because oemscan is working pretty well. :D I have to say it is great to not have to call to activate all the time anymore. :thumbup I think I have only had to call MS once in the past 2 weeks... whereas before I was calling them 1-3 times a day!

Link to comment
Share on other sites

Manufacturer: Dell Computer Corporation
Model: Dimension 2350
44656C6C 20436F6D 70757465 7220436F 72706F72 6174696F 6E

-D F000:E800
F000:E800 28 0E 00 00 00 00 01 00-00 01 00 01 02 00 00 00 (...............
F000:E810 00 00 00 00 00 00 1E 50-51 B8 40 00 8E D8 E9 9C .......PQ.@.....
F000:E820 07 77 61 72 64 20 E8 17-98 CB E9 73 FF 65 EB 29 .ward .....s.e.)
F000:E830 90 63 2E 20 41 77 61 72-64 20 53 6F 66 74 77 61 .c. Award Softwa
F000:E840 44 65 6C 6C 20 43 6F 6D-70 75 74 65 72 20 43 6F Dell Computer Co
F000:E850 72 70 6F 72 61 74 69 6F-6E 1E 56 51 BE 40 00 8E rporation.VQ.@..
F000:E860 DE 8A CC BE 1A 00 F6 C4-EF 75 27 51 E8 78 C0 59 .........u'Q.x.Y
F000:E870 FA 8B 04 3B 44 02 75 10-B8 02 90 CD 15 FB E6 EB ...;D.u.........
-

Link to comment
Share on other sites

Range	|	 String
________________________

0-FFFF | AcerSystem
0-FFFF | Compaq (2003)
0-FFFF | Dell System (2003)
0-FFFF | Founder PC
0-FFFF | FSC SYSTEM
0-FFFF | FSC SERVER
0-FFFF | FUJITSU-PC
0-FFFF | FUJITSU SIEMENS
0-FFFF | GREATWALL
0-FFFF | HEDYCOMPUTER
0-FFF0 | Hewlett
0-FFFF | Hewlett-Packard (2003)
0-FFFF | HP Pavilion
0-FFFF | IBM CORPORATION
0-FFFF | LEGEND Dragon
0-FFFF | LENOVO
0-FFF0 | NECC_
0-FFF0 | NEC-PC
0-FFF0 | NEC_Product
0-FFF0 | NEC Computers
0-FFFF | TCL123
0-FFFE | TravelMate
0-FFFF | TSINGHUA TONGFANG COMPUTER

E700-FFFF | AMOI Electronics CO.,Ltd
C000-FFFF | ASUS_FLASH
FE00-FFFF | BenQHub
49A9-49B9 | Dell System
E05E-E06E | Dell System
E076-E086 | Dell System
E840-E850 | Dell Computer
E838-E850 | Dell Inc
E840-E850 | Gateway
E710-E810 | $SAMSUNGPC
E600-E606 | MEI_CF
DFC0-E000 | Sony Corporation
FF80-FFFF | Sony Corporation
FF80-FFF0 | Sony Corporation
E800-E880 | Sony Corporation
8000-E000 | TOSHIBA
FF00-FFFF | TOSHIBA
FE10-FE17 | TOSHIBA

I'm assuming the list above means as long as that string is within that range they activate?

"(2003)" reflects Server 2003 and is not part of the string.

What i am trying to figure out is;

1). How can i take a range ..say "E838-E850 | Dell Inc" and know where in the Virtual PC DMI area to place that string.

2). Are some of the above ranges outside of the DMI area of the bios?

Having success with HP Pavilion & Virtual PC, i assume range "0-FFFF" is the Type 1 Manufacturer name feild of the DMI area, so i added it in the list although i havnt tested if ONLY that one string there works or if it must require it in the Type 2 area as well.

Edited by Randy Rhoads
Link to comment
Share on other sites

There are utilities that read the OEMBIOS.DAT file and output the unencrypted data, knowing the addresses contained within isn’t essential for a few reasons. If a bios contains “Dell Inc” chances are very good it’s a dell. With the exception of gateway all the current oembios file sets I’ve seen contain the obsolete filesets addresses and SLP strings. Collecting memory addresses and bios information isn’t vital to the project anymore. Collecting new OEMBIOS file sets is however.

A distinction needs to be made between specific ranges and broad ranges. For example HP Pavilion uses 0xF0000-0xFFFFF, that range encompasses most of the bios which includes among other things the DMI Tables. Dell uses 0xFE838-0xFE850 which is a very specific range inside the BIOS not the DMI tables.

I’m reluctant to give a detailed answer to your problem because the solution could very easily aid piracy and it isn’t necessary anymore

Like Siginet said, the project is slowing down. The next milestones are Windows 2003 & Vista support.

Link to comment
Share on other sites

I have to say it is great to not have to call to activate all the time anymore. :thumbup I think I have only had to call MS once in the past 2 weeks... whereas before I was calling them 1-3 times a day!
I hear ya there! with 150 systems to repair a month... pre-activation saves my life :P
Link to comment
Share on other sites

  • 2 weeks later...
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*

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

@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?

Link to comment
Share on other sites

@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?

Are you using version 1.3? There was a bug in 1.2.1 which reported false corruption.

I checked ASUS FLASH with 1.3 and they passed validation. If you used a CD maybe they were burned incorrectly, check the checksum’s on the CD.

OEMBIOS.CAT B20C65BF

OEMBIOS.DAT 8C3FD204

OEMBIOS.SIG 05858B8E

OEMBIOS.BIN C904A0D0

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...