hla set up for the art of assembly
in [ASM]
|
From: Frank Kotler on 12 Jun 2008 20:28 ronaldsorrell2005(a)yahoo.com wrote: > hlainc=C:\hla\hla\include > hlalib=C:\hla\hla\hlalib\hlalib.lib Looks like one too many "hla"s. > lib=;C:\hla\hlalib;C:\hla\hlalib;C:\hla\hlalib;C:\hla\hla\hlalib This looks like you've attempted multiple installations(?). > Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C: > \Program Files\Common Files\Roxio Shared\DLLShared\;C:\Pr > ogram Files\QuickTime\QTSystem\;C:\Program Files\Texas Instruments\CC > Essentials 2.0\eclipse\plugins\com.ti.eem.wrapper_ > 2.0.0 Here's your problem. You need "C:\hla" on your path! > Directory of C:\hla > > 06/12/2008 10:44 AM <DIR> . > 06/12/2008 10:44 AM <DIR> .. > 05/15/2006 07:26 PM 76,288 fasm.exe > 01/07/2008 11:58 AM 73,728 fhla.exe > 01/07/2008 11:58 AM 73,728 ghla.exe > 06/12/2008 10:42 AM <DIR> hla This looks like you've got a second copy of all this in "C:\hla\hla". (curiously, it's dated two minutes earlier than its parent directory???) Unless this is intentional, you could just "deltree" it - and go back to just one "hla" in "hlainc=", "hlalib=", "lib=" (I guess this one's for polink?) - and on your path, of course! .... > Directory of C:\hla\Projects > > 06/12/2008 04:16 PM <DIR> . > 06/12/2008 04:16 PM <DIR> .. > 06/12/2008 03:58 PM 0 cd > 06/12/2008 03:58 PM 0 dir > 06/12/2008 03:58 PM 0 hla > 06/12/2008 03:58 PM 0 hlalib > 06/12/2008 10:40 AM 145 hw.hla > 06/12/2008 03:58 PM 0 include > 06/12/2008 03:58 PM 0 Projects > 06/12/2008 03:58 PM 0 set > 06/12/2008 04:16 PM 59 sometext.txt > 9 File(s) 204 bytes > 2 Dir(s) 143,569,522,688 bytes free Those zero-length files look "funny" to me, but I guess they won't do any harm. > C:\hla\Projects>hla hw.hla > 'hla' is not recognized as an internal or external command, > operable program or batch file. This is because hla.exe isn't on your path. When you were in the "C:\hla" (or "C:\hla\hla") directory, HLA would run (current directory is on your path), but couldn't open "hw.hla"... 'cause it's in "C:\hla\projects". Now you're in "C:\hla\projects" HLA won't run because "hla.exe" isn't on your path. You *could* put "hw.hla" and all your source code in the same directory as "hla.exe". That would get real cluttered real quick! You could, every time you open a command prompt, do "path=C:\hla;%PATH% as Santosh suggested. I *think* the GUI method Santosh refers to involves right clicking on the icon, then selecting "properties" -> "advanced"(?) -> "environment" or some such. The old-fashioned way used to be to edit "c:\autoexec.bat". If that still works, it's probably easiest (I haven't run Windows later than 98, so I don't know what still works in XP... never mind Vista! But "someone will come along"...). It's probably worth learning enough of your OS so that you know how to do this (and why you need to) - even though it's not "assembly language". These installation problems with HLA are becoming quite rare, since the automatic installation program came along. I don't know if you didn't use it, or used it more than once... but it looks like something didn't go quite right. Might be worth deleting everything and starting over, but just deleting "C:\hla\hla" and cleaning up the environment variables (including PATH) to match should do it. Hang in there, it gets easier once you get to the "assembly language" part! Best, Frank
From: NathanCBaker on 12 Jun 2008 22:04 On Jun 12, 1:00 pm, ronaldsorrell2...(a)yahoo.com wrote: > hey every one, i am new to this program and to programing i am having > problems getting the hla to work. in the command window i have: C: > \hla> hla -v hw.hla , and hit enter i get what the install > instructions say under trouble shooting, but the last part "Compiling > "hw.hla" to "hw.obj"" and on down. what i do get there is "Could not > open hw.hla" . i hope one of you know what my problem is because i > really donot know but i am thinking the compiler and linker is not > working and i have no clue yet on how solve this issue. any > suggestions? It is less fun to play "hide-n-seek" without the hide: http://sevag.krikorian.googlepages.com/hide Nathan.
From: santosh on 12 Jun 2008 23:58 Frank Kotler wrote: [learning HLA] > Hang in there, it gets easier once you get to the "assembly language" > part! I think "once" is the operative word here. :-)
From: santosh on 13 Jun 2008 00:08 Frank Kotler wrote: > ronaldsorrell2005(a)yahoo.com wrote: >> hey every one, i am new to this program and to programing i am having >> problems getting the hla to work. in the command window i have: C: >> \hla> hla -v hw.hla , and hit enter i get what the install >> instructions say under trouble shooting, but the last part "Compiling >> "hw.hla" to "hw.obj"" and on down. what i do get there is "Could not >> open hw.hla" . i hope one of you know what my problem is because i >> really donot know but i am thinking the compiler and linker is not >> working and i have no clue yet on how solve this issue. any >> suggestions? > > When you type "dir", do you see "hw.hla"? If not, that's your problem. > Some editors insist on saving files as "hw.hla.txt" or so. Beat the > editor into submission, rename it, or simply give HLA "hla -v > hw.hla.txt", if that's the problem. Or change to the directory where > "hw.hla" *does* exist. If HLA is finding "hw.hla" and it *still* > doesn't work, get back to us. > > You might want to joint the !YAHOO! group: > > http://tech.groups.yahoo.com/group/aoaprogramming/ > > In the "Tales out of school" department, some HLA "fans" in this ng > will be amused to hear that someone just posted: > > "I really don't want to learn Assembly and thats why I am interested > in HLA" > > At least he knows what he's up against... Maybe it's Betov in disguise? :-)
From: ronaldsorrell2005 on 13 Jun 2008 07:24
On Jun 12, 8:28 pm, Frank Kotler <fbkot...(a)verizon.net> wrote: > ronaldsorrell2...(a)yahoo.com wrote: > > hlainc=C:\hla\hla\include > > hlalib=C:\hla\hla\hlalib\hlalib.lib > > Looks like one too many "hla"s. > > > lib=;C:\hla\hlalib;C:\hla\hlalib;C:\hla\hlalib;C:\hla\hla\hlalib > > This looks like you've attempted multiple installations(?). > > > Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C: > > \Program Files\Common Files\Roxio Shared\DLLShared\;C:\Pr > > ogram Files\QuickTime\QTSystem\;C:\Program Files\Texas Instruments\CC > > Essentials 2.0\eclipse\plugins\com.ti.eem.wrapper_ > > 2.0.0 > > Here's your problem. You need "C:\hla" on your path! > > > Directory of C:\hla > > > 06/12/2008 10:44 AM <DIR> . > > 06/12/2008 10:44 AM <DIR> .. > > 05/15/2006 07:26 PM 76,288 fasm.exe > > 01/07/2008 11:58 AM 73,728 fhla.exe > > 01/07/2008 11:58 AM 73,728 ghla.exe > > 06/12/2008 10:42 AM <DIR> hla > > This looks like you've got a second copy of all this in "C:\hla\hla". > (curiously, it's dated two minutes earlier than its parent directory???) > Unless this is intentional, you could just "deltree" it - and go back to > just one "hla" in "hlainc=", "hlalib=", "lib=" (I guess this one's for > polink?) - and on your path, of course! > > ... > > > Directory of C:\hla\Projects > > > 06/12/2008 04:16 PM <DIR> . > > 06/12/2008 04:16 PM <DIR> .. > > 06/12/2008 03:58 PM 0 cd > > 06/12/2008 03:58 PM 0 dir > > 06/12/2008 03:58 PM 0 hla > > 06/12/2008 03:58 PM 0 hlalib > > 06/12/2008 10:40 AM 145 hw.hla > > 06/12/2008 03:58 PM 0 include > > 06/12/2008 03:58 PM 0 Projects > > 06/12/2008 03:58 PM 0 set > > 06/12/2008 04:16 PM 59 sometext.txt > > 9 File(s) 204 bytes > > 2 Dir(s) 143,569,522,688 bytes free > > Those zero-length files look "funny" to me, but I guess they won't do > any harm. > > > C:\hla\Projects>hla hw.hla > > 'hla' is not recognized as an internal or external command, > > operable program or batch file. > > This is because hla.exe isn't on your path. When you were in the > "C:\hla" (or "C:\hla\hla") directory, HLA would run (current directory > is on your path), but couldn't open "hw.hla"... 'cause it's in > "C:\hla\projects". Now you're in "C:\hla\projects" HLA won't run because > "hla.exe" isn't on your path. > > You *could* put "hw.hla" and all your source code in the same directory > as "hla.exe". That would get real cluttered real quick! You could, every > time you open a command prompt, do "path=C:\hla;%PATH% as Santosh > suggested. I *think* the GUI method Santosh refers to involves right > clicking on the icon, then selecting "properties" -> "advanced"(?) -> > "environment" or some such. The old-fashioned way used to be to edit > "c:\autoexec.bat". If that still works, it's probably easiest (I haven't > run Windows later than 98, so I don't know what still works in XP... > never mind Vista! But "someone will come along"...). It's probably worth > learning enough of your OS so that you know how to do this (and why you > need to) - even though it's not "assembly language". > > These installation problems with HLA are becoming quite rare, since the > automatic installation program came along. I don't know if you didn't > use it, or used it more than once... but it looks like something didn't > go quite right. Might be worth deleting everything and starting over, > but just deleting "C:\hla\hla" and cleaning up the environment variables > (including PATH) to match should do it. > > Hang in there, it gets easier once you get to the "assembly language" part! > > Best, > Frank Thanks frank, yes i did put another HLA into the projects file after the first one to see if it would reconize it thier, well it did not and i have deleted it out shortly after but it was after i sent the message. I have used the auto install methode and it still came out wrong. i think some of the settings i have on all my computers prevented somthing from happening. I work with packaging for hazardous materials and explosives for UN certification. So I have a lot of securety programs and this gets in my way. I am hoping soon to get another lap top that i can use for my personal use. I will most likely do as said and start over with the installation, but if all else fails, thanks you guys i can get to work again. test professor, see ya |