MAX 4.1 et fsecure

Bonjour,
Comme beaucoup d'entre vous j'ai eu pas mal de soucis lorque je ma suis mis à jour vers DAQ 8.3. En effet nos firewall bloquent les requêtes TCP de MAX4.1
Dans mon cas j'utlise Fsecure comme logiciel et voici comment je m'en suis sorti:
Après avoir installé nidaq 8.3 il faut configurer manuellement le contrôle d'accès de plusieurs fichiers ni.
Pour celà ouvrez fsecure. Cliquez sur "protection internet" puis sur "configurer" en face de "applications autorisées/refusées".
Une fenêtre s'ouvre. Elle liste vos programmes bloqués ou autorisés.
Cliquez sur ajouter, parcourir et allez chercher le fichier C:\Program Files\National Instruments\MAX\NIMax.exe.
Dans les cadre "Action sur une tentative de connexion inconnue" sélectionnez "application et port" et "autoriser" dans les sections client et serveur.
Reproduisez cette méthode pour les fichiers:
          C:\Program Files\National Instruments\MAX\nimxs.exe
            C:\Program Files\National Instruments\MAX\NiAsstnt.exe
            C:\Windows\systeme32\nipalsm.exe
            C:\Program Files\National Instruments\Ni-DAQ\HWConfig\nidevmon.exe
Une petite réparation de l'installation de Nidaq 8.3 et le tour est joué
Cette méthode n'est peut être pas la plus sécurisée possible mais dans mon cas cela a été le seul moyen de m'en sortir.

Hello,
I had some problems when setting up NiDaq 8.3. My MAX 4.1 couldn’t log
its data base.
I use fsecure software as firewall and this is how I did to have good
work with MAX.
After installation of nidaq 8.3 I had to configure manually the acces control
of fsecure:
I am using
a French version of fsecure and this is a translation of what I did (I hope it’s
the same thing for other langage)
Open
Fsecure, clic on « internet » and « configure »
Then clic « Add »
Browse C:\Program Files\National Instruments\MAX\NIMax.exe.
And allow all application and ports for this software
Make the
same thing for:
C:\Program Files\National Instruments\MAX\nimxs.exe
C:\Program Files\National Instruments\MAX\NiAsstnt.exe
C:\Windows\systeme32\nipalsm.exe
C:\Program Files\National Instruments\Ni-DAQ\HWConfig\nidevmon.exe
After repair Nidaq 8.3 and restart windows.
Normally it works.

Similar Messages

WHEN TRYING TO OPEN FIREFOX, GET MESSAGE PATFORM VERSON 8.0 NOT COMPATBABLE WITH MIN VERSION 7.D MAX VERSION 7.D

I AM TRYING TO OPEN FIREFOX, AND GET A URL MESSAGE: PLATFORM VERSION 8.0 NOT COPATABLE WITH MIN VERSION 7.D MAX VERSI 7.D

If you use ZoneAlarm Extreme Security then disable Virtualization and reinstall Firefox.
*http://kb.mozillazine.org/Browser_will_not_start_up#XULRunner_error_after_an_update
See also:
*[[/questions/880050]]

I'm getting this error statement: XULRUNNER error: platform version 6.0.2 is not compatible with min etc max etc6.0.1 - what is this about and how can it be corrected?

This is what I think may have happened. The other day, Thursday Sept 8th, I shut down my pc in the middle of a Firefox upgrade. Now when I try to access Firefox on my pc, I get this error message:
XULRUNNER Error: Platform version '6.0.2 is not compatible with min Version >= 6.0.1 max Version < 6.0.1
What is this about and how can I retsore access to Firefox on my pc?

If you use ZoneAlarm Extreme Security then try to disable Virtualization.
Do a clean reinstall and delete the Firefox program folder.
* http://kb.mozillazine.org/Browser_will_not_start_up#XULRunner_error_after_an_update
*[[/questions/869812]]
*[[/questions/869951]]

How much RAM can my Macbook Pro hold MAX?

