First post, by SamBushman
I've been experimenting with a Magma 1-slot PCMCIA Cardbus-to-PCI enclosure. For my messing around, I acquired an old Sony Vaio PCG-FX170. When it arrived it had Windows XP Pro already installed on it. I got the Magma drivers all set up and installed an ATI Radeon 9250 PCI in the enclosure. Once all the hardware was up I noticed one of the 2 display devices were failing to start in Device Manager. No sweat, I continued forward anyway. Everything seemed to work. I got 3D acceleration for Max Payne and Morrowind. Neat!
To try and improve the laptop's performance, I removed the existing OS and did a clean install of Windows ME (the original OS this laptop would have shipped with). I also installed a batch of community aggregated official updates to get the OS as stable as possible. With that done, I installed the Magma drivers and ATI drivers as before. However I saw some subtly different behavior from my XP experience. The ATI card is displaying the message:
If you can read this message, Windows has successfully initialized this display adapter.
To use this adapter as part of your Windows desktop, open the Display option in the Control Panel and adjust the settings on the Settings tab.
Seems like a good sign....except any attempt to enable the display connected to the card just does nothing. I get a prompt from Windows confirming enabling the display, I click ok, and the Settings UI makes it appear that the display is enabled. However clicking ok in the settings window or closing it doesn't enable the display, and going back to display settings shows the display disabled again.
Furthermore, I noticed in Windows ME one of the 2 Radeon devices in Device Manager again failed to start. The Device Status says:
Multiple Display Support cannot start this device. The area of memory normally used by video is in use by another program or device.
That seems to explain why my display isn't enabling....but IDK how to further diagnose things. It also seems interesting to me that this hardware configuration seemed to work in XP just fine. Maybe the different display drivers handle the memory overlap differently?
Anyone have insight I could use to help further troubleshoot things?
Thanks!