Plantage CS4 à l'ouverture ou la création d'un fichier fla AS3

Bonjour à tous,
Je rencontre un gros problème : lors de la création d'un nouveau fichier Flash en AS3, Flash CS4 plante.
(cf le rapport de crash en fin de post)
Pareil lorsque j'ouvre un fichier .fla existant en AS3.
Par contre, je peux bien créer un fichier fla en AS2, ca fonctionne.
J'ai fait une réinstallation de Flash (pas de toute la suite), installé la dernière mise à jour, mais rien y fait, ca plante toujours.
Un fichier fla corrompu pourrait-il corrompre toute l'installation de Flash ??
Merci de votre aide.

Je rencontre le même problème depuis hier,
J'ai essayé de réinitialiser les préférences comme indiqué par adobe, de réinstaller complètement l'application, de revenir à une version antérieure de mon pilote d'affichage, rien n'y fait.
Voici le rapport de crash:
<?xml version="1.0"?>
<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">
<crashreport version="1.1" crVersion="2.5.0.01052007" applicationName="Adobe Flash CS4" applicationVersion="10.0.2" build="10.0.2.566">
<time year="2011" month="5" day="15" hour="13" minute="8" second="50"/>
<user guid="30ec6d78-2dd9-48ab-be1a-78752c870b69"/>
<system platform="windows" osversion="6.1.7601 SP 1.0" applicationlanguage="Anglais (Ã‰tats-Unis)" userlanguage="fr_FR" oslanguage="fr_FR" ram="4085" machine="Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz" model="Intel64 Family 6 Model 30 Stepping 5" cpuCount="8" cpuFreq="1600 MHz" busFreq=""/>
<crash exception="EXCEPTION_ACCESS_VIOLATION" instruction="0x6ff6b8c7">
<backtrace crashedThread="0">
<thread index="0">
<stackStatement index="0" address="0x6ff6b8c7" symbolname="DllUnregisterServer"/>
<stackStatement index="1" address="0x00b73fe8" symbolname="unknown"/>
<stackStatement index="2" address="0x700457d5" symbolname="DllUnregisterServer"/>
<stackStatement index="3" address="0x6fff35b3" symbolname="DllUnregisterServer"/>
<stackStatement index="4" address="0x7000a228" symbolname="DllUnregisterServer"/>
<stackStatement index="5" address="0x7000b3b2" symbolname="DllUnregisterServer"/>
<stackStatement index="6" address="0x700183e0" symbolname="DllUnregisterServer"/>
<stackStatement index="7" address="0x70018482" symbolname="DllUnregisterServer"/>
<stackStatement index="8" address="0x6ffe621d" symbolname="DllUnregisterServer"/>
<stackStatement index="9" address="0x7000c592" symbolname="DllUnregisterServer"/>
<stackStatement index="10" address="0x7003f49b" symbolname="DllUnregisterServer"/>
<stackStatement index="11" address="0x7003d900" symbolname="DllUnregisterServer"/>
<stackStatement index="12" address="0x70001b1d" symbolname="DllUnregisterServer"/>
<stackStatement index="13" address="0x70001ba3" symbolname="DllUnregisterServer"/>
<stackStatement index="14" address="0x70001bcc" symbolname="DllUnregisterServer"/>
<stackStatement index="15" address="0x70001d2b" symbolname="DllUnregisterServer"/>
<stackStatement index="16" address="0x76236f9e" symbolname="GetThreadDesktop"/>
<stackStatement index="17" address="0x74194c39" symbolname="free"/>
<stackStatement index="18" address="0x6ffeab7c" symbolname="DllUnregisterServer"/>
<stackStatement index="19" address="0x6ffeab5f" symbolname="DllUnregisterServer"/>
<stackStatement index="20" address="0x70042bc4" symbolname="DllUnregisterServer"/>
</thread>
</backtrace>
<registerSet>
<register name="EAX" value="0x6c66e6ee"/>
<register name="EBX" value="0x6c66deb0"/>
<register name="ECX" value="0x0018f340"/>
<register name="EDX" value="0x00000000"/>
<register name="ESI" value="0x03b17748"/>
<register name="EDI" value="0x000000f9"/>
<register name="ESP" value="0x0018f780"/>
<register name="EBP" value="0x00000000"/>
<register name="EIP" value="0x70042bc4"/>
<register name="EFL" value="0x00210297"/>
</registerSet>
<binaryImageSet>
<binaryImage start="0x00400000" end="0x01894000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\Flash.exe"/>
<binaryImage start="0x77e40000" end="0x77fc0000" type="__TEXT" path="C:\Windows\SysWOW64\ntdll.dll"/>
<binaryImage start="0x76490000" end="0x765a0000" type="__TEXT" path="C:\Windows\SysWOW64\kernel32.dll"/>
<binaryImage start="0x760d0000" end="0x76116000" type="__TEXT" path="C:\Windows\SysWOW64\KERNELBASE.dll"/>
<binaryImage start="0x64d00000" end="0x64d34000" type="__TEXT" path="C:\Program Files\Alwil Software\Avast5\snxhk.dll"/>
<binaryImage start="0x10000000" end="0x10309000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\amtlib.dll"/>
<binaryImage start="0x761c0000" end="0x76217000" type="__TEXT" path="C:\Windows\SysWOW64\shlwapi.dll"/>
<binaryImage start="0x765a0000" end="0x76630000" type="__TEXT" path="C:\Windows\SysWOW64\gdi32.dll"/>
<binaryImage start="0x76220000" end="0x76320000" type="__TEXT" path="C:\Windows\SysWOW64\user32.dll"/>
<binaryImage start="0x76630000" end="0x766d0000" type="__TEXT" path="C:\Windows\SysWOW64\advapi32.dll"/>
<binaryImage start="0x75d60000" end="0x75e0c000" type="__TEXT" path="C:\Windows\SysWOW64\msvcrt.dll"/>
<binaryImage start="0x76190000" end="0x761a9000" type="__TEXT" path="C:\Windows\SysWOW64\sechost.dll"/>
<binaryImage start="0x75b10000" end="0x75c00000" type="__TEXT" path="C:\Windows\SysWOW64\rpcrt4.dll"/>
<binaryImage start="0x759a0000" end="0x75a00000" type="__TEXT" path="C:\Windows\SysWOW64\sspicli.dll"/>
<binaryImage start="0x75990000" end="0x7599c000" type="__TEXT" path="C:\Windows\SysWOW64\CRYPTBASE.dll"/>
<binaryImage start="0x77e10000" end="0x77e1a000" type="__TEXT" path="C:\Windows\SysWOW64\lpk.dll"/>
<binaryImage start="0x77570000" end="0x7760d000" type="__TEXT" path="C:\Windows\SysWOW64\usp10.dll"/>
<binaryImage start="0x73e60000" end="0x73e71000" type="__TEXT" path="C:\Windows\System32\netapi32.dll"/>
<binaryImage start="0x73e50000" end="0x73e59000" type="__TEXT" path="C:\Windows\System32\netutils.dll"/>
<binaryImage start="0x73e30000" end="0x73e49000" type="__TEXT" path="C:\Windows\System32\srvcli.dll"/>
<binaryImage start="0x75510000" end="0x7551f000" type="__TEXT" path="C:\Windows\System32\wkscli.dll"/>
<binaryImage start="0x76700000" end="0x76735000" type="__TEXT" path="C:\Windows\SysWOW64\ws2_32.dll"/>
<binaryImage start="0x77890000" end="0x77896000" type="__TEXT" path="C:\Windows\SysWOW64\nsi.dll"/>
<binaryImage start="0x73a60000" end="0x73bfe000" type="__TEXT" path="C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1d f_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.dll"/>
<binaryImage start="0x73980000" end="0x739d8000" type="__TEXT" path="C:\Windows\System32\winhttp.dll"/>
<binaryImage start="0x73930000" end="0x7397f000" type="__TEXT" path="C:\Windows\System32\webio.dll"/>
<binaryImage start="0x77610000" end="0x7768b000" type="__TEXT" path="C:\Windows\SysWOW64\comdlg32.dll"/>
<binaryImage start="0x76800000" end="0x7744a000" type="__TEXT" path="C:\Windows\SysWOW64\shell32.dll"/>
<binaryImage start="0x75660000" end="0x75669000" type="__TEXT" path="C:\Windows\System32\version.dll"/>
<binaryImage start="0x73440000" end="0x73472000" type="__TEXT" path="C:\Windows\System32\winmm.dll"/>
<binaryImage start="0x74650000" end="0x74669000" type="__TEXT" path="C:\Windows\System32\avifil32.dll"/>
<binaryImage start="0x75f70000" end="0x760cc000" type="__TEXT" path="C:\Windows\SysWOW64\ole32.dll"/>
<binaryImage start="0x74630000" end="0x74644000" type="__TEXT" path="C:\Windows\System32\msacm32.dll"/>
<binaryImage start="0x74070000" end="0x74091000" type="__TEXT" path="C:\Windows\System32\msvfw32.dll"/>
<binaryImage start="0x75c50000" end="0x75c55000" type="__TEXT" path="C:\Windows\SysWOW64\psapi.dll"/>
<binaryImage start="0x75ab0000" end="0x75b10000" type="__TEXT" path="C:\Windows\SysWOW64\imm32.dll"/>
<binaryImage start="0x75ea0000" end="0x75f6c000" type="__TEXT" path="C:\Windows\SysWOW64\msctf.dll"/>
<binaryImage start="0x12000000" end="0x121cb000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\xerces-c_2_6.dll"/>
<binaryImage start="0x74190000" end="0x7422b000" type="__TEXT" path="C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.559 2_none_d09196c24426e2d4\msvcr80.dll"/>
<binaryImage start="0x32100000" end="0x321b4000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\Workspace.dll"/>
<binaryImage start="0x747c0000" end="0x74950000" type="__TEXT" path="C:\Windows\winsxs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.76 01.17514_none_72d18a4386696c80\GdiPlus.dll"/>
<binaryImage start="0x01ac0000" end="0x01bfe000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\dvacore.dll"/>
<binaryImage start="0x76740000" end="0x767cf000" type="__TEXT" path="C:\Windows\SysWOW64\oleaut32.dll"/>
<binaryImage start="0x73fe0000" end="0x74067000" type="__TEXT" path="C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.559 2_none_d09196c24426e2d4\msvcp80.dll"/>
<binaryImage start="0x01c00000" end="0x01e34000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\dvaui.dll"/>
<binaryImage start="0x01e40000" end="0x01f7c000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\AdobeOwl.dll"/>
<binaryImage start="0x71fa0000" end="0x720af000" type="__TEXT" path="C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.559 2_none_cbf62b764709d1c9\mfc80u.dll"/>
<binaryImage start="0x74ad0000" end="0x74ad5000" type="__TEXT" path="C:\Windows\System32\msimg32.dll"/>
<binaryImage start="0x00290000" end="0x002a3000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\AlcidDLL.dll"/>
<binaryImage start="0x002c0000" end="0x002ce000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\ahclient.dll"/>
<binaryImage start="0x002e0000" end="0x002ed000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\CrashReporter.dll"/>
<binaryImage start="0x75570000" end="0x7565b000" type="__TEXT" path="C:\Windows\System32\dbghelp.dll"/>
<binaryImage start="0x00380000" end="0x0038f000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\LogUtils.dll"/>
<binaryImage start="0x003a0000" end="0x003b8000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\LogTransport.dll"/>
<binaryImage start="0x003d0000" end="0x003ea000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\LogSession.dll"/>
<binaryImage start="0x018a0000" end="0x018b6000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\LogTransport2.dll"/>
<binaryImage start="0x778a0000" end="0x77a3d000" type="__TEXT" path="C:\Windows\SysWOW64\setupapi.dll"/>
<binaryImage start="0x76460000" end="0x76487000" type="__TEXT" path="C:\Windows\SysWOW64\cfgmgr32.dll"/>
<binaryImage start="0x75a00000" end="0x75a12000" type="__TEXT" path="C:\Windows\SysWOW64\devobj.dll"/>
<binaryImage start="0x75c60000" end="0x75d55000" type="__TEXT" path="C:\Windows\SysWOW64\wininet.dll"/>
<binaryImage start="0x76320000" end="0x76456000" type="__TEXT" path="C:\Windows\SysWOW64\urlmon.dll"/>
<binaryImage start="0x77450000" end="0x7756d000" type="__TEXT" path="C:\Windows\SysWOW64\crypt32.dll"/>
<binaryImage start="0x761b0000" end="0x761bc000" type="__TEXT" path="C:\Windows\SysWOW64\msasn1.dll"/>
<binaryImage start="0x77690000" end="0x7788b000" type="__TEXT" path="C:\Windows\SysWOW64\iertutil.dll"/>
<binaryImage start="0x03f90000" end="0x0402d000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\amtservices.dll"/>
<binaryImage start="0x04030000" end="0x04067000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\adobe_caps.dll"/>
<binaryImage start="0x733c0000" end="0x73440000" type="__TEXT" path="C:\Windows\System32\uxtheme.dll"/>
<binaryImage start="0x73a30000" end="0x73a51000" type="__TEXT" path="C:\Windows\System32\ntmarta.dll"/>
<binaryImage start="0x75c00000" end="0x75c45000" type="__TEXT" path="C:\Windows\SysWOW64\Wldap32.dll"/>
<binaryImage start="0x040c0000" end="0x040e0000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\asneu.dll"/>
<binaryImage start="0x04f60000" end="0x061e5000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\fr\Configuration\FlashResources.dll"/>
<binaryImage start="0x73890000" end="0x738e1000" type="__TEXT" path="C:\Windows\System32\winspool.drv"/>
<binaryImage start="0x73850000" end="0x7388c000" type="__TEXT" path="C:\Windows\System32\oleacc.dll"/>
<binaryImage start="0x733a0000" end="0x733b3000" type="__TEXT" path="C:\Windows\System32\dwmapi.dll"/>
<binaryImage start="0x75890000" end="0x7589b000" type="__TEXT" path="C:\Windows\System32\profapi.dll"/>
<binaryImage start="0x75a20000" end="0x75aa3000" type="__TEXT" path="C:\Windows\SysWOW64\clbcatq.dll"/>
<binaryImage start="0x73f30000" end="0x73f5e000" type="__TEXT" path="C:\Windows\System32\mlang.dll"/>
<binaryImage start="0x73360000" end="0x73399000" type="__TEXT" path="C:\Windows\System32\MMDevAPI.dll"/>
<binaryImage start="0x73220000" end="0x73315000" type="__TEXT" path="C:\Windows\System32\propsys.dll"/>
<binaryImage start="0x734f0000" end="0x73520000" type="__TEXT" path="C:\Windows\System32\wdmaud.drv"/>
<binaryImage start="0x74620000" end="0x74624000" type="__TEXT" path="C:\Windows\System32\ksuser.dll"/>
<binaryImage start="0x74600000" end="0x74607000" type="__TEXT" path="C:\Windows\System32\avrt.dll"/>
<binaryImage start="0x73670000" end="0x736a6000" type="__TEXT" path="C:\Windows\System32\AudioSes.dll"/>
<binaryImage start="0x745e0000" end="0x745e8000" type="__TEXT" path="C:\Windows\System32\msacm32.drv"/>
<binaryImage start="0x745d0000" end="0x745d7000" type="__TEXT" path="C:\Windows\System32\midimap.dll"/>
<binaryImage start="0x74480000" end="0x74488000" type="__TEXT" path="C:\Windows\System32\credssp.dll"/>
<binaryImage start="0x734b0000" end="0x734ea000" type="__TEXT" path="C:\Windows\SysWOW64\schannel.dll"/>
<binaryImage start="0x72200000" end="0x72256000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\PlugPlug.dll"/>
<binaryImage start="0x721b0000" end="0x721fa000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\BIB.dll"/>
<binaryImage start="0x71960000" end="0x71a0a000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\AXEDOMCore.dll"/>
<binaryImage start="0x08d90000" end="0x08dd4000" type="__TEXT" path="C:\Program Files (x86)\Common Files\Adobe\CS4ServiceManager\CSI-Launcher.dll"/>
<binaryImage start="0x752a0000" end="0x752ec000" type="__TEXT" path="C:\Windows\System32\apphelp.dll"/>
<binaryImage start="0x73330000" end="0x7335e000" type="__TEXT" path="C:\Windows\System32\shdocvw.dll"/>
<binaryImage start="0x718f0000" end="0x71960000" type="__TEXT" path="C:\Windows\System32\ntshrui.dll"/>
<binaryImage start="0x75500000" end="0x7550b000" type="__TEXT" path="C:\Windows\System32\cscapi.dll"/>
<binaryImage start="0x742f0000" end="0x742fa000" type="__TEXT" path="C:\Windows\System32\slc.dll"/>
<binaryImage start="0x73e10000" end="0x73e26000" type="__TEXT" path="C:\Windows\System32\cryptsp.dll"/>
<binaryImage start="0x73dd0000" end="0x73e0b000" type="__TEXT" path="C:\Windows\System32\rsaenh.dll"/>
<binaryImage start="0x75550000" end="0x7555e000" type="__TEXT" path="C:\Windows\System32\RpcRtRemote.dll"/>
<binaryImage start="0x718a0000" end="0x718e1000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\BIBUtils.dll"/>
<binaryImage start="0x09750000" end="0x09841000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\ACE.dll"/>
<binaryImage start="0x712c0000" end="0x71893000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\AGM.dll"/>
<binaryImage start="0x71260000" end="0x712b2000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\ARE.dll"/>
<binaryImage start="0x0a4a0000" end="0x0a8d6000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\MPS.dll"/>
<binaryImage start="0x70fb0000" end="0x7125e000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\CoolType.dll"/>
<binaryImage start="0x70ec0000" end="0x70fa3000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\FileInfo.dll"/>
<binaryImage start="0x70e50000" end="0x70ebd000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\AdobeXMP.dll"/>
<binaryImage start="0x70dd0000" end="0x70e46000" type="__TEXT" path="C:\Windows\System32\riched20.dll"/>
<binaryImage start="0x70cc0000" end="0x70dca000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\pdfport.dll"/>
<binaryImage start="0x706f0000" end="0x70cb7000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\AdobePDFL.dll"/>
<binaryImage start="0x70640000" end="0x706e7000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\JP2KLib.dll"/>
<binaryImage start="0x73490000" end="0x734a2000" type="__TEXT" path="C:\Windows\System32\mpr.dll"/>
<binaryImage start="0x70610000" end="0x7063e000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\AXE8SharedExpat.dll"/>
<binaryImage start="0x742e0000" end="0x742ec000" type="__TEXT" path="C:\Windows\System32\atmlib.dll"/>
<binaryImage start="0x70510000" end="0x7060b000" type="__TEXT" path="C:\Windows\System32\WindowsCodecs.dll"/>
<binaryImage start="0x70490000" end="0x704c1000" type="__TEXT" path="C:\Windows\System32\EhStorShell.dll"/>
<binaryImage start="0x0b020000" end="0x0b06f000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\Common\Configuration\External Libraries\EnvBrush.dll"/>
<binaryImage start="0x0b070000" end="0x0b0d4000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\Common\Configuration\External Libraries\EnvCollision.dll"/>
<binaryImage start="0x0ad30000" end="0x0ad47000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\Common\Configuration\External Libraries\EnvPointGrid.dll"/>
<binaryImage start="0x0b2a0000" end="0x0b358000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\Common\Configuration\External Libraries\FlashIK.dll"/>
<binaryImage start="0x0b110000" end="0x0b15b000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\Common\Configuration\External Libraries\FLBridge.dll"/>
<binaryImage start="0x0add0000" end="0x0ade7000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\Common\Configuration\External Libraries\FLfile.dll"/>
<binaryImage start="0x0b480000" end="0x0b4ca000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\fr\Configuration\External Libraries\FLAir1_1.dll"/>
<binaryImage start="0x0b530000" end="0x0b57c000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\fr\Configuration\External Libraries\FLAir1_5.dll"/>
<binaryImage start="0x70350000" end="0x70483000" type="__TEXT" path="C:\Windows\System32\msxml3.dll"/>
<binaryImage start="0x6d6c0000" end="0x6d85b000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\JVM\bin\client\jvm.dll"/>
<binaryImage start="0x6d280000" end="0x6d288000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\JVM\bin\hpi.dll"/>
<binaryImage start="0x6d690000" end="0x6d69c000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\JVM\bin\verify.dll"/>
<binaryImage start="0x6d300000" end="0x6d31d000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\JVM\bin\java.dll"/>
<binaryImage start="0x6d6b0000" end="0x6d6bf000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\JVM\bin\zip.dll"/>
<binaryImage start="0x6fdc0000" end="0x7034a000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\Common\Configuration\authplay.dll"/>
<binaryImage start="0x71f20000" end="0x71f99000" type="__TEXT" path="C:\Windows\System32\mscms.dll"/>
<binaryImage start="0x758a0000" end="0x758b7000" type="__TEXT" path="C:\Windows\System32\userenv.dll"/>
<binaryImage start="0x73c00000" end="0x73c08000" type="__TEXT" path="C:\Windows\System32\secur32.dll"/>
<binaryImage start="0x212f0000" end="0x21573000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\AdobeLM_libFNP.dll"/>
<binaryImage start="0x73d10000" end="0x73d2c000" type="__TEXT" path="C:\Windows\System32\IPHLPAPI.DLL"/>
<binaryImage start="0x73d00000" end="0x73d07000" type="__TEXT" path="C:\Windows\System32\winnsi.dll"/>
<binaryImage start="0x73fd0000" end="0x73fd9000" type="__TEXT" path="C:\Windows\System32\snmpapi.dll"/>
<binaryImage start="0x73cb0000" end="0x73cf4000" type="__TEXT" path="C:\Windows\System32\dnsapi.dll"/>
<binaryImage start="0x73f70000" end="0x73fc2000" type="__TEXT" path="C:\Windows\System32\rasapi32.dll"/>
<binaryImage start="0x71f00000" end="0x71f15000" type="__TEXT" path="C:\Windows\System32\rasman.dll"/>
<binaryImage start="0x73f60000" end="0x73f6d000" type="__TEXT" path="C:\Windows\System32\rtutils.dll"/>
<binaryImage start="0x73480000" end="0x73486000" type="__TEXT" path="C:\Windows\System32\SensApi.dll"/>
<binaryImage start="0x73d70000" end="0x73d80000" type="__TEXT" path="C:\Windows\System32\nlaapi.dll"/>
<binaryImage start="0x73c20000" end="0x73c26000" type="__TEXT" path="C:\Windows\System32\rasadhlp.dll"/>
<binaryImage start="0x73d60000" end="0x73d70000" type="__TEXT" path="C:\Windows\System32\NapiNSP.dll"/>
<binaryImage start="0x73d40000" end="0x73d52000" type="__TEXT" path="C:\Windows\System32\pnrpnsp.dll"/>
<binaryImage start="0x73d30000" end="0x73d3d000" type="__TEXT" path="C:\Windows\System32\wshbth.dll"/>
<binaryImage start="0x06460000" end="0x06479000" type="__TEXT" path="C:\Program Files (x86)\Bonjour\mdnsNSP.dll"/>
<binaryImage start="0x73d90000" end="0x73dcc000" type="__TEXT" path="C:\Windows\System32\mswsock.dll"/>
<binaryImage start="0x73ca0000" end="0x73ca8000" type="__TEXT" path="C:\Windows\System32\winrnr.dll"/>
<binaryImage start="0x73c70000" end="0x73c97000" type="__TEXT" path="C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL"/>
<binaryImage start="0x73d80000" end="0x73d85000" type="__TEXT" path="C:\Windows\System32\WSHTCPIP.DLL"/>
<binaryImage start="0x73a20000" end="0x73a26000" type="__TEXT" path="C:\Windows\System32\wship6.dll"/>
<binaryImage start="0x73c30000" end="0x73c68000" type="__TEXT" path="C:\Windows\System32\FWPUCLNT.DLL"/>
<binaryImage start="0x71ea0000" end="0x71efa000" type="__TEXT" path="C:\Windows\System32\netprofm.dll"/>
<binaryImage start="0x73320000" end="0x73328000" type="__TEXT" path="C:\Windows\System32\npmproxy.dll"/>
<binaryImage start="0x739f0000" end="0x73a02000" type="__TEXT" path="C:\Windows\System32\dhcpcsvc.dll"/>
<binaryImage start="0x73a10000" end="0x73a1d000" type="__TEXT" path="C:\Windows\System32\dhcpcsvc6.DLL"/>
<binaryImage start="0x745f0000" end="0x745fa000" type="__TEXT" path="C:\Windows\System32\wbem\wbemprox.dll"/>
<binaryImage start="0x72150000" end="0x721ac000" type="__TEXT" path="C:\Windows\System32\wbemcomn.dll"/>
<binaryImage start="0x766d0000" end="0x766fd000" type="__TEXT" path="C:\Windows\SysWOW64\wintrust.dll"/>
<binaryImage start="0x74610000" end="0x7461f000" type="__TEXT" path="C:\Windows\System32\wbem\wbemsvc.dll"/>
<binaryImage start="0x720b0000" end="0x72146000" type="__TEXT" path="C:\Windows\System32\wbem\fastprox.dll"/>
<binaryImage start="0x74300000" end="0x74318000" type="__TEXT" path="C:\Windows\System32\ntdsapi.dll"/>
<binaryImage start="0x71e90000" end="0x71e93000" type="__TEXT" path="C:\Windows\System32\icmp.dll"/>
<binaryImage start="0x21990000" end="0x21a2b000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\registration.dll"/>
<binaryImage start="0x71e70000" end="0x71e8c000" type="__TEXT" path="C:\Windows\System32\oledlg.dll"/>
<binaryImage start="0x71de0000" end="0x71e63000" type="__TEXT" path="C:\Program Files (x86)\Adobe\Adobe Flash CS4\AdobeUpdater.dll"/>
<binaryImage start="0x749e0000" end="0x74a05000" type="__TEXT" path="C:\Windows\System32\powrprof.dll"/>
</binaryImageSet>
</crash>
<reproSteps>
</reproSteps>
</crashreport>
Le seule manipulation que j'ai effectué avant hier est d'installer le flash player debugger et d'avoir testé flashFirebug sur firefox.
J'ai bien entendu tenté de desinstaller le player flash pour firefox ainsi que les modules flashfirebug, sans succès.

