Jump to content

Star Shadow

Member
  • Posts

    4
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by Star Shadow

  1. Hi, I want to change the path of all TEMP directories: the main system one (C:\Windows\Temp) to D:\Temp and the ones in %USERPROFILE%\AppData\Local\Temp to D:\Temp\{username}\ So, if I make new accounts those paths will be used. Can someone provide step by step instructions on doing this? I want to get it right the first time. I know Win 7 is still available as RC, but it should be the same command for the final when that is released ... well I hope, but we'll burn that bridge later. Now is the time to practice on RC images. Thanks.
  2. I can't tell anything about issue you are having but you can NOT integrate hotfixes or service pack to Vista x64 while runing x86 Windows as a host, while opposite is possible (you can integrate into Vista x86 while runing x64 Windows as host). Cheers I know, and I said as much in my post. That's why I didn't know if this issue is specifically related to being vlited on a 32 bits platform or not. I think it might be since no one has mentioned this before.
  3. My source was Windows Vista Home Premium OEM w/SP1. This is the new OEM disc that has SP1 integrated on it. I had vLite 1.1.6 installed on a Vista x86 (not a type ) machine. I only use vLite to add hotfixes, drivers, make the install unattended, and select a few performance enhancers (like forcing kernel to run only in memory rather than swap to hard disk). However, being on 32 bit I couldn't integrate hotfixes this time. I entered in my personal information for my name and organization in the unattended area. Everything proceeded as normal and I installed it on a new computer. After installing Office 2007, I noticed that in the area where you can enter your name, initials, and organization, the default was "Microsoft" for both name and organization. I did a search of the registry and found that the 32 bit fields had my name and organization filled in, but the 64 bit fields did not. Those fields are located at: HKLM\Software\Wow6432Node\Microsoft\WindowsNT\CurrentVersion\ and the two fields are: RegisteredOrganization and RegisteredOwner. Those fields both contained "Microsoft", which leaves me to believe that they were not updated by the vLite to contain the info I entered. I don't know if this is normal for having done this on a 32 bit version of Vista or not. I have yet to try vLite'ing Vista64 from Vista64, so I cannot say if this will fix the issue. However, if one is vLite'ing Vista64 from Vista32, maybe vLite can be updated to know about those two registry keys and update them. Also, I have not looked at the new beta yet. Thanks and I hope this helps.
  4. Does anyone know if it is possible to take all the update .msu and .exe files and extract the contents to be combined into one nice update package? I am not talking about taking all .msu files and extracting them to a individual .cab files and then compressing those .cab files into a zip file, but actually extracting the contents of the .cabs and combining them into one install .cab/.7z/whatever file to be integrated using vLite. I have used packs by Ryanvm for XP and that was one nice file. That is what I want for Vista. I do not wish to distribute this file, but use it for my own purposes. Also, I noticed that some updates need to be installed in a particular order, since two updates my update the same file, one being newer than the other, and so version information would need to be determined in combining all the updates to one file. I have the WAIK, would that allow me to do that? Do I need the .xml and .pkgProperties.txt files that get extracted from the .msu file? I am beginning to think that I may need to write my own program to make one update file. If so, what are the resources that I need to read to learn about how to interface with the Vista updates? Thanks.
×
×
  • Create New...