Quad-Core/Dual-Core Front firewire issue with VX2100 camcorder

Hi,
My VX2100 camcorder will not work (isn't recognized) by the front firewire port on my quad-core G5. The camcorder works on the back port, and I have tried this at the apple store on other machines, all with the same result. Has anyone else had this issue or can offer some advice? Other firewire devices and camcorder have worked fine (I have a canon one that works with the front).
ikiris

Well, I went back into Best Buy to test on 3 other laptops (2 Asus, and their floor model for this Sony). It seems to be doing the same problem so at least I was able to rule out broken hardware issue on my particular laptop.
Here's what I did to test:
Since I couldn't really install Adobe Premiere on their machines, I used the DVIO software (http://www.carr-engineering.com/dvio.htm) and a 5 min clip I captured. I transferred onto their machines, hooked up my Sony D8, and attempted to play the video. It would play for 15 seconds and then stop and jitter with a loud noise (like it does on my laptop). I even tried changing each machine's firewire driver to the legacy one and same results. I pulled a brand new 4 pin to 4 pin firewire cable off their shelf and still the same problem.
I think I've nailed it down to Win7x64 bit Home Edition not playing nice with Firewire driver. Very annoying. I can't find any concrete evidence of this from other users on any of the forums that have my particular problem, but from my own testing, it's all I can conclude.
I have 2 other things I can try:
1. Opening the laptop and looking at the firewire to maybe find appropriate driver (ugh, I don't want to have to open this thing up).
2. Upgrading to Win7x64bit Pro and possibly testing with XP on the new MS Virtual PC (http://www.microsoft.com/windows/virtual-pc/). I can't do it with my Home edition apparantly.
Who needs to view video on an external TV anyways....sheeesh...(scarcasm).
Tim

Similar Messages

How well will a 15.4-inch MacBook Pro 2.0GHz Quad-core Intel i7 work with Final Cut Pro X for video editing 4K

How well will a 15.4-inch MacBook Pro 2.0GHz Quad-core Intel i7 work with Final Cut Pro X for video editing 4K

It will work just fine. I would max out the RAM

Slow Mac Mini with i7 quad core (current gen.) with most current OSX vs. a PC-Winodws 8.1

My Mac Mini is somewhat slow... don’t get me wrong it’s a fast computer but I got a new work laptop i5 Dual Core Acer laptop with windows 8.1 (I know LOL)
& it is so much faster with media and browsing the web and overall boot up everything.... Now I have started to leave my Mac on all the time (sleep vs. off) and its much better but having multi-webpage’s up and YouTube it still get slow and will ever crash from time to time...
Anyone else has this issue? Know what can be done?
Maybe it’s just because the i5 on the Acer is a newer Haswell design? But the Mac is quad core…. Even my old PC desktop that I never use with an Intel Core 2 quad is so much faster even at 8 years old; boots Windows in 9 sec.
Mybe is just OSX - I'm thinking about install WIndows 8.1 on the Mac Mini.... ( anyone have this option; is it fast?)
Thanks

Sometimes all Apps stop working or take a long time to come back.. Have to restart.
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "BOOT_TIME" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Note the timestamps of the BOOT_TIME log messages, which refer to the times when the system was started. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Select the messages logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.
If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent of each. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
☞ If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
☞ Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

Windows 7 Firewire Issues with CS5 and ADVC-700

I've got a Windows 7, 64 bit system with CS 5. In dubbing out for playback, I route a firewire cable from the PC to an Canopus/Grass Valley ADVC-700. Both units are less than a year old and are having issues with "black outs" during the dub out process. I've read different things about Windows 7 having issues with firewire drivers. After speaking to someone with Adobe, I've changed my firewire driver to Legacy. That hasn't helped.
The ADVC-700 has s-video out running to preview monitor and BNC out/XLR audio running to my playback system for ingest. When the video goes to black (usually for a 1/2 second), the audio drops out with it.
I've reset the settings on the ADVC-700 with no luck.
Any suggestions on a fix or something else to try?

I did test with a JVC GY-HD200U and there weren't any performance issues which led me back to the PC or other on the PC.
The system is running Windows 7, 64 bit with CS5 Production Premium following an upgrade from the CS4 version.
I've got 12 GB of Ram, (2) Intel Xeon Quad Core E5560 -2.8 GHZ processoCrs.
(1) 500GB SATA2 hard drive, 7200 RPM, 32 MC (System Drive)
(3) 1 TB SATA2 Hard drives, 7200 RPM, 32 MC (3 TB, RAID0 Storage Drive)
Nvidia GeForce 9800GT graphics Card
Supermicro X8DAi motherboard, Intel 5520 Chipset, 2-PCIe X16, 1 PCIe x4, 3-PCI, 10-USB2 ports, 2-pro/1000 NIC, 8-channel HD audio, 6 SATA ports, RAID 0/1/5/10
I've got the legacy drivers for the firewire card. I've checked to make sure all of the power save options are off along with all screen saver options. I've cleaned my Adobe Cache out, deleted my Adobe Preferences, went from the 4pin/6pin cable to a 6pin/6pin cable to feed the ADVC-700 from the PC, reset the ADVC 700 back to factory specs...all of this with no luck.
The problem seems to be worse since the move from CS4 to CS5 but it's hard to tell.
I've also hooked up an older ADVC-500 unit with the same output results.
I think I noted in the first post that this is happening on two indentical systems with the same cabling and programs and the same ADVC-700 boxes.
I've been told by Adobe to clean my C; drive and reload the OS and Adobe CS5 as I should have done that when I upgraded instead of just upgrading the system from CS4 to CS5 using the discs. I haven't done this yet as I have to budget time/workflow to accomodate.

Firewire issues with Leopard

I updated to Leopard few days ago on my G5 Dual 2Ghz
FW Card is http://www.sonnettech.fr/product/tango_2.html
- First problem was : tasks UserEventAgent and CoreAudio turned to red into activity monitor
- I sampled the tasks (Actity monitor/Inspect) and here are the loops :
UserEventAgent sample ---------------------
Sampling process 1092 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling UserEventAgent (pid 1092) every 1 millisecond
Call graph:
2286 Thread_2503
2286 0xffc
2286 0x25ec
2286 0x385c
2286 CFRunLoopRun
2286 CFRunLoopRunSpecific
2286 mach_msg
2286 machmsgtrap
2286 machmsgtrap
2286 Thread_2603
2286 pthreadstart
2286 AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*)
2286 CFRunLoopRun
2286 CFRunLoopRunSpecific
2286 mach_msg
2286 machmsgtrap
2286 machmsgtrap
2286 Thread_2703
2286 pthreadstart
2286 CAPThread::Entry(CAPThread*)
2286 HALRunLoop::OwnThread(void*)
2286 CFRunLoopRunSpecific
2286 mach_msg
2286 machmsgtrap
2286 machmsgtrap
Total number in stack (recursive counted multiple, when >=5):
Sort by top of stack, same collapsed (when >= 5):
machmsgtrap 6858
Sample analysis of process 1092 written to file /dev/stdout
CoreAudio sample ------------------------
Sampling process 1094 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling coreaudiod (pid 1094) every 1 millisecond
Call graph:
2163 Thread_2503
2163 0xbfffff38
2163 0x2040
2163 0xcdf0
2163 CFRunLoopRunSpecific
2163 mach_msg
2163 machmsgtrap
2163 machmsgtrap
2163 Thread_2603
2163 pthreadstart
2163 AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*)
2163 CFRunLoopRun
2163 CFRunLoopRunSpecific
2163 mach_msg
2163 machmsgtrap
2163 machmsgtrap
2163 Thread_2703
2163 pthreadstart
2163 CAPThread::Entry(CAPThread*)
2163 HALRunLoop::OwnThread(void*)
2163 CFRunLoopRunSpecific
2163 mach_msg
2163 machmsgtrap
2163 machmsgtrap
Total number in stack (recursive counted multiple, when >=5):
Sort by top of stack, same collapsed (when >= 5):
machmsgtrap 6489
Sample analysis of process 1094 written to file /dev/stdout
After some investigation it occured that
"2163 AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*)"
leads to some other components :
AVC.plugin that is a core media IO service and IOFireWireAVC.kext that handles I/O for Firewire
So I ran the test : stop my external drives connected to the FW Sonnet card, and there it was ! no more task in red... I know many of my friends had same issues with same G5 (2, 2.2 ,2.7) and especially, using video apps like final cut with FW cameras and external drives. I suspect de dual kext to be a part of the problem here, because on other Macs, nothing happens like this.
Can I hope for some help or can we expect driver update to get started at work with Leopard soon ?
Thx for answers

Hi all
Since I've updated to Leopard, I've encountered the same problem - without Sonnet Card - using FW800 port with a hard disk and ADVC100 in a FW400 port.
Only UserEvenAgent freezes.
Sampling process 162 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling UserEventAgent (pid 162) every 1 millisecond
Call graph:
2255 Thread_2503
2255 0xbffffd40
2255 0x25ec
2255 0x385c
2255 CFRunLoopRun
2255 CFRunLoopRunSpecific
2255 mach_msg
2255 machmsgtrap
2255 machmsgtrap
2255 Thread_2603
2255 pthreadstart
2255 AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*)
2255 CFRunLoopRun
2255 CFRunLoopRunSpecific
2255 mach_msg
2255 machmsgtrap
2255 machmsgtrap
2255 Thread_2703
2255 pthreadstart
2255 CAPThread::Entry(CAPThread*)
2255 HALRunLoop::OwnThread(void*)
2255 CFRunLoopRunSpecific
2255 mach_msg
2255 machmsgtrap
2255 machmsgtrap
Total number in stack (recursive counted multiple, when >=5):
Sort by top of stack, same collapsed (when >= 5):
machmsgtrap 6765
Sample analysis of process 162 written to file /dev/stdout
Perhaps an Apple update could be needed.
I'll try your solution - but loose the use of my 500Gb HD is difficult
Regards
Didier

