Recommended Posts

Yeah it does but it's the beta version not the RC.

What do you mean by that?

It's the build of IE 8 for that build of Windows. You can't install the Vista version of IE on Win7... Just like you can't install the XP version of IE 7 on Vista.

Except the build number for ie8 in win 7 is different from the beta for vista so it's not the same. Maybe why it doesnt need the patch for the new IE exploit although I do wonder since vista with the sp2 beta won't accept the patch, so I'm assuming they are both possibly immune to the exploit.

Except the build number for ie8 in win 7 is different from the beta for vista so it's not the same. Maybe why it doesnt need the patch for the new IE exploit although I do wonder since vista with the sp2 beta won't accept the patch, so I'm assuming they are both possibly immune to the exploit.

The upcoming beta release is not affected by that vulnerability. Those running a pre-beta build should probably make use of one of the workarounds described in the advisory (details here).

What do you mean by that?

It's the build of IE 8 for that build of Windows. You can't install the Vista version of IE on Win7... Just like you can't install the XP version of IE 7 on Vista.

Yes, i know that, i was just replying to the OP, which he stated "Hey I was wondering if a build of IE8 RC1 has been released for Windows 7 ."

Actually if you extract the IE8-WindowsVista-x86-ENU and then extract the IE8.msu:

> Find file names Windows6.0-KB944036-x86-pkgProperties.txt

> Contents of txt file:

Applies to="Windows 6.0" change to 6.1

Build Date="2008/12/6"

Company="Microsoft Corporation"

File Version="1"

Installation Type="FULL"

Installer Engine="Component Based Servicing - WUSA.exe"

Installer Version="N/A"

KB Article Number="944036"

Language="ALL"

Package Type="Hotfix"

Processor Architecture="x86"

Product Name="Windows 6.0" change to 6.1

Support Link="http://support.microsoft.com?kbid=944036"

repack the .cab files along with .xml + .txt file and you can install it on Windows 7

So anyone with the RC version of IE8 care to answer how it goes ram wise? IE7 was very good with ram but it seems IE8 has hit epic FF ram usage levels. I'm on beta 2 for IE8 btw.

Actually if you extract the IE8-WindowsVista-x86-ENU and then extract the IE8.msu:

> Find file names Windows6.0-KB944036-x86-pkgProperties.txt

> Contents of txt file:

Applies to="Windows 6.0" change to 6.1

Build Date="2008/12/6"

Company="Microsoft Corporation"

File Version="1"

Installation Type="FULL"

Installer Engine="Component Based Servicing - WUSA.exe"

Installer Version="N/A"

KB Article Number="944036"

Language="ALL"

Package Type="Hotfix"

Processor Architecture="x86"

Product Name="Windows 6.0" change to 6.1

Support Link="http://support.microsoft.com?kbid=944036"

repack the .cab files along with .xml + .txt file and you can install it on Windows 7

Ugh, that's a terrible idea.

Actually if you extract the IE8-WindowsVista-x86-ENU and then extract the IE8.msu:

> Find file names Windows6.0-KB944036-x86-pkgProperties.txt

> Contents of txt file:

Applies to="Windows 6.0" change to 6.1

Build Date="2008/12/6"

Company="Microsoft Corporation"

File Version="1"

Installation Type="FULL"

Installer Engine="Component Based Servicing - WUSA.exe"

Installer Version="N/A"

KB Article Number="944036"

Language="ALL"

Package Type="Hotfix"

Processor Architecture="x86"

Product Name="Windows 6.0" change to 6.1

Support Link="http://support.microsoft.com?kbid=944036"

repack the .cab files along with .xml + .txt file and you can install it on Windows 7

While this will trick the Windows Installer into allowing the package to install on Windows 7, I'm sure this will also be a good way to break Internet Explorer (if not more than that), you're replacing files from Windows 7 with files from Windows Vista, I don't think that's going to go over too well.

Well, I'm running Windows 7 on virtual PC and installed IE8 RC 1 with the above mentioned "trick", and the only problem I encountered was not being able to manage addons, other than that all seems fine so far, again I am doing this on virtual PC and dont really care about the outcome/effects to the system. I just wanted to see what IE8 RC1 was.

  • 1 month later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The problem isn't with Epic, it's with the platform holders like Steam and Nintendo, they should be a lot more strict in their review process.
    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
    • "it opens up new doors for people who prefer using Edge, but cannot be bothered to configure a Microsoft account" You already have a Microsoft account if you are using Windows 11, because you can't set it up without one.
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      84
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!