Can my Macbook Pro hold a MAX of 8GB or is it just 4GB? I'm getting different answers online and I'm a little annoyed at this point. My computer specs currently are:
15 inch Laptop
MacBook Pro 2.6 GHz Intel Core 2 Duo
2 GB 667 MHz DDR2 SDRAM.
Got my computer in 2009.
At Crucial.com it says it can hold up to 8GB when I select my computer processor speed from their list, but I noticed it saying DDR3 (and I don't know what that means to be honest). Here's the link:
http://www.crucial.com/store/mpartspecs.aspx?mtbpoid=7F3A5584A5CA7304
To the best of my knowledge I selected the correct computer, which I own, from their list.
Under "About This Mac", on my computer, it says DDR2 for the memory, on Crucial.com it says DDR3. As a result I'm confused and will that cause problems?
I'll be getting my RAM kit from Crucial.com, so do I buy the 4BG kit, because that's all my laptop can handle, or is it OK to get the 8GB kit, which says DDR3?
I do a lot of video and audio, so I would like to get my RAM up to 8 GB if it will.
Thanks

One more question friend....You've been so helpful
Will these two sticks work together on my machine?
2GB, 200-pin SODIMM, DDR2 PC2-5300 memory module
http://www.crucial.com/store/mpartspecs.aspx?mtbpoid=B54C51B4A5CA7304
along with a...
4GB 200-pin SODIMM DDR2 PC2-6400 Memory Module
http://www.amazon.com/Crucial-CT51264AC800-200-pin-SODIMM-PC2-6400/dp/B001RB21JE
So these two would add up to 6GB total. Now the ONLY DIFFERENCE that I see is the 2GB stick is PC2-5300(667Mhz)speed and the 4GB stick is PC2-6400(800Mhz)speed. I understand that my machine won't run at the 800Mhz speed that the PC2-6400 stick is designed for, cause my machine says 667 under the memory info. From what I read online, it's ok to put a higher Mhz stick in there, it will just cap at 667Mhz speed? But.......both sticks are DDR2, which is right for my computer, but will the 667 MHz with a 800 Mhz be a huge no-no to run together? At this point I think that is my main concern! If I can't do this, than I think I'll have to go with the 2x2GB kit for 4GB total, but I REALLY would like to run 6GB.
Shew.... :P
Thanks again!

How to find the max data transfer rate(disk speed) supported by mobo?

I plan on replacing my current HDD with a new and bigger HDD.
For this I need to know the max data transfer rate(disk speed) that my mobo will support. However, dmidecode is not telling me that. Am I missing something?
Here's dmidecode:
# dmidecode 2.11
SMBIOS 2.5 present.
80 structures occupying 2858 bytes.
Table at 0x000F0450.
Handle 0xDA00, DMI type 218, 101 bytes
OEM-specific Type
Header and Data:
DA 65 00 DA B2 00 17 4B 0E 38 00 00 80 00 80 01
00 02 80 02 80 01 00 00 A0 00 A0 01 00 58 00 58
00 01 00 59 00 59 00 01 00 75 01 75 01 01 00 76
01 76 01 01 00 05 80 05 80 01 00 D1 01 19 00 01
00 15 02 19 00 02 00 1B 00 19 00 03 00 19 00 19
00 00 00 4A 02 4A 02 01 00 0C 80 0C 80 01 00 FF
FF 00 00 00 00
Handle 0xDA01, DMI type 218, 35 bytes
OEM-specific Type
Header and Data:
DA 23 01 DA B2 00 17 4B 0E 38 00 10 F5 10 F5 00
00 11 F5 11 F5 00 00 12 F5 12 F5 00 00 FF FF 00
00 00 00
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A17
Release Date: 04/06/2010
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 4096 kB
Characteristics:
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
EDD is supported
Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
BIOS Revision: 17.0
Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: OptiPlex 755
Version: Not Specified
UUID: 44454C4C-5900-1050-8033-C4C04F434731
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified
Handle 0x0200, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: 0PU052
Version:
Handle 0x0300, DMI type 3, 13 bytes
Chassis Information
Manufacturer: Dell Inc.
Type: Space-saving
Lock: Not Present
Version: Not Specified
Asset Tag:
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
Handle 0x0400, DMI type 4, 40 bytes
Processor Information
Socket Designation: CPU
Type: Central Processor
Family: Xeon
Manufacturer: Intel
ID: 76 06 01 00 FF FB EB BF
Signature: Type 0, Family 6, Model 23, Stepping 6
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Not Specified
Voltage: 0.0 V
External Clock: 1333 MHz
Max Speed: 5200 MHz
Current Speed: 2666 MHz
Status: Populated, Enabled
Upgrade: Socket LGA775
L1 Cache Handle: 0x0700
L2 Cache Handle: 0x0701
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 2
Core Enabled: 2
Thread Count: 2
Characteristics:
64-bit capable
Handle 0x0700, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 32 kB
Maximum Size: 32 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: None
System Type: Data
Associativity: 8-way Set-associative
Handle 0x0701, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 6144 kB
Maximum Size: 6144 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: <OUT OF SPEC>
Handle 0x0800, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PARALLEL
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-25 female
Port Type: Parallel Port PS/2
Handle 0x0801, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SERIAL1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0802, DMI type 126, 9 bytes
Inactive
Handle 0x0803, DMI type 126, 9 bytes
Inactive
Handle 0x0804, DMI type 126, 9 bytes
Inactive
Handle 0x0805, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0806, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB2
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0807, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB3
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0808, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB4
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0809, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB5
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB6
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB7
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB8
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: ENET
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: RJ-45
Port Type: Network Port
Handle 0x080E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MIC
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x080F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0810, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-IN
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0811, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HP-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0812, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MONITOR
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x090A, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT1
Type: x1 Proprietary
Current Usage: In Use
Length: Long
Characteristics:
PME signal is supported
Handle 0x0901, DMI type 126, 13 bytes
Inactive
Handle 0x0902, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT2
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 2
Characteristics:
5.0 V is provided
3.3 V is provided
PME signal is supported
Handle 0x0903, DMI type 126, 13 bytes
Inactive
Handle 0x0904, DMI type 126, 13 bytes
Inactive
Handle 0x0905, DMI type 126, 13 bytes
Inactive
Handle 0x0906, DMI type 126, 13 bytes
Inactive
Handle 0x0907, DMI type 126, 13 bytes
Inactive
Handle 0x0908, DMI type 126, 13 bytes
Inactive
Handle 0x0A00, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Disabled
Description: Intel Graphics Media Accelerator 950
Handle 0x0A02, DMI type 10, 6 bytes
On Board Device Information
Type: Ethernet
Status: Enabled
Description: Intel Gigabit Ethernet Controller
Handle 0x0A03, DMI type 10, 6 bytes
On Board Device Information
Type: Sound
Status: Enabled
Description: Intel(R) High Definition Audio Controller
Handle 0x0B00, DMI type 11, 5 bytes
OEM Strings
String 1: www.dell.com
Handle 0x0D00, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0F00, DMI type 15, 29 bytes
System Event Log
Area Length: 2049 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: Memory-mapped physical 32-bit address
Access Address: 0xFFF01000
Status: Valid, Not Full
Change Token: 0x00000018
Header Format: Type 1
Supported Log Type Descriptors: 3
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: System limit exceeded
Data Format 2: System management
Descriptor 3: Log area reset/cleared
Data Format 3: None
Handle 0x1000, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 4
Handle 0x1100, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_1
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Manufacturer: AD00000000000000
Handle 0x1101, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_3
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1102, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_2
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1103, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_4
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1300, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FDFFFFFF
Range Size: 4064 MB
Physical Array Handle: 0x1000
Partition Width: 1
Handle 0x1400, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1100
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1401, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1101
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1402, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1102
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1403, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1103
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1410, DMI type 126, 19 bytes
Inactive
Handle 0x1800, DMI type 24, 5 bytes
Hardware Security
Power-On Password Status: Enabled
Keyboard Password Status: Not Implemented
Administrator Password Status: Enabled
Front Panel Reset Status: Not Implemented
Handle 0x1900, DMI type 25, 9 bytes
System Power Controls
Next Scheduled Power-on: *-* 00:00:00
Handle 0x1B10, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD00
Handle 0x1B11, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD01
Handle 0x1B12, DMI type 126, 12 bytes
Inactive
Handle 0x1B13, DMI type 126, 12 bytes
Inactive
Handle 0x1B14, DMI type 126, 12 bytes
Inactive
Handle 0x2000, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected
Handle 0x8100, DMI type 129, 8 bytes
OEM-specific Type
Header and Data:
81 08 00 81 01 01 02 01
Strings:
Intel_ASF
Intel_ASF_001
Handle 0x8200, DMI type 130, 20 bytes
OEM-specific Type
Header and Data:
82 14 00 82 24 41 4D 54 01 01 00 00 01 A5 0B 02
00 00 00 00
Handle 0x8300, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 00 83 14 00 00 00 00 00 C0 29 05 00 00 00
F8 00 4E 24 00 00 00 00 0D 00 00 00 02 00 03 00
19 04 14 00 01 00 01 02 C8 00 BD 10 00 00 00 00
00 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00
Handle 0x8800, DMI type 136, 6 bytes
OEM-specific Type
Header and Data:
88 06 00 88 5A 5A
Handle 0xD000, DMI type 208, 10 bytes
OEM-specific Type
Header and Data:
D0 0A 00 D0 01 03 FE 00 11 02
Handle 0xD100, DMI type 209, 12 bytes
OEM-specific Type
Header and Data:
D1 0C 00 D1 78 03 07 03 04 0F 80 05
Handle 0xD200, DMI type 210, 12 bytes
OEM-specific Type
Header and Data:
D2 0C 00 D2 F8 03 04 03 06 80 04 05
Handle 0xD201, DMI type 126, 12 bytes
Inactive
Handle 0xD400, DMI type 212, 242 bytes
OEM-specific Type
Header and Data:
D4 F2 00 D4 70 00 71 00 00 10 2D 2E 42 00 11 FE
01 43 00 11 FE 00 0F 00 25 FC 00 10 00 25 FC 01
11 00 25 FC 02 12 00 25 FC 03 00 00 25 F3 00 00
00 25 F3 04 00 00 25 F3 08 00 00 25 F3 0C 07 00
23 8F 00 08 00 23 F3 00 09 00 23 F3 04 0A 00 23
F3 08 0B 00 23 8F 10 0C 00 23 8F 20 0E 00 23 8F
30 0D 00 23 8C 40 A6 00 23 8C 41 A7 00 23 8C 42
05 01 22 FD 02 06 01 22 FD 00 8C 00 22 FE 00 8D
00 22 FE 01 9B 00 25 3F 40 9C 00 25 3F 00 09 01
25 3F 80 A1 00 26 F3 00 A2 00 26 F3 08 A3 00 26
F3 04 9F 00 26 FD 02 A0 00 26 FD 00 9D 00 11 FB
04 9E 00 11 FB 00 54 01 23 7F 00 55 01 23 7F 80
5C 00 78 BF 40 5D 00 78 BF 00 04 80 78 F5 0A 01
A0 78 F5 00 93 00 7B 7F 80 94 00 7B 7F 00 8A 00
37 DF 20 8B 00 37 DF 00 03 C0 67 00 05 FF FF 00
00 00
Handle 0xD401, DMI type 212, 172 bytes
OEM-specific Type
Header and Data:
D4 AC 01 D4 70 00 71 00 03 40 59 6D 2D 00 59 FC
02 2E 00 59 FC 00 6E 00 59 FC 01 E0 01 59 FC 03
28 00 59 3F 00 29 00 59 3F 40 2A 00 59 3F 80 2B
00 5A 00 00 2C 00 5B 00 00 55 00 59 F3 00 6D 00
59 F3 04 8E 00 59 F3 08 8F 00 59 F3 00 00 00 55
FB 04 00 00 55 FB 00 23 00 55 7F 00 22 00 55 7F
80 F5 00 58 BF 40 F6 00 58 BF 00 EB 00 55 FE 00
EA 00 55 FE 01 40 01 54 EF 00 41 01 54 EF 10 ED
00 54 F7 00 F0 00 54 F7 08 4A 01 53 DF 00 4B 01
53 DF 20 4C 01 53 7F 00 4D 01 53 7F 80 68 01 56
BF 00 69 01 56 BF 40 FF FF 00 00 00
Handle 0xD402, DMI type 212, 152 bytes
OEM-specific Type
Header and Data:
D4 98 02 D4 70 00 71 00 00 10 2D 2E 2D 01 21 FE
01 2E 01 21 FE 00 97 00 22 FB 00 98 00 22 FB 04
90 00 11 CF 00 91 00 11 CF 20 92 00 11 CF 10 E2
00 27 7F 00 E3 00 27 7F 80 E4 00 27 BF 00 E5 00
27 BF 40 D1 00 22 7F 80 D2 00 22 7F 00 45 01 22
BF 40 44 01 22 BF 00 36 01 21 F1 06 37 01 21 F1
02 38 01 21 F1 00 39 01 21 F1 04 2B 01 11 7F 80
2C 01 11 7F 00 4E 01 65 CF 00 4F 01 65 CF 10 D4
01 65 F3 00 D5 01 65 F3 04 D2 01 65 FC 00 D3 01
65 FC 01 FF FF 00 00 00
Handle 0xD403, DMI type 212, 157 bytes
OEM-specific Type
Header and Data:
D4 9D 03 D4 70 00 71 00 03 40 59 6D 17 01 52 FE
00 18 01 52 FE 01 19 01 52 FB 00 1A 01 52 FB 04
1B 01 52 FD 00 1C 01 52 FD 02 1D 01 52 F7 00 1E
01 52 F7 08 1F 01 52 EF 00 20 01 52 EF 10 21 01
52 BF 00 22 01 52 BF 40 87 00 59 DF 20 88 00 59
DF 00 E8 01 66 FD 00 E9 01 66 FD 02 02 02 53 BF
00 03 02 53 BF 40 04 02 53 EF 00 05 02 53 EF 10
06 02 66 DF 00 07 02 66 DF 20 08 02 66 EF 00 09
02 66 EF 10 17 02 66 F7 00 18 02 66 F7 08 44 02
52 BF 40 45 02 52 BF 00 FF FF 00 00 00
Handle 0xD800, DMI type 126, 9 bytes
Inactive
Handle 0xDD00, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 00 DD 00 01 00 00 00 10 F5 00 00 00 00 00
00 00 00
Handle 0xDD01, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 01 DD 00 01 00 00 00 11 F5 00 00 00 00 00
00 00 00
Handle 0xDD02, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 02 DD 00 01 00 00 00 12 F5 00 00 00 00 00
00 00 00
Handle 0xDE00, DMI type 222, 16 bytes
OEM-specific Type
Header and Data:
DE 10 00 DE C1 0B 00 00 10 05 19 21 01 00 00 01
Handle 0x7F00, DMI type 127, 4 bytes
End Of Table
Hdparm also does not tell me the max data transfer rate (disk speed) of my current drive although this link : www.wdc.com/en/library/sata/2879-001146.pdf says that it is 3.0Gb/s
and here's hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: WDC WD800JD-75JNC0
Firmware Revision: 06.01C06
Standards:
Supported: 6 5 4
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156250000
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 76293 MBytes
device size with M = 1000*1000: 80000 MBytes (80 GB)
cache/buffer size = 8192 KBytes
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 8
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
SET_MAX security extension
Automatic Acoustic Management feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* SMART error logging
* SMART self-test
* Gen1 signaling speed (1.5Gb/s)
* Host-initiated interface power management
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
Checksum: correct
Last edited by Inxsible (2011-03-27 04:40:49)

I just checked my BIOS and my current setting is set at IDE although it also mentions that the default should be AHCI. Currently I have a dual boot of Windows 7 (need it for Tax software) and Arch
So I guess, when I get the new HDD, I will first set it to AHCI and then install the OSes on it. See if NCQ helps any, and if not I will turn it back and re-install (if I have to). I am planning to have Windows only in virtualbox in the new drive.
Anyhoo, while I was in the BIOS I found two things which I had questions about :
1) Under Onboard Devices --> Integrated NIC , my setting is currently set at "On w/PXE" and it says the default should be just "On". Would it be ok to change it back to On since its a single machine and its not booting an OS on any server. I just don't want to have to re-install anything now since I will be doing that in the new HDD.
2) How would I know whether my BIOS would support a 64 bit OS in Virtualbox? I checked some setting under Virtualization, but they weren't very clear.
I will edit this post and let you know exactly what settings were present under the Virtualization sub-section.

