Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

0 Neutral

About BikinDutchman

  1. Partition Magic can hide partitions. You can also edit partition tables manually but in that case you really need to know what you are doing.
  2. In addition: Make your partition primary indeed and make it active (means it will be the boot partition). Also make sure you have the following option in your unattend data file (WinNT.sif): [Data] AutoPartition=0
  3. Cut back on the Intel SATA drivers (iaAHCI and iaSTOR). Only keep the one that you really need and try again. There is a problem with integrating multiple instants of the same textmode driver.
  4. The C:\$WIN... you mean? that is not his choice but what the installer creates fro the GUImode setup.
  5. Yes that remains strange. I can barely imagine that you removed something that disabled disk management. You might have an incomplete installation. Do you have nLite 1.4.8 for sure? Did you look at Windows\Setuperr.log?
  6. Well, one situation where you can sit behind your screen and wait for you PC apparently doing nothing for a long time is when it is searching for unavailable network locations. -One of the most notorious examples is pointers to icons that resided on \\Whatever\No_Longer_There. It is difficult to beleave that is an issue during installation; I am not sure if the network is already installed at t13. -Anyway the fact that there is so little disk activity for so long reminds me of the PC either searching for "something" out there.
  7. The MS article is about substantial slow down not completely halting the process. You might remove the OEM parts: the $oem$ folder and I386\WinNT.sif, and see if you get a better integration.
  8. What I meant to say is completely delete the partitions not just format them. There are several ways to do that. -If you booted from another disk you could work with My Computer > Manage > Disk Management or: --CMD > diskpart > list disk > select yourdisknumber > clean You end up with a single disk in raw format and no partitions; then start partitioning again.
  9. Fast and unstable does not sound good. We recently had issues with the windows install crashing due to WBEM copy errors. That crashing means that during unattended install the installer cannot do/find something, drops the ball (stops copying, registring etc) and moves on to the next step. This has all been fixed in nLite 1.4.8. The crash would generally leave some errors in setuperr.log though. The installation loitering at t13 is normal, see previous posts, and it is a matter of taste whether long is too long. I would be more concerned about the installation being too fast there.
  10. If you can start all over again I would just delete all partitions and create one primary partition with un attended windows install. After that create one, two ot three PRIMARY partitions after you are back in windows. There are more ways of doing this but this is the simplest.
  11. I see you have two Silicon Image drivers installed; that can cause trouble if certain file names are the same. For testing you may get rid of the other one. Also there are subfolders in your driver package. Personally I would "flatten" the driver: delete the IA64 folder; merge the contents of ext64 in the root and adjust oemsetup.sif accordingly. For real analysis of the problem you need to look in DOSNET.inf and TXTSETUP.sif and see if all the right files are present and get copied in either textmode or guimode. This is difficult to spell out; you might look at what happens with a simple in
  12. Did you check your Windows\Setuperr.log and Setuplog.txt? Setuperr.log should have nothing, zero, nada. Setuplog.txt is a mess; you can ignore most of the bulk errors such as those about cannot delete and cannot copy in the dll cache.
  13. Can you tell us how you make partitions
  14. Are you sure that any one of the "drivers" in the All folders is actually installed? The SMBUS bang may be a symptom that nothing happened at all. Look under Device Manager > System Devices if any installed device has a recent Intel "driver". As far as I know you would normally integrate the drivers in the All folder with nLite by Insert > Single driver and picking one of the inf files. You can verify what nLite copies by inspecting DOSNET.inf.
  • Create New...