Similar Messages

Recuperer la date de création d'un fichier texte.

Bonjour,
j'aimerai savoir comment je peux récupérer sous LV9 la date de création d'un fichier texte.
Merci
Sebastien DEVISSCHER - Nerys
Résolu !
Accéder à la solution.

Bonjour,
Dans les fonctions entrée sortie sur fichiers puis fonctions de fichiers avancés en bas à droite puis fonctions 'Info sur le fichier/ répertoire' vous pouvez récupérer la date de la dernière modification du fichiers.
Sinon il existe aussi une fonction dans la bibliothèque OpenG en utilisant le JKI software VPIM http://jki.net/ vous l'obtiendrez facilement.
Cordialement.
Greg S.
CNRS
LV 7.1 8.2 8.6 2009 2011 2012 2013
LPMC - CNRS
N'oubliez pas de complimenter cela fait toujours plaisir.

Flash CS4 Trial not producing SWF with ActionScript

After installing Flash CS4 (the trial), it has appeared that
when compiling saved FLAs no longer produce SWFs with AS3 code.
AS1/2 works fine, and compiling a Untitled-1 document works fine,
it is just saved AS3 FLAs. Even FLAs saved with Flash CS3 that work
in that product no longer work in Flash CS4.

if you really started the installation and it installed halfway through or similar, run the cleanup script which can be found here: http://kb2.adobe.com/cps/406/kb406241.html and reinstall CS4 again, this time download it with a different browser if possible.

