Jump to content

WinNTSetup v5.2.4


JFX
 Share

Recommended Posts

Does  NoPageFile=0 have any effect when installing to a VHD? In such a case, I've been setting NoPageFile=1 and wondering if it even matters.

I read somewhere that if you use a vhd file for booting, you have no possibilities to reserve space for the pagefile inside the vhd (Windows does not support it). You need to place the file outside of the virtual drive. I'm not sure if that's correct though.

Edited by click-click
Link to comment
Share on other sites


I keep forgetting what some ini values do such as BCD= MERGE IDE=, DriversMode=, DriversWinRE= etc.. Is there one place where the less obvious entries are explained?

I see there is a Help for the [Options] section. A lot of the items in the other sections are self-explanatory, but not all and I tend to forget those. :unsure:

[WinNT6]

[WinNT6\TWEAKS]

[WinNT6\READY]

[VHD]

Thanks ...

 

Edited by click-click
  • Like 1
Link to comment
Share on other sites

Yes, NoPageFile has effect on VHD, too. Windows does not like to put the pagefile.sys inside a VHD so it would just use another drive.

As for the ini file simply use WinNTSetup to set the options.
Everything you can't set in the GUI is explained inside WinNTSetup.ini.txt.

Edited by JFX
Link to comment
Share on other sites

@JFX

Some issues abbout GUI

Type error in translation

User string space is not enogh.

Move field about user/password on the right and icnrease space for text string

"Group" string aligned on center on drop down list

Screenshot about explanation and changes after.

WinNTSetup - 01.jpg

WinNTSetup - 02.jpg

Edited by bovirus
Link to comment
Share on other sites

Where does "drive letter preassignment" for Vista/7/2008 take the letters from? The current system? Currently I have boot drive C with NT5 on it, and B as the potential installation drive for NT6. I would like for the new system to see them swapped for better compatibility (the system should be C, and the boot should be B). I expect the boot code to reside on current C, and retain the ability to boot into NT5. Can I achieve this with WinNTSetup?

Link to comment
Share on other sites

"drive letter preassignment" does nothing if you only have 2 drives and want both to be changed.
If you select C: as boot and B: as installation drive than:

- you will be able to multi boot both
- your NT6 system will be see it self as C:

but your NT5 partition will properly get a D: as drive letter

Link to comment
Share on other sites

@JFX

Strange Isuue in GUI

Seems that not all strings in WinNTSetup GUI are included in language file.
Some menu options seems get automatically by Windows OS syem in native language.

Please check screenshot.
My system is Windows 10 64bit Italian.

I rename 1040.dll as 1040.dll.old and started WinNTSetup.

The menu are all in English except some strings that remain in Italian.
The Italian language is not available and seems that WInNTSetup get these strings from Windows OS.

Could you please include these strings in language file?


Thanks.

WINNT Setup GUI.jpg

Link to comment
Share on other sites

1 hour ago, bovirus said:

Could you please include these strings in language file?

Nope, that's a feature! Besides the last 6 are directly coming from windows.

Link to comment
Share on other sites

I'm having a problem booting Win7 from a vhd on a USB Flash Drive. The OS boots, but it stops after doing some initial processing with the msg:

Windows could not update the computer's boot configuration. Installation cannot proceed.

I used WiNTSetup to format the flash and to create the vhd. I don't understand what the problem is.
See attached ini and log for more info.

If I install Win7 on a vhd using a HDD test partition with WinNtsetup, booting and install work fine.
Thanks for any tips or suggestions.

Edit: I restored a Windows7.vhd that I had which boots from the same flash (only replaced the problem vhd) and that works without problems, so it looks like something in the wim integration. There are differences in the old and new WinNTSetup logs

W7_WinNTSetup.ini WinNTSetup.log

WinNTSetup.oldlog

Edited by click-click
Link to comment
Share on other sites

I installed the system ok. The original C: drive didn't get a letter, but luckily the registry still uses the familiar format of DosDevices, so I could add it.

For some reason, the BCD boot data wasn't created: it gave a cryptic error that I failed to print-screen. I also found that a boot.ini from an entirely different disk got copied to the boot drive. The BCD command-line utilities that I installed were from Windows 7. The "ADK" that gets downloaded automatically has utilities incompatible with WinXP. If I already have new Windows running that can run the new "ADK", I'd be less likely to need to setup another copy of new Windows. The requirements of a tool like this should be minimal.

I understand you want to dance around licenses with the ADK download...

Link to comment
Share on other sites

  • JFX changed the title to WinNTSetup v5.2.4
  • wimb featured this topic

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
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...