tomasz86

The AMD graphics drivers for XP for won't work. They need to be modified (the actual driver files, not just the INF file). The only person capable of doing that is blackwingcat. No In my experience, the latest drivers working "out of the box" are v270.61 available at my website. In case of the newer drivers I believe that you need to modify the DLL files too. You should try to use the v300.xx drivers from BWC.

The AMD and Intel graphics drivers won't work with PAE enabled The NVIDIA drivers do work.

Well, first of all, you should never install both of them because BWC kernel is already included in UURollup... but at the end it shouldn't really matter in this particular case since you've just installed same files and registry settings twice. I'd suggest you send a PM directly to blackwingcat and ask him whether he could modify the latest official AMD graphics drivers (which support your specific graphics card model) to make them work in Windows 2000. Edit: Did you enable PAE by any chance?

What updates have you installed in your system? Is UURollup or BWC kernel installed?

Updated. Bug 2 has been added to the list.

@NorthAzimuth I'm sorry your system got broken because of UURollup-v11 daily Actually I've encountered that problem a few times too while doing testing but haven't been able to find the culprit yet. It seems to be some other software to cause the critical error on boot. To be safe I'd suggest to try installing the daily release in a clean and fully updated system before everything else. Edit: The bug has been added to the Bug Tracker. UURollup-v11 itself requires at least Unofficial SP 5.1 (or official SP4 + Update Rollup 1) and unofficial Update Rollup 2. When using SP4+UR1 installing IE6 is not required but highly recommended. Of course it would be the best if ALL other updates were installed before applying the rollup but at the moment preparing a FULLY updated Windows 2000 installation is quite complicated. There are too many separate packages available and gathering all of them without getting confused is not an easy task. You can find my fully updated HFSLIP package in the Download Archive (go to Windows2000/UnofficialSP5/HFSLIP_ia.7z). It's intended to be used with HFSLIP but you can get an idea what kind of updates are necessary. It's 4 months old though so there may be a few updates missing including the newest release of UURollup-v11.

@jakson It would be probably good to change ECHO %%I|FIND /I "Vista">NUL 2>&1&&(SET HostOS=Vista&GOTO :HOSD)to ECHO %%I|FINDSTR /I "Vista 7 8">NUL 2>&1&&(SET HostOS=Vista&GOTO :HOSD) I don't know what is displayed in Windows Server 2008 and Windows Server 2012 so it'd be nice if someone checked and told us about it. Edit: Actually the whole HostOS checking script could be improved a little bit. I've got no time at the moment but I'll edit this post later today.

@InsaneNutter The difference is that Update Rollup 1 will install IE5 related files and registry entries if you apply it before installing IE6. In the end it shouldn't matter though...

Thanks a lot for the updated release I've noticed one cosmetic issue: ECHO ???[MSFN COMMUNITY MAINTENANCE RELEASE] ???I don't know what the "???" were supposed to be but these lines look like this here. Did you use any special characters? As for addons, at the moment I'd really stick to using only completely true addons for HFSLIP, and for the other addons use nLite or RVM Integrator. By the way, I've simplified the Addon script a little bit more: 1. Change IF EXIST HFAAO\* CALL :HFAAOto IF EXIST HFAAO\* IF EXIST HFTOOLS\7za.exe CALL :HFAAOso that the addon folder won't be processed at all if no 7za.exe is present in HFTOOLS. 2. Change :HFAAO TITLE %T1% - Processing App Addons FOR /F "DELIMS=" %%I IN ('DIR/B HFAAO') DO SET AAOTBP=1 IF NOT DEFINED AAOTBP GOTO :EOF FOR /F "DELIMS=" %%I IN ('DIR/B/A-D/ON HFAAO') DO ( IF EXIST HFTOOLS\7ZA.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\7ZA x "HFAAO\%%I" -o"%PREP%\TEMP\AAO" -r >NUL&&CALL :PROCESS_AAO ) to :HFAAO TITLE %T1% - Processing App Addons FOR /R HFAAO %%I IN (*) DO ( ECHO. ECHO Processing %%I >NUL HFTOOLS\7ZA x "%%I" -o"%PREP%\TEMP\AAO" -r CALL :PROCESS_AAO )Same thing, less code.

@WildBill 7-Zip works for me. Are you using the newest version? Mine is 7-Zip 9.30 alpha.

In order to install UURollup-v11 daily just run "update\update.exe" after unpacking the archive.

Let's hope everything will work without too much hassle I'd suggest to use a fully updated Windows 2000 source for installation.

