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. 


JFX

WinNTSetup v4.2.5

Recommended Posts

During setup or during WinNTSetup ?
In case WinNTSetup update the bootsector, it will be logged in the logfile.

I tried with Terabyle MBR.exe utlility, that add Press F?? Key boot option. Works with NT6.x installs.

Share this post


Link to post
Share on other sites

During WinNTSetup. It happens at the very end after the updating boot code message. The yellow ball then turns green. I can't find a log file. Is it supposed to be on the drive where the system is installed?

If you have a binary compare app, I can send you the before and after versions of the MBR  I'm not sure if the mbr exe uses the same amount of code for the MBR like Bootit Bare Metal.

Edited by click-click

Share this post


Link to post
Share on other sites

Log file is in the ?:\Windows\WinNTSetup.log.
How you disable the bootsector update, command line or ini file?

Share this post


Link to post
Share on other sites
3 hours ago, JFX said:

Log file is in the ?:\Windows\WinNTSetup.log.
How you disable the bootsector update, command line or ini file?

From the drop-down in the GUI (do not update boot code). Did not know there was an ini entry or cmdline parm for that. I must have missed the discussion about it. What is the ini entry supposed to be?

I see BootSect=2 after I updated to the newer .ini

WinNTSetup.log

Edited by click-click

Share this post


Link to post
Share on other sites

Your log file is from version 3.8.7.3, the bug should be already be fixed in the current version.

Share this post


Link to post
Share on other sites

Sorry, old version from a disk that I restored. I will redo an install ans send the correct info.

Share this post


Link to post
Share on other sites

I'm back in business now. I don't know what happened the last time when my MBR was overwritten. Maybe I unknowingly used the old version. This time the yellow ball stayed yellow. Sorry for the confusion

BTW, what is the ini setting for /nobootsect ?

WinNTSetup.log

Edited by click-click

Share this post


Link to post
Share on other sites

Good, the ini option would be:

[WinNT6\READY]
BootSect=0

But better you set all GUI options and create a new ini file.

Share this post


Link to post
Share on other sites

Hi Sergei,

The name comes from the XML of the WIM file.
<DISPLAYNAME> is used. If this does not exists than <Name> is used.

See: imagex -info wimfile.wim

Edited by JFX

Share this post


Link to post
Share on other sites

@JFX:

I always use WinNTsetup. I don't never use (and liked) Windows Setup (Boot.Wim). Thank you for your efforts and updates.

I have a few notes.

1) WinNTSetup_x86.exe's v3.8.7.4 gives that error: "An internal error occurred in the Win32 x86 emulation subsystem."
For technic details is here. I keep to installs lastest the Visual C++ Runtime Installer (All-In-One) by Burdafel.
Actually no need WinNTSetup_x86.exe for me when running in win10 x64. It's works all Win7 PE.
Still, I just wanted to you informed. Because WinNTSetup_x86.exe's version 3.8.7.0 working without this WOW error given in Win10-x64-(v1607). Strange.

2) In Command lines options unlisted -noapply

3) First Suggestion: I know, The WinNTsetup's ChangeLog contained description in the RAR package. But only there. I recommends you that created new folder (for example: Documents) in the RAR package. And can be added Changelog.txt/History.txt in Documents folder? Also WinNTsetup's full command-lines as file in again this folder(CommandLines.txt)?

4) Second Suggestion: WinNTsetup opens the Format feature from "F" button. I would recommend a new button next to it: "Only Delete Windows Folders". I prepared (and using) this batch file (of course it lazy coding and can made more optimization, like you masters). So, No need format to disc/partition. Thus it's enough to extract files from WIM file.

I'm sorry, my bad English.
Regards...

Edited by ilkertezcan
Correcting

Share this post


Link to post
Share on other sites

Hi ilkertezcan,

1) It's no bug, I'm going to remove support for WinNTSetup_x86.exe running on x64 OS.
Reason: There are some API's that can not work in WoW64 emulation,
I though i could find a good solution, but it would just makes thinks to complicated.

Also there is an faster x64 version available, don't know why sp many people want to run the x86 version.

2) Good, will add it to help.

4) Not so sure I like to add that.

Edited by JFX

Share this post


Link to post
Share on other sites

@JFX,

Thank you for your reply and info. I will consult to you soon about an off-topic (from PM because of I don't know your e-mail).
 

Share this post


Link to post
Share on other sites

When adding more than one driver, do I put all the driver package files in one directory?

Edited by click-click

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.

×
×
  • Create New...