[JFX]

First command line option must be one of the following: /NT5, NT6 or /VHD all others don't need any order.

WinNTSetup2_x86.exe /NT5 /DisableSFC should work.

[click-click]

JFX, on 18 January 2013 - 11:34 AM, said:

First command line option must be one of the following: /NT5, NT6 or /VHD all others don't need any order.

WinNTSetup2_x86.exe /NT5 /DisableSFC should work.

Sorry, I missed that in the spoiler. Anyway, I ran an install with DisableSFC and got errors in setuperr.log

Error:
Setup detected that the system file named [c:\windows\system32\sfc_os.dll] is not signed properly
by Microsoft.  This file could not be restored to the correct Microsoft version.
Use the SFC utility to verify the integrity of the file.

***

Error:
Setup detected that the system file named [c:\windows\system32\syssetup.dll] is not signed properly
by Microsoft.  This file could not be restored to the correct Microsoft version.
Use the SFC utility to verify the integrity of the file.

***

Also my dllcache still had 500MB after the install finished. I went back and redid the install without DisableSFC and setuperr.log was clean.

This post has been edited by click-click: 26 January 2013 - 08:54 AM

[JFX]

These errors in setuperr.log are normal for patched files.

Version 2.3.4.0 is up. It fixed quite same bugs and should also solve your SFC problem.

This post has been edited by JFX: 09 March 2013 - 10:29 AM

[Atari800XL]

Thanks for the new version. I can't say that I noticed any "bugs" lately, so now I wonder which bugs you fixed in the new release....

Also, are you saying that disableSFC was not working with XP setup before? So I should test XP setup again with the latest version?
Sorry for asking, but it's just that the previous version was working OK for me, and the only reason for a new test would be the DisableSFC thing...

Thanks for WinNTSetup!!!!

[JFX]

DisableSFC patch is a bit tricky, WinNTSetup will avoid making changes to system dll files if it's not entirely sure.
Before Vista every windows language was a bit different. Cause I don't have all languages and service pack, it may not work in all version.

Most other bug were just silly coding, that properly never had cause any problem, but should have been fix.
Only serious bug was with driver integration for windows 8, while running under windows XP.
Well it's getting harder to support XP, but i don't give up yet

[Atari800XL]

JFX, on 01 February 2013 - 05:01 AM, said:

Only serious bug was with driver integration for windows 8, while running under windows XP.
Well it's getting harder to support XP, but i don't give up yet

OK, thanks for your reply, but it leaves one thing open: You mention that "driver integration for W8 was buggy when running under XP".
So when you say support for XP is getting tougher, is that:
(1) Running WinNTSetup from XP (which I never use, I use WinPE_SE = W7)
(2) Using WinNTSetup to *install* XP

...or both?

[JFX]

Just the 1st case, the dism from windows 8 doesn't really like to run under Windows XP/2003.

[Atari800XL]

I guess it wouldn't be a very big problem if you decided to "reduce" the possibilites to run WinNTSetup from XP, as long as using it to install XP is still possible.

Speaking of which: I always run WinNTSetup from WinPE_SE, which of course you also have (had?) a lot of involvement in. Do you still recommend that as a platform (or even the best platform) for WinNTSetup? Or are there better alternatives? I did some testing with PE4.0 (just the standard Windows 8 PE, with XYPlorer as a shell and Autohotkey for running my most used utilities with a single keystroke, no real need for a normal shell with menu etc).

WinPE_SE is wonderful, but there may come a time to "upgrade" the base for WinNTSetup to PE4? I have no complaints at all about WinPE_SE, it's just strange that sometimes it freezes at boot time ( I always use USB), it looks like there's a problem with some processes waiting for other processes to initialize, which ends up in a freeze. A reboot/ reset usually solves this, but it would be nice to know who is waiting for who... That's the only (tiny) blemish on this perfect system!!!!

This post has been edited by Atari800XL: 02 February 2013 - 03:37 AM

[JFX]

As long WinXP is still used by some many, i'll try to keep supporting it if the workarounds are that easy.

Yes, Windows 7 or a PE3 based PE like Win7PE_SE are the recommended platform to run it.
Some goes for Windows 8 and PE4, but both of them still are under development.

Never had a freezing problem, maybe it's Grub4DOS causing it on some machines, but just a guess.

[zpimp]

please help
i just installed win7 pro
from an xp pe using winntsetup v 2.3
i checked [ drive letter preassignment ] and [ mount installation drive as C: ]
now i get this
red is the bootdrive, and all removable i connect shows 2 times - green
i suspect is winntsetup, even though i used the same version before
in diskpart i only see each drive/partition once

[JFX]

hi zpimp,

open cmd.exe with admin rights and use mountvol to remove the wrong letters.

example: mountvol Y: /D

[zpimp]

thanks for the fast reply, it worked
any idea why did it happen ?

[JFX]

Sorry, have no idea why this is happening.

[xcv150]

Hi, JFX! How to integrate MassStorage drivers in Win Xp, Win 7 and Win 8 program WinNTSetup???

[Scampy82]

Hi JFX!
Some questions for you

I have win7.wim with 4 Windows editions:
1 - Home Premium x86
2 - Ult x86
3 - Home Premium x64
4 - Ult x64

Install win7.wim: WinNTSetup.exe -NT6 -source:Y:\LIVE\winsetup\win7\win7.wim -syspart:C: -WimIndex:2 -tempdrive:C: -unattend:"win7\Autounattend.xml" -Sysletter:C



If I choose 64 bit edition, description on top remains 32 bit edition. Why?




Are there still no command lines keys for function "Disable automatic system Restore..." and "Turn off USB..."?

This post has been edited by Scampy82: 18 February 2013 - 06:52 AM

[JFX]

xcv150, on 17 February 2013 - 08:34 AM, said:

Hi, JFX! How to integrate MassStorage drivers in Win Xp, Win 7 and Win 8 program WinNTSetup???

Hi xcv150!
Just make sure your MassStorage drivers are unpacked, the *.inf files must be available.
So just select this folder under the "Add Drivers" option and they will be integrated.

Scampy82, on 18 February 2013 - 06:51 AM, said:

Are there still no command lines keys for function "Disable automatic system Restore..." and "Turn off USB..."?

Well, there is -DisableSystemRestore but as already told we can't have cmdline options for everything so get familiar with the ini file

For the combo box, yeah reproduced. It only happens if wimindex is used in command line.
Had not thought someone would specific something as cmd parameter and try change it right after the app has started

But it's no serious problem only description is not updated.
You can use mouse wheel while the box hast focus to manually fix it for now.

This post has been edited by JFX: 18 February 2013 - 09:59 AM

[Scampy82]

JFX, on 18 February 2013 - 09:59 AM, said:

Well, there is -DisableSystemRestore but as already told we can't have cmdline options for everything so get familiar with the ini file

You are right it is time to transfer on ini files

[alacran]

JFX

Could you please make available for me the v2.3.4.0 language.ini in order to update Spanish translation.

Thanks in advance

[JFX]

Oh, I forgot to update it. Here is the latest language.zip

I put that link to 1 page, but so far I don't expect any language changes for version 2.x anymore.

[xcv150]

Thanks JFX! WinNTSetup drivers zip archives can process and integrate or just the drivers are unpacked, the *. Inf files???

This post has been edited by xcv150: 21 February 2013 - 12:12 AM