Install on Windows 7 Pro (64 bit not working)
Install on Windows 7 Pro (64 bit not working)
Hi,
I have just downloaded and installed Zeus Version 3.97I onto a 64 bit Windows 7 Pro platform and the install does not seem to be working properly.
None of the default keyboard mappings are shown under Options>Editor Options>Keyboard Mappings (it's just blank with all of the options greyed out).
Under Tools> the menu items ASCII chart, Hex Dump, File Grep, Current Directory, Calculator, Explorer, Version Control Setup
are missing.
Under Tools>Options>Keywords
the default keywords for FORTRAN files are missing.
etc.
I have another 32 bit XP computer with Zeus installed which works perfectly, so there's something about the 64bit Windows 7 Pro which is causing the problem.
I have run the program as administrator in case there were permission problems but this not fix the problem.
Any ideas?
I have just downloaded and installed Zeus Version 3.97I onto a 64 bit Windows 7 Pro platform and the install does not seem to be working properly.
None of the default keyboard mappings are shown under Options>Editor Options>Keyboard Mappings (it's just blank with all of the options greyed out).
Under Tools> the menu items ASCII chart, Hex Dump, File Grep, Current Directory, Calculator, Explorer, Version Control Setup
are missing.
Under Tools>Options>Keywords
the default keywords for FORTRAN files are missing.
etc.
I have another 32 bit XP computer with Zeus installed which works perfectly, so there's something about the 64bit Windows 7 Pro which is causing the problem.
I have run the program as administrator in case there were permission problems but this not fix the problem.
Any ideas?
Hi Andrew,
But in this instance it does sound like the install process has failed
To help figure out what went wrong this is what should have happened.
The installer should have copied the Zeus install files to this location:
Then the first time you run Zeus it should have copied the files from the above location to this location:
In this case the <UserName> is your user id.
So to fix the install you should be able to just do the copy of these files on behalf off the installer.
In other words make sure this folder is populated:
If this works please let me know what you did as I will then try to fix the install process for 64 bit machines.
You should be able to see this by looking at the exact same folders on this 32 bit machine.
Cheers Jussi
Unfortunately I don't have access to a 64 bit version of Windows to test this install process.I have just downloaded and installed Zeus Version 3.97I onto a 64 bit Windows 7 Pro platform and the install does not seem to be working properly.
But in this instance it does sound like the install process has failed

To help figure out what went wrong this is what should have happened.
The installer should have copied the Zeus install files to this location:
Code: Select all
C:\ProgramData\Xidicone\Zeus\
Code: Select all
C:\Users\<UserName>\AppData\Roaming\Xidicone\Zeus\
So to fix the install you should be able to just do the copy of these files on behalf off the installer.
In other words make sure this folder is populated:
Code: Select all
C:\Users\<UserName>\AppData\Roaming\Xidicone\Zeus\
On this 32 bit machine the install should have perfromed the exact same steps described above.I have another 32 bit XP computer with Zeus installed which works perfectly
You should be able to see this by looking at the exact same folders on this 32 bit machine.
Cheers Jussi
Hi,
I made the copies as requested and all the profiles, etc came back.mnI'm exact;ly sure of I have done everything correctly, as the folders zCVS, zDebugger, zGNU and zOxygen were left on the directory with the Zeus.exe application (in my case, c:\program files\Zeus.
Thanks for your quick response,
Andrew
I made the copies as requested and all the profiles, etc came back.mnI'm exact;ly sure of I have done everything correctly, as the folders zCVS, zDebugger, zGNU and zOxygen were left on the directory with the Zeus.exe application (in my case, c:\program files\Zeus.
Thanks for your quick response,
Andrew
Hi Andrew,
The reason Zeus has to do all this extra work of copying files around is Windows 7 unlike Windows XP locks the content of the c:\Program Files\Zeus folder.
So the only files left in that folder are read only.
1) Tools, DOS Command Line menu
2) In the Arguments entry field type in this:
You should see this output and more importantly you should see that the version number is 1.10 as should below:
If you do see this then search the machine for another xfgrep.exe and if you find one delete it.
If you don't see this then that would be very confusing since this file is part of the installer
In any case to fix this, just copy the xfgrep.exe from the 32 bit machine.
Cheers Jussi
That sounds OK.as the folders zCVS, zDebugger, zGNU and zOxygen were left on the directory with the Zeus.exe application (in my case, c:\program files\Zeus.
The reason Zeus has to do all this extra work of copying files around is Windows 7 unlike Windows XP locks the content of the c:\Program Files\Zeus folder.
So the only files left in that folder are read only.
Can you do the following:the "find in files" option does not appear to be working.
1) Tools, DOS Command Line menu
2) In the Arguments entry field type in this:
Code: Select all
"c:\Program Files\Zeus\xfgrep.exe" -?
Code: Select all
xfgrep -?
xfgrep searches files for a given pattern. Execute by
xfgrep [flags] regular_expression file_list
Flags are single characters preceeded by '-':
-c The count of the matches found is displayed
-f Print full file name for matching lines, see below
-s Print short file name for matching lines, see below
-l List the first occurence of a matching line for each file
-n Each line is preceeded by its line number
-v Only print non-matching lines
-i Ignore case
-d Search subdirectories
-x Disable regular expression searching
-r Assume the file_list provided is an input response file
The file_list is a list of files (wildcards are acceptable modes).
Eg. [file1.c file2.c] or [*.c *.h] or [\prog\*.c;*.h]
xfgrep version 1.10
No search pattern provided
Usage: xfgrep [-cfslnvidx] pattern [file ...]. xfgrep ? for help
If you don't see this then that would be very confusing since this file is part of the installer

