Splwow64.exe

[ZZBeard]

A compiled complex BB4W program which has run perfectly on Windows 7 for many months seems to inexplicably and irregularly start or spawn an additional dependent iteration of Windows ‘Print Host for Applications” Splwow64.exe when the program is run on Windows 10.

The print host dependency can be seen in the Windows 10 Task manager as a sub task of my program’s exe file. There in no intentional print functionality programmed or required in my program, and I haven’t so far found a reason for this extra program to be started.

I have searched for information about how splwow64.exe would be invoked if it IS wanted but I have not found any. Can anyone help me identify why my program might be invoking this unwanted Windows program on Windows 10?

David

[guest]

There in no intentional print functionality programmed or required in my program, and I haven’t so far found a reason for this extra program to be started.

Whether your program has "print functionality" isn't relevant, since there's no way BBC BASIC (or Windows itself) could possibly know that. It's entirely reasonable that 'printer support' would be installed in case it's needed, just as support for (e.g.) sound or a joystick will also be installed whether or not your program needs them. If you look at the set of DLLs loaded into your process you'll probably be surprised by how many and varied they are.

Why does it concern you (assuming it does)?

Richard.

[ZZBeard]

If you look at the set of DLLs loaded into your process you'll probably be surprised by how many and varied they are.
Why does it concern you (assuming it does)?
Richard.

My program is designed to run for almost 24 hours and then quit itself at a particular time of day, and then get re-run by Task Scheduler a minute or so later.

Whenever the spawned print host app has become present, my program fails to quit itself, but becomes an inactive 'background task' along with the print host.

Task Scheduler sees that the program is still running and doesn't reload the program in the foreground at the programmed time, so that the actions that the fresh version of my program is designed to perform for the next day, do not get done.

Is there a way of compiling a BBC BASIC program as a 64 bit executable? Maybe this wouldn't then invoke the 32bit program print host helper Splwow64?

David

[guest]

Is there a way of compiling a BBC BASIC program as a 64 bit executable?

There's no way of compiling a BBC BASIC program at all (BBC BASIC is interpreted)!

I don't understand why the presence of a 'spawned task' would cause your program not to quit; the QUIT statement should unconditionally terminate the process. The spawned printer helper program may well keep running (it's probably designed to remain resident, once started, until the PC is next rebooted) but that shouldn't have any unwanted impact.

What happens if you create an executable from a minimal program, something like:

Code: Select all

      WAIT 1000
      QUIT

If you run the EXE does that also result in a 'hung' process?

Richard.

[ZZBeard]

Is there a way of compiling a BBC BASIC program as a 64 bit executable?

There's no way of compiling a BBC BASIC program at all (BBC BASIC is interpreted)!

Yes, of course I know that! I was using the term in the same sense that YOU have used for the tooltip that appears saying "Compile" when you hover your pointer over the double gearwheels of the BB4W Toolbar!

I will try the dummy program suggested and see what happens...

David

[guest]

Yes, of course I know that!

Fair enough, but in that case I'm sure you also know that there isn't a 64-bit version of 'BBC BASIC for Windows' so it was something of a rhetorical question.

My assumption remains that Windows will be the last of the 'mainstream' operating systems to drop support for 32-bit applications, and there's no suggestion that I've heard that it will happen any time soon. That makes it almost certain that if BB4W is ever adapted to be a 64-bit app it won't be done by me - I'll be long gone or at least (even more) gaga.

I also doubt that you would be enthusiastic about making the changes to your program that would be likely to be necessary to make it 64-bit compatible. Even now I tend to write BBC BASIC programs initially as 32-bits and then make the necessary modifications as an afterthought if I'm concerned about 64-bit compatibility. In an ideal world it would be helpful to have an automated tool that would scan a program and make the necessary changes (or at least alert to where they are needed) but that's something else never likely to exist unless somebody volunteers to write it - which of course they won't because nobody cares.

Richard.