At max how many columns is advisable to create in a table/view

Hi All,
I have two transaction table from which i want to create a simple view or materialized view. But the number of columns is about 200. So i want to know at max how many columns is advisable from the performance point of view.
Even though i will create 200 columns in a view , for a perticular client installation i may not use all the columns.
one more thing i will never use 200 columns in the select statement . At a time i will use only 4/5 columns.
It may happen from this four column one column will be the 1st and 2nd column will be the 200th one.
I want to know how it affects the performance and in which scenario . Please help if any body knows or already faced this kind of scenario.
I am using oracle 10g .

Annapurna Nayak wrote:
thanks for ur reply .
We are going to use this view in a report , so if i will create it as simple view it will affect report performance. because the view script is too long ...so every time quring to a view will decrease the performance.
Are you asking me if it will? I think it probably won't but of course you have the means to test it to be sure, right?
As u said MV should be done with minimum possible column . what can be the maximum column in MV ..??It would be defined by the limits on:
* The maximum number of columns that a table can contain
* The size of the query needed to define the select statement
* Limitations on queries needed to maintain the data
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/limits003.htm#i288032

Remote system disconnected after installing MAX 4.7.3

Hello!
This topic is related to the topic you can find here.
In order to repair the Regional Settings issue in Windows (XP in my case) I used the System Configuration 1.1.3 update and it seems to work. I changed the Regional Settings to my local and installed the update. Silverlight does not crash anymore, so that is fixed. However, this created a new issue:
Now my remote devices (NI-1742 and NI-1746) status is always "disconnected". The devices are connected to a different subnet than the development computer. Pinging their IPs showed that they are there. I can connect to the cameras using the Real-time Project. However, in MAX the remote system status remains "disconnected". I tried to delete and re-create the devices in MAX but that did not work either.
I also tried the latter with Windows firewall on and off and updated the software with NI Update Service. On an another computer, which has not had the update yet, I can connect to and modify the devices.
In addition, I completely reinstalled the development system, but the issue persists.
Kind regards,
Mart
Solved!
Go to Solution.

