• 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 / 3.8.7 Beta 3

1,519 posts in this topic

Hi

I decided to test this by booting to a vanilla WinPE v3 ISO (ver 6.1.7077) from a USB flash drive and the trying to use R-Click to mount an XP ISO - but nothing seems to happen after I select the ISO from the file dialogue window and click Open.

I also tried running imdiskinst.exe and got a 'can't start because crtdll.dll is missing' message.

Is WinPE v3 not supported?

P.S. When installing Win 7 to VHD you say

- requires Windows 7 as OS and Windows 7 Ultimate, Enterprise or Server 2008 R2 as Source

Why not 7 HP or Pro? What is the restriction?

Edited by steve6375
0

Share this post


Link to post
Share on other sites

I've been using winntsetup for a while with great results.

New problem when installing Win7 or Vista.

Mount Installation drive as,option is unavailable.

Tried v2.1 with same results.I'm puzzled never had this happen before.

Tried from inside xp win7 and pe with same results.

This option is not supported for Vista installations, but for Windows 7 and later it should be avalible.

I'll take a look at it.

Hi

I decided to test this by booting to a vanilla WinPE v3 ISO (ver 6.1.7077) from a USB flash drive and the trying to use R-Click to mount an XP ISO - but nothing seems to happen after I select the ISO from the file dialogue window and click Open.

I also tried running imdiskinst.exe and got a 'can't start because crtdll.dll is missing' message.

Is WinPE v3 not supported?

Yes all versions of WinPE are supported.

This seem to be a problem of the imdisk installer. You could add crtdll.dll from an x86 Windows 7 in the same folder as imdiskinst.exe or unpack it with 7zip and run install.cmd manually.

Seems Olaf has ruined the silent install anyway with that msgbox pop up.

I'll make 2 new install packages to fix this and also add support for vanilla x64 Winpe.

P.S. When installing Win 7 to VHD you say

- requires Windows 7 as OS and Windows 7 Ultimate, Enterprise or Server 2008 R2 as Source

Why not 7 HP or Pro? What is the restriction?

All Windows 7 versions would support VHD booting, but it's a license restriction.

During logon there is a check made for Kernel-NativeVHDBoot, think through SLGetWindowsInformationDWORD.

You would get an error and stuck on logon screen, if you use a lower edition than Ultimate.

I proplery could fix that :angel , but some people would have a problem with this. :whistle:

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites

Thank you very much for the reply.

It was Vista (of course) works fine for Win7. Any options to manualy set as C.