FireWire issues with external drive in Yosemite

I have just upgraded to OS X Yosemite, and I have an annoying problem with my 500GB FireWire external drive (which I use for Time Machine backups).
Basically, after updating the drive won't show up anymore, neither in the Finder nor in the Disk Utility. I also tried the "diskutil list" command in the Terminal, but it is nowhere to be found. Note that the drive does indeed receive power from the port - it spins - and when I look into System Report --> Hardware --> FireWire it does show up there (but I can't mount it). Furthermore, if I use a USB cable to connect the drive everything works fine, so the disk itself seems to be OK.
The funny thing is that if I boot with the drive plugged in the FireWire port the system mounts it normally. But as soon as I eject the drive, I am unable to mount it again (unless I switch to the USB cable, as mentioned above).
Prior to the update, everything worked flawlessly. For now, I backed up my Mac via USB 2.0, but it's very slow and I definitely don't want to resort to this workaround everytime. And it goes without saying that I don't like having issues with my primary backup device in general.
I already did all the usual troubleshooting (rebooting, resetting NVRAM and SMC, ...), but the problem still persists.
Any suggestion?

I had the same issue on a rMBP 13'', brand new 2015 March.
Two thunderbolt adapter connected: one for ethernet, one for firewire Lacie drive.
and...
even after taking the ext. Firewire on the Spotlight exclude list, and also after disabling sleeping hard drives, I always got the issue.
Until I realized that touching the laptop or moving the screen was immediately leading to disconnection.
Then I exchanged the thunderbolt connectors, and now it is stable and does not disconnect again.
??? Maybe one of the ports is more "delicate" than the other?
Big hardware weakness here...

