Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dale harris

Pages: [1]
1
QB64 Discussion / Re: QB64 incompatible with Windows 10 v2004?
« on: January 24, 2021, 09:35:15 pm »
Good news.

I am in the DHPOS chat room (that just opened 30 minutes ago) and one of the people there has a 2004 machine and the program worked there just fine.

So it looks like it is a specific computer problem.

I am sorry that I bugged everyone with this.

Dale

2
QB64 Discussion / Re: QB64 incompatible with Windows 10 v2004?
« on: January 24, 2021, 08:53:34 pm »
SMcNeill

I have forwarded your reply to the user.

3
QB64 Discussion / Re: QB64 incompatible with Windows 10 v2004?
« on: January 24, 2021, 08:29:55 pm »
I just checked my email and the user reported back with no luck.

So here is my list of possibilities…

1. QB64 programs will not run under Windows 10, build 2004.
2. Windows has screwed up somehow.
3. There is a problem with the user’s copy of Windows 10, build 2004.
4. It is a problem with the user’s new computer.
5. Gremlins.

So if anyone wants to test this with a different computer using Windows 10, build 2004 it would be greatly appreciated.
The user did not upgrade an old computer he purchased a new computer with Windows 10, build 2004 already on it. (My mistake.) So no QB64 program has ever worked on his new computer.
Note the two following links are for the version of  the program usxing the latest version of QB64.
Here is the download link for the program in question. http://keyhut.com/bigpoleq5.exe
Here is the source code for the program. http://keyhut.com/bigpoleq5.exe
Here is the link to the page on my site that describes the program http://keyhut.com/bigpole.htm
Or you can just test one of your programs on a Windows 10, build 2004 machine.

Thanks in advance for any help that anyone can provide.

4
QB64 Discussion / Re: QB64 incompatible with Windows 10 v2004?
« on: January 24, 2021, 08:04:05 pm »
Pete,
    I retired from owning a Sears Key Shop about 4.5 years ago. Obviously my timing was pretty good. I do not do that much coding anymore although I still do support the POS and other program on my site. As you can see by my being here I do dip my hands into coding when necessary.
   The source code for the main POS.EXE program has become too large to compile in Qb7.1 so I had intended to port it to QB64 but that has sort of bogged down although some of the smaller program files have been converted. And I did write the BigpoleQ program in QB64
   Mostly I do repair and construction work for friends and relatives and I have just finished converting half of the basement into a home theater.
   It seems as though when people learn that you are retired they just assume that you now have nothing to do so they come up with chores to help fill your time. “Thoughtful” of them.
   I see by your “beans” comment that you did find the link to the facebook page (https://www.facebook.com/daleharrispos) but did not click on it or you would know what is happening to me. It is about 20% actual POS support, 30% my reaction to some POS users, and the rest about my life. I know that sounds boring but somehow it seems to have a fan base. You will have to judge for yourself.



5
QB64 Discussion / Re: QB64 incompatible with Windows 10 v2004?
« on: January 24, 2021, 05:56:45 pm »
Pete,

I am that Dale Harris and I am still offering the free POS software at http://keyhut.com/pos.htm.
The QB64 version I am using is “QB64 VERSION (20160902/48)” or so it tells me.

I have just downloaded the latest version of QB64 and I will recompile one of my smaller programs and send it to my user to test.

Download done and QB64 did start.

I will report back.

6
QB64 Discussion / QB64 incompatible with Windows 10 v2004?
« on: January 24, 2021, 04:56:37 pm »
I received an email from one of my users that has upgraded to Windows 10 Version 2004 and he has complained that my programs in QB64 will no longer start.

I have not upgraded QB64 for quite a while. Is this a known problem? Will upgrading to the current version of QB64 and recompiling my programs fix this?

Pages: [1]