Sager np9380 Hotkey driver problems (.NET Mainframe)

Hello all,
Just a question about the Hotkey drivers.

The problem I`m having is with the Hotkey drivers which turns the keyboard backlight to different colors, is not working, I have no function of Hotkeys whatsoever apart from volume and screen brightness. the Hotkey driver currently installed is v7.0026 Every time i start the computer I get this error message from Microsoft .NET Framework; see atachment. Currently Microsoft .NET Framework 4.5 is currrently installed, i did also try Framework 4.0 but that came up with the same error.
All other drivers are currently up to date.

Just wondering if anyone can help me out with this as i have the laptop for more than a week now. I already asked xoticpc`s customer service desk, but their service is absolutely terrible, it takes them forever to respond, just a nightmare to deal with.

Any help with this would be brilliant. Thanks.

 

Hi, I'm having the exact same problem, same exact error message about the input string not being in the correct format. I'm on a sager np 8265 (which I also only got a few days ago), and have already tried xpc (where I bought it) and the sager support call service. The strange the is that the backlit keyboard DOES work (it's blue as I type this).

I have windows 7 pro 64 bit installed and the exact same .net framework 4-4.5 drivers installed.

A few things I've noticed. Upon install, after the error, it shows the hotkey symbol with the little laptop with the red circle with the cross through it and only the volume and brightness keys work but if you hover your mouse over the icon in the taskbar (with windows aero enabled), you can see a minimized version of the hotkey command center (what SHOULD be maximized), of course, you can't maximize it.

I really want to get this resolved.

 

Yes this exactly, it`s exactly as you stated in your message.
I have tried different installs uninstalls but the problem is not with .NET, it is the code in Sagers Hotkey drivers. I have no idea why they would put out buggy code??
I have been emailing exoticpc still, and they barely even reply just stating to install and re-install the .NET software but the problem is with the Hotkey code?? I honestly don`t think they know what they are talking about tbh.
Sager recently updated the Hotkey driver to v.7.0026, but I`m still getting the same problem.

If you find a fix for this problem,I would greatly appreciate telling me about it.

 

I found the FIX I found the FIX yay!!!!
First ignore the .net corruption error BS, this is entirely sagers problem not ours.


Hi again Kaiah or whoever else has this problem I found what looks to be an almost 95% fix (I'll explain the missing 5%). Basically, the new sager drivers are crap, they only work for some, BUT, after trying out some older drivers I FINALLY found a stable driver that actually lets you use the freaking hotkey backlight color changer!! (Success ). Anyhow, the one issue with it (the lost 5%), is that the power key to the backlight still doesn't work. I mean, the key itself works but the only way to completely shut off the backlight is if you turn off the color in the backlight color changer. Also, the keyboard dimmer works (to use, tap don't hold until satisfied--if you want you can turn off the backlight via that method but it still takes time....) Oh and all the other hotkeys work .

I uploaded the 6.01 version that worked for me to dropbox so help yourself.

FILE: https://www.dropbox.com/s/fw0fvnqs9vsa7t1/06_Hotkey_9370.exe

Edit: Note, make absolutely sure all traces of the old (technically new) hotkey driver are gone, use Ccleaner and clean the registry and also delete the hotkey folder from programs. Then, instead of clicking the auto restart upon install, shut down the whole laptop. Wait a sec, then reboot. This is the only foolproof way. This time, the program should work as soon as windows loads however for a split second there may be the laptop error symbol, BUT Then everything will work I'm so happy, now I can turn my backlight to white instead of blue .

One last thing (part of the 5% I guess), you have to change your backlight to your personalized settings every time you come out of sleep mode or reboot--because otherwise it will stay the default blue).

 

Hrrrm.....well, I know I said it was stable...and it DOES work, but it occasionally does still get the .net framework error after all, but just ignore it and click OK if ever prompted, it will still work.

 

Hi , thanks for that, i was playing with that yesterday, yes you do have some control-ability with it, but its not good enough imo.

Xoticpc is now just ignoring my emails, so they are the worst.
I bet they're all like; he paid $3000 on a laptop and he thinks he will be able to customize his keyboard, ha. ha. haha. hahahaha . Should have got Alienware.

 

Guys, I believe v7 hotkey is for win8 only and v6's for win7. Probably where all your issues with .net came from.

Also lights and what not for the keyboard is limited by the BIOS/EC, which is in clevos hands and unfortunately xoticpc will not be able to help out config wise as they do not write BIOS's for clevo.

 

SUCCESS!!! I figured it out for real this time--consider this the final fix.

First, Kingyr, I don't mean to be rude but you're wrong about the v7 drivers, they ARE for windows 7, the v8 drivers are for windows 8. Anyhow, Kaiah, crucial question, one which I had only considered on a whim but which I finally tested. After you completed the initial install of the 7.0026 driver and you were prompted with a restart later or restart now which did you choose? Because, for the longest time I had just been clicking the restart now prompt--BIG MISTAKE. For whatever the heck reason, sager computers need a complete system shut-down restart for the hotkey driver to be fully installed or it will screw up. That's right, instead of clicking the restart now option, choose restart later, then, from the start menu, click shutdown MANUALLY. Do not hold the power button. Once COMPLETELY off, THEN and only then press the power button to restart. You should now be presented with complete and total hotkey v7.0026 functionality, including (for me at least), the option to simply shutoff the backlit keyboard all together.

If you want more functionality than all it offers to begin with you may have to buy a non-stock keyboard from steel series and do a manual upgrade. Anyhow, hope this helps you like it did me.

 

For some reason my v7 Hotkey Driver is also affected by the video driver. The last time I did a fresh install of Windows, I installed the Hotkey one first, then shutdown the the laptop and turned it back on after a while. The KB Light would turn off by itself after logging into Windows. Everything with the Hotkey worked except for the KB Light. I then installed the 780m Driver and after shutting down and powering back up, it started working.

I've always had to uninstall the Hotkey Driver when I have to uninstall and reinstall the video driver to get it to work for some reason. However, I never got any of these .net errors.

 

Hey man, all good - You are right though, v8 is for Win8 (my bad). I always thought last hotkey version from clevo was 6.0100, then next ver was for win8. Glad you got it sorted.

 

Hi Cozndawz144, I`m just after trying what you stated but the problem is still the same? I get the same error again on start-up?
Although this is the first time I opted for the "restart later" option button.
Can you tell me what version of .NET you have installed please?

 

I have microsoft .NET framework 4.5 and chart controls for .NET framework 3.5 but you probably already have that. The real question is, do you honestly have EVERY microsoft update installed? I mean every single important and recommended update ixcluding internet explorer 9 (the newest is 10)? Also, are you on win7 service pack 1? Cus, I called sager and they don't officially support win7 1.0. If you haven't downloaded it that might be partially the issue.

I really think now though that what you have is a driver issue cus I had the exact same error lines (I went through all of yours and mine again to be sure.) Luckily this means a fix IS possible .

My best advice for you. Install Every windows update possible (inc. SP1) and THEN do as I stated.

Hope this helps!