MXI-3 to PXI bridge under Windows XP problems

Hi,
I have installed a MXI-3 card in my PC's PCI bus, and have it connected to a
8330 MXI3 card in a PXI1000B crate. Also in this crate are various I/O cards
(6533, 6713, GPIB etc).
When I booted the XP machine first time, it detected new hardware and wanted
to install drivers, but it couldn't find them.
I ended up ignoring the requestes and installing the MXI-3 optimization
software - this worked fine, but the PCI device installation wizards
persisted at every boot-up, and still unable to find any drivers to satisfy
itself.
I then installed Labview 6i with MAX 2.0.3.6. MAX detects my crate and
devices fine. Additionally, when I booted up the installation wizards were
now able to find device drivers for my 6533 etc. cards
Now when I boot up, I get no new hardware found, and no wizards pop up.
Phew.
BUT.....
If I look in Control Panel > System > Hardware > Device Manager I see two
items under "other Hardware" with yellow question marks next to them.
These are: "other PCI bridge device"
and "PCI Simple Communications controller".
Both these failed to install drivers using the wizard. They have the
details "PCI slot 2, PCI bus2 device 9 function 0" and "PCI slot 2, PCI bus2
device 12 function 0" respectively.
I assume these devices are in my PXI crate?
I have a 8422 GPIB card in PXI slot 5, and a MXI2 8320 card in slot 8. Could
these be the problem? Should I be worried about them, or just ignore them? -
I know the GPIB card works fine through labview.
Thanks in advance,
Joe

It sounds like your installation procedure varied from what we normally recommend, but we should be able to fix your system up. Typically, you should install all drivers on your system before linking the PXI chassis and cards up to your PC. In your case, this means installing NI-DAQ, NI-488.2, and NI-VXI before linking the chassis up.
I would recommend removing your PXI-GPIB card and PXI-MXI-2 card from chassis, and then booting your chassis and PC. Check in Device Manager to see if there are any unknown devices. If these are gone, we have found the correct devices with problems. Install NI-488.2 and NI-VXI, then shut down, install your cards, and boot back up. The two cards should detect properly.
Here are links to the necessary drivers:
http://www.ni
.com/support/gpib/versions.htm
http://www.ni.com/support/vxi/drivers.htm
Ryan Tamblin
Applications Engineer
National Instruments

Similar Messages

CS6 Bridge Under Windows 8 Slow Response

When I use CS6 Bridge in Windows 8 (64 bit) it takes about 10 seconds to open a folder. I select an image from the grid and press the spacebar to see it full size. It takes another 10 seconds. If I go to the Menu Bar and click on an item such as Window it takes about 10 seconds to get the drop down list, but if I then slide the cursor over to View and click on it, the menu appears right away and if I then click on Full Screen Preview, the full size image appears immediately. When I check the Widows Resource Monitor there is no unusual activity occurring during these 10 second intervals. It is as if the program is in a wait state pending some event.
When I was running CS6 under Windows 7 (32 bit) everything worked fine. When I run CS4 Bridge on Windows 8 (64 bit) it also runs fine. I have purged the cache, and increaed cache size but to no avail. My system has lots of processing speed, memory and disk space.
Does anyone know what I could do to get CS6 Bridge running correctly in my Windows 8 environment?   Is it possible that there is some kind of incompatibility with
Bridge, Windows 8 and the GPU?

Curt Y wrote:
I discussed this "solution" with Adobe back in July. Here is their response.
"There really should be no reason that running in Vista compatability mode would change the behavior of the application. Vista and 7 are so similar at the fundamental level that there shouldn't be any advantage.   Really, this is likely pointing to a lack of OS updates being installed, or installed improperly. One person mentioned that a new user account fixed things. I have a feeling that would true of more folks who are willing to try it. I'll run this by my collegues though."
But if it works it is better than the alternative.    curt
Surprisingly the bit about trying it under a different or new user actually works here. All the aggruvating 5 to 10 second long freezes disappear when used under a fresh account.
Ok, so how can that be parlayed into being able to use Bridge CS6 under my own account?
Does the fact that it works as expected under a new fresh account point to something particular that needs changing or adjustment under my regular account?
The Adobe staff person seems to think it is most likely a problem of (lack of) updates or incorrectly installed updates, but that would not have any bearing if changing to a new account fixes the problem would it?
PS - How does one run in Vista compat mode?

Photoshop CC2014 running under window 8.1. How do I access mini bridge. It does not show under FILE or WINDOW-EXTENSIONS. Works ok with CS6

