Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Arab Emirates

Everything posted by Arneh

  1. Mine as well. But please search before asking: http://www.latestintech.com/vista-wont-rem...work-passwords/ There are plenty of reports so seems it's a Vista bug or a feature. Yea I know about that. What I mean is I didn't have the issue before in any previous builds (this includes vLited installs of old Server 2008 installs, older Vista SP1 installs both preintegrated and Reverse Integrated and normal RTM installs etc.) which is why I found it weird.
  2. I ran vLite in WinFLP (which basically is XP "light" that MS built from XP Embedded) and removed the Dynamic Volume Manager and it worked/installed fine with no errors in vLite or during setup using the x86 preintegrated 080118... Settings included as attachment. I've got another issue though. It seems it keeps forgetting my Network Share login passwords after reboots even if I select the checkbox to remember the password. Last_Session.ini
  3. 1. Depends on your system and hdd speed. It's a few hours work I'd say. 2. Imagex will ignore and automatically not include pagefile, hibernation etc. when it starts capturing the wim. 3. Yes, you should run vsp1cln before imagex while you're still in the Vista install and it should be fine for vLite use. 4. Don't delete any files before imagex'ing it. That's what vLite is for.
  4. Heh, if you have the 18000 build from 080118, that most likely is not RTM. As for "gluing" them together, that's actually quite easy with SP1. The reason being Vista x64 can now be installed using the 32bit setup so all you need to do is make a copy of your x86 iso, then imagex /export the x64 index from the x64 install.wim to the x86's install.wim and repack the ISO and you're good to go. There's no need to use the x64 boot.wim or anything else fancy.
  5. Basically: 1. It's been known for quite a while that SP1 will not be directly slippable, there should be no surprise about that by now. MS will not make a slippable service pack until SP2. 2. MS will release preintegrated/prebuilt full SP1 ISOs to OEM/Retail and probably MSDN etc. 3. There is no "Updates" folder like behavior for Vista where it would pick up any updates in the Updates folder unlike Office 2007 where it will pick them up and install them. 4. If you can't get the full SP1 ISO, then check vlite.net's first post for a link to the guide on how to "Reverse Integrate" SP1 using WU or the EXE but again, getting the full SP1 ISO is the much much better option compared to trying to "Reverse Integrate" it.
  6. Arneh

    vLite on Vista SP1

    Just an FYI Tihiy, that build of 18000 doesn't look like it'll be the final build anymore if you saw the winfuture post at: http://winfuture.de/news,37209.html Nevertheless, it is useful info for nuhi (as a bug report) and anyone with a copy of a full SP1 to know about. And that WU news is awesome
  7. Yea, it is risky, but since the person probably has to be dual booting in order to do that the procedure and it would be best if that was made mandatory, at least they'll have another OS to boot into. I guess there could be another option of somehow making a System Restore point that could somehow be manually restored using vLite in case things go screwy OR vLite making a .wim of the orig. drive as a backup then proceeding with the changes and if things go screwy, one could just apply the backed up wim.
  8. Yea, imagex capture should/could work but there's also the possibility that if vLite in the future had the option to look in a folder/drive for the .wim contents instead of going into an install.wim, it could just make the changes to the "extracted" files on the spot as long as the person is booted into another OS. No idea if it would work correctly though.
  9. MS in my opinion took the best approach with Windows Fundamentals. Although it's nowhere near as advanced as nLite or vLite, WinFLP does have basic customization settings during setup allowing you to not install WMP, IE, DirectX, additional drivers etc which and it really brings down install size. At the same time, WinFLP doesn't have many of the bits from the regular XP that could be considered "bloat". They should've used the same basic idea for Vista as an advanced customization feature in setup.
  10. Everyone knows that Vista needs a tool like this to get rid of all that "bloat" while XP, even if it isn't nLited, is still pretty decent.
  11. It may or may not be final but one of the exes floating out there is the real 18000, something which hasn't even been released to testers. They only got a WU release of one version of 18000 according to a friend and not the actual exe bits.
  12. vLite does not build a stripped installer. All it does is mount the wim, remove components, update registry hives and that's pretty much it as far as I know and uses pkgmgr whenever a new driver/hotfix is to be inserted. The KB article you pointed to has nothing to do with not using ImageX to capture a Vista OS image for deployment. In fact, it says that that's what ImageX should be used for. All that article is saying is that ImageX should not be used as a general backup tool.
  13. Yes, there is an SP1 RC1 ISO from Connect however it's only available to those in the actual Vista SP1 Beta program. The general public only got the WU choice or the standalone .exe packages.
  14. Looks like someone figured out how to get Vista on the Asus Eee PC thanks to vLite. http://www.modaco.com/content/Asus-EEE-PC-...t-and-it-works/ Its been making the news on various sites today (Wired, Gizmodo etc.)
  15. By the way, there is a newer build out today (only for Server 2008 64-Bit because it includes the new Hyper-V bits) but nevertheless it seems to be much newer than RC1. 6001.17119: http://www.microsoft.com/downloads/details...;displaylang=en
  16. Perhaps you could include that option nuhi as an Alpha (Experimental) option with newer builds of vLite for folks that really want to slim things down and don't really care about the Hotfix/Component install issues or would they rather have to go back the v. old build of vLite that still included that option (after removing stuff with a newer vLite) to be able to use that option?
  17. Yeah, that is what I meant in the guide, don't boot back into that Sysprepped Vista after you're all done with it. It should make no difference I believe whether you use another Vista or XP to capture it.
  18. I personally boot back into my XP install to capture the drive Vista is installed on. 1. Install Vista to a secondary partition. (not the main boot partition) 2. At OOBE, don't do anything and type CTRL-SHIFT-F3 to get into Audit Mode (this is a must) 3. When in Audit Mode, don't close the Sysprep window and install SP1. Let it restart however many times and do its thing. 4. When SP1 is completely installed, in the Sysprep window select OOBE and Generalize and to shutdown the system and select to apply those. Vista should then start shutting down, cleaning out hardware data etc. 5. Restart into XP/another Vista install/WinPE (I really doubt it should make a difference which one you use but I booted back into XP) and run: imagex /compress maximum /flags "Business" /capture d: c:\install.wim "Windows Vista Business" replacing the drive letters etc. That, for me, works. That method has also worked for many other folks I know to get a slipped SP1 install. vLite against that new install.wim. Not as many have tried this one compared to just Reverse Integrating it and getting a full install.wim, but I have tested it with every build (except Beta 1, just didn't have the time) and have always had success. As I said though to MagicAndre1981 in a private message, this is a non-issue nevertheless, no one would want to use Reverse Integrated .wims over the actual slipstreamed SP1 media that MS will release and I'm sure obtaining those from MS or from your OEM or buying a $5 Vista disc update thing etc. won't be too difficult.
  19. I used the RTM imagex to be honest to repack it and then used vLite against that new .wim, worked great. In fact, you don't even need to run that .wim through the whole setup again. Just reapply the .wim using imagex after vliting it, it'll go through hardware detection, OOBE etc. and you're in Vista.
  20. A. If I understood what you said correctly, then you already have a slipstreamed SP1 version of Vista: "only a eval edition of vista with sp1 slipstreamed (RTM)", you just need to run that through vLite and don't need to do anything else. B. There's no such thing as Vista Ultimate (VLK). MS did not release a VL Ultimate Edition. C. If you don't have an integrated SP1, then installing Vista RTM to a partition, entering Audit mode, then installing SP1 on top, then repacking with imagex and vLiting the new WIM will work. Just follow this guide.
  21. Not directly yea. Indirectly (Reverse Integration), of course it can and can be used with vLite but it's not exactly a quick method and the best option will always be to get the slipped image from MS. I wonder why MS don't want to support SP1 integration via pkgmgr. I know they say it'll apparently corrupt the image but surely they could've worked on it and figured out a way.
  22. Yes and no. To convert a normal XP ISO to a WIM would no doubt prove to be extremely difficult and time consuming if even possible. However, MS do ship a version of XP that uses a WIM based setup, that version being Windows Fundamentals for Legacy PCs, or just WinFLP. It's a version of XP built from XP Embedded but runs practically everything the standard XP Pro runs. Unfortunately, MS do not provide any tools to use for it that I know of, so one has to dig up an old version of ximage (from the LH 40xx era) and you can't really integrate hotfixes or service packs easily as there is no "pkgmgr" for offline hotfix integration to a pre-built WIM for XP.
  23. If you are able to obtain the full SP1 ISO, then a better way may be the following: 1. vLite the SP1 ISO customizing/removing any components/features that you don't need 2. Install the vLited SP1 and enter Audit mode as per my guide. 3. Install your apps 4. Generalize/OOBE from Sysprep 5. Repack the wim In this way, you won't have to deal with the possibility that vLite may screw up app installs but you may still have the issue with shortcuts etc. that I described in the previous post (if that issue even exists when using Generalize)
  24. with your method, will be be able to install Office 2007 and other stuff aswell so there already installed? You could install anything you want and then repack the wim however you may get issues with shortcuts etc. not working correctly if you then install to a different partition/drive letter (this is a complete guess as I haven't tried to install apps). The generalize function for Sysprep takes care of partition/drive letter issues for the actual Windows install so that you can install it to whatever system/drive you want later but in terms of it taking care of specific applications, you'll have to try for yourself and see. Again, it's something that I haven't had time for but would like to try sometime. Of course, another issue with installing apps and repacking the wim is what effect it will have on vLite when you go to try and remove components etc. and whether or not vLite will break anything in the registry store or remove any files related/required for those apps.

  • Create New...