LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

When building my application the system W98 crashing

I have an application with subvi dinamically linked, My O.S. is W98 and the Labview 6.1 with the Application builder 6.1.The latest version of MAX(3).The target is P3 666Mhz 32MB ram. When i compile the application in this target machine i have a crash of system (only reeboot for resolve it).I have try in my portable with W2000 P4 2,4Ghz 512MB ram, and the application is builded correctly no error and the run is OK.
Thanks Nicola
Bytelabs.it
0 Kudos
Message 1 of 7
(3,151 Views)
It could be related to the memory RAM in the windows 98 system. 32 MB ram is the minimal you can use for windows 98.
At one time, I had labView executables crashing on win98 systems, or go to long wait states (virtual memory being used/swapped), because 32 MB was not adequate. Increasing the memory then solved the problem. My applications on win98 used version 5.1.1 and 6.02
0 Kudos
Message 2 of 7
(3,151 Views)
Hi,Dr.
I think it's one of the problem,but the previous version of the application don't present the problem in the same target machine.Incredible for me is The application builder crash in the building of application.For me is normal for "little memory size" the crash when the application is run,but not when is in building.
I wait your comments,
Thank's Nicola
Bytelabs.it
0 Kudos
Message 3 of 7
(3,151 Views)
Nicola,

How much smaller is the previous version than the current version? You may have just passed a threshold for your application. Memory is cheap. I suggest buying an additional stick and trying it again.

Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask
0 Kudos
Message 4 of 7
(3,151 Views)
Hi Randy,
The previous version is not too small of new version.I buy another bank memory and trying but now i have also a message error in the step of loading VI in application builder.
The message is :

LABVIEW ha provocato un errore di pagina non valida nel
modulo KERNEL32.DLL in 017f:bff7d76b.
Registri:
EAX=fed9f000 CS=017f EIP=bff7d76b EFLGS=00010207
EBX=81672784 SS=0187 ESP=00dcee20 EBP=00dcee44
ECX=fecc3c50 DS=0187 ESI=0000dbaf FS=4507
EDX=bffc9490 ES=0187 EDI=fed31280 GS=45a6
Byte all'indirizzo CS:EIP:
83 38 00 74 28 83 c0 08 46 3b f1 72 f3 be ff ff
Immagine dello stack:
00dcee44 00000000 00000000 ce114ff0 bff92e7f 81672784 bff7db0e 81672784 00000000 001f0003 bff8521c 81672784 ce114ff0 001f0003 00dcee84 00000000

Whe
n the process of loading is in act i have very full of memory an i'm with you for the memory small.
If you have advise for the message error thank's for answer.

Kind Regards
Nicola
Bytelabs.it
0 Kudos
Message 5 of 7
(3,151 Views)
ADDITIONAL DETAIL FOR THE PREVIOUS MESSAGE
I have a detail of memory usage of the application builded.
It's 421,3KB(main or call VI) and i have dinamically linked 16 VI of 456KB everyone(called VI).
The reentrant VI have a signifiant for this problem?More of the subVI is in REENTRANT EXECUTION.
I have cheked for reduce the array increase.

Best Regards
Nicola
Bytelabs.it
0 Kudos
Message 6 of 7
(3,151 Views)
Are these the VI sizes in memory or on disk? If it is just on disk, then the memory size will probably be higher than that. Plus, it you hav reentrant VIs and you are calling them multiple times, then you need to multiply the memory size that many times and add it to the main application. Also, if you are using the VI Profiler, it does not keep track of reentrant VIs by definition becasue it tracks things by name.

Also, make sure that the new memory is compatible with the old because it may not be (speaking from experience).

Randy Hoskin
Applications Engineer
Nationsl Instruments
http://www.ni.com/ask
0 Kudos
Message 7 of 7
(3,151 Views)