In any case to fix this, just copy the xfgrep.exe from the 32 bit machine.
Cheers Jussi
Hi,
I have put an xfgrep.exe into every directory where Zeus is likely to be reading it (including the install directory). The program exists and runs correctly. But the error still persists when running Zeus.
I have also deleted the extra xfgrep.exe's so that there is only one on the computer.
My tuppence worth is that the path to xfgrep is corrupted. Is there anyway I can see what is actually being executed ?
I have put an xfgrep.exe into every directory where Zeus is likely to be reading it (including the install directory). The program exists and runs correctly. But the error still persists when running Zeus.
I have also deleted the extra xfgrep.exe's so that there is only one on the computer.
My tuppence worth is that the path to xfgrep is corrupted. Is there anyway I can see what is actually being executed ?
Hi Andrew,
Can you use the Options, Editor Options menu and in the General section turn on the Help debug tools, macros and executables option.
Then run the find in files and use the Macros, Macro/Debug Output menu to see the resulting command.
Post that output here.
Cheers Jussi
Is the xfgrep.exe version number 1.10But the error still persists when running Zeus.

Yes there is.I can see what is actually being executed ?
Can you use the Options, Editor Options menu and in the General section turn on the Help debug tools, macros and executables option.
Then run the find in files and use the Macros, Macro/Debug Output menu to see the resulting command.
Post that output here.
Cheers Jussi
Two issues,
1) there is a problem with the license key when I restart the program it is corrupted and I have to re-enter it.
2) Below is a copy of the debug output. All I get is the message
"Bad command line arguments supplied."
---------------------------------------------------------------------------
Zeus for Windows Programmers Editor - Version 3.97i-beta5
Copyright (c) Xidicone P/L 1993-2011. All rights reserved.
---------------------------------------------------------------------------
**** NOTE: DEBUG OUTPUT ENABLED ****
This and the other debug output shown below is being created because the Zeus
debug output option is currently enabled.
To disable this option, use the Options, Editor Options menu and in the General
panel un-check the 'Debug, tools, macros and executables' option.
This debug option can be very helpful when configuring compilers and tools or
when creating new scripts.
**** NOTE: DEBUG OUTPUT ENABLED ****
Bad command line arguments supplied.
1) there is a problem with the license key when I restart the program it is corrupted and I have to re-enter it.
2) Below is a copy of the debug output. All I get is the message
"Bad command line arguments supplied."
---------------------------------------------------------------------------
Zeus for Windows Programmers Editor - Version 3.97i-beta5
Copyright (c) Xidicone P/L 1993-2011. All rights reserved.
---------------------------------------------------------------------------
**** NOTE: DEBUG OUTPUT ENABLED ****
This and the other debug output shown below is being created because the Zeus
debug output option is currently enabled.
To disable this option, use the Options, Editor Options menu and in the General
panel un-check the 'Debug, tools, macros and executables' option.
This debug option can be very helpful when configuring compilers and tools or
when creating new scripts.
**** NOTE: DEBUG OUTPUT ENABLED ****
Bad command line arguments supplied.
This sounds like the editor does not have access to the registry.1) there is a problem with the license key when I restart the program it is corrupted and I have to re-enter it.
I would recommend trying to apply the registration key while logged in as a sys admin and then logging out and then re-running the Zeus executable.
There is no extra debug output being generated2) Below is a copy of the debug output. All I get is the message
"Bad command line arguments supplied."

Did you turn on the debug option mentiond earlier?
Cheers Jussi