Tripredacus

Interesting... Whatever guide I originally used for WinPE 2.0 said to use it, and I still use it to this day.

Its being worked on.

wpeinit does not start up the NIC. This does: wpeutil initializenetwork

The question then becomes, how to determine if your BIOS is UEFI 2.3.1 compliant? I suspect most current ones are not since this UEFI specification was released in June 2012. UEFI 2.3.1 started showing up early this year, nevermind the publish date on that document. There are a few ways I have found so far. 1. In the BIOS, there is an option to enable UEFI boot 2. The motherboard spec sheet mentions support for "Fast Boot" All Intel boards (look at board rev/AA number) on this list have it: http://www.intel.com/support/motherboards/desktop/sb/CS-033076.htm Note the exceptions below. Anything newer from Intel have it, such as X79, 77 chipsets, but some of their "embedded" type systems, do not have it such as the D2700MUD. You'd have to look at the ProductSpec PDFs to find this info. Other ones its tough. All the new Compal, Pegatron and ASI notebooks/Ultrabooks have it, as do the A75 MSI AMD boards, but this information is even harder to find. The only reason I know those is because I've gotten in the habit of asking.

There should be a rotating ball type animation below the logo... Here is an example: http://www.techfeb.com/wp-content/uploads/2012/06/windows8-release-preview-booting-screen-for-windows-7.png

I don't think it has PowerShell. iirc, only WinPE 4 (a Windows 8 boot.wim) can add PowerShell3 to it. I doubt adding the PowerShell package in the ADK to a Windows 7 boot.wim is supported but who knows if it would actually work!

You found one of our user's link! Here is that thread if you want to check it out:

Not really. OEM discs are of two "kinds": the "BIG" OEM's like HP, Dell and the like the "small" OEM Clarification. There are three "OEM" type discs. 1. The popularly known one, aka channel media, is DSP (as noted on that site)... This is commonly a hologram disc and comes with a COA that does not have a company's name on it. For example, XP Pro SP2 (X10-59871) can unlock with an X14 COA. Some Technet or MSDN subscribers can download this OS type from their download center. This type also appears on the secondary market, or can be purchased from a VAR (computer shop) with a qualifying piece of hardware. 2. There is the OEM Recovery CD/DVD that has a company's name on it, and restores a BIOS-locked installation. These discs commonly do additional hardware checks, for example a Compaq XP Recovery CD may refuse to install on Dell hardware. Most companies will sell a copy of the recovery CD to a user but only if the user can confirm they have qualifying hardware. These CDs often appear on the secondary market. 3. The last is the CD that Microsoft sends to the OEM/System Builder to create both the OS and the recovery CD. These discs are white and are stamped with "Confidential." Users with appropriate Microsoft Partner accounts may have access to download this type of media from Microsoft. I have not seen this media type in the secondary market, likely because its resale (like Intel Confidential hardware) is illegal. #3 here is what allen2 is referring to.

Turisas - The Great Escape For some reason this song gives me chills.

You need to automate your installation. You can use batch, AutoIT or some other method to prompt for the key and store it into a variable. Then after the key is input, you can execute your cmd as (example only) kis13.0.0.3370.exe /s /p"ACTIVATIONCODE=" & $var & "

I guess it does... I mean, they did not tell me how to use it. It appears to be some sort of calibration program for "something" I presume we do not have. So yes!

So you need to (beside start using code tags and get rid of that extra space) is to find where the image is kept. You can do it with WMI, but many people cheap out and just search all drive letters for a matching path. Example: cmd /c for %i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %i:\wpi\wpi.exe start %i:\wpi\wpi.exe source: But I do not know if you can read from WMI directly with a .cmd in WinPE (does wmic work?) without using a scripting or programming language.