Front Row issues with MacBook Pro?

I just bought my MacBook Pro today and transferred all my files from my old Mac via firewire. I run Front Row, and it says "an error has occurred" every time i try and play any playlist OTHER than the playlists of stuff bought from iTunes... any ideas?
Also --- how do I NOT make it shuffle?
Thanks!

ohhhh
No, actually, I leave my folders somewhere else. That must be why, because my downloads ARE there!
Another question then...if you guys know...I reinstalled Entourage, and I'm now told that I can't access that identity with this version of Entourage!
Thanks, you guys are awesome.

Firewire issues with DV camera

When connecting a Samsung VP-D305i mini DV camera to the firewire port (4pin to 6pin cable) Mac OS fails to recognise it.
I know this is an issue that has been covered in this forum a few times, but none of the answers seem to work for me. Furthermore rather than get the "unable to list firewire devices" in system profiler, system profiler displays it as unknown device. The following is given as the detail:
Manufacturer: 0xF0
Model: Unknown
GUID: 0xF000084139E5
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Up to 400 Mb/sec
Sub-units:
Unknown Unit:
Unit Software Version: 0x10001
Unit Spec ID: 0xA02D
Final Cut Pro and iMovie both fail to work with the device, however they do recognise that a camera has been plugged in. My MacBook Pro has the Texas Instruments Firewire chipset, is this not supposed to be the more reliable chipset?
Flushing the SRAM doesn't work, I've formatted reinstalled Mac OS X, didn't work. The DV camera works fine through the same cable on my sister's MacBook. Furthermore, the DV port works 100% fine when booting my MacBook Pro, using Bootcamp, in XP. This port did work, I've used it before with iMovie in November last year. (with Bootcamp and Windows installed). Does anyone else know anything that may help?

