tomasz86

The forum seems to be unavailable again

From HFSLIP: and

A new daily is ready. I've fixed all bugs related to slipstreaming. At the moment kernel32.dll 5.0.2195.7187 is included because it works fine while the newest one seems to have some problems. Actually, at the moment I'm not sure whether there will ever be a stable version of UURollup-v11. The reason is quite simple. Unless you've checked the update.inf you probably don't know this but there are so many workarounds implemented in the current daily in order to make it work in HFSLIP that I myself can't even look at it any more I had to use same nasty tricks to make it slipstreamable and I don't really like it. It does work but it requires so much time to prepare and test that I'm not sure whether there's a point in doing that any longer. All of these problems would not exist if it was a Service Pack. I'm thinking about leaving UURollup-v11 in the current daily / weekly stage (and updating it) and releasing one more version of UURollup-v10 (because I've found a bug in v10c, also related to HFSLIP and slipstreaming).

This hotfix is old and obsolete. All files included in it are available in newer versions elsewhere

I've found the culprit. It's the newest version of BWC kernel32.dll 5.0.2195.7191 to cause the SclgNtfy problem. It doesn't happen when the older version (5.0.2195.7187) is used.

You can use the same ISO as before. You should add BlackWingCat's drivers from here (iata76_cd2kd.zip). UURollup-v10c is already integrated in your ISO. What I meant is that you should install the newest daily version of UURollup once the system has been installed and is running.

I've just uploaded the graphics driver. It's called nVIDIA 306.81 Display.7z and it's located in the same folder where you downloaded the AMD drivers from. The driver requires UURollup-v10c or newer. You don't need to re-download the HFSLIP_ia.7z file again but in case of UURollup you should download the newest daily as it's been updated since last time.

There won't be any problems with the graphics (I'll upload the newest drivers modified to work in 2K later). I don't know anything about the SATA controller used in that laptop. Could you try doing some research on this (we need to know the exact name)?

I can assure that the current daily can be slipstreamed and the installation itself works but there's still one problem whose cause is still unknown: I've been trying to find it by replacing files and redoing the whole installation process but no success yet.

I think that you didn't tell us everything MSI.DLL 3.1.4001.5842 is NOT included in any of those packages. You must've installed other updates too. Are you 100% sure that the problem happens with MSI installers only? Do any of them work or all just fail to start? Could you go to Services (services.msc) and try to manually start "Windows Installer"? What happens? Even if it's not directly related to the issue which you've been experiencing, I myself did test this particular version of MSI.DLL in the past and found it very problematic (if not buggy). Windows Installer service just refused to start randomly. The situation came back to normal after I've restored the previous version (KB968006).

@ What's yourr MSI.DLL version?

I have updated the first post and added a list of drivers which I can say for sure that they will be integrated. At the moment the majority of them are the ones which I have already tested on my system so I'm 100% sure that they can be integrated and work 100% properly. Of course this is only the beginning and more drivers are going to be added later. If anyone has got any special requests then please tell me in advance. I've also done more testing regarding VirtualBox and I don't think that it will be possible to add VBox drivers in several different versions simply because all of them share the same Hardware ID so the system won't be able to distinguish between them. Unfortunately the drivers are not inter-compatible so the new ones won't work properly in an older version of VBox. I can add the drivers to USP5.1 but they wouldn't be automatically installed, just included inside it so anyone interested would be able to install them manually.

I have just uploaded a new daily. I've used some tricks to make it slipstreamable so you can try doing it (but you need to repack it yourself). If everything goes OK then the upcoming weekly version should be "officially" ready for slipstreaming. I've also prepared a script for myself. It's capable of: Choosing a HFSLIP folder (so it's possible to have several folders prepared for different configurations and systems). Copying the selected folder to a temporary directory (I use RAMdisk for this). Running HFSLIP from the temporary directory. Integrating drivers. Creating ISO. Automatically starting a VirtualBox machine to test the ISO. (Optionally) preparing a HDD based installation. (Optionally) adding additional tweaks. All of this done in just one click. I originally wanted to just have such a script to save time for myself but if anyone is interested in it then please send me a PM. And I've also managed to integrate VirtualBox drivers directly into Win2k source (link). It's very useful and convenient if you use VirtualBox for testing (as I do).

I wonder whether it's a "mistake" or they do it on purpose Good for us nevertheless

It's in this update: http://www.microsoft.com/en-us/download/details.aspx?id=19364

exfat.sys 5.1.2600.3453 133,632 bytes

I have managed to integrate drivers for VirtualBox 1.5.6 directly into Windows source. You just need to gather the following files: VBoxControl.exe VBoxDisp.dll VBoxGuest.inf VBoxGuest.sys VBoxMouse.sys VBoxMRXNP.dll VBoxService.exe VBoxSF.sys VBoxVideo.inf VBoxVideo.sys The two INF files have been modified as following: 1. VBoxGuest.inf (settings for VBox Mouse and Shared Folders have been added) [Version] Signature="$WINDOWS NT$" Class=System ClassGuid={4D36E97D-E325-11CE-BFC1-08002BE10318} Provider="innotek GmbH" DriverVer=08/21/2006,5.00.2072 [DestinationDirs] DefaultDestDir = 12 ; drivers VBoxService_CopyFiles = 11 ; system32 [Manufacturer] "innotek GmbH" = VBoxGuest [VBoxGuest] "VirtualBox Device"=VBoxGuest_Install,PCI\VEN_80ee&DEV_cafe [VBoxGuest_Install] CopyFiles = VBoxGuest_CopyFiles, VBoxService_CopyFiles AddReg = VBoxService_Add_Reg [VBoxGuest_CopyFiles] VBoxGuest.sys ;Mouse VBoxMouse.sys ;SF VBoxSF.sys [VBoxService_CopyFiles] VBoxService.exe VBoxControl.exe ;SF VBoxMRXNP.dll [VBoxGuest_Install.Services] AddService = VBoxGuest, 0x00000002, VBoxGuest_ServiceInstallSection DelService = VBoxService, 0x00000004 ;Mouse AddService = VBoxMouse, , VBoxMouse_Service_Inst ;SF AddService = VBoxSF, , VBoxSF_Service_Inst [VBoxGuest_ServiceInstallSection] DisplayName = "VirtualBox Guest Driver" ServiceType = 0x00000001 ; kernel driver StartType = 0x00000003 ; demand start ErrorControl = 0x00000001 ; normal error handling ServiceBinary = %12%\VBoxGuest.sys [VBoxService_Add_Reg] HKLM, SOFTWARE\Microsoft\Windows\CurrentVersion\Run, VBoxService, 0x00000000, %11%\VBoxService.exe ;Mouse HKLM, System\CurrentControlSet\Control\Class\{4D36E96F-E325-11CE-BFC1-08002BE10318}, UpperFilters, 0x00010000, "VBoxMouse", "mouclass" ;SF HKLM,"SYSTEM\CurrentControlSet\Services\VBoxSF\NetworkProvider","DeviceName",,"\Device\VBoxMiniRdr" HKLM,"SYSTEM\CurrentControlSet\Services\VBoxSF\NetworkProvider","Name",,"VirtualBox Shared Folders" HKLM,"SYSTEM\CurrentControlSet\Services\VBoxSF\NetworkProvider","ProviderPath",0x20000,"%SystemRoot%\system32\VBoxMRXNP.dll" HKLM,"SYSTEM\CurrentControlSet\Control\NetworkProvider\Order","ProviderOrder",,"LanmanWorkstation,VBoxSF" [VBoxMouse_Service_Inst] DisplayName = "VirtualBox Guest Mouse Service" ServiceType = 1 StartType = 3 ErrorControl = 0 ServiceBinary = %12%\VBoxMouse.sys [VBoxSF_Service_Inst] DisplayName = "VirtualBox Shared Folders" ServiceType = 2 StartType = 1 ErrorControl = 1 LoadOrderGroup = Network ServiceBinary = %12%\VBoxSF.sys 2. VBoxVideo.inf [Version] Signature="$WINDOWS NT$" Provider="innotek GmbH" ClassGUID={4D36E968-E325-11CE-BFC1-08002BE10318} Class=Display DriverVer = 05/17/2007,1.04.0000 [DestinationDirs] DefaultDestDir=11 VBoxVideo.Miniport = 12 ; drivers VBoxVideo.Display = 11 ; system32 [Manufacturer] "innotek GmbH"=Model [Model] "VirtualBox Graphics Adapter" = VBoxVideo, PCI\VEN_80EE&DEV_BEEF [VBoxVideo] CopyFiles=VBoxVideo.Miniport, VBoxVideo.Display [VBoxVideo.Miniport] VBoxVideo.sys [VBoxVideo.Display] VBoxDisp.dll [VBoxVideo.Services] AddService=vboxvideo, 0x00000002, vboxvideo_Service_Inst, vboxvideo_EventLog_Inst [vboxvideo_Service_Inst] ServiceType=1 ; SERVICE_KERNEL_DRIVER StartType=1 ; SERVICE_SYSTEM_START ErrorControl=0 ; SERVICE_ERROR_IGNORE LoadOrderGroup=Video ServiceBinary=%12%\VBoxVideo.sys [vboxvideo_EventLog_Inst] AddReg = vboxvideo_EventLog_AddReg [vboxvideo_EventLog_AddReg] HKR,,EventMessageFile,0x00020000,"%SystemRoot%\System32\IoLogMsg.dll;%SystemRoot%\System32\drivers\VBoxVideo.sys" HKR,,TypesSupported,0x00010001,7 [VBoxVideo.SoftwareSettings] AddReg = vboxvideo_SoftwareDeviceSettings [vboxvideo_SoftwareDeviceSettings] HKR,, InstalledDisplayDrivers, 0x00010000, VBoxDisp ; Set 'Full' hardware acceleration up. On W2003 the level is by default None=5, leading to software mouse cursor HKR,, Acceleration.Level, 0x00010001, 0 HKR,, VgaCompatible, 0x00010001, 0 I can't test newer versions of VirtualBox now because they don't work in Windows 2000 but I've checked their drivers and there seem to be only minor differences between the two so you can just modify them in exactly the same way. Such modified drivers should be integrated easily even with nLite.