Hey Mart,
It looks like this may be related to a possible bug introduced in MAX 4.7.3. I've uploaded Juurma.zip to our FTP site. Please obtain this .zip file by navigating to ftp://ftp.ni.com/outgoing.
This .zip file contains a patched version of mxRmCfg.dll. First, close all NI software and stop the NI System Web Server service and all its dependencies (you can get to your services by going to Start->Run and typing in services.msc). Then, navigate to this directory: C:\Program Files\National Instruments\Shared\MAX\Bin
You will need to rename the existing mxRmCfg.dll to mxRmCfg.bak, and copy the new version to that location. Restart your system, open MAX, and see if you can connect to and view your targets.
If this resolves your issue, PLEASE post back in this thread indicating as much. If not, let us know and we'll continue to investigate. Note that items on our FTP server will be removed after 48 hours, so let me know if you're unable to get that file in time
Justin E
National Instruments R&D

Max no of connections in the RFC receiver ?

Hi Guys,
when i increse the max no of connections from 1 to 5 , i am getting the following errors, i saw we can give up to 50. why it is not taking more than 1.
SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: resource error: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool RfcClient[cc_sap_recv]eb54a45a23bc3e3eabd929cc3f3b0688 is exhausted. The current pool size limit (max connections) is 1 connections.</SAP:AdditionalText>
any help would be appreciated
Thanks,
srini

