Burning PE3.02: memory allocation error

Similar Questions

• JNI memory allocation errors

  We took a 32-bit 10.1.2.3 B2B instance on Linux. We have dedicated as much memory as possible to the JVM and for some messages we receive memory errors in allocation of native code NYI (EDIFACT). When the native code allocate the memory?
  
  My real question is whether we should allocate less memory for the JAVA virtual machine in order to make more memory in the 32-bit address space available for the operating system for allowances of JNI or what we should do instead. There are many memory physical machine (16 G, no more than 4 G) it must have something to do with the 32-bit limitation.

  My mistake. Not sure which used Oracle of the API, but for native code memory must be allocated in the heap of BONES and not in the java heap.

  When execution of a piece of large capacity memory is requested, then the allocator of OS will try to find that OS bunch and if she couldn't then returns the bad_alloc exception (as far as I know, bad_alloc is a class in the C++ standard library). It needs a lot of debugging to know the exact cause and find a solution; and for this, Oracle's Support is certainly knocking on the right door.

  There are many memory physical machine (16 G, no more than 4 G) it must have something to do with the 32-bit limitation.

  This statement is interesting because as far as I know, Linux does not need to be defragmented and so if 4G memory is available then bad_alloc exception should not come. However I still can not comment because there are other factors as well that should be considered, as - size of the payload, of environment settings, by the memory of the affected user, by the maximum memory allocation process has allowed etc.

  Please check the above factors and try to find any occurrence of pattern/common between exceptions. I'm not a linux expert, but again, it seems that the problem is with OS and its parameters.

  Kind regards
  Anuj

• ADT - Java memory allocation error

  OK, this isn't really a problem of AIR, but maybe some of you have come across this.

  Compilation of command line with ADT used to work, but lately, I get this error:

  Error occurred during initialization of VM

  Could not reserve enough space for lots of things

  Error: Could not create the Virtual Machine Java.

  My machine is Windows 8 x 64, 8 GB of RAM, there is a lot of available memory.

  I tried editing adt.bat and adding - Xmx512m but I still get this error. I tried different values without success.

  Interestingly, it only happens when I compile for iOS.

  I don't know why this is happening. Any ideas?

  You use 32 or 64 bit java? If 32, try it with 64

