WinNTSetup v2.3 small tool to Setup Windows from an(y) win32 environment.
Posted 21 September 2012 - 12:46 PM
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?
Posted 21 September 2012 - 01:12 PM
Please try small size Portable USB-harddisk instead. Is much faster and stable.
Western Digital 320GB Elements Portable 2.5"
This post has been edited by wimb: 21 September 2012 - 01:19 PM
Posted 21 September 2012 - 01:26 PM
But from your answer I conclude that you *did* see some weird problems like these before? Thanks again for your reply!!
Posted 21 September 2012 - 04:29 PM
Knowing such a power tool at hand is quite enjoyable to me,
Although I've never got chance to use myself ( using same windows since 2007 :> , and it still works very well) I will have a chance some months later to install w7 (as a 2nd os :>)
ufd boot problems differs, up to main reason bios (long story, shortly bios fails to identify ufd as disk but as floppy), and to workaround (if possible, up to bios) a set of ways exists.....
Workarounds I know:
using small sized ufd, (wimb already mentioned)
using 2 partitioned ufd,
using grub4dos mbr OR nt5x mbr OR nt6x mbr (my personal experience, ntldr5x mbr caused trouble on my old hardwares, grubdos works, but I remember I had read opposite results too )
having boot file (grldr-ntldr whatever) close to disk map (I personally copy these files first to achive this, I am not sure but there was a size limit for that, maybe on cd or also on disk...)......
check bios settings and update bios if possible.....
and of course, using usb-harddisk (this should solve
and even better of course, using usb-cd (I use my dvdw this way with a box (converter) more than five years now)
none of both good for vallet
ps: converting ufd to cd (by using ufd chip settings) does not help solving this problem, I personally tested...
ps: if there is a solution of booting ufd first as floppy than doing things on dos, maybe grbldr.exe forcing floppy to disk, I do not know
My general personal solution that works so far good is (with 4gb kingston): preparing ufd disk with bootice using grld mbr option and double partition (1 of them very small). (made a newbie tutorial for that on Gena ufd prepare besides I do not think you are newbie )
for usb1.1 case:
try your chance using different usb-slots, sometimes one of them works with 1.1. and other with 2.0 (I believe manufacturer going cheap with assuming 1.1 is for keyboard/mouse ) or maybe starts 1.1 at boot time (whatever...)
There is also plop http://www.plop.at/ that forces ufd work with 2.0 speed at boottime,
my personal choice so far is, starting plob from grub4dos and get back to grub4dos menu and boot from other stuff, still I did not have a chance to test this on a real hardware that fails that way.....
That is nearly all I know, which may help or not
Posted 21 September 2012 - 11:00 PM
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....]
This post has been edited by Atari800XL: 21 September 2012 - 11:03 PM
Posted 22 September 2012 - 03:02 AM
It often switched between USB 1.0 and 1.1 Speed, even with same USB disk.
On a cold boot, it never was able to boot from USB.
Guess most problems are related to stupid BIOS,
Lately had one machine that could not boot an XP boot sector on a 2K aligned partition.
After changing some BIOS settings it worked.
This post has been edited by JFX: 09 March 2013 - 10:19 AM
Posted 22 September 2012 - 10:31 AM
I'm just wondering, do you solved the issue with Drive letter preassignment (to remind, it works perfect, except as it also assign the S letter to System partition what make it visible and not hidden)?
Everything else works perfect, great tool.
P.S. Is it possible to add (much) more tweaks (it is lot of the available sources), as it can make it really highly customizable tool for every installation (more personal targeted tool), e.g. change users drive, public drive, system wide right click extender, etc. (so, see e.g. Win Toolkit tweak & service menu)?
Run; RunOnce, RunOnceEx and FirstLoad (Active Setup Component - it execute just once after first login load) will be nice to be added.
Posted 22 September 2012 - 10:45 AM
...and much more than those, this aging page of mine still contains valid points (FAQ #10):
For the record just recently I found an (old) EPIA 5000 motherboard that for *whatever* reasons does need USB ZIP geometry AND NOT *any* grub (grub legacy/grub4dos/grub2) (but boots with the standard 2K/XP MBR+bootsector and with the Syslinux bootsector. Though I haven't done all the possible tests, I made quite a few (and then let it aside since I managed to solve the actual issue and needed to put back the machine to work).
But usually the issue (if USB/BIOS related) is in the very first phases of boot, what you reported does sound a lot like the motherboard needing a good clean (particularly the RAM sockets and the RAM be reseated).
Posted 23 September 2012 - 11:31 AM
Well, there is no real way to detect a "system" partition. Until Vista properly nobody has hidden his active partition, so i don't think the boot partition should be hidden by winntsetup in general.
Currently it checks if the drive label is called ""system reserved" and if the partition is smaller than 1 GB. If both true it will be hidden for the new installation.
Personally, I would suggest the change the partition id with diskparts setid command.
This way, any windows will never assign a drive letter to it
@lama & komital
I don't plan to add anymore tweaks to it. It's a simple setup tool not a tuning and tweaking suite
It should be possible to get most of these things done with the "Runafter" switch.
This post has been edited by JFX: 09 March 2013 - 10:19 AM
Posted 23 September 2012 - 11:32 AM
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.
Posted 23 September 2012 - 12:12 PM
[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>
Posted 23 September 2012 - 12:51 PM
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.
(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?
Posted 23 September 2012 - 01:55 PM
(2) Is it a bug?
No adding drivers for Win7 and later makes use of dism /add-driver ... and for XP files are copyied to C:\DRV and all sub dirs of it are added to registry.
If correctly added to driver store by dism your display driver should be installed during setup.
Winntsetup.log is created in the new Windows dir. It should log if a driver is added or if an error occured.
This post has been edited by JFX: 09 March 2013 - 10:20 AM
Posted 23 September 2012 - 02:04 PM
"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...
This post has been edited by Atari800XL: 23 September 2012 - 02:06 PM
Posted 23 September 2012 - 02:14 PM
1.inf: The driver package was successfully installed.
2.inf: Error - An error occurred. The driver package could not be installed.
EDIT: Okay there is a bug, the trailing \ cause the trouble
This post has been edited by JFX: 23 September 2012 - 02:22 PM
Posted 23 September 2012 - 02:30 PM
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.
[EDIT: Okay, I read *your* edit about the trailing backslash]
This post has been edited by Atari800XL: 23 September 2012 - 02:32 PM
- ← Help me detect what kind of BCD
- Install Windows from USB
- How to install Windows from USB- WinSetupFromUSB with GUI →