Software Compatibility List (SCL) - App listings issues, errors and improvments

If you spot an error in a SCL listing, want to suggest improved descriptions/installation instructions/listing details or report an error. Please post your feedback, corrections and comments in this thread.

Suggest the vxHPC pages

https://www.hpcfactor.com/scl/1047/Cambridge_Computer_Corporation/vx...

and

https://www.hpcfactor.com/scl/223/Cambridge_Computer_Corporation/vxH...

be merged, or just update the tags for 1047 and delete 223.

-Changed 223 to be version 2.7.8 + added binaries for newly discovered version 2.7.8

-Fixed tags for 1047

-Found/located new releases by same developer + added to SCL

Edited by torch 2022-12-15 7:00 AM

Awesome, thanks torch!

I noticed tonight that there are two versions of uBook in the SCL. The newer one (https://www.hpcfactor.com/scl/1011/Gowerpoint_Software/Book/version_2010) is under "µBook" and the older one (https://www.hpcfactor.com/scl/449/Gowerpoint_Software/uBook/version_0.9h) is under "uBook". I would like to suggest that the license file appear in both since I've tested it and it works for both. It currently only appears in the downloads for the "2010" version.

Also, should we change "µBook" to "uBook" to make it easier to find in the search and make it match the other entry?

Edited by thenzero 2022-12-16 12:25 AM

-Changed "µBook" to "uBook" for ID#1011, but added tag for "µBook" so it'll still show up.
-Added OS/Arch Compatibility Data
-Added License file to ID#449, tagged as "Supplemental", added notes in install instructions reflecting this.
-Matched above to ID#1011 "tagging as supplemental"

Also, we are missing the 2008 and 2009 versions in the SCL, but they're not on WBM
http://web.archive.org/web/20090508114625/http://www.gowerpoint.com...

I have reversed your µBook changes. Unless we can't encode the name because of the database collation, we don't get to decide the name of an app, it's developer does. The app's name is µBook. So I've set it back to µBook and put 'uBook' in the tag to aid search instead.

Thanks both- looks great.

I wonder if we should add the tag #MicroBook as well, since that's technically how the name is supposed to read verbally.

Okay, I have an idea about the SCL compatibility data..

So, maybe we could scrap the function of "Discover compatible software in the HPC:Factor Windows CE App Store
View: Software Compatiblity List (SCL)" in the H/PC device specs page...and add an architecture button:
SH3, SH4, x86, MIPS, ARM/Xscale--so here's how the behavior would work:
-Go to SCL home page
-and maybe add a button that says "Browse by Architecture"
-Then it would spit out a page that says "Generate a list of compatible programs for your CPU architecture" with buttons that say SH3, SH4, x86, MIPS, ARM/Xscale, CEF
-The "Results" page wouldn't have to be fancy literally just a plaintxt style list- just the SCL links for programs that are "theoretically" compatible - remember, we're not "really" using this page for discoverability - it's more a quick and dirty way to explore programs that work for your cpu

BUT: I'm playing devil's advocate- I'd worry such a system could theoretically encourage bandwidth hoarding "OMG I gotta download all of the SH4 apps!!" kinda thing --- so I don't know if it's viable - or helpful.
I think for me, it makes it a lot easier to find x86 programs if this were implemented..

Edited by torch 2022-12-22 8:15 AM

The idea doesn't work because then CE 2.00 SH3 users get shown pages of CE 2.11 SH3 apps that cannot work.

What it actually needs is dynamic regeneration of the categories listing so that it doesn't show empty categories when device flltered.

FYI, I don't mean now.
This is a "later down the road" one.

But: speaking of runtimes
For example, we have Example Application #225 in the SCL.
This program requires usage of .net Compact Framework 1.0 SP3.

Could we hardcode a link to that exact runtime required for the particular CE version that's most relevant. That way the user has a guide on what exact runtime version file they need.
I know we could just put in links, but the url would take up a lot of room. Maybe a simple BB code could be enabled so it's neat, bolded, and the URL is clickable from that name:
Like:
Windows CE 2.0: 1.0SP3
etc
and those would all be clickable

But: maybe that's a bad example, because the CE2.0 runtime requires you to append .exe.net to the files...alas, I don't know..

pstarppp doesn't work without one of the dat files.

SCL entry:
https://www.hpcfactor.com/scl/1397/Unknown_or_not_specified/pStar/ve...

There are also a bunch of other versions (original site still up and working):
http://www.pienet.co.jp/okubo/pstar.htm

Gonna attach the pstar.dat file to this post as the smallest change that could get it working would be to add that to the entry.

Thanks, I have added the dat file to the downloads tab.

@C:Amie great, thank you.

Okay, so question:
(which may be my next project)
The old abandonware style VBCE2.0 programs that work on my x86 thin client (after extracting a cab) (if they only have CPU runtime specific versions)
Should I post the raw vb or try and make a cef cab but append -beta to it in case there's issues with it?
I don't want to mess with the original binaries the SCL has