Archives for MacOSX category
Heres a recap for everyone to Install HP LaserJet 1020 on Mac OSX. 1)
Download; http://www.narc.ca/1601-LJ_1022_Series_OSX.dmg (Old version)
2)If you have anything for the HP 1020 in “/Library/Reciepts” delete it.
3) Delete anything for the HP 1020 in Printer in “Printer Setup Utility”
4) Add new printer in “Printer Setup Utility”, select HP LaserJet 1020, driver should come up, click ADD Then you should be able to print.. glad we finally got around this one.. and one big FU to HP.
but it runs very ok!
vmware fusion
In the comments of Customize Prompt On Mac OS X, jh asks how to color your command prompt:
How about the colored bits below the command
prompt?
I’ve noticed that when I do an ‘ls’ on my own mac it tends to
be monochromatic, however, when I’m ssh-d in to a linux machine and
‘ls’ I tend to get output that colors directories, and executables
differently.
Why is this? And is there any way to get my own mac’s
output to be color coded as well?
Of course there is!
Open up ~/.bash_profile and add the following two lines:
export CLICOLOR=1
export LSCOLORS=ExFxCxDxBxegedabagacad
Save, exit, log out, log in, and there you are!
Update: For tcsh users, I was able to get the same effect putting the following in ~/.tcshrc:
setenv CLICOLOR "1"
setenv LSCOLORS “ExFxCxDxBxegedabagacad”
For iTerm users, add the following to ~/.bash_profile:
export TERM=xterm-color
alias ls=’ls -G’
alias ll=’ls -hl’
Bueno cuando no haya blogjet 
o MarsEdit para Mac
Powered by ScribeFire.
My Mac Pro arrived. However, one thing I noticed immediately is that I could copy files at around 30MB/s across my gigabit network if the Mac Pro was talking to one of my Infrant ReadyNas boxes (AFP), but as soon as I tried to copy to or from Windows XP using SMB, network traffic slowed to a crawl. I was unable to transfer data faster than 4MB/s, which is 1/2 of real-world 100Mbps. Luckily, I found a fix late last night.
I did some investigating online and discovered that some Windows boxes don’t like ACK delay. I also read that the slow network performance might also be an IPv6 compatibility issue. So here’s what I did:
Now I’m getting around 30MB/s when copying between MAC OS X and Windows XP boxes, which is good. But man, what a pain in the ass to get these machines talking.
1. I downloaded VirtualCloneDrive from Slysoft (or use an other disk image mounting utility) and mounted my disk image with it.
2. Opened VMware and made a new machine. I selected Other, Other. for the OS.
3. Chose the add hardware option when I had created my virtual machine. I selected CD-ROM drive, and chose PHYSICAL DRIVE. I selected my VirtualCloneDrive, in my case it was I:/
4. Power on the virtual machine. When I installed I used “-v -x Platform=X86PC”
abrir el archivo con freebds.vmx and paevm = “TRUE”
5. I erased virtual disk in teh disk utility and installed OS X to it. make sure you select the patches in teh intsllation options part. I skipped the installation disk check part.
6. When I booted I got the “b0 error” I went back to VirtualCloneDrive and I mounted the gParted liveCD (google for it)
6 II. I booted up VMware and pressed escape and chose boot to CD. when it loaded I selected the partition, right clicked and selected “manage flags” and ticked boot. I restarted teh virtual machine.
7. This time it loaded up perfectly, when through the set up Mac OS X process and most of teh stuff worked. I dont have a network connection because I didn’t set one up when creatign the virtual machine, and it cried about some Sound driver plugin kext.
Conclusion:
OS X in VMware is good. It lets you fiddle with OS X to see it is right for you, But I wouldn’t recommend using it like it was native, it’s too slow for that and maty be difficult to set up for network, etc.
Para bootearlo
rd=disk0shd platform=X86PC -v
After setting up and installing and rebooting the first time, your install hangs, try this fix.
Boot FROM THE INSTALL DVD. Go to utilities and open up TERMINAL. Type (without the quotes): “mount -a” then type “/Volumes/yourosxinstall/usr/sbin/chown -R root:wheel /Volumes/yourosxinstall/system/library/extensions/” then type “touch /Volumes/yourosxinstall/system/library/extensions/” REPLACE yourosxinstall with the name of the volume where your os x is installed (Mac for example). Reboot and pray.
WARNING: Some have experienced data corruption when using sata on nForce4! If this occurs to you, it is not our fault and you use this information at your own risk. Neither I nor Jas will be responsible for any loss of your time or money caused by this.
Hope this helps some of you.
Para activar root
sudo passwd root
Para tener acceso a root
sudo bash
Para cambiar la pantalla
input;
<key>Graphics Mode</key>
<string>"1024×768x16@60"</string>
-in your com.apple.Boot.plist located in \Library\Preferences\SystemConfiguration
19. Close the 10.4.3 window in VMWare (”File”->”Close”). Manually edit your VMWare guest conf file (.vmx) and add the line
paevm=true
If you use VMWare 5.5, you can also manually change the guest OS type to
guestOS = “darwin”
20. Open and startup the 10.4.3 VMWare guest and use “mach_kernel.sse2″ as boot option if you have installed a patched kernel. This will get you into the GUI. You can also add flags like ” -v” (verbose), ” -s” (single user mode) etc.
That’s it. Takes about 45 minutes to complete.
Tips
* To put files to your 10.4.3 image you have two options:
o add the 10.4.3 image file as an additional HD to your 10.4.1 Vmware guest and copy under 10.4.1 to the volume (as described above).
o use e.g. TransMac to access the HFS+ volume in the VMware image directly.
* In single-user mode you have to explicitly mount the volume as writable to modify files (as explained here). Basically, just type:
fsck -fy
mount -uw /
* To clear and force a re-caching of the kernel extensions use the “kextcache -k” command.
* To properly shutdown your system from the system console (e.g. in single-user mode), just use shutdown -h now or reboot.
* If you use VMWare and you get this popup
* VMWare workstation internal monitor error (bug 9297) *
“The guest opearting system you are running is using Physical Address
Extension (PAE) processor option. For more information about running
PAE-enabled guest operating systems, please consult
http://www.vmware.com/info?id=28
then you forgot to add the “paevm=true” line to your VMWare config file (It’s the .vmx file, usually in the same folder with your image file).
* If you use VMWare 5.5 RC1 or RC2 and your systems reboots or you get the above popup while loading, try to downgrade to VMWare 5.0.
Remarks
* The guide is based on my 1st one. You might want to read it since it explains the cause of all the troubles with the Mac OS X x86 boot loader issue.
* Java Boot Patcher (not required for this guide, but might be handy in the future); see this forum posting for usage.
* For using 10.4.3, your CPU has to at least support PAE (”Physical Address Extension”). Check this first, when you try to run it in native mode.
ZiVo Nix Blog