• How to check the ESX memory for errors?

  Hi all

  I faced with the strange behavior of ESX:

  Some linux VMs (RHEL) were stopped. No error messages in the vCenter nor LabManager, I even thought that someone just connected and Runic stop.

  Below you will find information of ESX server logs:

  (1) the vmkernel newspaper:

  #grep - color = always-i ' 1922 [^ 0-9] "... /VMkernel *"

  .. (/ VMkernel.8:Dec 8 22:22:40 WKK1EC02 vmkernel: 290:11:51:47.230 cpu14:23084) UserDump: 1441: Dumping cartel 23079 (of the world 23084) to file the vmfs/volumes/4a4ce277-4a35505c-8828-0024817b058c/labmanager/1922/vmware-vmx-zdump.000...

  (2) the journal of the VM:

  # grep ' 08 Dec' /vmfs/volumes/4a4ce277-4a35505c-8828-0024817b058c/labmanager/1922/vmware-1.log '.

  16:53:49.164 Dec 08: vmx | GuestRpcSendTimedOut: message to the Toolbox has expired.
  16:54:14.972 Dec 08: vmx | GuestRpcSendTimedOut: message to the Toolbox has expired.
  21:59:05.262 Dec 08: mks | Cannot write the temporary image THUMB
  21:59:15.264 Dec 08: mks | Cannot write the temporary image THUMB
  21:59:30.270 Dec 08: mks | Cannot write the temporary image THUMB
  21:59:35.271 Dec 08: mks | Cannot write the temporary image THUMB
  21:59:45.275 Dec 08: mks | Cannot write the temporary image THUMB
  21:59:50.285 Dec 08: mks | Cannot write the temporary image THUMB
  22:00:00.274 Dec 08: mks | Cannot write the temporary image THUMB
  22:00:05.276 Dec 08: mks | Cannot write the temporary image THUMB
  22:01:15.410 Dec 08: mks | Cannot write the temporary image THUMB
  22:03:25.312 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:00.324 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:05.340 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:15.331 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:20.341 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:30.344 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:35.353 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:40.354 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:45.366 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:50.357 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:55.361 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:00.365 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:05.371 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:10.395 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:15.379 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:20.381 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:30.397 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:40.403 Dec 08: mks | Cannot write the temporary image THUMB
  22:20:45.541 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:10.580 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:15.538 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:20.554 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:25.545 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:30.580 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:35.591 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:40.537 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:45.629 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:50.583 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:55.616 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:00.590 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:05.638 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:10.595 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:15.582 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:20.622 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:25.583 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:30.627 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:35.673 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:40.588 Dec 08: mks | Panic: file lock (was the bug 49968)
  22:22:40.589 Dec 08: mks | Bora/lib/image/imageUtilPng.c:462 unrecoverable memory allocation failure
  22:23:21.438 Dec 08: mks | Backtrace:
  22:23:21.440 Dec 08: mks | Backtrace [0] 0x3ccf63d8 eip 0xa3f88cd
  22:23:21.442 Dec 08: mks | Backtrace [1] 0x3ccf6818 eip 0x9ff705c
  22:23:21.443 Dec 08: mks | Backtrace [2] eip 0xa2803bc 0x3ccf6b88
  22:23:21.443 Dec 08: mks | Backtrace [3] eip 0xa2803f6 0x3ccf6bb8
  22:23:21.444 Dec 08: mks | Backtrace [4] eip 0xa27fcc3 0x3ccf6bd8
  22:23:21.444 Dec 08: mks | Backtrace [5] eip 0xa27fd28 0x3ccf6c28
  22:23:21.445 Dec 08: mks | Backtrace [6] eip 0xa115582 0x3ccf7128
  22:23:21.445 Dec 08: mks | Backtrace [7] eip 0xa115717 0x3ccf7138
  22:23:21.445 Dec 08: mks | Backtrace [8] eip 0xa00d0a9 0x3ccf7168
  22:23:21.446 Dec 08: mks | Backtrace [9] 0x3ccf9278 0xa00dbef eip
  22:23:21.447 Dec 08: mks | Backtrace [10] eip 0x3ccf9298 0xa298217
  22:23:21.447 Dec 08: mks | Backtrace [11] eip 0x3ccf92b8 0xa298255
  22:23:21.448 Dec 08: mks | Backtrace [12] eip 0x3ccf92e8 0xa10bfe9
  22:23:21.448 Dec 08: mks | Backtrace [13] eip 0xa0f2e81 0x3ccf93c8
  22:23:21.504 Dec 08: mks | Backtrace [14] eip 0x160534fb 0x3ccf94b8
  22:23:21.505 Dec 08: mks | Backtrace [15] eip 00000000 0x1613ae3e
  22:23:21.507 Dec 08: mks | SymBacktrace [0] 0x3ccf63d8 eip in function 0xa3f88cd in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.508 Dec 08: mks | SymBacktrace [1] 0x3ccf6818 eip 0x9ff705c panic function in/usr/lib/vmware/bin/vmware-vmx of the object loaded on the 0x9f98000
  22:23:21.508 Dec 08: mks | SymBacktrace [2] 0x3ccf6b88 eip in function 0xa2803bc in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.511 Dec 08: mks | SymBacktrace [3] 0x3ccf6bb8 eip in function 0xa2803f6 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.511 Dec 08: mks | SymBacktrace [4] 0x3ccf6bd8 eip in function 0xa27fcc3 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.512 Dec 08: mks | SymBacktrace [5] 0x3ccf6c28 eip in function 0xa27fd28 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.513 Dec 08: mks | SymBacktrace [6] 0x3ccf7128 eip in function 0xa115582 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.514 Dec 08: mks | SymBacktrace [7] 0x3ccf7138 eip in function 0xa115717 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.515 Dec 08: mks | SymBacktrace [8] 0x3ccf7168 eip in function 0xa00d0a9 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.515 Dec 08: mks | SymBacktrace [9] 0x3ccf9278 eip in function 0xa00dbef in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.516 Dec 08: mks | SymBacktrace [10] 0x3ccf9298 eip in function 0xa298217 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.517 Dec 08: mks | SymBacktrace [11] 0x3ccf92b8 eip in function 0xa298255 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.518 Dec 08: mks | SymBacktrace [12] 0x3ccf92e8 eip in function 0xa10bfe9 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.519 Dec 08: mks | SymBacktrace [13] 0x3ccf93c8 eip in function 0xa0f2e81 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.519 Dec 08: mks | SymBacktrace [14] 0x3ccf94b8 eip 0x160534fb in function (zero) in the object /usr/lib/vmware/lib/libpthread.so.0 to the 0x1604e000
  22:23:21.520 Dec 08: mks | SymBacktrace [15] eip 00000000 0x1613ae3e based on cloning in object /usr/lib/vmware/lib/libc.so.6 loaded in 0 x 16069000
  22:23:21.520 Dec 08: mks | Msg_Post: error
  22:23:21.521 Dec 08: mks | [msg.log.error.unrecoverable] fatal error VMware ESX: (mks)
  22:23:21.521 Dec 08: mks | Bora/lib/image/imageUtilPng.c:462 unrecoverable memory allocation failure
  22:23:21.521 Dec 08: mks | [msg.panic.haveLog] a log file is available in "/ vmfs/volumes/4a4ce277-4a35505c-8828-0024817b058c/labmanager/1922/vmware.log".  [msg.panic.haveCore] a base file is available in "/ vmfs/volumes/4a4ce277-4a35505c-8828-0024817b058c/labmanager/1922/vmware-vmx-zdump.000".  [msg.panic.requestSupport.withLogAndCore] please request support and include the contents of the log file and the base file.  [msg.panic.requestSupport.vmSupport.vmx86]
  22:23:21.523 Dec 08: mks | To collect the data to submit to the VMware support, run 'vm-support.
  22:23:21.524 Dec 08: mks | [msg.panic.response] we will respond on the basis of your entitlement to support.
  22:23:21.525 Dec 08: mks | ----------------------------------------
  22:23:21.739 Dec 08: vmx | Watched VTHREAD thread 1 "mks" is dead
  22:23:22.651 Dec 08: 1 vcpu. Watched VTHREAD thread 0 "vmx" is dead
  22:23:22.740 Dec 08: vcpu-3 | Watched VTHREAD thread 0 "vmx" is dead
  22:23:22.741 Dec 08: vcpu-2 | Watched VTHREAD thread 0 "vmx" is dead
  22:23:22.743 Dec 08: vcpu-0 | Watched VTHREAD thread 0 "vmx" is dead

  I found the suggestion to check the ESX memory for problems.

  I found the information that ESX 3.0 was ramcheck service which could check the memory, but there is no such service in future versions of ESX.

  Could someone help me find how to check the memory without stopping the ESX Server (I could not migrate virtual machines per host)?

  The only way you will get a true test of the memory of the HOST must stop it and run the test directly. Any tool running in the ESX console will only have indirect access RAM. The vmkernel controls access to physical RAM.