Is the sound mixer physically connected to the mac via firewire? Maybe just unplugging it will help; there is only one firewire bus, and sometimes the capturing you are trying to capture from needs to be the only device connected.

IPhone 4s having front camera issues with iOS 7.1.2 are there any fixes?

i started having some problems with the front facing camera as soon as i upgraded from iOS 7.1.1 to 7.1.2 the camera just freezes or turns black and i have to restart the phone in order to get it back working (at least the rear camera works when i do this) but as soon as i try and use the front camera it freezes again, is there any way to fix this?

To rule out a software issue, set it up as new device without using the latest backup. If the camera works after that, restore from the backup.
If it does not work, your phone might have a hardware problem and needs to be serviced:
How to back up your data and set up as a new device
iPhone - Contact Support - Apple Support

Firewire issue with Alesis Multimix

Hello, I have an iMac 10.6.4. I have been trying with no success to hook up (via firewire) to the Alesis Multimix 8. I also have the Tascam 1804. I downloaded the correct drivers for each source. Followed all directions such as turning units off and restarting. For some reason, it seems the iMac does not see either of the units. I have been alternating the units several times, removing and re-installing the drivers. Yet, I cannot see the either unit in hardware overview, nor in Logic Express. I am using a new firewire 9 pin to 6 pin cable. When I click on the icon for the Alesis unit, I get a message saying "Alesis Firwire, no devices found, connect devices" The Alesis does not show in Logic Express either. As far as the Tascam is concerned, their message states, FW1804 not available. It seems the iMac just does not recognize any of these units. Can anyone shed light on this for me please, I would hate to run out an buy another interface!

Have you tried hooking up just one device at a time? Don't know if it will help, but maybe it needs a little time to configure one device at a time.
I had the same kind of problem (with hooking up a Mbox2 (firewire) and an ext. firewire HD). I installed them separately. Now they still don't really like working together, but when I hook up my HD first and after that the Mbox, it works fine.

Bay 1 or bay 2 when installing a 120gig SSD Boot drive with 10.8 into a MacPro 3.2Ghz Quad core ?

