Atari800XL

JFX, could you please elaborate a little on "DisablePagefile"? Is it recommended to turn it off? In which situation could it be a good thing/ or a bad thing to turn it off? Thanks...

Thank you JFX for this new Sinterklaas gift (I know you don't understand, It's a Dutch thing...) I was just doing some testing with Windows 8 DISM, to remove Windows 8 apps from the install.wim. eg. like this: dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingFinance_1.2.0.135_x86__8wekyb3d8bbwe OK, that doesn't directly have anything to do with WinNTSetup, but it *IS* a very big coincidence that I was just checking out this forum, to see that you have more stuff for me to try out (new commandline options, YES!!, I will try out all new ones: DisableSystemRestore, DisableSFC, DisableHibernate, DisablePagefile). Lucky thing is that I timed my latest install, so I will time it again with these new switches, I'm looking forward to finding out how much time/ space it saves. I have absolutely no need for SystemRestore and SFC, I always use TrueImage, or WinNTsetup with my own PostInstall system for my programs. UltraClean, and also very fast!!! Thanks again!!! (PS, if you use the DISM commands below, you are greeted with extactly 3 (!!!) Metro icons upon a clean install!! "Desktop", "Internet Explorer" and "Store"). dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingFinance_1.2.0.135_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingMaps_1.2.0.136_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingNews_1.2.0.135_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingSports_1.2.0.135_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingTravel_1.2.0.145_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.BingWeather_1.2.0.135_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.Bing_1.2.0.137_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.Camera_6.2.8514.0_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:microsoft.microsoftskydrive_16.4.4204.712_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.Reader_6.2.8516.0_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:microsoft.windowscommunicationsapps_16.4.4206.722_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:microsoft.windowsphotos_16.4.4204.712_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.XboxLIVEGames_1.0.927.0_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.ZuneMusic_1.0.927.0_x86__8wekyb3d8bbwe dism /image:d:\mount /Remove-ProvisionedAppxPackage /PackageName:Microsoft.ZuneVideo_1.0.927.0_x86__8wekyb3d8bbwe

nLited sources can be tricky for "3rd party" utilities, still I have found WinNTSetup not very "harsh" here, most of my XP installs work (even nLited). I also love Rufus, but it also cannot fully support every "crazy" nlite thing you throw at it. My experience is: If you only use some basic nLite features, both programs work very well.

I just made a new ISO with 2 images combined into one .wim: (1) Windows 8 Pro WMC (for use with a [free] Microsoft Upgrade key) and (2) Windows 8 Enterprise (for use with KMS activation). And of course, just today JFX is releasing a wonderful new update to WinNTSetup, so this gave me the perfect chance to test everything in one go. My results: - The -nohiberboot and -win8noanimation commandline options work perfectly. So this means for both Pro and Enterprise, the childish animation is gone. THANKS!!! (My previous solution only seemed to work for Enterprise). - One question: When using the commandline options mentioned, shouldn't the checkboxes in "Tweaks" be selected? (is there a checkbox for Hiberboot?, can't remember). - Nohiberboot means in multiboot systems, there's no annoying checkdisk problems. I used to set this in Postinstall, but having the option right here in WinNTSetup means we're safe right from the start of Setup. This is also a wonderful addition. THANKS!!!! I'm also very proud of my 2-in-1 iso, but I'm sure for all you pro's here, that's just a piece of cake. It turned out I only needed 1 simple (though lengthy) DISM command. Oh well, I just think it's a lot of fun to learn new stuff like this. JFX, you're the best!

ISO files can be passed on any OS? Or only W8?Great additions!!!!

Yep, sorry about that, sometimes I get a bit excited about this stuff... OK, so you noticed the InstallAnimation glitch as well. I haven't looked into that much recently, but if you say you already have a solution for it, that would be great. Do you agree that the tweak works on W8Enterprise, and not on Pro? I haven't tested enough to be sure about that, though... Thanks!!

