- 238

- United Kingdom
More or less. Basically...Is not true that most hardware to a degree is incompatible until software forms a relationship between the 2?
A PS2 or PS3 joypad is not traditionally compatible with a PC, the PS2 pad from a physical hardware perspective, and a PS3 pad from a software perspective as it does have a USB etc. But either from a hardware addition (PS2) or a software addition (PS3) both can be made to work.
If an API can build bridges between 2 hardwares through software that dont traditionally work together is it not right to say that the problem is no longer a hardware issue but now a software issue?
So if we are talking about wheels for the 360, if a software patch can allow for a wheel to work on a device despite hardware incompatibility then as mentioned the issue is no longer a hardware issue but that of a software issue.
Plonking a Cell processor into an Intel motherboard will not work, as that is a hardware issue. No amount of software can fix that, as I am sure a cell CPU does not even fit physically into an Intel CPU housing.
So from what I understand, the issue with the 360 and its wheels is that it is a hardware issue until a software solution can fix it, which in my mind makes it a software issue that requires software to fix it? Of course this conclusion only works in my mind if a software solution can indeed allow for certain other incompatible hardware to work togehter! (Does that sound right?)
Anyway I am not a programmer or a hardware specialist so please feel free to set me straight
1. If you can plug A and B together (e.g. 8 pin USB male / female), that's a good start.
2. If devices A and B share the same device controller type, (e.g. USB) that's also important.
3. After this, anything & everything can be done or emulated in software via O/S patches, firmware patches (if one / other devices can be flashed) or a device driver.
Microsoft can do whatever they want in s/w on their own platform, they could make all devices compatible if they so wanted but it would come at a price to them.
It's all doable & I've done it myself since the days of serial / parallel / RS485 port & ISA / PCI card stuff to more modern day ethernet & USB. Most dev kit devices are flashable, but for final, production h/w it's cheaper to write to ROM and ship. It just means that later on you may have to do some patching on the PC / other to fix compatibility issues... In as far as stock control and shipping, etc goes... Quite often manufacturers will change the h/w internals (chips, PCB, etc) to save costs and may ship EPROMs as well anyway - so some devices can be rescued by flashing rather than soldering a new ROM with new firmware.