Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by redxii

  1. This is what my HP laptop says for my BIOS: "This package contains the WinFlash utility and a BIOS image for the supported notebook models and operating systems. The WinFlash utility is used to locally flash the System BIOS (ROM) on notebooks operating in a Microsoft Windows or Microsoft Windows Vista environment. Operating system(s): Microsoft Windows XP, Microsoft Windows Vista, Microsoft Windows Vista (64-bit), Microsoft Windows Vista Home Premium (64-bit), Microsoft Windows Vista Home Basic (64-bit), Microsoft Windows Vista Home Basic (32-bit), Microsoft Windows Vista Home Premium (32-bit), Microsoft Windows XP Professional, Microsoft Windows XP Media Center, Microsoft Windows XP Home Edition" The BIOS is flashed while the OS is loaded, whereas in olden days you would have to make a bootdisk with the BIOS image and boot from that and flash.
  2. It will still ask for a key during installation, but you can choose to skip it. However, if you intend to validate with WGA after installation (such as to use Windows Update), that requires you to activate, and when you try to activate, you will have to enter a valid CD key at that time in order to activate. The key-less installation does not get around activation or validation.
  3. I think it is meant that .NET 3.0 doesn't appear on Windows Update for SP3. It's probably because they haven't "enabled" it to show up as an update for SP3 yet.
  4. Nothing is going to change in the service pack between now and when it is officially released.First try integrated SP3 fresh install. Do not remove or change anything else with nLite.
  5. As far as I know, this is correct. A search on the Internet reveils that "Windows Media Player[strings]" is an existing subfolder of the 32-bit Program Files folder. BTW... npds.zip is a Netscape 4 Java plugin that's used for scripted interaction with Windows Media Player 6.4 (LiveConnect). I was looking on Google if anyone else had this "problem".Part of mplayer2.inf looks like this by default: It should be: Because the inf is supposed to have a [strings] section.I did a search on Google for "Windows Media Player[strings]" and this thread, a spyware forum thread, and one of those pages that puts random text related to nothing you were searching for, were the only results. I fixed it myself and placed a new mplayer2.inf on my XP x64 CD (happens in Server and XP x64).
  6. The express installer doesn't support slipstreaming. What junk are you talking about? You'll get the junk either way.
  7. Windows doesn't need to tell the future. XP OEM, retail and corp have different media. If you install with retail, you can only enter a retail cd key, either during setup or after. If you install with OEM, you can only enter a OEM cd key, either during setup or after. If you install with volume license, you can only enter a volume license cd key and has to be done during setup.
  8. Clarifying goes both ways. Jazz needs to clarify what kind of license he is trying to use. I see no mention of it, it does make a difference. Also, looking further, Jazz doesn't mention if he wants to skip the cd-key part, unattendedly, which isn't supported and you have to provide a key in your answer file; or if when the cd-key part comes up, it forces him to enter a cd-key, and in which case cd-keyless isn't supported in Corporate. SP3 will still ask for a cd-key during normal setup, and if using oem or retail, you can just press "Next" and it'll prompt, just like in Vista.
  9. XP Pro Corp still requires the user to enter a key, OEM or retail does not. Dunno what to tell you about your cd key not working, I have one OEM and one retail and they are working fine on a SP3 slipstreamed install.
  10. redxii

    Intergrating SP3

    SP3 is cumulative to the previous service packs and there is no prerequisite service pack when integrating. The SP1 prerequisite is for upgrading a Windows installation. This question comes up a lot... is there a FAQ here somewhere?
  11. Yes. Or with SP1, or SP1a, or SP2.
  12. English v3311, directly from Microsoft: http://www.download.windowsupdate.com/msdo...e6ccb5ce018.exe (315MB)
  13. When they say "removed", they mean "removed". They even removed the Internet Explorer desktop icon setting. I guess it is an attempt to make IE look less integrated into Windows. The only hack is to open a hex editor and starting entering 0s and 1s into an address bar.
  14. There is a Post-SP2 update pack by RyanVM, which is like integrating a service pack and doesn't require to use unattended: http://www.ryanvm.net/msfn/ Then, if you want, you can create an answer file to use setup unattended.
  15. royal.sys is an activation crack. You're gonna have to buy Vista and use that disc instead of one downloaded and there won't be any errors.
  16. If that's true, how did it bloat by almost 200MB ("~500MB") if 3300 installer is 315MB? Or if he means RC2, in which case it's only 315MB installer.
  17. They released as SP1 so people wouldn't have to wait for SP1.
  18. Make sure that each .reg file has this on the first line, followed by a blank line: Windows Registry Editor version 5.00
  19. Vista SP1 and the cert/key are working fine on my HP. vLite_Business.ini
  20. "OEM" is what Dell etc use to build and sell with PCs. I guess Vista Enterprise is akin to XP Pro Volume License. XP Pro VLK is the same exact product as XP Pro OEM or retail, just the licensing/activation scheme is different.
  21. I vLited Vista x64 on XP 32-bit. Unless that's changed since the last time I vLited 64-bit Vista.
  22. Yes. The Vista x64 are files like any other. You'll have to test it on a real machine with a 64-bit processor, unless you have virtual machine that happens to support 64-bit guests.
  23. Just asking 'cause people are throwing around "6001.18000.080126-2040" saying 6001.18000.080118-1840 had a major bug, but failed to say anything about the bug. I even heard a 6001.18000.080131-1830. Of course none of these really have any solid source except 6001.18000.080118-1840 being the build of SP1 RC1 Refresh 2 and people feel that it needs an official "it's done" label .
  24. Is 6001.18000.080118-1840 official, though?
  25. That's not a slipstream; not 'a slipstream method that I'm not used to' but it goes by some other name than "slipstream" or "integration". Perhaps a "post-setup task". What if Microsoft just says "Oh we'll just put the Vista service pack file in the Updates folder and distribute it to retailers and put a nice "SP1" bubble on the box"? Not only would it take up more space, but AFTER setup you'd be waiting another good hour to have "Vista SP1", spending more time just so the SP1 installer can overwrite the files you just copied when the install source itself could have been updated.

  • Create New...