Extension lors d'une création de fichier

Bonjour à tous,
Je souhaiterais faire l'ajout automatique d'une extension lors d'une création d'un fichier par l'ajout d'une constante de caractère comme par exemple ".txt". J'ai essayé sous labview 2010 mais sans succès. Si quelqu'un a une piste ...
Merci d'avance
D. Charalampous
Dcharala, Ingénieur en instrumentation, pratiquant de LabVIEW 2010 sur Windows XP.

Je souhaiterais faire l'ajout automatique d'une extension lors d'une création d'un fichier par l'ajout d'une constante de caractère comme par exemple ".txt".
Ajout d'une constante .txt
Luc Desruelle | Voir mon profil | LabVIEW Code & blog
Co-auteur livre LabVIEW : Programmation et applications
CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW

How to Import *.FLA to Premiere Pro CS4?

is it posible to Import *.FLA to Premiere Pro CS4?
if it's able to, so How? ..please
thanx

I haven't tried it, but I'd be surprised if PR would import an .fla (the flash project file). It is not listed in the fiile formats:
CS5: http://help.adobe.com/en_US/premierepro/cs/using/WSd79b3ca3b623cac97fa024001235833a568-800 0.html
CS4: http://help.adobe.com/en_US/PremierePro/4.0/WSf52ca809ac8f6c7135876f961243120b72d-8000.htm l
SWFs are listed as okay for import in at least CS4 and CS5. But if you've got the fla, you can probably export a swf.

Why doesnt Adobe just UPDATE Flash Professional? Arent they reinventing the wheel?

Congratulations on getting to open beta with Flash Catalyst!
I know its late in the game to mention something like this but why didnt Abobe just update Flash Professional?
It seems that the arguments for flash Catalyst center around the following:
1) smooth workflow between Photoshop & Illustrator, especially because of the same layer view
2) No coding required to create components out of artwork
3) Can create FXG and FXPs to be used in Flash Builder
4) Can create multi screen aplications
1) 2) and 3) could all be solved by adding a new types of symbols to Flash Professional's 3 currently available symbols(MovieClip, Button, Graphic)
1) could be solved by adding a new Sprite symbol.
Flash Professional needs to be updated to keep up with and match the structure of AS3 anyway.
Sprites were added in AS3 and now wireframe components are being added to the code structure, why not just at that on the design side as well?
Sprites are essentially MovieClips with out a timeline.
So if you created a new Sprite symbol and opened it up in the timeline, you would only see one frame with folders and layers.
A Sprite symbol is essentially organized the in layers and folders and would just like a photoshop file.
And if you really want it to look like a Photoshop layout, then you just move the timeline view over to the right.
This would solve problem 1. Designers could import their artwork into Flash Professional as a Sprite and it would be a seemless experience.
Obviously I'm not saying that a bitmap is a sprite. But I am saying that layers of bitmaps and could be organized inside of a Sprite. And the designer could turn any of the assets into a Button, MovieClip, Graphic, Sprite, and hopefully other Classes and WireframeComponents available in Flash.
2)&3) could be solved by adding a new Symbols for the new Wireframe Components. The Button symbol already has a template with 4 states. Why not update Flash Professional to visually represent more Classes and Component Classes, instead of just the MovieClip Class and the Button Class. Even better, maybe there could be a way to make a template for creating our own wireframe components. Just assign a base class for the wireframe class and a base template, and the introspection view will display accordingly.
States of the component would be listed out at the top instead of frames, just like the Button Symbol used to be. Different layers could be designated for specific graphical parts of the component. The designer would be free to add their own layers if necessary.
In previous versions of Flash, everything was a movieclip and everthing had a timeline. Thats not the case anymore. The timeline is for intropecting MovieClips, but this view could be different when intropsecting different types of symbols such as Sprites, Buttons, Wireframe Components, and even Custom Wireframe Components(extensible).
These new Symbols and also Sprites could export to FXG very easily.
The multi screen applications in 4) look pretty similar to the Slide Presentation Template. Why not just make a new MultiScreen App Template and youre done. these MultiScreenApp Templates could exporte Screens to FXG or export the whole Template to a FXP.
I applaud the work done on the new wireframe components and FXG. Great Job!
But, just cant understand why you cant update Flash Professional with new types of Symbols(Sprites, new Buttons and wireframe Component Classes) and a new MultiScreen App Template.
Flash Professional needs to keep up with AS3 and also needs to export FXG and FXP.
Why doesnt Adobe focus on on this rather than create a new Tool? These features need to be added to Flash Professional anyway.
Isnt there more of a disadvantage to having 2 tools for designers that do the same thing?
I'm sure this issue has been debated before. Can anyone point to me links that have the arguments for creating a separate tool instead of updating?
Has anyone ever suggested that Flash Professional should keep up with AS3?
Has anyone ever suggested making Sprites a new symbol in Flash Professional so that it could be more seamless with Photoshop?
Has anyone ever suggested make Wireframe components in Flash Professional like the Button Symbol in Flash Professional?
Has anyone ever suggested updating Flash Professional so that it would export FXG and FXP?
What is your opinion on this?
-thomasglyn

