In article
<a42c2315-065d-45fb-9ee8-f9c7936724a7@m3g2000hsc.googlegroups.com>,
> > In article
> > <6a6443d4-4dcf-4437-b96e-47c4d0676...@m3g2000hsc.googlegroups.com>,
[quoted text clipped - 7 lines]
> well, the problem is directly related to VMWare Fusion, which is a mac
> app :)
Well... You're right that the way Fusion emulates the hardware is
causing the problem, but you'd get the same error if you attempted to
install on an unsupported PC - so I'm betting the solution to that
problem will not be directly related to Fusion.
> if it was a real Windows environment, and not Fusion for Mac, id have
> no issue and thus no post.
>
> also got a thread going on the vmware web forum, will post results.
That definitely seems like a better venue.

Signature
Note: Please send all responses to the relevant news group. E-mail
sent to this address may be devoured by my very hungry SPAM filter.
JR
SpaceMarine - 20 Mar 2008 14:48 GMT
> > also got a thread going on the vmware web forum, will post results.
>
> That definitely seems like a better venue.
there were a couple of issues, one of which being that my virtual OS
didnt have enough ram allocated to it (even tho Fusion is supposed to
use 500mb by default, it wasnt quite enough). groovy.
for any one interested, here is an excellent VMWare Fusion config
guide for win developers:
http://blog.phatboyg.com/category/vmware-fusion/
Jolly Roger - 20 Mar 2008 14:51 GMT
In article
<3e7d8142-f10c-4a20-bc03-3e00558c0d1b@n77g2000hse.googlegroups.com>,
> > > also got a thread going on the vmware web forum, will post results.
> >
[quoted text clipped - 3 lines]
> didnt have enough ram allocated to it (even tho Fusion is supposed to
> use 500mb by default, it wasnt quite enough). groovy.
Got a link to the thread so the rest of us can read about the other
details?

Signature
Note: Please send all responses to the relevant news group. E-mail
sent to this address may be devoured by my very hungry SPAM filter.
JR
SpaceMarine - 20 Mar 2008 14:59 GMT
> > there were a couple of issues, one of which being that my virtual OS
> > didnt have enough ram allocated to it (even tho Fusion is supposed to
> > use 500mb by default, it wasnt quite enough). groovy.
>
> Got a link to the thread so the rest of us can read about the other
> details?
the other was my own stupidity. the two errors from the initial scan
were hardware, and os incompatibility. ram fixed hardware -- but
Windows XP cant do the SQL Server 2005 Enterprise edition.
http://communities.vmware.com/message/892012
sm
Jolly Roger - 20 Mar 2008 15:47 GMT
In article
<7c4e0967-6798-408d-9cd1-729dfd9f3dc3@59g2000hsb.googlegroups.com>,
> > > there were a couple of issues, one of which being that my virtual OS
> > > didnt have enough ram allocated to it (even tho Fusion is supposed to
[quoted text clipped - 8 lines]
>
> http://communities.vmware.com/message/892012
Ok. I guess I was more interested in how you figured out low RAM was the
cause.

Signature
Note: Please send all responses to the relevant news group. E-mail
sent to this address may be devoured by my very hungry SPAM filter.
JR
SpaceMarine - 20 Mar 2008 16:02 GMT
> Ok. I guess I was more interested in how you figured out low RAM was the
> cause.
on a poster's tip, i just upped it to a gig to see what happened -- it
then made it past that warning.
sm
Jolly Roger - 20 Mar 2008 16:43 GMT
In article
<bd4d838e-5deb-44b9-afe3-da15062882a9@p25g2000hsf.googlegroups.com>,
> > Ok. I guess I was more interested in how you figured out low RAM was the
> > cause.
>
> on a poster's tip, i just upped it to a gig to see what happened -- it
> then made it past that warning.
Ah - ok. Thanks.

Signature
Note: Please send all responses to the relevant news group. E-mail
sent to this address may be devoured by my very hungry SPAM filter.
JR