Im about to install a 120gig SSD into a MacPro 3.2Ghz Quad core. It shipped with a 1TB Hitachi Ultrastar HDD Sata III, that runs 10.7 and is the boot disk running form bay #1. I plan to run 10.8 on the new SSD and use that as the boot disk.
Should I swap over the Hitachi HDD and SSD so that new SSD boot drive is in bay #1 ? If so am I correct that it would be okay to download and install Mountain Lion on the SSD using bay #2 first and then swap them over once installed ?

Thanks. FYI the planned build is this...
Bay 2 - BOOT DRIVE. 120gig SSD running OS 10.8 plus all apps (although not sure whether to wait a while regarding upgrade to 10.8 ? )
So far Im quite happy with 10.7.3 and the machine seems very stable
Bay 1 - 1TB HDD running OS 10.7.3 (so can boot from this HDD disk if required to should the SSD fail (if or when ). This is disk already running 10.7.3 as boot disk now.
Bay 3 & 4 - On horizon... x2 1TB Western Digital Black Caviar HDD set up with RAID '0' stripe. Not sure on whether to use a RAID 0 or not yet.... Might just go with one 2TB drive... TBC.
BACKUP: 3tb external HDD or Synology DS411j NAS drive
So from what I understand once I've installed the OS on to the new SSD along with any apps, use Carbon Copy Cloner to make an fresh image before I use the system... is that correct ???

Can I install Mavericks on Quad-Core Intel Xeon (w/10.6.8)?

From everywhere I have read so far, the answer looks like "yes I can install Mavericks", but I'm a bit confused and wanted to check with folks here before I dive in...
I'm running an early-2008 Mac Pro with 10.6.8 (check!), but I could swear that in the past when I tried to update certain pieces of software (and OS), that 10.7+ (or 10.8+) required a later processor than is running on my Mac Pro (which is a Quad-Core Intel Xeon).
With the Mavericks release, it seems to be that I can now update the OS even with this older processor, and then be able to run all the latest software (I really just use MSFT and Apple software). It seems counter-intuitive to me, so I just wanted to make sure I'm not missing something and will be left in deep doo-doo after trying to install Mavericks!
Thanks much all-

       Macs that can be upgraded to OS X Mountain Lion
         1. iMac (Mid 2007 or newer) - Model Identifier 7,1 or later
         2. MacBook (Late 2008 Aluminum, or Early 2009 or newer) - Model Identifier 5,1 or later
         3. MacBook Pro (Mid/Late 2007 or newer) - Model Identifier 3,1 or later
         4. MacBook Air (Late 2008 or newer) - Model Identifier 2,1 or later
         5. Mac mini (Early 2009 or newer) - Model Identifier 3,1 or later
         6. Mac Pro (Early 2008 or newer) - Model Identifier 3,1 or later
         7. Xserve (Early 2009) - Model Identifier 3,1 or later
You must have the third generation MP in order to run Mavericks. You can install over Snow Leopard:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
If all is well then run the Mavericks installer that you downloaded. Prior to this you may wish to make your own installer:
Make Your Own Mavericks, Mountain/Lion Installer
1. After downloading the installer you must first save the Install Mac OS X application. After the installer downloads DO NOT click on the Install button. Go to your Applications folder and make a copy of the 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:
Open Disk Utility in your Utilities folder.
After DU loads select your flash drive (this is the entry with the mfgr.'s ID and size) from the leftside list. Click on the Partition tab in the DU main window.
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.
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.
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.
Click on the Erase button. The format process can take up to an hour depending upon the flash drive size.
3. Use Lion DiskMaker 3.0 to put your installer clone onto the USB flash drive.
Make your own Mavericks flash drive installer using the Mavericks tool:
You can also create a Mavericks flash drive installer via the Terminal. Mavericks has its own built-in installer maker you use via the Terminal:
You will need a freshly partitioned and formatted USB flash drive with at least 8GBs. Leave the name of the flash drive at the system default, "Untitled." Do not change this name. Open the Terminal in the Utilities folder. Copy this command line after the prompt in the Terminal's window:
sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ Mavericks.app --nointeraction
Press RETURN. Enter your admin password when prompted. It will not be echoed to the screen so be careful to enter it correctly. Press RETURN, again.
Wait for the process to complete which will take quite some time.

ESATA adaptor for MacPro 3.2 Quad-Core?

I have a Quad-Core Mac Pro tower with only Firewire 800/400 ports. How can I increase my connectivity? Is there an eSATA adaptor that I can add to my computer? I work with FCP 7.0.3 and it's too slow with an HD project with Firewire 800. How do I improve it?
Thanks!

You should be able to add an eSATA card to your Mac Pro. I did for mine. OWC hasa a bunch. Follow this OWC link for a sampling of the kinds of cards that could be used.
Note, be aware that not all cards will fully work with all external enclosures due to the interactions of their drivers and the enclosure electronics. For example, I had a card that wouldn't remount the drive in my enclosure if I previously unmounted it. Only reboot would allow a remount. But I got a different card that solved that problem.
Depending on which model and year your mac pro is there is the possibility of using a cable plugged (internally) directly into your machine. See this link.

New NI CompactRIO calls the question, "¿Quien is mas macho, Intel quad-core Atom or 4-year-old i7?"

Perhaps you remember the Saturday Night Live TV sketch from 1979 where Bill Murray played a game show host who asked the show’s titular question, “¿Quien es mas macho?”
Today, Matt Spexarth, Principal Product Manager for Embedded Systems at National Instruments (NI), called the NI CompactRIO controller introduced this week at NI Week—the model cRIO-9039, which pairs a 1.91GHz, quad-core Intel Atom CPU with a Xilinx Kintex-7 325T FPGA—the highest-performance CompactRIO ever released. That includes the existing cRIO-9082 controller, which pairs a 1.33GHz, dual-core Intel i7 CPU and a Xilinx Spartan-6 LX150 FPGA. So both the processor and the FPGA have been upgraded in the new CompactRIO controller. The NI cRIO-9039 controller es mas macho.
NI Model cRIO-9039 Controller in an 8-slot CompactRIO Chassis
The new NI CompactRIO controller runs security-enhanced NI Linux Real-Time. It has an SDHC card slot for non-volatile storage and can directly operate a local, graphical UI (user interface) as a human-machine interface. Another key performance feature, noted Spexarth, is a bank of DDR3 SDRAM attached directly to the Kintex-7 FPGA to allow the FPGA to directly handle large data sets, to process large FFTs for example.
As with the entire line of NI CompactRIO controllers, you program the cRIO-9039 controller using NI’s LabVIEW graphical development environment with its many add-on modules including LabVIEW FPGA. In addition, the new CompactRIO controller maintain compatibility with the many CompactRIO plug-in I/O hardware modules.

Whygirl,
it reads as though an internal disk upgrade (and possibly a battery replacement) would suffice for you, and those two together would be far less expensive than a new MacBook Pro. Yes, you could install either a HDD or a SSD in place of its current internal HDD. You could look at the Hitachi Travelstar 7K1000 as an example of a suitable 1 TB HDD; SSDs are more expensive per unit of storage than a HDD, but might be worth the extra cost if your apps are disk-bound. (I put a Samsung 840 PRO into my 13-inch Mid 2010 model, and it’s been working well.) Note that Chrome might be responsible for the extra heat (and the extra heat is responsible for the increased volume from the fans kicking in); Chrome isn’t optimized for use on 64-bit versions of OS X, like 10.8.5.

Is it possible to install a i7 quad core processor in a Pavillion dv 1000 notebook?

My notebook is running XP, but I could load Win8 64
I think I'd have to upgrade the memory also, but don't know if the quad core chips are compatible with this motherboard

Hi,
Sorry NO, please check page 1-2 of the following manual:
http://www.hp.com/ctg/Manual/c00312379.pdf
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

Quad-Core/Dual-Core Front firewire issue with VX2100 camcorder

Similar Messages

Maybe you are looking for