@Ross
Thanks for your explanation. I appreciate your feedback.
I'm glad we agree that ideally there should be 2 main tools, one for designers(Flash Professional) and one for programming(Flash Builder).
You had mentioned "But, that assumes this is possible. As it currently stands it is not" and the reason being "Catalyst, and Builder both use a completely different framework from Professional. The component architecture is drastically different, not to mention the entire backend of the software.".
You could also argue that, the reasons to make a separate flex component creation tool like Flash Catalyst assumes that updating Flash Professional CS4 is NOT possible. But is the statement about the framework being entirely different really true?
Well, that depends on what you mean by the term "framework".
Framework can refer to 3 things in this case.
1) the component framework
2) the code framework(AS3)
3) the flex framework (mxml, fxg)
If you are refering to #1 then you're right, because Adobe hasnt updated the flash component framework in Flash Professional from Flex3 Halo components to Flex4 Spark components.
Flash components have gone through many iterations, and the switch from AS2 to AS3 was probably more profound than the new wireless component structure(Spark). And now that we have AS3, isnt the only difficulty creating a intuitive UI in Flash Professional, and adding export features?
If you are refering to #2 then I think you're incorrect, because Flash Professional has been updated to AS3 and Flex4 Spark components use AS3. I would totally agree with you, if CS4 did not go through all of the trouble updating to AS3.
If you are refering to #3 then you're right, because Flash Professional doesnt export mxml, fxg, or fxp, but with a little creativity, it would probably be possible to allow such an export. Adding FXG/FXP export features could be solved by creating a new type of project file. Adobe did this for AS2, AS3, flash lite, etc. Why cant they just make a new AS3/FXG file that only allows you to build fxg/fxp exportable assets.
Why cant Adobe make a Sprite class the default document class for AS3/FXG projects and when some adds a movie clip asset, export movie clips as swfs or swcs?
So to be honest, after opening up Flash Catalyst again and looking at it again, I almost get the feeling that its just a Flash Component creation tool with a Photoshop UI, for the new AS3/Flex 4 components(Spark components) that Adobe just refuses to add to CS4. CS4 uses AS3 and Spark components use AS3. CS4 needs to be a visual design tool for all the classes in AS3(as much as possible).
Perhaps Adobe originally meant to name this product...
ADOBE FLASH COMPONENTS
Or maybe Adobe Flex Components(but thats no longer true, because Flex 4 will be Flash Builder).
In regard to "reinventing the wheel". Flash components have been reinvented several times, and I totally agree with you that this is important to "reinvent" components to keep up with new techiques as2,as3,fxg. You are right, this is a positive thing. However in this case, I am using "reinvent in a negative sense.
So maybe I shouldnt say "reinvent the wheel", but "reinvent the car".
Perhaps Adobe is trying to create a wheel for the upperclass RIA programmer Flex car, and isnt making it compatible common designer/programmer Flash car. And when they finished the wheel, and they decided just to make a Segway for the Designers and Flash people to ride, that uses this new wheel.
You might argue that its more approachable for designers, and designers feel at home because the ui is similar. This is precisely why Adobe should hurry up and finish updating the ui of the Flash Professional IDE so that its ui is more compatable with Photoshop and Illustrator. The fact that Photoshop and Illustrator is the standard for designers are perhaps one of Adobe's greatest advantages. They could make the designers happy if they just make a Sprite inspector view with layers like photoshop in Flash Professional, instead of using the old "everything
is a movieclip" paridgim. Flash Professional has already upgraded to AS3 and in AS3 everything isnt a movieclip. So it would be nice if they could make views for some of the new classes and wireframe components.
This is the age old debate, update or start from scratch. I guess I'm saying that I think the hard work of updating to AS3 has already been done, and its just plain wierd that Adobe decides to build a separte tool for components, when they use the same AS3 code base.
Its just insanely exciting to just think about what could have been if Flash updated and brought on more Designers and at the same time linked in the Flex community. Thats what Flash has always been about! The meeting point between Designers and Programmers.
To go this far and quit just because of components just leaves me blue.
It seems that many projects stop at 80% complete and if the developers just spent the extra 20% on fine tuning things then they would have a very high quality product. In this case the remaining 20% is components, ui, and export. I understand that there are probably many things I dont understand, especially when you through in marketing, and product life cycle.
But I think Adobe could have done it, if they put as much effort into it as they did to make an entirely new product.
Maybe we should make some noise before its too late.
I'm still interested in seeing more links that show the logic behind the initial discussions of this debate when it was first decided.
pls keep me posted.
@nwfa & macsavers
Yes, youre right. it does seem to be their plan. I just hope they are just testing the waters. Perhaps after they do the initial selling of Flash Compenents, then maybe they could offer a free update to CS4.
As I mentioned above, the main reason designers feel at home is because of the UI of Flash Catalyst. UI's can be updated, and I believe Flash Professional can and should update itsui for the reasons I mentioned above.

