Illustrator runtime/processing logs locations?
Hello,
I'm going to check with my company's developers to look at the issue, they might know the answer or some of it, but in any case thought I'd ask here as well.
We have a custom AI script that processes art files (removes some stuff from file). There's a single processing version where you open art file and run script to process it. Then there's a batch processing version where you run script from AI > Scripts > batch > script name. It will ask for directory then process all art files in that location.
When using the single processing version, no script specific logs are generated (that I know of, will check with developers). For batch processing, AI or script does generate a log in same folder specified for the batch processing.
What I've run into is processing a specific art file causes AI to ramp up memory usage all the way up to 1.27 GB (virtual memory being at 1.25 GB). At that point, AI stops doing any processing and doesn't close the art file (which it should do on completion). When processing AI could be unresponsive and see CPU usage at 50% more or less, etc. At the problem point, AI CPU is 0%, and is responsive, but art file processing has completely stopped, and memory usage is way as mentioned.
The script log (if available) doesn't indicate any issue. So I would like to look into AI system/app logs if available to see what might be the problem. I'm also going to talk with our developers about this when I get back to work.
So my question here is where can I find AI system/app logs if any? I'm not looking for AI installation logs.
Absent any logs, looks like troubleshooting might require analyzing what the AI script does, adding debug logging to AI script, and/or run some type of spy tool to AI to see what it's doing up to that crash point.
You don't mention the OS that you are on but on the mac you can open you crash logs using the 'Console' app It sounds as though you are not actually getting to a crash so Im not sure if this would help… The log for your batch script is almost certainly being wrote by the script at runtime and not a report from either Adobe's app or the OS… Your question is almost certianly for the developer…
Similar Messages
-
Hi all,
I'm trying to excute a Standard Batch Loader Script, but I have always the same error.
I have realized an FDM Appication, the bacth loader script and the data file (with this name 1@JDE@Actual_Inp@August@RR ).
Adapter, Import formats, Maps and Location seems ok.
THIS IS THE ERROR LOG:
** Begin FDM Runtime Error Log Entry [2013-09-24 12:59:06] **
ERROR:
Code............................................. 6
Description...................................... Overflow
Procedure........................................ clsBatchLoader.mExecuteParallelBatchProcess
Component........................................ upsWBatchLoaderDM
Version.......................................... 1112
Thread........................................... 4100
Could someone help me?
Thanks in advance
AndreaIf I use manaul process I can see the data in Import/Validation/Export steps, if I use Batch processing no data are dispalyed....
This is the script that I'm using, maybe something is wrong?
the bacth processing settings are:
Batch Type: standard
Process Level: Up To Load
Process Methid: Serial
File Name Delimiter: @
Load Balance Server: the server name avilable on the server Group
Sub TestLoad()
'Oracle Hyperion FDM Custom Script:
'Created By: ALu
'Date Created: 9/16/2013 4:17:23 PM
'Purpose: Execute a Standard Serial Processing FDM Batch
'Standard Batch Serial Processing
'Declare Local Variables
Dim lngProcessLevel
Dim strDelimiter
Dim blnAutoMapCorrect
'Initialize Variables
lngProcessLevel = 12 'Up-To-Check
strDelimiter = "@" 'File-Name-Delimiter"
blnAutoMapCorrect = 0 'Auto Map Correction is Off
'Create the file collection
Set BATCHENG.Pcolfiles = BATCHENG.fFileCollectionCreate(CStr(strDelimiter))
'Execute a Standard Serial Batch
BATCHENG.mFileCollectionProcess BATCHENG.PcolFiles, CLng(lngProcessLevel), , CBool(blnAutoMapCorrect)
End Sub
Thanks
Andrea -
Webutil error "unable to communicate with runtime process."
Hi,
Yesterday I configured webutil with Developer 10g (9.0.4).
I used webutil_106.zip and jacob_18.zip.
I succesfully deploy a form that display the selection file dialog with the function:
CLIENT_GET_FILE_NAME
Today I tried to test again the form, and I got an error when the form is opening, I review the log and I find "unable to communicate with runtime process.".....
I didn't change any configuration... what I'm doing wrong..... It just work great yesterday!!!!
I tried signing again the jacob.jar and frmwebutil.jar files..... However I still have the error.......
Any help is welcome....
The error in the log:
09/03/25 10:57:45 Started
09/03/25 10:57:55 forms90web: jsp: init
09/03/25 10:57:55 forms90web: f90servlet: init
09/03/25 10:57:55 forms90web: FormsServlet init():
configFileName: c:\dev10g/forms90/server/formsweb.cfg
testMode: false
09/03/25 10:57:55 forms90web: 9.0.4.0.0 Started
09/03/25 10:57:56 forms90web: l90servlet: init
09/03/25 10:57:56 forms90web: ListenerServlet init()
09/03/25 10:58:02 forms90web: Forms session <1> aborted: unable to communicate with runtime process.
09/03/25 10:58:02 forms90web: Forms session <1> exception stack trace:
java.io.IOException: FRM-93000: Unexpected internal error.
Details : No HTTP headers received from runform
at oracle.forms.servlet.ListenerServlet.forwardResponseFromRunform(Unknown Source)
at oracle.forms.servlet.ListenerServlet.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:765)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
09/03/25 11:00:58 forms90web: l90servlet: destroy
09/03/25 11:00:58 forms90web: 9.0.4.0.0 Stopped
09/03/25 11:00:58 Stopped (Shutdown executed by jazn.com/admin from 127.0.0.1 (localhost))
Edited by: Santiago on 25/03/2009 11:23 AMI Find the way, It's OK now.
When I use the webutil.olb in a form. I chose "Subclass", It's necessary to choose "Copy". -
I got this error when calling report from my form：
FRM-93652: The runtime process has terminated abnormally
Forms Session ID is WLS FORMS.formsapp.101
Here is the trace dump info :
Last Trigger FORM/BLOCK/FIELD: FRM_ACTIVITY_QUEUE.BLK_ACTIVITY_QUEUE.BTN_PRINT
Last Trigger: WHEN-BUTTON-PRESSED - (In Progress)
Last Builtin: RUN_REPORT_OBJECT - (In Progress)
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
siehDumpStackTrace( call kgdsdst() 000000000 ? 000000000 ?
)+104 7FFFBF18D110 ? 7FFFBF18D1D8 ?
7FFFBF1AD130 ? 000000000 ?
siehjmpterm()+650 call siehDumpStackTrace( 000000000 ? 2B1668E4EB00 ?
) 7FFFBF18D110 ? 7FFFBF18D1D8 ?
7FFFBF1AD130 ? 000000000 ?
__restore_rt() call siehjmpterm() 00000000B ? 2B1668E4EB00 ?
7FFFBF18D110 ? 7FFFBF18D1D8 ?
7FFFBF1AD130 ? 000000000 ?
00002B1660459EB0 signal __restore_rt() 2B16603F2929 ? 7FFFBF1ADBD8 ?
000000000 ? 000000002 ?
000000001 ? 0EBC57ED8 ?
Anybody knows what might be the cause ?
ThanksRefer to : Oracle Support : Forms Runtime Crash (FRM-93652) When calling RUN_REPORT_OBJECT in 11g (Doc ID 1306368.1)
-
PJC set_custom_property gives unable to communicate with runtime process
Hi
I am modifying a PJC that extends VTextItem to act as a hyperlink I have registered a property in the PJC with the following code:
public static final ID activeColor = ID.registerProperty("ACTIVE_COLOUR");
I then attempt to set the property from my form with the following code
set_custom_property('icr_block1.icr_details',lv_rec_number,'ACTIVE_COLOUR','45,213,169');
icr_block1.icr_details is a text item that has the PJC as its implementation class. The following error appears in the java console
oracle.forms.net.ConnectionException: Forms session <5> aborted: unable to communicate with runtime process
Anybody have any ideas?
many thanks
paul schweigerPermission granted - here is the full java code. When I set_custom_property in the form neither of the debug messages in the java fire
package pjcs;
//package totem.forms.extensions;
import java.awt.*;
import java.awt.event.*;
import java.util.StringTokenizer;
import oracle.forms.properties.ID;
import oracle.forms.ui.VTextField;
public class TextLink extends VTextField
public static final ID treatAsLink = ID.registerProperty("TREAT_AS_LINK");
public static final ID activeColor = ID.registerProperty("ACTIVE_COLOUR");
public static final ID visitedColor = ID.registerProperty("VISITED_COLOUR");
private Cursor defaultCursor;
private Cursor hoverCursor;
private String pTreatAsLink = "YES";
private Color pActiveColor;
private Color pVisitedColor;
private Color pNormalColor;
private boolean m_debug = true;
private boolean m_debugAll;
private final String CLASSNAME = this.getClass().getName();
public TextLink()
try
jbInit();
catch(Exception e)
e.printStackTrace();
private void jbInit() throws Exception
log("start text link");
// Get reference to standard cursor
defaultCursor = this.getCursor();
// Create hand cursor for hover state
hoverCursor = new Cursor(Cursor.HAND_CURSOR);
// Add mouse listeners for changing cursor
// Anonymous class used for simplicity
this.addMouseListener(new MouseAdapter()
public void mouseEntered(MouseEvent me)
// Set hover cursor if field contains text
if (getText().length() > 0 && pTreatAsLink == "YES")
setCursor(hoverCursor);
pNormalColor = getForeground();
setForeground(pActiveColor);
public void mouseExited(MouseEvent me)
// Change cursor back
if (pTreatAsLink == "YES")
setCursor(defaultCursor);
setForeground(pNormalColor);
* set the properties of the bean
public boolean setProperty(ID property, Object value)
log("set prop");
if (property == treatAsLink)
pTreatAsLink = value.toString();
return true;
else if (property == activeColor)
pActiveColor = stripColour(value) ;
return true;
else if (property == visitedColor)
pVisitedColor = stripColour(value) ;
return true;
else
return super.setProperty(property, value);
private Color stripColour(Object pColour) {
String color = pColour.toString().trim();
int r=-1, g=-1, b=-1, c=0 ;
StringTokenizer st = new StringTokenizer(color,",");
while (st.hasMoreTokens()) {
c = new Integer((String)st.nextToken()).intValue() ;
if( (c <0) || (c > 255) ) c = 0 ;
if( r == -1 ) r = c ;
else if( g == -1 ) g = c ;
else if( b == -1 ) b = c ;
return (new Color(r,g,b));
public void log(String msg)
if(m_debug||m_debugAll)
System.out.println(CLASSNAME + ": " + msg);
} -
Forms session 125,296 aborted: unable to communicate with runtime process
Forms 10g version on Hp unix.
We have about 400 users are using 10g web based application. Our users get the error "There was a failure in the forms server during startup. This could happen due to invalid configuration.
Please look into the web-server log file for details."
web-server log file it says
'Forms session <125,296> aborted: unable to communicate with runtime process.'
It is not reproducible error. But it happens to everybody at random time/form/database which makes big impact on our business.
We are in the edge of backing out of oracle forms due to this error
Any help will be appreciatedWould be a really bummer if you backed out of Forms and found the problems were because of network glitches ;o)
You need to do a bit a scratching around to get more details on this.
http://www.oracle.com/technology/products/forms/pdf/10g/troubleshooting_fls.pdf would be a good place to start. Chances are, network glitches are cause a disconnects but you need to confirm this by using the techniques described in this paper.
Regards
Grant -
Currently i have stored procedure which over a dblink pulls data from 1 database &
loads into another database
We want to log the whole process
say the started , ended, status flag, date_time, failure cause, affected rows
i am not looking here for an error log but process log
who can log details about the step by step process involved
Rgrds
SushantYou can use the UTL_FILE package to write to files from your procedure, so can maintain a process log file through this package.
If you are using 9i you can use directory objects to specify the location of you files. For earlier versions you need to use the UTL_FILE_DIR init.ora parameter to specify the locations. This needs a restart for the parameter to take effect.
Then, its up to you to code into you procedure what you want to put in your log file. -
IOException starting Java runtime process
Whenever i run a program, i get this error
-- IOException starting Java runtime process --
java.io.IOException: CreateProcess: D:\Borland\JBuilder2005\jdk1.4\bin\javaw -classpath "E:\Documents and Settings\Administrator\jbproject\SwingApplication\classes;D:\Borland\JBuilder2005\jdk1.4\jre\lib\im\indicim.jar;D:\Borland\JBuilder2005\jdk1.4\jre\lib\im\thaiim.jar;D:\Borland\JBuilder2005\jdk1.4\jre\lib\ext\dnsns.jar;D:\Borland\JBuilder2005\jdk1.4\jre\lib\ext\sunjce_provider.jar;D:\Borland\JBuilder2005\jdk1.4\jre\lib\ext\ldapsec.jar;D:\Borland\JBuilder2005\jdk1.4\jre\lib\ext\localedata.jar;D:\Borland\JBuilder2005\jdk1.4\jre\lib\jsse.jar;D:\Borland\JBuilder2005\jdk1.4\jre\lib\plugin.jar;D:\Borland\JBuilder2005\jdk1.4\jre\lib\sunrsasign.jar;D:\Borland\JBuilder2005\jdk1.4\jre\lib\charsets.jar;D:\Borland\JBuilder2005\jdk1.4\jre\lib\rt.jar;D:\Borland\JBuilder2005\jdk1.4\jre\lib\jce.jar;D:\Borland\JBuilder2005\jdk1.4\jre\javaws\javaws.jar;D:\Borland\JBuilder2005\jdk1.4\lib\tools.jar;D:\Borland\JBuilder2005\jdk1.4\lib\dt.jar;D:\Borland\JBuilder2005\jdk1.4\lib\htmlconverter.jar" swingapplication.SwingApplication error=3
I use JBuilder , if this error is related to classpath, how do i set path? please help meCan javaw.exe be found at that location?
- Saish -
HI all,
Can i know where the jlaunch process logs are located for only As java system.Thanks in advance.
Also i wanted to know where are the logs for sap os collector.Thanks in advance.Hi,
You will find all the logs in
windows <drive:\>usr\sap\SID\JC<NN>\work
unix \usr\sap\SID\JC<NN>\work
Thanks
Anil -
ABAP Mapping - Message shown in Standard Change List Process Log
Hi
I am working with ABAP Mapping program. I had created ABAP class using ABAP workbench. Before this, in exchangeProfile..data was provided for com.sap.aii.repository.mapping.additionaltypes ==>> as " R3_ABAP|Abap-class;R3_XSLT|XSL (ABAP Engine) " and 'Saved'.
In Interface Mapping, after providing the Class Name under 'Mapping Program' and activated. After activation (Standard Change List), it is showing the following messages under 'Processing Log'.
--> Standard Change List - Process Log message
Activation of the change list canceled Check result for Interface Mapping IM_ABAP_MAPPING | http://ABAP_Mapping_SREE: Type R3_ABAP of
program ZSREETEST is invalid because it is not registered in the exchange profile . Check the values for the exchange profile parameter
IntegrationBuilder.Repository.com.sap.aii.repository.mapping.additionaltypes
--> End of Log message
Can some one please guide me in resolving the ABAP mapping issue.
Thanks in advance.
..SreeSree,
The log says that there is ABAP mapping included in your exchange profile. Do the things what michal have told and also check your mapping program whether working fine or not in SXI_MAPPING transaction.
You can see this weblog for reference:
/people/sameer.shadab/blog/2005/09/29/testing-abap-mapping
---Satish -
Error message in processing log in VA02 in External send.
Hi,
In my smartform I am using READ_TEXT to read one text and I have checked the exceptions also in the call to function module.
CALL FUNCTION 'READ_TEXT'
EXPORTING
ID = 'ST'
LANGUAGE = ZNAST-SPRAS
NAME = Y_LV_NAME
OBJECT = 'TEXT'
TABLES
LINES = y_i_tline
EXCEPTIONS
ID = 1
LANGUAGE = 2
NAME = 3
NOT_FOUND = 4
OBJECT = 5
REFERENCE_CHECK = 6
WRONG_ACCESS_TO_ARCHIVE = 7
OTHERS = 8.
endif.
But I am not maintaining the text in SO10 and the READ_TEXT will return sy-subrc 4 .In va02 in messages tab ,I am creating output 1(print output) and 5 (external send) and save the document.when I check the processing log for both,In print output I can't see any error messages.But in external send I am getting error message that the text <my text> not found in language <my lang>.I want to know why the error message (exception thrown by READ_TEXT)comes in EXternal send in processing log and it is not coming in the processing log of print output ? .can anybody help me out ? I can't debug while saving the document since everything is handled in back groud(The smartform won't get triggered while saving).hi
Please debug, for which u need to '/H' B4 that have a break-point in ur Driver program on SSF or the READ_TEXT Fm and SAVE in debug mode. When in DEBUG mode ,Under SETTINGS choose SYSTEM DEBUGGING and UPDATE DEBUGGING which allow you to debug and check the Error/Exception from the READ_TEXT FM ...
surya -
Adobe Premiere Elements 8 Can't finish installing Air Runtime Process, and Can't open New Project!
Hey guys,
I'm having some major issues installing PE8. I can open the installer screen fine, and it installs fine until it gets to installing the Air Runtime Process. I have left it downloading that one process for about 5 hours, and i'm not exaggerating. Finnally, I get too mad waiting for it to finish that I exit out of the installation process. Even though the installation was never fully finished, for some reason I do have a Desktop icon for PE8. I click on that and it opens the splash screen with the buttons "New project", "Open Project", and "Organize". When I try to open "New Project" it begins loading the files that it needs to to open it. When it gets to loading the Windows Media file, it freezes and then crashes.
I have uninstalled the PE8 and reinstalled it about 5 times now. I have also used the Windows Cleanup program to clean these corrupted files out of my system before reinstalling. I have called in twice now to the technical support and they haven't helped me one ounce. Any answers would be appreciated! Thanks
Thanks Again,
Spencer
Here is the Crash Data:
<?xml version="1.0"?>
<!DOCTYPE crashreport SYSTEM "AdobeCrashReporter.dtd">
<crashreport version="1.1" crVersion="3.0.20090804" applicationName="Adobe Premiere Elements" applicationVersion="8. 0. 0. 0" build="unknown">
<time year="2009" month="11" day="20" hour="22" minute="57" second="2"/>
<user guid="f32bcbfe-242d-4051-8b96-487956b2e7bc"/>
<system platform="windows" osversion="5.1.2600 SP 2.0" applicationlanguage="Language Neutral" userlanguage="en_US" oslanguage="en_US" ram="893" machine="AMD Athlon(tm) 64 X2 Dual-Core Processor TK-55" model="x86 Family 15 Model 104 Stepping 1" cpuCount="2" cpuFreq="1800 MHz" busFreq="" locale="English (United States)"/>
<crash exception="EXCEPTION_ACCESS_VIOLATION" instruction="0x01a29f27">
<backtrace crashedThread="0">
<thread index="0">
<stackStatement index="0" address="0x01a29f27" symbolname="UIF::MenuUtils::RenameMenuItemCommand"/>
</thread>
</backtrace>
<registerSet>
<register name="EAX" value="0x00000000"/>
<register name="EBX" value="0x000000fa"/>
<register name="ECX" value="0x50010001"/>
<register name="EDX" value="0x0012ddc0"/>
<register name="ESI" value="0x0c93f3a0"/>
<register name="EDI" value="0x0012df24"/>
<register name="ESP" value="0x00000057"/>
<register name="EBP" value="0x0000004f"/>
<register name="EIP" value="0x00000000"/>
<register name="EFL" value="0x00010246"/>
</registerSet>
<binaryImageSet>
<binaryImage start="0x00400000" end="0x008de000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Adobe Premiere Elements.exe"/>
<binaryImage start="0x7c900000" end="0x7c9b2000" type="__TEXT" path="C:\WINDOWS\system32\ntdll.dll"/>
<binaryImage start="0x7c800000" end="0x7c8f5000" type="__TEXT" path="C:\WINDOWS\system32\kernel32.dll"/>
<binaryImage start="0x10000000" end="0x1000f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\CrashReporter.dll"/>
<binaryImage start="0x59a60000" end="0x59b01000" type="__TEXT" path="C:\WINDOWS\system32\dbghelp.dll"/>
<binaryImage start="0x77c10000" end="0x77c68000" type="__TEXT" path="C:\WINDOWS\system32\msvcrt.dll"/>
<binaryImage start="0x77c00000" end="0x77c08000" type="__TEXT" path="C:\WINDOWS\system32\version.dll"/>
<binaryImage start="0x77dd0000" end="0x77e6b000" type="__TEXT" path="C:\WINDOWS\system32\advapi32.dll"/>
<binaryImage start="0x77e70000" end="0x77f02000" type="__TEXT" path="C:\WINDOWS\system32\rpcrt4.dll"/>
<binaryImage start="0x77fe0000" end="0x77ff1000" type="__TEXT" path="C:\WINDOWS\system32\secur32.dll"/>
<binaryImage start="0x00340000" end="0x0034f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\LogUtils.dll"/>
<binaryImage start="0x7c9c0000" end="0x7d1d6000" type="__TEXT" path="C:\WINDOWS\system32\shell32.dll"/>
<binaryImage start="0x77f10000" end="0x77f58000" type="__TEXT" path="C:\WINDOWS\system32\gdi32.dll"/>
<binaryImage start="0x77d40000" end="0x77dd0000" type="__TEXT" path="C:\WINDOWS\system32\user32.dll"/>
<binaryImage start="0x77f60000" end="0x77fd6000" type="__TEXT" path="C:\WINDOWS\system32\shlwapi.dll"/>
<binaryImage start="0x774e0000" end="0x7761c000" type="__TEXT" path="C:\WINDOWS\system32\ole32.dll"/>
<binaryImage start="0x78130000" end="0x781cb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.405 3_x-ww_e6967989\msvcr80.dll"/>
<binaryImage start="0x7c420000" end="0x7c4a7000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.405 3_x-ww_e6967989\msvcp80.dll"/>
<binaryImage start="0x77120000" end="0x771ac000" type="__TEXT" path="C:\WINDOWS\system32\oleaut32.dll"/>
<binaryImage start="0x008e0000" end="0x00a34000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvacore.dll"/>
<binaryImage start="0x00370000" end="0x003fc000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLFoundation.dll"/>
<binaryImage start="0x4ec50000" end="0x4edfb000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.60 01.22319_x-ww_f0b4c2df\GdiPlus.dll"/>
<binaryImage start="0x76bf0000" end="0x76bfb000" type="__TEXT" path="C:\WINDOWS\system32\psapi.dll"/>
<binaryImage start="0x00a50000" end="0x00a56000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PRM.dll"/>
<binaryImage start="0x773d0000" end="0x774d2000" type="__TEXT" path="C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1d f_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll"/>
<binaryImage start="0x012a0000" end="0x012d7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\adobe_caps.dll"/>
<binaryImage start="0x012f0000" end="0x01322000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Startup.dll"/>
<binaryImage start="0x01340000" end="0x01369000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PreRegistration.dll"/>
<binaryImage start="0x01380000" end="0x0168b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtlib.dll"/>
<binaryImage start="0x5b860000" end="0x5b8b4000" type="__TEXT" path="C:\WINDOWS\system32\netapi32.dll"/>
<binaryImage start="0x71ab0000" end="0x71ac7000" type="__TEXT" path="C:\WINDOWS\system32\ws2_32.dll"/>
<binaryImage start="0x71aa0000" end="0x71aa8000" type="__TEXT" path="C:\WINDOWS\system32\ws2help.dll"/>
<binaryImage start="0x4d4f0000" end="0x4d548000" type="__TEXT" path="C:\WINDOWS\system32\winhttp.dll"/>
<binaryImage start="0x763b0000" end="0x763f9000" type="__TEXT" path="C:\WINDOWS\system32\comdlg32.dll"/>
<binaryImage start="0x12000000" end="0x121c7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\xerces-c_2_1_0.dll"/>
<binaryImage start="0x016a0000" end="0x016b1000" type="__TEXT" path="C:\WINDOWS\system32\msvcirt.dll"/>
<binaryImage start="0x018c0000" end="0x01dae000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\UIFramework.dll"/>
<binaryImage start="0x016d0000" end="0x01843000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ImageRenderer.dll"/>
<binaryImage start="0x7f840000" end="0x7fa07000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MCDVD_32.DLL"/>
<binaryImage start="0x76b40000" end="0x76b6d000" type="__TEXT" path="C:\WINDOWS\system32\winmm.dll"/>
<binaryImage start="0x01db0000" end="0x02073000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\libmmd.dll"/>
<binaryImage start="0x02080000" end="0x022ae000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvaui.dll"/>
<binaryImage start="0x01870000" end="0x01886000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLMessaging.dll"/>
<binaryImage start="0x022b0000" end="0x02ac0000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Backend.dll"/>
<binaryImage start="0x02ac0000" end="0x02c8e000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\xerces-c_2_7.dll"/>
<binaryImage start="0x02ca0000" end="0x02d04000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AudioRenderer.dll"/>
<binaryImage start="0x02d20000" end="0x02d47000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MediaFoundation.dll"/>
<binaryImage start="0x02d60000" end="0x02d84000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\processcoordinationclient.dll"/>
<binaryImage start="0x02da0000" end="0x02da9000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\processcoordinationsupport.dll"/>
<binaryImage start="0x02dc0000" end="0x02dd3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLUnitTesting.dll"/>
<binaryImage start="0x02df0000" end="0x02e00000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ASLConsole.dll"/>
<binaryImage start="0x02e10000" end="0x02ed7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvaworkspace.dll"/>
<binaryImage start="0x76380000" end="0x76385000" type="__TEXT" path="C:\WINDOWS\system32\msimg32.dll"/>
<binaryImage start="0x5ad70000" end="0x5ada8000" type="__TEXT" path="C:\WINDOWS\system32\uxtheme.dll"/>
<binaryImage start="0x02ef0000" end="0x02f19000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MLFoundation.dll"/>
<binaryImage start="0x02f30000" end="0x02f6f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\About.dll"/>
<binaryImage start="0x031c0000" end="0x03617000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\UIFramework.en_US.DLL"/>
<binaryImage start="0x03630000" end="0x03695000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\About.en_US.DLL"/>
<binaryImage start="0x602d0000" end="0x602e5000" type="__TEXT" path="C:\Program Files\CA\CA Internet Security Suite\CA Anti-Spam\QSP-5.1.18.0\QOEHook.dll"/>
<binaryImage start="0x05820000" end="0x058bd000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amtservices.dll"/>
<binaryImage start="0x77920000" end="0x77a13000" type="__TEXT" path="C:\WINDOWS\system32\setupapi.dll"/>
<binaryImage start="0x77690000" end="0x776b1000" type="__TEXT" path="C:\WINDOWS\system32\ntmarta.dll"/>
<binaryImage start="0x76f60000" end="0x76f8c000" type="__TEXT" path="C:\WINDOWS\system32\wldap32.dll"/>
<binaryImage start="0x71bf0000" end="0x71c03000" type="__TEXT" path="C:\WINDOWS\system32\samlib.dll"/>
<binaryImage start="0x059e0000" end="0x05a00000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\asneu.dll"/>
<binaryImage start="0x05a10000" end="0x0632f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Premiere.dll"/>
<binaryImage start="0x06340000" end="0x065cf000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AMocWrapper.dll"/>
<binaryImage start="0x065d0000" end="0x0660b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\VideoFrame.dll"/>
<binaryImage start="0x75a70000" end="0x75a91000" type="__TEXT" path="C:\WINDOWS\system32\msvfw32.dll"/>
<binaryImage start="0x06620000" end="0x06627000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MemoryShell.dll"/>
<binaryImage start="0x06640000" end="0x06654000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\BackendLegacyLib.dll"/>
<binaryImage start="0x06670000" end="0x06677000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Memory.dll"/>
<binaryImage start="0x06690000" end="0x06774000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ImporterHost.dll"/>
<binaryImage start="0x06790000" end="0x067fd000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeXMP.dll"/>
<binaryImage start="0x06810000" end="0x0688f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeXMPFiles.dll"/>
<binaryImage start="0x068a0000" end="0x068a6000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\QTMutex.dll"/>
<binaryImage start="0x068c0000" end="0x068e0000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MediaUtils.dll"/>
<binaryImage start="0x77be0000" end="0x77bf5000" type="__TEXT" path="C:\WINDOWS\system32\msacm32.dll"/>
<binaryImage start="0x068f0000" end="0x06922000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AudioSupport.dll"/>
<binaryImage start="0x06940000" end="0x06969000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\SweetPeaSupport.dll"/>
<binaryImage start="0x06980000" end="0x069af000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PluginSupport.dll"/>
<binaryImage start="0x71b20000" end="0x71b32000" type="__TEXT" path="C:\WINDOWS\system32\mpr.dll"/>
<binaryImage start="0x069c0000" end="0x06a2d000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ContentAnalysisData.dll"/>
<binaryImage start="0x06a40000" end="0x06a82000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvatemporalxmp.dll"/>
<binaryImage start="0x06aa0000" end="0x06ab9000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ContentAnalysisDBCache.dll"/>
<binaryImage start="0x06ad0000" end="0x06b07000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ARA.dll"/>
<binaryImage start="0x06b20000" end="0x06b93000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\OLS.dll"/>
<binaryImage start="0x06bb0000" end="0x06bc3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\OperaMgr.dll"/>
<binaryImage start="0x06be0000" end="0x07828000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HSL.dll"/>
<binaryImage start="0x07840000" end="0x07873000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MediaCoreUI.dll"/>
<binaryImage start="0x07890000" end="0x07918000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dvaeve.dll"/>
<binaryImage start="0x77a80000" end="0x77b14000" type="__TEXT" path="C:\WINDOWS\system32\crypt32.dll"/>
<binaryImage start="0x77b20000" end="0x77b32000" type="__TEXT" path="C:\WINDOWS\system32\msasn1.dll"/>
<binaryImage start="0x07930000" end="0x07a6c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AdobeOwl.dll"/>
<binaryImage start="0x07a80000" end="0x07bc3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\SettingsUI.dll"/>
<binaryImage start="0x07be0000" end="0x07cbc000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\FileInfo.dll"/>
<binaryImage start="0x74c80000" end="0x74cac000" type="__TEXT" path="C:\WINDOWS\system32\oleacc.dll"/>
<binaryImage start="0x76080000" end="0x760e5000" type="__TEXT" path="C:\WINDOWS\system32\msvcp60.dll"/>
<binaryImage start="0x73000000" end="0x73026000" type="__TEXT" path="C:\WINDOWS\system32\winspool.drv"/>
<binaryImage start="0x07cd0000" end="0x07d1a000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\BIB.dll"/>
<binaryImage start="0x07d30000" end="0x07dba000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\EncoderHost.dll"/>
<binaryImage start="0x07dd0000" end="0x07dfe000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PostEncodeHost.dll"/>
<binaryImage start="0x07e10000" end="0x07e48000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\amefoundation.dll"/>
<binaryImage start="0x07e60000" end="0x07e8f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ameproperties.dll"/>
<binaryImage start="0x07ea0000" end="0x07f12000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ExporterHost.dll"/>
<binaryImage start="0x07f30000" end="0x08009000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AMEWrapper.dll"/>
<binaryImage start="0x08020000" end="0x080c3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\VideoRenderer.dll"/>
<binaryImage start="0x080e0000" end="0x080f7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AMEAppFoundation.dll"/>
<binaryImage start="0x08110000" end="0x081a2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\VideoFilterHost.dll"/>
<binaryImage start="0x081c0000" end="0x08295000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\exo.dll"/>
<binaryImage start="0x082b0000" end="0x082ba000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\RoyaltyActivation.dll"/>
<binaryImage start="0x082d0000" end="0x08329000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\RecorderHost.dll"/>
<binaryImage start="0x08340000" end="0x08393000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PlayerHost.dll"/>
<binaryImage start="0x083b0000" end="0x08513000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\DVDCreator.dll"/>
<binaryImage start="0x08530000" end="0x099f2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AuthorScript.dll"/>
<binaryImage start="0x7c3a0000" end="0x7c41b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\msvcp71.dll"/>
<binaryImage start="0x7c340000" end="0x7c396000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\msvcr71.dll"/>
<binaryImage start="0x09a00000" end="0x09aba000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\px.dll"/>
<binaryImage start="0x73f10000" end="0x73f6c000" type="__TEXT" path="C:\WINDOWS\system32\dsound.dll"/>
<binaryImage start="0x76780000" end="0x76789000" type="__TEXT" path="C:\WINDOWS\system32\shfolder.dll"/>
<binaryImage start="0x5ed00000" end="0x5edcc000" type="__TEXT" path="C:\WINDOWS\system32\opengl32.dll"/>
<binaryImage start="0x68b20000" end="0x68b40000" type="__TEXT" path="C:\WINDOWS\system32\glu32.dll"/>
<binaryImage start="0x73760000" end="0x737a9000" type="__TEXT" path="C:\WINDOWS\system32\ddraw.dll"/>
<binaryImage start="0x73bc0000" end="0x73bc6000" type="__TEXT" path="C:\WINDOWS\system32\dciman32.dll"/>
<binaryImage start="0x09ad0000" end="0x0a1d9000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Mezzanine.dll"/>
<binaryImage start="0x0a1f0000" end="0x0a202000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ahclient.dll"/>
<binaryImage start="0x771b0000" end="0x77258000" type="__TEXT" path="C:\WINDOWS\system32\wininet.dll"/>
<binaryImage start="0x0a220000" end="0x0a232000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ProjectSupport.dll"/>
<binaryImage start="0x0a250000" end="0x0a2d0000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\dynamiclink.dll"/>
<binaryImage start="0x0a2e0000" end="0x0a2fe000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AudioFilterHost.dll"/>
<binaryImage start="0x0a310000" end="0x0a33a000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\DynamicLinkClient.dll"/>
<binaryImage start="0x0a350000" end="0x0a36c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\DVDStructures.dll"/>
<binaryImage start="0x0a380000" end="0x0a4af000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitlerCreator.dll"/>
<binaryImage start="0x0a4c0000" end="0x0a6a7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleLayer.dll"/>
<binaryImage start="0x0a6c0000" end="0x0a716000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitlerUI.dll"/>
<binaryImage start="0x0a730000" end="0x0a739000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleOSUtils.dll"/>
<binaryImage start="0x0a750000" end="0x0aa3a000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleLayout.dll"/>
<binaryImage start="0x0aa50000" end="0x0aaeb000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleCharacterFactory.dll"/>
<binaryImage start="0x0ab00000" end="0x0abd9000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleCG.dll"/>
<binaryImage start="0x0abf0000" end="0x0ac33000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AudioFilters.dll"/>
<binaryImage start="0x0ac50000" end="0x0ac62000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ProjectConverterHost.dll"/>
<binaryImage start="0x0ac80000" end="0x0acd1000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ContentAnalysisHost.dll"/>
<binaryImage start="0x0acf0000" end="0x0ad7c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Descriptors.dll"/>
<binaryImage start="0x0ad90000" end="0x0adaf000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\IPLibrary.dll"/>
<binaryImage start="0x0adb0000" end="0x0aee0000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerCapture.dll"/>
<binaryImage start="0x0aef0000" end="0x0b138000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerTimeline.dll"/>
<binaryImage start="0x0b150000" end="0x0b189000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerAudioNarration.dll"/>
<binaryImage start="0x0b1a0000" end="0x0b29f000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerAudioMixer.dll"/>
<binaryImage start="0x0b2b0000" end="0x0b340000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerDVDLayout.dll"/>
<binaryImage start="0x0b350000" end="0x0b4cf000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerMonitor.dll"/>
<binaryImage start="0x0b4e0000" end="0x0b526000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\PresetManager.dll"/>
<binaryImage start="0x0b540000" end="0x0b68e000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerOrganizer.dll"/>
<binaryImage start="0x0b6a0000" end="0x0b722000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ScCore.dll"/>
<binaryImage start="0x0b740000" end="0x0b7e3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ExtendScript.dll"/>
<binaryImage start="0x0b800000" end="0x0b830000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerHistory.dll"/>
<binaryImage start="0x0b840000" end="0x0b86d000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerInfo.dll"/>
<binaryImage start="0x0b880000" end="0x0b89e000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerEvents.dll"/>
<binaryImage start="0x0b8b0000" end="0x0b8e1000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerSharingCenter.dll"/>
<binaryImage start="0x0b900000" end="0x0b983000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\SCCommon.dll"/>
<binaryImage start="0x0b9a0000" end="0x0bcc0000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerEffectControls.dll"/>
<binaryImage start="0x0bcd0000" end="0x0bd36000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerMovieTheme.dll"/>
<binaryImage start="0x0bd50000" end="0x0c0b6000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerProject.dll"/>
<binaryImage start="0x0c0d0000" end="0x0c0f3000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\HandlerGetProperties.dll"/>
<binaryImage start="0x0c3d0000" end="0x0c3e1000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\TitlerUI.en_US.DLL"/>
<binaryImage start="0x0c490000" end="0x0c7e7000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\Mezzanine.en_US.DLL"/>
<binaryImage start="0x0c410000" end="0x0c448000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\HSL.en_US.DLL"/>
<binaryImage start="0x0c7f0000" end="0x0c864000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Localeresources\en_US\Premiere.en_US.DLL"/>
<binaryImage start="0x0ffd0000" end="0x0fff8000" type="__TEXT" path="C:\WINDOWS\system32\rsaenh.dll"/>
<binaryImage start="0x769c0000" end="0x76a73000" type="__TEXT" path="C:\WINDOWS\system32\userenv.dll"/>
<binaryImage start="0x0cc70000" end="0x0ccdf000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleFontEngine.dll"/>
<binaryImage start="0x0cce0000" end="0x0ccf2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\BravoInitializer.dll"/>
<binaryImage start="0x0cd10000" end="0x0ce01000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ACE.dll"/>
<binaryImage start="0x0ce20000" end="0x0d1b1000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\AGM.dll"/>
<binaryImage start="0x0d1d0000" end="0x0d47e000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\CoolType.dll"/>
<binaryImage start="0x0e090000" end="0x0e0b2000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\TitleImageManager.dll"/>
<binaryImage start="0x0f120000" end="0x0f12c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ObjectTracking.dll"/>
<binaryImage start="0x0f140000" end="0x0f15b000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\Plug-ins\Common\AsioWdm.dll"/>
<binaryImage start="0x76c30000" end="0x76c5e000" type="__TEXT" path="C:\WINDOWS\system32\wintrust.dll"/>
<binaryImage start="0x76c90000" end="0x76cb8000" type="__TEXT" path="C:\WINDOWS\system32\imagehlp.dll"/>
<binaryImage start="0x72d20000" end="0x72d29000" type="__TEXT" path="C:\WINDOWS\system32\wdmaud.drv"/>
<binaryImage start="0x72d10000" end="0x72d18000" type="__TEXT" path="C:\WINDOWS\system32\msacm32.drv"/>
<binaryImage start="0x77bd0000" end="0x77bd7000" type="__TEXT" path="C:\WINDOWS\system32\midimap.dll"/>
<binaryImage start="0x73ee0000" end="0x73ee4000" type="__TEXT" path="C:\WINDOWS\system32\ksuser.dll"/>
<binaryImage start="0x66800000" end="0x673ab000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTime.qts"/>
<binaryImage start="0x68a40000" end="0x68a6e000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QTCF.dll"/>
<binaryImage start="0x0f3f0000" end="0x0f4ba000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\CoreFoundation.dll"/>
<binaryImage start="0x0f4d0000" end="0x0f4e0000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\pthreadVC2.dll"/>
<binaryImage start="0x71ad0000" end="0x71ad9000" type="__TEXT" path="C:\WINDOWS\system32\wsock32.dll"/>
<binaryImage start="0x0f4e0000" end="0x0f4fc000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\objc.dll"/>
<binaryImage start="0x0f6c0000" end="0x0f7bd000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\icuin40.dll"/>
<binaryImage start="0x0f7c0000" end="0x0f8a1000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\icuuc40.dll"/>
<binaryImage start="0x4ad00000" end="0x4ba5b000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\icudt40.dll"/>
<binaryImage start="0x0f530000" end="0x0f53d000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\ASL.dll"/>
<binaryImage start="0x0f8b0000" end="0x0f943000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\CFNetwork.dll"/>
<binaryImage start="0x0f960000" end="0x0f9c3000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\SQLite3.dll"/>
<binaryImage start="0x0f9e0000" end="0x0f9f3000" type="__TEXT" path="C:\Program Files\Common Files\Apple\Apple Application Support\zlib1.dll"/>
<binaryImage start="0x76d60000" end="0x76d79000" type="__TEXT" path="C:\WINDOWS\system32\iphlpapi.dll"/>
<binaryImage start="0x687e0000" end="0x6883a000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\CoreVideo.qtx"/>
<binaryImage start="0x67e40000" end="0x67e9a000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTime3GPP.qtx"/>
<binaryImage start="0x67ea0000" end="0x67f1e000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTime3GPPAuthoring.qtx"/>
<binaryImage start="0x68460000" end="0x687d4000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeAudioSupport.qtx"/>
<binaryImage start="0x67780000" end="0x679ae000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeAuthoring.qtx"/>
<binaryImage start="0x679b0000" end="0x67a03000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeCapture.qtx"/>
<binaryImage start="0x67a10000" end="0x67aa1000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeEffects.qtx"/>
<binaryImage start="0x67cd0000" end="0x67d35000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeEssentials.qtx"/>
<binaryImage start="0x680e0000" end="0x6845b000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeH264.qtx"/>
<binaryImage start="0x67ac0000" end="0x67bb5000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeImage.qtx"/>
<binaryImage start="0x676b0000" end="0x67780000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeInternetExtras.qtx"/>
<binaryImage start="0x67c50000" end="0x67cc9000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeMPEG.qtx"/>
<binaryImage start="0x67d40000" end="0x67d9a000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeMPEG4.qtx"/>
<binaryImage start="0x67da0000" end="0x67e32000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeMPEG4Authoring.qtx"/>
<binaryImage start="0x67bc0000" end="0x67c42000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeMusic.qtx"/>
<binaryImage start="0x673b0000" end="0x6748b000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeStreaming.qtx"/>
<binaryImage start="0x68050000" end="0x680ab000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeStreamingAuthoring.qtx"/>
<binaryImage start="0x680b0000" end="0x680dd000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeStreamingExtras.qtx"/>
<binaryImage start="0x674e0000" end="0x675bb000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\QuickTimeVR.qtx"/>
<binaryImage start="0x58420000" end="0x58427000" type="__TEXT" path="C:\WINDOWS\system32\imaadp32.acm"/>
<binaryImage start="0x72cf0000" end="0x72cf7000" type="__TEXT" path="C:\WINDOWS\system32\msadp32.acm"/>
<binaryImage start="0x58330000" end="0x58335000" type="__TEXT" path="C:\WINDOWS\system32\msg711.acm"/>
<binaryImage start="0x58300000" end="0x58308000" type="__TEXT" path="C:\WINDOWS\system32\msgsm32.acm"/>
<binaryImage start="0x582d0000" end="0x582d4000" type="__TEXT" path="C:\WINDOWS\system32\tssoft32.acm"/>
<binaryImage start="0x73b70000" end="0x73b77000" type="__TEXT" path="C:\WINDOWS\system32\tsd32.dll"/>
<binaryImage start="0x58310000" end="0x5832d000" type="__TEXT" path="C:\WINDOWS\system32\msg723.acm"/>
<binaryImage start="0x58340000" end="0x5838a000" type="__TEXT" path="C:\WINDOWS\system32\msaud32.acm"/>
<binaryImage start="0x582e0000" end="0x582fe000" type="__TEXT" path="C:\WINDOWS\system32\sl_anet.acm"/>
<binaryImage start="0x581a0000" end="0x581d9000" type="__TEXT" path="C:\WINDOWS\system32\iac25_32.ax"/>
<binaryImage start="0x58390000" end="0x5841a000" type="__TEXT" path="C:\WINDOWS\system32\l3codeca.acm"/>
<binaryImage start="0x76fd0000" end="0x7704f000" type="__TEXT" path="C:\WINDOWS\system32\clbcatq.dll"/>
<binaryImage start="0x77050000" end="0x77115000" type="__TEXT" path="C:\WINDOWS\system32\comres.dll"/>
<binaryImage start="0x74980000" end="0x74a94000" type="__TEXT" path="C:\WINDOWS\system32\msxml3.dll"/>
<binaryImage start="0x15ff0000" end="0x16081000" type="__TEXT" path="C:\Program Files\QuickTime\QTSystem\AppleProResDecoder.qtx"/>
<binaryImage start="0x736b0000" end="0x736b7000" type="__TEXT" path="C:\WINDOWS\system32\msdmo.dll"/>
<binaryImage start="0x74810000" end="0x7497d000" type="__TEXT" path="C:\WINDOWS\system32\quartz.dll"/>
<binaryImage start="0x74ef0000" end="0x74ef8000" type="__TEXT" path="C:\WINDOWS\system32\wbem\wbemprox.dll"/>
<binaryImage start="0x75290000" end="0x752c7000" type="__TEXT" path="C:\WINDOWS\system32\wbem\wbemcomn.dll"/>
<binaryImage start="0x20000000" end="0x202c5000" type="__TEXT" path="C:\WINDOWS\system32\xpsp2res.dll"/>
<binaryImage start="0x74ed0000" end="0x74ede000" type="__TEXT" path="C:\WINDOWS\system32\wbem\wbemsvc.dll"/>
<binaryImage start="0x75690000" end="0x75706000" type="__TEXT" path="C:\WINDOWS\system32\wbem\fastprox.dll"/>
<binaryImage start="0x767a0000" end="0x767b3000" type="__TEXT" path="C:\WINDOWS\system32\ntdsapi.dll"/>
<binaryImage start="0x76f20000" end="0x76f47000" type="__TEXT" path="C:\WINDOWS\system32\dnsapi.dll"/>
<binaryImage start="0x174b0000" end="0x1754c000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\MediaIO\codecs\aacaudio.vca"/>
<binaryImage start="0x4f180000" end="0x4f22c000" type="__TEXT" path="C:\WINDOWS\system32\wmadmoe.dll"/>
<binaryImage start="0x17b30000" end="0x17c14000" type="__TEXT" path="C:\WINDOWS\system32\wmspdmoe.dll"/>
<binaryImage start="0x75cf0000" end="0x75d81000" type="__TEXT" path="C:\WINDOWS\system32\mlang.dll"/>
<binaryImage start="0x184f0000" end="0x18602000" type="__TEXT" path="C:\Program Files\Adobe\Adobe Premiere Elements 8.0\ad2h264vout.001"/>
<binaryImage start="0x4c250000" end="0x4c38b000" type="__TEXT" path="C:\WINDOWS\system32\wmvdmoe2.dll"/>
<binaryImage start="0x59090000" end="0x590ae000" type="__TEXT" path="C:\WINDOWS\system32\wmsdmoe.dll"/>
<binaryImage start="0x4ea30000" end="0x4eb87000" type="__TEXT" path="C:\WINDOWS\system32\wmsdmoe2.dll"/>
</binaryImageSet>
</crash>
<reproSteps>
</reproSteps>
</crashreport>Hello,
I have the exact same problem as you with PE8 and Win7 (x64), and a reboot also helped me. But the problem came back the next time I tried to open PE. Have you expreienced the same? It cant be that we have to reboot every time we want to use PE?
Best regards
Øystein Morvik
Norway -
RE: Processing Logged messages in batch mode ?
Paul,
One way to findout the log file is to inspect your
<CentralServer>.log. It should have a line something like..
Redirecting output to <someDirectory>/forte_ex_26564.log.
That is the file the the current ftexec is writing to.
This has worked fine for me.
Another way is to sort the files by date, and look at the latest
ones.
...I'd love to hear about a better way to do this.
Ajith Kallambella. M
Forte Systems Engineer
International Business Corporation.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, March 01, 1999 9:06 AM
To: Forte-Users (Adresse de messagerie)
Subject: Processing Logged messages in batch mode ?
Hi,
When I launch partitions, they display a whole bunch of 'useful' messages.
(maybe using 'task.logmgr.putline')
I'm afraid these traces go directly in the launcher's log file under
$FORTE_ROOT/log
As I get control only when the ftexec ends for the next instruction to be
interpreted,
how can I figure out which of these log files relates to the ftexec I just
got executed ?
(example: "forte_ex_3613.log")
I found '/output' for node managers, but for single ftexec(s) ?
(thinking also about re-used ftexec(s))
Thanks in advance,
j-paul gabrielli
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>Paul,
One way to findout the log file is to inspect your
<CentralServer>.log. It should have a line something like..
Redirecting output to <someDirectory>/forte_ex_26564.log.
That is the file the the current ftexec is writing to.
This has worked fine for me.
Another way is to sort the files by date, and look at the latest
ones.
...I'd love to hear about a better way to do this.
Ajith Kallambella. M
Forte Systems Engineer
International Business Corporation.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, March 01, 1999 9:06 AM
To: Forte-Users (Adresse de messagerie)
Subject: Processing Logged messages in batch mode ?
Hi,
When I launch partitions, they display a whole bunch of 'useful' messages.
(maybe using 'task.logmgr.putline')
I'm afraid these traces go directly in the launcher's log file under
$FORTE_ROOT/log
As I get control only when the ftexec ends for the next instruction to be
interpreted,
how can I figure out which of these log files relates to the ftexec I just
got executed ?
(example: "forte_ex_3613.log")
I found '/output' for node managers, but for single ftexec(s) ?
(thinking also about re-used ftexec(s))
Thanks in advance,
j-paul gabrielli
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/> -
FW: Processing Logged messages in batch mode ?
If you rename your partitions' log files before running the app and do the
renaming according to each partitions' purpose or partition number, then
after running the app, just go to the approprate log file. You can do the
renaming using system agents so that it is not a manual process.
Essentially, you know in advance where the output goes.
-Ravi
-----Original Message-----
From: J-Paul GABRIELLI [SMTP:[email protected]]
Sent: Monday, March 01, 1999 11:29 AM
To: 'Kalidindi, Ravi CWT-MSP'
Subject: RE: Processing Logged messages in batch mode ?
Sorry, I was looking for a batch way, when the partition is dead (i.E.
can't monitor it nor view it in escript)
No gui :-)
j-p
-----Message d'origine-----
De: Kalidindi, Ravi CWT-MSP [SMTP:[email protected]]
Date: lundi 1 mars 1999 17:51
A: 'Kallambella, Ajith'; 'J-Paul GABRIELLI'; 'Forte'
Objet: RE: Processing Logged messages in batch mode ?
In case of installed applications or running in distributed mode, you can
use econsole to choose the appropriate active partition and view the log
file for it. The "log file" window also displays the name of the
particular
log file. In case of installed applications, you can also rename the log
file for your partitions.
Hope that helps
-Ravi Kalidindi
Born Info Svcs Group
-----Original Message-----
From: Kallambella, Ajith [SMTP:[email protected]]
Sent: Monday, March 01, 1999 9:47 AM
To: 'J-Paul GABRIELLI'; 'Forte'
Subject: RE: Processing Logged messages in batch mode ?
Paul,
One way to findout the log file is to inspect your
<CentralServer>.log. It should have a line something like..
Redirecting output to <someDirectory>/forte_ex_26564.log.
That is the file the the current ftexec is writing to.
This has worked fine for me.
Another way is to sort the files by date, and look at the latest
ones.
...I'd love to hear about a better way to do this.
Ajith Kallambella. M
Forte Systems Engineer
International Business Corporation.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, March 01, 1999 9:06 AM
To: Forte-Users (Adresse de messagerie)
Subject: Processing Logged messages in batch mode ?
Hi,
When I launch partitions, they display a whole bunch of 'useful'messages.
(maybe using 'task.logmgr.putline')
I'm afraid these traces go directly in the launcher's log file under
$FORTE_ROOT/log
As I get control only when the ftexec ends for the next instruction tobe
interpreted,
how can I figure out which of these log files relates to the ftexec Ijust
got executed ?
(example: "forte_ex_3613.log")
I found '/output' for node managers, but for single ftexec(s) ?
(thinking also about re-used ftexec(s))
Thanks in advance,
j-paul gabrielli
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>If you rename your partitions' log files before running the app and do the
renaming according to each partitions' purpose or partition number, then
after running the app, just go to the approprate log file. You can do the
renaming using system agents so that it is not a manual process.
Essentially, you know in advance where the output goes.
-Ravi
-----Original Message-----
From: J-Paul GABRIELLI [SMTP:[email protected]]
Sent: Monday, March 01, 1999 11:29 AM
To: 'Kalidindi, Ravi CWT-MSP'
Subject: RE: Processing Logged messages in batch mode ?
Sorry, I was looking for a batch way, when the partition is dead (i.E.
can't monitor it nor view it in escript)
No gui :-)
j-p
-----Message d'origine-----
De: Kalidindi, Ravi CWT-MSP [SMTP:[email protected]]
Date: lundi 1 mars 1999 17:51
A: 'Kallambella, Ajith'; 'J-Paul GABRIELLI'; 'Forte'
Objet: RE: Processing Logged messages in batch mode ?
In case of installed applications or running in distributed mode, you can
use econsole to choose the appropriate active partition and view the log
file for it. The "log file" window also displays the name of the
particular
log file. In case of installed applications, you can also rename the log
file for your partitions.
Hope that helps
-Ravi Kalidindi
Born Info Svcs Group
-----Original Message-----
From: Kallambella, Ajith [SMTP:[email protected]]
Sent: Monday, March 01, 1999 9:47 AM
To: 'J-Paul GABRIELLI'; 'Forte'
Subject: RE: Processing Logged messages in batch mode ?
Paul,
One way to findout the log file is to inspect your
<CentralServer>.log. It should have a line something like..
Redirecting output to <someDirectory>/forte_ex_26564.log.
That is the file the the current ftexec is writing to.
This has worked fine for me.
Another way is to sort the files by date, and look at the latest
ones.
...I'd love to hear about a better way to do this.
Ajith Kallambella. M
Forte Systems Engineer
International Business Corporation.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, March 01, 1999 9:06 AM
To: Forte-Users (Adresse de messagerie)
Subject: Processing Logged messages in batch mode ?
Hi,
When I launch partitions, they display a whole bunch of 'useful'messages.
(maybe using 'task.logmgr.putline')
I'm afraid these traces go directly in the launcher's log file under
$FORTE_ROOT/log
As I get control only when the ftexec ends for the next instruction tobe
interpreted,
how can I figure out which of these log files relates to the ftexec Ijust
got executed ?
(example: "forte_ex_3613.log")
I found '/output' for node managers, but for single ftexec(s) ?
(thinking also about re-used ftexec(s))
Thanks in advance,
j-paul gabrielli
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/> -
Processing Logged messages in batch mode ?
Hi,
When I launch partitions, they display a whole bunch of 'useful' messages.
(maybe using 'task.logmgr.putline')
I'm afraid these traces go directly in the launcher's log file under $FORTE_ROOT/log
As I get control only when the ftexec ends for the next instruction to be interpreted,
how can I figure out which of these log files relates to the ftexec I just got executed ?
(example: "forte_ex_3613.log")
I found '/output' for node managers, but for single ftexec(s) ?
(thinking also about re-used ftexec(s))
Thanks in advance,
j-paul gabrielliThe instrument "LogFile" on the active partition agent contains the name of
the log file.
At 10:47 AM 3/1/99 -0500, Kallambella, Ajith wrote:
Paul,
One way to findout the log file is to inspect your
<CentralServer>.log. It should have a line something like..
Redirecting output to <someDirectory>/forte_ex_26564.log.
That is the file the the current ftexec is writing to.
This has worked fine for me.
Another way is to sort the files by date, and look at the latest
ones.
...I'd love to hear about a better way to do this.
Ajith Kallambella. M
Forte Systems Engineer
International Business Corporation.
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, March 01, 1999 9:06 AM
To: Forte-Users (Adresse de messagerie)
Subject: Processing Logged messages in batch mode ?
Hi,
When I launch partitions, they display a whole bunch of 'useful' messages.
(maybe using 'task.logmgr.putline')
I'm afraid these traces go directly in the launcher's log file under
$FORTE_ROOT/log
As I get control only when the ftexec ends for the next instruction to be
interpreted,
how can I figure out which of these log files relates to the ftexec I just
got executed ?
(example: "forte_ex_3613.log")
I found '/output' for node managers, but for single ftexec(s) ?
(thinking also about re-used ftexec(s))
Thanks in advance,
j-paul gabrielli
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>============================================
Don Nelson
Senior Systems Architect
Forte Software, Inc.
Denver, CO
Phone: 303-265-7709
Corporate voice mail: 510-986-3810
aka: [email protected]
============================================
"Nothing spoils fun like finding out it builds character." - Calvin
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
Maybe you are looking for
-
I'm trying to download Acrobat XI free trial to my MacBook Pro. First step is to accept the terms of use. But it will only let me scroll part of the way down. It stops me at 24.9, so I can't get to the box to check to indicate I accept the terms of u
-
I have restored my ipod nano 6th generation and am being told it is now in recovery mode so needs to be restored which is what i have just done. I can't get any further than this. Please help.
-
Hello Gurus, I am working on ECC 5.0 R/3 systems. Now my company wants BW system. I want to know Whether BW is already in R/3 system or We have to install Netweaver Server and then add BW component. In short want to know how to install and configure
-
Storing ItemCode,Vendor Name,Vendor Code in Database
Hi All, i have created UDO in user defined form, in the form all the fields are stored in database except ItemCode,Vendor Name,Vendor Code. i want to know how to store these values. please help me, it's very urjent. Jayanth
-
Event handling for radiobuttonGroup in HTML
Hi All, In HTML , for a group of radio buttons we need to give the same name to each button so that all other RBs are deselected if , one is selected , but for triggering a server side event from an element using HTML , in BSP application we have to