Check the forum for new posts

[zedd151]

Okay, took a few minutes as I don't have a disk image of Windows 7 64 bit with browser, and other proggies I use. So had to install opera and a few necessities.
Anyway upon trying  CheckNewPostsHttps in Windows 7 64 bit, same results for me.   
Now I will slap windows 10 on this box. ( I hate windows 10/11) and try that... 

[StrykerX]

I will add that there's no firewall running on my Windows box however I have a firewall (pfSense) and it functions fine with that.

[zedd151]

Okay. I had to break from this and walk both the dogs.    A few more minutes... 

[zedd151]

SUCCESS with windows 10 64 bit... 
Now I have to troubleshoot why both Windows 7 32 bit and Windows 7 64 bit refuse to run the program properly. I am certain that the original programs did not require this.
At any rate Jochen I now certify your program to be ready for themasses Take it either as 'the masses' or 'them asses'.   
Also win 10 64 downloaded your dll  without a hiccup.

[StrykerX]

Are you doing this on VMs?

[zedd151]

Are you doing this on VMs?

Nope.

[jj2007]

Worked first try here on Win10 x64 :)

Great

Are you doing this on VMs?

I tested it in a WinXP-32 client: program starts but cannot download. So I opened Internet Explorer, and guess what? Masm32 not accessible. Hmmm... local files work. Google works. Google works fine, only that I cannot open any of the links provided, not even Microsoft.com: "The page cannot be displayed".

As suggested, I click "Tools/Diagnose connection problems", and as usual, Windows tells me useless and wrong stories, such as "must be a firewall problem". Ha ha, and Google found a way to cheat it, right? Besides, switching off didn't change anything

Has Windows diagnostics ever worked for any of the dozens of common problems with Windows?

^ ^ ^ Right-click the whole phrase, then click "Search the web for ...", and Google with put this hit on top: Has Windows ever actually found a solution to a problem?

First answer:

Windows is old, rickety, and antequated, but thinks it can fix anything. Sometimes you feel bad for it, so you give it a few seconds to try.

It's kind of like when your drunken uncle Jasper comes over. The dishwasher has been making a noise, and he swears it's an easy fix. Later that day, there's dishwasher parts all over the floor, and his attention is switched to watching the game and yelling at the TV.

Google is clever, Microsoft isn't

[StrykerX]

Worked first try here on Win10 x64 :)

Great

Are you doing this on VMs?

I tested it in a WinXP-32 client: program starts but cannot download. So I opened Internet Explorer, and guess what? Masm32 not accessible. Hmmm... local files work. Google works. Google works fine, only that I cannot open any of the links provided, not even Microsoft.com: "The page cannot be displayed".

As suggested, I click "Tools/Diagnose connection problems", and as usual, Windows tells me useless and wrong stories, such as "must be a firewall problem". Ha ha, and Google found a way to cheat it, right? Besides, switching off didn't change anything

Has Windows diagnostics ever worked for any of the dozens of common problems with Windows?

^ ^ ^ Right-click the whole phrase, then click "Search the web for ...", and Google with put this hit on top: Has Windows ever actually found a solution to a problem?

First answer:

Windows is old, rickety, and antequated, but thinks it can fix anything. Sometimes you feel bad for it, so you give it a few seconds to try.

It's kind of like when your drunken uncle Jasper comes over. The dishwasher has been making a noise, and he swears it's an easy fix. Later that day, there's dishwasher parts all over the floor, and his attention is switched to watching the game and yelling at the TV.

Google is clever, Microsoft isn't

Microsoft Troubleshooter being remotely close has a similar odds to winning lotto without a ticket...

[TimoVJL]

This site use TLS 1.3 and Windows 10 support it.

https://sockettools.com/kb/windows-and-supported-tls-versions/


CheckNewPosts.exe works for me in Windows 7 Pro x64

[zedd151]

CheckNewPosts.exe works for me in Windows 7 Pro

64 bit or 32 bit timo?


That's okay Jochen. It's always a ME problem.    Your program is probably fine.
I am going to try an unadulterated version of win 7 32 bit later today, only to test your proggy.
If even THAT fails, I will try to source a 'new' copy of the Windows 7 x86 iso... maybe the one here is corrupted or otherwise missing something???

It's always a ME problem.   

That's one way to look at it. The other is that YOUR program is the only program I cannot run...     It is really bugging me ... I'll get to the bottom of this eventually.

[jj2007]

It's always a ME problem.   

That's one way to look at it. The other is that YOUR program is the only program I cannot run...     It is really bugging me ... I'll get to the bottom of this eventually.

You are a bug chaser, like me. But don't invest too much time, it's not worth it ;-)

[zedd151]

You are a bug chaser, like me.

Only when I cannot otherwise solve the problem at hand... 

[jj2007]

Recent Posts is the only option for getting the info without being logged in.

The reason being that the site doesn't let you log in from an external program (only browsers can). That implies also that CheckNewPosts.exe cannot inform you about PMs.

[zedd151]

Okay. With a clean install of windows 7 32 bit no changes were needed to run your program. It did not download your .dll but once the .dll was put into program folder it ran as it should. 
I have no clue what is going on with my 'backup' of the OS. But since I am rebuilding a backup for x64, making a new backup for x86 won't be a big deal.  I just have to look at the batch file used in the original backups to see if there is any settings change there that *could* affect running you program.

edit to add...
internet options --> advanced  --->under security
checked Use SSL 2.0
checked Use SSL 3.0
checked Use TLS 1.0
checked Use TLS 1.1
checked Use TLS 1.2

[zedd151]

Now back on a fresh install of my original backup, I put the firewall settings and UAC settings same as the clean install. Does not run here. So apparently I was correct that something is amiss with this backup. So, back to the drawing board.