If it's not an easy answer,don't put yourself out (Vista's a pain).

Love the new v2.2. I'm stuck on XP and it works perfect. I use both nLite and RVM_Integrator

to tweak my installations. WinNTSetup The best hands down!

Thanks again.

0

Share this post


Link to post
Share on other sites

Sadly Vista is very limited in offline servicing.

The only way to change the drive letter of vista installations would be to use the normal setup.exe.

And creating a new sysprep image.

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites

I'll make 2 new install packages to fix this and also add support for vanilla x64 Winpe.

A bit late, but here are 2 new imdisk installer that works (silently) in all WinPE.

Also linking to new Alpha version, as there won't be any new version in the near future ...

This version has a lot of rewritten code and was not tested fully.

If someone noticed bugs or even mange to crash it, please report.

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites

Just did a test of version 2.3a (sorry, didn't use your Imdisk installers, I always use its "daughter", osfmount [silently, of course]).

Booted with WinPE_SE, used my Autohotkey scripts (ctrl-sh-7, ctrl-sh-8, ctrl-sh-x) to install W7, W8, XP to 3 seperate primary partitions:

WinNTSetup2_x86.exe -nt6 -source:k:\sources\install.wim -syspart:c: -unattend:"autounattend_w7.xml" -savedriveletters -sysletter:c -reboot -disableuac

WinNTSetup2_x86.exe -nt6 -source:k:\sources\install.wim -syspart:c: -unattend:"autounattend_w8.xml" -savedriveletters -sysletter:c -reboot -disableuac

WinNTSetup2_x86.exe -nt5 -source:k: -syspart:c: -unattend:winnt.sif -savedriveletters -drivers:"L:\" -reboot

Everything fully unattended, it all works so perfectly it's almost not funny anymore!!! :}

.... I'm kidding, of course: WinPE_SE and WinNTSetup are absolutely amazing in their power and possibilities!!! :w00t:

Thank you soooo much for all your work! :thumbup

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

Is it necessary to format the target partition for a clean Win7 install with WinNTSetup?

No, it's not mandatory. install will overwrite files and abort if there would be a problem.

But yes there will be files remaining from old Windows installation.

With removing an old installation without formating, i see 2 problems:

1. NTFS security settings

- one would need to take ownership & grant access

or using a tool like xdel

2. Junctions and Symlink (and this is the thing that scares me ! :ph34r: )

- junctions and symlinks in Win7 are created with full path.

think you have an offline win7 that has C: as normal drive letter and is now under your current running windows mounted as D:

It's junctions and symlink will still point to C:, but that could be the current running windows :ph34r:

Even Mircosofts own tools like robocopy don't handle symlinks right.

It might happen that deleting an offline windows switch the drive and start deleting files/folder one the current system drive !

Fyi JFX

After asking the author to add an enhancement to XDEL, he has updated it with a new parameter: --one-volume-only You no longer need to be scared. :no: With this parm, only files on the target drive are deleted. The updated version is not on his website because he is in the process of moving files to another site, Here's the Link.

0

Share this post


Link to post
Share on other sites

Everything fully unattended, it all works so perfectly it's almost not funny anymore!!! :}

.... I'm kidding, of course: WinPE_SE and WinNTSetup are absolutely amazing in their power and possibilities!!! :w00t:

Ha, ha I know what you mean. Yeah sometimes a project make a lot of fun while doing it, but someday one noticed there nothing more to improve.

Thanks for the feedback :)

Fyi JFX

After asking the author to add an enhancement to XDEL, he has updated it with a new parameter: --one-volume-only You no longer need to be scared. :no: With this parm, only files on the target drive are deleted. The updated version is not on his website because he is in the process of moving files to another site, Here's the Link.

That's great news.

Finally a good way to remove a windows installation without formating and XDEL is also pretty fast :)

Thanks

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites

Yes, XDEL is fast, and also very dangerous, as I found out...

So I want to give an extra WARNING for anyone who might want to try it out:

DON'T even think about trying to get some help or explanation by carelessly trying out these commands:

XDEL (if you might expect some helpmessage)

or

XDEL /? (if you might expect a list of command-line options)

The first commands wipes out your current drive, the second deletes all 1-character filenames (like I use for my most important files: My TrueCrypt volumes, which have single-letter names that correspond with the driveletters they're mounted under).

Luckily, I always have enough backups, but I must say this is the most dangerous tool I have ever come across!!! :blink:

I fully realise powertools like this one should not be used by noobs, but even then, I was surprised by this little wolf in sheep's clothing!!!! :o

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

Luckily, I always have enough backups, but I must say this is the most dangerous tool I have ever come across!!! :blink:

I fully realise powertools like this one should not be used by noobs, but even then, I was surprised by this little wolf in sheep's clothing!!!! :o

JFYI ;):

http://www.marriedtothesea.com/041808/this-is-what-i-get.gif

jaclaz

0

Share this post


Link to post
Share on other sites

If you mean I shouldn't have touched XDEL in the first place, you're probably right.

Still, I'm glad I tried it, because I'm sure I can use it in the future. I just never came across a tool that was so powerful (dangerous) when starting it without any parameters, or with the "/?" parameter.

Again, I'm only blaming myself for any data loss that could have occurred (*), but looking back, I still wonder why there isn't a list of command line options.

(*) On my test PC, I sometimes use "destuctive" tools on purpose, just to see what happens. That's why it's a test machine.

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

If you mean I shouldn't have touched XDEL in the first place, you're probably right.

Naaah, not at all :), just showing you another "classical" destructive tool.

(*) On my test PC, I sometimes use "destuctive" tools on purpose, just to see what happens. That's why it's a test machine.

Yep :thumbup:

Life is "trying things to see if they work".

jaclaz

0

Share this post


Link to post
Share on other sites

Good you had backups.

For me XDEL works as assumed without parameter it shows the help screen.

Using /? is also logical, but your right it's unexpected.

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites
For me XDEL works as assumed without parameter it shows the help screen.
If I understand you correctly:

When you type:

XDEL

(without parameters) you get a help screen? Hmmmm, maybe I should try again, but I'm almost positive it started deleting immediately. Maybe I tested a different version? I downloaded the version from the link given by "click-click"...

