[M3devel] Ticket #1082

[Coleburn, Randy]

I have updated the comments on Ticket #1082

There are two postings, as shown below.

Note that it looks like there is a problem with "START /WAIT ..." command differences between Windows versions, so we may need to open up a new Trac ticket for this issue (see comment #2 below).

FIRST COMMENT:
---------------------

The "startReactor.CMD" file is obsolete and no longer in the repository.

The new files are in "scripts\install\windows" and should be copied to the "cm3\bin" folder on a windows installation.

"cm3StartIDE.CMD" replaces "startReactor.CMD". This file makes use of "cm3CommandShell.CMD", a script that ensures the environment is set up properly, including Visual C++.

It appears that the problem reporter has his installation rooted at E:\cm3 rather than C:\cm3. So, he will need to set an environment variable "set CM3_ROOT=E:\cm3" to let these scripts know where to find the cm3 installation.

Alternately, cm3CommandShell can be invoked with the arguments "Root E:\cm3" to tell it where to find the installation.

Today, I checked in an update to cm3CommandShell.CMD that allows it to search the current PATH environment variable in an attempt to find the root of the cm3 installation, so now if "E:\cm3\bin" is in your path, it will find it without having to set the CM3_ROOT or invoking with "Root E:\cm3". Hope this helps!

Note also that strictly speaking, these CMD files are not necessary; rather they are conveniences I've found useful under Windows. I also can supply some .REG files that will allow you to integrate these into the Explorer shell so that you can start a cm3 command shell in any folder and you can start CM3IDE.

SECOND COMMENT:
---------------------

Ok as for CM3IDE timing out, I've been able to reproduce this problem on Vista.

There seems to be some difference I don't understand yet between the way the various Windows versions deal with the "START /WAIT ..." command.

Here is a "quick fix" until we come up with a better solution. Note that the downside here is that when you terminate your browser, CM3IDE will stay running, instead of terminating. You can restart your browser and point it back to the  http://localhost:3800/<http://localhost:3800/> URL and verify that it reconnects to CM3IDE. So, to terminate CM3IDE, you will have to use CTRL-C from its console output window.

Now for the quick fix:

1. Go to your CM3_IDE_HOME folder (e.g., C:\Users\RColeburn\Documents\CM3_IDE_Home).

2. Open the most recent CM3_IDE.cfg file in notepad (e.g., notepad CM3_IDE.cfg1).

3. Edit the line toward the end of the file that begins with "proc start_browser". On this line change TRUE to FALSE. Note that case is significant.

Now try cm3IDE.exe, or cm3_StartIDE.CMD. It should work for you now as described above.

Regards,
Randy Coleburn


________________________________
CONFIDENTIALITY NOTICE: This email and any attachments are intended solely for the use of the named recipient(s). This email may contain confidential and/or proprietary information of Scientific Research Corporation. If you are not a named recipient, you are prohibited from reviewing, copying, using, disclosing or distributing to others the information in this email and attachments. If you believe you have received this email in error, please notify the sender immediately and permanently delete the email, any attachments, and all copies thereof from any drives or storage media and destroy any printouts of the email or attachments.

EXPORT COMPLIANCE NOTICE: This email and any attachments may contain technical data subject to U.S export restrictions under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR). Export or transfer of this technical data and/or related information to any foreign person(s) or entity(ies), either within the U.S. or outside of the U.S., may require advance export authorization by the appropriate U.S. Government agency prior to export or transfer. In addition, technical data may not be exported or transferred to certain countries or specified designated nationals identified by U.S. embargo controls without prior export authorization. By accepting this email and any attachments, all recipients confirm that they understand and will comply with all applicable ITAR, EAR and embargo compliance requirements.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100311/18eab30a/attachment-0001.html>