[Rebeldawg]

I have a question, Is it possible to still create a pre-activated copy of windows if you don't have
access to the required cd? My Compaq Presario didn't come with a recovery cd of any type so I
had to make one and one of the cd's got a few scratches so it doesn't work as it should... Anyone
have any suggestions on how I can create a oem activated copy of Windows xp?

This post has been edited by Rebeldawg: 21 April 2007 - 01:03 AM

[severach]

Why not take the CD down to a place that offers scratch repair? They will let you know whether or not the scratches are fatal.

[Rebeldawg]

severach, on Apr 22 2007, 04:27 PM, said:

Why not take the CD down to a place that offers scratch repair? They will let you know whether or not the scratches are fatal.

I've tried using a program called Badcopy Pro to scan the cds for errors and it reported a lot of errors on the first cd so
I'm sure there are probably a lot of errors on the other 5 cds as well..

[FreeStyler]

Post #202 updated

HAIERCOMPUTER (OEMBIOS CRC=A94BE5ED)
EMACHINES (OEMBIOS CRC=5B886419) (obsolete)

thx to severach

[FreeStyler]

Added HI-GRADE (OEMBIOS CRC=AE805BAE)

This post has been edited by FreeStyler: 27 June 2007 - 06:52 AM

[AndyI]

ASUS_FLASH

00fe840: 4153 5553 5f46 4c41 5348 0000 0000 0000 ASUS_FLASH......
00fe850: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00fe860: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00fe870: 0000 0000 0000 0000 0000 0000 0000 523a ..............R:
00fe880: 4546 381d 2a36 8040 2010 0804 0201 e97f EF8.*6.@ .......
00fe890: 4900 0000 0000 0000 0000 0000 0000 0000 I...............

F000:DFC0 41 53 55 53 5F 46 4C 41-53 48 00 78 78 78 78 2E ASUS_FLASH.xxxx.
F000:DFD0 78 78 78 00 00 00 00 00-00 00 00 00 00 00 00 00 xxx.............
F000:DFE0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
F000:DFF0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................
F000:E000 EA 05 E0 00 F0 EA B2 A5-00 F0 84 64 00 00 49 42 ...........d..IB
F000:E010 4D 20 43 4F 4D 50 41 54-49 42 4C 45 20 49 42 4D M COMPATIBLE IBM
F000:E020 20 49 53 20 41 20 54 52-41 44 45 4D 41 52 4B 20 IS A TRADEMARK
F000:E030 4F 46 20 49 4E 54 45 52-4E 41 54 49 4F 4E 41 4C OF INTERNATIONAL

This post has been edited by AndyI: 09 July 2007 - 10:58 PM

[HexxKreator]

Hi I am new to MSFN but i read stuff on here before about slipstreaming stuff and unattended installs... but what i was wondering was what does this mean

'f000','c000','3fff','ASUS_FLASH'

I think it is in the bios somewhere but i have some questions..that any help would be greatly appreciated.

1) are they memory addresses in the BIOS?
2) if they are how would i get there Hex editor / other programs
3) and would "ASUS_FLASH" have to be in the f000 c000 and 3fff locations if it is memory addresses?

it has probly been said already if it has im sorry if you could point me to the post # or help it would be appreciated..

thanks in advanced

[Bezalel]

HexxKreator, on Jul 13 2007, 06:18 PM, said:

Hi I am new to MSFN but i read stuff on here before about slipstreaming stuff and unattended installs... but what i was wondering was what does this mean

'f000','c000','3fff','ASUS_FLASH'

I think it is in the bios somewhere but i have some questions..that any help would be greatly appreciated.

1) are they memory addresses in the BIOS?
2) if they are how would i get there Hex editor / other programs
3) and would "ASUS_FLASH" have to be in the f000 c000 and 3fff locations if it is memory addresses?

it has probly been said already if it has im sorry if you could point me to the post # or help it would be appreciated..

thanks in advanced

It means that the string "ASUS_FLASH" must be located within the 3FFF bytes of memory starting from F000:C000. These ranges are all in the BIOS.

[HexxKreator]

Bezalel, on Jul 14 2007, 11:13 PM, said:

HexxKreator, on Jul 13 2007, 06:18 PM, said:

Hi I am new to MSFN but i read stuff on here before about slipstreaming stuff and unattended installs... but what i was wondering was what does this mean

'f000','c000','3fff','ASUS_FLASH'

I think it is in the bios somewhere but i have some questions..that any help would be greatly appreciated.

1) are they memory addresses in the BIOS?
2) if they are how would i get there Hex editor / other programs
3) and would "ASUS_FLASH" have to be in the f000 c000 and 3fff locations if it is memory addresses?

it has probly been said already if it has im sorry if you could point me to the post # or help it would be appreciated..

thanks in advanced

It means that the string "ASUS_FLASH" must be located within the 3FFF bytes of memory starting from F000:C000. These ranges are all in the BIOS.

Is there a program or a way to play with an award bios to see those memory ranges? does the modbin6 with a hex editor find the ranges?