Stop(); Action doesn't work in AS3?

I'm a designer and usually work in AS2.
But I created a movie in as3 (to use the Bones function), and now my stop actions are not working.
What I usually do for my movies is break the movie down in parts on the Main timeline (Start/Content/End), place stops on each of these frames.
And within the Movieclips that play on these labels I put a call:
stop();
_root.gotoAndPlay("Content") etc...
Anyways any fixes for this in AS3?
I'm using CS4 if that matters.

The stop() command works as well in AS3 as it does in AS1/2. What doesn't work is using AS2 terms like "_root". In general, if a stop() command is not working it is because some other code is failing or otherwise overriding the stop().

Debug from a Remote Location

I installed the update to Flash 8 that allows for remote
debugging, and I had it all set up and working over the past week
or two. But, all of a sudden it's not working for me anymore. I was
able to access it by right clicking my movie from within the
browser and selecting "Debugger", but for some reason the option
isn't available anymore. I've rechecked my settings according to
the livedocs, and ensured the swd file is in the same dir as the
swf, but no dice... Anyone have an idea on how to bring this back?
or what I could be missing?
Thanks.

Any one help me?
Can you find out why after doing the following the flash debugger is not stopping at break points.
I have my action script in separate .as files (Action Script 3.0).
I have installed flash debugger 10.
The publish settings are set to allow debugging and allow trace statements.
I run the remote debugger for 3.0.
Open my browser (IE8), it asks me to connect to the Localhost which I do.
I can now see the trace statements as I play around with my .swf.
However even though I have set breakpoints in the AS it is not stopping at them.
This is my problem why can I see the trace statements but it doesn’t stop at the breakpoints.
I am using Flash CS4 and the files are being exported as flash 9 with AS3.

