Ah, OK. I might be wrong then. I was looking at the BBC web site which shows him with a time of 1:15.482, although there is no indication of how that time was determined.
I'm pretty sure 9th will be empty, as Hamilton got his only time deleted for jumping the chicane. Perez did manage to get a time in before his crash, which puts him ahead of Hamilton.
OK, you might need to wait for a PHP programmer to turn up, but sounds like you would need to pass the array by reference, which I believe you would do like this.
Who said delete anything? I said to re-add the LFS_External assembly to your project. The 'obj' folder is not designed to be touched by humans, that's why I think it's a configuration issue. Right-click on the project, select Add Reference and then select the LFS_External.dll file. Once that's done, recompile it.
It's impossible to know exactly what the error is, but that message says the issue is with the 'obj' folder, which makes it likely it's a configuration issue. I'd suggest re-adding the reference to LFS_External and then recompiling the project. I'm suspicious that's the issue, you just need to re-add the reference to that library.
I'd also suggest upgrading to Visual Studio 2010. It's free you know...
Because they're binary files designed to be read by programs, not by humans. You would need to write some code that reads the values, or alternatively you can open it in a hex editor.
I had thought about updating it for a while, but I couldn't be bothered. Then I realised that the free license for Reflector runs out at the end of May, so if I was going to do it I would have to do it now. The main point was to post the source for LFS_External, as once that is up anyone can change it, and I wouldn't have to worry about the license for Reflector being changed.. The changes I made took literally 30 minutes and could have been done by anyone in the last two years.
I will update InSim.NET to match the most stable release of LFS where I can. There is nothing in the current version of InSim.NET that stops you from using it with InSim 4 or 5, although there are a couple of small issues. For instance in the new patch Scawen has fixed the old BTN text bug. I could fix this in InSim.NET, but there are two reasons not to. Firstly, the old version of LFS still has the bug and fixing it would mean braking support for Z28. Secondly, it's actually easier for me to not fix it, as it would mean changing the way in which InSim.NET handles strings. This isn't laziness however, it's caution.
I normally would have no problem messing with this sort of stuff, but I've finally got to the point where the LFS string encoding is working reliably, and I'd prefer to leave it stable for a while rather than messing around with it and possibly breaking lots of new things. It will need attention at some point, as there are several issues that have built up that I would like resolve, but they all require the same bit of code to be refactored.
InSim.Send(byte, string, params object[]) became (possibly) much less efficient in a recent bug fix
InSim.NET still works around the text bug in IS_BTN (as mentioned above)
The EncodingHelper static class needs to be rewritten as an actual System.Text.Encoding derived object.
All of these issues are connected and require modification to the same piece of code, so I'm going to put it off for a while until I really feel like doing it. It's also the piece of code which has caused about 8 of the last 10 bugs in InSim.NET, so I don't really want to change it unless I have to (I'm also thinking about taking an entirely different approach to coding it).
To sum up, I will keep InSim.NET up-to-date with the most stable release of LFS, unless I have a reason not to, and that reason might not be immediately apparent. I won't break InSim.NET however.
The registry does get larger with time, of course, but this has an extremely minimal impact on performance. The reason I mentioned programs that promise to speed up your computer by cleaning the registry, is that those are the chief source of the myth that cleaning the registry improves performance. Orphaned registry keys have practically zero impact on your computer, which is one reason Windows doesn't bother to clean them up itself. I'm not saying Windows performance doesn't degrade with time, it frustratingly does, just that the registry isn't a culprate.
I'm actually saying the opposite, that these are the things that make Windows a good operating system. Every one of those little tweaks and hacks represent thousands of man-hours of testing and development. It's those little hacks that mean I can still run Planescape Torment on Windows 7. My understanding is that the code quality of Windows is actually pretty good, at least no worse than any other codebase of a similar size that's been in development for twenty years, which frankly there aren't many of. Seems to me that Windows works pretty well and they don't have problems adding new features, that's generally a good sign of a codebase's health.
I said ages ago that I'd release a quick example to show using InSim.NET in a Windows Forms application, but I never got round to it. So anyway, here is a small app that prints the contents of each MSO packet received to a text box.
You can find the VS2010 project and a screenshot below.
Yup, I accidentally made the DashLightFlags a ushort instead of a uint. That caused all the fields that follow it to be shifted up two bytes. I uploaded a fixed version.
Well, I discussed my feelings on UAC earlier on in the year in a very badly received and misunderstood thread regarding LFS+UAC (turns out most Windows users don't understand how Windows works). Fact is any issue people may have with UAC is the result of badly written programs, and not with any flaws in Windows itself. Sadly there are a lot of programs that don't understand how to play nice with Windows security and it's doubly-sadly that LFS is one of them. This is the complete failure of the programmers who write those programs. Anyway there is a very, very good argument to be made that UAC is the single best feature Microsoft have ever introduced to Windows.
Um... you do know that whole clogged up registry thing is a myth. I know a lot of people find this hard to believe, but it's true. Any program that pretends it can speed up your computer by cleaning out the registry is a scam.
But yes, Windows 7 is much more efficient. I've installed 7 on all my machines, and all of them run faster. Even the really sucky ones.