Hi everyone. I haven't been on in a while, but I have still been experiencing problems with my m15x. If I weren't good with computers I don't know how I would be using this thing right now. Quick list to update those new to my troubles: (For those of you who know the story already or just aren't in the mood to listen to me bitch...(im not sure if im allowed to say that...if i've offended anyone, I apologize) please scroll down to where it says TOPIC SUBJECT preceded by a swimmingly fitting blue smiley face scratching its head in confusion.
HDD Failed "we think"
Recovery Disc was a dud
On Keyboard #3 right now (1 the lights didn't work properly 2 the response was way off and 3 seems to be working)
Upon receiving the computer, my volume was turned all the way up. Thought it was just a mistake by one of the techs. Heard cracking about two weeks after and now I am down to one lonesome left speaker which is on its way out.
Touch capacitive buttons froze for a day (had to call tech support in the mall!)
SUBJECT TOPIC: I have been having a strange problem with the command center software as of late. By default when my m15x starts up, the only light that should be on is the wireless indicator. However, lately the UFO button decides it too wants to turn on before I even log into vista. Then when I get into vista, I try touching the button and it is unresponsive and when the command finally does go through the computer replies with something like the command center software is already running.
I have tried EVERYTHING! I have uninstalled and reinstalled OSD and Command Center dozens of times. I have tried playing with the msconfig. I have even tried deleting registry keys. I am about to try installing with XP SP 2 compatibility because 1: I care more about the light acting properly then I do about Fusion which, if we get honest with ourselves, is just windows power options with a really cool looking alienware them applied to something we can find in the control panel. However, I doubt its going to work.
I think the problem started with installing the nero software that CAME WITH THE COMPUTER and which is now incompatible with vista. As such, windows directs you to nero's site to download a "free" 30 day trial of nero 8. AW doesn't want to spring for version 8 and so a tech told me to install with xp sp 2 compatibility.
I then, a couple of days later, installed a few other legacy apps that came with the mass spectrometer I am using at my internship that were designed for windows NT or windows 2000. This is around the time I started to notice the UFO button problem. It is driving me crazy because I know its not the correct behavior. The DRIVERS should and coincidentally ARE running at startup, yet they have somehow become linked to the command center button. As such, when they run at startup, so does my command center button.
I realize this is an obscure question that probably no one else has experienced (basically because I own a lemon and everything that can go wrong is going wrong)...but if there is anyone out there that thinks they can help me out, I would be so grateful.
I feel like there should be a way to toggle the behavior of the buttons through the registry or opening a file in notepad and changing a 1 to a 0 but obviously from judging by what I just said, I don't know anything about programming. Thanks for listening and thanks for any help. You guys are usually awesome in these forums.
Shawn
HDD Failed "we think"
Recovery Disc was a dud
On Keyboard #3 right now (1 the lights didn't work properly 2 the response was way off and 3 seems to be working)
Upon receiving the computer, my volume was turned all the way up. Thought it was just a mistake by one of the techs. Heard cracking about two weeks after and now I am down to one lonesome left speaker which is on its way out.
Touch capacitive buttons froze for a day (had to call tech support in the mall!)
SUBJECT TOPIC: I have been having a strange problem with the command center software as of late. By default when my m15x starts up, the only light that should be on is the wireless indicator. However, lately the UFO button decides it too wants to turn on before I even log into vista. Then when I get into vista, I try touching the button and it is unresponsive and when the command finally does go through the computer replies with something like the command center software is already running.I have tried EVERYTHING! I have uninstalled and reinstalled OSD and Command Center dozens of times. I have tried playing with the msconfig. I have even tried deleting registry keys. I am about to try installing with XP SP 2 compatibility because 1: I care more about the light acting properly then I do about Fusion which, if we get honest with ourselves, is just windows power options with a really cool looking alienware them applied to something we can find in the control panel. However, I doubt its going to work.
I think the problem started with installing the nero software that CAME WITH THE COMPUTER and which is now incompatible with vista. As such, windows directs you to nero's site to download a "free" 30 day trial of nero 8. AW doesn't want to spring for version 8 and so a tech told me to install with xp sp 2 compatibility.
I then, a couple of days later, installed a few other legacy apps that came with the mass spectrometer I am using at my internship that were designed for windows NT or windows 2000. This is around the time I started to notice the UFO button problem. It is driving me crazy because I know its not the correct behavior. The DRIVERS should and coincidentally ARE running at startup, yet they have somehow become linked to the command center button. As such, when they run at startup, so does my command center button.
I realize this is an obscure question that probably no one else has experienced (basically because I own a lemon and everything that can go wrong is going wrong)...but if there is anyone out there that thinks they can help me out, I would be so grateful.
I feel like there should be a way to toggle the behavior of the buttons through the registry or opening a file in notepad and changing a 1 to a 0 but obviously from judging by what I just said, I don't know anything about programming. Thanks for listening and thanks for any help. You guys are usually awesome in these forums.
Shawn
