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. 



shabador

Member
  • Content count

    21
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About shabador

  • Birthday 06/07/1984

Profile Information

  • OS
    Windows 10 x64
  1. When running WPI and installing from a network share, all exe-files gets flagged as "blocked" and you have to manually press run on every exe as WPI launches them. I seem to remember this was an issue earlier when Win8 came out, and a later version of WPI solved it. So it seems your workaround for that issue has been voided. Hopefully there´s a quick and easy fix for this, as it´s kind of tedious to have to attend my unattended executables.
  2. WPI v8.7.2 Release Thread

    Sweet. I've been noticing that the process sometimes slows to a crawl, eating up the cpu on some configurations with 8.7.0. Keep up the great work!
  3. [Old Guide] Services and components

    Good initiative. I agree with all the follow-up posts here at the moment, and got a couple of extra notes for you: It is also used for text-to-speech applications. Ventrilo for example uses this to make Microsoft Sally (or whatever her name is) say who connects to the server, changes channels, etc. Isn't this needed for Dynamic Drives? As for drivers. If you have downloaded drivers available for integration, you can remove them all.
  4. Official x64 SP1 out today!

    From tweakguides.com "It appears that Microsoft has released Service Pack 1 (SP1) early for Windows Vista x64 users - many are reporting that SP1 is officially available in their Windows Updates. It is currently unclear as to whether this release is accidental or not, but if you want to install SP1 this way keep in mind that there are three pre-requisite updates (KB938371, KB937287, and KB935509) which you should install before installing SP1 via Windows Update. Note that the standalone SP1 package doesn't need these updates prior to installation. Update: It appears this loophole may have been closed now."
  5. Unattend part not working with rc1

    What you could do to start an unattended installation from a HD is to first boot a WinPE 2.0 image, then navigate to your vlite'd installation files through the cmd-prompt and run: setup.exe /unattend:Autounattend.xml Works without a hitch every time.
  6. vLite 1.1 beta - vBloat

    Getting this .Net-error when I press Apply and vlite starts doing it's magic, on 2 of my vlited computers (one 64-bit and one 32-bit) System.NullReferenceException: Object reference not set to an instance of an object.
  7. how does Vlite compress .wim files?

    So if Nuhi made vLite commercial, it would be okay? What if that is Nuhi's plan when vLite is a fully functional product out of beta? He has spent a lot of time and effort on it (and on nLite), and he certainly deserves to harvest the fruits of his work. I myself would not hesitate to buy it (If it of course came with good support, updates and was fairly priced). Speaking of which: OMG! WHEN IS NEXT VERSIONz!11111! EDIT: Cool. I made my MSFN-account before Nuhi. Give me cake!
  8. Sorry if this has been asked before, but I had no idea what to search for. As you can see from the topic, I had to improvise a lot creating that title... Anyway... I wondered if someone knows about a tweak that allows me to change the predefined shortcuts in these dialogboxes (marked in red):
  9. Continue searching. There are a couple of more places to edit. (I know about them, I've editet them manually before...) Anyway. I think fedek9001's solution is the best one I've encountered if there is no possibility to edit one of the files in i386. And fedek... You can combine some of the syntaxes on setenv. So you only need this. md E:/Temp setenv -umd temp E:/Temp setenv -umd tmp E:/Temp
  10. Thank you very much. It's not what I wanted the most, but this is the second best solution. Thanks again.
  11. Thanks for the regkey, Tsunami. But as you said. That does not work for the user variable. It is propably possible to export out all the user variables and append them on a new install... But that is not what I would like to achieve. There must be a way to edit this in one of the files on the XPCD. These environment settings must (logically) be created by something. But sadly it seems like the solution is buried deep withing the files of i386...
  12. I know that, but I need to change them before I have the ability to go to My Computer Properties. I'm talking about doing this unattended, during the installation preferably. Also: If you change the variables in the path you specify, not all of the temporary files are created in the new place. There are still numerous listings in the registry that points to the old location.
  13. Your winnt.sif file seems ok. (Looks a lot like mine) You have remembered to format both the C: and D: disks before you start your install, right? Try to set: FileSystem=* It is a long shot, but could perhaps work. Sometimes (often) windows works in mysterious ways...
  14. True. But I'm not certain about what regtweaks that will be needed to change all temp variables to another destination. If someone has done this before, it would be great if they posted what they did to make it happen. Isn't those variables supposed to be located in the i386 folder somewhere? Hive seemed to be the most likely place, but I couldn't find the correct place to edit.
  15. As the title says. Is it possible to change the location of the TMP and Temp variables before installation? I want to be able to move them all to, say E:/tmp/ without having to go through the registry manually after the installation. I've checked around in the Hivedef.ini and other hives. I only found one listing, changed that, but it didn't work. Temp was still located in C:/Windows/Temp and D:/Documents and Settings/xxxx/... (I've used winnt.sif to change userdir location) I've thought about adding regtweaks that are installed post-install, but I'd rather try to get it done in the middle of installation.
×