Jump to content

JFX

Member
  • Posts

    1,271
  • Joined

  • Last visited

  • Days Won

    6
  • Donations

    0.00 USD 

Everything posted by JFX

  1. Hmm, I really would have thought they would be marked as spanned wim, but they are not. One has only Metadata and the other only resources. This should fix it now: http://1drv.ms/1ICThCV
  2. You can try new beta version: http://1drv.ms/1GB4OOt It will now search for *.rwm in the same folder, if the wim is multi part.
  3. HI sincere74, this is the first time i read about these Riprep Images. Is there a way to apply them using imagex or dism?
  4. Dism will load dynamically what it needs, like VHD or WIM providers. Since all is located in the same cab file, compete dism package is downloaded. also including - power shell scripts - api sets to run dism on older windows host - drivers to mount WIM or access wimboot / compact setups
  5. It's mainly a bugfix version, only new thing is the support of the new wofadk driver from latest win 10 ADK. So with other words, wimlib isn't the only way to apply in wimboot mode using a Windows 7 OS. I also removed the version check for wimboot, as it's now possible with win7 and win8.0.
  6. Updated to version 2.1.3 - added -w2k3disk switch - updated Windows 10 files to 10.10041.0 10 Build 10074
  7. @laddanator Chris is right, you running out of RAM. Win8.1 SE x64 will use ~ 1.7GB by it self already, so there not much left for any program. I will increase pagefile size in next version, but you should reconsider using a x86 windows for such an office pc. X64 starts to makes sense if you have 4GB or more RAM.
  8. @belivakov it should be possible to do your PPPoE in unattend.xml. @Lordk1 a very unusual error, is this really a clean install.wim?
  9. @lkertezcan Sorry have no idea about the "Windows could not complete the installation" error, I never experienced that one. The Windows Update can't work in OOBE mode anymore, that's a change Microsoft made with Windows 8.1. There is a "no extracting" feature using command line WinNTSetup_x64.exe NT6 -noapply -bcd:none But mount and preassigment only work for your current disks, as it saves the MBR signature and the partition offset. Not so sure you want that in your wim.
  10. Have you looked a the setup log files inside \Windows\Panther folder? There should be a setupact.log and setuperr.log.
  11. This combo box is the firmware type option for BCDBoot.exe.
  12. It's hard to find out what original Windows setup actually does. Maybe it's a BSOD, have you disabled automatic reboot?
  13. There was indeed a problem with user creating using, but only using x86 exe. Switching off system restore works, on vista and later quota is set to 0. It's not so easy to fully disable it on nt6, I wanted to address this with a service like I did with password reset. But that resulted in to many false positive AV reports.
  14. Well, it's a technical preview, they can brake or change functionality with every build as they like. So no, there is no way to tell.
  15. You right, it gives this "wrong paramter" error if the vdisk is already attached or detached. I uploaded new version, that should fix the gui not want to create a vhdx.
  16. Hmm, no I use diskpart.exe and that decides between the 2 by extension. But I wonder that there is a problem with attaching them.
  17. @RUSerious you are right there is a problem with the file extention, I'll fix this later. @Atari800XL Problem is Microsoft lately produce dirty images that contain boot files. files like the following should not be in the image, but create with setup on the boot partition. \boot\ \efi\ \bootmgr \bootnxt this time there was even an empty bcd store, but bcdboot is designed to extend an existing or create a new one. It can not handle an empty one. An yes please mention these issue, whenever you find them.
  18. So, new version is up with a workaround for bcd problem.
  19. By default bcdboot option creates both types of firmware boot files. For the tweak, no, this will not be added. The new Console should be a great feature. Let put some hope in MS guys, to fix all the bugs.
  20. The error comes from bcdboot.exe while creating the EFI bcd store. With this new leek, it creates an empty hive and than complains that it can not open the main key. Well this will be easy to fix, but i wonder why it happens.
  21. Hi Holger, There is hardly any reason why it could crash after using tweaks options. What software do you have installed on your system? I remember TeamViewer as one app, that inject hook in other programs which tend to crash on window creation/destruction. @Atari800XL Just wonder, how is it if you try with proxy?
  22. Updated to version 2.1 - file size trimmed down - added -windiff switch- added -xpwinload switch- added Windows 10 TP ADk
  23. Changelog is also in the zip file as comment, if you use WinRAR for zip files.
  24. It works here on WinXP, maybe you added a newer wimgapi.dll to the tools folder? Website is currently a bit slow but works.
  25. Yes, in the original WTG, the drives are offline. But I decided to not do that, cause properly the half of the users would ask how to fix that.
×
×
  • Create New...