In the Help it says 50!
http://help.sap.com/saphelp_nw04/helpdata/en/c8/e80440a832e369e10000000a155106/frameset.htm
However, a fix for how to trace the exact Error is found here:
http://help.sap.com/saphelp_nw04s/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm

MAX function to get recent date doesn't work as expected

Hi,
I recently started working on Oracle and came across this problem. I coded below given query to get the latest date from table and compare it with Sysdate + 1 timestamp. I am not able to understand what I coded wrong but the query gives me wrong results as explained below :
select NVL(MAX(to_char(max(last_update),'mm/dd/yyyy hh12:mi:ss AM')), to_char(sysdate + 1,'mm/dd/yyyy')||' 12:00:00 AM')
from Audit_Table_Name
where col1 = 'AA'
and location_type = 'STATE'
and original_flag = 'Y'
group by col1,location_type,original_flag;
Here Max(last_update) from Audit Table Contains value --> 08/25/2009 12:00:00 AM
Note : Data type of last_update is Date
so ideally speaking it should give 08/26/2009 12:00:00 AM but surprisingly it is giving 08/25/2009 12:00:00 AM as output. Anyone can explain why this is happening and what we need to do to get correct results?
Regards,
Amol

1) Why would you expect this to return a date of 8/26? NVL returns the first parameter unless it is NULL. If the first parameter is NULL, it returns the second parameter. Since
MAX(to_char(max(last_update),'mm/dd/yyyy hh12:mi:ss AM'))returns a non-NULL value, that value will be returned. Oracle never needs to evaluate the second parameter
to_char(sysdate + 1,'mm/dd/yyyy')||' 12:00:00 AM'You state that you want to compare the MAX( last_update ) to SYSDATE + 1. Your code isn't doing a comparison now. And it's not clear from your description what comparison you actually want to do. Can you elaborate a bit on what you want to compare and what the output should be depending on the result of that comparison?
2) You almost certainly want to do as much of the logic as possible using dates and only convert to a string at the very end. Otherwise, you risk comparing two strings that represent dates using string comparison semantics and getting a result you don't expect.
3) My guess (and it is just a guess) is that you want something like
SELECT GREATEST( max(last_update), trunc(sysdate+1) )or
SELECT TO_CHAR( GREATEST( max(last_update), trunc(sysdate+1) ), 'mm/dd/yyyy hh12:mi:ss AM' )Justin