Photoshop CC2014 running under window 8.1. How do I access mini bridge. It does not show under FILE or WINDOW-EXTENSIONS. Works ok with CS6

Photoshop: Spring Cleaning | PHOTOSHOP.COM BLOG

LiveCycle ES 8,2 JBoss : will it work under Windows PC 2007

LiveCycle ES 8,2 JBoss : will it work under Windows PC 2007 virtual machine? (Turnkey or non turnkey version)
Thanks
Yog

great - another few hundred pounds I'll have to spend..... thanks adobe... more profit for you... but here is another question what about cs4? is that compatible with windows 8 as I have a web standard version, what ever that means but I dont have photoshop for CS4 as I got it for the web desing ...and there no chance of using your cloud thingy 'cos I aint spending $50 a month !!!!
can anyone suggest what I should do - I have my original Photoshop 6, then I purchased CS2, following that I got CS4 Web standard as I was doing a Dreamweaver course and the CS4 came as part of the course but with no photoshop. Now I use adobe bridge and photoshop extensively, these are the 2 I realy want and with Cs2 it worked great as it upgraded Photo 6 to cs2 and I got Bridge NOW I GOT NOTHING !!!! how frustrating

PCI to PXI bridge

My PC doesn't start while I'm connecting the MXI-4 to PXI.
What can be the problem?
Guy.

Depending on where your PC hangs, it's likely not a SW problem. With MXI-4 hangs near the BIOS post, it is usually because your host computer is having trouble enumerating the additional PCI bridge and/or devices. This usually shows up as a slow boot, a hang or improperly detected PCI devices.
Another possible problem is that your computer is not providing a 3.3V and 5V rail to the PCI MXI-4 univeral card. The Universal card can do 3.3V or 5V signaling but requires 3.3V and 5V power rails to be present. Do you get both the power and link light when using the computer that is misbehaving?
What computer models are you using? I assume they are different. I would encourage you to try updating your BIOS on the misbehaving computer to see if any improvements to PCI enumeration have been made. Additionally, try contacting the computer manufacturer to ensure they provide both 3.3V and 5V power rails to the PCI slots.
-Adam U.

No library panel option under windows menu PC signed in to cloud

I have photoshop at home and work I want to use shape captured on my ipad noticed no library panel option under windows menu.
in general Cloud, Bridge andLlibraries confuse me obviously not the same but after viewing tutorials more confused.
Damian Burns smart and stupid at the same time!

Chris and Gener7here are my system details below
Adobe Photoshop Version: 2014.2.0 20140926.r.236 2014/09/26:23:59:59 x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:10, Stepping:7 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX, HyperThreading
Physical processor count: 2
Logical processor count: 4
Processor speed: 2491 MHz
Built-in memory: 8074 MB
Free memory: 5400 MB
Memory available to Photoshop: 7045 MB
Memory used by Photoshop: 60 %
3D Multitone Printing: Disabled.
Windows 2x UI: Disabled.
Highbeam: Disabled.
Image tile size: 128K
Image cache levels: 4
Font Preview: Medium
TextComposer: Latin
thankyou for trying to help me
Damian Burns
Sent from my iPad

Watchdog PXI-8184 on Windows to reboot the PXI when the application is frozen

Hi,
I have a Labview application running under Windows XP on a PXI-8184 controller. Now, I want to know if it is feasible to trig some kind of watchdog on this PXI controller in my application to check if Windows or my application is frozen.
Thanks
Alexandre Boyer

Hey Alexandre,
If you want your system to reboot automatically if it crashes, you can set this up in Windows. Go to My Computer>>Properties>>Advanced Tab>>Startup and Recovery>>Settings and check the "Automatically Restart" box. This should reboot the system controller whenever the system stops unexpectedly.
I hope this helps,
Jason W
Application Engineer
National Instruments

MXI-3 with PXI-7344 etc blue screens

