our companies wewre forced to put more fibre down, so at the moment quite a few of us living in built up areas can get FTTC, they dont lead it into most homes yet.. so the last 600m is covered by VDSL, which means lots of large exchange boxes around the estates with big signs saying "fibre is now available in your area" lol.
One of the smaller ISP's has a terminal right across the lane from us, you should see the rats nests hanging from the poles.
To answer the original question (doesn't seem to be necessary anymore, perhaps, but in case anyone searches this in the future) the setupapi.dev.log and setupapi.setup.log files in \Windows\INF will describe what happened when a device was detected.
thanks for the info cluberti, noted for future reference.
@Anak
its not that bad here, unless to consider bloody seagulls.. most places are planning culls as they are attacking ppl more and more especially at the moment.. while most wont consider what we are getting in the UK as a heatwave for us brits it is lol.. most of us dont have ACs in our homes so it gets pretty humid especially at the moment
so am l for the last 600m lol tho ld love a FTTH connection
well thats the limit for FTTC.. basically you have to be within 600m of the box otherwise you cant get it since lm in a built up area l live between three or so boxes which were put in over the last year or so.. others however arent so lucky on the other side of town.. they have the new fibre boxes installed but none of them have been turned on lol.
Good to see you again, noted also. One, maybe two question(s).
As the file name implies these two logs are for setup, after looking in them they go back to the initial build of the machine, in my case four years ago.
To me timeless's question implies s/he wanted to know if there is a current log showing devices including any upgraded hardware, where would a user find that log?
The logs are for device installation, from the beginning of "time" on that machine up until current. Best thing to do is to go to the bottom of the log, and search upwards the string ">>>", which is inserted every time a new device install instance is detected. It's pretty verbose, so being able to go to each step (versus scrolling the file) can help.
For reference, the log name comes from the API set used to provide setup functions to devices on Windows:
SetupAPI (Windows Drivers)
Quote
