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 v3.9.4 / 4.0 Beta 2

Recommended Posts

Really don't understand what you mean with subst not working.
1. subst.exe Y: C:\Windows /mount any directory (disk) as Y:\ /

2. Start WinNTsetup3 and exit.

3. Drive Y:\ there... but unavailable :(

4. SUBST Y: /d - don't work

5. subst.exe Y: C:\Windows - don't work.
PS: In version 3.1.0 is not included Russian localization.

Share this post


Link to post
Share on other sites

@click-click

Next version will accept relative paths to winntsetup.exe like version 2 did.

@conty9

Sorry forgot language while moving software to a new PC, but re-uploaded now.

Could reproduce your subst problem and it's really a bug.

This will take some time to fix as I'm a bit busy these days and there is different behavior

between NT5 and NT6 windows versions (as well as WinPE).

Share this post


Link to post
Share on other sites

I would also like to know about .esd files. I must admit I don't know too much about them, I only know they have higher compression and can't be edited as easily as wim files can. I plan on doing some experiments on creating an .esd from a .wim, and see how much space it will save. But if you don't support them, I will not bother with it.

After reading a topic on MDL forum about esd creation, I think there is a misunderstanding about esd files.

People started to call recovery compressed wim files now install.esd instead of install.wim. :huh:

Well adding support for such files shouldn't be a problem.

However this compression type is not thought as a replacement for maximum compression

and will have much slower applying times.

Edited by JFX

Share this post


Link to post
Share on other sites

Installed XP with 3.1.0 and noticed that the RegTweak directory in \$WIN_NT$.~LS\$OEM$\ is being populated with a bunch of directories numbered 5-22 and also with a file called RegTweals.cab. I have my own tweaks that I copy to RegTweak and I did not select anything from the tweaks menu. Previously, if no tweaks were selected, the RegTweak dir remained empty. Now I'm not sure if my reg files will be applied after copying them to RegTweak since it looks like the tweaks process has changed. Can I just delete the dirs and cab file?

The RegTweak.cmd doesn't even access these dirs.

Edited by click-click

Share this post


Link to post
Share on other sites

Seems Microsoft had the idea to call LZMS compressed wim files esd, too.

So I will add support for esd files created by dism, but not the ones downloaded by ms store :angel .

@click-click

Nothing changed, all *.reg files will be applied during setup.

Temp files in the folder are just not delete, but will be in next version.

Share this post


Link to post
Share on other sites
It is possible to use WinNTSetup v3.2 for Install of XP in VHD


0. If desired use first UFD_FORMAT.exe to make USB-Stick bootable with Grub4dos Menu and that can be used as Target Boot Drive

1. Then Use VHD_XP_Create.exe where XP Setup ISO file is NOT Selected in this case.

Select Target Drives and Grub4dos Boot Menu Checkbox and use GO

to make XP-1.vhd on NTFS System Drive and to make NT Setup Grub4dos Boot Menu on Target Boot Drive.


2. Mount XP-1.vhd as ImDisk Virtual Drive (if needed use imdiskinst.exe to install ImDisk driver)

3. Use WinNTSetup v3.2 - click on XP tab for menu - Right-click to Select XP Setup ISO file.

Select as Boot Drive and as Installation Drive the ImDisk Virtual drive of mounted XP-1.vhd

Click Setup to prepare $WIN_NT$.~BT and $WIN_NT$.~LS folders in XP VHD

4. Use menu.lst on Target Boot Drive which has following entries in Grub4dos Boot Menu

5. Take care that winvblock.ima is found next to XP-1.vhd

6. Reboot to Install XP in VHD - Start TXT-mode and then reboot 2x with Grub4dos menu Boot Windows XP





title Start - TXT-mode XP Setup on XP-1.vhd - WinVBlock driver - 2000 MB
find --set-root --ignore-floppies /XP-1.vhd
map --mem /winvblock.ima (fd1)
map --mem /winvblock.ima (fd0)
map /XP-1.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr

title Boot Windows XP from Image - XP-1.vhd - WinVBlock driver - 2000 MB
find --set-root --ignore-floppies /XP-1.vhd
map /XP-1.vhd (hd0)
map --hook
root (hd0,0)
chainloader /ntldr



post-132150-0-87786300-1390296990_thumb. ===> post-132150-0-80982100-1390297023_thumb.




:)

Edited by wimb

Share this post


Link to post
Share on other sites

Sounds good. So to be clear: esd files are compressed better, but take longer to apply? If that's the case, I'm not sure I would like them for normal use (I like faster apply better than smaller size, but I'm sure it could be useful for some).

Those LSMS compressed wim files are created by using "/compress:recovery" with DISM? That's how I understood it, but it really doesn't make sense... ("/compress:lsms" or something would be clearer, but that's Microsoft for ya...)

Seems Microsoft had the idea to call LZMS compressed wim files esd, too.

So I will add support for esd files created by dism, but not the ones downloaded by ms store :angel .

Share this post


Link to post
Share on other sites

Yes, it will be useful if one still burn a setup DVD, with it's limited space.

I mostly use fast compression, only for winpe maximum compression seems useful.

Don't forgot if you not run winntsetup on XP host, you can update wimgapi.dll in the tools folders.

The 8.1 ADK api saves also a bit time while applying.

Share this post


Link to post
Share on other sites

Ok, so this took a while but should adress all problems.

WinNTSetup v3.2

- fixed problem with "subst" drives
- fixed drive label still not displayed on some systems
- new support for esd files
- command line accept relative pathes
- on windows 8.1 system32 wimgapi.dll will be preferred
- admin check now token based

- updated offreg library to latest version

Share this post


Link to post
Share on other sites
Great :thumbup

Post #1 displays Current Version: 3.1.0


For a future WinPE plugin. Is it possible to have a switch, in a future version to download the Windows 8 ADK required files at build time ?

Knowing that GetWaikTools can do the trick, but a little bigger.

Edited by ChrisR

Share this post


Link to post
Share on other sites

Ah, that evil first page, I always forgot there something.

I'll add a download command line, with the next version :)

Share this post


Link to post
Share on other sites

Okay done, you now can run it like this: "WinNTSetup_x86.exe download".

It will silently download the adk tools and close with exitcode 0 if successful.

WinNTSetup v3.2.1

- reduced ADK download size by 600KB
- new download command line option to download ADK silently
- added links to about gui
- removed bootice from tools

Share this post


Link to post
Share on other sites

xcv150,

it's no real difference to normal BIOS.

Just make sure you create a EFI system partition and select this one as boot drive.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...