Matrix Orbital Corp

I just got back from a short deployment and went to turn my computer on and my screen on my mx4 is now corrupted on startup and windows detects it as an unknown device and declares it working properly which it obviously isn't. If I try to manually install the drivers, after clicking have disk and pointing it at the new 1.4 driver directory it just says that the directory doesn't contain any information about my device. I'm running xp pro (32bit) sp2, athlon64 3200, a8n-sli delux, usb keyboard/mouse (both are working), usb thumbdrive (working), usb rio (working). I've tried:
-a simple uninstall/scan for hardware changes in device manager
-plugging it into different usb ports
-powering the system up with it unplugged
-resetting the system bios with the psu unplugged for a few hours
-tried removing all keys containing "mx4", "unknown device","ftdibus" and "ftser2k" from the registry as well as all system files assosiated with MO.

The GPO still powers my fans but at the default startup speed I set of 30% so I can't really do anything stressful on my machine which sucks. I'm at a loss here, the last time I saw it working was when I set my machine up back home after returning from quakecon then I left the next day. My machines were unplugged the entire time. I was wondering if maybe the displays had an eeprom type controller or bios that's suseptable to being corrupted?

Hi wiperblades,

Can you try removing the USB hub, and try plugging in just the display. I want to eliminate other devices. You will also want to try testing the unit on another pc, to eliminate the problem to be the pc or the display.

The problem isn't a corrupt eeprom. The eeprom is external to the controller, and it is used for saving settings like the start screen or contrast. If it is a hardware issue, the problem would most likely be part of the communications circuit.

Let me know what the results are.

Best Regards,

Thanks for the reply, sorry for the delayed answer, went to sea again monday morning. The problem has become intermitent now but I'm not sure why. When I first posted here it wouldn't detect at all, now sometimes it detects it just fine, sometimes it assigns it a new com port and I have to go into lcdc and reconfigure and sometimes it's an unknown device again. I've tried it on my other machine with the same results. It's wierd that it just started doing this for no reason after 1.5 months of being powered off.

wiperblades,

Can you email me at support@matrixorbital.ca to discuss some RMA options.

Best Regards,