Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Alandor

Members
  • Content count

    7
  • Joined

  • Last visited

About Alandor

  • Rank
    InsanelyMac Protégé
  1. [How To] 5.1 Surround Sound

    Laik, I had that problem too, I get a "solution" using Jack (just google "jack for mac"). With it you can send any input/output from system or applications to another one. This way you can get a stereo music in itunes playing on 5.1 for example, just send the out1 of iTunes to system 1,3,5 and out2 to 2,4,6. And so on for the rest of applications.
  2. Nvidia G92 (8800GT) support in 10.5.2

    wjblol, seems there is no way to fix it yet. But if i was correct maybe there is only a problem of "wrong show info" not a problem about the amount of memory used by Leopard. All I tried was with no problems about video memory (and It was showing 0Mb), so I think is OK.
  3. Nvidia G92 (8800GT) support in 10.5.2

    same problem here I hope this can be fixed, I will try another values with this card and if i can't find any valid I will put the 256 one. It could be becausse the 8800 cards until the g92 ones where 320 and 640 so the values are not the same maybe) EDIT: Ok, some test done and no luck. But there is something weird, if I delete the VRAM,totalsize key completely It detects the card as 256Mb one and if I use the VRAM,totalsize option no matter what value I put, it can be correct one or completely incorrect It detects the 771Mb RAM size although more strange is if you put the key, but the value completely empty the ram size displayed is literally 0 (with no problems, the same usual freezes as the other people because beta drivers). EDIT2: Also I discovered some curious thing making changes on nvidia control panel for windows, It display this on the system information option: Note: (my version is spanish, so I hope to translate options accurately) Forceware version: 169.25 (in my case) Total Memory Available: 1279Mb (my computer has 2Gb of RAM altough I think this is not the RAM memory because the next). Dedicated video memory: 512Mb (just what should) System video memory: 0Mb (what ?? first strange here) Shared system memory: 767Mb (what again ?? this is getting really strange at this point). I will try to explain my thoughts about this and the relation with NVinject information. My motherboard is a nforce4 with a Geforce 6100 integrated and of course if It is in use It takes the video memory from the computer RAM. Actually I am using a PCI-E Geforce 8800GT 512Mb for video output so what is the deal ? Just the same as we see in the nvidia panel, the information we see on nvinject is a mix from the integrated and the pci-e cards. If we see the 0 System video memory, is just the value we obtain in nvinject when no value is given for VRAM,totalsize, also the Shared system memory we see is 767Mb wich is seems to be the same 771Mb nvinject reports (possibly due the same use of mb the DVD-R or harddisk uses giving one size or another slightly different depending on the 1000=1Kb vs 1024=1KB system). So if we take 767 and add 512 we have the 1279 Total Memory Available the nvidia control panel shows. Also, VRAM means that, virtual RAM, the name of the shared RAM used by integrated cards, so at the end the data we got is correct, but we are trying to see another information, we can say we are the wrong So the question now is where the people with integrated vga motherboards can access or check the real pci-e video memory ? My guess is the video ram is being used by the system correctly according to 512Mb but we can't see it. Maybe some especific software like the RivaTuner one for windows. mmmmm, what could happen if we run rivatuner from darwine ? the data about ram size or ram used given by the software is not from drivers but low level instead so it could work. I will try when i can.
  4. Driver for nForce4 LAN

    @monsieur D: thanx very much for your modified driver (and of course credit me, something I think I don't deserve but thanx very much). I realize that the MAC changed but really doesn't look more about it so I didn´t realize it was reversed, I always reset the cable modem. So thanx again. Oh, about the applesana forums, becausse spanish is my native language if anyone have any question or problem related to any thread that don't understand becausse of the language I am glad to help.
  5. Driver for nForce4 LAN

    well, you should see first the ID of your card and if it is not inside the .plist you should add it.
  6. Driver for nForce4 LAN

    I discover some weird behaviour since I got working the mcp61 lan, sometimes it says it is connected but really it doesn't work, but those times if i reboot (or poweroff) the computer and boot from a linux distribution (sysrescd for example) and configure the LAN and use it (just a ping to google) and then reboot directly to the MACOSX ALWAYS works. So people with similar problem about the 03ef LAN take care of this.
  7. Driver for nForce4 LAN

    Hi, this is my first post. And as I see I am not the only one with the nforce4 MCP61 (device ID 03EF) network driver problem. I will tell what I discovered so far and the way I solved this to get the network card work like a charm. First of all the version I used of the OS is 10.4.10. Well, first of all is of course download the file with the driver from Linux, windows becausse It is needed to edit the .plist file and the MacOSX itself consider read only that file (even as root) so It is much easier to use a windows or a linux. Also If you use a Windows you better will need an editor with support for unix files (like freeware notepad++). Next is open the info.plist file inside "forcedeth\build\Release\forcedeth-nockd.kext\Contents" directory and go to the longest line of the file where the cards IDs are (0x003710DE, etc) under the "IOPCIPrimaryMatch" key section, and change one of them to the ID of MCP61 (03EF) for example the last one changing only the second 2 digits of it (0x037310DE) this way it will be 0x03EF10DE. Next is to copy it to anywhere you can then read from MacOSX (usb pendrive, partition, cd, etc) and copy it to the desktop (easiest place) and run the proper commands from the first post but using the forcedeth-nockd.kext of course. It will detect the card and telling it is not supported but it will continue to load and it will work. And the last thing is to go to system preferences and the network configuration and create a new location in case you use static IPs. One thing I did and I am not sure if it's mandatory is change the advanced configuration section of the card where you change manually the network speed and so on (i use the manual system). Try that if doesn't work on automatic mode. I hope this helps all the people with same card as me with no luck using the forcedeth driver. VERY IMPORTANT NOTE: Remember to use ONLY the forcedeth-nockd.kext version becausse is the only one working with this network card, all the others detect it but it doesn't work.
×