There are some cases where files have newer version even though their time stamp is older. I can think of at least several Windows 2000 updates which are like that. It should be relatively easy to use "filever.exe" to compare file versions of those files instead of using "xcopy/d". I've got no time to look at it at the moment but can try to do something about it in the future. It's always good to be able to get the information from several sources than relying on just one. I myself would specifically not consider the M$ website a reliable source since they tend to change their websites quite often and I won't be surprised if all info related to 2K / XP / 2003 is completely removed after the official support ends in 2015. This already happened to stuff related to Windows 9x and NT 4.0.

HFSLIP support for addons is extremely limited. Only true addons are supported. However, integrating large and complicated update packs (like Onepiece Win2k postSP4 UpdatePack and others) results in a corrupted Windows installation even though the update packs are technically also true addons. For Windows XP I integrate the following ones Kels_Runtimes_addon_v8.5.7z OnePiece_Microsoft.NET_Framework_v1.1.4322.2502_True_AddOn_ENU_CECE82149DF5A0F4250D766448995ADF.cab OnePiece_Microsoft.NET_Framework_v3.5.30729.4051_True_AddOn_ENU_71968F1BC3AC2E433F3E9AA143B3E728.cab OnePiece_Microsoft.NET_Framework_v4.0.30319.1008_True_AddOn_ENU_B59D6FA8C909DAD14965B880F957FB29.cab Ricks-YumeYao_MicrosoftVC7891012RuntimeLibraries_Addon_2_2_1.7z YumeYao_MicrosoftOldRuntimeLibraries_Addon_1_0_0.7z and they are integrated correctly. In case of the .NET Framework addons I had to rename them since "extract.exe" was unable to process the files with long names but now, with 7-Zip, it's no more necessary. If I've got some time I'll try to have a closer look at the addon integration process in HFSLIP. At the moment I think that the most important thing is to fix the "extract.exe" problem

I've finally solved the problem reported in the other topic (Strange bug in HFSLIP related to short 8.3 names #3). The full explanation is provided there but, in one word, my suggestion is to change FOR /F "DELIMS=" %%I IN ('DIR/B/A-D/ON HFAAO') DO ( IF /I "%%~xI"==".rar" IF EXIST HFTOOLS\RAR.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\RAR e "HFAAO\%%I" * "%PREP%TEMP\AAO\" >NUL&&CALL :PROCESS_AAO IF /I "%%~xI"==".cab" IF EXIST HFTOOLS\EXTRACT.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\EXTRACT /E /L TEMP\AAO "HFAAO\%%I" >NUL&&CALL :PROCESS_AAO IF /I NOT "%%~xI"==".rar" IF /I NOT "%%~xI"==".cab" ( IF EXIST HFTOOLS\7ZA.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\7ZA x "HFAAO\%%I" -o"%PREP%TEMP\AAO" -r >NUL&&CALL :PROCESS_AAO ) ) to FOR /F "DELIMS=" %%I IN ('DIR/B/A-D/ON HFAAO') DO ( IF EXIST HFTOOLS\7ZA.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\7ZA x "HFAAO\%%I" -o"%PREP%TEMP\AAO" -r >NUL&&CALL :PROCESS_AAO )

