JFX

WinNTSetup v3.8.7

1,543 posts in this topic

So here is what I do. Within XP, I create a virtual HDD image, say XP.IMG (could be VHD as it's nearly the same thing). Mount it as a virtual drive with ImDisk.

Then I configure WinNTSetup to use the virtual drive as a target disk, and to inject the WinVBlock driver ("Add Driver" checkbox). So far so good.

Next, first reboot. Said XP.IMG is now mounted as virtual HDD by Grub4Dos. Chainload NTLDR on the physical HDD to start setup.

TXT-mode setup goes well....till the phase "Windows is Starting". At this point it greets me with something like "the setup temporary files cannot be found and cannot continue".

Any clue what the problem might be ?

Seems the driver integration don't work for a virtual driver like winvblock, it will be skipped and Txtsetup will get a problem.

But if you boot this img with Grub4Dos, why not use a virtual F6 floppy with winvblock files?

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites

But if you boot this img with Grub4Dos, why not use a virtual F6 floppy with winvblock files?

Yes of course that's always possible and it's been reported to work. I didn't try it because I thought the driver integration would do the job....

Seems the driver integration don't work for a virtual driver like winvblock, it will be skipped and Txtsetup will get a problem.

Yes I've also come to that conclusion. I'm not an expert, and perhaps I'm not looking where I should, but when I look in $WIN_NT$.~BT on the boot drive, there is no sign of winvblk32.sys although I would expect to find it there....

Is there a fundamental problem to make the driver integration work with WinVBlock ? or is this some sort of bug / incompatibility ? At least can WinVBlock be integrated manually (if yes, how) ?

Would the driver integration work with e.g. SATA drivers for physical hardware ?

Edited by Doodoo
0

Share this post


Link to post
Share on other sites

Is there a fundamental problem to make the driver integration work with WinVBlock ? or is this some sort of bug / incompatibility ? At least can WinVBlock be integrated manually (if yes, how) ?

Would the driver integration work with e.g. SATA drivers for physical hardware ?

MSSTMake can integrate Massstorage drivers, for physically existing devices and so far is the best app to do this.

It just don't recognize drivers like WinVBlock.

IntegrateDrv surely is interesting, but has a few week points:

- it's only thought to integrate 1 single driver, no recrusiv adding of drivers

- no silent automation, it ask my to choose 1 of 23 "drivers" for my Intel Storage

- accepts only one target, but $WIN_NT$.~BT and $WIN_NT$.~LS can be on different partitions

0

Share this post


Link to post
Share on other sites

MSSTMake can integrate Massstorage drivers, for physically existing devices and so far is the best app to do this.

It just don't recognize drivers like WinVBlock.

Any idea what it would it take to work around the problem (if possible at all) ? Would a tweaked INF file solve the issue ? Or is it just wishful thinking ?

IntegrateDrv surely is interesting, but has a few week points:

Yes indeed it's not perfect... but the source code is available ! As usual it's a question of time more than a question of skill... but I suppose it could easily be integrated in WinNTSetup and improved at the same time :-)

- accepts only one target, but $WIN_NT$.~BT and $WIN_NT$.~LS can be on different partitions

Yes I've experienced it myself... It just doesn't like that....

Perhaps the simplest solution is to keep MSSTMake as the default tool, and only use IntegrateDrv for problematic drivers such as WinVBlock ? (anyone tried FiraDisk ?)

0

Share this post


Link to post
Share on other sites

Any idea what it would it take to work around the problem (if possible at all) ? Would a tweaked INF file solve the issue ? Or is it just wishful thinking ?

Can't say, as I not sure how MSSTMake works exactly, WinNTSetup only merges the information into the windows source.

Perhaps the simplest solution is to keep MSSTMake as the default tool, and only use IntegrateDrv for problematic drivers such as WinVBlock ? (anyone tried FiraDisk ?)

How to decide what is a problematic driver? Just guessing that a driver rejected by MSSTMake can be integrated with force (as IntegrateDrv does) is OK, could cause other problems.

Yes indeed it's not perfect... but the source code is available ! As usual it's a question of time more than a question of skill... but I suppose it could easily be integrated in WinNTSetup and improved at the same time :-)

Well, if someone is volunteer to create an improved and small app, I would like to integrated it, but personally have no free time at all.

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites

From Google translator...

Sorry maybe offtop.

It is impossible to establish Windows 7 SP1 Ultimate. "Error:2 failed to applying the Systemimage!" In what a mistake? Used different images install.wim. Program version 2.2

Thanks

0

Share this post


Link to post
Share on other sites

Hi Sampy82,

Error: 2 usually means that an error occurred while read or write from disk.

Maybe there is a problem with your harddisk or an antivirus software blocking the apply process

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites

Hi JFX,

You are probably right that matter in a disk, but I checked on liveCD Windows. The antivirus isn't established. Everything is developed on version 2.3 beta 4, but setup not started :(

