Problem with gcc in Leopard terminal

Hi,
I am hoping to study computer science in college and eventually become a mac developer. I just recently bought an objective C programming book that is geared toward beginners. After reading it some, I tried to make a very simple program. I used text edit and saved it as a .m file. When I tried to compile it in terminal using gcc, (I have installed the dev tools) it spat back this error message.
+Undefined symbols:+
+".objcclass_nameObject", referenced from:+
+.objcclass_nameFraction in ccG8DljJ.o+
+"objcmsgSend", referenced from:+
+_main in ccG8DljJ.o+
+_main in ccG8DljJ.o+
+_main in ccG8DljJ.o+
+_main in ccG8DljJ.o+
+_main in ccG8DljJ.o+
+_main in ccG8DljJ.o+
+ld: symbol(s) not found+
+collect2: ld returned 1 exit status+
My program (below) follows one in the book very closely and I am sure the code is sound.
Any help would be appreciated.
Thanks!
+#import <stdio.h>+
+#import <objc/Object.h>+
+@interface Point: Object+
+int xcor;+
+int ycor;+
+-(void) setxcor: (int) x;+
+-(void) setycor: (int) y;+
+-(int) getxcor;+
+-(int) getycor;+
@end
+@implementation Point;+
+-(void) setxcor: (int) x+
+xcor = x;+
+-(void) setycor: (int) y+
+ycor = y;+
+-(int) getxcor+
+return xcor;+
+-(int) getycor+
+return ycor;+
@end
+int main (int argc, char *argv[])+
+Point *mypoint = [[Point alloc] init];+
+[mypoint setycor: 100];+
+[mypoint setxcor: 50];+
+printf("The point's coordinates are (%i,%i)\n",[mypoint getxcor], [mypoint getycor]);+
+[mypoint free];+
+return 0;+

Through gcc in terminal. I typed in the following: "gcc ~/Desktop/testprog/main.m -o ~/Desktop/testprog/proj1 -1 -ObjC ." The first directory is that of the source file and the last one is that of the target file (i.e. the finished command line app). I am not sure what significance the "-o" and "-1" arguments have.

