Mail Archives: djgpp/2004/06/23/08:00:14
Paul Wilkins <disk AT paradise DOT net DOT nz> wrote:
> Hans-Bernhard Broeker wrote:
[...]
> > There's your problem. You almost certainly don't want to start RHIDE
> > in either of those two ways. Instead, open a command line shell, 'cd'
> > to the place you actually want your project to be in, and *then* run
> > 'rhide projectname'. Make that place one devoid of blanks in the
> > path, to be on the sane and safe side of things.
> I *know* that's the problem, BUT - the installation and usage guide at
> http://www.rhide.com/doc/rhide_1.html#SEC3 doesn't say anything about it.
Of course not: that's the node about *installing* RHIDE. Your issue
is with how to *run* it. Those are two quite separate issues.
It's obviously impossible to completely enumerate all possible ways
not to something, so you shouldn't be expecting it say something about
any which way you came up with.
But you're right in one aspect: the nodes of the above document
actually talking about how to run RHIDE (1.5 and 1.8) just say 'type
this' or 'run it', without noting at what prompt to do that.
> >>Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\djgpp\bin
> >
> > I'm reasonably sure that this Path is not what the instructions told
> > you to make it. If at all possible, you should have c:\djgpp\bin
> > *first* on the path, not last.
> Yes well, a google search for Install DJGPP Windows XP gave me a page called
> How to install DJGPP
> http://www.dcs.kcl.ac.uk/staff/pinzon/csmdsi/html/instgpp.html
And since when is the 'i feel lucky' link off google.com the
definitive reference guide for a product? You may have found some
instructions, but they're not "the instructions" to be called that
without any qualification.
> I take it that I should have the djgpp path ahead of everything else?
Preferrably yes. It removes one more place for potentially confusing
problems to come from.
> Other than possible performance improvements, what reasoning is
> there for the change?
Being sure that when you call any DJGPP tool by name, you actually get
it, and not some other program that happens to be installed having the
same name.
> > A further note of caution: this is the Win32 / cmd.exe view of the
> > environment (detectable by the variable names being lower-case). You
> > want to look at the *DOS* view instead. You may have to explicitly
> > run 'command.com' to get a look at that. It should be equivalent, but
> > it never hurts to be sure.
> Both cmd.exe and command.com look exactly the same, even down to having
> the same vesion number with the VER command.
Look more closely, then. You'll find that 'set' typed from inside
command.com produces rather different output.
> >>As RHIDE is primarily developed for Windows machines,
> >
> > Huh? Whatever made you think that?
> This line from the http://www.rhide.com/ front page made me think that.
> "The original system, RHIDE was written for, is DJGPP. Because of
> many requests and the increasing popularity I made RHIDE also
> available for GNU/Linux."
> The "made RHIDE also available for GNU/Linux" is a big clue that its
> primary development was for the Microsoft based OS's.
Oh, so the world is now cleanly divided into GNU/Linux and MS Windows,
with no other options, is it? Well -- it's not. It clearly says
there that the system is "DJGPP". Which is not Windows, nor does it
want to be.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -