Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[wierd]

check on the root hub also.

[Elvang]

Ah, it was enabled on those; disabled now. Will have to wait and see if that fixes it.

[Gunner-Chan]

There are tons of XP-compatible games that don't work on any later Windows OS. It's not just copy protection, the underlying driver model and a few other systemic things changed between XP and 7.  Plus, it seems like a bunch of game-specific workarounds got pulled out of the OS.

Examples?

Games shouldn't care about the driver model changes (they should only interact with devices through the Windows API / Direct-X, which didn't break compatibility) outside of copy-protection drivers (and I already mentioned copy protection). So that just leaves the wonderfully vague "a few other systemic things" and "a bunch of game-specific workarounds".

Some games had 16-bit installers (which don't work on 64-bit Windows) but Microsoft actually put a compatibility shim in later Windows versions which recognises all the known generic 16-bit installers and substitutes them for 32-bit versions so that they can install successfully.

The only issue I know of outside of copy-protection is some 256-colour games have technicolour issues on Windows 7, but there are workarounds for that (and it may be fixed on later Windows versions anyhow, I haven't checked).

Wow this is late as hell but I forgot I posted here at all!

Some of the games I've had trouble with are from a certain sorta era of videogaming, like Jagged Alliance 2 loves to freak out, freeze horribly or crash even with a bunch of fixes and the 1.13 mod installed and tweaked for windows 8 compatibility. Pretty much anything that wants to run in 16 bit color also works terribly full screen and refuses to be windowed. Both combined being why I wanted to set up a VM, it's a lot simpler than messing around with hacks and tweaks for any given game.

[wierd]

This is surprisingly common.

Another issue comes from the added layer of thunking between 64bit and 32bit code stacks on modern windows OSes. things like DirectX are going to be 64bit native libraries on modern systems, but the games will be expecting 32bit calls. The added waiting for doing the thunking can cause timing loops to fail, and thus for games to crash spectacularly.

Microsoft has a tool that is intended for ... business clients that just wont/cant upgrade their software.... (ahem).. called the Compatibility Toolkit.

It is sometimes useful for getting old games running on modern windows, and is the "On steroids" version of the compatibility settings options when you right click on a shortcut.  It has options. LOTS AND LOTS OF OPTIONS.  You need to know what you are doing.

[Thief^]

I've played with that... it gives you a real appreciation for how much work Microsoft puts into application compatibility.

[chaoticag]

I guess I'll bite. So recently I had upgraded to windows 10 on my desktop but now having one tiny issue. My mouse keeps disconnecting and reconnecting. I'd tried unplugging and plugging it back in, setting it so that windows cannot close it down to save power, plugging it into a different usb port and restarting my computer. Problem still persists. It worked fine when I was running windows 7, so this is kinda confusing. The mouse is a Razer Death adder 3.5G and the drivers seem up to date.

[Thief^]

On the last page someone else had the same issue, and was recommended to check the power settings on the "USB root hub" in device manager as well as the mouse.

Edit: also check it on another machine, there's always the possibility it's just developed a fault.

[chaoticag]

I knew I forgot to mention something. I'd done that yeah, for all the listed usb root hubs on my computer. It's also weird since this started specifically when I upgraded the OS, as in moments after.

[wierd]

Is this one of those straight up USB3.0 controllers that does not also have a USB2.0 interface baked in?

You can tell in device manager, because there will only be a USB3 root hub, and no USB2 or USB1.2 root hubs.

If so, my guess is that this is a driver related issue with the USB host controller. (Microsoft and their insistence on their WHQL signed drivers, and forcibly updating drivers via windows update have a pretty strong track record of removing perfectly functioning OEM drivers and putting less than stellar, and even broken generic ones in their place. One of the many things I really dont like about windows 10.)

I will research it more to see if others have had this issue.  I will presume for the moment that it is one of those usb3 only host controllers, which are almost always intel based.  Give me a bit.


To help me find you a solution, (and because the friendly name is almost never useful), can you please put the PCI hardware ID for the USB host controller up here?  you can easily get it into the clipboard from device manager.  I can more definitively identify the controller, and hunt for known driver problems that way.

So far, initial digging suggests that there have been a number of people having problems with USB devices on windows 10, but most have been related to USB2 root hubs. 

[chaoticag]

I'm in class at the moment but I'll post the PCI stuff when I get back from uni. It doesn't seem to be affecting my keyboard, so I'm not sure what is going on, and they're plugged right next to each other before I replugged the mouse in a different usb port

Well, here's what device manager spits out as far as names go for usb stuff.

Spoiler (click to show/hide)

As for the PCI hardware ID, I don't seem to have that option on the intel usb host controller for some reason? This is the options it gives me under details.

Spoiler (click to show/hide)

So yeah, this is what I'm getting.

[wierd]

OK, this is an older intel USB3 controller. It has EHCI (USB2.0) device class in addition to XHCI (USB3) device class.

 I am reading that this is a very common problem, but am not getting a very good set of solutions. Some users reporting this problem suggest that the issue may be from a short in the cord. (looking up your mouse, it appears to be a corded mouse.)  See if you can cause it to disconnect by straightening the cord all the way out, and wiggling it.  If so, the mouse itself may be the problem.

If there are no issues with the mouse itself, there is ample evidence to suggest that MS's USB driver for this device (USB controller) is lacklustre. Try making a restore point, and installing the intel OEM driver.

Bear in mind, there is a caveat here.  Intel has not released a windows 10 driver for this model, probably because it is an older chipset. The newest available is a windows 7 driver.  I would expect that it got overwritten during the install process with MS's generic one because of this.  This may or may not even work at all.   Due to windows 10's absolute batshit insistence on signed drivers only, you cannot redecorate the .inf to make windows install the older driver.  Instead, you will probably have to use the compatability troubleshooter stupidity to make the intel installer for the driver work.

Simple intructions on troubleshooter:
http://win10faq.com/install-or-update-drivers-in-windows-10-2/

and link to intel's latest driver for that USB controller:
https://downloadcenter.intel.com/download/22824/USB-3-0-Driver-Intel-USB-3-0-eXtensible-Host-Controller-Driver-for-Intel-8-9-100-Series-and-Intel-C220-C610-Chipset-Family

!
REMEMBER TO MAKE A RESTORE POINT FIRST.  This very well could go sideways on you!

[chaoticag]

Hmm, apparently my computer "doesn't meet the minimum requirements for this program" when I tried to run it under compatibility. Since the chipset is the issue I guess what I'm going to have to do is either get a new mouse or a new motherboard? Thanks for the help at least.

[wierd]

did you try running the installer as administrator?

[chaoticag]

Yeah, set it to windows 7 and administrator but it wouldn't install.

[wierd]

Freaking typical.

You might get lucky if you run it without compatibility mode, but meh.

Now you know why the "Fuck you Microsoft" thread exists, and why myself and others chipped in on it.

I am not a fan of this crap, and I refuse to use windows 10 as a result unless I am forced into it at work. At home I use win7, 8.1 with classic shell (gag), or linux with WINE.

With 7 and 8.1 I can disable strict driver signing enforcement, and use a doctored INF to get get drivers that I know actually work to be installed--- but Mother Microsoft knows best!! 

(grumbles angrily.)