• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
JFX

WinNTSetup v3.8.6 / 3.8.7 Beta 3

1,519 posts in this topic

That means that wimlib has a problem with applying a file or other NTFS data from the WIM to disk.

 

If your drive D: contains data already, than format it and try again.

If this not helps, right-click on title bar --> "WIM API" and select WimGAPI.

0

Share this post


Link to post
Share on other sites

Final Version 3.6.0

- new option to use wimlib 1.7.0 for all WIM operations*
- wrong error message for VHD checks
- fixed applying failed on to low system free space
- fixed avoid wimboot uses on server type OS
- fixed applying to a folder if current working dir has the same root as install drive
- added -regtweaks:{path} commandline and gui option

*You have to add the wimlib dll files to "Tool\x??\wimlib" folder
and add "-wimlib" commandline parameter

0

Share this post


Link to post
Share on other sites

3.6.0 gui wimlib 1.70 failed to copy $OEM$ folder twice. u might wan to check if smth broken

i checked twice my $OEM$ folder exist and with files inside.

 

edit:

wimgapi broken too. folder were created, but files were not copied.

Edited by josywong
0

Share this post


Link to post
Share on other sites

Hmm, can't reproduce it, but try re download, I reverted back to an older fileop.lib

0

Share this post


Link to post
Share on other sites

thanks for the update. it is now copy-ing $OEM$ files as usual

0

Share this post


Link to post
Share on other sites

Hello 'JFX'

 

Can 'WinNTSetup v3.6.1' install 'Win 8.1 Update1' in both 'BIOS/MBR' drive partitions and 'UEFI/GPT' drive partition without changing Partition scheme ?

 

 

1-

 

IC570854.jpg

 

 

 

2-

 

IC514408.png

 

 

I mean Can 'WinNTSetup v3.6.1' install 'Win 8.1 Update1' into 'Windows Partition' of both 'BIOS/MBR'  and 'UEFI/GPT' partition scheme without converting partition scheme ?

 

Please confirm if it works for both.................

 

 

Thanks...........

0

Share this post


Link to post
Share on other sites

@kreker

Thanks, for the updated language file.

 

@devdevadev

Yes, of course you can do that.

0

Share this post


Link to post
Share on other sites

Well, thinking still the same ;)

 

devdevadev, please stop polluting this and other topics on every forum you see.  

0

Share this post


Link to post
Share on other sites

Hi,

 

Are there any known issues with Win 8.1 Enterprise 32b?

 

I have used the great WinNTSetup 3.6.1 method before to successfully install Win 8 pro to USB HD.

 

I have now repeatedly and unsuccessfully tried with Win 8.1 Enterprise 32b with exactly same procedure, on same PC, to same USB HD.

Everything was double checked and looked fine (MBR,  BOOTMGR.PBR, BOOT PART)  and installation was reported as successful, but the first reboot to USB HD looped to a blinking prompt indefinitely.

 

Thanks for any help,

 

edborg

0

Share this post


Link to post
Share on other sites

Hi edborg,

 

no there are no problems with Win 8.1 Enterprise 32b.

A blinking cursor on the top left screen is usually cause by a BIOS and boot sector incompatibly.

 

If possible delete the partition and create a new one with some partition software.

0

Share this post


Link to post
Share on other sites

Thanks JFX for your prompt reply  :)

 

I have done that already, more than once, to no avail.

 

I have now run bootsect.exe /NT60 X: to rewrite the partition boot record with the bootsect.exe version included in WinNTSetup v3.6.1, to no avail either. :wacko:

 

I may have to try to rebuild from Win8 as my previous attempts (including the successful ones for Win8 pro!) were made from WinXP

 

edborg

 

Ediit:

I forgot to mention that the Win8.1 Enterprise 32b is the evaluation version made available for free from Microsoft to IT developers

 

Update:

rebuild from Win8 did not solve the problem either 

Edited by edborg
0

Share this post


Link to post
Share on other sites

Just for the record,  not all bootsect.exe's are the same:

http://www.msfn.org/board/topic/171749-bootsectexe-various-versions-compared/

but the blinking underscore is usually an issue with partitioning (frequently connected with HS geometry), and bootsect.exe won't do anything to solve it (it just replaces the bootsector CODE, while the issue is more likely to be with the DATA).

 

jaclaz

0

Share this post


Link to post
Share on other sites

Just for the record,  not all bootsect.exe's are the same:

http://www.msfn.org/board/topic/171749-bootsectexe-various-versions-compared/

but the blinking underscore is usually an issue with partitioning (frequently connected with HS geometry), and bootsect.exe won't do anything to solve it (it just replaces the bootsector CODE, while the issue is more likely to be with the DATA).

 

jaclaz

Happy to "see" you here jaclaz!  :sneaky:
 
Based on your always detailed and reliable info I could ascertain that the bootsect.exe included in WinNTSetup v3.6.1 is the Win8 version (8/Waik4/PE4.x->6.2.9200.16384->25/07/2012->117,688 bytes).
 
I therefore downloaded with GetWaikTools the Win8.1 version (8.1/Waik5/PE5.1->6.3.9600.16384->21/08/2013->100.968 bytes) and updated the boot code with that.
 
However, as expected (by you), this did not solve the issue.
 
The USB HD I am using has three primary partitions with one Win8 working installation (and two non working Win8.1 attempts :no: ).
 
How could I solve the issue with the DATA in the bootsector without repartitioning?
Could I only (once more) delete and recreate THAT partition, without affecting the others?
If repartitioning is a MUST, how could I make sure that the problem doesn't show again on the freshly repartitioned and reformatted disk?
 
Thanks  :hello:
 
edborg
Edited by edborg
0

Share this post


Link to post
Share on other sites

