Jump to content

Recommended Posts


Posted

Thanks Steve,

Anyone know if for a WinToGo USB drive, should I have used “Mount Installation drive as” set to ‘*’ ??

Or what does preassignment actually do?

Thanks

Posted

If you set “Mount Installation drive as” to '*' than the system drive letter will not change.

A stock Windows 7 will result in D:, and Windows 8 and newer usually in C:

 

The preassignment option will save the drive letters of all fixed volumes.

So for WinToGo this option is no use.

Posted (edited)

If you set “Mount Installation drive as” to '*' than the system drive letter will not change.

A stock Windows 7 will result in D:, and Windows 8 and newer usually in C:

 

The preassignment option will save the drive letters of all fixed volumes.

So for WinToGo this option is no use.

Thanks JFX,

Anyone any ideas on how to change the WTG drive letter -- only visible when booted (active) and within a VHD within a imgPTN??

Want to try to change from W to *.

Very Strange:  Have a secondary data HDD with nothing but GPT data partitions, and WTG -- as W -- wants to take all those GPT partitions and letter them first (D, E, F. etc..), which changes most other letters (and shortcuts / cross references).

Edited by RUSerious
Posted (edited)

Anyone any ideas on how to change the WTG drive letter -- only visible when booted (active) and within a VHD within a imgPTN??

Want to try to change from W to *.

Well, I tried to do this with Regedit, but mucked something up -- eternal preparing windows dots...

So, for my start-over,

Should it be ok to set “Mount Installation drive as” to '*' for a Windows To Go drive?

Or would this also give the eternal dots circle?

Thanks

Edited by RUSerious
Posted (edited)

Why you first wanted W: and now not?

You can used this option as you want, it has no relation to WTG.

 

EDIT: shuffling partition letters using WTG is normal,

your WTG windows doesn't know how the offline windows has define drive letters for partitions.

Edited by JFX
Posted (edited)

Why you first wanted W: and now not?

You can used this option as you want, it has no relation to WTG.

The reason for setting it at W: was to prevent partition  letter shuffling.

But at W: did NOT prevent partition  letter shuffling.

So thought I would try * for WTG and see if that would allow WTG to NOT shuffle partition letters.

edit: Would WTG still boot as C: even if I set “Mount Installation drive as” to '*' ??

Edited by RUSerious
Posted

On this page for Windows To Go: Feature Overview
http://technet.microsoft.com/en-us/library/hh831833.aspx
Under differences it states:
“Internal disks are offline. To ensure data isn’t accidentally disclosed, internal hard disks on the host computer are offline by default when booted into a Windows To Go workspace. Similarly if a Windows To Go drive is inserted into a running system, the Windows To Go drive will not be listed in Windows Explorer.”
Which made me think maybe it should be set as “ * “ for “Mount Installation drive as” for WTG to work as stated.

Thanks
 

Posted

Yes, in the original WTG, the drives are offline.

But I decided to not do that, cause properly the half of the users would ask how to fix that.

Posted

Sorry, don't want to bother you, but just wanted to throw this in:

- Latest WinNTSetup doesn't start in XP, is that "by design"? Doesn't bother me much, but saw it by accident.

- Winntsetup.com is down for a few days?

Posted (edited)

It works here on WinXP, maybe you added a newer wimgapi.dll to the tools folder?

 

Website is currently a bit slow but works.

Edited by JFX
Posted

Thanks JFX, looks like a clean download works fine on XP, thanks for clarifying!

 

Winntsetup.com still doesn't work here, though... Not a big problem, but I like to check it for the changelog from time to time...

Posted (edited)

Changelog is also in the zip file as comment, if you use WinRAR for zip files.

Edited by JFX
Posted (edited)

Thanks JFX, I was aware of the changelog in the zip (nice touch), just thought you might want to know about the website being a bit "shaky"...

 

EDIT: Just installed the new W10 build 9926 (much more languages this time!), using WinNTSetup and my 8.1 unattend.xml. Still working nicely, fully unattended of course. Thanks again, JFX!

Edited by Atari800XL
  • 4 weeks later...
Posted

Hi JFX,

 

I have some problems installing winntsetup-v3.7.5 on a fresh Windows Server 2012R2 system. Every time I am choosing some options in the window followed after checking the button "tweaks" the setup procedure breaks down and I get an error message: "Universal Windows Installer funktioniert nicht mehr etc", Problemsignatur:
  Problemereignisname:    APPCRASH
  Anwendungsname:    WinNTSetup_x64.exe
  Anwendungsversion:    3.7.5.0
  Anwendungszeitstempel:    54a919f7
  Fehlermodulname:    WinNTSetup_x64.exe
  Fehlermodulversion:    3.7.5.0
  Fehlermodulzeitstempel:    54a919f7
  Ausnahmecode:    c0000005
  Ausnahmeoffset:    0000000000088fcd
  Betriebsystemversion:    6.3.9600.2.0.0.272.7
  Gebietsschema-ID:    1031
  Zusatzinformation 1:    fa92
  Zusatzinformation 2:    fa92ff279825754930874a64072a4b62
  Zusatzinformation 3:    159f
  Zusatzinformation 4:    159f02d3e552cb5e12cd94d8abb97ade

I have tried all the previous versions of winntsetup but I still get the same message. If I don't check the button "tweaks" everything is alright and I am able to produce my VHD. Could you please give me any advice how to solve the problem?

 

Kind regards

 

Holger

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...