Dear support folk,
This is a follow-on from unsolved problem discussed below. I have this problem on multiple computers now with varying severities. One machine is unuseable due to the frequency of blue screens. Is it our C-code perhaps? Please help - this problem is going to be the death of me!
Old question:
"Okay, this is driving me crazy! I've asked this question before and really didn't resolve the problem fully so here we go again. I have an MXI-3 card with PXI-6052E, 6508 and 7344 in cPCI chassis. Trouble is I get random bluescreen errors (especially towards the end of boot process but they can be anytime). This happens on just about every machine I install this hardware configuartion on. Disabling stuff like the c
om ports and killing background processes such as virus scanners seem to help a little but have never solved the problem. The latest installation won't go at all and bluescreens every time. I tried a Win 2000 installation and the boot-up blue screens disappeared but our software would not work properly (this could well be our fault though so I will restrict my question to the boot-up bluescreens). Any help would be very much appreciated!"
Old answer
"Hi,
There was a bug in the MXI-3 software that could cause a Windows page fault exception (0xE) on Windows 98. It is very rare, but there is a patch to fix it. I attached it below. If this does not solve the problem, please email us so that we can help you further. Go to http:\\www.ni.com\ask and select Email an Engineer. You will want to select PXI/VXI for the product.
Thank you,
Katie Shiels

Marcus,
The most common cause of problems with MXI-3 systems is simply not using the correct boot order. I would first verify the proper boot order (chassis first, then computer). Verify that the LINK LED comes on right after the computer boots, and that the LINK LED never, ever, blinks or strobes during operation. If the LINK LED goes out, strobes, blinks, etc, then a hardware problem with the link (PCI-MXI-3 board, PXI-MXI-3 board, or cable) is indicated.
If you continue to have blue-screens at boot, then the next step is to "divide-and-conquor" the system. What we want to do is make sure that none of the cards in the PXI (or CompactPCI) chassis are themselves causing the problem (for example, if a card has a resource conflict). For troubleshooting purposes, remove all cards from the PXI chassis, shutdown, and then power-up again with the proper boot sequence (chassis first, computer second). If the problems disappear, then a problem or resource conflict with one of the PXI / cPCI cards is indicated.
If the blue-screens continue, even with the hardware removed, then the next step would be to uninstall the MXI-3 Optimization software. What we are going after here is if it is during the run (every time at boot) of the MXI-3 optimization software that the blue screen occurs.
If none of these indicate the problem, then the "divide-and-conquor" approach requires us to determine if the problem is with the MXI-3 kit itself, or something specific to that computer. Two things to try. The first is to try the MXI-3 kit on a different machine. The second is to try another MXI-3 kit (if available) with that machine.
Through these steps, you should be able to isolate a single piece of hardware (a PXI card, the MXI-3 kit, the PC, etc) that is common to the problem.
(note, the bug referred to by Katie was specific to running the MXI-3 optimization software, not the MXI-3 hardware in general - so if you are seeing the problem she referred to, you should see the blue-screens disappear when the MXI-3 Optimization software is uninstalled).
As always, National Instruments Technical Support is only a phone-call away (7am - 7pm CST) if you want to work with a NI engineer on this procedure.
Regards,
Greg Caesar
Applications Engineer

Adobe Bridge CS3 windows error

Hi,
When I open Bridge cs3 on its own after a few seconds the window banner comes up. Adobe bridge has encountered a problem and needs to close.We are sorry for any inconvenience. The same happens if I try to open bridge from within Photoshop cs3
I can still work in the programme ok and move the windows error aside, I would like to fix the problem, Tried to debug but the programme just closes.
I use windows xp pro with all the latest updates that are available.
have any others experienced this problem and how to fix it.
Thanking you in advance.

Mikep500 wrote:
This is a copy of the message that comes up.
No messageto see, but you can check your Startup Scripts in Bridge preferences. Mine are like this:

X230T graphics performance under Windows 8

My Thinkpad originally came with Windows 7 Pro, but I have changed to Windows 8 in order to resolve problems with VSS. OOB, both Windows 7 and Windows 8 gave me a "Desktop graphics performance" rating of 5.7. Under Windows 7, upgrading to the latest Lenovo driver improved this to 6.1, leaving my HDD (at 5.9) as the limiting factor in performance. Under Windows 8, however, replacing the Windows driver with the latest Lenovo driver has reduced "Desktop graphics performance" to 5.6! What gives?
P.S. I just discovered a Power Options advanced power setting "Intel Graphics Power Plan", which was set to "Maximum Battery Life" for both battery and plugged in. I changed it to "Maximum Performance" when plugged in, but the Windows experience Index (WEI) for "Desktop graphics performance" remains a mer 5.8.
X320T running Windows 8 Pro x64

