LaTeX2rtf not running
anon k
Cannot execute C:\PROGRA~1\LATEX2RTF\LATEX2RT.EXE
latex2rt.exe is definitely there, and if I go into that directory and
execute it from the command line, I get the same message.
There don't seem to be any log files explaining WHY this program cannot
be executed. Nor could I find anything in the sourceforge documentation
indicating that I had to configure options in advance.
Any suggestions as to what's wrong here?
Wilfried Hennings
Please cite exactly the complete error message (if there is any) and
tell us the follwing details:
Which version of latex2rtf?
Did you install the Windows version including the GUI shell or the DOS
version?
If executing from the command line: Did you just double-click on the
.exe file in Windows explorer or did you open a command prompt window?
What command (exactly) do you issue on the command line?
And it would be nice if you'd introduce yourself with your real name.
--
email me: change "nospam" to "w.hennings"
Wilfried Hennings c./o.
Forschungszentrum (Research Center) Juelich GmbH, MUT
<http://www.fz-juelich.de/mut/mut_home>
All opinions mentioned are strictly my own, not my employer's.
anon k
> anon k <nos...@nul.nul> wrote:
>
>> I just installed LaTeX2rtf on WinXP and consistently get this error message:
>>
>> Cannot execute C:\PROGRA~1\LATEX2RTF\LATEX2RT.EXE
>
That is the entire error message. It doesn't offer any clues to a
tech-illiterate humanities person like me.
> Which version of latex2rtf?
Version 1.9.16a, downloaded from Sourceforge a day or two ago.
> Did you install the Windows version including the GUI shell
Yes, it is the Windows version with the GUI shell, and is run through
double-clicking the icon for l2rshell.exe.
The program was installed to the default c:\program files\latex2rtf.
I updated the batch files so that c:\l2r is now "c:\program
files\latex2rtf\" (with quotation marks around the whole path and filename).
There is also a reference to g:\djgpp, which does not seem relevant to
my system. This is only for compilation, is that right?
The desktop icon was initially set to "start in" some directory of the
Start menu. After the first failure to run, I changed that to the
latex2rtf directory thinking that it might be the reason but it did not
help.
> What command (exactly) do you issue on the command line?
I tried running "latex2rt.exe" from the command line, within that
directory, and with no parameters, just to see if the file was in fact
there. It gave the same "cannot execute..." message but no explanation.
Louie
> Wilfried Hennings wrote:
> > anon k <nos...@nul.nul> wrote:
>
> >> I just installed LaTeX2rtf on WinXP and consistently get this error message:
>
> >> Cannot execute C:\PROGRA~1\LATEX2RTF\LATEX2RT.EXE
>
> > Please cite exactly the complete error message (if there is any)
>
> That is the entire error message. It doesn't offer any clues to a
> tech-illiterate humanities person like me.
>
I just checked the executable from that site and it works fine on this
box.
Do you mind copying the paths written on the environment tab of the
GUI? It might be that the setup process went wrong.
Luis.
anon k
Target: "C:\Program Files\latex2rtf\l2rshell.exe"
Start in: "C:\Program Files\latex2rtf"
I also tried adding an extra backslash to the 'start in' path, to no
visible advantage.
Wilfried Hennings
No, that is not the place Louie asked you to look at.
Start the shell (C:\Program Files\latex2rtf\l2rshell.exe), open the tab
"Environment" and then have a look at the pathes.
It may help to replace "C:\Program Files" by "C:\PROGRA~1" in these
strings.
But can you start this shell?
If you cannot start latex2rt.exe from the command line, your problem is
probably related to window, not to latex2rtf.
What version of Windows do you run?
Do you run a 64bit CPU? latex2rtf is compiled for 32bit and may not run
on a 64bit system.
Do you run a virus scanner which may prevent starting latex2rt.exe?
If no virus scanner but WinNT / 2000 / XP / 2003: What user rights are
assigned to the folder C:\Program Files\latex2rtf and to the files
installed in it?
anon k
> anon k <nos...@nul.nul> wrote:
>
>> Louie wrote:
>>> On Mar 28, 9:19 am, anon k <nos...@nul.nul> wrote:
>>>> Wilfried Hennings wrote:
>>>>> anon k <nos...@nul.nul> wrote:
>>>>>> I just installed LaTeX2rtf on WinXP and consistently get this error message:
>>>>>> Cannot execute C:\PROGRA~1\LATEX2RTF\LATEX2RT.EXE
>>>>> Please cite exactly the complete error message (if there is any)
>>>> That is the entire error message. It doesn't offer any clues to a
>>>> tech-illiterate humanities person like me.
>>>>
>>> I just checked the executable from that site and it works fine on this
>>> box.
>>>
>>> Do you mind copying the paths written on the environment tab of the
>>> GUI? It might be that the setup process went wrong.
>> Target: "C:\Program Files\latex2rtf\l2rshell.exe"
>> Start in: "C:\Program Files\latex2rtf"
>>
>> I also tried adding an extra backslash to the 'start in' path, to no
>> visible advantage.
>
> No, that is not the place Louie asked you to look at.
Indeed. The shell's running fine.
Configuration directory: C:\Program Files\latex2rtf\cfg
LaTeX: C:\Program Files\MiKTeX 2.5\miktex\bin\latex.exe
ImageMagick: - not installed (?) -
GhostScript: - not installed (?) -
ImageMagick and GhostScript are indeed not installed.
> If you cannot start latex2rt.exe from the command line, your problem is
> probably related to window, not to latex2rtf.
I don't know whether the error message comes from Windows or from
latex2rt when I try starting it from the command line. The error
message is simply uninformative.
> What version of Windows do you run?
XP home.
> Do you run a 64bit CPU? latex2rtf is compiled for 32bit and may not run
> on a 64bit system.
It's a Celeron of some sort inside a cheap Dell Inspiron notebook about
four years old... I would guess that it's 32-bit. The specs that I have
don't say.
> Do you run a virus scanner which may prevent starting latex2rt.exe?
The virus scanner (Symantec) doesn't stop anything else from running so
I doubt that this is the cause. It is not issuing any warnings, as it
usually does, when suspicious things happen.
> If no virus scanner but WinNT / 2000 / XP / 2003: What user rights are
> assigned to the folder C:\Program Files\latex2rtf and to the files
> installed in it?
I don't know how to tell but since this particular machine has only one
user profile, the so-called 'owner', it would seem likely that all
rights are assigned. None of the files or directories are set as 'read
only'.
Wilfried Hennings
The fact that ImageMagick and GhostScript are not installed only affects
the conversion of images and the conversion of equations to images, if
chosen. If your LaTeX file contains neither images not equations, it
doesn't matter.
However you should replace "C:\Program Files\" by "C:\PROGRA~1\" which
is the short (8.3) equivalent. The file accesses may fail if the path
contains spaces (blanks).
Same applies to the folder "MiKTeX 2.5". Open a command window and cd to
"Program Files", then do a "dir /X M*" which should display the 8.3
equivalent for the folder name "MiKTeX 2.5", and specify the short
equivalent in the environment tab of l2rshell.
Or, better, uninstall MiKTeX and reinstall it in a folder without a
space in the name, e.g. in "C:\MiKTeX2.5".
> > If you cannot start latex2rt.exe from the command line, your problem is
> > probably related to window, not to latex2rtf.
>
> I don't know whether the error message comes from Windows or from
> latex2rt when I try starting it from the command line. The error
> message is simply uninformative.
>
> > What version of Windows do you run?
>
> XP home.
OK, that eliminates the possibility of elaborated user access rights to
the files.
> > Do you run a 64bit CPU? latex2rtf is compiled for 32bit and may not run
> > on a 64bit system.
>
> It's a Celeron of some sort inside a cheap Dell Inspiron notebook about
> four years old... I would guess that it's 32-bit. The specs that I have
> don't say.
Then you probably have a 32 bit system and no problem from this side.
> > Do you run a virus scanner which may prevent starting latex2rt.exe?
>
> The virus scanner (Symantec) doesn't stop anything else from running so
> I doubt that this is the cause. It is not issuing any warnings, as it
> usually does, when suspicious things happen.
>
> > If no virus scanner but WinNT / 2000 / XP / 2003: What user rights are
> > assigned to the folder C:\Program Files\latex2rtf and to the files
> > installed in it?
>
> I don't know how to tell but since this particular machine has only one
> user profile, the so-called 'owner', it would seem likely that all
> rights are assigned. None of the files or directories are set as 'read
> only'.
User rights and "read only" are two different things. If you create a
new user in WinXP, you can give this user either full (administrative)
or limited rights. I did not yet test whether latex2rtf would run for a
user with limited rights.
But as you tell us that there is only one user profile, it is likely
that you have full rights and so the rights should not be a problem.
Can you please tell us exactly and literally what steps you do to "run
latex2rt.exe from the command line"?
Btw I will be out of office next week and unable to reply until after
easter.
anon k
I've tried this since your last suggestions, and have just tried it
again, to no avail.
Adding c:\progra~1\latex2rtf\ to the path also did not help.
> Can you please tell us exactly and literally what steps you do to "run
> latex2rt.exe from the command line"?
I opened a DOS command window and navigated down to the directory in
which latex2rt.exe is located.
Then I typed "latex2rt" at the command prompt and pressed enter just to
see what it would do. I also tried
latex2rt test
latex2rt test.tex
l2r test
l2r test.tex
In each case I get "Cannot execute C:PROGRA~1\LATEX2RTF\LATEX2RT.EXE"
returned. I don't know how to tell whether it's a DOS error message or
a latex2rtf error message. I'm leaning toward the former.
text.tex is a short text-only LaTeX file, by the way, and LaTeX has no
problems with it.
Louie
> Wilfried Hennings wrote:
> > However you should replace "C:\Program Files\" by "C:\PROGRA~1\" which
> > is the short (8.3) equivalent. The file accesses may fail if the path
>
> again, to no avail.
>
> Adding c:\progra~1\latex2rtf\ to the path also did not help.
>
Please notice this path is not 8.3 compliant. `latex2rtf' is a nine
character string. You should add
c:\progra~1\latex2~1\
or something similar, to the path to make the program run on DOS.
>
> I opened a DOS command window and navigated down to the directory in
> which latex2rt.exe is located.
>
> Then I typed "latex2rt" at the command prompt and pressed enter just to
> see what it would do. I also tried
> latex2rt test
> latex2rt test.tex
> l2r test
> l2r test.tex
>
> In each case I get "Cannot execute C:PROGRA~1\LATEX2RTF\LATEX2RT.EXE"
> returned. I don't know how to tell whether it's a DOS error message or
> a latex2rtf error message. I'm leaning toward the former.
>
You may be right.
I assume "C:PROGRA~1\LATEX2RTF\LATEX2RT.EXE" (please notice the "C:"
without backslash, and the nine character string "LATEX2RTF") to be
verbatim and not typos.
Again, try adding
C:\PROGRA~1\LATEX2~1\
(and perhaps also the path without the last backslash) to the path,
and tell me what happened...
Good luck,
Luis.
Dan
> On Mar 30, 7:56 am, anon k <nos...@nul.nul> wrote:
>
> > Wilfried Hennings wrote:
> > > However you should replace "C:\Program Files\" by "C:\PROGRA~1\" which
> > > is the short (8.3) equivalent. The file accesses may fail if the path
>
> > I've tried this since your last suggestions, and have just tried it
> > again, to no avail.
>
> > Adding c:\progra~1\latex2rtf\ to the path also did not help.
>
> Please notice this path is not 8.3 compliant. `latex2rtf' is a nine
> character string. You should add
>
> c:\progra~1\latex2~1\
>
> or something similar, to the path to make the program run on DOS.
>
Is it really necessary to use DOS? I can't even get to a DOS prompt
in WinXP without running command.com explicitly: the "Command Prompt"
menu item opens cmd.exe.
Cmd.exe has none of these shortcomings.
>
> > I opened a DOS command window and navigated down to the directory in
> > which latex2rt.exe is located.
In actual DOS (command.com), latex2rtf is an "invalid directory".
That's the
error I get when I try to cd there in a command.com shell. How does
one navigate there in the DOS window? In a cmd.exe window it is easy.
So I wonder: are we really dealing with DOS (command.com) or with
windows (cmd.exe)? If the latter, I expect a permissions problem.
On the other hand, I would prempt all these invalid path problems by
installing latex2rtf in C:\ltx2rtf instead of "C:\Program Files
\latex2rtf".
Dan
Louie
>
> Is it really necessary to use DOS? I can't even get to a DOS prompt
> in WinXP without running command.com explicitly: the "Command Prompt"
> menu item opens cmd.exe.
>
> Cmd.exe has none of these shortcomings.
>
> That's the
> error I get when I try to cd there in a command.com shell. How does
> one navigate there in the DOS window? In a cmd.exe window it is easy.
>
> installing latex2rtf in C:\ltx2rtf instead of "C:\Program Files
> \latex2rtf".
>
You're right. That's another option.
However, here we're trying to figure out why this fellow can't run his
app on the standard directory. If uninstall and reinstall doesn't do
the job, my only guess is that the binary is corrupted, and anon-k may
try to download it again, or else try another binary (maybe the native
DOS compiled binary).
Good luck, anyway!
Luis.
anon k
Tried re-downloading and re-installing several times, which tells me
that there's probably something quirky with my Windows installation.
Serves me right for ever letting people talk me into a GUI. Problems
were so much easier to deal with under DOS 3.11.
Philip A. Viton
nos...@nul.nul says...
I've had this problem in several other contexts, and I haven't the
faintest idea why: for example, with .html files associated with
Firefox, attempting to "start" myfile.html resulted in the "can't
execute" message. The good news is that after several reboots it
evenually went away; but I still don't know what happened.
Another case concerned Lyx (binary: lyx.exe): this was "solved" by
switching from one installer to another. I repored this on the Lyx
development list; but again no-one has been able to figure out what's
happening. Others with the same OS report no such problems. I'd venture
a guess that it has something to do with the security settings; but I
don't know how.
--
Philip A. Viton
Ohio State University