Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

  • Days Won


Radish last won the day on September 10 2018

Radish had the most liked content!

Community Reputation

12 Good

About Radish

Profile Information

  • OS
    Windows 7 x64
  • Country

Recent Profile Visitors

1,626 profile views
  1. Radish

    Update Win 7, or Not ?

    erpdude8, that article ends with the paragraph: Which to me seems presumptuous with its, "everyone would have to upgrade to Windows 10", why 'have to'? aren't there other options?, and Win10 is a downgrade, and "It's just a matter of time anyway." If ever I'm forced off Win7 then I've got Win8.1 as my next OS, for a while. If I ever get pushed off that then I'll go back to Linux Mint and to hell with Microsoft. I would never in a million years install Win10 or any upstream derivatives thereof. Of course there is the outlier of ReactOS but when, if ever, that will be stable and usable is anyone's guess at this point in time. But if the drip, drip, drip of its development continues then eventually it will fill the tub.
  2. Radish

    Update Win 7, or Not ?

    Yes, this is so. The propaganda worked on me for a couple of years many years ago then I recognised it for what it was, a heap of sh*t. Yup, mostly propaganda too. It's like they say about the paid-for anti-virus vendors, "If viruses didn't exist they'd be coding them themselves." I do often think that Microsoft are in the same position when it comes to updates - code in something naff somewhere then somewhere down the line release a 'fix'. Keep the masses thinking they need to be suckling at the teat - tripe! Only thing about Microsoft that isn't propaganda is that they're after your data, and at that, big-time now! Strongest case for not updating I know of - to Hell with them! Punting Spyware Suites and calling them Operating Systems. Of course with Win10 you get the Suite even if you don't update. It's a malignant joke. "It's just telemetry." "'Telemetry', what!" They think our heads zip up the back.
  3. To reply to my own question in case anyone has use for the information. 1) Made an image of the boot partition of the SSD - TRIM was enabled on this. 2) Using that image, restored it to the boot partition of an HDD. 3) Boot into the HDD and check TRIM setting - it was still enabled, so Win7 doesn't seem to auto-disable TRIM on an HDD. 4) Changed the TRIM setting on the HDD to disabled. HDD seemed to have survived all this fine. 5) In all, turns out safe to use an SSD image to restore to an HDD system. My computing-life just got very simplified by knowing that. All done! (Interesting. This was the first time I'd used an HDD for about a year and half - have been exclusively using SSD system. Boy the experience really showed up just how slow an HDD is. Wow! And that's with a motherboard that is SATA 2, not SATA 3, so I don't get the full speed benefit of an SSD. Nonetheless, still Wow!)
  4. Kind of puzzling over this today. What is an "Upvote" for? What is it meant to indicate? Also what is a "Like" for? What is it meant to indicate? And what is the difference between the two? How are users meant to use them?
  5. Radish

    Weird "Item Not Found" Error

    Don't know the solution myself but found this post elsewhere that suggests a couple of ways of a potential fix that folks say worked for them: https://superuser.com/questions/620238/could-not-find-this-item-every-time-when-renaming-moving-copying-win-7-expl/683995 If it was me and I was going to edit the registry I'd save off any keys I was going to edit/delete before trying the registry hack. That way can get back to base if something goes wrong. That said, if it was me, I'd try booting in Safe Mode and see if the problem still occurs while in Safe Mode. I think I'd try that before doing anything else.
  6. Radish

    No E-Mail Notifications?

    Mmm . . . I'm kind of totally confused on that issue too I guess. I have so many problems with email notifications from this forum, which make it difficult to actually try and judge what is going on. Really should be 'Sticky' notice/thread somewhere that explains what is happening in this respect. Or even a statement at a user's profile 'Notifications Settings' -- probably the best place to put such a notice, no one can miss it that way. Should add, got another email for your response directly above. Hope that holds up.
  7. Radish

    No E-Mail Notifications?

    Well I just got an email informing me of your response in this thread, Dave. Yippee! Hopefully some fixer in the background has fixed things for me. Wait and see I suppose. On the subject of only getting one email per-last-time-you-visited I'm not a big fan of that scheme. Keep things simple, you're subscribed to a thread send, an email on every post. There are enough options available in notifications to do otherwise. Or just make one email per-last-time-you-visited a yes/no option in it's own right. Anyway I hope my issue on not getting emails at all is fixed now.
  8. Radish

    No E-Mail Notifications?

    I'm in the same boat, no email notifications to threads that I follow. I've tried disabling notifications, saving that setting, then resetting it to allow notifications. Doesn't seem to be working for me. Is there anything that an admin at MSFN can do to help stop this happening?
  9. Radish

    Update Win 7, or Not ?

    Have another piece of interesting information on installing KB3033929 as follows: Cutting a long story short I had occasion to go into Windows Event Viewer (never really go there) and look at some of the Windows logs in there. In the Application section I discovered masses of errors labelled CAP12, Event ID 4107. There were lots. The General (description) information for these events was: Unbeknowns to me, these errors were occurring from the time I had fresh installed Win7 Pro. SP1 up to early this month (September), then they just stopped happening. Kind of scratching my head over that so looking for a solution to the puzzle had a look at the Setup log and lo and behold the 4107 errors stopped after I had installed KB3033929. So it would seem that (again) the 4107 errors were being generated because Win7 Pro. SP1, with no other updates installed, couldn't read the certificate properly, because it lacked the capacity to manage SHA-256 hashes, and then misreported what the error was via the 4107 error description. I'm kind of guessing this but it seems to me it very much looks that way. Different subject, but for what it's worth for folks trying to run Win 7 SP1 without updating it unless essential. In the Application logs I also found lots of errors labelled WMI, Event ID 10. They had the General description: After a bit of research found this webpage: Event ID 10 is logged in the Application log after you install Service Pack 1 for Windows 7 Seems this is common problem for some installs of Win 7 SP1. I created and ran the script mentioned on that webpage and the errors were no longer generated on every boot into Windows. So I thought this might be useful information to post into this thread. As a result of finding all this out I've now become converted to at least viewing what is going on in Event Viewer logs and have even setup, via Event Viewer, Scheduled Tasks to automatically inform if any of these errors recur (not that I'm expecting them to, they pretty well seem fixed). Hope this helps.
  10. Thanks very much for the responses. I'll take that it is safe enough to try my experiment and see how restoring a HDD boot partition from an SSD boot partition image goes. Didn't want to do it without at least trying to find out if the system would trash the HDD in some way on first attempted boot-up because TRIM was enabled. Searched the web for this information, nowhere to be found.
  11. I'm kind of at an in-between stage in that I have my day to day working system, Win7 x64 SP1, installed to a SSD. However, I have a backup Win7 x64 SP1 system installed to a HDD. My thinking is that if the SSD ever goes bang! then I can just switch to the old HDD and be up and running again very quickly. I have been making separate boot partition images of these systems for restore purposes if I corrupt them. However, as I update the working system, which is on SSD, then I've been manually replicating that on the HDD. This means that (so far) I have been keeping two sets of separate image files. One image for the SSD, the other image for the HDD. Today I was looking at my notes for the SSD system and thinking that that system would work just as well on a HDD -- so I could eliminate keeping two sets of images for systems that are in essence the same system. I would also be freed of replicating the SSD system over onto the HDD. The only flaw I can see in this is that the for the SSD system I need TRIM enabled. So now I'm wondering if enabling TRIM on a HDD system would cause any problems for that system? Or would the HDD operate just fine even with TRIM enabled? I'm even wondering, if I restored the system on the HDD from an image of the SSD system would Windows 7 immediately recognise that TRIM isn't necessary on the HDD and, hence, automatically disable it on first boot into the HDD system?
  12. Radish

    Update Win 7, or Not ?

    Big thank you from me too, erpdude8. Will follow your advice. (Have now put a correction in my original post on this matter.) Thanks again. (Now I have to try work out why I don't receive email updates to new posts in this thread. Argh!!!!!!)
  13. Radish

    Update Win 7, or Not ?

    Well, I'm going to, not so much "eat my hat" but at least have a little nibble at its edges. I just came across a situation in which in the space of a few days I tried installing and using two new programs and Win7 SP1 told me that the drivers the programs were trying to install weren't digitally signed -- so Win7 wasn't going to let the programs install them. I went off and did some research and found out that the drivers the programs were trying to install were signed but using SHA-256 signatures. And, it seems, Win7 x86/x64 at SP1 level, and with no other updates installed, can't read the signatures. Cutting a long story short the solution was install the following updates (and in the following order): KB3035131 (download can be accessed via here) https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2015/ms15-025 KB3033929 (download can be accessed via here): https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929 So, Taos, or anyone else that is reading/following this thread and trying not to update their Win7 SP1 system unless really necessary, it would seem that these two updates are moving into the necessary stage as more and more software developers will move towards digital signing using SHA-256. So, going by my experience, I'd recommend installing those two. Now I'm thinking that it would be a useful addition to this "Windows 7" section of the forum if there was a kind of 'sticky' thread where people using Win7 SP1 that are trying to avoid updating it, if possible, could post information on updates that, over time, they've found are necessary but that avoid Microsoft spyware and other suspect stuff. Of course, don't just say, "Install KBxxxxxxx," say why it's pretty well essential to do so too. Hope this helps. Important Edit: erpdude8 has posted a correction to this post (see erpdude8's post below). Do not install KB3035131 -- it is obsolete. Instead install KB3071756 -- again see erpdude8's comments below with a link to the update.
  14. Ops! Sorry, jaclaz. Getting older and bit befuddled now and then. Link is in the post now.
  15. Thanks for the responses. Apart from my own musings on this I found this webpage on the advisability/inadvisability of partitioning an SSD. There is one poster there, "Community", that writes quite extensively on how SSDs deal with data on the SSD. (Community's post starts with the first paragraph, "SSDs do not, I repeat, do NOT work at the filesystem level!") Reading it blew all my own thoughts on how SSDs must work out of the water -- if he is right. Problem is I don't have the technical expertise to decide if he is right or wrong. Very interesting read though. If Community is right then, by my reading, on an SSD you can partition as freely as you please or not partition as freely as you please; it makes no difference how the SSD handles wear levelling. I was just wondering if any folks on this forum had any thoughts on this.