I know adding more commandline options can't go on forever, but it would be great if the "No Windows 8 animation during setup" could also be done. Something like -win8noanimation I tested it in autounattend.xml (I just added it manually, without adk or something), and it doesn't always work (looks like it works in Enterprise, but not in Pro). It's probably my own fault, but I don't have all the knowledge to figure it out. So maybe you can consider it, but if not, no problem... As I said before, I always use WinNTSetup with commandline options, so I can call it from WinPE_SE with a (autohotkey) hotkey (ctrl-sh-x=xp, ctrl-sh-7=windows 7, ctrl-sh-8=windows 8], then all I have to do to start the setup is press Enter twice. (of course another script is setting up the mounted isos etc). It's just such a wonderful tool!!!!! [EDIT: Removed the Offtopic W8Pro bit]

Well, if I do a W8 install, and choose "Shut down" by accident, I'm *always* in trouble. With "Reboot" I'm usually OK. Sometimes though, I don't remember exactly which one I chose... GrubInstgui also gives me a hard time when I chose "Shutdown" (invalid partition table). So once again, it would be great to have it turned off right from the start. Whichever commandline you choose is OK by me!! I'm spoiled enough already!!!

Yes, I can confirm it's Hiberboot. I also turn it off in my PostInstall system. That still leaves me with the "dangerous" first reboot, I just have to remember to choose "Reboot" after Windows 8 is done installing (not "Turn Off", that makes XP and Windows 7 go into "checkdisk"). Click-click, I always use a similar setup (XP, W7, W8) to yours, but I use 1 HD for it. Nice to see you actually use 2 different HD's (so it gives me the opportunity to install another 3 OS's on the second HD!!) And JFX, great to see you plan a "turn off hiberboot" in WinNTSetup! That will even get rid of the "dangerous" first reboot/ turn off after first install! You just always amaze me with new stuff like this.... Oh, and it would be great to have a commandline option for turning off hiberboot please!!!!!

JFX, thanks for the language.ini, this just shows once more how professional your program is [the fact that we can easily translate it, I mean]! I found a few spelling errors in the file, is it OK if I post them here? 004 contain -> contains, 007 contain -> contains, 007 inculde -> include 104 installationsdrive -> installationdrive 169 Dou -> do 217 unsinged -> unsigned 1021 an first -> at first, deaktivated -> deactivated 1028 BallonTips -> Balloontips 2031 completly -> completely 3030 avalibe -> available 3035 Finshed -> Finished 3040 occured -> occurred 3045 Faild -> Failed Maybe you can change them in the original files? Please don't think that this is criticism, hey, I'm not a native English speaker myself, but I'm sure you're too busy yourself to take notice of these little "slips of the pen".

I tested the new XP "file copy engine" on my old HP nc6320 (5400rpm HD, so extra speed is welcomed!): "Old version": File copy takes 108s (16s for driver copy etc), so XP source file copy: 92s New version: XP source file copy: 63s!! That's a 29 second improvement, or 30+ % !!!!! Very nice, never expected that you could squeeze a little more performance out of it. Great that you don't forget about XP just yet!

Thanks JFX!!! Nice going on the Windows 8 animation tweak Could you please elaborate a little on the new XP file copy engine? Is it really much faster? I'm already looking forward to more testing!!

Was the "driver-trailing-backslash" also fixed in 2.3.0.2? (No hurry.....)

Part of the log (note the *two* empty lines) Start applying WIM Applying WIM finished successfully Applying took: 03:43 Integrate Drivers using DISM from: L:\ using user defined unattend.xml: q:\winntsetup\autounattend_w8.xml loading offline registry: C:\Windows\System32\configIt's a Windows 7 driver, don't know if that's of any influence. But as I said, it works perfectly as a "manual" install. Weird...? [EDIT: Okay, I read *your* edit about the trailing backslash]

Thanks, there's a line in the log reading: "Integrate drivers using DISM from L:\" So then I guess it must have something to do with the fact that Windows 8 uses the standard "Windows driver" for my board (1024*768max with the standard driver) which it finds by default, instead of the better driver I added with higher resolutions. I think I must force Windows 8 somehow to use the new driver instead of the standard one. Something new for me to learn once again...

OK, one last test I squeezed in before the weekend's over: I used WinNTSetup to install Windows 8 to a system that needs an "external" driver (display). I already tested the driver before "by hand" on this system, but I wanted to test if WinNTSetup could add it at setup time (like I used countless times before with XP and W7). I never had to use an extra driver for Windows 8 up to now. So I mounted the drivers.iso as drive "L:", started WinNTSetup (from WinPESE), checked the "drivers" box and selected drive "L:" After two tests, the drivers is not installed. After the W8 setup completes, I install the driver "by hand" (from the same ISO) without problems. My questions: (1) Is adding drivers for W8 the same as with XP? ie. copying the drivers to c:\DRV? If so, I can see right before the reset that there's no c:\DRV. (2) Is it a bug?

OK, the test worked. For anybody interested: Add this part to your autounattend.xml to get rid of the animation at the end of setup: [i believe animations like this have no place in an UNATTENDED setup!! Who's there to watch it then, anyway? ] <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1 </Order> <Path>reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v EnableFirstLogonAnimation /d 0 /t REG_DWORD /f </Path> </RunSynchronousCommand> </RunSynchronous> </component> <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Order>1 </Order> <Path>reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v EnableFirstLogonAnimation /d 0 /t REG_DWORD /f </Path> </RunSynchronousCommand> </RunSynchronous> </component> </settings>

Thanks everybody for your help with the "Black Magic USB Ports". I now accept that (older?) boards can be completely unpredictable when it comes to hi-speed USB boots. For these cases, I'll keep a CDR handy... At least now I know I'm not the only one with this problem, and my house is not haunted. Now off to my next test: a little addition to Windows 8 autounattend.xml, to prevent the stupid animation at the end of setup. If it works I'll let you know.

@Lancelot_Real: Thanks! Of course it will help (if not in one way, then in another!) I guess you guys have said all there is to say about this (slightly off-topic) matter, thanks! (and thanks to JFX for letting us go a little OT). All the alternatives you mentioned will come in handy one day, but the original "strangeness" of the problem still stands: **WHY** would it boot in one case, but not in the other, with the same stick, on the same PC, etc. Something like black magic, powercrumbles, etc.? [EDIT: I *did* make a test-CDRW of my WinPESE.iso, which *did* boot in 100% of the cases on that particular PC. But in the meantime, the USB port hasn't given me any more problems -- which is also strange as the problem seems unreproducable now....]

Thanks Wimb, I know what you mean. But I tried different sticks on this system on that "fatefull day", all of which NEVER had problems before (used on dozens of systems). That's why I thought about a dirty or corroded connector (now if that's the case, a USB HD would also have problems, no?) Also, a 2,5" drive still doesn't fit in my wallet... But from your answer I conclude that you *did* see some weird problems like these before? Thanks again for your reply!!

I check this page often for updates, and to be honest I don't really understand why not more (much more!) people write here to thank you for this wonderful software. I'm sure there must be other ways that people thank you? Fresh flowers must be delivered to your door every day? But seeing as it is relatively quiet around here, I was wondering if I could ask you USB-boot pro's (including Wimb) a little question that might be a little off-topic from WinNTSetup: Last week I received a few PC's from about 2008. One was a Core2-E4500. My first step was to boot them with my WinPE_SE USB, because I wanted to use PE with WinNTSetup from this same USB to partiton/ format/ reinstall W7 and W8 (a grub multiboot setup I use often, sometimes also with XP). But booting from USB gave me some very weird problems that I never really experienced before: The USB-boot was TOTALLY unreliable: sometimes it worked, other times it didn't. Sometimes it booted in USB-low-speed (1.1), other times fullspeed, but it was stuck at the very last stage of booting. This happened with different USB sticks. Now for the last couple of days things seem to go OK, but I really don't understand what was going on then. Now these PC's came from a school, and I was wondering if maybe this could have something to do with dust or other dirt (corrosion even?) collecting in the USB ports? There's no visible evidence of this however... And I used both the front *and* back ports!?? The system has been running perfectly for a coupe of days now, no USB or memory, or whatever problems anymore. Isn't this REALLY strange? Sorry again for asking this slightly unrelated question in here, but I figured that if *anybody* would know about stuff like this, it would be you guys. Have you ever experienced something like this before?

Thanks JFX, I use WinNTSetup often (several times today), and as you know by now, I really love it!

Thanks!! WinNTSetup=Perfect! [bTW: Nice touch to only diplay the "bits" when there's actually two different types. No need to "clutter" the list when they're all the same... Hadn't even thought about that. Shows us who's the genious....]

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!

JFX, I really don't know how to thank you anymore!!!! 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!!!