Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ulaiphur

Profile Information

  • OS
    Windows 7 x64
  • Country

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Could you rename my account to Ulaiphur? Thanks!
  2. Hello! I'm trying to create an updated XP SP3 x86 image with all the updates since SP3. I need some help on figuring out the order to install updates downloaded from WUD. What I have so far is: 1. Download all updates via WUD using the list from 2. Slipstream WMP11 via WMP11 integrator 3. Slipstream IE8 via nlite 4. Slipstream all updates from folders: Security Updates, Non-Security Updates, WMP 11 Updates 5. Slipstream AHCI/SATA 3rd party drivers using DPs_Base MassStorage pack Now, for the questions... a) Is the order above correct? b) Does WMP11 integrator works for XP x64? It outputs an error. Thank you.
  3. There's a bug that crashes WinNTSetup if you click on the VHD button. To reproduce do the following: click the Tweaks button and then click VHD and the error is universal windows installer has stopped working. I'm using Windows 8.1 x64 if it matters. Also, congrats for the new version.
  4. I have a windows 7 computer in which I've used a driver installer application to update all drivers. Now, this program crippled the default usb drivers, and generic mouse and keyboard. Uninstall from device manager did not work, as after restart it still installed the custom driver. Using sysprep.exe /generalize worked, it removed all drivers but also removed specific computer related elements like hostname, users and some settings. I'm looking for a sollution similar to sysprep, but something that will only remove the drivers and leave applications and settings alone. What would be the best way to remove all custom drivers and reinstall windows default drivers?
  5. I have a question, sorry if it's a lame one: I created a VHD and want to setup Windows 7 on it. I'm not interested in booting from it --just extract the files. WinNTSetup insists that I select a Boot Drive and will not allow to select the VHD as Boot drive. Is there any way to get passed this? All I want is to extract all WIM files to a vhd. Also, I think I found a bug: After the creation of VHD through WinNTSetup, and clicking again on the VHD>> menu, it displays: Universal Windows Installer stopped working.
  6. Nevermind, it works fine with -Source: Thanks
  7. You really thought of everything --that's how all coders should be. Great job (again)! Is there any way of doing this by cmd? Load the iso and set the image index?
  8. I'm using WinNTSetup in a WinPE environment. I don't think I can use IMDISK.
  9. JFX Maybe you could research a way to use an .iso as the wim input format. WinNTSetup will then only extract the install.wim from the .iso to a temporary location. This would be usefull for me as I have, at the moment, both ISO files and .WIM files so it takes double the space to keep them. I am aware that I can extract the .ISO files and then use the full path on WinNTSetup but by doing so it also changes the checksum of the ISO and I don't want that.
  10. I'd like to discuss this topic further. Say it's the same .wim used to install the windows. No, I'm talking about everything else EXCEPT the registry hives. In this case, all of the user settings would be saved, right?
  11. Is an imagex /apply operation the same as a Windows DVD Repair operation? Say we have a system with many corrupted files, HDD issues. Would the imagex /apply be able to fix it? Everything will get overwritten obviously but the user registry hives will remain intact, correct? I'm assuming some if not all user application will no longer work but windows would be fully repaired. Has anyone tried this? Is this a better way than windows repair? Thank you
  12. The Software Restriction policies really mess up your system. Any new install you make will be broken if those policies aren't whitelisted. Not to mention programs that are actually run from APPDATA, like jDownloader, and WUD. You might say, put the executables under whitelist but it will be getting tedious once you will have 10 apps you need to whitelist -- this is not a sollution. Short answer: no. This is because whatever access you have on those drives/folders/files, your malware application will also have because it is run under your user account. Thus, there are two options: one way would be to store your files on an HDD with encryption (programs like TrueCrypt). With this no writing or reading can be performed without entering your password for the drive. or make a complete backup of your system using software like Acronis TrueImage and make a weekly backup. Store the backup on an external HDD, and never keep it plugged in to your system. Then IF you get infected, just boot up the CD and restore the image from the backup. It'll format all the partition and re-create your data.
  13. Yes, but is winnt.sif in i386 the same with the one you use in your batch? In my cause, the one from i386 is very different from the one I use through WinNTSetup
  14. 1. Here's an example of a deployment day: open winntsetup.exe, load 7-admin.ini for virtual machine testingsetup finished, take HDDinsert new HDD for windows 10 deploymentsame instance of winntsetup.exe, load 10-user.ini which contains image, unattend and OEM paths different than the 7-admin.ini If I do this 10 times a day, should I do it manually? I'm the only one who requested because I am the only one that actually uses it every day, and some times more than once a day. 2. Passing on to another issue... I think something is wrong withour XP deployment. If I already have a winNT.sif in XPDir\i386\, and trying to add an external winNT.sif or winNT.txt, the result is strange and unstable. Sometimes it applies the file in i386, otherwise the external one. I've tried it 3 times, and it is the same. It only worked when there is no winNT.sif in i386. If this is a normal behaviour, a suggestion might be to exclude the file in i386 if an external one is applied. Can anyone confirm? 3. Also, I would like to say that your application is the best and does not need any kind of change. Some points to look out for, and my humble two cents: always make it compatible with WinPE, cause that is where it will be used the most. All of them, because on some computers, the latest PE does not work, so try to maintain a PE2 (Windows Vista) To PE10 and beyondmake available the same options in the .ini configuration as well as in the command-line. Sometimes it is easier to work with .ini rather than batch, and other way aroundBe on the lookout for bloated stuff, keep it small, keep it simple, and focus on deployment only. Not other functions
  • Create New...