Hello there, I purchased a Zepto 6214W in January. I've had the heat problems described in many other topics, done various surgeries and had it in for repairs once without luck. Awaiting sending it in another time since my games still overheat.
However, that aside, this is the new problem that's boggling my mind: I can't make the P1 and P2 buttons on my keyboard work. I know Zepto released a program called QLButton which purpose is to let you configure these buttons. However, when I try to start the program (tried both versions, one from CD and the one from the Zepto FTP) a big load of nothing happens. I get the Windows "thinking" cursor (hourglass) for a split second then it disappears and I'm left with nothing, wondering what on earth just happened. I've checked the system-tray for any icon and the Task Manager to see whether the process is running at all, which it's not. This has been an issue since the first day I tried it (same day I received the rig). I had this AHA! feeling today as I looked through my software and I realized I had replaced my .NET Framework from 1.1 to 2.0 and thought it might have caused the issue. I tried reinstalling 1.1, but to no avail. Same problem.
Anybody with the same problem around? Solutions for this problem? Experiences? All is received by me.I'm burnt on this case.
Thanks much,
Eirik Rye - Not-so-happy Zepto customer.
EDIT: Yeah, gotta add. I'm on Windows XP, not Vista.![]()
-
Have you tried uninstalling and then installing again? Although God knows I've had my share of problems with my 6615 the Quicklaunch program worked just fine. (I've only used it under XP with all updates, not Vista).
Are you sure that Framework 1.1 has been replaced by 2.0 or has 2.0 been added? This might be a/the problem.
Oops, did I give the impression that my problems are over? Nope, not true, waiting for a new motherboard after a BIOS upgrade wrecked my Lancard. -
When I installed the .NET Framework 2.0 a good while ago I also uninstalled the old one thinking I wouldn't need 1.1 when I have 2.0. However I have now tried with both installed, and only 1.1 and only 2.0. In fact, I don't even have a slightest clue whether my problem is with the .NET Framework at all. I've tried reinstalling a couple times and I do still have the same problem.
Thanks.
EDIT: Make note I hadn't make any of these changes the first time I attempted to use QLButton. I do think now the problem lies elsewhere. Seems weird to me that I'm the only person experiencing the problem though. -
Bump. (10)
QLButton problem? (6214W)
Discussion in 'Other Manufacturers' started by eirik.rye, Jun 4, 2007.