Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Applications / Virtual PC / April 2005



Tip: Looking for answers? Try searching our database.

Business Contact Manager install problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
RAmeeti - 10 Apr 2005 19:51 GMT
When attempting to install Business Contact Manager for Outlook 2003, I
get the following message:

This computer does not meet the minimum requirements necessary to run
Business Contact Manager. Business Contact Manager requires at least a
400 MHz processor and 128 MB of RAM.

What would be the fix for this?
Paul - 10 Apr 2005 20:42 GMT
We would need a lot more info first.

What version of VPC?
What version of Windows?
What is the speed of your Mac processor?
How much RAM do you have on your Mac?
How much RAM do you have allocated to VPC?
vpc@customvisuals.com - 10 Apr 2005 21:49 GMT
I'm not the original poster, but I've seen the same message.
Windows XP SP2
PowerBook with G4 at 1.5 GHz
1.5 GB RAM total
512 MB RAM allocated to VPC

Thanks for any ideas.
Paul - 10 Apr 2005 22:47 GMT
What version of VPC??
RAmeeti - 10 Apr 2005 23:34 GMT
VPC v 7.0 (040819)
XP
1.67 MHz
1.5 GB
About VPC says Memory used by VPC: 535 MB (I have another VPC paused at
the moment)
File Get Info says PC RAM 256 MB, Total 270 MB
PC Settings: 256 MB
Paul - 13 Apr 2005 14:55 GMT
In PC Settings, allocate 384MB RAM to VPC.
Having more than 1 VM active (even though the second is 'paused') is
NEVER a good idea.
Put the second VM in 'Saved' or 'Shut down' state.

Another good idea would be to ensure that you do not have any other Mac
apps running (uses up resources on the Mac side unnecessarily)
RAmeeti - 14 Apr 2005 17:42 GMT
I'll try anything but...

I don't understand the suggestions. The error message says 128 MB
required. I have 256 MB allocated. Shouldn't that be enough? Or are you
just suggesting that more is always better?

And quitting all other open applications didn't work either.

Were these just standard 'try this' options or did you really expect
that they might work? If either of them did actually work it would just
really speak to the terrible design of Virtual PC. Not having any other
apps open in this day and age should not even be on anyone's need of
things to check but nice try.
Paul - 14 Apr 2005 18:55 GMT
No, I'm not just suggesting that more RAM is better. In fact, I always
advocate alloting 50% of your physical RAM to VPC to a MAXIMUM of
384MB.

If you have more than one virtual machine running at the same time (and
'paused' is actually a running state), then you are using RAM to keep
that VM going. That's why you're getting the message.

It's in the VPC Help files:
do a search for 'managing multiple virtual machines'
RAmeeti - 15 Apr 2005 13:15 GMT
> No, I'm not just suggesting that more RAM is better. In fact, I always
> advocate alloting 50% of your physical RAM to VPC to a MAXIMUM of
[quoted text clipped - 3 lines]
> 'paused' is actually a running state), then you are using RAM to keep
> that VM going. That's why you're getting the message.

But that is not why I am getting the message since giving it 384 MB of
RAM with no other VM going, and no other Mac apps open still gives me
the same error that the program won't install until I have the minimum
requirements of 128 MB of RAM in my computer (which is a totally bogus
error message in this situation.)
RAmeeti - 15 Apr 2005 13:57 GMT
What's with the recommendation of maxing out at 384 MB of RAM? I see
nothing that alludes to this in the Help files. Nor do I see anything
about recommendations about allocating 50% of physical RAM.

The Help files are all about recommendations given the OS that a user
is trying to run. And how without adequate unused physical RAM in the
Mac, the PC will be sluggish and will have to rely on Virtual RAM which
will be slower. But I see not stated numbers or percentages (Minimums,
Maximums, or Recommended) for any of the issues as you've mentioned.

And then again, even by throwing more RAM at VPC, quitting all other
virtual machines, and quitting all other Mac apps, I still get the same
error that the app needs 128 MB of RAM in my computer to be able to
install. Who can I request support from on this? Does MS provide
support on this stuff or are we just SOL?
Paul - 15 Apr 2005 16:16 GMT
What's with the attitude???????

I don't get paid to do this. If you want help and advice, try being
pleasant.

You want everything written in stone? Then you need to buy another
product. There is not much documentation available for Virtual PC. The
recommendations that I make are from personal experience and I don't
make any guarantees that they will work.
RAmeeti - 15 Apr 2005 23:38 GMT
Sorry about the attitude. I didn't think the offering of throwing more
RAM at it or the offering of quitting all other Mac apps was all that
beneficial. I heard those kinds of suggestions 20 years ago. I was
hoping for some technical support from some MS kind of person who might
have offered an answer as to why a Microsoft product can't install a
Microsoft product.

As for writing in stone? Well, are you saying that MS doesn't offer
support on this product? Or just not in this news forum.
Paul - 16 Apr 2005 00:30 GMT
MS did not develop VPC. In fact the purchase happened less than a year
ago. Now, this is a very small market and throwing multi millions of
dollars at VPC for development and documentation would not be in MS's
interest, given that VPC is relatively cheap and the cost recovery
would be almost impossible. Thus, you're not going to get an enormous
database of fixes, workarounds, or SPs to cover each and every issue.
The original developer (Connectix) did not document 'extensive' support
files for VPC either. The documentation that is provided is for basic
use and setup. All of those files are contained in the Help section.

For Virtual PC support, Microsoft is responsible for ensuring that VPC
runs and that a supported operating system (W2K or XP) is operating
within VPC. There are no guarantees that ANY software program will run
within that environment and technical support for that product is the
responsibility of the software developer. So, if you are trying to
install a Microsoft program in VPC and you are encountering difficulty,
you need to contact the department responsible for the software
(Outlook, MS Word, MS Access, etc.) All too often, people contact VPC
support for these issues and turn away in frustration when the issue
cannot be resolved at that level
Shallen - 27 Apr 2005 16:47 GMT
> When attempting to install Business Contact Manager for Outlook 2003, I
> get the following message:
[quoted text clipped - 4 lines]
>
> What would be the fix for this?

I have seen this and have a work around for this issue.  When Virtual
PC runs on a PowerBook G4 the processor is identified by Windows XP in
system requirements as well as most all other benchmark programs as
being equal to roughly 295 MHz.  This could potentially be due to the
CPU cycling being identified at only the lowest potential level within
a Mac G4 PowerBook, or it may be in relation to a different issue
similar to this.  As a result the program will not install as it
requires the minimum 400MHz processor to be identified to complete
installation.

Try the following to see if you can get it to install:

- On the first attempt it would probably be best to identify the last
screen that appears before the Benchmark screen, or identify the last
screen before the error that the minimum system requirements was not
met appears.

- Once this is identified continue with the installation until you
reach the
previous screen before the benchmark is identified but do not click
continue yet.

- Be ready to pause and resume the machine using Apple + Escape.

- Now click continue, next, or whatever is the option to continue
toward the next screen, and then immediately pause the Virtual PC.

- At this point begin resuming for 1 second, and then pausing for 3
seconds repeating the pausing process until the next screen appears
with the benchmark results.

- If the benchmark screen no longer appears great, or if the benchmark
screen says that we past great, we now continue on through the install
most likely without incident.

- If the benchmark failed still but displays a result pay close
attention to the
result and attempt again.  It is possible it is working you may just
need to make a second attempt to reach the desired results. In
particular, it may be necessary to start the pausing and resuming from
the moment you begin to run the installer however it is more likely
that the above steps will work just fine.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.