tomasz86

Of course, it can be "UIAcore" It doesn't matter as long as it's 8.3.

The script works 100% correctly. I've just tested it. You need: WUAv256.cmd 7za.exe wget.exe Make sure that your folder path doesn't contain any spaces. Run the script and wait until it has finished. An installer "WindowsUpdateAgent30-x86.exe" will be created.

I know what has to be done to enable DualView in case of the 18x/19x drivers work. It's just one registry entry which was present in 185.85 (and below) but was removed later. This doesn't apply to the newest drivers though as something else seems to be broken in them. There's also another issue related to the nVIDIA Service which loads up VERY slowly in some of the 19x drivers and I haven't had time to do the proper testing yet. The driver is very small and it really shouldn't be a problem to include it in USP5.2 itself... but could you first tell me what exactly it is needed for? As I said before, I've got no clue about Xbox. What can you do with the driver installed?

I don't think that the current problem with nVIDIA drivers may have anything to do regarding the hardware acceleration issues I've checked the Xbox official package and what you need to do to install it is: Unpack it (using ex. 7-Zip). Go to "xbox360\setup\files\driver\vista_xp" and open "xusb21.inf". Find "[MSFT.NTx86]" and change it to "[MSFT]". Save changes. Go to "xbox360\setup". Use Orca to open "xboxacc.msi", go to "LaunchCondition" and remove everything from there. Save changes. Run "xboxacc.msi".

http://reviews.cnet.com/8301-33642_7-57454524-292/just-what-is-windows-rt-anyway-faq/

Does anyone know how to easily change langauge of Metro apps? Is it possible to do it one by one, separately for each of them? At the moment they just follow the language used in system regional settings / locale / language pack. If I change the locale then the language used in those applications also change. I'd just like to be able to set it manually. I hope that it's possible...

It's probably an automatic message added by that Board Express application

I'll repeat myself. Is the system freshly installed? Is it a clean default installation or did you modify it somehow (nLite, etc.)?

I've done more testing regarding nVIDIA graphic drivers and it seems that Win2k compatibility was broken between Forceware 185.85 and 186.08. 185.85 - everything works correctly: but in case of 186.08: and when trying to enable Dualview: I'm now going to find out what the difference between these two versions is and what exactly is responsible for this problem, and also whether there's any way to fix it. Edit: I've also found this very interesting topic which may be useful to repack the drivers' installer later. @desertofunknown Frankly speaking, I've got no idea about Xbox. What kind of drivers are you thinking about? Could you give any links to download them?

That's why I've never liked ATI. Their driver support is just awful. Anyway, I haven't tested it myself but you should probably be able to just add your graphic card's hardware ID to the INF file of the "normal" XP drivers and install them. Could you check the hardware ID in the Device Manager?

Which IE6 installer are you trying to use? Is your system freshly installed?

A new daily is ready. I've fixed one bug and updated several files. However there's a possibility that te newly added msftedit.dll is buggy so be careful. For the last few days I've been fighting with nVIDIA graphic drivers. For some reason nView Dual Display doesn't want to work in the newer versions of the drivers. I've managed to modify the installer so that it installs not only the driver files themselves but also the nVIDIA Control Panel and other tools and eveything seems to work except for Dual Display It does work in the older versions of the drivers so I'm determined to find out which version exactly broke the Win2k compatibility.

The first one is a Battery Optimization software, the second is Wireless switch software. Both of these programs are the new Windows 8 version for the notebook I am working on. Both are 32bit apps that are running on a 64bit OS. If there's really no way to change this then using Process Explorer as Task Manager replacement is now not an option but a must.

A good article but there's a mistake: IE7 is going to be supported until 2017 (together with Vista), and IE6 up to 2015 (together with Windows 2003 Server).

I don't know but I think that Hardware Acceleration does work in Chromium, doesn't it? It doesn't work in Firefox. By the way, I haven't mentioned it before but the .NET Framework installer should also work in XP and 2003.

Confirmed. Works in Windows 2000.

Thank you for testing I wonder if you could do the "standard" testing procedure (for both packages) which means - install - uninstall - reinstall - uninstall Send me (upload) the log file: - %windir%\uurollup-*.log in case of UURollup - %windir%\netfx*.log in case of .NET Framework I haven't tested slipstreaming in case of .NET Framework but it won't work from HF for sure, and should work from HFSVCPACK_SW1. The files themselves follow the 8.3 name format so HFSLIP will integrate them properly even when placed in HF but the commands from [ProcessesToRun*] in update.inf won't be executed. I can fix this though, and after that it should be also possible to integrate the package directly. Edit: I was overoptimistic. HFSLIP won't be able to copy the files to the right folders. The only way to slipstream the .NET Framework installer is HFSVCPACK_SW1. In USP5.2 there are going to be two different .NET installers - one same as the current installer used only when USP5.2 is installed manually in a running system, and a CAB / INF based installer used for slipstreaming executed during Windows setup. It's necessary because a CAB / INF installer can be used before the SVCPACK stage which is important if you want to use SVCPACK to install applications requiring .NET Framework. The OnePiece's .NET true addons are exactly like this but my CABs will be simpler (it will actually be only one CAB for all .NET Framework files).

