Itunes on x64 platform

I'm about to do a clean install of my system (Dell Precision T5400 64-bit system with 2 300GB drives setup in a RAID 1 mirror and 8GB of memory). I will be running XP Pro x64 Edition with Service Pack 2.
I have had itunes running over the last year fine, but I remember the install process was relatively difficult to get it running on a x64 XP system.
Is itunes now supported on a x64 version of XP? If not, can someone point me to the instructions for the correct installation steps? I had to use Orca and 7-Zip File Manager to get it installed correctly last time. I'm hoping there is an easier process now.
Thanks.

iTunes versions 9.0.x have been tricky for folks using the Orca workarounds for XP 64-bit. The iPod Service has gone 64-bit in the new versions which adds some complexity to proceedings by comparison to the versions 8.x.
I've seen a claimed procedure here for 9.0.x:
http://discussions.apple.com/thread.jspa?threadID=2360631&tstart=75
... but +caveat emptor,+ as always. (That's certainly not the most detailed Orca procedure I've ever seen.)

Similar Messages

  • ITunes (Win7 x64) is no longer opening after the latest version update

    iTunes (Win7 x64) is no longer opening after the latest version update - I have attempted an un/reinstall - can anyone offer other suggestions?
    I am running Windows 7 64-bit, and am trying to reinstall the 64-bit iTunes from the iTunes website.  I previously have had this working for the last few years with no major issues, the Apple Software Updater has been pestering me for some time so I finally got it to update.  However now iTunes will not start, if I select the icons nothing happens.  There are no iTunes applications running in the background in Task Manager either.
    I look forward to your suggestions.
    Thanks,
    James.

    1. First check if this file APSDaemon.exe is the problem here.
    Close your iTunes.
    Press Ctrl-Alt-Del key and choose Task Manager. In the "Processes" Tab, select the file APSDaemon.exe and click End Prosses button, then close the task manager window.
    Now open itunes and see if it is working?
    If that works, to prevent having to do the same process everytime you restart Windows, go to. START button, type in
    MSCONFIG
    Hit ENTER
    Click STARTUP Tab, Uncheck "Apple Push", click OK.
    Restart Windows.
    2. If that fails, refer to following article to remove SC Files
    http://support.apple.com/kb/TS2363
    3.  If that fails, repair or reinstall your Quicktime.  START / CONTROL PANEL / PROGRAMS N FEATURES / hightlight QUICKTIME and click REAPIR.

  • Please help!!! Cant install itunes 10 x64

    Any help would be greatly appreciated. I cannot install itunes 10 x64. Keep getting error message saying bonjour services failed to start make sure you have sufficiant privelages. I have tried every fix i have seen including disabling my firewall and anti-virus, disabling bonjour service, uninstalling itunes and all traces of other programs. I just purchased an iPad and have yet to be able to sync content from my itunes library becuase i cant install it. I am losing my mind over this and would very much appreciate any help. Very irritating having brand new iPad and not being able to sync. Thank you

    Bonjour, j'ai eu le même problème et je n'ai pas trouvé de solutions. Je te conseille d'utiliser atunes pour gérer la musique et sharepod pour actualiser ton ipod

  • OCIServerAttach() coredump with Oracle10.2 64bit on X64 platform

    hi, i get a problem using OCI to connect to server. On X64 platform, Solaris10 system, and 64bit Oracle10.2 release, when i use OCIServerAttach() to attach a server, it will core dump. However, with the same code and same Oracle version, on a spark platform, it works well.My code is 32bit, so it depens on $ORACLE_HOME/lib32/libclntsh.so.10.1. Under Spark platform it works,but under x64 platform it will coredump. I copied a libclntsh.so.10.1 from a 32bit Oracle 10.2 client instance $ORACLE_HOME/lib on X86 platform to the X64 $ORACLE_HOME/lib32, the code then works. Why?
    My code:
    OCIEnv      *m_pEnvHandle;               
    OCIError      *m_pErrHandle;               
    OCIServer      *m_pSrvHandle;               
    OCISvcCtx      *m_pSvcHandle;               
    const char* i_pszSrv = "iccshis";
    OCIEnvCreate(&m_pEnvHandle, OCI_THREADED|OCI_OBJECT, (dvoid *)0,
                   0, 0, 0, (size_t) 0, (dvoid **)0);
    OCIHandleAlloc((dvoid*)m_pEnvHandle, (dvoid**)&m_pErrHandle,
                   OCI_HTYPE_ERROR, (size_t)0, (dvoid**)0);
    OCIHandleAlloc((dvoid*)m_pEnvHandle, (dvoid**)&m_pSrvHandle,
                   OCI_HTYPE_SERVER, (size_t)0, (dvoid**)0);
    OCIServerAttach(m_pSrvHandle, m_pErrHandle, (text*)i_pszSrv, strlen((char*)i_pszSrv), OCI_DEFAULT);
    The stack back trace when the programme core dumped:
    00000000 ???????? (fb1f3430, 0, 804068c, 822e1d8, b, 8040690)
    fa996a3f nnfgrne (fb1f3430, 8043058, 0, fb1b5e38, 0, 8040e00) + 25b
    faa0b30d nlolgobj (fb1f3430, 8043058, 16, 8040e64, 8040e68) + 669
    fa9951ab nnfun2a (fb1f3430, 8043058, ff, 8043034, 8040ef0, 1000) + 15b
    fa994e9e nnfsn2a (fb1f3430, 8043058, ff, 8043034, 8040ef0, 1000) + 36
    fa983f97 niqname (fb1f3430, 1001, 8043058, 7, c0e887c, 8046290) + 2fb
    fa8cfd38 kwfnran (9721ba8, 7, 804628c, 8046290, c0ee8bc, c0ee8c0) + 168
    fa8a7b33 kwfcinit (c0e475c, 9721ba8, 7, 804628c, 8046290, be896d0) + 1b7
    fa726f04 kpuatch (c0e475c, c0e41d0, 9721ba8, 7, 0, 0) + 7c0
    fa7e6f06 OCIServerAttach (c0e475c, c0e41d0, 9721ba8, 7, 0, 0) + 56
    f7574b07 bool COracleDBI::Open(const char*,const char*,const char*) (be7c998, 9721ba8, 89b6d90, 95f7170) + 12f;
    Can anybody tell me why? thanks.

    I'd hesitate to use SQL*Plus to determine a failure on this single OCI call.
    While I haven't checked lately, the last time I looked, SQL*Plus didn't use OCIServerAttach. Instead, it used UPI to perform most connection and session initialization and then converted its handles for use by OCI calls. Like I said, it may work, but this is a very basic call that should work.
    I know a couple people who worked at Oracle and based on their information, I believe it would be nearly impossible for this blatant of a bug to pass regression. I'd opt for trying one of the OCI demo programs to see if this same issue can be replicated.
    Just my 2 cents :)

  • WCFServiceApplication and x64 platform

    I have a WCFservice application that will not compile when I change the solution to x64 platform. My ultimate goal is to get the WCFApplicaion to reference a EDidEv.FrameworkEDI.Net4.X64.dll. I get an error of "
    An attempt was made to load a program with an incorrect format"
    Please help me in getting WCFservice to use a x64 platform.   Thank you

    Hi,
    If you are using Any CPU, you might encounter this issue if the Prefer 32-bit option is checked:
    Make sure you uncheck this option then have a try about.
    Besides, you could clean the solution and rebuild it.
    Regards

  • Unresolved external symbol NumericArrayResize when compiling a DLL at x64 platform using vs2005

    I have a dll which is called by Labview through "Call Library Function Node". I want to port this dll to x64 platform from 32bit code which runs well at x86 computer. So, I download the Labview 8.5 evaluation version, replace the orginal referenced header file and library file in 32 bit code, such as extcode.h, fundtypes.h, labview.lib etc. Then I compile the code with Visual Studio 2005, error occurs when link "error LNK2001: unresolved external symbol NumericArrayResize". I don't know why because I really link library labview.lib. Can anyone help me?

    Please check the solution in this thread, this may help you solve your problem.
    http://stackoverflow.com/questions/925540/how-to-resolve-the-following-linker-errors-in-visual-studio
    If you still get the same problem after try the solution, please feel free and let me know.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • How about gccfss for Solaris x86/x64 platforms?

    Subject says it all... it could make compiling a lot of code out there a whole lot easier!
    Bob

    I also desire gccfss for Solaris x86/x64 platforms .
    In the interim I have downloaded the source and am attempting to create such a beast.
    It is slow progress to fix the unexpected script breakage, but it seems to be going OK:
    Problems:
    1.): Issues like "-mtune=v9" and an "embeded spec" in gcc and cpp (from files
    gccfss_src/build/gcc/gccspec.o and gccfss_src/build/gcc/cppspec.o).
    2.): Use of OPTTABLE_H = $(srcdir)/config/target-option-table.h with SPARC specific
    options throughout
    EG:
    #ifdef CROSS_COMPILE
    #define NATIVE \
    { "-native", "-xtarget=generic" }, \
    { "-xarch=native64", "-Zarch=v9 -Zarchm64=v9 -Zm=64" },\
    { "-xarch=native", "-Zarch=v8plus -Zarchm32=v8plus -Zarchm64=v9 -Zm=32" },\
    { "-xtarget=native64", "-Zarch=generic -Zarchm32=generic -Zarchm64=v9 -xchip=generic -xcache=generic -Zm=64"}, \
    { "-xtarget=native", "-Zarch=generic -Zarchm32=generic -Zarchm64=v9 -xchip=generic -xcache=generic -Zm=32"}
    #else
    #define NATIVE \
    { "-native", "-xtarget=native" }, \
    { "-xarch=native64", "-xarch=native64 -Zm=64"}, \
    { "-xarch=native", "-xarch=native -Zm=32"}, \
    { "-xtarget=native64", "-xtarget=native64 -Zm=64"}, \
    { "-xtarget=native", "-xtarget=native -Zm=32"}
    #endif
    Thus, one would need to change:
    { "-xarch=native64", "-Zarch=v9 -Zarchm64=v9 -Zm=64" },\
    to something like:
    { "-xarch=native64", "-xarch=386 -m64" },\
    3.): Copy the "sparc_output_scratch_registers()" function from file
    "gccfss_src/src/gcc/config/sparc/sparc.c" to "gccfss_src/src/gcc/tree-ir.c".
    4.): Use the undocumented command line option "-frtl-backend" when this error
    occurs during the build (a simple Makefile change):
    `-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead.
    xgcc: SUNW0scgfss 4.2.0 has not been installed. Either install it or use -frtl-backend.
    5.): More ...
    All these issues occur because the scripts expect "--build=sparc-pc-solaris2.11" but
    I configured using "--build=i386-pc-solaris2.11" . It seems like it is going to work
    but I am yet to finish stage1 of the build (I do have a working "xgcc").
    Rob

  • Tons of problems iTunes + W7 x64! HELP!

    I am currently running a custom build:
    Intel i5 Sandy Bridge 2500k
    CORSAIR DOMINATOR 4GB (2 x 2GB) 240-Pin DDR3 SDRAM
    SeaGate Barracuda 1TB 7200RPM
    XFX HD Radeon 6870
    CORSAIR Professional Series 750W
    MSI P67 LGA1155
    Windows 7 Ultimate x64
    (Yes I am a victim of the infamous SATA port problem :[ but NewEgg is sending me a new one.)
    I'm currently a lot of problems with iTunes x64. One is that iTunes turns of Aero every time I boot it up (if my PC can handle Crysis at max settings I doubt iTunes would break my video card), but that's not the pressing issue that is easily fixed with quickly running the Aero troubleshooter.
    The more pressing issue here is that iTunes has started to refuse to play my songs. This is a very recent and very annoying problem. What happens is I'll be listening to my music and around 10 minutes in give or take a few minutes the song just stops. I try to hit pause or play and it refuses to play, when I change the song or anything it also refuses to play those songs. It's not until I restart iTunes, fix Aero again, that a new song will play and then in another 10 minutes the same thing happens. Please tell me that other people are having this problem and that there is some sort of solution. Any ideas are much appreciated.

    When it says to make a playlist, it means your library is bigger than the free space on your ipod. Make a playlist of all the songs you want on your ipod. You wont be able to fit all of them, just fit as many as you can.
    Also, the volume is the sound. at the top next to the play button, slide the knob over to the right a little.

  • Installing iTunes with x64 XP Pro

    How can I install iTunes on a system that is running x64 XP Pro. It keeps telling me that its not compatible. Is it compatible or are there different drivers I need to download and install?
      Windows XP Pro  

    ... for instructions on how to provide a screenshot, see this user tip:
    hudgie: Taking screenshots to help with problems

  • Syncing iTunes across Different Platforms (Windws & PC) - Mac Version

    I'm not sure where to put this questions so I'm adding it to the iTunes for Windows section as well. I have an iTouch that I have been using on my Windows platform iTunes. In addition to music, I also use iTunes to sync up my contacts and calendar list from Microsoft Office Outlook to my Touch.
    Last week I switched to Mac and ported all my music to a new iTunes libary on my Mac. Due to issues with Office I can not use the Mac ver of office for my contacts and calendar.
    I loaded VMware Fusion and Windows XP on my Mac and installed iTunes for Windows. I did not move any music, podcasts, etc... over to the Fusion/Windows iTunes - only my contacts and calendar info is on that version.
    Now I have two instances of iTunes on my Mac... a Mac version and a Windows version under Fusion.
    What I would like to do is:
    - Sync my iTouch for Music only using the iTunes running under Mac.
    - Sync my iTouch to the Windows version under Fusion for the contact list and calendar updates. This version will not have any music in the library.
    Questions:
    1) Can I do this without causing a melt down on my touch?
    2) What happens when you sync to a library without music? Does it erase the music on the touch?
    3) I haven't tried to sync my touch to the Mac yet- what will happen when a windows based touch tries to load a mac based iTunes?
    If this doesnt work I guess I could reload all my music to the Fusion(PC) version of iTunes and be done with it but I would really like to use my Mac version.
    Thanks,
    Jim

    You have got to be kidding! I have been trying for months to do this between my three machines. What exactly is the point to having an iTunes account for multiple machines if you can not have the same library across them? If this isn't the stupidest thing I've come across in years, honest to Pete...
    What if I use a thumb drive to keep the directories manually synced? Or does apple go the extra step to prevent this too? Can you point to a library through the intranet? I could just put up a server and point my machines to it, boy wouldn't that be speedy and elegant.
    I just want to scream this is so annoying. I might as well go back to a system that works, a Windows phone... The iPhone isn't that much nicer than my old tilt.

  • Syncing iTunes across Different Platforms (Windws & PC) - Windows Version

    Im not sure where to put this questions so I'm adding it to the iTunes for Mac secion as well. I have an iTouch that I have been using on my Windows platform iTunes. In addition to music, I also use iTunes to sync up my contacts and calendar list from Micosoft Office Oulook to my Touch.
    Last week I switched to Mac and ported all my music to a new iTunes libary on my Mac. Due to issues with Office I can not use the Mac ver of office for my contacts and calendar.
    I loaded VMware Fusion and Windows XP on my Mac and installed iTunes for Windows. I did not move any music, podcasts, etc... over to the Fusion/Windows iTunes - only my contacts and calendar info is on that version.
    Now I have two instances of iTunes on my Mac... a Mac version and a Windows version under Fusion.
    What I would like to do is:
    - Sync my iTouch for Music only using the iTunes running under Mac.
    - Sync my iTouch to the Windows version under Fusion for the contact list and calendar updates. This version will not have any music in the library.
    Questions:
    1) Can I do this without causing a melt down on my touch?
    2) What happens when you sync to a library without music? Does it erase the music on the touch?
    3) I havent tried to sync my touch to the Mac yet- what will happen when a windows based touch tries to load a mac based iTunes?
    If this doesnt work I guess I could reload all my music to the Fusion(PC) version of iTunes and be done with it but I would really like to use my Mac version.
    Thanks,
    Jim

    You have got to be kidding! I have been trying for months to do this between my three machines. What exactly is the point to having an iTunes account for multiple machines if you can not have the same library across them? If this isn't the stupidest thing I've come across in years, honest to Pete...
    What if I use a thumb drive to keep the directories manually synced? Or does apple go the extra step to prevent this too? Can you point to a library through the intranet? I could just put up a server and point my machines to it, boy wouldn't that be speedy and elegant.
    I just want to scream this is so annoying. I might as well go back to a system that works, a Windows phone... The iPhone isn't that much nicer than my old tilt.

  • [SOLVED]Building UEFI (EDK II) for x64 platform

    HI,
    I am trying to build the EDK II source for an x86 platform. I am carrying out the following steps from the release notes for Unix Systems. My OS is Linux 2.6.32
    ===============================================================================
                             HOW TO BUILD (UNIX-LIKE SYSTEM)
    ================================================================================
    Unix-Like System Configuration:
      DistributorID: Ubuntu
      Description:   Ubuntu 9.10
      Release:       Ubuntu 9.10
      Codename:      Karmic
    1.  Extract Common Source Code
        1)  Create a working space directory in the build machine, for example, ~/src/MyWorkspace
        2)  Extract files in [UDK2010.UP4] to the working space directory.
            In this case, it is ~/src/MyWorkspace. There are two BaseTools package one
            is for Windows system and another is for UNIX-Like system. Please make
            sure BaseTools(Unix).tar is used here.
        3)  Extract files in [P.UDK2010.UP4.Network] and copy the NetworkPkg Directory to the working    
    space directory. In this case, it is ~/src/MyWorkspace.
        4)  Extract files in [P.UDK2010.UP4.SourceDebugging] and copy the SourceDebuggingPkg Directory    
        to the working space directory. In this case, it is ~/src/MyWorkspace.
    3.  Generate OpenSSL* Crypto Library
        1)  Open file "~/src/MyWorkspace/CryptoPkg/Library/OpensslLib/Patch-HOWTO.txt"
            and follow the instruction to install OpenSSL* for UEFI building.
    4.  Setup Build Environment
        1)  Follow instructions for setting up the build environment on tianocore.org.
            http://sourceforge.net/apps/mediawiki/t … ke_systems
            a) Please be noticed that here the root is "~/src/MyWorkspace" instead
               of "~/src/edk2"
            b) Follow the instructions for building GCC* for X64 and IA32 as well as
               building the Intel ASL compiler. Some of these steps are listed under
               the <Enabling Other Tools> section.
            c) At last check again and make sure "BaseTools", "GCC* for IA32", "GCC*
               for X64" and IASL compiler are successfully built out. Check if these
               tools path defined in "Conf/tools_def.txt" are accordant with actual
               tools path especially for UNIXGCC_IA32_PETOOLS_PREFIX,
               UNIXGCC_X64_PETOOLS_PREFIX and UNIX_IASL_BIN.
    5.  Build Steps
        1)  Open a terminal and type "cd ~/src/MyWorkspace" to enter the workspace
            directory.
        2)  Initialize the build environment by typing ". edksetup.sh BaseTools".
        3)  Now type "build -t UNIXGCC -a IA32 -p Nt32Pkg/Nt32Pkg.dsc"
            to build the platform.
    I am successful in executing the steps untill I run the last command which is 'build'. This instruction is from the link
    http://sourceforge.net/apps/mediawiki/t … ke_systems (as pointed up above in step 4.1)
    I get errors while running the command build.
    Could someone help?
    Regards!
    Last edited by Flash99 (2011-09-20 05:06:54)

    These are the Error messages that I receive:
    /tmp/cc21nZXF.s: Assembler messages:
    /tmp/cc21nZXF.s:2: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:2: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:2: Warning: setting incorrect section attributes for .debug_abbrev
    /tmp/cc21nZXF.s:4: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:4: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:4: Warning: setting incorrect section attributes for .debug_info
    /tmp/cc21nZXF.s:6: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:6: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:6: Warning: setting incorrect section attributes for .debug_line
    /tmp/cc21nZXF.s:11: Error: unknown pseudo-op: `.def'
    /tmp/cc21nZXF.s:11: Error: unknown pseudo-op: `.scl'
    /tmp/cc21nZXF.s:11: Error: unrecognized symbol type "32"
    /tmp/cc21nZXF.s:11: Error: unknown pseudo-op: `.endef'
    /tmp/cc21nZXF.s:58: Error: unknown pseudo-op: `.def'
    /tmp/cc21nZXF.s:58: Error: unknown pseudo-op: `.scl'
    /tmp/cc21nZXF.s:58: Error: unrecognized symbol type "32"
    /tmp/cc21nZXF.s:58: Error: unknown pseudo-op: `.endef'
    /tmp/cc21nZXF.s:117: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:117: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:148: Error: unknown pseudo-op: `.def'
    /tmp/cc21nZXF.s:148: Error: unknown pseudo-op: `.scl'
    /tmp/cc21nZXF.s:148: Error: unrecognized symbol type "32"
    /tmp/cc21nZXF.s:148: Error: unknown pseudo-op: `.endef'
    /tmp/cc21nZXF.s:1594: Error: unknown pseudo-op: `.def'
    /tmp/cc21nZXF.s:1594: Error: unknown pseudo-op: `.scl'
    /tmp/cc21nZXF.s:1594: Error: unrecognized symbol type "32"
    /tmp/cc21nZXF.s:1594: Error: unknown pseudo-op: `.endef'
    /tmp/cc21nZXF.s:1612: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:1612: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:1621: Error: unknown pseudo-op: `.def'
    /tmp/cc21nZXF.s:1621: Error: unknown pseudo-op: `.scl'
    /tmp/cc21nZXF.s:1621: Error: unrecognized symbol type "32"
    /tmp/cc21nZXF.s:1621: Error: unknown pseudo-op: `.endef'
    /tmp/cc21nZXF.s:1972: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:1972: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:2082: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:2082: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:2102: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:2114: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:2150: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:2210: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:2222: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:2281: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:2281: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:3839: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:3839: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:3842: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:3850: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4117: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4122: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4132: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4137: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4154: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4162: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4173: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4176: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4187: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4190: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4194: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4200: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4206: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4212: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4223: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4226: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4230: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4232: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4236: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4242: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4248: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4254: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4260: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4262: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4267: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4271: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4273: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4285: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4291: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4297: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4303: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4309: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4315: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4321: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4327: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4329: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4341: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4347: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4353: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4359: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4365: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4371: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4382: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4388: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4394: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4400: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4406: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4412: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4418: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4441: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4490: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4515: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4612: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4666: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4673: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4675: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4679: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4685: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4691: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4708: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4711: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4715: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4721: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4727: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4733: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4735: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4739: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4741: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4746: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4750: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4752: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4764: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4791: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4794: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4809: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4836: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4889: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4903: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:4944: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:4944: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:5567: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:5567: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:5570: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:5587: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:5587: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:5587: Warning: setting incorrect section attributes for .debug_aranges
    /tmp/cc21nZXF.s:5590: Error: unknown pseudo-op: `.secrel32'
    /tmp/cc21nZXF.s:5599: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:5599: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:5633: Warning: entity size for SHF_MERGE not specified
    /tmp/cc21nZXF.s:5633: Warning: group name for SHF_GROUP not specified
    /tmp/cc21nZXF.s:5648: Error: unknown pseudo-op: `.def'
    /tmp/cc21nZXF.s:5648: Error: unknown pseudo-op: `.scl'
    /tmp/cc21nZXF.s:5648: Error: unrecognized symbol type "32"
    /tmp/cc21nZXF.s:5648: Error: unknown pseudo-op: `.endef'
    /tmp/cc21nZXF.s:5649: Error: unknown pseudo-op: `.def'
    /tmp/cc21nZXF.s:5649: Error: unknown pseudo-op: `.scl'
    /tmp/cc21nZXF.s:5649: Error: unrecognized symbol type "32"
    /tmp/cc21nZXF.s:5649: Error: unknown pseudo-op: `.endef'
    /tmp/cc21nZXF.s:5650: Error: unknown pseudo-op: `.def'
    /tmp/cc21nZXF.s:5650: Error: unknown pseudo-op: `.scl'
    /tmp/cc21nZXF.s:5650: Error: unrecognized symbol type "32"
    /tmp/cc21nZXF.s:5650: Error: unknown pseudo-op: `.endef'
    /tmp/cc21nZXF.s:5651: Error: unknown pseudo-op: `.def'
    /tmp/cc21nZXF.s:5651: Error: unknown pseudo-op: `.scl'
    /tmp/cc21nZXF.s:5651: Error: unrecognized symbol type "32"
    /tmp/cc21nZXF.s:5651: Error: unknown pseudo-op: `.endef'
    /tmp/cc21nZXF.s:5652: Error: unknown pseudo-op: `.def'
    /tmp/cc21nZXF.s:5652: Error: unknown pseudo-op: `.scl'
    /tmp/cc21nZXF.s:5652: Error: unrecognized symbol type "32"
    /tmp/cc21nZXF.s:5652: Error: unknown pseudo-op: `.endef'
    as: /home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BasePrintLib/BasePrintLib/OUTPUT/./PrintLibInternal.obj: warning: sh_link not set for section `.debug_abbrev'
    as: /home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BasePrintLib/BasePrintLib/OUTPUT/./PrintLibInternal.obj: warning: sh_link not set for section `.debug_info'
    as: /home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BasePrintLib/BasePrintLib/OUTPUT/./PrintLibInternal.obj: warning: sh_link not set for section `.debug_line'
    as: /home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BasePrintLib/BasePrintLib/OUTPUT/./PrintLibInternal.obj: warning: sh_link not set for section `.rdata'
    as: /home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BasePrintLib/BasePrintLib/OUTPUT/./PrintLibInternal.obj: warning: sh_link not set for section `.debug_frame'
    as: /home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BasePrintLib/BasePrintLib/OUTPUT/./PrintLibInternal.obj: warning: sh_link not set for section `.debug_loc'
    as: /home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BasePrintLib/BasePrintLib/OUTPUT/./PrintLibInternal.obj: warning: sh_link not set for section `.debug_pubnames'
    as: /home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BasePrintLib/BasePrintLib/OUTPUT/./PrintLibInternal.obj: warning: sh_link not set for section `.debug_aranges'
    as: /home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BasePrintLib/BasePrintLib/OUTPUT/./PrintLibInternal.obj: warning: sh_link not set for section `.debug_ranges'
    as: /home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BasePrintLib/BasePrintLib/OUTPUT/./PrintLibInternal.obj: warning: sh_link not set for section `.debug_str'
    make: *** [/home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BasePrintLib/BasePrintLib/OUTPUT/PrintLibInternal.obj] Error 1
    build.py...
    : error 7000: Failed to execute command
    make tbuild [/home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BasePrintLib/BasePrintLib]
    build.py...
    : error 7000: Failed to execute command
    make tbuild [/home/max/UEFI/UDK2010.UP4/Build/MdeModule/DEBUG_UNIXGCC/X64/MdePkg/Library/BaseLib/BaseLib]
    build.py...
    : error F002: Failed to build module
    /home/max/UEFI/UDK2010.UP4/MdePkg/Library/BasePrintLib/BasePrintLib.inf [X64, UNIXGCC, DEBUG]
    Last edited by Flash99 (2011-09-16 15:12:20)

  • Homogeneous Copy Between x86 platform and x64 platform

    Dear All,
    we have doing a migration from and BW older system with x86 32 bits and W2000server/SQL2000server with BW 3.1C, so the target system is an AMD machine x64 64 bits wih Operating system 2003server/SQL2000server and BW 3.1C.
    we have been talking with SAP OSS support and the conclusion is that this configuration is not supported for SAP for BW 3.1c SQL2000 and W2003server with x64.
    Nevertheless we need to do this migration because after the migration we have to do an upgrade to BI 70/SQL2005 and W2003 in this machine
    The problem here is the SAPinst for BW 3.1c is for x86-32bits and not for x64-64bits, so do you know some way of do that, I mean if we can use some sapinst diferent for do the installations, or if someone already did this migration before???
    Best Regards and thanks very much

    Ernest,
    I think you are stuck in terms of your current strategy. SAP does not have a 64 bit kernel for BW 3.1 on an NT platform. What you'll most likely need to do is to upgrade the SAP system to a release that has a 64 bit NT kernel - BI 7.0 on the WAS700 kernel. The problem you'll run into here is that you'd be attempting to get a BW 3.1 system onto a 64 bit OS and only have a 32 bit kernel for the SAP system - this will lead to myriad of technical issues that you do not want to contend with I'm sure.
    Otherwise, you'll run into the issue of not having the proper kernel components to make the jump. While sometimes it is necessary to move briefly to an unsupported platform combination to get to the OS/DB platform you need, you have to make sure that there are technical tools from SAP available first.
    You may need to rethink the strategy here and make sure that for each jump, you'll have the tools needed.
    Please let me know how this works out for you - I'm sure that in the near future, many of us will also need to contend with such an situation.
    Cheers,
    Tim

  • ITunes for x64 Windows

    Hi,
    Does anyone know anything about iTunes putting out drivers for Windows x64? Or do they not care because Vista is around the corner. This pretty much blows because ever since I moved my computer over to x64 I can't burn cd's with iTunes. I think I've tried every possible fix for this but if anyone has any new ideas please share.
    Thanks,
    Damon

    I have the same problem. x64 is a crap operating
    system, nothing works correctly with it.
    Yeah there is a bunch of other stuff that doesn't work with it, or they give crappy drivers for. Are you going to get Vista? That's going to be 64bit, I think it's all in one version though. I didn't want to get it right when it came out because I figured it would still need more work, but I might just go for it anyway. Not sure when it's coming out.

  • Known Issue: Deriving from SerializationBinder causes incorrect results on "Release" built C#/VB UWP apps on x64 platforms (Windows 10 Insider Preview SDK and tools, April 2015 Release)

    If you are using a serializer such as Json.NET, and use a custom SerializationBinder to handle type resolution, on x64 "Release" builds with .NET Native (C#/VB UWP) you will encounter corrupt parameters.
    This code, if you pass it "assembly" and "type", will throw on Retail builds but work on Debug (CoreCLR) builds.
    class MySerializer : SerializationBinder
        public override Type BindToType(string assemblyName, string typeName)
            if (typeName != "type") throw new Exception("type");
            if (assemblyName != "assembly") throw new Exception("assembly");
            return null;

    Add System.Runtime.CompilerServices.MethodImplAttribute to your BindToType method:
    class MySerializer : SerializationBinder
        [MethodImpl(MethodImplOptions.NoOptimization)]
        public override Type BindToType(string assemblyName, string typeName)
            if (typeName != "type") throw new Exception("type");
            if (assemblyName != "assembly") throw new Exception("assembly");
            return null;

Maybe you are looking for