Illegal override of usedMetadataFacets ???

What the heck is this?
VerifyError: Error #1053: Illegal override of usedMetadataFacets in org.osmf.layout.DefaultLayoutRenderer.

Operator Error:
I had placed OSMF.swc (Sprint 10) in the CS4...Actionscript 3.0/libs folder
but my FLA publish settings library path was still pointed to (Sprint 9).
Thanks for pointing me in the right direction.

Flash animation working in program preview, not in browser with up to date Flash Player.

After hitting next on this animation you can see there appears to be blank areas on the animation. If you mouse over them you will see buttons appear which is their "over state." When I publish the animation and preview it in Adobe Flash CS5.5 all the buttons are visible and work correctly. It is only in the brower (chrome, firefox, safari) with up to date Flash Player that is is not working. This is happening in a number of animations I created originally in CS4 last year, and am updating them as CS5.5 using AS3.
My application is up to date.

Are you loading those images externally?
Can you share an example of you loading an external file if so? It should look similar to this:
import flash.display.Loader;
import flash.display.Sprite;
import flash.events.Event;
import flash.events.IOErrorEvent;
var myLoader:Loader = new Loader();
myLoader.contentLoaderInfo.addEventListener(IOErrorEvent.IO_ERROR, onErrorHandler);
myLoader.contentLoaderInfo.addEventListener(Event.COMPLETE, onCompleteHandler);
function onErrorHandler(e:IOErrorEvent):void
     // put some visual code here to tell yourself you have a load error
     // otherwise you'll never know
     trace(e);
function onCompleteHandler(e:Event):void
     // add to display list if you wish (a Loader is a displayobject), or add it to a sprite and name it, etc
     addChild(e.target);
If you're not checking for errors then you won't know it's not loading things properly. That is of course if you're loading external assets.

Panneaux de métadonnées customisées XMP avec la CREATIVE CLOUD

Bonjour à tous,
Avant la CREATIVE CLOUD, nous avions l'habitude de créer des panneaux de métadonnées customisées pour l'industrie de la mode afin de gérer les nombreux fichiers graphiques (Illustrator, Photoshop, Indesign) permettant la création des modèles de vêtements, les plans de collection, les prints et Artwork, voir même les dossiers techniques dans indesign.
A l'aide d'Adobe bridge, nous pouvions définir des processus de gestion des ressources numériques très efficaces, s'appuyant sur le tri, la classification, l'annotation de ces fichiers.
Il était même possible en utilisant des mots clés, de récupérer les métadonnées en légende dans Indesign afin de produire très rapidement des documents synthétisant l'ensemble des informations essentielles de la collection.
En matière d'édition, nous pouvions également exporter dans un PDF ou un slide show, l'ensemble des fichiers d'une collection intelligente ou d'un filtre, via le module Output de Bridge (certes limité, mais quand même pratique, d'où l'incompréhension de nombreux utilisateurs qui ont vu ce module être retiré par défaut de Bridge CC, sans apporter d'alternative sérieuse).
Nous notons toutefois que le module output peut être réinstallé dans bridge CC mais ne présente aucune évolution fonctionnelle (voir le lien ci-dessous) :
Installation du module de sortie Adobe
Avec l'arrivée de la CREATIVE CLOUD, la procédure de création des panneaux XMP a été modifiée par Adobe.
En effet, avec les versions de la créative suite, il fallait utiliser Flash Builder pour créer des panneaux avancés de métadonnées (File info Dialog), ou alors un kit de fichiers fourni par Adobe se nommant GENERIC PANEL (fichier XML modifiable), permettant de créer des panneaux de métadonnées relativement simples.
Cette méthode présentait toutefois des problèmes évoqués sur les forums, car souvent ces panneaux apparaissaient vides dans les logiciels de la CREATIVE SUITE.
Malgré des explications plus ou moins hasardeuses des équipes techniques d'Adobe (création d'un fichier trust.cfg ou utilisation de la bonne version du SDK), beaucoup d'entre-nous n'ont jamais réellement su démystifier les caprices d'affichage des panneaux XMP utilisant la technologie flash.
Désormais, avec la CREATIVE CLOUD, il faut utiliser le kit XMP Metadata UI SDK qui regroupe un ensemble de fichiers XML paramétrables.
Théoriquement, nous n'avons donc plus besoin de passer par Flashbuilder pour créer des panneaux de métadonnées XMP.
Malheureusement, Il semblerait que la migration des panneaux XMP créés dans les anciennes versions (CS5, CS6) avec Flashbuilder ne soit pas possible en l'état (sauf pour le Generic panel qui a été réalisé via un fichier XML et qui peut être converti via le Generic panel converter mis à disposition par Adobe)
Avant de mettre la main dans le cambouis, j'aimerais donc savoir si :
Quelqu'un d'entre-vous a déjà expérimenté la création de ces nouveaux panneaux XMP via le kit XMP Metadata UI SDK
La procédure de création est plus simple
Les possibilités offertes par Flashbuilder via de l'action script ont été conservées dans ces nouveaux panneaux( ex : possibilité de créer des listes de saisies filtrables en fonction des critères renseignées)
L'affichage des nouveaux panneaux dans les outils Adobe se fait correctement
Dans l'attente de votre retour d'expérience.
Merci.
Daté TETEGAN

Bonjour,
Peut-être pourriez-vous tout désisntaller de façon clean avec l'utilitaire Cleaner Tools : http://helpx.adobe.com/fr/creative-suite/kb/cs5-cleaner-tool-installation-problems.html
Réinstaller suivant la configuration souhaitée.
Creative Cloud, n'a pas besoin d'être installé spécifiquement sur le bureau.

Integrating Flash CS3 with XML

Hello, I done a tutorial from learnflash.com on Integrating
Flash CS3 with XML, and I can't figure out why when the file is
published the scrollbar component doesn't work.

Yep, big difference. Flash CS3 is the earlier version of
Flash, so you can't open CS4 files in CS3. You are probably
confusing CS3 with AS3, which is supported by both versions of
Flash CS#.

Lectuer fichier .hyd

