Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
PCI-GPIB card installation
Ya-hoo
Member
06-27-2005 12:35 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Some problems encountered after PCI-GPIB card was installed.
1. After PCI-GPIB card was installed, it could be seen from device manager, but no resource assined to it.
2. GPIB driver caused Windows 2000 restarting when whatever is chosen in start menu (standy, shut down or logoff). When GPIB is disabled in device manager, this problem disappeared.
Anybody has experence about it?
Thank you so much for your any opinions?
1. After PCI-GPIB card was installed, it could be seen from device manager, but no resource assined to it.
2. GPIB driver caused Windows 2000 restarting when whatever is chosen in start menu (standy, shut down or logoff). When GPIB is disabled in device manager, this problem disappeared.
Anybody has experence about it?
Thank you so much for your any opinions?
LuI
Active Participant
06-28-2005 02:37 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Ya-hoo,
have'nt seen such behaviour with any of my installation.
You know, PCI is not _that_ fixed standard. You may check the PCI version and supply voltage of both your motherboard and PCI-GPIB card.
You may also want to check the PCs BIOS for any PCI-related settings. Depends on the BIOS, so you have to ckeck yourself. But there might be some settings that disable ressource assignment to new devices or block some ressources from being assigned by the BIOS. It might even help to simply put the card into another slot.
This all sounds mystic, but one or the other way it _is_ mystic ;-))
Greetings from Germany!
--
Uwe
have'nt seen such behaviour with any of my installation.
You know, PCI is not _that_ fixed standard. You may check the PCI version and supply voltage of both your motherboard and PCI-GPIB card.
You may also want to check the PCs BIOS for any PCI-related settings. Depends on the BIOS, so you have to ckeck yourself. But there might be some settings that disable ressource assignment to new devices or block some ressources from being assigned by the BIOS. It might even help to simply put the card into another slot.
This all sounds mystic, but one or the other way it _is_ mystic ;-))
Greetings from Germany!
--
Uwe
LuI
Active Participant
06-28-2005 02:37 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Ya-hoo,
have'nt seen such behaviour with any of my installation.
You know, PCI is not _that_ fixed standard. You may check the PCI version and supply voltage of both your motherboard and PCI-GPIB card.
You may also want to check the PCs BIOS for any PCI-related settings. Depends on the BIOS, so you have to ckeck yourself. But there might be some settings that disable ressource assignment to new devices or block some ressources from being assigned by the BIOS. It might even help to simply put the card into another slot.
This all sounds mystic, but one or the other way it _is_ mystic ;-))
Greetings from Germany!
--
Uwe
have'nt seen such behaviour with any of my installation.
You know, PCI is not _that_ fixed standard. You may check the PCI version and supply voltage of both your motherboard and PCI-GPIB card.
You may also want to check the PCs BIOS for any PCI-related settings. Depends on the BIOS, so you have to ckeck yourself. But there might be some settings that disable ressource assignment to new devices or block some ressources from being assigned by the BIOS. It might even help to simply put the card into another slot.
This all sounds mystic, but one or the other way it _is_ mystic ;-))
Greetings from Germany!
--
Uwe
JenK
NI Employee (retired)
06-28-2005 08:07 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Ya-hoo,
What version of the NI-488.2 driver do you have? The latest version for Windows 2000 is 2.3. If you do not have this driver I would suggest you install it from here. Please repost if you have more information or if you have the current driver version and you still see this same behavior.
JenK
What version of the NI-488.2 driver do you have? The latest version for Windows 2000 is 2.3. If you do not have this driver I would suggest you install it from here. Please repost if you have more information or if you have the current driver version and you still see this same behavior.
JenK
06-28-2005 09:21 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Thanks Uwe and Jenk.
Problem was solved. It caused by chipset driver. After Chipset driver was installed properly, everything is ok.
THank you very much for your response.
Problem was solved. It caused by chipset driver. After Chipset driver was installed properly, everything is ok.
THank you very much for your response.
