Opened 13 years ago
Closed 13 years ago
#25 closed defect (fixed)
Installation problems using Win7
| Reported by: | Becka Lawson | Owned by: | Olly Betts |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.2.2 |
| Component: | Other | Version: | 1.2.0 |
| Keywords: | Cc: |
Description
My operating system is Win7 which doesn't seem to agree with Survex. When I just install Survex it won't work at all. Julian fiddled around to specify paths and eventually got .svx files to process by double-clicking on them but this doesn't produce a .log file so I don't know the vital statistics for a successfully processed file and, much worse, if there's an error it doesn't give me any hints about what it is.
I can run Survex using Command Prompts but I have to specify the full path to find the programme (so "ProgamFiles?\Survex\cavern.exe" witchesII.svx for example and again this doesn't save a log file.
On the CUCC expo this summer the Expo machine running Linux was also not producing log files so perhaps this is a more general problem?
Change History (4)
comment:1 Changed 13 years ago by
| Status: | new → assigned |
|---|---|
| Summary: | Installation problems using Win7 and lack of .log files → Installation problems using Win7 |
| Version: | → 1.2.0 |
comment:2 Changed 13 years ago by
OK, I tested on a Windows 7 box - I created a fresh normal user, and installed which asked me for an administrator password (I gave it Administrator and the admin password) and I can process .svx files using right click and "Process" as I would expect.
The custom cursors don't look right, but otherwise everything seems to work.
Did you install as a normal user or as a user who already had administrator rights? (I didn't try the latter yet).
Did you have a previous version of Survex installed on this machine?
comment:3 Changed 13 years ago by
| Milestone: | → 1.2.2 |
|---|
Just to update the side issue I noted, I've fixed the custom cursors in 1.2.1.
comment:4 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Becka reports by email that this is solved. It looks like the issue was installing over an older version which was still running.
Not sure why the file associations aren't working by default. I'll see if I can find a machine to test that on.
The .log file isn't produced by default, but rather by the file association which gets set up which passes --log to cavern - this is:
"{app}\cavern.exe" --log -q -o "%1" "%1"So the lack of a .log file is just a consequence of the installation issue (and Julian not passing --log in what he set up by hand).
Incidentally, with modern aven, you can just open a .svx file directly which you might find nicer. It still needs a few tweaks (you don't get to read the log unless there were warnings or errors, which is annoying sometimes) so isn't the default set up yet.