Skip to main content

Someone forgot the VFP splash screen?

Kind of funky - after installing SP2, I was hit with two issues:

One was more serious - my apps wouldn't run with the runtime, or at least the runtimes that were in the Shared/VFP folder. When I moved them to my app directory, they worked fine. Go figure.

The second was a head-scratcher. Now, I know Microsoft isn't putting more resources into VFP development and I know the team worked really hard on getting SP2 completed with everything. But is there any reason why they couldn't have properly cleaned up the splash screen? Here is what comes up when you first start FoxPro:


UPDATE: Yag has identified that they missed the file. Expect a refresh soon.

Looks like someone edited a bitmap file with MS Paint. On that topic, anyone know how to change the splash screen that is within the EXE?

I remember with older versions of Windows, it was simply a file that was attached to the end of the EXE.



Comments

Michael Babcock said…
Well, looks like they can't kill it now...there will have to be a SP3.
Bernard Bout said…
About the splash screen, it is stored in the file VFP9CHS.DLL and has the resource name - REGISTRATIONP in the Bitmap section. It can be edited by any resource editor.

However I don't know whether MS will allow anyone to edit this absolutely sloppy bit in this release.

I sincerely hope the actual SP2 and fixes are not as sloppily done.
Bernard Bout said…
It is also in the VFP9CHT, VFP9KOR and VFP9ENU DLLS. I guess for the English version you will need to edit the VFP9ENU.DLL
Tod McKenna said…
I find this absolutely hilarious...

It's like VFP went to prison and no one cares...
calloatti said…
The bitmap is in the following files: vfp9???.dll and vfp9????.dll

I made a correct bitmap available here: http://www.ctl32.com.ar/vfp9.sp2.splash.screen/vfp9.sp2.splash.screen.htm

A tool to change the file is also mentioned in that page.

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…