Randy Rhoads
Content Type
Profiles
Forums
Events
Posts posted by Randy Rhoads
-
-
I can back this up. When i ran the command: S F000:0000 FFFF "HP PAVILION" it would not return anything. Using "HP Pavilion" instead, as it was exactly in the bios, returned the results in the areas i posted above.The SLP string 'HP PAVILION' may be in all caps but the BIOS contents is not. You'll do much better with:S F000:0000 FFFF "HP Pavilion"
Not every manufacturer uses WINNT.SIF but Dell does. This means you can construct a Home OEM cd for another Royalty system by changing the key in WINNT.SIF and overwrite the OEMBIOS.* files. The only drawback is that the Dell disk will include a few Dell only drivers that won't apply to your target system.For your convenience, you should obtain a trustable n-in-1 XP CD, find the complete OEM distributions on them, and learn which and how to modify the remaining non OEM distributions to make them OEM.
For OEM MCE i started with a clean retail XP Pro,
1) Slipstreamed to SP2
2) Added hotfixes (didnt use integrate commands) and Media Player 10
3) Added patched uxtheme.dll and custom billboard files
4) Added $OEM$\$1\drivers directory and copied 300MB of assorted drivers extracted from the driver packs files
5) Copied over manufacture specific OEMBIOS files inside I386 and included an edited OOBEINFO.IN_ with the manufactures specific MCE slp key edited inside it along with a WINNT.SIF with same slp key. Used SETUPP.INI from an Dell OEM MCE 2K5
6) Added CMPNENTS folder from a MCE CD 2 in the root source directory
Burned all as bootable DVD.
For XP PRO OEM CDR:
Just replace MCE slp keys inside WINNT.SIF and OOBEINFO with manufacture specific SLP XP Pro keys instead and skip the MCE CMPNENTS folder.
0 -
Here is the debug and crystal report on that HP machine:
Debug F000: "HP Pavilion" = F000:335EDebug E000: "HP Pavilion" = E000:0057
Debug F000: "Hewlett" = Blank
Debug E000: "Hewlett" = Blank
Debug F000: "Compaq" = Blank
Debug E000: "Compaq" = Blank
------------------------------------------------------------------
01 System Information
------------------------------------------------------------------
Manufacturer: HP Pavilion 04
Product Name: P7515A-ABA 531w
Version: 20000RE101LOMITA
Serial Number :
UUID (Universal Unique ID): E0FCFFCBE813D611B14DE593CE8452BC
------------------------------------------------------------------
02 Base Board Information
------------------------------------------------------------------
Type : 02h (2)
Length : 08h (8)
Handle : 0002h
Manufacturer : Trigem Computer, Inc.
Product : Lomita
Version : None
Serial Number : xxxxxxxxxxxx
------------------------------------------------------------------
------------------------------------------------------------------
11 OEM Strings
------------------------------------------------------------------
Type : 0Bh (11)
Length : 05h (5)
Handle : 0017h
Count : 01h (1)
OEM String 1 : HP invent
0 -
I only care about official HP BIOSes not those that had their DMI tables edited by the und user.
The problem i explained with the HP oem file sets were from an offical unedited HP machine. Any "Hewlett" oem set i tried on that machine would not pre-activate...only the HP PAVILION would.
The reference to editing dmi strings on the retail board were just to show that, it can be done, and the HP PAVILION set worked without having to include any extra strings like model and serial numbers and that the Dell set B6F0EEFD requires a more strict dmi setup. Older Dell oem files may not, but havnt tested those yet.
0 -
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'?
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.
0 -
Manufacturer: Sony Corporation
Model: PCV-RX640(UC)
536F6E79 20436F72 706F7261 74696F6E
------------------------------------------------------------------
System Information
------------------------------------------------------------------
Type : 01h (1)
Length : 19h (25)
Handle : 0001h
Manufacturer : Sony Corporation
Product Name : PCV-RX640(UC)
Version : 28440030
Serial Number : xxxxxxxxxx
UUID (Universal Unique ID) : 00000000000000000000000000000000
Wake-up Type : Power Switch
------------------------------------------------------------------
Base Board Information
------------------------------------------------------------------
Type : 02h (2)
Length : 08h (8)
Handle : 0002h
Manufacturer : ASUSTeK Computer INC.
Product : TUSL-LV
Version : REV 1.xx
Serial Number : xxxxxxxxxxx
Successful install of Media Center 2005 using:
OEMBIOS.BIN: CRC FA09A945
0 -
Did you run modifype on the edited file before placing it inside the I386?
If not, you will need to do this on any resource or hex modified M$ file you edit in the future before using makecab to compress it back.
Search the forum for modifype, should be a download somewhere, once downloaded just throw it inside your current system32 folder. This will fix the edited file so setup doesnt complain that it isnt original.
The command you use is:
MODIFYPE WINNTBBU.dll -c
It will reply, "No errors, have a nice day"
Now just compress the file with:
MAKECAB WINNTBBU.dll
I place both a compressed and non compressed file inside the I386
0 -
Manufacturer: Dell Inc.
Model: Dell DM051
44656C6C 20496E63 2E202020 20202020 20202020 20202020 20
OEMBIOS: 5D93572F
**Edited post with correct crc values.
0 -
Manufacturer: HP Pavilion 061
Model: ED898AA-ABA a1213w
48502050 6176696C 696F6E20 303631
0 -
Manufacturer: Compaq Presario 061
Model: PP150AA-ABA SR1303WM NA510
436F6D70 61712050 72657361 72696F20 303631
0 -
Welcome..on your screenshots i noticed you changed the tooltip color to white which is what i wanted to do, but didnt remember seeing where it was done.
I also think i will change the "On" "Off" selection images to say "Yes" "No" instead.
0 -
Here is a custom i threw together with a Vista flavor.
http://rapidshare.de/files/26130264/Vista_Wait_V23.rar.html
Edit: Changed "On-Off" images to "Yes-No"
0 -
File entries to be copied to your drive are inside TXTSETUP.SIF, but those files are not inside the I386 folder to be copied so you get an error. Sounds like the files were removed by Nlite, but the TXTSETUP.SIF file didnt get updated with those changes.
May have to start over with a fresh source and redo Nlite mods or remove the file entries inside TXTSETUP.SIF manually if you are positive those entries are the stuff you had Nlite remove.
0 -
Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
The Stop 0x7B message indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. Stop 0x7B errors could also indicate possible virus infection.
The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:
* Disks or storage controllers that are failing, defective, or improperly configured.
* Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.
Possible Resolutions:
* During I/O system initialization, the controller or driver for the startup device (typically the hard disk) might have failed to initialize the necessary hardware. File system initialization might have failed because of disk or controller failure, or because the file system did not recognize the data on the boot device.
* Repartitioning disks, adding new disks, or upgrading to a new disk controller might cause the information in the Boot.ini file, or Boot Manager, to become outdated. If this Stop message occurs after installing new disks to your system, edit the Boot.ini file or adjust the Boot Manager parameters to allow the system to start. If the error occurs after upgrading the disk controller, verify that the new hardware is functioning and correctly configured.
* Verify that the system firmware and disk controller BIOS settings are correct and that the storage device was properly installed. If you are unsure, consult your computer's documentation about restoring default firmware settings or configuring your system to auto-detect settings. If the error occurs during Windows XP Professional setup, the problem might be due to unsupported disk controller hardware. In some cases, drivers for new hardware are not in the Windows XP Professional Driver.cab library, and you need to provide additional drivers to complete the Windows XP setup successfully. If this is the case, follow the hardware manufacturer's instructions when installing drivers. Periodically check for driver and firmware updates.
* Hard disk corruption can also cause this Stop message. For more information about checking hard disk integrity, see the instructions provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.
* Problems that cause 0x7B errors might also cause Stop 0xED errors.
I would load bios defaults or try a bios upgrade and then load defaults. Next would be to download the hardrive manufactures dignostic floppy image and see if any errors show up..if not , do a low level format and retry the install over.
0 -
"Use MMTool 2.22.1"
That did it..thanks for the info and file.
0 -
After renaming the 256kb resource file to bios.rom, i try to load it up with MMtool v3.12 and i always get an error saying "Error loading rom image (10007FFh)
0 -
had the BIOS modifed with the SLP for that OEM
How are you going about this? Are you using one of the dos based apps like DMI.exe, etc?
I have M$'s VirtualPC 2004, but also have the older non M$ version..which one will i need installed and if you, or anyone else, can explain the process to patch the Virtual PC bios to test my ISO's i would appreciate it.
0 -
Thanks guys..i kinda thought the hotfix shortcut i took might be it but wanted to see if anyone has seen the disk do that if was something else.
0 -
I have been trying this and not having any success with an HP install. The HP machine came with XP Home installed ..drive crashed and lost all the original files and would like to create a restore disk for this machine with hotfixes and drivers.
I used an OEM Dell Home cd with SP1 as my source. Below is what i have done to the cd.
1. Slipstreamed to SP2
2. Copied over the svcpack folder and SVCPACK.INF file from an updated source so i wouldnt have to run all the integrate commands over.
3. Copied the OEM files for HP inside the I386 folder.
4. Used my custom Winnt.sif, which works fine on my retail source, with an HP SLP Home key.
Using the disk setup completes with no issues. At 1st boot all i get is the XP logo screen and then the system restarts and keeps doing this over and over.
Any suggestions?
0 -
Go with ither Abit or Asus because they seem to use good capacitors on there boards more often. Capacitors made by; Rubycon, Sanyo, Nichicons, etc are what you want to see on the board and psu.
Any board, reguardless of options, brandname, or price will serve you about 2 years before those cheap caps start to leak or dry out. This is what takes most psu's out as well.
0 -
If you are legal and/or can do without this garbage, but still want to install the "update", just find a "fixed" file, run modifype on that file, extract the original update exe file contents using winrar, swap the original file with the fixed file and rebuild the exe with winrar or simular app. This will run the update as usual but will install the fixed file instead. No nags and doesnt show as needed to be installed on Windows Update.
0 -
XP Home and Pro keys cant be mixed and matched. It would be easier to use just a single "master" backup of each retail version and edit in the customers OEM XP Home or Pro key, that came with there pc, inside the WINNT.SIF file matching the version they have, create any custom unattend.txt files for that pc, if needed, and then burn there restore cd which can then be activated online afterwards.
Once its done, just delete there key from the masters WINNT.SIF file, and just basicly reverse your steps to keep the master backup clean.
If you know how to add the updated drivers on the cd, you can also add them on the disk and simply swap the drivers inside the driver folders each time you make a new disk.
To free up some space for drivers, there are a few folders inside the I386 file that can be deleted. One is the LANG folder.
0 -
2) to "create a .ex_ file" run
CODE
makecab logonui.exe
from a command promt
Will need to use modifype.exe, which i attached, on any edited ".exe" or .".dll" system files before compressing them or Windows will reject the file during setup.
Just copy the modifype.exe file inside your system32 folder, open a command prompt and type:
MODIFYPE logonui.exe -c
Press Enter
It will display a message " No error occured, have a nice day"
Now its ready to be compressed using makecab.
0 -
Symantec Corporate 10 may work, but i dont have Vista to test it. Alot of these "broken" apps are probably just coded a specfic way to only accept certain versions so when the next Windows release comes out you have to plunk down cash for a new "compatable" version. This way, software makers can keep there seats on the M$ gravy train.
0 -
"The Option Pack Basic Edition will be USP5 + the updates (incl. IE6) from WU - excl NETFX and WMP9.
"The Option Pack Standard Edition will be USP5 + all the "official" component upgrades.
"
Oh, i didnt know you planned to include a IE6 inside your SP5 project ..i had thought that the IE6 and such would be single addons packs that would have to be installed after Windows setup by runonce. If you plan to make a SP5, that has IE6, and can be slipstreamed using standard M$ commands, then that is great and was my biggest need. Being able to slipstream IE6 along with the SP5 will reduce most people's cd source alot and just be a cleaner and faster install.
I would include DirectX 9 with that one as well though. Then people can exclude those during runonce and add other stuff they may need without having to do a IE upgrade beforehand and without having to turn to dvd.
0
Multi Manufacturer Pre-Activation
in Unattended Windows 2000/XP/2003
Posted · Edited by Randy Rhoads
Being this is a oem multi manufacture thread here are 6 multi manufacture XP MCE SP2 root folder "starter kits" for Dell, HP-Compaq, HP Pavilion, Gateway, Sony, and Toshiba that have custom setup.exe's, that reflect the OEM name, oembios.bin crc, and oembios slp string values and other root files needed.
I also edited setup.exe so it can run CrystalDMI and the computer report vbs. Also included the oeminfo and oemlogo files in the correct folders. The oeminfo file also reflects crc and slp bios values so edit these and the setup.exe to match the oem files you use if they differ from mine.
Just add your MCE SLP XP PRO I386 folder with matching manufacture OEMBIOS files and keys for each and the MCE files inside the empty CMPNENTS folder i included and burn as a bootable DVD.
http://rapidshare.de/files/29921174/OEM_MCE_ROOT.rar.html