Windows 10: what versions of windows can i run Microsoft Cinemania "95 on?

what versions of windows can i run Microsoft Cinemania "95 on?

:)

 

Map Windows 7 Shared Folder to Win 95

Okay .. I figured it all out.

Configuring Windows 95 so it can map Windows 7 shared folders.

You need to update Windows 95 so that it can utilitze NTLMv2 network protocols (and use 128 bit encryption for authentification).
Nothing needs to be done on the Windows 7 machine other than sharing a drive or folder.

On the Windows 95 Machine you will need a local account with the same name and password as on the Win7 machine or in the domain.
The Windows 95 computer does not have to be a member computer in the domain (ie. does not need domain authentification)

1) Install the Distributed File System client for Windows 95 (dfs41w95.exe)
2) Install WinSock 2.0 (w95ws2setup.exe)
3) Install Microsoft Dial-Up Network 1.3 (MSDUN13.exe)
(I wasn't sure what msdun13 does to the TCP/IP stack so I reinstalled winsock2.0 again)
4) Install Internet Explorer 4.01 SP2 / 32 bit (ie40sp2.exe ... you need this or step #6 will termintate without installing)
5) Install Microsoft Installer 2.0 (InstMsiA.exe .. you need this so Windows 95 knows what to do with the .msi file in the next step)
6) Install Distributed Services Client for Windows 9x (dsclient9x.msi)
7) Go into the registry editor (regedit) and go to ...
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control
Create a Key named Lsa
Create a DWORD in Lsa named LMCompatilbility with a hex value of "3".
8) Reboot once more.

Mapping a network drive on a Windows 7 machine should now work.

 

Microsoft Jigsaw and Solitaire apps will not load and run

Hello,

Thank you for posting your query in Microsoft Community.

As you are facing issues with Windows store download and Windows updates too, I suggest you to follow the below steps and check if it helps:

Step 1: Try clearing the Store Cache:

• Press the Windows key + R keys.
• In the Run window, type
  WSReset.exe and click “Ok”.

Step 2: Also I would suggest you to run
Windows Store Troubleshooter and check if it helps:

1. Type Troubleshooter in the
search bar and click on it from the list.

2. Click on view all and select
Windows Store Apps and click next.

3. Follow the onscreen instruction.

Step 3: Run Windows Update Troubleshooter

I suggest you to run the Windows Update Troubleshooter. Follow these steps to run Windows Updatetroubleshooter:

• PressWindows key + W and type troubleshooting.
• Select Troubleshooting.
• Select View all on the top left corner.
• ClickWindows Update troubleshooter.
• Follow the on-screen instructions to run the troubleshooter.
• Check if issue persists.

Step 4:

I suggest you to check if the services responsible for Windows update is running. Refer to these steps:

• Press Windows key +R, type “services.msc”
• Locate the BITS, Cryptographic, MSI Installer and the
  Windows Update Services and check if it is running.
• If not, right click on the service and click start to start the service.

Hope this will fix the issue, if not let us know with the updated status and we will be happy to assist you further.

Thank You.

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



Microsoft suggests updating to Windows 10 to patch Windows 7

• 
  
  
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer