Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


tomasz86

Member
  • Content Count

    2,765
  • Donations

    $0.00 
  • Joined

Community Reputation

89 Excellent

About tomasz86

  • Rank
    windowsarchives.com

Contact Methods

  • Website URL
    http://windowsarchives.com

Profile Information

  • OS
    Windows 2000 Professional
  • Country

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You can find the old Global version in https://mega.nz/#F!SlACALYL!9eek__QpDtB4CIqLR_hUDQ. Please keep in mind that it is very old, and also does not offer most of the benefits of the BWC kernel (or even the last UURollup for ENU), since most of the core system files are language specific.
  2. Unfortunately I do not have the skills to do it. In case of Windows XP, M$ has released a new version of the file termdd.sys. The file itself is OS specific, so it is impossible to use the XP file in Windows 2000. The file in our OS would have to be reverse engineered and patched accordingly to the XP file.
  3. Make sure that your drivers, and especially the graphics driver, support PAE. I do not know for now, but in the past in my testing only the NVIDIA drivers worked, while both AMD and Intel drivers did not.
  4. I asked the same question regarding Windows 2000 a few years ago, but there has been no definite answer.
  5. While true, I still think that this is a good option to do for the greater good. Right now, the links are accessible only to those logged in on the MSFN forum. If the forum goes down or something happens to the file, they may be lost forever. I myself have gathered all the POSReady updates with their respective links available in the MS Catalog from 2010 to now, but have not managed to archive the older links yet. In case of many Windows 2000 (and older) updates, some of them did actually "vanish", and we have no access to the files any more. Only the broken URLs remain. This is especially true for updates for the less popular language versions of Windows.
  6. I think that it may be beneficial to create a new topic with all the links listed directly in the post instead of a text file. This way they could be indexed by search engines, and also hopefully grabbed by the Wayback Machine while they are still functional.
  7. Ah, so I guess that we have found the culprit then! Even though you did take some time away from me, it is all right . At least now we know that slipstreaming with HFSLIP2000 works fine under all versions of Windows, and I myself will definitely make use of the HFSLIP2000-info script in my future testing. You kind of motivated me to actually write the script, and for that I am very thankful. I would guess that it is nLite adding those drivers to cause the IE/DX issue. Installing from USB should normally not affect anything, unless you have used some kind of a fancy tool which tampers with the system files. I do not use nLite anymore, but as far as I remember, there is a special instruction on using it after HFSLIP. Please check https://web.archive.org/web/20171220125454/http://www.vorck.com/windows/2ksp5.html, especially "Step 13". "This utility" can be found here: Edit: I just want to say that I have not forgotten about the .NET incomplete installation problem. If you look carefully at the progress bar during the Windows setup process, you can clearly see that the .NET Framework components are being processed extremely quickly. I would say - too quickly. This likely means that the INF files responsible for their installation are simply being skipped there. I will try to troubleshoot the problem, but I may need some time to investigate all the possible causes.
  8. Yeah, so the only difference between the old HFSLIPWU.INF and the new HFSLIPWU.INF is the HFSLIP2000 version number included in one of the strings (1.0.2 vs 1.0.3BETA), which does not matter also. Right now there seem to be basically no differences between your and my copies of the updated Windows 2000 source, but mine installs perfectly here, so I am quite confused. I myself am using Windows 7 (fully updated) as the host OS, and testing the installation in VirtualBox (v5.2.28). Where are you installing your Windows 2000? Is it a real computer, or a virtual machine? I will try to test slipstreaming under Windows 10 (1809), and will also try to find out why that experimental version of HFSLIP2000 fails (because it is the only case where I can reproduce the IE/DX versioning issue). Edit: Slipstreaming under Windows 10 makes no difference for me. The resulting source folder is exactly the same as the one slipstreamed under Windows 7. It installs correctly too.
  9. Thank you. As I mentioned above, the difference between the two SETUPREG.HIVs does not seem to matter though. There is, however, another difference in the two HFSLIP-info files of yours. Could you please upload HFSLIPWU.INF from the i386 folder - both the old and the new one?
  10. I think that we may have a little bit of a mistery here. Your "SETUPREG.HIV" is indeed abnormal. The file has basically its contents doubled, hence it has twice the size of the original. The problem is that even in this state, it does not affect the installation process. I have used the file for my test installation, and there was no difference with the previous one. The installed system was functioning 100% normally, with both IE6 and DX9 present. At the moment, the only way that I can reproduce the IE/DX missing issue is when using that experimental version of HFSLIP2000 from two years ago, but your log file suggests just the standard version of HFSLIP2000, so I am really not sure what may have caused the issue .
  11. Hmm, I expected some significant differences in the slipstreamed files, but in fact almost all of them are exactly the same as in my source, with the exception of "SETUPREG.HIV". Yours is almost double the size of the original, which is quite strange. This file is modified by HFSLIP only in the very beginning of the slipstreaming process when adding support for larger drives to the Windows 2000 installer, and I am suspecting that this may be the host OS (which is Windows 10 in your case) to mess the things up. Even after the modifications, the file size should normally stay roughly the same (as it is in my case). I would like to ask for two things: 1. Could you please share your "SETUPREG.HIV" file for inspection? If possible, both the one from your unmodified Windows 2000 source, and the one after using HFSLIP2000. 2. I have uploaded a new, beta version of HFSLIP2000 to the Archive under https://mega.nz/#F!2lBVBBLI!WqmqhpxuX0qyCY1LiX4-gw!L0omSarK. This one does not use "reg.exe" from the host OS, but rather relies on the one from Windows 2000 to patch "SETUPREG.HIV". This will probably require some time, but if possible could you use this version of HFSLIP2000 to slipstream everything again, and then run "HFSLIP2000-info.cmd" on the newly created source? I would like to compare it with the old one to verify my suspicions.
  12. I like this attitute . I have uploaded the script to the download Archive under https://mega.nz/#F!2lBVBBLI!WqmqhpxuX0qyCY1LiX4-gw!L0omSarK. Please download "HFSLIP2000-info.7z" and unpack it to your Windows source folder. The file structure will look something like this: I386 SUPPORT CDROM_IP.5 CDROM_NT.5 CDROMSP4.TST HFSLIP.LOG HFSLIP2000-info.cmd Then just run "HFSLIP2000-info.cmd" and wait for the results. It may take some time as the script is not optimized (=it is slow), and also right now requires to be run in Windows 7 and above (because of one of the tools used to calculate SHA1). The script will make a list of all files from the i386 folder, including their size, version, and SHA1 checksum. Once the script has finished its job, you will find a new file called "HFSLIP2000-info.txt" next to the script file. Please pack it and upload somewhere for me to see.
  13. Thank you. The log indeed indicates the official version of HFSLIP 2000, not the experimental one, and is exactly the same as mine from yesterday, which installs correctly here. Something must have gone wrong during the slipstreaming process, but the HFSLIP log, unfortunately, does not include any post-slipstreaming information. What is your host OS, by the way? HFSLIP, of course, always says "Windows Vista", but in reality this covers all Windows versions from Vista to 10. If the HFSLIP log included a full list of files with their version and what not, then it would be a different story, but with such limited information, I am unable to do any more blind troubleshooting. To really be able to investigate more, I would either need to have access to the full i386 folder to check the files myself, or ask you to run a special script that would make a full list of the slipstreamed files with their versions. My question is - would you be willing to run such a script? I am asking since I have to write the script first and do not want to do it for nothing. Another option would be to pack the i386 folder and upload it somewhere, but this would be classified as illegal Windows file sharing by M$, even if done only for troubleshooting purpose . PS To hide the content, you need to manually type [spoiler] [/spoiler] around the content you want to hide. It will show up as a thin line in the preview, but clicking on the line will not do anything at this stage. The content will become hidden only after you submit the post. Sounds complicated? Yes, the new "modern" and shiny forum software is kind of a pain to actually use. Who would have guessed...
  14. Please let me know once you try again. The thing is that that experimental version is/was also called "1.0.2", although the structure of the final log file would be a little different. If you can still find the log file, I would like to have a look at it.
  15. I did some testing and here is what I have found. Everything slipstreams and installs correctly when using the official version of HSFLIP 2000, which at the moment is version 1.0.2, which is also included in the FullPack package. Using my test version of HSLIP 2000 which I talked about sometime 2 years ago (i.e. the one which greatly sped up the integration process) results in a partially broken installation. I am not sure what exactly gets broken, but there is at least this IE and DX problem, and also the installer once asks something about installing unsigned drivers, which should not happen in an untouched, clean installation. I liked to use that version of HFSLIP 2000 for my testing because, well, it is so much faster, but I will not do it anymore. That version is currently available to download at my GitHub, but it is not advertised anywhere else otherwise. The FullPack uses just the standard version of HFSLIP 2000 as well. My question then is - @win32, did you happen to use the experimental version of HFSLIP 2000 by any chance? On the other hand, the problem with .NET is unrelated and I believe it is simply HFSLIP being unable to properly slipstream it. All the files are copied to the system folders correctly, but there is likely an error in the file registration and executing process. I will try to see if there exists any simple fix to this issue. In the worst case, I may simply end up disabling the automatic installation, and leaving only the manual installation through the Add/Remove Programs applet in the Control Panel. Right now I will very likely remove the broken experimental version of HFSLIP 2000 from GitHub, as I have not been working on it any longer. I actually do not want to do any more patchwork on HFSLIP, and I have some other ideas in mind for the future, so for now I will concentrate on bug fixes only.
×
×
  • Create New...