Jump to content
11 posts in this topic

Recommended Posts

Hi, new user here. I've tried googling around for a solution to this problem to no avail.

 

I recently got an Empire EFI build of OS X 10.6.2 up and running in VMware Workstation 7 and everything seems to be working just fine, but for some reason even though I have over 3 GB of RAM allocated, OS X is only recognizing 1 GB. I'm running this all through Windows 7 on an Acer Aspire 5552 with an AMD Phenom II and 4 GB RAM. If needed, I'd be happy to provide any other details on my hardware or software.

 

Also, an unrelated issue that I haven't been able to find a working solution for as of yet, whenever I try to open Mail, I'm given the following error:

 

"You have Mail version 4.0 (1075/1077). It can't be used on Mac OS X Version 10.6.2 (Build 10C540)."

I've seen several conflicting solutions from various sources online and I've been apprehensive to jump right in and try any of them at the risk of potentially screwing something up.

 

Any and all help with either of these issues would be greatly appreciated, and thanks for putting up with my newbish questions.

The amount of RAM that you allocate to your virtual system is managed by VMWare itself. When you start up VMWare Workstation and select your Virtual Machine it should list some facts like RAM:, Cores, etc. Double click on this section and from there click RAM. There, you can move the slider however you please. I would advise against allocating more RAM than is Recommended. That is all.

The amount of RAM that you allocate to your virtual system is managed by VMWare itself. When you start up VMWare Workstation and select your Virtual Machine it should list some facts like RAM:, Cores, etc. Double click on this section and from there click RAM. There, you can move the slider however you please. I would advise against allocating more RAM than is Recommended. That is all.

 

Thanks for the reply, but that wasn't what I was asking. I have 3GB of RAM allocated to the virtual OS in VMware, but when I load it up, only 1 GB is being recognized.

 

Here are a couple of screenshots to show what I mean:

 

vmware_reference_01.png

 

vmware_reference_02.png

 

I apologize in advance if I'm misunderstanding you.

The problem is in the ISO that you use as the boot cd.

 

Looks like you are using darwin_snow_legacy.iso (I can't see the whole filename in your picture), which loads a preboot.dmg disk image at startup, and uses a com.apple.Boot.plist file to set the boot flags:

 

darwin_snow_legacy.iso / VMware Tools (disk image) / Extra / Preboot.dmg / Preboot (disk image) / Extra / com.apple.Boot.plist

 

The boot flags in question: arch=i386 -v maxmem=1024 cpus=1

 

With maxmem set to 1024 you'll never get more than 1 GB of memory in the VM.

 

I'm trying to figure out how to either edit the contents of the ISO (without corrupting it) or create a new one without the maxmem flag - if you already know how to do that then you're all set, if not I'll keep you posted if I make any progress.

OK, I finally figured it out...

 

If you are using the darwin_snow_legacy.iso image, here's a modified version without the maxmem flag:

 

darwin_snow_legacy_nomaxmem.iso (compressed 7zip archive)

 

On first boot, and anytime you make changes to the memory settings in the VM, you'll need to manually specify boot flags -v -f. After that you should be able to boot normally.

 

If you're using a different ISO just let me know which one and I'll see if I can patch it for you...

OK, I finally figured it out...

 

If you are using the darwin_snow_legacy.iso image, here's a modified version without the maxmem flag:

 

http://bit.ly/jsR4Hq (compressed 7zip archive)

 

On first boot, and anytime you make changes to the memory settings in the VM, you'll need to manually specify boot flags -v -f. After that you should be able to boot normally.

 

If you're using a different ISO just let me know which one and I'll see if I can patch it for you...

 

You are awesome. That is exactly what I needed. OS X is now showing over 3 GB of ram.

 

I'm going to sound even more like a total newbie, but I had to boot without setting the boot parameters as honestly, I wasn't quite sure how to do it. I googled around a bit and while I could find plenty of descriptions for the flags, I couldn't find out how to actually set them.

 

Again, thanks a lot for your help. I really appreciate it.

You are awesome. That is exactly what I needed. OS X is now showing over 3 GB of ram.

 

I'm going to sound even more like a total newbie, but I had to boot without setting the boot parameters as honestly, I wasn't quite sure how to do it. I googled around a bit and while I could find plenty of descriptions for the flags, I couldn't find out how to actually set them.

 

Again, thanks a lot for your help. I really appreciate it.

Glad it worked for you without the boot flags, I couldn't get it to load on my machine without the -v -f (I probably didn't need the -v but I like to see what's happening during startup).

 

For future reference, should you need it: When you get to the Empire EFI disk selection screen, click once inside the VM to make it active, then press the Tab key to get to the alternate selection mode. Use the arrow keys to select your startup disk, type your boot flags, then press Enter.

  • 2 weeks later...
Glad it worked for you without the boot flags, I couldn't get it to load on my machine without the -v -f (I probably didn't need the -v but I like to see what's happening during startup).

 

For future reference, should you need it: When you get to the Empire EFI disk selection screen, click once inside the VM to make it active, then press the Tab key to get to the alternate selection mode. Use the arrow keys to select your startup disk, type your boot flags, then press Enter.

 

I have the same problem with empireefi amd....you can fix this?.....or how can i fix this? because i cant change .dmg.....please help

Yes but im use amd procesor and only can boot with EmpireEFI For AMD Processors.

 

OK, try this one:

 

EmpireEFI4AMD_nomaxmem.iso (compressed 7zip archive)

 

 

EDIT:

 

Excuse me work with....pres tap in empireefi and write -f in your file. thanxs!!!

 

Glad it worked, I'll leave the new link anyways in case someone else might want to use it.

 

I think the bootloaders are essentially the same, but darwin_snow_legacy has the VMWare Tools install package on it and EmpireEFI4AMD does not...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...