• 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

1,518 posts in this topic

Thanks JFX, knowing that you find it interesting is reward enough for me :-)

 

Well, I could have edited/ deleted the whole first part, but I thought it might be an interesting read after all.

 

If it's really only one reg tweak, I can add it in my postinstall system, time will tell.

 

Thanks again!

0

Share this post


Link to post
Share on other sites

...edit mishap...

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

I guess, this more a matter of taste. A combobox has it's disadvantages, too.

Such as these ugly focus rectangles, or the need of a refresh button cause not everything send device message on changes.

With the current input box, you just need to push the key for the letter you want.

0

Share this post


Link to post
Share on other sites

JFX, "Harkaz" has released his first (?) public beta of an XPSP4 (English only at the moment).

 

I tried it on a clean XPSP3-ENU (as a standalone update, after installing with WinNTSetup, of course) and it seemed to work OK (very nice work by Harkaz!!). Then I tried integrating in into the XPSP3-ENU source, which seemed to work OK as well. But installing *that* version (SP4 integrated) with WinNTSetup was not a big success. Maybe this has to do with dosnet.ini/ txtsetup.sif (like the OnePiece pack), but I know too little about that to make a judgement.

I you ever have some spare time, maybe you can have a look. But **only** if you have spare time, because I know this is not a priority, specially considering the OnePiece Final pack/ updated source is already working very nicely. It would just be so cool if WinNTSetup would support this one as well.

Please share your views on this, if you decide not to bother, that perfectly understandable as well.

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

@Atari800XL

No not this time, adding support for Onpiece pack was just because it's final and was simple to do.

The XP setup stuff, I will not touch anymore, therefor the sysprep support was added.

However you should be able to solve these issues by compare the $WIN_NT$.~LS folder create by winntsetup and the one created by winnt32.exe.

 

@AZJIO

Hmm, I still don't see the problem with the file dialog that I currently use.

Edited by JFX
0

Share this post


Link to post
Share on other sites
@AZJIO

Hmm, I still don't see the problem with the file dialog that I currently use.

1. If there is an installation disk, then the address (disk:\sources\install.wim) is added to the list and it does not need to look for.

2. Why such a long input field if it is introduced one letter?

3. What the "F" button? Better "Formatting"

4. To select a drive, folder selection dialog is used.

5. Button with an icon is not obvious that it can be used. Apparently so is duplicated.

0

Share this post


Link to post
Share on other sites

602c3ae5b2eft.jpg
 
