This is QB64 man! You don't have to Declare Sub nor "Call" Subs. :)

FWIW, while I agree that having to declare all subs at the top was a bloody nuisance, "Call subfoo" is, IMO, way more readable, than just naming the sub. Especially when others need to read and understand your code.

Yes, that's exactly what I wanted to do next, but first I need a mic. I'll look to see what Steve and Spriggsy concocted. And to work right, it would have to accommodate a certain amount of slop in length, spacing, and frequencies of the tone.

Could this also be related to the problem with the QB64 PRNG, when you cycle through a set of RND that is a power of 2? I'd say, to be on the safer side, always go through an odd number of RND in the loop?

See this, and how it creates a nice colorful pattern, over time.

Rem  Program creates dots using random x and y coordinates
Rem
Rem  To eliminate pattern, make sure the number of Rnd variables in
Rem  the loop are not a power of 2.
Rem -------
Do
    Call Initialize
    Call DrawDots
Loop
End

Sub Initialize
    _Title "Random Number Distribution"
    Screen _NewImage(840, 480, 12)
    Cls
End Sub

Sub DrawDots
    Randomize Timer
    Color 9
    Print "First random number this cycle"; Rnd
    Do
        x = Rnd * 840
        y = Rnd * 480
        c = 1 + Int(Rnd * 15)
        a4 = Rnd
        a5 = Rnd
        a6 = Rnd
        a7 = Rnd
        a8 = Rnd
        a9 = Rnd
        a10 = Rnd
        a11 = Rnd
        a12 = Rnd
        a13 = Rnd
        a14 = Rnd
        a15 = Rnd
        a16 = Rnd
        PSet (x, y), c
        _Delay .005
        If InKey$ = Chr$(27) Then Exit Do
    Loop
    Cls
    Locate 15, 35
    Input "Start with new seed (y/n)"; cont$
    If cont$ = "n" Then End
End Sub


Jeez, guys, aren't we exaggerating a bit? I think the moral of the story is same as it always is: don't go bleeding edge, if you want longer lifespan?

I had a 250 GB SSD in my previous work laptop, and it hung in there for more than 4 years (I kept blowing away the persistent requests to refresh, out of sheer laziness). Maybe that's the main thing. Don't go for multiple TB drives.

My new work PC's SSD is also 250 GB.

People who are packrats also demand the largest disc drives. Just as, people who have messy physical desks also have messy PC desktops. Ever noticed?

Well, I'm going crazy. Several things caused me to write new lyrics to "Careless Whispers."

Last night I woke up after watching Rugby on YouTube and low and behold a video done by @FellippeHeitor about subs and functions was playing, and he created an endless loop by calling a function within function. Then I read the post below. I lost it ...

Maybe it was all part of the dream.

Like, just the other day, I thought I had awakened. I was going about my business, talking to my wife, even, and then I said wait! How is there this wall to wall carpeting in this corner of the room, when we changed the floor to hardwood?

Crazy stuff. It was recursive, but it didn't give me that error message. Probably it would have now, though, that I installed the new dev build.

Hey, many thanks, guys!! Glad to have this working again. I've been using it quite a bit, and suddenly discovered several broken programs today. I didn't do it!

Don't know about what others do, but I've been using QuickBasic for real work, for years. No problem.

Started with Fortran in college, then had to switch to Basic, on a remote a time sharing system, in grad school. Used that same time sharing system at my first job. Then used the HP Basic, at a remote work site, on an HP 9830. And then, when we got our first IBM PS/2s at work, just for the hell of it, I typed "basic" at the DOS c:\ prompt. Surprise! There was my Advanced Basic IDE, right in front of me.

Then QBasic appeared, with the better IDE. I always used those at work. Who could possibly complain? The company didn't have to shell out any more money, and just about anyone can understand Basic code.

Then, in spite of its "invisibility," when I got a 64-bit PC with a 64-bit Windows, I had to find a better way to keep using Basic. Hey, I just used a search engine, and found this "invisible" QB64, no problem. And not just that, but unlike the previous transitions, all my programs worked. A couple had minor bugs, but this was as pain-free a transition as ever.

I've never had anyone complain about using Basic. One C programmer only said it makes his head hurt. Other than that, as far as work goes, I'm not sure who can possibly complain, or on what grounds.

Ye, the QB64 performance seems mostly unchanged, perhaps a hair slower than it was with Win10. I'm not positive about that yet.

I use Steve's graphics speed test, and my own number crunching speed test program. Both give more or less the same results as before. In my test, which creates three groups of five results, I get one or two slightly higher numbers in each group, than previously. But, still beta testing days for Win11, and that sort of stuff gets improved over time.

So, good deal there. In Steve's graphics test, the high number was increased when I enabled virtualization based security (VBS). Even using Windows 10. The low number was unchanged by VBS. And my number crunching performance numbers also unchanged, by VBS.