rsbrux wrote:
My Thinkpad originally came with Windows 7 Pro, but I have changed to Windows 8 in order to resolve problems with VSS. OOB, both Windows 7 and Windows 8 gave me a "Desktop graphics performance" rating of 5.7. Under Windows 7, upgrading to the latest Lenovo driver improved this to 6.1, leaving my HDD (at 5.9) as the limiting factor in performance. Under Windows 8, however, replacing the Windows driver with the latest Lenovo driver has reduced "Desktop graphics performance" to 5.6! What gives?
P.S. I just discovered a Power Options advanced power setting "Intel Graphics Power Plan", which was set to "Maximum Battery Life" for both battery and plugged in. I changed it to "Maximum Performance" when plugged in, but the Windows experience Index (WEI) for "Desktop graphics performance" remains a mer 5.8.
After you changed the setting to "Maximum Performance" , did you run the WEI test again?

Premiere Elements 8 under Windows 7: HOW TO DO?

My system is a MICROSTAR (MEDION) Quadcore 6600(think it's made by MSI) with 4GB memory, 2 x 1TB HD Wetern Digital GREEN (replacing the very poor quality Seagates 2 x 500Gig originaly installed) and running Windows 7 64 and 32 Ultimate. The 32 version was installed especially for PE8
Why I didn't stay with PE7?
Strange enough, PE7 worked perfectly under Windows 7 64bit RC and RTM, but with the Official release of Windows 7 32 or 64 Ultimate, it was finished with the Happy Hour, Crash, crash, crash all the time!
So I downloaded from Adobe a official PE8 and started very happily with it.
But it was CRASH & GO all the way !!!
I have send a few messages to Adobe Contact, which deviated me to this forum so I could spit my poison far from their "Ivory Tower" No answers or help from them. PE8 is paid, so go to ...
I found out immediately that I was one of the many people to regret this "Buy of the Year", but since PE7 didn't work and Windows 7 is so good that I don't want to go back to XP or Vista, I had to find a way to make this SH.. work. Luckily the Forum proposed me a few solutions for which I am very grateful.
After a few editing's with DV (about 3hours long), I am having a little bit more experience with this PE8-pre-beta-thing.
First of all I disabled the GPU-thing in the preferences, then I disabled the "Background rendering".
The Medion computer has a "diet" Nvidia Geforce 8600 so there are no 3D drivers to disable, neither has Windows 7 this Windows Defender, so that could also not be the problem.
Anyhow, these few minor changes seem to have solved a lot of crash problems.
Also, NEVER open a PE7 project in PE8 !!!!! It's really not 100% compatible: no way to render previews and crashes guarantied!
Be very careful in applying transitions and video effects, especially if you start cumulating them. Maybe they will work in preview, but you never know if you will be able to render a film or DVD from it.
For example "camera view" + "Soft edge" ( since I have a Dutch version, I don't know if these are the right names) to make a kind of 3D frame around your image. No problem in PE7, but PE8 doesn't digest it! The only way to render this to a film is to import the project in to PrProCS4 and change the other transitions which are not supported by PrPro with similar ones. Or going from New York to Chicago over Mexico City!!
If you take care of these precautions you can work very satisfactory with PE8, without crashing more then was the case with PE7 (low memory problems)
This PE8 should have been written for 64 bit, so it would have suffered much less memory problems, then now.
Some things I like better with PE8, like the ClipArt's, the Menu's and the new Smartmovie themes, which I create and then edit manually.
Automatic backup creates now 5 instead of one file.
What I don't like:
If you capture in scenes, it's still scene 11 coming after scene 109 etc, instead of counting from 001.
With PE7, you could see in which map the project you wanted to open was situated, here not.
Place of the Project changed, without reason, change for the fun of change?
Making "markers" has become more complicated, without improving. Also changed just for the fun of it?
Can still not capture HDV by scenes, for that I have to use Sony Vegas.
Until now I didn't try to edit HDV in PE8, because I don't trust PE8.
What we really need is for Adobe to bring a major update to fix al these annoying misfits and to make a customer's dialog instead of a one way street policy.
If I find new ways to make work easier and without crashing I will not hesitate to let you know.
Until then, hope this can help you a little bit!
Roald

NO, YOU CANNOT !!!!
If your project was started in PE7 and you import that project to PE8, you cannot, I REPEAT, you CANNOT render this files to a preview.
You wil get the render window, but no counter or anything else will move or happen.
Nothing, rien , nada, niets, nichts!!!!!!
At least not here on neither of the 3 installations which I did under 3 different Windows 7 !!!!

Photoshop Elements does not start under Windows Vista

The Twain-Module of my Canon CanoScan FS4000US Filmscanner works only under Windows Vista (no newer OS!). Fortunately I own an older Notebook with Vista as OS, so I have PSE Version 5.0.2 installed and use it to import my old color negatives via the twain module. Fine! It even works with 42 bit. But suddenly, PSE refuses to start and freezes at the window loading the libraries. At this stage it can only be stopped with the help of the task manager. A little search in the internet informs me that I am not the only user with that specific problem. Any help from Adobe?

After a view days of searching a found a solution: I installed the MS Visual C++ Reditributable für Visual Studio 2012 Update 4 (both 32 bit and 64 bit) and now Photoshop Elements runs without any problems.

Bridge CS3 (Windows XP) fails to start because Symlib.dll was not found

Bridge CS3 (Windows XP) fails to start because Symlib.dll was not found? How do I fix this? I've re-installed and the auto updater has run...I even downloaded and ran the patcher application? By the way Bridge CS3 doesn't show up in the CS3 program list in the start menu but it is installed in my program files - I've tried launching it directly from there as well. Bridge CS2 is operating just fine.
Update: I installed and ran the Adobe Support Advisor, resulting in - Issues: "The module found no solutions to report for the selected log file."
I tried to package the report and the error read: "The size of the package is too large to be handled with the current configuration! Please contact Adobe Support for additional information."
I opened a web based report/case number at the Adobe Support Portal about the missing Symlib.dll (including the Adobe Support Advisor error). Their response was: We regret to inform you that complimentary support for your product is not available and/or has expired.

Did Bridge work before? If so, reset preferences by holding down the Ctrl key when starting Bridge. If successful you will get a Reset Window, choose all 3 options.

Running DS-5 armcc compiled code (PIC) under Windows EC 2013

Hi All,
i just wanted to know if it is generally (officially) supported to run code that is compiled via the armcc (5.03) from DS-5 under Windows Embedded Compact 2013. Or if this is discouraged (reasons?).
The problem i have:
The bootloader contains some code that must be run during Windows EC Startup. So this code is loaded from the Flash, copied to RAM (reserved and commited via VirtualAlloc and marked as executable) and then the functions are called via FunctionPointers.
The code is compiled and linked as position independent and the stack base register is set accordingly before any function is called via pointer and reset when it returns.
This works in about 9 out of 10 tests without problems. But sometimes i get all sort of exceptions (Data Abort, Prefetch Abort, Unknown Instruction, ...). Most (if not all) of the time they occur when the position independent code runs on one of the two
cores.
The code runs on an i.MX6DQ (dual).
If i only enable one core, i can't reproduce the problem (i assume that multicore-handling and multithreading in WinEC 2013 Update 10 is really well tested and works without problems, so this can't be the real reason).
I've thoroughly checked and debugged the code, i'm really sure there is no illegal access or other problem with the code itself.
Could it be a problem to call code compiled via DS-5 armcc? I've compared assembler code that Visual Studio/Platform Builder generates with code that DS-5 generates (but i'm no assembler expert). I can't see any obvious special code that is added by Visual
Studio/Platform Builder (i.e. that functions need) that is not there in the DS-5 code.
Best Regards
Sebastian