Similar Messages

  • Problems with ViaVoice under Leopard, especially key mapping problems

    ViaVoice's behavior has changed considerably under Leopard. First I will discuss the key mapping problem, since I'm eagerly looking for an answer to this problem. At the end of this post, I will voice some of the other problems I've experienced for those who may be interested. The key mapping problem may be specific to the fact that I use a foreign keyboard with a US version of ViaVoice.
    INTRO:
    I have used ViaVoice on my Mac for years, more or less without problems (ViaVoice's bugginess is notorious).
    Those who know ViaVoice will know that one has two general options for dictation. One can dictate into ViaVoice's so-called SpeakPad, which allows special formatting, editing and dictation error correction within the dictated text, or one can dictate into "external" software such as Microsoft Word, in which case ViaVoice just sends a string of characters to that software. SpeakPad appears to make strong use of the operating system's built-in functionality for character formatting, document formatting, etc.
    *MY PROBLEM*
    I have a German keyboard on my PowerBook, yet dictate in US English. When I dictated into SpeakPad under Tiger, all characters appeared correctly. However, when I dictated into Microsoft Word using Tiger, I had to switch the keyboard mapping from German to US to get all characters (that means including the characters that are located at different positions on a German keyboard than they are on a US keyboard such as y, z, apostrophes and parentheses) to appear correctly.
    Under Leopard, things have changed. Now it doesn't matter whether I dictate into SpeakPad or Word; the results are the same and many characters do not appear correctly.
    If set to a German keyboard, y and z appear as expected. To name a few irregularities:
    "(" appears as ")"
    ")" appears as "="
    apostrophes appear as "#" and
    ";" appears as ","
    If set to a US keyboard, y and z are interchanged. "(" and ")" appear as expected. Apostrophes appear as "\" and ";" appears as ","
    By comparison, if typed (as opposed to dictated, as in the examples above) "correctly" (i.e. based on the letters printed on the keyboard) on a German keyboard set to imitate a US keyboard:
    y and z are interchanged
    apostrophes appear as "|"
    "(" appears as "*"
    ")" appears as "(" and
    ";" appears as the symbol for "less than"
    Since I don't have a US keyboard, I can't say how it would behave if set to imitate a German keyboard, i.e. if there's a correlation to the results I get when I dictate.
    Since I was previously able to dictate correctly into SpeakPad by setting the keyboard to "German" and into Word by setting the keyboard to "US," I presume that this is a problem in Leopard, not ViaVoice.
    *OTHER PROBLEMS WITH VIAVOICE UNDER LEOPARD*
    In addition to the aforementioned key mapping problems (that may be specific to those of us with foreign keyboards), ViaVoice appears to have lost considerable functionality in Leopard. I cannot access SpeakPad's Preferences and the correction window. Moreover, the traffic-light like window buttons have disappeared from the VoiceCenter (although they work if you click where they should be). SetupAssistent appears to function.
    I've written to Nuance about these problems, but have little hope that they will invest the time in producing a patch since they haven't released any updates since 2003.

    Thrums1,
    I've never had to "register" ViaVoice after updating the system. I thus suspect you haven't fully followed my above, three-step advice (particularly step 3).
    1) Reinstall ViaVoice from CD.
    2) Update to the latest version (using the patch downloadable from Nuance's website).
    3) Replace the “temp” and “users” folders (in the "ViaVoice" folder at the upper level of your home directory) by a previous copy thereof. When I say previous copy, I mean a copy from when ViaVoice was still working properly, e.g. a copy from when it was running under Tiger.
    As I said, I've gotten ViaVoice to survive several system updates by following the above steps. To my knowledge, the last step is critical since it saves you from having to reconfigure ViaVoice under the new operating system (in this case Leopard). I suspect that ViaVoice is crashing on your system because it's trying to start some module of the SetUpAssistant that is incompatible with Leopard (as many are). If you instead use old copies of the "temp" and "users" folders (from the previous system), then ViaVoice doesn't have to go through the initial "registration" process; ViaVoice doesn't need the SetUpAssistant; and all is (more or less) fine.
    Good luck!
    BTW, to my knowledge, Dictate only runs on Intel Macs. It thus won't run on a G4 iBook, just as it won't run on my PowerBook G4.

  • Problem with gcc -pg

    Hello,
    I have a problem using profiling on solaris 8 using gcc. When I compile a small test program with gcc -g -pg, it compiles and runs correctly. However, when I build my main application using the same flags at the compilationa and likning steps, the build completes successfully but
    the application gives a segemntation fault. Is it a bug? Does gcc have a problem profiling in presence of threads or shared libs?
    Thanks in advance,
    Rajsekhar Bhattacharjee (Raj)
    The relevant details are as follows:
    OS (using uname -a): SunOS 5.8 Generic_108528-15 sun4u sparc SUNW,Sun-Blade-100
    gcc version (using gcc -v): gcc version 2.95.3 20010315 (release)
    debugger output :
    GNU gdb 5.0
    Copyright 2000 Free Software Foundation, Inc.
    GDB is free software, covered by the GNU General Public License, and you are
    welcome to change it and/or distribute copies of it under certain conditions.
    Type "show copying" to see the conditions.
    There is absolutely no warranty for GDB. Type "show warranty" for details.
    This GDB was configured as "sparc-sun-solaris2.8"...
    Core was generated by `/home/raja/zentime/bin/solaris/gprof/zentime /mnt/elmer/export/home1/TestSyst
    em'.
    Program terminated with signal 11, Segmentation Fault.
    Reading symbols from /usr/lib/libdl.so.1...done.
    Loaded symbols for /usr/lib/libdl.so.1
    Reading symbols from /usr/lib/libpthread.so.1...done.
    Loaded symbols for /usr/lib/libpthread.so.1
    Reading symbols from /usr/lib/libcurses.so.1...done.
    Loaded symbols for /usr/lib/libcurses.so.1
    Reading symbols from /usr/lib/libsocket.so.1...done.
    Loaded symbols for /usr/lib/libsocket.so.1
    Reading symbols from /usr/lib/libnsl.so.1...done.
    Loaded symbols for /usr/lib/libnsl.so.1
    Reading symbols from /usr/openwin/lib/libX11.so.4...done.
    Loaded symbols for /usr/openwin/lib/libX11.so.4
    Reading symbols from /usr/lib/libc.so.1...done.
    Loaded symbols for /usr/lib/libc.so.1
    Reading symbols from /usr/lib/libmp.so.2...done.
    Loaded symbols for /usr/lib/libmp.so.2
    Reading symbols from /usr/openwin/lib/libXext.so.0...done.
    Loaded symbols for /usr/openwin/lib/libXext.so.0
    Reading symbols from /usr/lib/libthread.so.1...done.
    Loaded symbols for /usr/lib/libthread.so.1
    Reading symbols from /usr/platform/SUNW,Ultra-1/lib/libc_psr.so.1...done.
    Loaded symbols for /usr/platform/SUNW,Ultra-1/lib/libc_psr.so.1
    #0 0xfd7dbe8c in __csigsetjmp () from /usr/lib/libthread.so.1
    (gdb)

    Hi,
    we have the same Problem with the inline assembler. We are using Sunstudio 12 on x86 and tried to get this code compiled (Sunstudio 12 should be gas compatible).
    any ideas ?
    thanks
    Dieter
    #define HEC_HTONF(x) \
    (__extension__ \
    register HVB::float32_t __v, __x = (x); \
    __asm__ ( \
    "bswap %0" \
    : "=r" (__v) \
    : "0" (__x) \
    __v; \
    #define HEC_HTONLF_INPLACE(x) \
    __asm__ ( \
    "leal %0, %%ecx \n\t" \
    "movl (%%ecx), %%eax \n\t" \
    "movl 4(%%ecx), %%edx \n\t" \
    "bswap %%eax \n\t" \
    "bswap %%edx \n\t" \
    "movl %%eax, 4(%%ecx) \n\t" \
    "movl %%edx, (%%ecx) \n\t" \
    : "=m" (x) \
    : "m" (x) \
    : "%eax", "%ecx", "%edx" \
    );

  • Problem with RFC for Risk Terminator - GRC 5.2 SP12

    We are having a problem with the RFC connection for Risk Terminator in one of our SAP environments.  It is working in our 'DV3' environment, but not in our 'RT3' environment.  Everything is set up just the same in both environments and all SAP Adaptors show green.
    This was working in RT3 when we first upgraded to GRC 5.2 last November, but it now gives me an error when I do an update with PFCG and it calls RT.  The error message and our Basis support group both say the RFC needs to be 'registered', but our SAP Support contact during our upgrade said it does not, and I can't find any documentation that says this is required also.  Plus it was working before even though it was unregistered.
    What is causing this problem and how do I resolve it?
    Also, if these RFCs do not have to be registered, is there some documentation that states this that I can show to our Basis group?
    Thanks.

    What about the question of the RFC needing to be registered?  This is the solution our Basis group thinks is required, so it will be hard to get them to do anything else until this issue has been addressed.
    Thanks.

  • Problem with gcc-like inline assembly in cc

    Hi,
    I am trying to compile the following code for a sparc machine using sun studio 12.
    #define MAGIC(n)  asm("sethi %0, %%g0" : :"g"(n));
    int main(int argc, char **argv)
            int x=1;
            MAGIC(x);
            return 0;
    }I am using the following command:
    cc -xO3 -xtarget=ultra2 -m32 -xarch=sparcvis -xregs=no%appl -w test.c -o test
    and I get the following error:
    cg error (as) : "__gnu_asm_inline_fake_test.c (template for __gnu_asm_inline_temp_func_001)", line 1 : statement syntax
    cc: cg failed for test.c
    Isn't Sun cc supposed to support gcc-like inline assembly? If so, what is the problem with the code above?
    Thanks in advance,
    Nick

    Hi,
    we have the same Problem with the inline assembler. We are using Sunstudio 12 on x86 and tried to get this code compiled (Sunstudio 12 should be gas compatible).
    any ideas ?
    thanks
    Dieter
    #define HEC_HTONF(x) \
    (__extension__ \
    register HVB::float32_t __v, __x = (x); \
    __asm__ ( \
    "bswap %0" \
    : "=r" (__v) \
    : "0" (__x) \
    __v; \
    #define HEC_HTONLF_INPLACE(x) \
    __asm__ ( \
    "leal %0, %%ecx \n\t" \
    "movl (%%ecx), %%eax \n\t" \
    "movl 4(%%ecx), %%edx \n\t" \
    "bswap %%eax \n\t" \
    "bswap %%edx \n\t" \
    "movl %%eax, 4(%%ecx) \n\t" \
    "movl %%edx, (%%ecx) \n\t" \
    : "=m" (x) \
    : "m" (x) \
    : "%eax", "%ecx", "%edx" \
    );

  • Xerox 7750 & 4500 laser printing problems with OS X Leopard

    Since upgrading to Leopard from Tiger we have experienced a number of printing issues:
    Printers rebooting each time we send a print job
    Sent print jobs appearing in the print list but not printing, then printing the second time they are sent
    The printer going to Pause on it's own
    A single copy of a document printing, but not printing when more than one copy is specified
    Our network seems OK, we are not experiencing problems file sharing or connecting to our server or the internet. The printers themselves are not that old and the have the latest firmware updates and we are using the latest Xerox drivers.
    Anyone else experience anything similar?

    It seems like it´s a problem with all Xerox Work Center drivers together with the 10.5.7 update.
    here is the configuration of our Mac where it does not work:
    Hardware-Übersicht:
    Modellname: iMac
    Modell-Identifizierung: iMac9,1
    Prozessortyp: Intel Core 2 Duo
    Prozessorgeschwindigkeit: 2.93 GHz
    Anzahl der Prozessoren: 1
    Gesamtzahl der Kerne: 2
    L2-Cache: 6 MB
    Speicher: 4 GB
    Busgeschwindigkeit: 1.07 GHz
    Boot-ROM-Version: IM91.008D.B08
    SMC-Version (System): 1.37f3
    Seriennummer (System): VM916ER40TL
    Status: Inaktiv
    Printserver: Lokal
    Treiberversion: 10.4
    Standard: Nein
    URI: lpd://192.168.73.33/
    PPD: Xerox WorkCentre 7328/7335/7345
    PPD-Dateiversion: 1.0
    PostScript-Version: (3016.103) 6
    Speicher-Steckplätze:
    ECC: Deaktiviert
    BANK 0/DIMM0:
    Größe: 2 GB
    Typ: DDR3
    Geschwindigkeit: 1067 MHz
    Status: OK
    Hersteller: 0x80AD
    Teilenummer: 0x484D54313235533641465238432D47372020
    Seriennummer: 0x25900F67
    BANK 1/DIMM0:
    Größe: 2 GB
    Typ: DDR3
    Geschwindigkeit: 1067 MHz
    Status: OK
    Hersteller: 0x80AD
    Teilenummer: 0x484D54313235533641465238432D47372020
    Seriennummer: 0x25100F65
    Seems to be like a problem of a plugin of the Xerox drivers.
    Hopefully there will be a solution soon.

  • Problems with GCC version - compiling OpenOffice

    I am trying to compile OpenOffice 4.1.1 to run on 10.6.8. When I run the ./configure it runs for a few seconds then shows the following error:
    "checking the GNU gcc compiler version... configure: error: found version "1.0.2", use version 3+ of the gcc compiler"
    If I run:
    gcc -v
    I get:
    gcc version 4.2.1 (Apple Inc. build 5659)
    Any ideas on how to fix this?
    Thanks

    I suppose the real incentive is to be able to just continue using 10.6. But it seems from other feedback that the problem with OpenOffice 4.1 is dependencies on libraries in 10.7, rather than the GCC version. I know that I could probably eventually code around those dependencies, but it would certainly involve more time and effort than I am currently able to devote to it.
    I have tried LibreOffice in the past, but frankly I found it so horrible and slow (I think because of its dependency on Java) that I ended up using the X11 version of OpenOffice - which in itself was not a terrific user experience, but was a lot better than the alternative.
    I will try the version you have mentioned, but I also note that this is planned to be obsolete by May next year, and is also the last version that will support 10.6 or 10.7 (10.8 will be the lowest requirement). Which will leave a fair number of 64-bit intel machines unsupported, since some of those are only able to run 10.7. Thanks for the feedback.

  • Problems with CS3 and Leopard

    Having a bit of a nightmare with Indesign and Photoshop CS3 since upgrading to Leopard. Running a Dual 2.5 GHz PowerPC G5 With 2GB DDR SDRAM. Anyone else having problems?

    Below is the Adobe Marketing Line (copied verbatim). It's what I was told by Adobe Sales and what I read at Adobe.com, FAQ, before buying CS3 in October 07. Imagine my surprise when I discovered all of the issues with CS3 and Leopard, even after the update to Acrobat 8.1.2 Professional which promised full compatibility (see chart at bottom).
    Apple and Adobe... ARGH.
    Oh yes, for all of the new suckers out there who are about to buy CS3 for their new Macs, the exact same FAQ is at Adobe.com, even now, Thursday, 12 Jun 2008.
    ADOBE CREATIVE SUTIE 3 Frequently Asked Questions
    Support for Mac OS X Leopard
    Q. Is Mac OS X Leopard (v10.5) important to Creative Suite 3 customers?
    A. Yes, Mac OS X Leopardthe latest version of Apples operating systemdelivers an elegant,
    productive new computing experience for creative professionals. Adobe and Apple have been
    collaborating closely for months to ensure that Adobe Creative Suite® 3 applications can run
    smoothly and reliably on Mac OS X Leopard. We are proud to support this impressive new
    operating system, and to ensure that our creative customers can take full advantage of the
    performance and value of using Creative Suite 3 applications and Mac OS X Leopard on
    Intel-based and PowerPC Macs.
    Q. Are Adobe Creative Suite 3 applications compatible with Mac OS X Leopard (v10.5)? If
    some are not fully compatible today, when will they be compatible?
    A. Thanks to close collaboration between Adobe and Apple, most of the CS3 applications and associated technologies, such as Adobe Bridge CS3, Version Cue CS3, and Device Central CS3, are compatible with Mac OS X Leopard without requiring additional updates. However, the following CS3 applications will require updates for full compatibility with Leopard: Adobe Acrobat 8 Professional and our professional video applications, including Adobe Premiere Pro CS3, After Effects CS3 Professional, Encore CS3, and Soundbooth CS3. We expect to publish free Leopard compatibility updates for the video applications in December 2007 and for Acrobat 8 Professional and Adobe Reader 8 in January 2008. For a complete overview of compatibility between Adobe creative applications and Mac OS X Leopard, see the chart on page 2 of this FAQ.
    Q. Will older versions of Adobe creative softwaresuch as Creative Suite 2 and
    Macromedia Studio 8 softwaresupport Mac OS X Leopard?
    A. While older Adobe applications may install and run on Mac OS X Leopard, they were
    designed, tested, and released to the public several years before this new operating system became available. You may, therefore, experience a variety of installation, stability, and reliability issues for which there is no resolution. Older versions of our creative software will not be updated to support Mac OS X Leopard. For a complete overview of compatibility between Adobe creative applications and Mac OS X Leopard, see the chart on page 2.
    Q. Will Adobe continue to test CS3 applications on Mac OS X Leopard?
    A. Yes. Adobe sets high standards of quality, stability, and reliability for our professional creative
    products, and we have worked closely with Apple to test Creative Suite 3 applications on both pre-release versions and the final shipping version of Mac OS X Leopard. While this testing showed that most CS3 applications perform well on Leopard (and that others run well but need updates for a few identified issues), we recognize that other issues may unexpectedly arise on any new operating system. We plan to continue testing and to monitor user experience closely to address any such issues. If you encounter any issues, please report them by going to www.adobe.com/misc/bugreport.html and clicking Report
    A Bug. Please note that we dont respond to submissions, but we do review them closely with the appropriate CS3 product teams.
    Q. Which CS3 applications will need patches to be compatible with Mac OS X Leopard?
    A. The following table summarizes compatibility between Adobe creative applications and Mac OS X Leopard. It notes which CS3 applications require updates for full Leopard compatibility and when Adobe expects to release those free updates.
    At A Glance: Mac OS X Leopard Compatibility
    ADOBE APPLICATION COMPATIBLE WITH REQUIRES UPDATE NOTES ABOUT
    Mac OS X Leopard For Mac OS X Leopard Compatibility
    Creative Suite 3 Design Premium ✔ Requires update to Acrobat 8.1.2
    Professional for full compatibility.
    Expected to be available
    in late January 2008.
    Creative Suite 3 Design Standard ✔ Requires update to Acrobat 8.1.2
    Professional for full compatibility.
    Expected to be available
    in late January 2008.
    Creative Suite 3 Web Premium ✔ Requires update to Acrobat 8.1.2
    Professional for full compatibility.
    Expected to be available
    in late January 2008.

  • Darwin and problem with gcc

    Hi,
    I'm trying to compile c-programs with gcc installed with the xtools from the tiger 1.4.8-cd on my system. For the first step I tried a "Hello World" program.
    When I compile it with 'gcc HelloWorld.cpp' on a linux system I get a a.out, and this is the program, that tells me "Hello World!".
    When I try
    "me$ gcc HelloWorld.cpp"
    on my MacBook, then I get the error message
    "/usr/bin/ld: Undefined symbols:
    __gxx_personalityv0
    collect2: ld returned 1 exit status"
    What is wrong on my system?
    Can anyone please help me to solve this problem?
    Best regards,
    Boltzmann
    The source code is ;-):
    #include<stdio.h>
    int main()
    printf("Hello World!");
    return 0;
    MacBook 13"   Mac OS X (10.4.8)   1gb ram; 1.83Mhz; 60gb disk space

    Name the file HelloWorld.c; .cpp is for C++. If you want to compile C++, use g++, which links to the proper libraries for C++.

  • Serious problems with mac snow leopard

    I am having some very serious problems with my Wireless USB internet device (BSNL EVDO AC8799 ZTE make) and Mac. Everytimes it freezes my mac asks me to restart.. works fine on windows 7 installed via boot camp.
    attaching error pic and log:
    here is the error log:
    Interval Since Last Panic Report:  28425 sec
    Panics Since Last Report:          4
    Anonymous UUID:                    F548AB92-4576-4F47-9CA1-60D91BD3FB94
    Sun Jul 10 23:35:44 2011
    panic(cpu 0 caller 0xffffff80002d1208): Kernel trap at 0xffffff7f808541f9, type 14=page fault, registers:
    CR0: 0x000000008001003b, CR2: 0xffffff805f8740e0, CR3: 0x0000000000100000, CR4: 0x0000000000040660
    RAX: 0x0000000009b3ffc5, RBX: 0x0000000000000000, RCX: 0x0000000018000040, RDX: 0x0000000010000000
    RSP: 0xffffff805f873f30, RBP: 0xffffff805f873fa0, RSI: 0x0000000000000000, RDI: 0x0000000000020006
    R8:  0x0000000000000003, R9:  0x0000000000000001, R10: 0x0000000000000007, R11: 0xffffff80004f4ece
    R12: 0x0000000004000000, R13: 0xffffff805f873f20, R14: 0x000000000e000040, R15: 0xffffff800cd43cf0
    RFL: 0x0000000000010246, RIP: 0xffffff7f808541f9, CS:  0x0000000000000008, SS:  0x0000000000000010
    Error code: 0x0000000000000000
    Backtrace (CPU 0), Frame : Return Address
    0xffffff805f873bd0 : 0xffffff8000204d15
    0xffffff805f873cd0 : 0xffffff80002d1208
    0xffffff805f873e20 : 0xffffff80002e3f4a
    0xffffff805f873e30 : 0xffffff7f808541f9
    0xffffff805f873fa0 : 0xffffff80002c8527
          Kernel Extensions in backtrace (with dependencies):
             com.apple.iokit.IOSerialFamily(10.0.3)@0xffffff7f80851000->0xffffff7f8085afff
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    10K540
    Kernel version:
    Darwin Kernel Version 10.8.0: Tue Jun  7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64
    System model name: MacBookPro8,1 (Mac-94245B3640C91C81)
    System uptime in nanoseconds: 7923118028595
    unloaded kexts:
    com.ZTE.driver.ModemDriverMacEx          1.0.6d1 (addr 0xffffff7f8085b000, size 0x28672) - last unloaded 798326091621
    loaded kexts:
    com.ZTE.driver.ModemDriverMacEx          1.0.6d1 - last loaded 7633147910063
    com.regularrateandrhythm.driver.RowmoteIREmu          1.0
    com.parallels.kext.prl_vnic          6.0 11994.637263
    com.parallels.kext.prl_netbridge          6.0 11994.637263
    com.parallels.kext.prl_usb_connect          6.0 11994.637263
    com.parallels.kext.prl_hid_hook          6.0 11994.637263
    com.parallels.kext.prl_hypervisor          6.0 11994.637263
    com.apple.driver.AppleHWSensor          1.9.3d0
    com.apple.filesystems.ntfs          3.4
    com.apple.driver.AGPM          100.12.31
    com.apple.driver.AppleMikeyHIDDriver          1.2.0
    com.apple.driver.AppleHDA          2.0.5f13
    com.apple.driver.AppleMikeyDriver          2.0.5f13
    com.apple.driver.AppleUpstreamUserClient          3.5.7
    com.apple.driver.AppleMCCSControl          1.0.20
    com.apple.driver.AudioAUUC          1.57
    com.apple.driver.SMCMotionSensor          3.0.1d2
    com.apple.filesystems.autofs          2.1.0
    com.apple.driver.AppleIntelHDGraphics          6.3.6
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.AudioIPCDriver          1.1.6
    com.apple.driver.ACPI_SMC_PlatformPlugin          4.7.0a1
    com.apple.driver.AppleLPC          1.5.1
    com.apple.driver.AppleBacklight          170.0.46
    com.apple.kext.AppleSMCLMU          1.5.2d10
    com.apple.driver.AppleIntelSNBGraphicsFB          6.3.6
    com.apple.driver.AppleUSBTCButtons          201.6
    com.apple.driver.AppleUSBTCKeyboard          201.6
    com.apple.driver.AppleIRController          303.8
    com.apple.iokit.SCSITaskUserClient          2.6.8
    com.apple.iokit.IOAHCIBlockStorage          1.6.4
    com.apple.BootCache          31.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.driver.AppleFWOHCI          4.7.3
    com.apple.driver.AirPort.Brcm4331          433.11.5
    com.apple.driver.AppleSDXC          1.0.3
    com.apple.iokit.AppleBCM5701Ethernet          3.0.5b8
    com.apple.driver.AppleEFINVRAM          1.4.0
    com.apple.driver.AppleUSBHub          4.2.4
    com.apple.driver.AppleSmartBatteryManager          160.0.0
    com.apple.driver.AppleRTC          1.3.1
    com.apple.driver.AppleAHCIPort          2.1.7
    com.apple.driver.AppleACPIButtons          1.3.6
    com.apple.driver.AppleUSBEHCI          4.2.4
    com.apple.driver.AppleHPET          1.5
    com.apple.driver.AppleSMBIOS          1.7
    com.apple.driver.AppleACPIEC          1.3.6
    com.apple.driver.AppleAPIC          1.4
    com.apple.driver.AppleIntelCPUPowerManagementClient          142.6.0
    com.apple.security.sandbox          1
    com.apple.security.quarantine          0
    com.apple.nke.applicationfirewall          2.1.12
    com.apple.driver.AppleIntelCPUPowerManagement          142.6.0
    com.apple.nke.ppp          1.5
    com.apple.driver.AppleProfileReadCounterAction          17
    com.apple.driver.DspFuncLib          2.0.5f13
    com.apple.driver.AppleProfileTimestampAction          10
    com.apple.driver.AppleProfileThreadInfoAction          14
    com.apple.driver.AppleProfileRegisterStateAction          10
    com.apple.driver.AppleProfileKEventAction          10
    com.apple.driver.AppleProfileCallstackAction          20
    com.apple.driver.AppleSMBusController          1.0.10d0
    com.apple.iokit.IOFireWireIP          2.0.3
    com.apple.iokit.IOSurface          74.2
    com.apple.iokit.IOBluetoothSerialManager          2.4.5f3
    com.apple.iokit.IOSerialFamily          10.0.3
    com.apple.iokit.IOAudioFamily          1.8.3fc2
    com.apple.kext.OSvKernDSPLib          1.3
    com.apple.driver.AppleHDAController          2.0.5f13
    com.apple.iokit.IOHDAFamily          2.0.5f13
    com.apple.iokit.AppleProfileFamily          41
    com.apple.driver.IOPlatformPluginFamily          4.7.0a1
    com.apple.driver.AppleSMBusPCI          1.0.10d0
    com.apple.driver.AppleBacklightExpert          1.0.1
    com.apple.iokit.IONDRVSupport          2.2
    com.apple.driver.AppleSMC          3.1.0d5
    com.apple.iokit.IOGraphicsFamily          2.2
    com.apple.driver.AppleThunderboltDPOutAdapter          1.3.2
    com.apple.driver.AppleThunderboltDPInAdapter          1.3.2
    com.apple.driver.AppleThunderboltDPAdapterFamily          1.3.2
    com.apple.driver.AppleThunderboltPCIDownAdapter          1.1.6
    com.apple.driver.BroadcomUSBBluetoothHCIController          2.4.5f3
    com.apple.driver.AppleUSBBluetoothHCIController          2.4.5f3
    com.apple.iokit.IOBluetoothFamily          2.4.5f3
    com.apple.driver.AppleUSBMultitouch          207.7
    com.apple.iokit.IOUSBHIDDriver          4.2.0
    com.apple.driver.AppleUSBMergeNub          4.2.4
    com.apple.driver.AppleUSBComposite          3.9.0
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          2.6.8
    com.apple.iokit.IOBDStorageFamily          1.6
    com.apple.iokit.IODVDStorageFamily          1.6
    com.apple.iokit.IOCDStorageFamily          1.6.1
    com.apple.driver.XsanFilter          402.1
    com.apple.iokit.IOAHCISerialATAPI          1.2.6
    com.apple.iokit.IOSCSIArchitectureModelFamily          2.6.8
    com.apple.driver.AppleThunderboltNHI          1.2.6
    com.apple.iokit.IOThunderboltFamily          1.4.9
    com.apple.iokit.IOFireWireFamily          4.2.6
    com.apple.iokit.IO80211Family          320.1
    com.apple.iokit.IONetworkingFamily          1.10
    com.apple.iokit.IOUSBUserClient          4.2.4
    com.apple.iokit.IOAHCIFamily          2.0.6
    com.apple.driver.AppleEFIRuntime          1.4.0
    com.apple.iokit.IOHIDFamily          1.6.6
    com.apple.iokit.IOUSBFamily          4.2.4
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          6
    com.apple.driver.DiskImages          289
    com.apple.iokit.IOStorageFamily          1.6.3
    com.apple.driver.AppleACPIPlatform          1.3.6
    com.apple.iokit.IOPCIFamily          2.6.5
    com.apple.iokit.IOACPIFamily          1.3.0
    Model: MacBookPro8,1, BootROM MBP81.0047.B0E, 2 processors, Intel Core i7, 2.7 GHz, 4 GB, SMC 1.68f96
    Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB
    Memory Module: global_name
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 5.100.198.104.5)
    Bluetooth: Version 2.4.5f3, 2 service, 12 devices, 1 incoming serial ports
    Serial ATA Device: Hitachi HTS545050B9A302, 465.76 GB
    Serial ATA Device: MATSHITADVD-R   UJ-898
    USB Device: FaceTime HD Camera (Built-in), 0x05ac  (Apple Inc.), 0x8509, 0xfa200000 / 3
    USB Device: Hub, 0x0424  (SMSC), 0x2513, 0xfa100000 / 2
    USB Device: Apple Internal Keyboard / Trackpad, 0x05ac  (Apple Inc.), 0x0245, 0xfa120000 / 5
    USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 4
    USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x821a, 0xfa113000 / 7
    USB Device: Hub, 0x0424  (SMSC), 0x2513, 0xfd100000 / 2
    USB Device: IR Receiver, 0x05ac  (Apple Inc.), 0x8242, 0xfd110000 / 3

    t33n-iv wrote:
    i am facing problem only when i have internet working on this device. no other user using this device and snow leopard are facing same problem. just because of freezing i have to use stupid windows on my new macbook pro!
    ur reply was helpful, but how should i rectify this problem?
    Have you looked at the manufacturer's website to see if there is an updated driver for it?
    If that doesn't work, I do not know which of the KP troubleshooting steps might resolve the issue. In your place, I would try each one.

  • So clearly there's a problem with WiFi and Leopard.....

    ...that is affecting a subset of us. This problem is driving me nuts, and I've searched this board, as well as many others aggressively for a fix. So far, I've only found a few work-arounds, that don't really work.
    The question is, are we certain that Apple has picked up this issue and is working on it? Any comments?

    I am now having problems with my imac (2.16 core two duo, 20") running 10.5.1. I have been using this imac for nearly a year now with a wireless coneection and have never had a problem. I installed Leopard a month ago and have had no problems.
    Yesterday I noticed my connection drop several times but I could always get it back. I have a good wireless connection on my ibook so I know my router is good. This morning my imac dropped the wireless connection and I cannot get it back. I had to run an ethernet cable to regain my connection.
    It seems from a quick look around the boards that this problem is plaguing imacs only. I have noticed this problem happening with imacs running leopard and tiger. Hope a solution is found soon.
    EDIT: I restarted the imac and my airport connection returned. I hope this doesn't become a regular thing.
    Message was edited by: Dread Pirate Roberts

  • "Invalid password" intermittent problem with MBP Snow Leopard Netgear

    This is driving me mad, please help.
    My MacbookPro (new, Sept '10, Snow Leopard) has intermittent connection problems with my Netgear wireless-N 300 router. Everything works fine a lot of the time. I put the computer to sleep, and next time I open it, I bite my nails to see if it will connect or not. Today, it's not. And there's no logical reason why. What's maddening is that I get an Airport "Invalid Password" error when trying to connect, when I'm using the right password and it has connected automatically before. I will sometimes have success by restarting the computer, or by restarting the computer AND the modem, or by resetting the modem. But sometimes I don't have that success, and today is one of those days.
    Now, I also have an older Macbook Pro (Mar '08, Leopard) that NEVER has a problem connecting. So I know it's a Snow Leopard issue.
    I have tried changing the channel in the router's wireless settings (including to Auto). I have tried deleting the keychain item for the router's wireless. I still get the "Invalid Password" error.
    The irony is that the whole time, I'm updating the router via the old MBP which has no problems with ANY of the settings. That's what I'm writing this on. But I need the other computer to get online. It's getting ridiculous.
    I CAN connect by connecting an Ethernet cable to the router, but that kind of defeats the purpose of going wireless.
    Please help. Any suggestions are greatly appreciated.

    First log into your router and make sure it is up to the current time and maybe sync it to a Time Server. Then on your Mac open System Preferences->Network. At the top of the pane is the "Location" drop-down. Use that drop-down to make a new custom Location calling it whatever you like. Then at the bottom Network pane click on the 'Apply' button to save this new custom Location you made. Then use the Network pane to rejoin your wireless network.
    Also in System preferences->Date & time and make sure it is set to your current living Location. Plus open /Applications/Utilities/Keychain Access. In this program first click on the menu item "Keychain Access" and select "Keychain First Aid". Then go to the entry for you wireless network and delete it. Then the wireless connection should ask you again to save the password, only once, hopefully.
    Good Luck.

  • Triggering Problems with a SCB-68 Terminal

    Hello
    I nedd some suggestions about triggering with a SCB-68 terminal.
    I would like to make a triggered aquisition. I need to use to poles? That is, I nedd to connect the high digital pole (+5V) to the PFI0 screw terminal and the low pole (+0V) to the pin# 44 or is enough to connect the sole high pole to PFI0.
    If I measure voltage between pin#11 (PFI0) and pin#44 (GND) I get +5 V. Is that correct? How can I trigger my acquisition with a digital signal of +5V if the PFI0 already is at +5V?
    I don't understand
    Hope someone kindly help me.
    Thanks
    Moreno

    Thank you so much for the answer.
    There was a bad explanation maybe. I'm really using a trigger form +0V to +5V. The most important thing that I would like to know is: is correct the between PFI0 and the pin#11 (DGND) there are +5V without any external connection (at open circuit)
    Thanks a lot
    Moreno

  • I have a problem with a snow leopard to mountain lion upgrade. Any suggestions?

    I have a late 2007 I-Mac currently running snow leopard. My computer meets the requirements for RAM, available disk space, etc. to upgrade to Mountain Lion. I also have a new Mac Book Pro that I just updated the Mountain Lion software on. I have followed the steps outlined by Apple as follows.
    To install OS X Lion or Mountain Lion on another Mac, open the Mac App Store, sign in to your account, and re-download the OS by selecting it in the Purchases list. Follow these steps:
    Download Lion or Mountain Lion from the Mac App Store on one of your personal authorized Macs. The download is approximately 4 GB in size.
    Install the OS.
    Log in to another computer that you wish to install it on.
    Open the Mac App Store. Enter your Apple ID and password that was used to download either Lion or Mountain Lion on the first computer.
    Click the Purchased icon, then click the download link for the appropriate OS.
    The problem I continue to have is that the program will act like it's going to download and will say it's downloading then after approximately 10 minutes the App Store no longer says the program is downloading and I again get the green box to "install app".
    I have made sure to update my software and I have the latest updates 10.6.8 for snow leopard. I have also disabled the anti virus program. Any suggestions??

    If you are willing to experiment:
    Unfortunately, the link for getting specific hardware versions has disappeared. So basically:
      1. Get yourself a spare hard drive freshly erased or with a freshly erased partition of
          around 8 GBs or more.
      2. Boot to your Recovery HD. Select Reinstall Lion from the main menu.
      3. From the beginning screen select your spare partition/drive as the target
          destination then begin the download.
      4. At the end of the download you will observe an Install button for you to click.
          Now this is important - as soon as that gadget appears you must abort the
          installation process. There are only two reliable ways to do this quickly: (a.) yank
          the cable for the drive from the computer; (b.) pull the power on the computer -
          shut it down quickly.
    This will result in your finding a folder on the drive that contains InstallESD.dmg that you can now use to create a bootable USB flash drive installer based on the special build for your model. Use it until the next public release of Lion appears or you move on to Mountain Lion.
    If you do not stop the download process immediately upon its completion you will end up with an installer that always boots to a non-functioning installation progress window instead of the normal main menu.
    Make Your Own Mountain/Lion Installer
    1. After downloading Mountain/Lion you must first save the Install Mac OS X Mountain/
        Lion application. After Mountain/Lion downloads DO NOT click on the Install button.
        Go to your Applications folder and make a copy of the Mountain/Lion installer. Move
        the copy into your Downloads folder. Now you can click on the Install button. You
        must do this because the installer deletes itself automatically when it finishes
        installing.
    2. Get a USB flash drive that is at least 8 GBs. Prep this flash drive as follows:
      a. Open Disk Utility in your Utilities folder.
      b. After DU loads select your flash drive (this is the entry with the mfgr.'s ID and size) from the left
          side list. Click on the Partition tab in the DU main window.
      c. Under the Volume Scheme heading set the number of partitions from the drop down menu to one.     
          Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the
          partition scheme to GUID then click on the OK button. Click on the Partition button and wait until
          the process has completed.
      d. Select the volume you just created (this is the sub-entry under the drive entry) from the left side
          list. Click on the Erase tab in the DU main window.
      e. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the
          button for Zero Data and click on OK to return to the Erase window.
      f. Click on the Erase button. The format process can take up to an hour depending upon the flash
         drive size.
    3. Locate the saved Mountain/Lion installer in your Downloads folder. CTRL- or RIGHT-click on the installer and select Show Package Contents from the contextual menu. Double-click on the Contents folder to open it. Double-click on the SharedSupport folder. In this folder you will see a disc image named InstallESD.dmg.
    4. Plug in your freshly prepared USB flash drive. You are going to clone the content of the InstallESD.dmg disc image to the flash drive as follows:
      a. Double-click on the InstallESD.dmg file to mount it on your Desktop.
      b. Open Disk Utility.
      c. Select the USB flash drive from the left side list.
      d. Click on the Restore tab in the DU main window.
      e. Select the USB flash drive volume from the left side list and drag it to the Destination entry field.
      f. Drag the mounted disc icon from the Desktop into the Source entry field.
      g. Double-check you got it right, then click on the Restore button.
    When the clone is completed you have a fully bootable installer that you can use without having to re-download Mountain/Lion.
    Note: The term Mountain/Lion used above means Lion or Mountain Lion.
    As an alternative to the above you can try using Lion DiskMaker 2.0 that automates the process.

  • Problems with BNC and chassis termination

    Hi All,
    forgive me if this is the wrong forum but i assume someone here from a test and measurement background will be able to help.
    I am trying to measure leakage current using a source meter and electrometer. The problem i have is that the termination method of my instruments is BNC. The DUT i am measuring is inside a shielded diecast box. In order to make my measurement i am using the chassis and the outer core of the coax cable as the reutn path. However i do not know if this will increase noise within the measurement. I am measuring currents in the Nanoamp region.
    Also from a safety point of view i am using high voltage and having the return path going through the diecast box does not sit well with me.
    Does anyone have any opinions on this or can advise on a better solution?
    Thank You
    Andy
    Here is a diagram of what i am doing
    https://forums.tm.agilent.com/community/download/file.php?id=8518&mode=view: https://forums.tm.agilent.com/community/download/file.php?id=8518&mode=view

    Yes i have tried this setup and i do get measurments in approximate range. The trouble is its a leakage current test in the Nanoamp range, ideally the leakage should be as small as possible but i am concerned that the config/setup is causing or adding an error to the  reading.
    Also i have concerns over the safet of the setup. The only NI product i am using is labview 8.5 to control the instruments but this post is not really a software issue.
    Thanks

Maybe you are looking for