• 836: failed to create the shared memory data, error 22 store segment

  Hi, I am new to timesten and databases in general, and I'm testing the database timesten to test.
  
  I am running ubuntu linux in virtualbox and have java 6 is installed. So far, I installed the timesten database and configured the sys.odbc.ini to create a new database. However, it seems that I can't connect to a database.
  
  I connect with the orattadmin of the user (which belongs to groups both timesten and ttadmin)
  
  I run the commandes./ttenv.sh and I have the classpath for ttjdbc6.jar in it.
  then I run le./ttisql.sh, and when I try to connect to mydatabase or any other database present in the sample folder I get:
  
  $. / ttisql
  
  Copyright (c) 1996-2011, Oracle. All rights reserved.
  Type? or 'aid' help, type "exit" to leave the ttIsql.
  
  
  Command > Connect "dsn = mytest_ttdb";
  836: failed to create the shared memory data, error 22 store segment
  The command failed.
  
  what I am doing wrong? What can I do?
  
  Thanks for your time

  A data store active TimesTen consists of a single shared memory segment allocated from o/s. The size of this segment is PermSize + TempSize + LogBufMB + ~ 20 MB. This allowance will not allow the o/s unless the 'package' kernel parameter has a value greater than the requested size of the segment. According to the Guide of Installation TimesTen, you set various parameters of the kernel on the appropriate values (memory shared, semaphores, etc.).

  Chris

