Re: EMC problems



Ray and Fred Z,

If Fred manages to get into a shell then he can issue the command
"script" (without quotes) and all input and output in the shell's window
will be saved in a file named "typescript" (again without the quotes).
After he's done running EMC he can enter the command "exit" and a
history of the complete session should be in typescript. Emailing
the complete file may be better than trying to paste pieces of it
together.

Drew

Ray wrote:
> 
> Fred Z
> 
> We have found a couple downloads where the copy was not the same as the
> ftp site file.  Henkka at yty.net has a brief description of a program
> called checksum and a good checksum value to test your download against.
> I really think that this is an essential task for a file this big.
> 
> (comments in)
> 
> On Friday 30 November 2001 02:24 am, Fred Z wrote:
> > Thank you very much for that information, I will try that on monday when
> > I return to the site.
> >
> > I should state at this point that I am extremely greatfull to those who
> > have contributed there suggestions to my problems, they have all helped
> > in one way or another.
> 
> This help is why we hang around here.  We need it also!
> 
> > Can I assume from your statement that when I run the EMC_Run from the
> > icon, it uses the EMC.INI, and when I run the EMC_Generic from the icon,
> > it uses the GENERIC.INI files and so on ???
> 
> Yep!  Usually but read on.
> 
> > Being involved with the virus(Windows), I tend to just use icons and not
> > command lines.
> 
> Point and click is a common affliction.  Command lines do not take much
> more effort at the level we need you to use them.
> 
> Click on the little house icon on the bottom bar or panel.  It will bring
> up an instance of kfm, the file manager.  I assume that you are running as
> root and you will be in the /root directory.   You can always see where
> you are in the file window.  Press the up arrow near the top bar of kfm
> and it will move you to /.  Now click on the usr directory icon then the
> emc directory icon.  Now you will display the correct directory for
> running the emc. It should show you a bunch of files like TkEemc and such.
> Hey, that's not so different.
> 
> Clicking on a text based file icon should show its contents in a window.
> Right clicking on a terminal or executable file and selecting open with
> should let you look at those as well.  Sometimes clicking on an unknown
> file type will get you an open with window much like you see in MS
> windows.  At that point you can always type kwrite and it will show you
> the file, even if it is a binary.
> 
> A file named *.run, where the star has the usual definition of any or all,
> is a start the emc file.  It one of these files about line 27 should be a
> variable which points that run file at an .ini file.  It will say
> something like
> 
> INIFILE=ppmc.ini
> 
> except the file pointed to is the name of your ini file.  Perhaps it will
> be emc.ini.  This information is critical because that is the specific
> .ini file that you will need to edit to work with that .run file.  I've
> made this mistake before, changing one ini while running another.  I kept
> wondering why my changes weren't doing anything.
> 
> Now let's take one more little step away from the icons to running from a
> terminal because that way you can view the startup feedback and some of
> the run stuff.  The Kfm window that you got to this directory with needs
> to have the focus.  Kfm is the file browser and focus means that the top
> line is a different color than the background.  (Click on the top line to
> change focus to that window)  Now press and hold  <control> and press t on
> the keyboard.  This opens a new terminal so that you can enter text
> commands.  This keystroke, <control>t , opens that terminal in the
> directory shown in the kfm window.  This means that you should be ready to
> go to work entering text.
> 
> In the terminal window you will see something like
> 
> [ray-at-localhost emc]$
> 
> The $ means that it is ready to accept a command.  the emc] just before it
> is the name of the directory the terminal is working in.  Type in
> ./emc.run (dot slash) and it should immediately say something like file
> not found.  This is a good thing if it goes on with other stuff. It is
> this other stuff that will allow you to begin to debug your setup.
> 
> With the mouse, you can click and drag across the lines of the terminal
> window to highlight what you want.  But you can't press <control>c to
> capture them.  Just leave them highlighted and start kwrite, advanced
> editor, or text editor from the k menu in the bottom left corner and
> select copy from the menu or press <control>v in the editor and you should
> have a copy of the highlighted text from the terminal.  Copy that into
> your favorite email program and we can comment on what we see there.
> 
> Hope this helps.
> 
> Ray
> 

-- 
Drew Rogge
drew-at-pixar.com



Date Index | Thread Index | Back to archive index | Back to Mailing List Page

Problems or questions? Contact