Replies

OscarCP wrote:

Does it have a version for the Mac as well?

No, according to the Tracker Software web site it’s for Windows only.

-windows7forever

@geekdom –

I have used the free version of PDF-Xchange Viewer for years and it supports filling in form fields.

The Viewer (which is still available on the Tracker Software web site, although no longer being developed) has been replaced by the PDF-Xchange Editor. I believe its free version also supports filling in form fields.

These are the best Adobe Reader replacements that I have found, with tons of features not available in Adobe Reader or other replacements.

windows7forever

3 users thanked author for this post.

geekdom, Microfix, Elly

Update

@Elly Thanks for your PM that my post was caught in the spam filter and thank you for unspamming it.

@Kirsty Thanks for posting the link to the post which @Elly unspanned.

1 user thanked author for this post.

Elly

@NightOwl-

Just Lurking wrote:

Question: was your post formatted inside the *reply box*, or was it copy/pasted from some other source? The question pertains to more than just the text of the reply–did you have any links to other sources, or quotes from other sources? Did you have any formatting from HTML or word processors that add formatting to its text?

It was pasted from Notepad. There were no links to, or quotes from, other sources, and since it was pasted from Notepad there shouldn’t have been any formatting added. (Please correct me if I’m wrong about this)

I will try your suggestion and get back to you here with the result.

@Elly-

Thanks for your reply. It is now more than 5 hours and it hasn’t shown up.

abbodi86 wrote:

It’s hard to explain, i myself don’t understand the binary values

See http://grc.com/inspectre.htm / Release History / Release #4:

1    OS is not aware of the Meltdown vulnerability
2    OS is not aware of the Spectre vulnerability
4    The system is vulnerable to Meltdown
8    The system is vulnerable to Spectre
16    CPU does not support Spectre (microcode not updated)
32    CPU does not support low-overhead Meltdown protection
64    Meltdown protection disabled by registry setting
128    Spectre protection disabled by registry setting

Paul and PK,

Let  me give you what additional information I can.

I use Avira Free, which had set the key.

I deleted the key with O&O RegEditor and closed it. I then re-ran it and it showed that the key was deleted.

I ran the installer. After it had finished I reran O&O RegEditor, which showed that the key had been set.

 

windows7forever

2 users thanked author for this post.

Cascadian, PKCano

PKCano,

I am running 64-bit Windows 7 Pro SP1 on an Intel i5-4460S CPU.

The registry key was not set.

I ran the KB4056897 MSI installer.

The patch was installed AND the registry key was set.

 

Those are the facts and you are correct.

2 users thanked author for this post.

Cascadian, PKCano

I have no idea what is going on in your case, but I am in Group B running 64bit Windows 7 Pro and KB4047206 installed without a hitch.

Thanks for correcting my error.

zero2dash wrote:

Neither the October nor the November updates had any Security fixes. (And now I know why there hasn’t been a .NET Security Only update since September.)

Although this is what MS claims, it is wrong. (What else is new?) On the Microsoft Update Catalog site there is a November .NET Security Only update for .NET Framework 3.5.1 on Windows 7. It can be found by searching for KB3097989 (although not by searching for .NET security updates, at least as far as I can tell).

PKCano wrote:

We’re not giving up on Group B.

Good to hear, since Woody’s Computerworld article says

The old “Group B” – security patches only – isn’t dead, but it’s no longer within the grasp of typical Windows customers. We’re actively discussing whether it’s worthwhile continuing to post information about the security-only patching path.

3 users thanked author for this post.

Charlie, wdburt1, The Surfing Pensioner

Let me clarify that the ”missing updates”, some of which I checked, were these:

Of the original list of updates that Group B was “missing” by not hiding the Monthly Rollups, “final important updates list” still had these “missing” updates.
2676562 Security
3005607 Security
3033929 Security
3123479 Security
3138962 Security
3149090 Security
3168965 Security
2868116 Win Update
3021917 Win Update
3118401 Win Update

Windows7Forever

1 user thanked author for this post.

walker

I read skimmed through your three part article before I made my post (the “missing” updates I referred to were the ones mentioned in that article). Maybe I missed something?

Windows7Forever

I have not checked all your “missing” updates on MS Catalog Update, but those I did check were all from before October 2016, i.e., before there were “Security Only Quality Updates”.

I did a clean install about six months ago with Windows Update by installing the latest Servicing Stack update, repeatedly hiding the ‘Rollups” until there were none left, and then installing all the patches marked “security” from September 2016 and earlier. It was time-consuming, but not difficult. Then I used the Update Catalog to install the SOQUs. Again, time-consuming, but not difficult.

May I suggest that:

1. It is still possible to do a clean install Group B style, and

2. Group B people aren’t missing security patches, after all

Windows7Forever