Can not see a sbRIO in MAX running on a virtual machine

I am trying to connect a sbRIO-9606 to a Windows 7 virtual machine (VMWare) running on a MacPro. I can open a CMD prompt and ping the sbRIO but when I run MAX, it does not appear in Remote Systems.
The virtual NIC is bridged to the pyhsical one (on the MAC)
Does anyone have experience doing this, or know why I cannot see the sbRIO?

Hi jaketc,
I've had similar issues at times depending on how my host and guest operating sytems network interfaces are configured. It sounds like your settings are correct (bridged), but it is difficult to guarantee. The first step I usually take is disable any network interfaces (on the host and guest OS) that are not critical to connecting to the remote target.
A more generic answer is to walk through the troubleshooting steps in this document, but it won't cover the virtualized OS considerations of your setup:
Why Does My CompactRIO Controller or Single-Board RIO Not Show Up in Measurement & Automation Explor...
Because you can ping the target, it sounds like the Single-Board RIO already has an IP address, you know what it is, and ethernet communication can be established. When I've been in that situation in the past, I've been able to manually add the RIO target to MAX. To find a system that is already configured with an IP address, simply right-click on Remote Systems and select Create New. Enter the appropriate configuration information in the dialog box, and MAX will manually place that system in the Remote Systems listing and all tasks will function properly.
Cheers,
Spex
National Instruments
To the pessimist, the glass is half empty; to the optimist, the glass is half full; to the engineer, the glass is twice as big as it needs to be...

