Jump to content

redxii

Member
  • Posts

    272
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts 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 hate to say this, but since this has not been "officially" released by MicroSoft I'd wait until SP3 is officially released and try again. They may fix this issue for you.
    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.

  4. I'm getting a folder in Program Files(x86) called Windows Media Player[strings] and it has on compressed file inside. Seems out of place to me.
    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:

    [DestinationDirs]

    wWMPCopy.Core.uni=16426,Windows Media Player

    wWMPDelete.URLs=16426,Windows Media Player

    wWMPCopy.Plugin=16426,Windows Media Player[strings]

    KEY_DXMEDIA="Software\Microsoft\Multimedia\DirectXMedia"

    KEY_NETSHOW = "Software\Microsoft\NetShow\Player"

    KEY_FILETYPEDB = "Software\Microsoft\Multimedia\MPlayer2"

    KEY_WMP = "Software\Microsoft\MediaPlayer"

    KEY_ACTIVESETUP = "Software\Microsoft\Active Setup\Installed Components"

    DSHOW_GUID = "{22d6f312-b0f6-11d0-94ab-0080c74c7e95}"

    It should be:

    [DestinationDirs]

    wWMPCopy.Core.uni=16426,Windows Media Player

    wWMPDelete.URLs=16426,Windows Media Player

    wWMPCopy.Plugin=16426,Windows Media Player

    [strings]

    KEY_DXMEDIA="Software\Microsoft\Multimedia\DirectXMedia"

    KEY_NETSHOW = "Software\Microsoft\NetShow\Player"

    KEY_FILETYPEDB = "Software\Microsoft\Multimedia\MPlayer2"

    KEY_WMP = "Software\Microsoft\MediaPlayer"

    KEY_ACTIVESETUP = "Software\Microsoft\Active Setup\Installed Components"

    DSHOW_GUID = "{22d6f312-b0f6-11d0-94ab-0080c74c7e95}"

    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).

  5. => This CAN NOT be related to the type of key because Windows cannot tell the future and cannot know what type of key you intend to enter "later on" (!).

    OK, I've also run into this problem... looking forward to a solution... :-) Unfortunately, I don't have one either and I was looking forward to this "feature" because it would allow me to create Virtual machines and give them to a friend who could then enter his own CD key...

    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.
  6. 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.

  7. 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.

  8. 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?

  9. 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.

  10. 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 .

  11. 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...