I have noticed two things right off the bat:
1) The samples aren't there (hello and roman) in the stated directory.
2) I constantly get a warning about "icont not found" when running the compiler from either the ide or command line even though it is on my path and "where icont" points to the C:\Unicon\bin\icont.exe
Many thanks for all the help (:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
unless you have your own libraries and you want to point at them, you never need to set IPATH or LPATH. This is true on all platforms and it has been that way for as long as I remember. I hardly use IPATH/LPATH at all.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
unless you have your own libraries and you want to point at them, you
never need to set IPATH or LPATH. This is true on all platforms and it
has been that way for as long as I remember. I hardly use IPATH/LPATH
at all.
check version 13.2, and let me know if you still see the issue please. We have made several fixes since that build but I know the one you reported is not one of them. If the problem persist I'd like to fix it before release 13.2.
Thanks!
Jafar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I uninstalled 13.1, made sure the c:\unicon folder was removed, ran the installer, verified that my path was set correctly, and attempted to compile the "features" example from: http://btiffin.users.sourceforge.net/up/unicon.html#
I got a different error this time stating "error in startup code cannot open interpreter file"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The interpreter file is iconx (and the graphical is wiconx), both live under c:\unicon\bin along with other binaries such as icont which was reported as "no icont found" in your first attempt.
can you compile without -x? -x just runs the program after compilation.
Here are a few things that would help us diagnose the problem
1- Compile your program and post the output here
2- Do "where iconx", where "wiconx", and share the output
3- run this command from the command line and share the output:
unicon -features
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
CenoByte,
I tried to reproduce the problem you are describing but with no luck. I did my latest test in the built-in sandbox that comes with Windows to make sure it is completely isolated from anything I did to my machine, here is run of the example in Brian's book:
```
c:\Unicon>unicon hello.icn -x
Parsing hello.icn: .
C:\Unicon\bin\icont.exe -c -O hello.icn C:\Users\WDAGUtilityAccount\AppData\Local\Temp\uni12344087
Translating:
hello.icn:
main
No errors
C:\Unicon\bin\icont.exe hello.u -x
Linking:
Executing:
Hello, world
Features in this Unicon Version 13.2. October 15, 2020
MS Windows NT
POSIX
DBM
ASCII
co-expressions
native coswitch
dc:\Unicon>ynamic loading
environment variables
event monitoring
external functions
keyboard functions
large integers
multiple programs
pattern type
pseudo terminals
system function
messaging
graphics
3D graphics
MS Windows
Win32
libz file compression
JPEG images
PNG images
SQL via ODBC
secure sockets layer encryption
CCompiler MinGW gcc 9.2.0
Physical memory: 4293836800 bytes
Revision 6188-cd2d8443
Arch x86_64
CPU cores 8
c:\Unicon>
```
As you can see, everything work/look OK. There is a chance your Windows is not trusting Unicon binaries you downloaded from the internet and limiting its access/permission and breaking it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nope, I'm not seeing anything there. I'm so puzzled that 13.1 gives a warning, but will still compile working programs, but 13.2 gives me even more confusing problems lol.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you verify that your user name does not have a blank in it?
Directory names (like a user name) that have blanks in them have in
the past caused problems similar to that described.
I have machines with blank embeded user names where unicon will not work
with files in the Documents directory but will work with files in the C:\Unicon directory.
On other machines, I have a different user name without a blank. On that machine
everything works.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the user name doesn't have a blank in it. it's just odd to me that:
1) 13.1 will compile things that do end up running, but issues the warning that icont is missing.
2) 13.2 will not even find the compiler even though "where icont" points right to it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello to all!
I stumbled across Unicon, and I'm super intrigued by a lot of what it has to offer.
I followed the installation instructions at:
http://unicon.org/utr/utr7.html
I have noticed two things right off the bat:
1) The samples aren't there (hello and roman) in the stated directory.
2) I constantly get a warning about "icont not found" when running the compiler from either the ide or command line even though it is on my path and "where icont" points to the C:\Unicon\bin\icont.exe
Many thanks for all the help (:
Good afternoon Cenobyte,
Can you confirm that the Unicon system has been installed in c:/unicon
and that there is a sub-directory call bin and a sub-directory called ipl?
I do not use windows and so what I have to say is most likely a decade
old, though I did check it on our media machine a few minutes ago.
Open command.exe
type in
set
and then look for the following environment variables
Path
IPATH
LPATH
and let us know what you find here
regards
Bruce Rennie
Last edit: Jafar 2020-11-26
i have Unicon installed to what the installer recommended on my system which is:
C:\Unicon
both the subdirectories are present.
PATH=C:\Unicon\bin;
(and more, but that's how it starts)
IPATH and LPATH aren't showing.
I must add, that examples from:
http://btiffin.users.sourceforge.net/up/unicon.html#the-unicon-programming-language
will work, but they do still give the warning:
Warning: no icont found thought it would be
icont.exe
but still "where icont.exe" gives me
C:\Unicon\bin\icont.exe
Cenobyte,
What version of you Unicon are you running ? What is your Windows version ?
You don't have to worry about IPATH and LPATH .
Good afternoon Jafar,
When did IPATH and LPATH no longer be necessary under windows? This is
good to know. Thank you.
regards
Last edit: Jafar 2020-11-26
unless you have your own libraries and you want to point at them, you never need to set IPATH or LPATH. This is true on all platforms and it has been that way for as long as I remember. I hardly use IPATH/LPATH at all.
Thank you Jafar,
As I have my own libraries this makes sense.
On 26/11/20 4:37 pm, Jafar wrote:
Windows 10 Home, and I downloaded: setup-unicon_13.1_amd64_rev5965.exe
and used that to install Unicon.
I don't remember seeing this error before.
We are preparing for a new release in a week or two. I have a build that is a month old here:
http://jafaral.com:8383/unicon/release/
check version 13.2, and let me know if you still see the issue please. We have made several fixes since that build but I know the one you reported is not one of them. If the problem persist I'd like to fix it before release 13.2.
Thanks!
Jafar
I uninstalled 13.1, made sure the c:\unicon folder was removed, ran the installer, verified that my path was set correctly, and attempted to compile the "features" example from:
http://btiffin.users.sourceforge.net/up/unicon.html#
I got a different error this time stating "error in startup code cannot open interpreter file"
The interpreter file is iconx (and the graphical is wiconx), both live under c:\unicon\bin along with other binaries such as icont which was reported as "no icont found" in your first attempt.
can you compile without -x? -x just runs the program after compilation.
Here are a few things that would help us diagnose the problem
1- Compile your program and post the output here
2- Do "where iconx", where "wiconx", and share the output
3- run this command from the command line and share the output:
unicon -features
Thanks.
attemmpting to compile without the -x gives the same error
where iconx
where wiconx
both point to C:\Unicon\bin\
unicon -features will not run, gives the "error in startup code unicon: cannot open interpreter file"
can you run:
iconx unicon -features
negative, same error when attempting to after installing 13.2 from the provided link.
I have also uninstalled and reinstalled 13.2 just to make sure i did not mess anything up.
what do you get when you run :
iconx
no argument or anything.
error in startup code
no icode file specified
ok, I will investigate this more tomorrow and get back to you. thanks for the feedback so far.
Thank you
CenoByte,
I tried to reproduce the problem you are describing but with no luck. I did my latest test in the built-in sandbox that comes with Windows to make sure it is completely isolated from anything I did to my machine, here is run of the example in Brian's book:
```
c:\Unicon>unicon hello.icn -x
Parsing hello.icn: .
C:\Unicon\bin\icont.exe -c -O hello.icn C:\Users\WDAGUtilityAccount\AppData\Local\Temp\uni12344087
Translating:
hello.icn:
main
No errors
C:\Unicon\bin\icont.exe hello.u -x
Linking:
Executing:
Hello, world
Features in this Unicon Version 13.2. October 15, 2020
MS Windows NT
POSIX
DBM
ASCII
co-expressions
native coswitch
dc:\Unicon>ynamic loading
environment variables
event monitoring
external functions
keyboard functions
large integers
multiple programs
pattern type
pseudo terminals
system function
messaging
graphics
3D graphics
MS Windows
Win32
libz file compression
JPEG images
PNG images
SQL via ODBC
secure sockets layer encryption
CCompiler MinGW gcc 9.2.0
Physical memory: 4293836800 bytes
Revision 6188-cd2d8443
Arch x86_64
CPU cores 8
c:\Unicon>
```
As you can see, everything work/look OK. There is a chance your Windows is not trusting Unicon binaries you downloaded from the internet and limiting its access/permission and breaking it.
it didn't pop anything up to indicate that it isn't, i'll dig around an look to see if that is the case though.
Nope, I'm not seeing anything there. I'm so puzzled that 13.1 gives a warning, but will still compile working programs, but 13.2 gives me even more confusing problems lol.
Can you verify that your user name does not have a blank in it?
Directory names (like a user name) that have blanks in them have in
the past caused problems similar to that described.
I have machines with blank embeded user names where unicon will not work
with files in the Documents directory but will work with files in the C:\Unicon directory.
On other machines, I have a different user name without a blank. On that machine
everything works.
the user name doesn't have a blank in it. it's just odd to me that:
1) 13.1 will compile things that do end up running, but issues the warning that icont is missing.
2) 13.2 will not even find the compiler even though "where icont" points right to it.
sorry, double post
Last edit: Cenobyte 2020-11-29