stillrapid.blogg.se

1. #How to install rosetta stone version 4on mac without cd drivers#
2. #How to install rosetta stone version 4on mac without cd Patch#

So to all of you who might use this, or some other flavor of BSD as a desktop, what advantages does it offer over Linux? That's 15.5 thousand services, applications, libraries and utilities available for the cost of typing "make install clean". This is being addressed in -CURRENT as nVidia have intimated that a key function they require is not present in the amd64 port and the devs are working on it, so the situation is set to change in the near future.īy the way, ports count at present is ~15500.

#How to install rosetta stone version 4on mac without cd drivers#

Also, there are no proprietary nVidia drivers for amd64 yet, which is not true for i386.

#How to install rosetta stone version 4on mac without cd Patch#

I tend to use the 32bit Linux version on amd64, but the native i386 version has the most plugins available for it (win32codecs, Flash - you need a patch to make Flash7 work with the linuxpluginwrapper and native Firefox, see the message displayed when you install the port - et al). OpenOffice now works perfectly on amd64, as does JDK15 (albeit without the browser plugin) but native Firefox still has "issues" (startup hangs on a machine with an NFS mounted /home, hard locks, crashes to name but a few problems I have encountered) and plugins are rather flaky. My last word on the subject is this: If you have an amd64 machine, for now I would use the i386 port (CPUTYPE=athlon64 in /etc/nf which will compile everything with -march=athlon-mp), especially if you use Firefox or you may end up rather frustrated. There's a lot of help to be had on the Usenet group .misc, too. Oh, and for anyone reading this thread who is saying "I only have one dsp device that gets locked and nothing else can use it," there is a sysctl knob which needs setting: hw.snd.pcm?.vchans which I usually set to 4 in /etc/nf. Also, try not to use "custom" compiler flags like -ffast-math and -funroll-loops as you can end up with hard to diagnose problems when building from source. Just watch what depends on what, especially the COMPAT_? options. Once you get used to it, nothing ever comes close to the ease of compiling new kernels IMHO. Or you could use those addresses for faster-than-usual I/O /NOTES files. If you were very clever, you could pull stunts with mapping different 256-byte chunks of memory into that space. You could use zero page memory as an extended register set. Most instructions had a "shorthand" form which accessed a byte in the address space $0000-$00FF, using only one byte for the operand address, so saving a clock cycle and a byte of RAM.

The 6502's "zero page" instructions were a timesaver.