So I think you could be able to image some code for ROM from another compiler and without knowledge of Windows CE. However, if the code will be called from Windows CE, this becomes more difficult requiring very careful isolation from the
MMU state, processor state, kernel/user mode, etc. Code that works great when called from the bootloader might not work at all from Windows CE itself. The main problem with mixing code from different compilers is the object file format and conventions for
entry and public names. Very unlikely that you'd be able to "link" code from any other compiler with PB-compiled code.
You might think about the x86 image which can easily call BIOS from the bootloader but which can't even begin to call BIOS from CE itself. The problem isn't the compiler (which is different), but the operating environment differences and assumptions.
Paul T.

JavaSoundRenderer now running under Windows

Hello,
I found out that the JavaSoundRenderer could run under Windows but only if you use Java 6.0 Beta.
So if you've problems of playing audio in Windows then just install the new Java (6.0) and it will work.
best regards,
thomas

Hi,
Refer [SAP Note:1337708 - Crystal Reports support of 64 bit Operating Systems|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_dev/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333333333337333733303338%7D.do] and also have a look at
[SAP Note:122050-An error has occurred while attempting to load crystal reports on 64bit|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333233323330333533303331%7D.do] might be helpful

MXI-3 to PXI bridge under Windows XP problems

Similar Messages

Maybe you are looking for