Crystal 2008: Text, Can Grow=true, Max Lines=0, truncated after 2 lines

I have a fairly simple, grouped report with a handful of fields in each Detail section, one of which is a note/text field. I put the text field on its own line and set Can Grow = true, max lines = 0 so that it will display what it needs to display.
This happens to be a crystalreports.com report using data coming from Salesforce, and I can see in the source report that I have about 7 lines of text for one of my groups, but crystal is truncating it after two lines, and in the middle of a word.
The word ('for') doesn't have any obvious special characters in it, so I'm guessing that there's some sort of character limit that I'm bumping up against.
I have another record that is returning more than two lines, though; are there particular characters that could cause this? I can scrub the data and/or put Salesforce Validation Rules in place to try and prevent them from getting in.
Any suggestions would be appreciated.
Duncan

Please re-post if this is still an issue or purchase a case and have a dedicated support engineer work with you directly:
http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryID=11522300?resid=-Z5tUwoHAiwAAA8@NLgAAAAS&rests=1254701640551

Détecter carte pickering 50-295-121-10/12 sur cible déportée dans MAX

Bonjour,
Je suis en train de développer une application de test temps réel dans laquelle je dois piloter une carte Pickering de type "50-295-121-10/12". J'aurais donc plusieurs questions qui sont pour l'heure sans réponse.
Premièrement, je cherche à détecter cette carte dans MAX afin d'avoir son identifiant pour communiquer avec elle. Cette carte est intégrée dans un bus PCI sur un PC cible RT. J'ai pour le moment déployé la dll "pipx40_32.dll" ainsi que les fichiers "inf" sur ma cible RT. Or je ne peux toujours pas la voir. Est-ce du au fait que la carte que j'utilise est une carte PCI et non PXI? Quelle doit être la marche à suivre pour parvenir à la détecter dans MAX? Pour info, j'ai suivi les instructions suivantes : http://www.pickeringtest.com/pdf/PI_Installation_Instructions.pdf
Deuxièmement, je souhaite utiliser le custom device fournit nativement par NI lors de l'installation de Véristand pour piloter cette carte, à savoir :"Custom Device Pickering 40-295". Etant donné que la carte que j'utilise est une 50-295 et non une 40-295, vais-je pouvoir tout de même utiliser ce Custom Device où alors va-t-il falloir que j'en développe un nouveau?
Dans l'attente de vos réponses,
Cordialement,
Nicolas

