Hello, I was on an official hands-on ST32M workshop on 2013-03-07, by ST & Arrow.
a) The free edition of the Keil uVision IDE still suggests to be installed at c:\Keil.
With Win7 and Win8, it's the best to install the uVision IDE ( on 32 Bit Windows ) at C:\Program Files\Keil
b) More important, the ST-Link debugger driver shipped with the Keil uVision IDE 4.70a does not install on Win8 :-(, while it was possible to install it on Win7 ( on 32 Bit Windows 7 Pro).
Still after install, Win8 does handle the driver for the ST-Link USB device as "not properly installed" in the Win8 device manager :-(. With Win7 everything works fine...
Sincerely Rolf
Lots of development tools do not like to be installed in any path that contains spaces.
When the IDE executes a command line tool where it is required to supply a command line parameter that happens to include a space, then the IDE must quote the parameter or add a break character before the spaces. That is too often missed, making that path being seen as multiple parameters by the command-line tool.
The above is probably not related to your issues with the USB driver installation.
Win8 did not complain or rejected the installation of the ST-Link driver, it just didn´t do it!!!
Thats a difference to have problems with "unsigned drivers" !!
a) Lots of development tools INDEED have a problem with the path "C:Program Files(x86)" of 64-bit Windows :-(.
b) As "Program Files" is the standard path to install proprietary non-GNU non-Linux based software since Windows95 ( = since 1995 ),
proprietary software like Keil uVision should be able to handle this.
c) Indeed, Vista, Win7, Win8 **demand** to install software to "C:\Program Files" ( or in German "C:\Programme", as else the software is not executed properly. Especially, temporary ore writable configuration files should not be there!!!
Yet, I've been using Keil and Windows 8 with assort ST dev boards for months. Win8 silently ignores unsigned drivers.
Microsoft dating back to at least Vista has been trying to stop people installing user modifiable content under Program Files, it's a single directory visible to all users. Having the examples under Program Files is a problem, and why most anyone doing this kind of install uses \Keil or \IARSystems or \Atollic to explicitly avoid this mess, and not have Windows make virtual links to \User directories for things under \Program Files.
I have the Keil tools under c:\keil\
Most other tools gets installed in subdirectories under c:\bin\
And I keep lots of documents under c:\doc\ instead of merging them into the M$-defined messy "My Documents"
Micro$oft have somewhere down the line made the decision that we don't own our computers and have to be protected from ourselves.
"Win8 silently ignores unsigned drivers" Thanks for the info :-), though it's a bad info :-(, but you know
The good, the bad, the ugly - Linux, Windows, DOS :-).
Don't you meain "Linux, DOS, Windows"?
Both Linux and DOS agrees that you are the rightful owner of your computer, and allowed to configure it and make use of it as you feel best suits your needs.
No, I think he was right with "Linux, Windows DOS"; ie,
Good = Linux;
Bad = Windows;
Ugly = DOS - so it's ugly, but not bad.
and allowed to configure it and make use of it as you feel best suits your needs.
you, yourself, do not know what you want, be happy someone in Redmond does.
Erik
Indeed, Vista, Win7, Win8 **demand** to install software to "C:\Program Files" ( or in German "C:\Programme",
No, they don't. At most they suggest you put stuff there (by making it the default where stuff ends up if you don't choose otherwise). And then they actually lie to you, because the real place the stuff ends up is neither "Programme" (because as of Win7, that is an illusion anyway), nor "Program Files" --- not for 32-bit programs in 64-bit Windows system, anyway.
as else the software is not executed properly.
Nonsense. They want you to believe that there's something special about that directory, but it's really all a big load of BS.