#Windows xp service pack 4 3.1b update#The issue (JFYI) is about the (stupid) update to the IPB software, NOT any change in MSFN policies/accounts/whatever. Well, whining is already something frowned upon, but whining about the wrong issue is even worse (you are barking up the wrong tree). (Not meaning to host the files, just providing the instructions and links as you do here.) Of course going that route finding a server host that isn't a copyright wuss might be a problem.haps a note is in order explaining the discrepancy. Kurt, you may have to suck it up and launch your own site for these projects. Not many other forums have that capability/feature and many that do are so afraid of copyright issues (without actually understanding them) that they simply won't let you post something like this there. (Not meaning to host the files, just providing the instructions and links as you do here.) Of course going that route finding a server host that isn't a copyright wuss might be a problem. Such permissions would obviously need to be handed out on a one-on-one basis after a review of the project, but that shouldn't be THAT much of a burden to the "powers that be" given the vast improvement in the quality of the content here. MSFN staff should consider creating a limited Admin type of account that allows the authors of such projects to edit (just their own) project threads. If that is no longer possible here then MSFN content will largely be dated and obsolete projects and MSFN will soon no longer be such a valuable asset. MANY Member Contributed Projects here on MSFN -RELY- (or did) on the ability to keep the first post updated and current. In a way of thinking MSFN has deliberately "obsoleted itself" for the very thing that made them unique and valuable. ![]() And IMHO horribly short sighted of MSFN's "powers that be". #Windows xp service pack 4 3.1b software#Unfortunately however due to changes in 's forum software it is no longer possible for me to update or maintain complex forum posts like the main guide in this topic. #Windows xp service pack 4 3.1b archive#Not what you Might wanna archive the full installers while they can still be found at all. "GoogleEarthSetup.exe" is the web installer. You can see the correct file names in the links. ![]() It is apparently only *not* present for newest file in each major version. #Windows xp service pack 4 3.1b install#full install file based on what the link to 7. Then I -guessed- what the link would be to 7. I found the direct links to some full installers on this page. So, I poked around on Google Earth's site. (Like most web-installers it doesn't tell you anything useful about what it's doing.) full installer actually went to the general online-installer file (usually on Google Earth's server) which presumably DL's the latest version only. The oldest 7.x.x.xxxx sequence "old version" available on Google Earth's site is newer than 7.Īnything I found on the web that appeared to be a link to a version 7. available, but that could go *poof* any day now. If you fiddle around you can still find version 6. using either of the first two links you give. There is no longer any way to get to version 7. Regarding line = ''Google Earth use version 7. After about 750Mb I had to restart it repeatedly (every 25-50 Mb or so) to get the complete file. I finally got the Google Drive to work from Ryan's page. ![]() The only way I found that worked for me to get SP4 v3.1b is to use the magnet link in Ryan's page. (They start downloading but never finish. The link in Ryan's page to the Google Drive works but once there the DL's didn't work for me. The current (and supposedly last) version is 3.1b. SP4 v3.1a has been obsolete since at least April 2016, if not before.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |