Jump to content

Bezalel

Member
  • Posts

    595
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by Bezalel

  1. I think some of your procedures are overcomplicated, here are some of the thing I do to solve the same problems.

    On my network I created an AD account that can join a computer to the domain but can't do much else. I don't care what model I'm installing to because I have INF files for every device in my organization (some of them were extremely difficult to extract from packaged installers). For user profiles I use roaming profiles. I set the policy for WSUS from cmdlines.txt.

  2. Bezalel or anyone else,

    Do you know how to show the Product ID of the installation?

    EXAMPLE: find XP Product ID from Digital ProductID or some other way and output PID, like 55274-OEM-0011903-00102 for Dell?

    I'm just trying to be able to get the XP PID from the rigistry, a reg file or other files, instead of having to run MGA.EXE or something else.

    Thanks.

    Just use the Win32_WindowsProductActivation WMI Class.

  3. The easiest method is to install Windows on a simular motherboard and to transfer the HD to the powervault when finished. as long as the motherboard uses the same HAL and mass storage driver you should be OK, all of the devices on the PowerVault 715N have their drivers build in to 2003 (I never tried XP). If you want to do it the hard way take a look at http://en.community.dell.com/forums/p/17729873/17889070.aspx.

  4. ugh, this is more complicating than what I thought. I only wanted to see how they did it in class.. It was pretty much like this. We turned on our computers, and Windows XP Setup Installation came up, and after the installation, it already had stuff on it like MS Office 2007, Adobe Reader, stuff like pidgin. I was just trying to find out how they did that. and I was asking because it basically looked like it was a CD from the manufacturer, except with additional stuff on it.

    What is running is called "Mini-Setup". Windows has already been completely installed and it is only showing enough of the screens from setup to personalize the PC.

  5. Hi all.

    First let me say Great Job for this guide

    Second I need a little help with HP recovery cd.

    HP sells pc with HP restore DVD plus (Done with Microsoft Desktop Deployment kit) and cd with OS(Vista or XP).

    Now If Explore the OS cd (windows Xp professional Italian SP2) I see that there is another folder called ITWXP32p_ZX and under this folder there is a Windows\System32 folder which contains oembios.sig, oembios.bin and oembios.dat.

    I tried your method but It still ask for activation... maybe I can use files stored into the folder above?

    Thanks for the answer

    Raziolo

    HP does weird things with their recovery sets. The best option is to run mgadiag and post the report and the CRC32 of your OEMBIOS.CAT.

  6. [Request]

    I'm searching OEMBIOS.* SLP set for Fujitsu Siemens Computers - OS: Windows XP Professional x64 Edition and Fujitsu Siemens Computers SLP Product Key. This OS is preinstalled on some CELSIUS Workstations from Fujitsu Siemens Computers.

    If a European Community (EC) msfn member have a FSC recovery CD, you can send me a PM or reply below.

    The sets are interchangable between x86 and x64. A generic x64 key can be found in the MS article titled "Preserving OEM Pre-Activation when Re-installing Windows XP"

  7. However, I don't know some SLPs range exactly, becaue they are maked as "." in oembiso.dat, so I enlarge their range. For example, AMOI, Tektronix, JVC, SHARP.

    Here is the relevant quote for the SLP Whitepaper:

    ReadSize can range from 0005 - FFFF; however, there are performance and security penalties if this range is unnecessarily large. If not specified, it has a hexadecimal value of 104 bytes. ReadSize is optional.
  8. I've been working on an OEM version of XP that installs some extra files (in this case, Windows Themes) but have run into conflicting information regarding the location of the $OEM$ folder. Since I am installing off CD, it only works when $OEM$ is at the same level (root) of the CD. Yet some places, including Microsoft's KB say it should be inside i386 for certain installation methods. Can you explain the details?

    It depends how you are starting the setup. If you are starting the setup by booting from the CD the $OEM$ folder should be in the root of the CD. If you start setup by running winnt32 then the $OEM$ folder should be in I386.

  9. I've heard of situations where a person has been scammed like this can receive a legit license in exchange for helping MS catch someone selling pirated software. I dunno if those are just old internet urban legends but i'd do it for free. seriously, whats the worst they can do to you? blacklist your serial on pirated copy? -i can almost guarantee thats already taken care of.

    The free license only applies if you have a high quality fake.

  10. Any chance someone could confirm the hashes of these file sets for me.

    The HP seems fine, but the Dell fails when tested on a Dimension 5150.

    HP = CC6CB12C

    Dell = C20D8FF5

    Do Dell servers use the same SLPBIOS string as their desktops?

    Thanks Guys.

    There is a newer HP set (D107C3EA) but I'm not sure why.

    Dell uses different ranges for 2003 but I haven't had any problems installing on any of their desktops.

×
×
  • Create New...