I will try to test on other disk

:yes:

With other disk Error:2 :(

Edited by Scampy82
0

Share this post


Link to post
Share on other sites

OK, so I'm doing a lot of Windows 8 testing, and WinNTSetup is proving once again to be a WONDERFUL tool!!!

Just two things I'd like to bring up:

(1) I guess WinNTSetup is now officially "Windows 8 ready"? So in the upper right corner (on the tab) you can add a "8" so it reads "Vista/7/2008/8"?

(2) I am testing with different ISO's, one is an Enterprise version (MSDN) with only one image in the Install.wim. The other is a Core/Pro version, so I had to add "wimindex:2" to the command line. But I can't get this to work. Now, from past experience, this must be something I'm doing wrong, but still I wanted to ask you if you're aware of problems with the -wimindex commandline switch?

Thanks! I love WinNTSetup!!!!!

:thumbup

EDIT: Did a little more testing with a Win8 All-In-One DVD (usually not my favorite, but this one was interesting for me, because it also has NET35 integrated, which I like. So until I figure out how to do that myself, I'll keep this one). It has these "images" in the wim:

Index : 1 Name : Windows 8

Description : Select to install Windows 8 (32-bits).

Index : 2 Name : Windows 8 Pro

Description : Select to install Windows 8 Pro (32-bits).

Index : 3 Name : Windows 8 Enterprise

Description : Select to install Windows 8 Enterprise (32-bits).

Index : 4 Name : Windows 8

Description : Select to install Windows 8 (64-bits).

Index : 5 Name : Windows 8 Pro

Description : Select to install Windows 8 Pro (64-bits).

Index : 6 Name : Windows 8 Enterprise

Description : Select to install Windows 8 Enterprise (64-bits).

Two things happen when I run WinNTSetup and use the /wimindex: commandline option:

(1) The description of the selected version under "Select location of install.wim file" is not automatically adjusted (it only corects itself after I manually pick the same or a different image in the dropdown box)

(2) /wimindex:1 doesn't work, it selects the 3rd image!? (Enterprise 32bit)

All the others (wimindex:2 through 6) work (except for the description)

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

(1) I guess WinNTSetup is now officially "Windows 8 ready"? So in the upper right corner (on the tab) you can add a "8" so it reads "Vista/7/2008/8"?

Yes, it's time to add "8" and "2012" to the tab, as fully supported OS. :yes:

(2) I am testing with different ISO's, one is an Enterprise version (MSDN) with only one image in the Install.wim. The other is a Core/Pro version, so I had to add "wimindex:2" to the command line. But I can't get this to work. Now, from past experience, this must be something I'm doing wrong, but still I wanted to ask you if you're aware of problems with the -wimindex commandline switch?

Oh, could reproduce it. Must have happed while I changed the WIM stuff. Combo box starts with 0, but wim index start with 1.

Seems I put that vice versa again :unsure:

Booth should be fixed now in RC1.

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites
it's time to add "8" and "2012" to the tab, as fully supported OS. :yes:
Now with :w00t:25% :w00t: more OS Support!
Booth should be fixed now in RC1.

The correct index is now used. THANKS!!!

....but the description of the index (under "Select location of the install.wim file") still doesn't correspond to the selected image (right after launching with the /wimindex: switch)!

[i mentioned it in my edited post above]

I guess the last one's only cosmetic, so once again: Thanks!

:thumbup

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

Okay fixed now, no version changed this time.

cheers.gif

Edited by JFX
0

Share this post


Link to post
Share on other sites

JFX, I really don't know how to thank you anymore!!!! :thumbup

Now I can use the Windows AIO ISO to select from 6 editions, with just one keystroke (in WinPE_SE).

Thanks to your latest adjustments, the correct image from the ISO is selected (and properly described)!

AMAZING!!! All OS's, Apps, backups etc. etc. on just **one** bootable USB. Pure magic, thanks to JFX!!!

:D

Edited by Atari800XL
0

Share this post


Link to post
Share on other sites

JFX:

I know I'm pushing my luck here, but as you are already on "Release Candidates", I have 1 more cosmetic thing to ask:

As I was using the Windows AIO ISO I mentioned above, this is what's displayed in the "Edition" dropdown"

Windows 8

Windows 8 Pro

Windows 8 Enterprise

Windows 8

Windows 8 Pro

Windows 8 Enterprise

The first three are 32bit, the last three are 64bit. The description on top of the WinNTSetup screen then shows you more details. But would it be possible to add the "bitness" also *inside* the dropdown? This would be very clear, and avoid selecting the wrong version. Something like the standard Windows setup list? (You know, where it says "Operating System | Architecture | Date modified" - even though I don't think we'll need that *date* column). Maybe only 32-bit or 64-bit, to prevent the "double/ identical" names like the list above?

Thanks!

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