A good idea would be:

1) starting a new thread, as this issue is unlikely to be related to WinNTSetup and it makes little sense to hijack this thread

2) provide some data about that hard disk, how it is partitioned, etc. and on the PC(s) you are finding this issue with

3) post as an attachment to your post on the new thread, inside a compressed .zip or .7z file, a copy of BOTH your MBR and bootsector(s) made using (say) Hdhacker : 

http://dimio.altervista.org/eng/index.html

or *any* dd-like tool you might have handy/you are familiar with.

 

jaclaz

0

Share this post


Link to post
Share on other sites

Discussion continues here

 

This link has been broken  :thumbdown

 

Post has been moved here

Edited by edborg
0

Share this post


Link to post
Share on other sites

How to add Windows XP installation in the Windows 8 boot loader ?

I've tried to add by using Bootice in the BCD file but got an error
0

Share this post


Link to post
Share on other sites

You can do it with bcdedit.exe

Bcdedit /create {legacy} /d "Windows XP"Bcdedit /set {legacy} device bootBcdedit /set {legacy} path \ntldrBcdedit /displayorder {legacy} /addlast

But you also need to copy ntldr, ntdetect.com, boot.ini and optional bootfont.bin from your XP partition to the current boot partition.

The one where bootmgr and Boot\Bcd is located.

0

Share this post


Link to post
Share on other sites

But you also need to copy ntldr, ntdetect.com, boot.ini and optional bootfont.bin from your XP partition to the current boot partition.

The one where bootmgr and Boot\Bcd is located.

OT :ph34r: This is what I never managed to get some accurate test results about. :w00t:

 

Possibly these files are not needed at all (i.e. BOOTMGR+boot\BCD+winload.exe can load a XP fine) :unsure:

 

Like:

http://www.betaarchive.com/forum/viewtopic.php?t=9602

http://www.msfn.org/board/topic/139807-difference-in-winloadexe-

 

Sanbarrow forum is not working, here is through Wayback Machine:

https://web.archive.org/web/20110106042923/http://sanbarrow.com/phpBB2/viewtopic.php?t=1695

 

jaclaz

Edited by jaclaz
0

Share this post


Link to post
Share on other sites

Yes, old winload.exe can load XP/2003, version of bootmgr doesn't matter.

If I remember right the Vista RTM version was the last working one.

 

But a small problem was that they checked for digital signature of the kernel.

And XP has no signed kernel.

0

Share this post


Link to post
Share on other sites

Hello Sir,


 


Which of the following method is more better (in terms of occupied Disk Space ) in order to create smallest


 'WTG + WimBoot + VHDX' Setup ?


 


1- WimLib way here (does NOT require win8.1u1 winpe).


2- WinNTSetup v3.6.1 way here


 


Note- WimLib way end up with a C drive occupied by only 250 MB (before 1st boot where pagefile.sys and hyberfil.sys will be created).


 


Thanks and Regards


0

Share this post


Link to post
Share on other sites
Hello Sir,

 

I got following error message for my 'install.esd' file.

 

Does following error occur for encrypted ESD files or I am doing else wrong 

 

How can I find out that my 'install.esd' is either encrypted or un-encrypted ?

 

Can I expect supports of encrypted ESD files from 'WinNTSetup 3' in near future ?

 

Regards......

post-394278-0-12043800-1404698560_thumb.

Edited by devdevadev
0

Share this post


Link to post
Share on other sites

You can not use esd files for wimboot.

 

For encrypted files, well you will notice it, if you try to apply them with any tool.

I can't support them without making changes to the wim files and that's not an option.

 

But maybe wimlib will support them in future ...

Edited by JFX
0

Share this post


Link to post
Share on other sites

HEy JFX.......

 

You can not use esd files for wimboot.

 

For encrypted files, well you will notice it, if you try to apply them with any tool.

I can't support them without making changes to the wim files and that's not an option.

 

But maybe wimlib will support them in future ...

 

Thanks, Now after uncheck 'WIMboot' option my 'install.esd' work properly. It means it is not encrypted. 

 

But How can I decide that 'install.esd' is encrypted/Un-encrypted ?

 

Final Version 3.6.0

- new option to use wimlib 1.7.0 for all WIM operations*
- wrong error message for VHD checks
- fixed applying failed on to low system free space
- fixed avoid wimboot uses on server type OS
- fixed applying to a folder if current working dir has the same root as install drive
- added -regtweaks:{path} commandline and gui option

*You have to add the wimlib dll files to "Tool\x??\wimlib" folder
and add "-wimlib" commandline parameter

 
I had created  'WTG + WimBoot + VHDX' Setup using 'WinNTSetup v.3.6.1' and 'install.wim' file. And it successfully completed and worked.

 

I had not added anything (wimlib dll files to "Tool\x??\wimlib" folder and  "-wimlib" commandline parameter ) in the WinNTSetup3\Tools\x86\wimlib folder, then why 'WIMBoot' successfully created ?

 

 But maybe wimlib will support them in future ...

 

Does you mean that 'WinNTSetup 3' and 'wimlib' uses different technique for creating WIMBoot ?

 

Does 'WinNTSeteup v.3.6.1' uses any other technique for 'WIMBoot' other than WimLib way ?

 

Which of the following three method will save maximum Disk Space ?

1-  WTG + WimBoot + VHDX

2-  WTG + VHDX

3-  Normal WTG

 

Which of the above method is best in term of 'Disk Space' , 'Speed' and 'Performance' ?

 

Question-  Will I have to use 'Dynamically Expanding VHD' in order to keep the size of the 'Windows81.vhdx' as minimum as possible so that there will be NO free space wastage within the 'Windows81.vhdx' ?

 

 

Regards.....

Edited by devdevadev
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.