Bonjour Nicolas,
Merci d'avoir posé votre question sur le forum de discussions de National Instruments,
J'aurais besoin de quelques informations supplémentaires,
Votre PC de développement est-il différent du PC RT dans lequel est insérée votre carte ?
Si ce n'est pas le cas, avez vous un accès depuis le réseau à ce PC RT ?
Par ailleurs, il pourrait être bon de savoir si le service windows NI Device Loader est bien actif, il permet la bonne communication entre un PC et un équipement, quelque soit le bus d'interface utilisé (USB, PCI, PXI... ).
Assurez vous également d'avoir tous vos drivers à jour.
En ce qui concerne un custum device sous Veristand :
Vous pouvez tester le custom device existant, mais le bon fonctionnement de votre application n'est pas garanti, et il pourrait donc être nécessaire de créer le votre.
En ésperant que ces premières pistes pourront vous aider,
Bien cordialement,
Vincent.O
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Été de LabVIEW 2014
12 présentations en ligne, du 30 juin au 18 juillet

I still haven't got the email for the 1 Year Creative Cloud with Adobe MAX

No Email for my 1 Year Ceative Cloud Membership
I purchased my Adobe MAX Full Conference Pass on the 24th of January. Its been about 14 days since then and i still have not recived my 1 Year Adobe Creative Cloud Membership from buying the pass. I have had to just through 4-5 of live chats and 2 phone calls, to no avail. All of the people that work at Customer Support just trasfer me somewhere else cause they don't know what to do, so I'm kind of stuck.
Any help would be much appreciated!
Thank you, Kyle

Hi Kyle,
Is the email address you use here on the forums the same one you used to register for MAX?
-Dave

Has anyone used a touch screen monitor with scxi.I am having video lock ups while using LV and MAX

I have a PCI-MIO-16XE-50 daq card (dev1) connected to a scxi-1000 chassis address 0 ID 1, with a scxi-1102,1163,1163,1162 slots 1,2,3,4 respectively.Cable is connected to daq card to 1102 card .Micro touch screen is used on com2. Have tried other serial ports 1,5. Touch screen works fine with windows until LabView and max is installed .Video lockups,Max failures occur.MAX seems to confict with touch screen.

Max is the NI interface for all the drivers. It may be a specific driver that is causing problems, perhaps NI-VISA. I would try installing things one piece at a time. Might want to start by uninstalling everything so that you start with a clean system. First install LabVIEW with no drivers at all. See if the Micro touch screen still works. Then try installing NI-DAQ. Install each of the drivers you need one at a time. If you don't need something, leave it out.

PCI-e wireless card causes lock ups Z87 MPower MAX

I've already asked this question once, but was part of an epic essay that I've decided to break down into smaller more manageable chunks (as unsurprisingly that one got no replies).
I've got an ASUS PCE-A66 wireless ac pci-e card. Had absolutely no issues with it in my old Z77 board, but I seem to be having a lot of issues with it in my new Z87 MPower MAX. System was locking up like mad when I was trying to install the drivers at first. Had to rip out the WiFi/Bluetooth/WiDi module to get the drivers installed but the system randomly hangs on boot up? Don't get the issues with the card unplugged and don't always get it with it plugged in, but there seems to be some form of conflict with it that I can't resolve. Has anyone else had any such issues with any PCI-e add in cards on this motherboard?
Specs are:
i7 4770k
MSI MPower MAX using .128 bios (will try the .131 later)
2x4GB Corsair Dominator Platinum 2400
Coolermaster Silent Pro Hybrid 1050w
EVGA NVidia GTX 780 SC ACX
Windows 8 Pro 64bit

Yes, old system was Win8 Pro 64 bit too and the drivers are Windows 8 certified. As I say though, I had no issues with it on the old build? Even got a replacement sent out by Amazon in case the card itself was damaged Did initially try to do a warm update of the hardware into the same OS installation but didn't play well so did a full re-install in the end. Tried standard and UEFI installs (just in case) and after a problem with my OCZ Vector 2 not being recognised I bought a new Samsung 840 Pro so was a virgin SSD installed on to as well.
I'll raise it directly with MSI but just wanted to know if anyone else had experienced anything similar with any wireless cards in this mobo.
Cheers for the reply though

MAX 4.1 et fsecure

Similar Messages

Maybe you are looking for