Problem Adjusting Window

On Wed, 21 Nov 2012 23:41:02 -0600, VanguardLH wrote:

My bad. Even though I reviewed my post before submission, often your
eyes will see what they expect to see.

You are asking how to get a product whose last version (major version,
not a service pack) was released back in 2004.

"Get" was the wrong word. Should've been "fix or alter the behavior of"
a product whose last release was before the release of the operating
systems in which you are attempting to use that product. So while you
are experiencing a glitch in a product that will never have another new
release, the only solutions that I can think of are workarounds.

That is fine.

Besides using the key combo to maximize the window (so it maximizes
inside the screen area outside the taskbar area), another option might
be to use AutoIt to detect when that window opens and run a script to do
the key combo for you automatically. You'd use AutoIt to force that
program's window so it was always maximized. Of course, you could
define the shortcut used to load FoxPro so that its window starts out
maximized, too.

That would be a good suggestion if it were VFP that was
misbehaving. It is VFP's on-line help that is acting weird. I start
it with F1 inside VFP.

I wish Microsoft would consider backwards compatibility really
important. I am also wrestling with getting some 16-bit programs
running under Windows 7. Virtual Windows XP does the trick for my
Windows 7 Professional desktop system, but not my Windows 7 Home
Premium laptop. (How is a limited product "Premium"?) I have found a
hack on the Web for getting it to run. I hope it works. I do not
think that I should have to jump through hoops to have my programs
continue to run reasonably.

Sincerely,

Gene Wirchenko

"Gene Wirchenko" wrote:

VanguardLH wrote:

Besides using the key combo to maximize the window (so it maximizes
inside the screen area outside the taskbar area), another option
might be to use AutoIt to detect when that window opens and run a
script to do the key combo for you automatically. You'd use AutoIt
to force that program's window so it was always maximized. Of
course, you could define the shortcut used to load FoxPro so that
its window starts out maximized, too.

That would be a good suggestion if it were VFP that was misbehaving.
It is VFP's on-line help that is acting weird. I start it with F1
inside VFP.

If the titlebar has a title that can be recognized, I still think you
could use AutoIt to detect that window to then maximize it. I haven't
use AutoIt (or AutoHotkey) for a long time. The folks over at
http://www.autoitscript.com/forum/ might know.

I wish Microsoft would consider backwards compatibility really
important. I am also wrestling with getting some 16-bit programs
running under Windows 7. Virtual Windows XP does the trick for my
Windows 7 Professional desktop system, but not my Windows 7 Home
Premium laptop. (How is a limited product "Premium"?) I have found
a hack on the Web for getting it to run. I hope it works. I do not
think that I should have to jump through hoops to have my programs
continue to run reasonably.

While I've touched on using XP Mode in Windows 7, I stuck with VirtualPC
2007 on one host and VirtualBox on another. I had VMWare Server on a
host but they dropped support for Server and went to Player but I
haven't bothered to try Player. There are times, however, that no VMM
(virtual machine manager) running a guest OS inside a virtual machine is
going to do what I want. Forget playing video games in a VM. That's
why I use multi-booting (not Microsoft's dual-boot scheme) to choose an
OS to load on booting the host with each host in a separate partition to
load it from there (see gag.sourceforge.net). However, that has the
nuisance that you have to reboot the host to get into the other full OS.


As for continuing to get your programs to run, well, that pretty much
dictates that you stick with the old OS under which those apps run well.
Changing an OS just because it's new is never a sufficient reason to
change to the new OS. Yeah, I know that most consumers have been
captured by the "newer is better" marketing mantra and worry about
support being lost on the older stuff (but for which they never did have
good support, anyway). If any apps are critical or important then they
should warrant being ran under an OS where they work, and that means NOT
moving to a new OS just because it shows up. I know several companies
that have mission critical apps that have to remain back on older
versions of Windows. Hell, many cash registers at retail stores are
still running Windows 98. I have an old host kept around because it
runs and old OS under which old games runs best using an old version of
the video driver (since a new version causes the games to crash).

Newer isn't necessarily better. It's just different.