[Bezalel]

HexxKreator, on Jul 15 2007, 11:34 PM, said:

Is there a program or a way to play with an award bios to see those memory ranges? does the modbin6 with a hex editor find the ranges?

Debug.

s f000:c000 3fff "ASUS_FLASH"

Unfortunately debug is case sensitive and the SLP sting is not.

[warmo]

Hving read and reread in some cases the post in this thread im still confused I have a NEC Powermate VL4 and the original HD died and have now reinstalled XP home using a generic OEM CD could someone explain to me how i an retain the original oem reactivation for this pc please.


I have the original OEM Bios files off the net

and here is the computer report provided via the script off the forum

Manufacturer: NEC Computers International
Model: POWERMATE VL4
4E454320 436F6D70 75746572 7320496E 7465726E 6174696F 6E616C

i think the problem is im using a acer SLP key do i need a generic one for NEC?

This post has been edited by warmo: 05 August 2007 - 09:02 AM

[HexxKreator]

Bezalel, on Jul 17 2007, 12:15 AM, said:

HexxKreator, on Jul 15 2007, 11:34 PM, said:

Is there a program or a way to play with an award bios to see those memory ranges? does the modbin6 with a hex editor find the ranges?

Debug.

s f000:c000 3fff "ASUS_FLASH"

Unfortunately debug is case sensitive and the SLP sting is not.

how would i use debug to view a a bios file with a specific address...i don't know how to use the debug command in windows, i looked it up somewhat and i don't really understand it.

also could you edit the bios with debug and save it? just to play around with the bios

[TwoJ]

severach, on Sep 29 2006, 07:05 PM, said:

>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

I've got a Windows XP Home CD, i assume it is OEM, and i just got the CRC32 of the oembios.cat file as 2B9D18CF
If i understand from severach, this is a general (generic) OEMBIOS files.

What i don't understand is that since this will not eliminate the need for activation, which would be the case for the retail versions, then what is the point of having the oembios files?

[severach]

2B9D18CF isn't the set you want, it's the set you get rid of when you make the preactivated CD. The OEM CD starts with 2B9D18CF and along with the SLP key you overwrite those OEMBIOS files with the ones that match your machine. If you fail to overwrite them correctly the 2B9D18CF gets installed which will result in a system that requires activation. Checking the CRC of the installed OEMBIOS.CAT shows whether or not the OEMBIOS files were copied correctly.

[TwoJ]

thanks severach

But i think i didn't explain my question properly;

I am trying to understand why there would be a oembios file (2B9D18CF) since my understanding is that the normal oembios file (such as HP/Dell/etc) are to pre-activate the computer.

hense what purpose does the oembios file (2B9D18CF) serve if it cannot pre-activate the computer?

Is it like a requirement that all OEM windows copies have a OEMBIOS file?

If this was the case then i guess one could use it as another test to see if the computer uses SLP?

[Bezalel]

TwoJ, on Sep 18 2007, 12:35 PM, said:

thanks severach

But i think i didn't explain my question properly;

I am trying to understand why there would be a oembios file (2B9D18CF) since my understanding is that the normal oembios file (such as HP/Dell/etc) are to pre-activate the computer.

hense what purpose does the oembios file (2B9D18CF) serve if it cannot pre-activate the computer?

Is it like a requirement that all OEM windows copies have a OEMBIOS file?

If this was the case then i guess one could use it as another test to see if the computer uses SLP?

They don't serve any purpose when normal activation is being used.

[TwoJ]

Bezalel - Not that i want to beat a dead horse, but

Do you think that the 2B9D18CF BIOS set could be used for pre-activation? i remember reading one post where the SLP 'Key' (ie usually the OEM name) was encrypted into the dat file, and that some people had the tools to decrypt the dat files.
Is it possible that the 2B9D18CF BIOS set has got some string like 'Pheonix' that it searches for in the BIOS which would allow it to pre-activate the system?
I realize that it would mean that pretty much all BIOS manufactures would have to incorporate the string into their bios so that it would activate but other than that it seems like the generic 2B9D18CF BIOS set is useless and so why include it on the CD?

[ZaForD]

TwoJ said:

it seems like the generic 2B9D18CF BIOS set is useless and so why include it on the CD?

Thoses files maybe useless for activating the OS, but aren't they used to save MS [and us] alot of messing around with setup files, by working as place holders.

[andrewwan1980]

Manufacturer: Dell Inc.
Model: Dimension 8400
44656C6C 20496E63 2E202020 20202020 20202020 20202020 20


Does this mean I can use a MSDN MCE2005 (which is like retail Pro) and put in my OEMBIOS files into it plus modify setupp.ini to make it take in OEM keys. Will this work Bezalel?

[nyep]

Hi, Does anyone have the OEMBIOS files for an IPEX? The COA shows 'Windows XP Professional - IPEX Computers' so I am assuming this should be a royalty OEM??? The HDD has crashed. Regards Norman