0

Share this post


Link to post
Share on other sites

Yes the version form click-click's link

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites

Thanks for that, JFX.

So it turns out that just typing "XDEL" is not supposed to start deleting right away. Good... As I said before, that would be really strange...

Now I'm sure about the first "XDEL /?" I typed (which deleted the 1-letter files), but now I'm starting to wonder what the second command was. I think it was "XDEL" without parameters, but I'm not 100% sure. It certainly was *not* "XDEL E:". Still, it wiped out my E: drive. It could have been "XDEL /" (single slash), which would have been produced by "cursor up" and a backspace. In that case, it was a stupid mistake and a freakish coincidence.

Thanks again!!!!

0

Share this post


Link to post
Share on other sites

Just did a quick test with the new Windows 8 release preview. Got a "0x000007f" error about 5% into "applying image" ("winimage.exe"). After that, WinNTSetup reported "failed to applying the Systemimage! Error -1073741818".

0

Share this post


Link to post
Share on other sites

Thanks for the report. I have not loaded the release preview.

Either the install.wim is corrupted or the MS guys changed their WIM format again.

maybe alpha 4 can handle it: WinNTSetup2.3 alpha4

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites

I believe the .wim is not corrupted, because the setup completed OK when I did my first test from a "normal" USB stick (created by Rufus).

But I'll wait for others to test the setup of Windows 8 release preview, because my reputation in the last weeks is one of stupid mistakes...

[bTW: Thanks for Alpha 4! anything else you changed in that version?]

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

I tried the release preview, works alright for me.

Alpha 4 has no other changes.

What version had this error the 2.2 or the 2.3 alpha ?

0

Share this post


Link to post
Share on other sites

I used WinNTSetup 2.3 Alpha 4.

"winimage.exe - Application Error

The instruction at 0x7607B515 referenced memory at 0x73254228. The required data was not placed into memory because of an I/O error status of 0xc000007f"

Right after this error, I tested the previous W8 version (CP), it installs without problems. Very strange.

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

Indeed strange.

"I/O error status of 0xc000007f" sounds more that something on your system is broken (RAM, DISK or even some system file)

Edited by JFX
0

Share this post


Link to post
Share on other sites

I guess I'll have to do some "manual" testing with imagex/dism? But I'm not very experienced with these tools (that's why I like WinNTSetup so much!!).

Maybe somebody can give me some hints how I can put the image on the C: drive directly from the install.wim?

JFX, you suspected RAM, Disk or system file:

- RAM: The testsystem has only 512mb. Never had any memory errors, but of course the low amount of RAM could be a probelem in itself. However, I've never had any RAM problems on this system with XP, W7 or W8CP!

- System: I'm using WinPE_SE for these tests. I *did* have some memory-related problems with that once, don't remember exactly what they were. So low amount of RAM could very well be the problem (still, why no probelems with W8CP then?)

0

Share this post


Link to post
Share on other sites

So low amount of RAM could very well be the problem (still, why no probelems with W8CP then?)

I could reproduce it in a VM with 256 MB RAM :yes:

Well Microsoft :ph34r: is to blame: wimgapi causes an appcrash instead of a nice and clear error message.

Interesting: To apply the new release preview wim's much more RAM is required (~80MB vs. 49MB Consumer Preview)

You maybe could solve your problem with a pagefile.

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites

JFX: Thanks for solving the problem!!

Just before reading your answer, I ran a test from "plain old" XP (no PE, but HD install), that went OK. For a moment, I thought the problem was the Wimindex (there's two images in the new Install.wim: "Windows 8" and "Windows 8 Release Preview"). But as we know now, that wasn't the problem. XP had no RAM problems because it can use a pagefile, as you also said.

Having a pagefile in WinPE_SE is not a very "clean" solution, now is it? Isn't the "purpose" (or at least: beauty) of a PE system that it runs independent of the harddisk?

So then the only solution would be adding more RAM, I guess. Or the conclusion that the combo WinPE_SE + WinNTSetup + Windows 8 Release Preview can't be done with 512mb. Do you think it would be practical to add a memory check in WinNTSetup? (If only to avoid this nasty appcrash? You don't want your app to look bad, when Microsoft is to blame?)

OK, one last thing: Is there no way to use the "Consumer Preview" apply method (~49mb) with the new "Release Preview"? (Guess not...)

Thanks!!!

:thumbup

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.