Hi-Tech 8051 C on Windows XP
Bruce Piper
Windows XP professional. I've done this successfully on XP home in the
past however now I find that when I try to compile one of my projects
(using HPD51) it's stopping when it gets to the linking stage (I
think). Has anyone else had any similar experience or does anyone have
it working? Any thoughts?
Please reply to bruce@<nospam>kit.net.au
Robert Gush
Have you tried calling all the exe's from a BAT file.
Regards - Robert
Bruce Piper
Thank you for your reply.
I can't really do this without changing the way I work. I just want to
get it working on my new computer, the same way it was working on the
old computer. I have large amounts of legacy projects that I have to
maintain; I just can't understand why it works ok on the old one
(which is XP) but not on the new one (also XP).
Michael A. Covington
"Bruce Piper" <bps...@kit.net.au> wrote in message
news:648cfe5c.03043...@posting.google.com...
Type SET and look at all your environment variables. Is something missing
on the new computer, or pointing to the wrong directory?
Pete Gray
Advanced -> Environment Variables and see what's set up.
If you're like me, you use mutliple Logins under XP (I use a different one
depending upon which compiler/IDE I'm using) and I've set the environment
variables at the User level, rather than the System level - it's neater, and
prevents environmental variable contention. Or, you might have set up your
environment variables at User level, and you're simply logged-in as a
different user.
-Pete.
"Michael A. Covington" <Mic...@CovingtonInnovations.com> wrote in message
news:UPCcncIbSew...@speedfactory.net...
Bruce Piper
Can't see anything wrong with the environment variables. I even tried
setting them from a batch file which then calls HPD51 and still no
joy.
Here's another strange symptom. On the PC where I have it working (XP
pro) I noticed that the disk it's on is formatted as FAT32. "Just for
fun" I converted it to NTFS and now the compiler doesn't work on that
PC either.
Does this provide any more clues?
Hans-Bernhard Broeker
[...]
> Here's another strange symptom. On the PC where I have it working (XP
> pro) I noticed that the disk it's on is formatted as FAT32. "Just for
> fun" I converted it to NTFS and now the compiler doesn't work on that
> PC either.
> Does this provide any more clues?
It certainly does. NTFS has a lot more features than the FAT file
systems. One of them it that every file and directory can have an
owner, and can be protected such that only the owner (or
administrators) can write there.
Installation methods designed for DOS or non-NT strands of Windows
will almost invariably get this wrong. The usual result being that it
won't work at all, or only for the admin account that installed it.
So: where on the disk *is* your compiler installed? Somebody's home
directory? Directly off the root directory? C:\"program files"? Or
maybe in the "all users\shared files" part?
What user account did you install it under? Is there any chance it may
be trying to write some temporary file into the directory it's
installed in?
--
Hans-Bernhard Broeker (bro...@physik.rwth-aachen.de)
Even if all the snow were burnt, ashes would remain.
Bruce Piper
Installed under Administrator account.
Installed in C:\HT-8051.
I did consider this as a possible problem but I thought that
administrator has full privileges. I'm sure this is something to do
with the problem as it doesn't seem to be creating any temporary or
intermediate files.
But I'm running as Administrator.
Any clues?
Hans-Bernhard Broeker
> I did consider this as a possible problem but I thought that
> administrator has full privileges.
Answer by Radio Erewan: "Yes --- in principle."
NT privilege management is rather weird. Details depend on lots of
things, including on what type of XP you have (home or pro), whether
you're networked to a "domain controller", and probably some others I
forgot.
I don't know this particular program you're running, but I assume it's
a DOS program, originally? In that case, you have the additional
problem that XP's support for DOS programs is not quite as complete as
you may need it --- that's the mildest way I can state it.
Check the attributes of the installed program very carefully, and
those of the source directory, too. Explorer won't even display them
--- you need a command line tool to show and manipulate these "access
control lists", or ACLs for short.
> I'm sure this is something to do with the problem as it doesn't seem
> to be creating any temporary or intermediate files.
Is it supposed to create temp. files? If so, do you know where it's
supossed to create them? Any chance that it's trying to create those
files in a directory that doesn't exist? Or one that is
write-protected?
You may eventually need a DOS call tracer (equivalent of 'strace' on
Unix) to debug this.