• Linux kernel parameters and Oracle memory allocations.

  I'm currently creating an Oracle 11 G R2 in database, on a Linux (SLES 11) OS. The software OS and DB are the two 64-bit.
  I wondered about the optimal method of memory allocation shared, such that I can get the automatic memory management to recognize 12G of memory (which allows 4 g for the operating system and other pieces).
  
  I put the kernel parameters are:
  SHMMAX: 8589934592 (the recommended physical memory/2).
  SHMALL: 3145728 (giving a total of 12 GB of shared memory allocation that the page size is 4096).
  
  The way I read the documentation, it must free up enough shared memory to allow the specification of a memory_max_target and memory_target "11 g". I'm getting 11G to ensure that I am not ruin by a few bytes (if it all works, I will develop to 12G).
  However, whenever I try a startup, I get the ' ORA-00845: not supported on this system MEMORY_TARGET' error.
  It disappears if I create a great shmfs block using a mount command, but I was under the impression you had is no longer to do with 64-bit and Oracle 11 G system.
  
  Could someone clarify a little bit about what I'm doing wrong and where I should be looking for the answer?
  
  See you soon,.
  
  Rich

  Note 749851.1 ID and ID 460506.1:

  AMM all SGA memory is attributed by creating the files under/dev/SHM. When Oracle DB not allowances of SGA that HugePages reserved/does not serve. The use of the AMM is absolutely incompatible with HugePages.

  eseentially, AMM requires that/dev/SHM.

• Satellite Pro A100 - NMI memory parity error parity check

  Sometimes I get this BSOD error during 2 months.
  Hardware malfunction call your provider for support NMI: Parity Check / Memory Parity Error * the system stopped *.

  It can occur if the laptop is asleep, or even refreshing a screen save or Stand-By condition.
  Model PSAAPE - 00s00KEN 2 GB installed. I checked that the memory is installed correctly. It's a laptop very clean with no dust clutter things. Aside from the Ram "goes wrong" and developing a fault, can anyone suggest another cause? It doesn't seem to be an obvious solution to this problem on a forum I've seen so far. Maybe it's my RAM that fails (but it seems to do it when he is not be underlined!) It could be the video drivers... who knows? I hope somebody.

  Hello!

  In your case, I would check the RAM, I think that's the problem.

  You can do this with Memtest86:
  http://Memtest86.com/
  Memtest86 is a diagnostic tool to check the RAM. Here, you can also download a CD image.
  It s easy to use. Run the test of 3-4 hours and then you will see if the RAM has some errors.

  Good bye

• Satellite P200 - Parity Check / Memory Parity Error

  Hi all experts!

  After updating a driver, I get this above mentioned message.
  + Message ' hardware malfunction NMI Parity Check / Memory Parity Error.

  But just at the moment where the P200 falls in sleep mode. I can't wake up and have to do a hard reboot. Windows is starting and works perfectly and everything seems to be okay!

  Any idea?

  Thanks in advance!
  YB

  Hello

  This behavior can occur if a hardware component malfunctions, or if it has installed the damaged or incompatible drivers.
  I think that you should remove the driver updated or installed first.
  If this does not work, test the laptop with preinstalled system cool.

  Finally if this is insufficient, a hardware malfunction might be possible.
  In this case the RAM modules need to be tested as the first part.

