Search results

  1. T

    function keys

    When I press function keys in parallels, they seem to go to os x. Is anyone else seeing this? Tested in netbsd 3.0 guest (running the ion3 window manager which is mostly function key driven).
  2. T

    NetBSD/i386 3.0 on Parallels -- no network!

    The quick workaround is to install 3.0, install the source (prob by copying source sets to another iso and mount it -- thats what I did) untar the source code, go to /usr/src/sys/arch/i386/conf and cp GENERIC to PARALLELSVM. Edit PARALLELSVM and add the following line: options PCI_CONF_MODE=1...
  3. T

    NetBSD/i386 3.0 on Parallels -- no network!

    I'm working on this now; since openbsd 3.9 does work, i'm examining the differences between their pci attach code and netbsds. I don't think it's really a parallels problem, per se, since they don't claim to support netbsd.
  4. T

    incompatibility with qt/mac

    That was beta2
  5. T

    What are you going to do with paralled systems?

    Thats what i'm using it for too, or what I hoped to use it for that is. My short experience thus far isn't too positive (crashed on start immediately first time I ran it because I had qt installed in its default location, and when i fixed that I find that the | key doesnt seem to work in freebsd...
  6. T

    Back Slash doesn't work

    I got that in freebsd6 as well, well in console mode | does nothing, but in X i get a >. Using unix without the pipe key is just not fun.
  7. T

    incompatibility with qt/mac

    If you have Qt/Mac installed in its default location (/usr/local/Trolltech), parallels will try to use it, and crash (or atleast, it crashed with my installed 4.1.1). This does make it a little annoying to use parallels; is this a known problem/being worked on?
Back
Top