Here is the text on the button. (http://pastebin.com/Q02GvcEh)
 

Such as these ugly focus rectangles,

 
The combo focus only when the style $CBS_DROPDOWNLIST
I failed to change the font of a menu. Wanted to do a data column. Combo font permissible change.
 
It is obligatory to do the edited entry field? It seems to me enough to make information field.

Edited by AZJIO
0

Share this post


Link to post
Share on other sites

Azjio, no offense, but I think you made your point now, just let JFX decide...

That's why I asked him about the Harkaz SP4 pack, you can always ask, but if you get a clear answer from "The Master", you just need to accept it.

There's always the alternative of making your own "WinNTSetup", of course, I will immediately admit I'm about 200 IQ points too stupid for that.

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites
Hi JFX,

 

First, thanks for your hard work!

 

I'm faceing a problem whem i try to install xp or 2k3 x64 with 5eraph's Windows XP x64 post-SP2 Update Pack.

 

I have some error messages with WinNTSetup 3.5.1. File is attached.

 

Can you check it out?

 

Am i doing something wrong?

 

Thanks!

setuperr.zip

0

Share this post


Link to post
Share on other sites

HI Ikky_Phoenix,

 

This an usual problem with these update packs, they are not supported by WinNTSetup.

0

Share this post


Link to post
Share on other sites

@JFX, not offense meant at all I assure you, but since the "problem" seems to effect builds made with update packs from OnePiece, harkaz, and now 5eraph, and perhaps the other ones as well, and builds made with those update packs all install correctly with no errors from both DVD and USB when using other methods than WinNTSetup, it seems that there might could be a modification made to WinNTSetup to allow it to be used with such builds, if it is possible of course.  If nothing else, perhaps you could work with the authors of those update packs so that they could add whatever they need to allow proper operation with WinNTSetup but not interfere with installation by other means, but I think it makes more sense to make a change in one place, WinNTSetup, than to require changes in multiple update packs, again if possible of course.  I realize that theses problems appear to only effect XP and 2K3 which are both at or near EOL, but those OS still have a rather large market share and I have a feeling they will both continue to live on well past EOL.

 

WinNTSetup is a very respected tool that is being used by more and more folks and it would seem to be in the best interest of all to resolve this issue.  Just my opinion.

 

Cheers and Regards

0

Share this post


Link to post
Share on other sites

For me XP/2003 setup stuff is settled.
Decision made to not parse txtsetup.sif and not to rely on Setup API, was for various reasons.
And there have never been any problem with official hotfix integration.

If an update pack support installing with the normal winnt32.exe,
- and not all do, that properly one of the main problems -
than the author should be able to make it compatible with WinNTSetup, pretty easy.

0

Share this post


Link to post
Share on other sites

JFX was nice enough to fix a little issue with the OnePiece pack, only a few weeks ago.

If you want to use a fully updated XP source, just use the OnePiece final pack, WinNTSetup supports it quite nicely. I even use nLite "over" that source (just some minor settings), that also works nicely.

 

If it wasn't for WinNTSetup, I probably wouldn't even install XP anywhere anymore, it's just very easy to add the source to my Win8PESE USB, no extra trouble (all Windows 7/8 .wim files are on there as well). Also, if I wouldn't be able to create XP/W7/W8.1 (Grub4Dos-) multiboot setups, and image them (with Acronis, Macrium, etc, also from that single PESE USB), there's no way I would have XP around anymore.

When I can use it in this "easy" (...) setup, it's still nice to have it around, as I've said before, there are quite a lot of "specialist" PC setups that still use XP (sometimes with quite expensive hardware, like industrial label printers, weighing systems, etc).

So, XP to me is actually quite "safe" still, because in case of trouble, I can reinstall it in less than an hour (that's including my own "PostInstall" thingy).

 

Thanks JFX, for still supporting XP. Others: Just use the OnePiece pack, it's great, and quite easy to make/ integrate into any language XPSP3 source. At the moment, I prefer it over the new SP4 projects, because it's much simpler (in a way), more up-to-date (either with or without the new POSReady stuff), and you can turn on or off the components you want in winnt.sif.

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

XP UpdatePack from user_hidden using RVM Integrator has always worked for me using WinNTSetup.

If I recall correctly I once used 5eraph's Windows XP x64 post-SP2 Update Pack with RVMi and that too was okay as the source for WinNTSetup.

Edited by click-click
0

Share this post


Link to post
Share on other sites

Then maybe it's something that nLite does to cause incompatibilities with WinNTSetup?  if that is true, then nuhi might be willing and able to fix the problem.  That would be wonderful if it was indeed a change in one tool that would enable successful use of all the various update packs with WinNTSetup.

 

Cheers and Regards

0

Share this post


Link to post
Share on other sites

Sure the authors of nlite / ryanvm integrator could maybe fix the WinNTSetup problem with the double listed files.

Like the ones occurred in the OnPiece update pack.

However that will not solve the problems Ikky_Phoenix has here.

 

I'm sure using the normal "winnt32.exe /makelocalsource" install will rise the exact same errors.

 

And that's simply a bug in most update/addon packs, they only support install form CD/DVD.

Well, I can't make it any more clear, you just asking for solution in the wrong place here.

Edited by JFX
0

Share this post


Link to post
Share on other sites

So to switch the topic, there new beta version available.

 

This and the next Beta versions will use wimlib to handle WIM / SWM / ESD files.

Thanks to wimlib, it also adds support for wimboot without the need of the WOF driver.

 

Keeps in mind that's a bit experimental.

0

Share this post


Link to post
Share on other sites

Congratulations JFX, you're in the latest issue of "Com! Magazin" (German)!!!!

(Article "Boot from NAS", starting at page 44, WinNTSetup 3.4 is on pages 47,50 and 54).

post-350624-0-48797100-1402053644_thumb.

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

I just read the article now. Looks interesting :D

0

Share this post


Link to post
Share on other sites

I know JFX is a little bit fed-up with special XP packs-related stuff, but I just wanted to mention one more thing:

Harkaz' latest "Unofficial XP SP4 - Beta 3" is now completely compatible with WinNTSetup. Or as JFX would probably put it: He has removed all the non-standard stuff, so everything runs as expected.

I think this is actually very nice work of him, I tested the latest beta 3, it supports the standard /integrate switch, so I integrated it into a (en-US) SP3, then added Mass Storage drivers with DPbase, then installed with WinNTSetup. Finally in beta 3, this works without a hitch!

 

I still have to decide if this will prove useful (as we already have the great OnePiece pack, which you can even rebuild easily every month with the latest POSReady updates, or use nLite to add them to your source), but I do believe the SP4 is something extremely Cool! B)

I hope he finishes his documentation soon, because until now we only have en-US, it would be nice to have localized versions as well.

 

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

@JFX

 

JFYI, there have been two updates to winlib v1.70 Beta last one 17 hours ago, first one is about behavior regarding exclusion of absolute links and last one is about improved the LZX compression performance during export operation by a further 10-15%

 

Previous update: http://reboot.pro/topic/18345-wimlib-with-imagex-implementation/page-10#entry184745

 

Last update: http://reboot.pro/topic/18345-wimlib-with-imagex-implementation/page-11#entry184758

 

Regards

Edited by alacran
0

Share this post


Link to post
Share on other sites

Yes, wimlib improves quite fast. I'll wait until final is out, so we will have two finals.

 

However if you guys make apply speed test, don't forget that you have to reboot your machine every single time.

Else the disk cache will make your results useless.

 

BTW: I don't think that the decompressor is wimlibs problem here.

I just made a apply test with uncompressed install.wim.

 

Latest wimgapi: 0:51 minutes

Current wimlib:  1:46 minutes

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.