Jump to content


  • Posts

  • Joined

  • Days Won

  • Donations

    0.00 USD 

Everything posted by JFX

  1. Indeed strange. "I/O error status of 0xc000007f" sounds more that something on your system is broken (RAM, DISK or even some system file)
  2. I tried the release preview, works alright for me. Alpha 4 has no other changes. What version had this error the 2.2 or the 2.3 alpha ?
  3. Thanks for the report. I have not loaded the release preview. Either the install.wim is corrupted or the MS guys changed their WIM format again. maybe alpha 4 can handle it: WinNTSetup2.3 alpha4
  4. @Homes32 Thanks, looks much better now. Added more command line options, see: GetWaikTools -? Already done.
  5. That's great work Thanks! I have integrated your code, cURL.exe is no longer needed but can be copied next to the tool, to be used. @Chris Thanks for the report, should be fixed now.
  6. Thanks Homes32, it seems to work, but I only receive the first 8KB of Neutral.cab. And then get: "This handle value has been terminated."
  7. Yes the version form click-click's link
  8. Thanks guy, good to hear it works! Well it would properly be possible, but would need an CDFS expert to know how much form the beginning of the ISO is needed. If one of these ISO-tools receive the absolute/relative offset and filesize it could be passed to cURL.
  9. Done. Hmm, I don't think that a 650 KB exe is big, but seriously your right the actual download is not more than that: curl -N -r 129740800-136032256 http://download.microsoft.com/download/8/E/9/8E9BBC64-E6F8-457C-9B8D-F6C9A16E6D6A/KB3AIK_EN.iso -o"Neutral.cab" 129740800 - 136032256 is the begin and end offset to download, easily to get with an good HexEditor The 500+ lines au3 code is used to decompress the broken cab file, rename and sort the files according their architecture. To avoid corrupt downloads, all files are hashed in the end. Should work now in WinXP, too
  10. Good you had backups. For me XDEL works as assumed without parameter it shows the help screen. Using /? is also logical, but your right it's unexpected.
  11. W2k3_SETUPLDR_SP2_to_SP1.xdelta3Most of us don't really need/use the WAIK to build our custom WinPE's. So there were always a problem to get the few tools like wimgapi, imagex or the WIM filter drivers. Attempts were made to use httpdisk to download files from inside the WAIK iso, but it was not a good solution as you still need to load hundreds of MB and it requires to install an unsigned driver. You even had to set your x64 Windows in testmode ... But now we came with a good solution: Our tool uses cURL winhttp functions provided by Homes32 to download only the needed bytes for the hugh WAIK ISO's. There is no need for admin rights and you only need to download 4-6 MB per choosen WAIK. For command line: GetWaikTools -? W2k3_SETUPLDR_SP2_to_SP1.xdelta3 GetWaikTools.zip
  12. Ha, ha I know what you mean. Yeah sometimes a project make a lot of fun while doing it, but someday one noticed there nothing more to improve. Thanks for the feedback That's great news. Finally a good way to remove a windows installation without formating and XDEL is also pretty fast Thanks
  13. Hi Nuno, interesting work. But what's the sense of it? I don't really get it It doesn't seems to handle hard links nor does compression works. So it seems it's more or less at the same state as 7Zip. Without compression boot time and RAM usage increase extremely ... But even bigger problems: It seems one have to be a member of the reboot.pro forum to even download it. And if I want to include it in my public projects, I would need to support it on this website? Also every Windows 7 (and later) systems do include the WimGAPI libray that allow handle WIM files at ease.
  14. A bit late, but here are 2 new imdisk installer that works (silently) in all WinPE. Also linking to new Alpha version, as there won't be any new version in the near future ... This version has a lot of rewritten code and was not tested fully. If someone noticed bugs or even mange to crash it, please report.
  15. Sadly Vista is very limited in offline servicing. The only way to change the drive letter of vista installations would be to use the normal setup.exe. And creating a new sysprep image.
  16. This option is not supported for Vista installations, but for Windows 7 and later it should be avalible. I'll take a look at it. Yes all versions of WinPE are supported. This seem to be a problem of the imdisk installer. You could add crtdll.dll from an x86 Windows 7 in the same folder as imdiskinst.exe or unpack it with 7zip and run install.cmd manually. Seems Olaf has ruined the silent install anyway with that msgbox pop up. I'll make 2 new install packages to fix this and also add support for vanilla x64 Winpe. All Windows 7 versions would support VHD booting, but it's a license restriction. During logon there is a check made for Kernel-NativeVHDBoot, think through SLGetWindowsInformationDWORD. You would get an error and stuck on logon screen, if you use a lower edition than Ultimate. I proplery could fix that , but some people would have a problem with this.
  17. Thanks for the infos. Indeed Winntsetup doesn't use language.ini it only get information form the image index xml you posted. It actually don't touch any language settings, besides setting the received language in the BCD store. Well i tried a few different language packs on my german install.wim file and had no problem. I have no idea's what could be the cause here ... That could explain it =) hmm maybe, thought that's actually what I did with WinNTSetup very often with no problem
  18. Need more infos, simple /Add-Package for langpack works alright for me. Did you used /Set-UILang, /Set-UILangFallback, /Set-Syslocale, /Set-UserLocale, /Set-InputLocale, /Set-AllIntl, /Set-SKUIntlDefaults, /Set-SetupUILang ? Why are there so many possibilities anyway
  19. Yes, it applies the WIM file and setup bootmgr and the \Boot\BCD store Not sure want happened there. How was that image created?
  20. Thanks, have fixed this. Btw: You will need to add leading and trailing quotes if the command includes spaces. -RunAfter:"myprogram.exe parameter 1 parameter 2 parameter n" RunAfter will now also add infos to log file.
  21. Update: Version - fixed command line -drivers not worked in some cases (Thanks Atari800XL) - fixed command line -NT5/-NT6 not standalone (Thanks IceBlackIce) - fixed command line -RunAfter not works with relative path (Thanks IceBlackIce) - fixed some bugs with the ISO file option (Thanks Lancelot) - fixed Windows 7 N and KN versions were not accepted for nativeVHDBoot - fixed GUI respond a bit slow in last versions - added bootmenu now contains edition name and VHD mark - added log file now contains details of successfull and failed driver integrations (Win7 only)
  22. For Windows Vista and 7 the offline servicing tools pkgmgr and dism are use directly on the selected folder. XP and 2003 Install are a bit different: - drivers are copied in "Drv" folder in the root of the installation drive - all sub folder from this will be listed in "OemPnPDriversPath" of the unattended file "winnt.sif" - MSSTMake is used on this folder to extract mass storage drivers and required information to load them in TXTMode of setup - MSSTMake results are merge in txtsetup.sif and setupreg.hiv, found driver files are copied to $WIN_NT$.~BT folder in the root of the selected boot drive
  23. Hi LeoZhu, You very quick finding the language.ini. This "feature" is not ready yet and will change in subsequent version. Well it's up to you, I've uploaded version that will accept the file in "unpacked" form. @Atari800XL, You would need the rebuild the ISO with these files added to \I386 folder. Carefully deleteing the lines in txtsetup.sif may help, have not tryed this. Maybe the same goes for dosnet.inf also. But you could also copy these files after WinNtSetup has run. Place them inside \$WIN_NT$.~LS\i386\ folder. The nomral Windows setup parses the txtsetup.sif and dosnet.inf to build up the $WIN_NT$.~LS folder. WinNTSetup just copies the complete i386 folder. @IceBlackIce Thanks, fixed in version
  24. I think The reason of these errors is that setup somehow request these files in both states, compress (oleacc.dl_) and uncompressed (oleacc.dll)If you only have oleacc.dl_ than try add expanded version to the same location. (with expand.exe or 7Zip) if you only have oleacc.dll than just make a copy and rename it to oleacc.dl_ (does not need to be compressed API accept it both ways, just the extension matters ) Thanks! Actually I highly appreciate feedback! Supporting all these windows version is very time consuming. Knowing problems helps a lot.
  25. Atari800XL, Please download again, I used wrong return code in one function that must cause failure of the "-drivers:" parameter. For nlite packs, I only fixed some that were reported multiple times. Fixing the root of this nlite problem would be way to much work. Thanks for reporting these bugs
  • Create New...