Prev: Asking Advice
Next: Outlook 2007 and second inbox created
From: Jeff Johnson on 22 Feb 2010 17:48
"LondonLad" <LondonLad(a)discussions.microsoft.com> wrote in message
news:677EC6DA-4648-47B0-AEB6-522CFC04EA32(a)microsoft.com...

> If I copy a VB Exe from my Desktop with OS XP Pro it fails to run on my
> laptop with OS Win 7.
> Can I get this to work?

If you don't have the "Home" version of Windows 7, take a look at this:
http://www.microsoft.com/windows/windows-7/features/windows-xp-mode.aspx


From: Dee Earley on 23 Feb 2010 04:46
On 22/02/2010 17:25, LondonLad wrote:
> Hi
> If I copy a VB Exe from my Desktop with OS XP Pro it fails to run on my
> laptop with OS Win 7.
> Can I get this to work?

Another one for the pot:
http://hashvb.earlsoft.co.uk/User:Dee/It_doesn%27t_work%21
(I know you've been given this URL before)

--
Dee Earley (dee.earley(a)icode.co.uk)
i-Catcher Development Team

iCode Systems
From: Tony Toews [MVP] on 25 Feb 2010 18:30
LondonLad <LondonLad(a)discussions.microsoft.com> wrote:

>If I copy a VB Exe from my Desktop with OS XP Pro it fails to run on my
>laptop with OS Win 7.
>Can I get this to work?

Obviously you need to give more information.

That said there's some kind of manifest stuff required for Windows
Vista and newer to tell the OS you only want user privileges. A VB6
utility of mine wouldn't work until I added that. The definition of
wouldn't work was rather obscure. It simply wouldn't copy files but
wouldn't give me an error message either.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
From: Webbiz on 26 Feb 2010 16:13
On Mon, 22 Feb 2010 09:25:01 -0800, LondonLad
<LondonLad(a)discussions.microsoft.com> wrote:

>Hi
>If I copy a VB Exe from my Desktop with OS XP Pro it fails to run on my
>laptop with OS Win 7.
>Can I get this to work?
>
>Thanks


Since I've been having to deal with various issues using both a
Windows 7 (32) Pro and Windows 7 (64) Pro systems, I'll chime in from
the more 'novice' crowd.

As everyone has already stated, you didn't provide much information.

For one, did you try to just 'copy' the .exe from XP to Windows 7, or
did you try to do an "install" of a VB app onto Windows 7? If you just
tried to copy the .exe file alone, chances are the app's dependency
files have not been installed or registered onto your Win 7 system.

Now, assuming you meant "install" failed, that I've seen happen with
Windows 7. The usual way to deal with that is to make sure you run the
install by selecting "Run as Administrator". Seems Windows 7 will
prevent some support files from being copied into its protected
directories and/or bother registering them.

To "Run as Administrator", simply right-click your installation file
and select it from the popup submenu.

One last thing. Some older apps, even if you install everything just
fine 'as administrator', will have some hickups. VB6 itself I've found
to have this issue on my machines. To get around this, you right-click
the program icon, select Properties, then Compatiblity tab. Click on
the "XP SP3 Compatibility" checkbox and also the "Run as
Administrator" checkbox.

Whether this is what you're 'suppose' to do, I can't swear to it. But
it is how I solved many of my Win 7 issues with apps from XP and
older.

:-)
Webbiz
From: MikeD on 26 Feb 2010 17:29


"Webbiz" <nospam(a)noway.com> wrote in message
news:1pdgo5p44617ujd589h8j7ug4fv5dsvp34(a)4ax.com...
>
> Now, assuming you meant "install" failed, that I've seen happen with
> Windows 7. The usual way to deal with that is to make sure you run the
> install by selecting "Run as Administrator". Seems Windows 7 will
> prevent some support files from being copied into its protected
> directories and/or bother registering them.
>
> To "Run as Administrator", simply right-click your installation file
> and select it from the popup submenu.

While I don't mean to discourage this as a sure-fire way to run the setup
with admin rights, it's not necessary if the file is named Setup.exe
(variations are also supported, but I don't know right off-hand exactly what
those variations are). Windows will automatically elevate to admin IF the
logged on user is a member of the Administrators group. I'm also pretty sure
any Windows Installer package, regardless of file name, will get elevated
since it can only be an installation (or patch/update).


> One last thing. Some older apps, even if you install everything just
> fine 'as administrator', will have some hickups. VB6 itself I've found
> to have this issue on my machines. To get around this, you right-click
> the program icon, select Properties, then Compatiblity tab. Click on
> the "XP SP3 Compatibility" checkbox and also the "Run as
> Administrator" checkbox.
>
> Whether this is what you're 'suppose' to do, I can't swear to it. But
> it is how I solved many of my Win 7 issues with apps from XP and
> older.

Those should usually be considered as last resorts; i.e. there's no other
way that the app will run properly and there's no newer version
available...especially running the app with admin rights. Ideally, the app
should be re-written to be compatible with Vista and Win7. You might,
however, need to use compatibility UNTIL the app is re-written, or perhaps
permanently if the app is no longer supported at all.


--
Mike


First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Asking Advice
Next: Outlook 2007 and second inbox created