Vista - Program too big to fit in memory

I'm running XP Pro sp2 as the guest OS on top of a Vista Ultimate host using
VPC 2007 (ver 6.0.192.0). Both Vista and XP are 32-bit.

When attempting to run InstallShield's setup.exe to install an application
on the VM, I get the message "Program too big to fit in memory".

I'm installing as Administrator. I've bumped the VM's memory to 1GB. I've
also copied the CD image to drive C and launched setup.exe from there. Still,
the same message appears.

Setup launches just fine if invoked from the host OS or on any of four other
computers I have available running XP Pro (512MB RAM) and various versions of
Vista.

I've installed several other applications in this VM using InstallShield's
setup with no problem.

Does anyone have any ideas or suggestions? I'm hoping this is a "duh!" moment.

Thanks!
--
Jack
<><>

On 06/09/2008 in message
<68DE2599-6B2F-4353-8607-6C22BA9EA4B5@xxxxxx> Jack wrote:
I haven't seen that for a long time but I think it's one of those
mis-leading error messages and often indicates that the install file is
corrupt.

--
Jeff Gaines Damerham Hampshire UK
If it's not broken, mess around with it until it is

On Sat, 06 Sep 2008 01:29:53 -0700, in microsoft.public.virtualpc, "Jeff
Gaines" <whitedragon@xxxxxx>, wrote

I completely agree with you. I think that particular message is a generic
"something's wrong" message that could be triggered by a cascade of error.

I am curious as to what app the OP was trying to install and if *the same
install file* had installed correctly on other VM's.............

FACE

I agree with both of you, "Program too big to fit in memory" is likely a
misleading report of the actual error encountered.

FWIW, I'm trying to install an ARM C# compiler. It installs just fine on a
box that's running Win XP Pro SP2 (version 5.1, build 2600). This box is not
running a VM. Setup is executing in essence in the host OS. The VM I'm
attempting to run setup on is also running Win XP Pro SP2 (version 5.1, build
2600). The setup installs just fine on a Vista box as well. (Unfortunately,
the publisher's licensing scheme doesn't work on Vista, hence my need for XP.)

With that, I'm pretty confident that the setup application isn't corrupt. It
looks to me as if the the VM code is interpretting some instruction in the
exe header differently than the code is interpretted when running under the
host OS. I suppose that it could indeed be an error in the setup application
that when running under the host environment, the OS/CPU acutally ignores or
adjusts and OS/CPU aren't ignoring or adjusting when running in a VM's guest
OS.

--
Jack Waller
<><>


"FACE" wrote:

Jack wrote:
Hi,

This is going to be a bit convoluted, and I hope that no one here gets
upset about it, but what you might do is create a VHD under VPC, and
then install your XP SP2. Then, shutdown the XP guest, and import the
VMC/VHD into VM Player, which is free.

Then, try your installation there, running under VM Player?

Jim

On Sun, 7 Sep 2008 21:21:07 -0700, Jack <n2(delete)jack@xxxxxx>
wrote:
It might be also a case where the "publisher" has actually put code in
the installer to stop you from installing in a virtual machine.
I have run across such programs and the apparent reason is that the
publisher does not want his code to be installed in a virtual
environment, which can more easily be duplicated (by copying the vmc
and vhd files).
Have you checked his condityions of usage/installation?

--

Bo Berglund (Sweden)

On Mon, 08 Sep 2008 01:01:50 -0400, Ohaya <ohaya@xxxxxx> wrote:
No one should get upset. VPC and VMWare do the same thing, but
through different and independent methods. Some things work in one
and not the other.
That's the beauty of competition, different solutions for the same
problem.

Look at VPC and VirtualBox, the Innotek guys built the OS/2 port of
VPC, but were still able to build an independent VM software...just
goes to show what can happen...

--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/
I do not work for Microsoft.

Hmm... I see your point. No, I haven't specifically asked. However, it was a
techy from the publisher that suggested installing on a VPC. I'll ask that
question today.

Thanks for the idea.

--
Jack
<><>

"Bo Berglund" wrote:

Thanks, too, Steve for the VirtualBox suggestion. I'll look at it as well.
--
Jack
<><>


"Steve Jain" wrote:

"Jeff Gaines" wrote:
I found the solution. I belileve the problem lies in the CD ROM driver and
CD ROM format. I haven't had a chance to exam things close enough to know for
sure. Anyway, I found that if I looked at the Setup.exe file using a Hex
editor while in VPC, the exe header was corrupt. Looking at it using a hex
editor from the host OS and the exe header was correct. It appears all other
files were corrupt as well.

When I copied the CD files from the host computer to the guest OS using a
shared drive, the files came over cleanly and I was able to install.

Thanks all for your contributions!

--
Jack Waller
<><>