• Photosmart HP5520: 5520 HP Photosmart Memory Card Error

  My Photosmart HP5520 will print from my IPhone and IPad wireless, however, on the touch screen memory card error appears saying "memory card error. Please remove the memory card. There is no memory card in the machine and I tried to unplug and disconnect when turned on several times. Can anyone help please?

  Hi @Bunters73,

  Welcome to the HP Forums!

  I see you found the error, "memory card error. Please remove the memory card. "With your printer Photosmart HP 5520. I'm happy to help you!

  Please try an another hard reset, as described in this post, How to perform a hard reset, by @Rich1. It is important that the power cable from the printer is plugged directly into the wall outlet, not a surge protector. Questions when it is connected to an uninterruptible power supply/Strip/surge protector power. This is true for printers and ink jet.

  Then I would try to make sure that the firmware in the printer is up-to-date. Get updates of the printer.

  If this does not resolve your problem, then the printer may need to be repaired / replaced. Please contact HPtelephone support for further assistance. (After you fill out the information, you will receive a phone number.) If you do not live in the United States / Canada region, please click the link below to get help from your region number. Language-country selector.

  Good luck!

  If this, or one of the posts on this thread, helped you to solve the problem, please click 'Accept as Solution' said post. To show you 'like', or that they are grateful for my post, please click the thumbs upwards below. If there is anything else I can do to help, please don't forget to let me know!

• Change the memory allocated for the graphics?

  Hi, I have an Equium A60-181 with graphics ATi Mobility Radeon 7000. For the moment, that this GPU is using 64 MB of my system RAM that result with only 448 MB of RAM (512-64) for Windows. For a video resolution of 1024 x 768 32 bit it's a ridiculous amount of memory since it only really requires 4 MB for this. I'm not interested in games or 3d graphics, so my question is if I can change the memory allocated to recover more memory system?

  see you soon,

  Richard S.

  HI Richard,

  ATi drivers include an improved graphics option devices-> display manager that allows the value of the AMU to change. My SA30 supports load 16 MB, 32 MB, 64 MB and 128 MB.

  The same value UMA adjustable in BIOS Setup Panel.

  HTH

• Get the DLL string (memory allocated for DLL)

  Hi, I'm aware there are a lot of discussions around this topic, but there are a lot of variations and I've never used before LabVIEW, and I seem to have a hard time at a very basic level, so I hope someone can help me with the below simple specific test case to put me on the right track before I pull my hair remaining.

  I've created a DLL with a single function "GenerateGreeting". When it is called, it allocates enough memory for the string "Hello World!" \0"at the pGreeting of pointer, copy this string to the pointer and sets the GreetingLength parameter to the number of allocated bytes (in the DLL in the end, I want to use, there is a DLL function to free the memory allocated for this way).

  I created a header file to go with the DLL containing the following line.

  extern __declspec(dllimport) int __stdcall GenerateGreeting(char* &pGreeting, int &GreetingLength);
  

  I then imported the LabVIEW file using the import Shared Library Wizard. That created a "generate Greeting.vi' and everything seems somewhat sensitive for me (although this does not mean a lot right now). When I run the vi, the ' GreetingLength on ' display correctly '13', the length of the string, but "pGreeting out" shows only three or four characters (which vary in each race), place of the string that is expected of junk.

  The pGreeting parameter is set to the 'String' type, the string "String pointer C" format, size currently Minimum of 4095. I think the problem is that the DLL wants to allocate memory for pGreeting; the caller is supposed to pass a unallocated pointer and let the DLL allocates memory for the string the right amount, but LabVIEW expected the DLL to write in its buffer préallouée. How to with LabVIEW? Most of the functions in the DLL in the end, I want to use work this way, so I hope that's possible. Or I have to rewrite all my DLL functions to use buffers allocated by the appellant?

  The vi , header and the DLL are atteched, tips appreciated. Edit - cannot attach the dll or the headers.

  tony_si wrote:

  extern __declspec(dllimport) int __stdcall GenerateGreeting(char* &pGreeting, int &GreetingLength);
  

  Although char * & pGreeting is actually a thing of C++ (no C compiler I know would accept it) and this basically means that the char pointer is passed as a reference. So, technically, it's a double referenced pointer, however nothing in C++ Specifies that reference parameters should be implemented as a pointer at the hardware level. So free to decide to use some other possible MECHANISM that takes the target CPU architecture support a C compiler constructor. However, for the C++ compilers, I know it's really just syntactic sugar and is implemented internally as a pointer.

  LabVIEW has no type of data that allows to configure this directly. You will have to configure it as a whole size pointer passed as a pointer value and then use a call MoveBlock() or the support VI GetValuePtr() to copy the data on the pointer in a string of LabVIEW.

  AND: You need to know how the DLL allocates the pointer so that you can deallocate it correctly after each call to this function. Otherwise you probably create a leak memory, since you say that the first 4 bytes in the returned buffer always change, this feature seems to assign to each run of a new buffer that you want to deallocate correctly. Unless the DLL uses a Windows such as HeapAlloc() API function for this, it should also export a function according to deallocate the buffer. Functions like malloc() and free() from the C runtime cannot always be applied in the same version between the caller and callee, so that calling free() by calling on a buffer that has been allocated with malloc() in the DLL may not work on the same segment of memory and result in undefined behavior.