Bonjour,
Mon travail est de redévelopper une application qui a été faites sous LabWindows en LabVIEW car il est plus simple. Une des fonctionnalités de ce programme est de pouvoir observer une courbe dont les données sont issu des capteur (pression, température, vitesse, debit) puis de l'enregistrer et l'imprimer. L'utilisateur à aussi la possibilité de faire des recherche dans une base de donnée pour ressortir le test. (On peut faire une recherche par dossier, N° de travail ou par client)(bon je suis débutant en labview mais je cherche comment faire tout ça ^^)
Sauf que sous labWindows, ils ont enregistrer les tests (graphique + information dessus) dans un fichier dont l'extension est .hyd
Est ce que Labview est capable de lire ces fichiers pour que le programme puisse les relire ?
merci de votre compréhension
ps : serait il possible de le deplacer

La ligne à laquelle vous faites référence : fichier=fopen("nom.hyd","x");
permet la création d'un fichier nommé "nom.hyd". En effet, la fonction ANSI C "fopen" utilisée avec le mode "x" permet de créer un fichier ( elle renvoie une erreur si le fichier existe déjà ).
Avez vous des fonctions dans votre code du type "fprintf" ou d'autres fonctions d'écriture sur fichier ?
Pourriez vous uploader votre code ? cela sera plus facile de vous aider de cette manière.
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

Proftpd problem

Hello;
I would like to create a new proftpd user with the work directory : /database/55L/Logs and all rights possible (write, read, etc, ...). The default root for the proftpd server is : /database/55L/Logiciels (defaultroot).
I have added this :
<Limit CDUP PWD CWD READ>
AllowUser dbousseb
DenyAll
</Limit>
<Directory /database/55L/Logs/*>
<Limit ALL>
AllowUser dbousseb
DenyAll
</Limit>
</Directory>
But when I connect to server on default directory : /database/55L/Logiciels
I tape : "cd .." to change work directory to Logs => This not work ?
The file proftpd.conf :
# Fichier de configuration du serveur PROFTPD h�berg� par le serveur STL
#Mail de l 'administrateur du serveur
ServerAdmin               admin@localhost
#Nom du serveur proftpd
ServerName               "ProFTPD Serveur de Telechargement Logiciel"
#Mode de fonctionnement du serveur : lanc� par (x)inetd
ServerType               inetd
#Utile surtout pour les "virtuals hosts" mais laissez ainsi
DefaultServer               on
#Epurer la banni�re : pour ne pas donner d'info sur le serveur
DeferWelcome               off
#Message � afficher lors d'une connetion qui r�ussie ou �choue
ServerIdent               on      "Le serveur proftpd est pret"
#R�pertoire racine, les connect�s au serveur ne verrons que lui et son contenu
DefaultRoot               /database/55L/Logiciels
#R�pertoire dans lequel arrivent les utilisateurs accept�s
DefaultChdir /database/55L/Logiciels
#V�rifier si un compte ftp poss�de un shell valide
RequireValidShell          yes
#Autoriser l'usage de /etc/ftpusers
UseFtpUsers on
#le daemon �coute sur le port 21
Port                    21
#standard umask qui sera appliquer lors de la cr�ation d'un fichier ou d'un r�pertoire : seul le
#propri�taire d'un fichier peut le modifier.
Umask                    022
#Nombre de processus fils maximum qui sera utiliser par proftpd
MaxInstances               30
#Les contr�le d'acc�s :
# - Le Timeout laiss� � l'utilisateur pour envoyer des commandes
# - Le Timeout laiss� � l'utilisteur de rester connect� sans recevoir aucune donn�e
# - Le timeout laiss� � l'utilisateur pour s'authentifier
#passer ce d�lai le serveur fermera la connection automatiquement. L'unit� est exprim�e en secondes (300 sec est un timeout correct)
TimeoutStalled               300
TimeoutNoTransfer          300
TimeoutIdle               300
TimeoutLogin               120
# Format des logs par d�faut, pour l'authentifcation et les transferts
LogFormat               default "%h %l %u %t \"%r\" %s %b"
LogFormat               auth "%v [%P] %h %t \"%r\" %s"
LogFormat               write "%h %l %u %t \"%r\" %s %b"
#Niveau des logs en mode debug pour afficher toutes les informations n�cessaires en cas d'un �ventuel dysfonctionnement
SyslogLevel               debug
#Localisation des logs des connections et transferts
TransferLog               /database/55L/Logs/Tel-Stl-UCA2-3/info.log
SystemLog               /database/55L/Logs/Tel-Stl-UCA2-3/error.log
ExtendedLog               /database/55L/Logs/Tel-Stl-UCA2-3/auth.log AUTH auth
ExtendedLog               /database/55L/Logs/Tel-Stl-UCA2-3/access.log READ,WRITE write
ExtendedLog               /database/55L/Logs/Tel-Stl-UCA2-3/all.log ALL
# Param�tres indiquant que le serveur proftpd est lanc� avec les privil�ges (c'est � dire aucun) de nobody
# Garder ces valeurs par d�faut afin d'eviter que l'utilisateur qui lance le serveur n'ai pas trop de privil�ges.
User                    nobody
Group                    nogroup
#limitation du nombre de tentatives de login
MaxLoginAttempts          5
#Message lors du login
AccessGrantMsg               "Bienvenue %u sur le STL...."
# Nombre maximum de clients diff�rents qui peuvent se connecter simultan�ment sur le serveur
MaxClients               1000 "Desole, max %m utilisateurs -- essayer plus tard"
# Limiter le nombre maximum de clients par machine
MaxClientsPerHost               1000
# Permet la reprise du t�l�chargement et la copie en cas de rupture
AllowRetrieveRestart on
AllowStoreRestart on
# Interdire la lecture sur le serveur sauf pour le compte dbousseb
<Limit CDUP PWD CWD READ>
AllowUser dbousseb
DenyAll
</Limit>
<Directory /database/55L/Logs/*>
<Limit ALL>
AllowUser dbousseb
DenyAll
</Limit>
</Directory>
Best regards;
Djamel;

The problem was indeed /etc/hosts ... over time it somehow drifted out of sync with reality All is well now, thank you!

Comment inserer mes photos dans les pages ?

bonjour,
Mes photos sont placées dans mon texte dans la création de mon fichier dans Indesign. Mais à l'exportation en Epub, elles se retrouvent à la fin du doc ?
Comment faire pour qu'elles restent à leur place ?
Merci

From InDesign CS6, all EPUB export is "reflowable." That means that it resizes depending on the device on which you're viewing the EPUB.
You need to use anchored objects to anchor your images:
https://helpx.adobe.com/indesign/using/anchored-objects.html
Also, do a browser search on "indesign anchored objects"

Plantage CS4 à l'ouverture ou la création d'un fichier fla AS3

Similar Messages

Maybe you are looking for