DmitryKo

Yep, it's the same as already posted above.BTW, if you need to look at the folder structure, you can actually download a 120-day trial of XP Professional x64 Edition and 180-day trial of Server 2003 R2 Enterprise x64 Edition from Microsoft: www.microsoft.com/windowsxp/64bit/facts/trial.mspx www.microsoft.com/windowsserver2003/evaluation/trial These are fully working versions provided you have compatible hardware, not counting the timebomb in setupreg.hiv, and Microsoft even gives you an activation key.

[double post]

I have EM64T processor, a copy of XP Pro x64 and extra empty hard drive, so I can provide some remote testing if you wish.As far as I can tell, .INF file structure remains intact, but main OS files now reside in \AMD64 folder on the instalation CD, and \I386 contains 32-bit binaries used for WOW64 emulation layer. Which basically means files from UPDATE and SP1QFE folders have to go to \AMD64, and there's also new subfolder, SP1QFE\WOW, which contains files that have to go to \I386 directory...

Here's an unrelated localization issue. For some unknown reason, MDAC packages do not contain locale designation or version number in their filename, unlike most other language-specific updates - that is, they all are named MDAC_TYP.EXE regardless of target language or version. This is a bit inconvenient, so I typically rename them to something like MDAC_TYP_281EN.exe, just in case. So, is it possible to check not just for MDAC_TYP.EXE but for .EXE files which begin with MDAC_TYP?

As I said above, it wasn't clear enough of a warning to me. "Geared for CD installation" is not equal to "geared for CD-bootable text mode installation", a term used by Microsoft's Knowledge Base (I can run setup.exe or winnt32.exe right from the CD and, in general sense, it's still a "CD installation"), and I read it in the HFSLIP doc that one can actually install from a distribution share using winnt32.exe

No, it's not corrupt in either of my sources (English and Russian), I can open and extract them witn both Explorer (in XP) and WinRAR. I could have integrated one of the installations under Windows 2000, which is not the right way according to KB889719. But I'm not sure because I could have done it under Windows XP Pro x64 as well. OK. But what's the technical reasons for this behaviour, if all the necessary setup files are updated according to the procedure defined by Microsoft? Well, it seems like a confusion on my part... maybe phrases like "use CD to install", "install by CD" etc. are not technical enough of a description for me - all in all, running setup.exe or winnt32.exe from the CD could be also qualified as "installing via CD", don't you think? (not to mention some "clever" programs that won't even install from a local or network folder unless it's mapped to a drive letter).Non-GUI precopying phase on NT installers has always been referred to by Microsoft as "text-mode setup", whenever it's invoked by booting to Windows kernel from the CD/floppy or by running winnt.exe from MS-DOS propmt, so maybe there should be an excplicit clarification somewhere in the docs, something like "Do not use winnnt.exe and setup.exe/winnt32.exe! The only supported installation method is CD-bootable (or floppy-bootable) text mode setup". I guess it doesn't matter anymore, but nevertheless... here's what I did.1) I've HFSLIPped two Windows 2000 CDs, English and Russian, in order to upgrade two different PCs to the latest hotfixes. I then run the textmode setup by booting from the CD in either cases and performed in-place installation, and there were no errors or warnings. (I could just apply the latest hotfixes I guess, but some of the Windows' components were behaving strange so I thought a "repair" install would help, but it didn't 2) Then I've HFSLIPpped two extra Windows XP CDs, also English and Russian, as I wanted to upgrade two more PCs from Winfows 2000 to Windows XP level (some programs wouldn't install on W2K). This time I didn't use bootable textmode setup, I just ran Setup.exe from within the Windows Explorer (one time from the CD and another from the SOURCESS folder). This way, I've got SP2.CAB not found warning, but I was able to Skip it over, and then Windows Media player setup found no System Files Protection and configuration for Personal Web Server was not accessible. 3) Finally, I've tried to upgrade newly-installed English XP one more time, again by running Setup.exe, and I've got stuck at Installing Windows, being told that "GLOBALROOT\DEVICE\CDROM0\I386" contains no "amss". I just had to specify the SOURCESS folder so the install would go on. There were no SP2.cab errors this time, but Windows Media Player and Personal Web Server warnings were still there.

But I've also made several Windows 2000 install CDs and upgrades were totally flawless (I started the bootable textmode setup to copy the GUI portion this time, not the WINNT32.exe) Windows XP is currently working fine as well, despite all the installation troubles. HFSLIP doc says you can use Winnt.exe (step twelve, http://www.vorck.com/hfslip.html): As I understant, HFSLIP basically follows the hotfix slipstreaming procedure recommended by Microsoft ( KB316037 and KB828930), with the exception that instead of integrating aka slipstreaming hotfix packages using /integrage switch (which BTW can be hacked to work with WXP updates under W2000, as described by KB889719), the packages are are expanded, contents (GDR branch) are copied over to i386 folder , then compressed as necessary and finally custom INF files are created for each hotifx. If so, I just don't understand why there are copy errors when I'm not adding anything past some XP hotfixes and WMP10... why there were no errors in W2K? Could you please explain this with a little bit more detail?