I've finally managed to find the culprit! Using "extract.exe" causes to unpack CAB addons causes the CMD window to use short names. "Extract.exe" is used by HFSLIP only once which is when unpacking CAB addons: This is the full code FOR /F "DELIMS=" %%I IN ('DIR/B/A-D/ON HFAAO') DO ( IF /I "%%~xI"==".rar" IF EXIST HFTOOLS\RAR.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\RAR e "HFAAO\%%I" * "%PREP%TEMP\AAO\" >NUL&&CALL :PROCESS_AAO IF /I "%%~xI"==".cab" IF EXIST HFTOOLS\EXTRACT.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\EXTRACT /E /L TEMP\AAO "HFAAO\%%I" >NUL&&CALL :PROCESS_AAO IF /I NOT "%%~xI"==".rar" IF /I NOT "%%~xI"==".cab" ( IF EXIST HFTOOLS\7ZA.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\7ZA x "HFAAO\%%I" -o"%PREP%TEMP\AAO" -r >NUL&&CALL :PROCESS_AAO ) ) After removing parts not related to CAB addons: FOR /F "DELIMS=" %%I IN ('DIR/B/A-D/ON HFAAO') DO ( IF /I "%%~xI"==".cab" IF EXIST HFTOOLS\EXTRACT.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\EXTRACT /E /L TEMP\AAO "HFAAO\%%I" >NUL&&CALL :PROCESS_AAO ) The problem lies here: HFTOOLS\EXTRACT /E /L TEMP\AAO "HFAAO\%%I" I did a simple test doing: DIR/B/S HFAAO before and after extracting a CAB addon. The result was: 1. Before: D:\HFSLIP\TEMP\HFSLIP_test\HFAAO\NETFX11.cab 2. After: D:\HFSLIP\TEMP\HFSLIP~2\HFAAO\NETFX11.cab "HFSLIP_test" got changed into "HFSLIP~2" and this causes all the issues which I described in this topic above. The solution to this problem is very simple. Remove this line all together: IF /I "%%~xI"==".cab" IF EXIST HFTOOLS\EXTRACT.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\EXTRACT /E /L TEMP\AAO "HFAAO\%%I" >NUL&&CALL :PROCESS_AAO and change the next one from IF /I NOT "%%~xI"==".rar" IF /I NOT "%%~xI"==".cab" ( to IF /I NOT "%%~xI"==".rar" ( so that the result should be FOR /F "DELIMS=" %%I IN ('DIR/B/A-D/ON HFAAO') DO ( IF /I "%%~xI"==".rar" IF EXIST HFTOOLS\RAR.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\RAR e "HFAAO\%%I" * "%PREP%TEMP\AAO\" >NUL&&CALL :PROCESS_AAO IF /I NOT "%%~xI"==".rar" ( IF EXIST HFTOOLS\7ZA.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\7ZA x "HFAAO\%%I" -o"%PREP%TEMP\AAO" -r >NUL&&CALL :PROCESS_AAO ) ) 7-Zip is capable of unpacking CABs so there's no need to use the outdated "extract.exe". In fact, at this point I'd suggest removing the RAR part too, leaving just FOR /F "DELIMS=" %%I IN ('DIR/B/A-D/ON HFAAO') DO ( IF EXIST HFTOOLS\7ZA.EXE ECHO.&&ECHO Processing %%I&&HFTOOLS\7ZA x "HFAAO\%%I" -o"%PREP%TEMP\AAO" -r >NUL&&CALL :PROCESS_AAO ) since 7-Zip can process RAR too.

@jakson I can't confirm the issue. In my case the only difference between hfslip-1.7.10_beta_J_v11.cmd and hfslip-1.7.10_beta_K_v2.cmd is: 1. 1.7.10_beta_J_v11.cmd portabledeviceapi.dl_ portabledeviceclassextension.dl_ portabledevicetypes.dl_ portabledevicewiacompat.dl_ portabledevicewdrm.dl_ wpdshextautoplay.ex_ wpdshextres.dl_ wpdshserviceobj.dl_ 2. 1.7.10_beta_K_v2 PDvApi.dl_ PDvClass.dl_ PDvTypes.dl_ PDvWiaCm.dl_ PDvWMDRM.dl_ wpdshext.dl_ wpdshext.re_ wpdshsrv.dl_ As you can see, these are the same files, just converted into 8.3 format by 1.7.10_beta_K_v2 in order to make DOS based installation possible. 1.7.10_beta_K_v2 also adds: SVCPACK\kb942288-v3.cat SVCPACK\wuweb.cat which 1.7.10_beta_J_v11 doesn't add at all. My HFSLIP.LOG:

Thank you for all the work, Mimo.

In this topic I'm going to keep and update a list of all bugs related to UURollup, USP5.1 and other packages. I think that it shall be much easier to track them once everything is described in details in one topic. Please let me know if you've got any ideas or suggestions about how the list should look like.

Placeholder

Placeholder.

This project has been discontinued. Please check the Unofficial SP 5.2 for Windows 2000 thread for more information.

I'd suggest AMD at least for one reason which is K10stat. Neither AMD's Cool'n'Quiet nor Intel's SpeedStep work in Windows 2000 but you can use K10stat for power management of AMD CPUs. In case of the Intel processor it's going to run at full speed all the time. My board is based on FM1 and AMD A55 chipset. Before buying a motherboard just make sure that everything will work in Windows 2000. I'm thinking specifically about the USB3.0 chip and the LAN card.

Thanks I've read a blackwingcat's post saying that there were no longer Windows 2000 updates included in the latest ISO. There was still another one released which is newer than the one listed on my website (Update List for HFSLIP). I'm going to update the whole list in the near future. I'm also going to gradually add to the Download Archive all updates for Windows XP (basing on the Mimo's list) and for Windows 2003 Server (basing on the FDV's list).

By the way, the whole processing of MSI 4.5 is kind of not right in my opinion. The MUI files, which are normally copied to several different directories in "%windir%\system32\mui", are removed by HFSLIP and only one of them is left depending on the language of the Windows source. It's then renamed and later installed as "msimsg.mui". Normally the all 38 MUI files of MSI 4.5 should be installed. I'm not sure but I think that it may have impact on the English Windows when you actually install and use different system MUIs. MSI 4.5 should probably change its language according to the system MUI but it won't do it if those MUI files are not present. Anyway, I'll try to provide a solution to this issue shortly.