|
Done all that. T?he workaround that I found on Belkin support site has shown that the driver is active.
Hopefully Belkin will get after it before they start getting more complaints as others continue to upgrade from 8 to 8.1
|
|
|
|
|
Do you still have the link to the work around I would like to look into it.
|
|
|
|
|
|
These files downloaded do not apear to be as new as they make out by the date on the download page.
One file Svlscapi.dll which appears to be a service controler is not digitly signed.
Then Sxuptp.sys located in sx-virtual_link_win_3120\s-33a3120\Files\Bin\Sxcsapi\WinVistaX64
When trying to view the imports thru a EXE viewer it outputs jibberish it may possibly be corrupted or protected in some way. But this one does have a digital signature.
it is supposed to run as a (Kernal)service. SXUPTP Driver.
you might check and see if that service is disabled as well.
I have a few in house tools for listing some info about drivers and services if you want them.
Just send an email, not sure if they will help or not.
|
|
|
|
|
Last I heard, the definition of "correctly" was not "works with every OS in the world except Win 'ate".
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I've had hardware, including some from otherwise reputable companies, that appeared to work only by chance. In one case, it worked only with Windows 98. (I currently have a USB gaming device which worked great on Win98 and kindof worked on XP [XP popped up errors that it wasn't recognized, but it still worked for some reason], haven't tried it on Windows 7. I should.)
|
|
|
|
|
This[^] cameraman certainly has that.
Be excellent to each other. And... PARTY ON, DUDES!
Abraham Lincoln
|
|
|
|
|
It's not like he had much choice.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
True, but he continues to shoot during and after the crash, then he checks on his mates and goes back to his camera.
I would possibly have gone for a change of clothes instead.
Be excellent to each other. And... PARTY ON, DUDES!
Abraham Lincoln
|
|
|
|
|
So now that a few of the die hards have probably been running with VS2013 for a while now and have been running the final release since it became available last week, is it in you opinion safe to uninstall VS2012?
Or is there something fundamentally broken that says "no hang onto VS2012 that bit longer"?
(I'm talking about PRO versions if that makes any difference).
Cheers,
|
|
|
|
|
No matter what versions of VS I've used, be it Express or Ultimate I've had nothing but problems trying to uninstall Visual Studio/other stuff it installs.
When I upgraded to VS2012 I did a fresh intall of Windows 7 just so I didn't run into the problems you hear about from having two versions installed.
.-.
|o,o|
,| _\=/_ .-""-.
||/_/_\_\ /[] _ _\
|_/|(_)|\\ _|_o_LII|_
\._. |\_/|"` |_| ==== |_|
|_|_| ||" || ||
|-|-| ||LI o ||
|_|_| ||'----'||
/_/ \_\ /__| |__\
|
|
|
|
|
My problem with that approach is I can never remember which order to install VS and SQL in - and I know that when I get it wrong, it mucks everything up and I have to start again...
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
OriginalGriff wrote: order to install VS and SQL
I'd like to have a separate box for the database server and keep them off my development system entirely. Maybe some day.
|
|
|
|
|
I've just been reading about 'what's new in VS2013'. The only thing that caught my imagination is edit-and-continue in 64 bit.
Is it worth upgrading?
Regards,
Rob Philpott.
|
|
|
|
|
I really like the delegating constructors and default template arguments. The variadic templates may come in useful. Apparently there are some speed improvements; hopefully intellisense is one of them.
|
|
|
|
|
Joe Woodbury wrote: hopefully intellisense is one of them Microsoft has been promising improvements in Intellisense for C++ developers since Visual C++ 6.0. I haven't seen any yet from the lying f***s.
Software Zen: delete this;
|
|
|
|
|
|
Unless you need HD space, I don't see the point of removing older versions of VS; they all are supposed to work side-by-side.
If you really want to remove it, wait for all your testing confirms that there are no issues with new build with VS2013 (unit test, ... )
I'd rather be phishing!
|
|
|
|
|
Yes, uninstall VS2012 and go back to VS2010, you'll be a lot happier.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Right what I did!
|
|
|
|
|
Oh no. I was happy going up to VS2012!
|
|
|
|
|
Since I have dated projects, I keep all Visual Studio versions back to 2008. Though, if I buy an SSD and do an OS reinstall, I'll just put on VS 2013.
|
|
|
|
|
Nothing is ever really uninstalled. Don't bother trying.
|
|
|
|
|
Nothing's ever fully installed, either. There's always something you haven't got.
|
|
|
|
|
Why uninstall it. I have all 2005-2008-2010-2012-2013 installed on same machine side-by-side.
I think you have to ask yourself "should I install 2013?", in first place.
2013 has very few new things (for sure it's not a new version worth a whole number).
I found two features useful:
1. Inline editing of referenced type (if it's in your code) - it nice but not a must have
2. 64 bit edit and continue (which is only good if you in win development)
After playing around with it an reading about it I can tell you two main differences:
1. If you want the new framework you must have a new VS (it's not new, we saw it at every VS-.NET version)
2. MSBuild no more part of .NET framework (so the only way to build is use VS!)
I have 20 years of experience with Microsoft - and the last 3 years I'm concerned about the way...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
|
|
|
|