How is Neptune related to Metro? It was just an updated and modified version of Windows 2000 RTM.

Hey Mimo, Have you done anything about this? I think that more should be done with this file. In its current form it doesn't follow the 8.3 filename format and therefore slipstreaming it will break a DOS based installation (WINNT.EXE). It should be renamed to something like "uiaucore.dll" and then renamed to its original name during Windows setup. HFSLIP should add the required lines to TXTSETUP.SIF in order to do it, ex.: [SourceDisksFiles] uiaucore.dll = 1,,,,,,,2,0,0,uiautomationcore.dll

I have just uploaded a new daily of UURollup-v11 and also a new version of the .NET Framework merged installer. There are a lot of changes in this daily release. I had to implement some tricky and "brutal" workarounds to make it slipstreamable. In the end it's possible to integrate it directly from HF (after repacking of course). In case of the .NET Framework installer I fixed some bugs in the .NET 4.0 installation process.

@blackwingcat It's just a comment / suggestion. You add and remove Cryptographic Services using a combination of SC.EXE, NET.EXE and update.inf: [Product.Add.Reg] HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc", "Description", 0,"Provides three management services: Catalog Database Service, which confirms the signatures of Windows files; Protected Root Service, which adds and removes Trusted Root Certification Authority certificates from this computer; and Key Service, which helps enroll this computer for certificates. If this service is stopped, these management services will not function properly. If this service is disabled, any services that explicitly depend on it will fail to start." HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc\Parameters" HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc\Parameters", "ServiceDll", 0x00020000, "%SystemRoot%\SystemXP\cryptsvc.dll" HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc\Parameters", "ServiceMain", 0, "CryptServiceMain" HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc\Security" HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc\Security", "Security",0x01, 00,00,0e,00,01 HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost","CryptWp",0x00010000,"CryptSvc" [ProcessesToRun] "sc create CryptSvc binpath= ""%systemroot%\system32\svchost.exe -k CryptWp"" type= share start= auto displayname= ""Cryptographic Services"" depend= RpcSs" [ProcessesToRunBeforeUninstall] "net stop CryptSvc" "sc delete CryptSvc" All of this can be done through update.inf without using any other tools. This is an alternative way: [Save.Reg.For.Uninstall] HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost","CryptWp" [Product.Add.Reg] HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc","Description",,"Provides key management services for this computer." HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc","Type",0x10001,0x20 HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc","Start",0x10001,0x2 HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc","ErrorControl",0x10001,0x1 HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc","ImagePath",0x20000,"system32\svchost.exe -k CryptWp" HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc","DisplayName",,"Cryptographic Services" HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc","DependOnService",0x10000,"RpcSs" HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc","ObjectName",,"LocalSystem" HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc\Parameters","ServiceDll",0x20000,"%%SystemRoot%%\SystemXP\cryptsvc.dll" HKLM,"SYSTEM\CurrentControlSet\Services\CryptSvc\Parameters","ServiceMain",,"CryptServiceMain" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost","CryptWp",0x10000,"CryptSvc" The key point is that in "ImagePath" you don't need to specify a full path as it automatically assumes that the path is inside %systemroot% so "system32\svchost.exe -k CryptWp" is enough.

Thank you all for your support @Hackeronte It would be nice to have both versions (ENU & ITA) ready before November 24 but don't worry if we aren't able to accomplish it. The ITA version can be released a little bit later if necessary. I think that it would be good to have a new script to check the files and automatically differentiate between ENU & ITA language versions. I'll try to prepare something and let you know when it's ready. What you can do now is to download the latest daily and check it (from this moment it will be better to rely on dailies if we want to finish this project in the near future ). You can also try to start translating files which will have to be translated for sure, ex. kernel32.dll, or maybe try to search for an easy way to translate DLL files (because the one I used, i.e. a manual translation with PE Explorer is very inefficient and time consuming). If anyone else has got any idea how to translate these files and then be able to apply the changes automatically when a new version is released then please share your thoughts. At the moment I'm fighting with this newest version of kernel32.dll which causes the problem mentioned in #202. It actually has to be slipstreamed because of other files but it also causes the error so I'm trying to find a workaround but it's not easy and requires to use some "nasty" tricks.

It's a good time for someone interested (and capable) to start working on an unofficial SP2 then

Which update do you mean exactly?