Try to remove this: FileSystem=*

I think that the wintrust.dll problem can be called "fixed" now. It seems that adding wintrust.dll from XP prevented the system from registering ANY catalogs. BlackWingCat has just re-added the original wintrust.dll to his kernel and the XP version is now placed in a separate folder together with Cryptographic Services (which also come from BWC kernel). It's still not possible to slipstream the current package but I'm sure that it will be possible shortly. I've finished working on the new .NET Framework package but I still need to do the whole testing process. I can create it 100% automatically basing on the OnePiece's addons. It's going to be a one big package of all .NET Frameworks (because only this way it's possible to eliminate all duplicate files and therefore reduce its size) but I can create an installer selectively too, ex. only .NET 1.1+2.0 or only 2.0+3.0+3.5 or even only 1.1+4.0, etc. Any combination is possible.

@blackwingcat I'm just wondering... what exactly do we gain from this Cryptographic Service?

Wasn't the original meaning of a Service Pack to just include all updates and hotfixes in a one package which can be either installed or slipstreamed? No new components were added to Win2k in any of its SPs. It's XP SP2 where a lot of new things were introduced. Not having to install a lot of single updates is a huge advantage. Another one is that if you check what exactly was included in the SPs for 2K/XP/2K3 you will see that apart from the security updates available to download directly from WU there were also HUNDREDS of hotfixes by request included. Downloading such hotfixes separately is a pain. You can't compare it like that First check size of system files in NT 4.0 and W8.

Any decent software firewall will be enough to protect from this...

This only means that the installer refuses to work You can edit it with Orca but I doubt that it will work even after removing the requirements. It's probably necessary to prepare a custom INF based installer. Let me state once again - under the current conditions the files are not compatible with XP because there are unfixed dependencies related to VS2012. BlackWingCat has fixed them so it's possible to run VS2012 applications in Win2k. In XP it's impossible until someone adds those APIs to XP system files.

Thanks a lot BlackWingCat has recently added VS2012 support to his kernel so there's a chance that .NET Framework 4.5 will work in Win2k. If it works then it will mean that it's possible to do the same to XP (add the necessary APIs) and use it there too.

Thanks for this. It seems that adding MDAC 2.82 won't be that easy. It will require a lot of repacking and creating a new installer for it.