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

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator)

So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinctions I…

Security in Windows 10

http://www.slate.com/articles/technology/bitwise/2015/08/windows_10_privacy_problems_here_s_how_bad_they_are_and_how_to_plug_them.single.html

 discusses some Windows 10 privacy settings and their implications.

"Finally, we will access, disclose and preserve personal data, including your content (such as the content of your emails, other private communications or files in private folders), when we have a good faith belief that doing so is necessary." "In other words, Microsoft won't treat your local data with any more privacy than it treats your data on its servers and may upload your local data to its servers arbitrarily"
I did a quick install on a VM choosing the Express settings. When I fully deploy this on a real workstation, I will likely choose to wade through all of the individual pages, as David recommends.

Of course, losing one's privacy is nothing new - it's happening all over the place (despite Santa Ana's police force's lawsu…

AppleSoft

I'm not TRYING to be "fanboy-flame bait" but what I saw yesterday was a typical "Do it this way, now do it this way and then we'll go back to this way" all over again.... a move similar to what Microsoft does to developers on an ongoing basis.

Remember the first iPhone? Smooth and curved, at least as far as it could be back then. I still pull out my 3G and can see the curves on it.

Then the 4 came out and "boxy" was all the rage. Everything should be "tight with corners"

Now iPhone 6.... smooth and curvy is back. Granted I don't have the actual device yet, but that's the message.

Guess that means the iPhone 8 will be back to boxy.

And honestly, Apple Watch is not worth "one more thing" --- especially when everyone knows it's going to be shown. "One more thing" would be something no one saw coming.  The device itself ? Very interesting and yes, definitely lots of potential but "one more thing" wor…