Export thread

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

Steve calls out Microsoft...

#1

stinkweed

stinkweed

BRAVO STEVE! ...as a long time Spinrite user, and a faithful Security Now viewer, I loved your recent Security Now comments about Microsoft's ongoing negligent handling, and continued failures, to correct & promptly update software security issues affecting ALL users of their Microsoft Windows operating system(s). Computers, and the internet, have provided the world with amazing opportunities to benefit the world's population, and unfortunately, also greatly enabled opportunities for global crime, political surveillance & control, etc., etc. Microsoft Corporation, with it's Microsoft Windows operating system being a current dominant global computer operating system, needs to step up and use it's vast financial resources to continually provide, and maintain, a safe and secure computer operating system for the entire global computer community!


#2

Barry Wallis

Barry Wallis

Microsoft Windows operating system being the current dominant global computer operating system
Not true. As of last year, there were 2.5 billion active Android devices (https://www.theverge.com/2019/5/7/1...ces-play-store-total-number-statistic-keynote) vs. 1.3 billion Windows devices (https://news.microsoft.com/bythenumbers/en/windowsdevices).


#3

Lob

Lob

While it might be possible to agree with @Steve in some ways, maybe the 25-year-old crap in some parts of Windows is actually very difficult to remediate without breaking something else. Clearly there were design decisions made many years ago when there was little Internet and mostly single-user mode that have lead to this situation.

There are always two sides to a coin and it might not be just a case of throwing money and resources at it.....


#4

C

cyberzod

Another thought, Microsoft Corporation as a whole does not have to be in bed with NSA/CIA/FBI/etc. There could be just a few well-placed developers or program managers in a company that size that are, perhaps, living lifestyles beyond their apparent means with ties to some handler that nudges rather than directs their activities. The type of neglect we are seeing could be a combination of old code developed before the advent of a focus on security and just a little influence near the ground level to rush or delay a project.
I think the best point made by Steve was that the incredible complexity of Windows makes it impossible for one person to fully comprehend. Sadly, it appears that the Linux community is re-implementing that level of complexity on what was once a pretty simple platform. (Yes, sssd, polkit, udevd, pulse-audio and systemd, I'm looking at you.) As we have all seen, complexity is the enemy of security.