I can say that this allows writing the WIN98 type bootsector. Rebooting and the DOS "image" comes up as normal. So this will work using Mbrfix presuming the original image was created using one of the 3 boot sector types it supports. So if it were actually using a Win95 or other version of DOS, some other method would be required to deploy it properly. For the sake of documentation, here is the current .cmd file: regedit /s z:\diskpart.reg diskpart /s z:\fat32.txt imagex /apply z:\dos.wim 1 c: diskpart /s z:\offline.txt z:\mbrfix64 /drive 0 /partition 1 fixbootsector WIN98 /yes exit offline.txt is: sel disk 0 offline disk exit

The idea that the UI is back to being HTML based seems to be a security hole waiting to happen. Wasn't that the reason why Active Desktop was ditched?

Warez discussion is not allowed on this forum. All official downloads from Microsoft are not available in a direct link, and are behind logon portals.

Well I do hope you contribute more than posting a link to a PS3 mod...

Allow me to doubt about this. Sure that's fine. I know it works because I had *tried* something just for fun... I had used Mbrfix to backup the MBR of the Seagate drive and applied it to the Toshiba drive... which obviously did not fix the booting issue.. BUT the BIOS detected the Toshiba drive as a 500GB Seagate. I'll take a look at your links on Thursday (vacation day) Thanks for the help so far.

Are you using a custom install? Also, what is the current Domain Functional Level?

Do you want to hear the good news or the bad news? I ran it again without the align, see attached files... although you won't see everything you might think because of this: X:\WINDOWS\system32>z:\mbrfix64 /drive 0 /partition 1 fixbootsector WIN98 You are about to Fix boot sector, are you sure (Y/N)? y Partition 1, type: 12 WIN95 OSR2 32-bit FAT, LBA-mapped Reading sector: 16065 FAT type: FAT32 Creating a new FAT32 bootsector, 1536 bytes long Writing boot sector to sector 16065 and to sector 16071 Function failed. Error 5: Access is denied. But it should be noted that this isn't specifically related to MBRFix not working properly, as it can write a Vista or Win7 bootsector if I choose that option. I can also restore a backed up bootsector... Hmmm another thing I thought of, does this matter that I am using FAT32 (the original file system) and not FAT? noalign.rar

Should be, but won't. Spec only supports 64bit capable "things." But... that's just official support. No one can say it won't work which in this case it sounds like it does.

Is this a separate issue than your other topic you just made?

I don't think it is required for you to demote the old DC. If it has no roles it can just sit there. Last time I did a migration I did this... however I left a role on the old DC because I got an error xfer it... and also put DNS on there. BUT my question is this (since you aren't too clear on this): Were your users able to work properly during those few hours after the promo, but before they got the error?

No I don't think I was using transparencies back then... It is simply white text on black background, maybe the "layer" is 1: background, 2:font. But the filter was applied to the letters only. I made multiple different attempts, then just stuck them all together. But it has been quite some time so I may be mistaken. iirc it was my first attempt at animation. I had another one made as well, but that file is not as good (IMO) and probably saved on my Windows 98 PC. Probably the last time I used Photoshop 5 (it was the LE version that came with something I bought) before getting Fireworks 2 at college.

My current progress, using a .cmd to run everything: regedit /s z:\diskpart.reg diskpart /s z:\fat32.txt imagex /apply z:\dos.wim 1 c: With this .reg file to add the VDS changes into the registry: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\VDS\ALIGNMENT] "LessThan4GB"=dword:00000000 "Between4_8GB"=dword:00000000 "Between8_32GB"=dword:00000000 "GreaterThan32GB"=dword:00000000 And this diskpart script adding an align option (not sure if needed or what) sel disk 0 clean create part pri size=31000 align=64 sel part 1 active format fs=fat32 label="LocalDisk" quick assign letter=c exit However it still does not boot the OS. I am wondering if it is possible to use Grub4dos (no experience with this) to solve this? For some reason I tend to think Grub4DOS is some sort of miracle program someone came up with... Attached is HDHacker files from deployment in this latest attempt. VDS.rar