JFX

WinNTSetup v3.8.6 / 3.8.7 Beta 4

1,535 posts in this topic

Personally, I also found the term 'Installation drive' confusing and had to double-check when I first saw those words.  

MS refer to the volume containing the boot manager files as the 'system' drive and the volume containing the Windows OS files as the 'boot' drive - which is also really confusing (even the MS techs agree it is confusing!). 

I think it would be clearer to say

'Select partition for boot files'

'Select partition for Windows files'

F1 help text could contain some text about 'The boot files and Windows files can both be placed on the same partition'

I don't know if it is possible, but when a drive letter is chosen and selected by the user, can the field say something like 'C: (disk0, partition 1)'  instead of just  C: - this would be helpful on multi-drive systems.

Edited by steve6375
0

Share this post


Link to post
Share on other sites
22 hours ago, steve6375 said:

Personally, I also found the term 'Installation drive' confusing and had to double-check when I first saw those words.  

MS refer to the volume containing the boot manager files as the 'system' drive and the volume containing the Windows OS files as the 'boot' drive - which is also really confusing (even the MS techs agree it is confusing!). 

I think it would be clearer to say

'Select partition for boot files'

'Select partition for Windows files'

F1 help text could contain some text about 'The boot files and Windows files can both be placed on the same partition'

I don't know if it is possible, but when a drive letter is chosen and selected by the user, can the field say something like 'C: (disk0, partition 1)'  instead of just  C: - this would be helpful on multi-drive systems.

Maybe the dangerous part is most of the mormal users don't know how to use the diskpart (I often use PartAssist to change the partitions)

0

Share this post


Link to post
Share on other sites

JFX, for a few years now, I'm using the command line option "-drivers: L:" to add drivers at "setup time" with WinNTSetup. I'm checking which PC I'm using, then I'm mounting drive "L:" with the corresponding drivers. This has always worked perfectly (with one XP exception, I've asked about that case before, but that's not the issue now).

With the latest Windows 10 versions (tried both Pro1607 and LTSB1607), something seems to have changed, because the drivers (video, in this case), are not auto installing anymore.

Can this be solved by adding the latest DISM to the tools folder? From a different thread (GetWAIKTools) I seem to recall this might cause some problems with Windows-7 based PEs? I'm using lots of different PE's, so I would really like your advice on this before I start messing with DISM versions... (EDIT: My current DISM folder has the oct-2015 files).

Can you confirm that indeed something has changed with adding drivers? Thanks!

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

No problems here. Integrate drivers to 1607 release from my win7pe works as it should.

You can check the log file in \Windows\WinNTSetup_Dism_stdout.log, to know if the problem is about integration.
Or if there no error than check \Windows\Inf\setupapi.setup.log.

The DISM folder in tools currently only needs the wofadk.sys and api-ms-win-downlevel*.dll files form from ADK5 (v. 9600)

0

Share this post


Link to post
Share on other sites

Thanks JFX, for pointing me to WinNTSetup_Dism_stdout. I believe it was my stupid mistake (once again...), because this is what that file reads:

"You cannot service an x86-based image from an x64-based host that does not support WOW64."

Sorry, I forgot about the fact that I have been testing some "x64 only" PE builds (both SE and normal ADK PE's) without WOW64. Thanks for replying so quickly, so I can nip this (self-created) problem in the bud. I will have to adapt my PE scripts to include checks on this. I must admit I didn't know about this issue until now, so I've learned something new!

I will test again and add a small edit to this post if everything goed well again. THANKS again!!!

EDIT: Tested and confirmed. Thanks again JFX, I'm sorry for wasting your time, but I'm very happy that I found the solution!

Edited by Atari800XL
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.