• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 1349 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Motorware, Instaspin, Controlsuite installation issues Light on Linux HEAVY on WINDOWS!!!

Roberto Romano
Guru 27285 points

Other Parts Discussed in Thread: CONTROLSUITE, MOTORWARE

 Hi, After a lot of time wasted trying to install suite I hit one main trouble:

 Linux Wine:

I can install to anywhere and no trouble come from installation but all suite and TI software must be on same drive :((((

 When I try run suite if all is not on same drive it fails due it search and assume all installation are on same Drive.... Again this is HARDWIRED to root including DRIVE: bad habit in root handling. Why not use a good path relative to installation path "DRIVELESS"??? I think leaving this away from professional help produce a better code.

 Issue come from lack of space on main HDD and desire to share (SAME) code and file system-wide and on networked space too avoiding multiple duplicates of same installation.. This is limited by this hardwiring of base drive usually from path root but too often just c:\.

 Windows XP, MORE (descendant too) worst  trouble, too many piece of suite insist on "C:/" hardwired search, CCS too and this slow down a lot system nor permit to mount an external "share" and install on it nor have part of code on different data drive.

 CCS winzz due to this problem doesn't work if project and CCS reside in a different drive also on local machine.

 So I created another partition and added Win mounted to "C:\TI", this work for storage but not on installation, for some way installation if not on same C:\ drive report user don't have access right to write folder, user has Administrator right and I observed every folder has Read Only mark permanently set...

 Again DAMN Windoze forever, this ISSUE is behaviour by design!!! What worst than a M$ product???? So you never can clear this fake Read only, but why a clean not protected file nor Folder open to everyone to write (Very worst security issue to do that) so installation report forever error?? After a google search I discovered this flag M$ use not as you intend reading but to have flagged folder is "customized!!!" Again useless messages disk full when printer was paper empty!!

 BLAME M$ but please address this worst situation on your side.

http://support.microsoft.com/kb/326549

 Last, C2000 is well supported from CCS in Linux, GUIComposer is also Linux Hosted so why not also produce pure linux executable than .EXE that refuse run still in native W$?

 I found just Modem Example with native Linux and none other package, it is so hard generate code for both platform?

 How much time wasted us by M$.... and everyone still insist use this worst expensive thrash...

 ERROR LOG:  

Fullscreen GUICError.log Download 
Error in action ExecuteAction

Error in action UnzipFile

can't create directory "C:/ti/guicomposer": read-only file system
    while executing
"file mkdir $dir"
    (procedure "::InstallJammer::CreateDir" line 13)
    invoked from within
"::InstallJammer::CreateDir $dir"
    (procedure "::InstallJammer::actions::UnzipFile" line 50)
    invoked from within
"::InstallJammer::actions::$component $this"
    while executing
"$obj execute"
    (procedure "::InstallJammer::ExecuteActions" line 69)
    invoked from within
"::InstallJammer::ExecuteActions $action -parent $id -conditions $eval"
    (procedure "::InstallJammer::actions::ExecuteAction" line 35)
    invoked from within
"::InstallJammer::actions::$component $this"
Error in action ExecuteAction

Error in action UnzipFile

can't create directory "C:/ti/guicomposer": read-only file system
    while executing
"file mkdir $dir"
    (procedure "::InstallJammer::CreateDir" line 13)
    invoked from within
"::InstallJammer::CreateDir $dir"
    (procedure "::InstallJammer::actions::UnzipFile" line 50)
    invoked from within
"::InstallJammer::actions::$component $this"
    while executing
"$obj execute"
    (procedure "::InstallJammer::ExecuteActions" line 69)
    invoked from within
"::InstallJammer::ExecuteActions $action -parent $id -conditions $eval"
    (procedure "::InstallJammer::actions::ExecuteAction" line 35)
    invoked from within
"::InstallJammer::actions::$component $this"
    while executing
"$obj execute"
    (procedure "::InstallJammer::ExecuteActions" line 69)
    invoked from within
"::InstallJammer::ExecuteActions $id -when $when"
    (procedure "::InstallJammer::RaiseEventHandler" line 93)
    invoked from within
"::InstallJammer::RaiseEventHandler  .wizard"
    (command bound to event)

  • 0
    TI__Guru**** 163035 points

    Roberto Romano said:
     When I try run suite if all is not on same drive it fails due it search and assume all installation are on same Drive.... Again this is HARDWIRED to root including DRIVE: bad habit in root handling. Why not use a good path relative to installation path "DRIVELESS"??? I think leaving this away from professional help produce a better code.

    Roberto for issues with controlSUITE or MotorWare you will get better responses in the C2000 and Hercules forums.  As part of the installation of these packages they add an entry in a folder in the user directory that helps CCS to find where they were installed.  CCS should not care where they are installed as this breadcrumb file will let it know where they are.  Unfortunately for a number of our software packages installers for windows are all that is available so you end up having to copy the package from an windows machine and then CCS will not have the breadcrumb file to use to find the packages so that they can be displayed in Resource Explorer.  I agree that not having Linux installation packages for these packages is a gap in our software offering.

    Roberto Romano said:
    CCS winzz due to this problem doesn't work if project and CCS reside in a different drive also on local machine.

    CCS shouldn't care if the project and installation are on different drives.  This is pretty common as lots of people using version control have the repository as a mapped drive letter.  What issues are you running into with CCS?

  • 0 in reply to JohnS
    Guru 27285 points

    JohnS said:
    CCS shouldn't care if the project and installation are on different drives.  This is pretty common as lots of people using version control have the repository as a mapped drive letter.  What issues are you running into with CCS?

     Hi Johns, sorry for long delay, it is difficult for me follow all forum from new interface.

     The worst I got was the forever message of read only file access, all right where available to files so I can read write delete rename and so on, but they appear forever read only on property.

     Reading about read only I found this flag from property mean folder is customized so fooled someone it is read only than what is by "feature!". So forever installation report no right to write or similar error when disk is readable to anyone too.

     Installing windows software too many time fails for unknown reason, the one of "customized follder" reported as read only is one of them, and installation can be incomplete or broken too.

     About control suite and motorware error are CCS related due to client server failure, so I hope all can be addressed with remote debug session with Patrick.

     About script not copying project session are some news?

     Thank you very much all great assistance provided.