Do you mean text mode setup invoked by booting from the CD?!! I was upgrading Russian localized version of Windows 2000 from the CD (not from text mode setup) but English version of Windows 2000 was upgraded the local folder, and it went just fine except for several non-critical error messages...Well, the saga contunues. I tried to do yet another "upgrade" for the Windows XP installation I just upgraded from Windows 2000. I removed the punctuation marks from the folder name (not that it made any difference), reran HFSLIP and then burned a CD and started winnt32.exe from it. There were no precopying errors regarding SP2.CAB this time, but instead it told me "amss" (all-lowercase) is not found in "GLOBALROOT\DEVICE\CDROM0\I386" (?!!), even though "AMSS" folder (in all-uppercase) was actually there. Pressing Cancel threw a critical failure and setup was permanently interrupted. Restarting from the CD didn't help either, so I had to manually type the path to my C:\HFSLIPWXPENG\SOURCESS folder, and then the setup went on. I had to type it some two dozen times more during the rest of the setup (mostly for some INF or CAT files), including Detecting Devices and Adding Start Menu phases. There were no messages from Media Player regarding System File Protection (I left it in HFSVPKSW for now), but there was "Unable to access configuration for Personal Web Server" (and I recall the same error appeared when I was upgrading from Windows 2000). I really hope Microsoft gets this whole setup and slipstreaming act right for the Windows Vista, I'm just tired of 15-year old floppy-based setup routines...

If I wanted to make a clean install I would do it, but this time I just needed an upgrade (I have clean-installed WXP Pro X64 on another partition). No, I didn't specify any switches, I just ran Setup.exe right from Windows 2000 and chose Install Windows (it doesn't matter if I burn a CD or run it from the SOURCESS folder, the error is still there) and it starts Winnt32.exe unattended mode - that is precopies setup files to a temporary folder and creates WINNT.SIF which contains my current system setting with a number of "interesting" options. BTW, it's supposed to be a "quiet" mode but actually Windows Media Players 10 asks me if I want it installed because Windows System Protection is turned off. There was also another dialog box but I don't remember the details..

WINNT32 tells me that SP2.CAB is missing when preparing upgrade from Windows 2000 SP4 using HFSLIPped version of the installation folder. What's more, it's happening with two differnet language versions! Setup goes on as usual right after a restart. WXP_EN.zip

Even though I realize it's probably a double work for maintaining wow64 chain and stuff...

In fact, it does have everyting to do with Vista, because Direct3D 10 aka WGF2.0 is be based on functionality provided by Advanced mode Vista Display Driver Model (VDDM, previously known as LDDM) There's also Basic mode drive model that supports current DX9 hardware, and Basic VDDM-complient drivers are required for DX9.L aka WGF 1.0 which is exposed by Aero Glass interface. Vista will also supports DX9 driver model that's used in XP/2000; Aero Glass is not supported in this mode but DX9/8/7/6 and OpenGL games will run as usual.See http://www.tgdaily.com/2005/09/22/vista_gr...han_xp_drivers/ http://www.microsoft.com/whdc/winhec/Pres05.mspx#toc8 (paper Windows Graphics Overview) WGF 2.0/1.0 SDK is going to be released along with Vista Beta 2 due in February. [Edit] Actually, the Direct3D 10 Technology Preview is included in December 2005 SDK update! http://msdn.microsoft.com/directx/sdk/

A couple of quick questions 1) can I just put dotnetfx.exe into HFSVPK_SW (it says it supports /Q switch); 2) does NetFX 2.0 runtime replace 1.1 runtime (i.e. can I run 1.1 applets under 2.0); 3) what do I do to instal 1.1 hotfixes 867460 and 886903 (they support /Q as well)??? I guess it's just too late anyway...

HFSLIP documentation says it's not possible but I've found the following references below, so I'm a bit confused... does it really work? unattend.doc from Deploy Tools for Windows2000: readme.txt for Intel Matrix RAID storage driver: PS. Just found this: KB234536 You cannot perform an unattended installation of mass storage drivers when you run the Setup program from the Windows CD to install Windows Server 2003, Windows XP, or Windows 2000 So, I guess the answer is NO

Although there's no direct download link included in KB887797 article, you can still find OS specific files by searching up the article number http://www.microsoft.com/downloads/results...eeText=KB887797 Maybe you should provide a direct link to the pages so that localized versions can be easily downloaded as well. Confusingly, there's a separate package for Windows XP, even though IE6 SP1 updates for both XP and 2000 always ship in one package. And the reason why didn't Microsoft include them in the article is beyond me... does it have to do with multiple registry hacks that's needed to enable the functionality provided by these updates? The same goes for Windows Script 5.6 - you can search up the files http://www.microsoft.com/downloads/results...Text=script+5.6 There are several pages for various OS, each offering localized versions. [Edit] Just noticed that TomCat76 has already posted the link to the download page for Windows2000/XP version of KB887797... BTW, there are two new Security Bulletins MS05-055 Vulnerability in Windows Kernel Could Allow Elevation of Privilege (908523) (Windows 2000) MS05-054 Cumulative Security Update for Internet Explorer (905915)