• Change THE Memory Allocation 6.0.

  I own a 7 '' netbook Sylvania, with 128 MB of RAM and Windows CE 6.0 OS. There the cursor to change the memory allocation between the PROGRAM and the STORAGE, but it won't budge. To get YouTube running on this thing, I need to go 68 MB of RAM allocated to executing programs for about 130 MB, taking storage (use an SD card to make up the difference - easy). Is there a way to unlock the slide or modify the default setting through the registry hive files? I have already made some adjustments with explore in this way and have managed to add a file to it. I understand in hex. Thank you!

  Hello GusCD6,

  The best place to ask your question on Windows CE 6.0 is in the MSDN forums for the development of Windows Mobile. Click here for a link to the Windows Mobile Development Forum.
  They are there, the experts and would be better able to solve your problem of Windows CE and help answer your questions.

  Sincerely,

  Marilyn

• memory card error

  My HP photosmart D110a continues to display a message on the display panel "memory card error".  During this time the display panel cannot be used.  On my computer the HP Solution Center window keeps poping up (annoying) with the message "error on the map".  Printing is also most of the time impossible.  Can you advise?

  I reinstalled the software from the computer and the problem was solved.

• OfficeJet pro 8600: officejet pro 8600 memory card error - any inserted memory card

  I am connected directly to my Lenovo Thinkpad laptop and I can print, but I can't copy, scan or fax. The touchpad display memory card error. It is plugged into a wall outlet and I did a hard reboot.  Not sure if my Windows 7 is 32-bit or 64-bit.

  I don't see any private messages.

• Analog output PCI-6251-DAQ-200016 memory overflow error

  NI PCI - 6251 DAQmx, AIMD-752 motherboard, dual core processor, a lot of speed and the ram running WinXP Pro & LabWindows/CVI

  get DAQ-200016 memory overflow error when I try to generate a signal of analog output with a rate higher than about 32 000 samples/second (?)

  going on what?  I have never seen it before.   Is this a problem with the motherboard?    "It's the same product on the CVI code example" \Cont Gen Volt Wfm - Int Clk\ContGen - IntClk.cws.

  If someone has had this problem, and is there a solution?

  Thank you

  PS: full text of the message reads:

  Measurements: On-board memory precision passing. Due to the limitations of system and/or the bandwidth of the bus, the driver could not write data to the device fast enough to track the rate of output of the device.  Reduce your sampling rate, change the method of transfer of data (from interruptions on DMA), use a product with more on-board memory or reduce the number of programs that your computer runs simultaneously. Task name: _unnamedTask<1> Code of State:-200016

  Well, I found my answer.   For later use, Olivia NI Apps Engineering suggested I have change the mechanism of data transfer by this Knowledge Base document:

  http://digital.NI.com/public.nsf/WebSearch/C326F7D33CA6DB0E86256DFE008043B7?OpenDocument

  ... so I inserted the line of code between the creation of the area of OCCUPANCY of the channels and set up the example of clock calendar.

  DAQmxCreateAOVoltageChan( ...
  
  DAQmxSetAODataXferMech(TaskHandle,chan,DAQmx_Val_Interrupts);
  
  DAQmxCfgSampClkTiming(...
  

  now, I am able to generate output to a 2.35 MS/sec... max sampling frequency not quite the 2.86MS / sec indicated in the specification 6251, but close enough that I'll stop complaining