[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]
==== Change Sort Dos Path Name (AREV Specific) ====
=== At 06 MAR 2006 01:44:24PM Jim Leong wrote: ===
{{tag>"AREV Specific"}}
Does anyone know a way to change the Sort Dos Path File Name while in an Arev application. I can change the rollout file name with the @ROLLOUT.FILE system variable, but cannot find a system variable for the Sort Dos Path file Name.
I am doing some testing on a Citrix XP Server. I need to change the rollout and Sort Dos path if a user logs into that server.
----
=== At 06 MAR 2006 03:00PM Victor Engel wrote: ===
I think it's in the ini file for version 3.x. Previously, it was in the environment record. After updating it, you have to call initialize(). See this thread.
http://www.revelation.com/__85256DB80017688B.nsf/0/BCFD1B30EA75175E8525659F00733F66?Open
Caveat: I haven't tried this, but I think it will work.
----
=== At 06 MAR 2006 03:05PM Victor Engel wrote: ===
Also this thread.
http://www.revelation.com/__85256DB80017688B.nsf/0/C264DAEBF36B04DA85256732005CAA5E?OpenDocument
Has version 3.13 been released yet?
----
=== At 06 MAR 2006 03:05PM Karen Oland wrote: ===
Create a different .INI file for use from that server and set the AREV environment variable to point to it. The location is saved in the INI file (either arevc.ini by default or by user if you have set that up).
----
=== At 06 MAR 2006 05:11PM Jim Leong wrote: ===
Looks like the answer may be no. I am using Arev 2.12 so a different ini file for each user is not possible or practical.
Thanks for the feedback.
----
=== At 06 MAR 2006 05:20PM Victor Engel wrote: ===
In that case, I think you need to update field 43 of the environment record in the SYSTEM file and call initialize().
----
=== At 06 MAR 2006 05:23PM Warren Auyong wrote: ===
I'm still waiting from Rev H myself...
----
=== At 06 MAR 2006 05:36PM Jim Leong wrote: ===
I tried that. No luck! It keep resetting back to the default. It even reset my @ROLLOUT.FILE variable back to the original.
----
=== At 06 MAR 2006 11:41PM Karen Oland wrote: ===
Did you just change @environ.set or did you read in the environment record from SYSTEM, change it (might as well do @rollout at same time), then write it back, then call inialize()?
You'll need a point to SYSTEM and a valid password if sysprog is protected (and full rights to write to the file, of course).
----
=== At 06 MAR 2006 11:45PM Karen Oland wrote: ===
Another simple solution is to copy just the revboot directory to a new subdirectory, update the environment there and then log into the app from there (hard code the full paths for data into the voc for all volumes you attach). You can even much with the copied revmedia to use all the same arev files in the old revboot area and leave just the arev.exe, files for SYSTEM and a revmedia in the new location (and nearly nothing else required) -- a similar technique is used when someone loses all the passwords (or damaged SYSTEM with no backups) to an app and calls in the consultant in desparation.
Then have the iconv on citrix run the app from the 2nd location.
----
=== At 07 MAR 2006 11:11AM Victor Engel wrote: ===
I think this would violate the licensing terms. Furthermore, some locking may not work (if using byte-range driver -- was this still an option in 2.12?).
----
=== At 07 MAR 2006 02:59PM Jim Leong wrote: ===
I just just change the @environ.set. I will try writing it to the system file.
Thanks for all your feedback!
----
=== At 10 MAR 2006 07:33PM Karen Oland wrote: ===
Yes, there could be licensing or locking issues. We usually had this type of setup for one runtime (most users) and a developer (few users). Both had appropriate number of lanpacks installed and we used novell locking (then the nlm later on) - no error occured. If you use the same serial number in both places, then I believe you need to get the user count adjusted appropriately (this can occur when the customer is running an RDK, so all serial #s are the same for all customers of a single developer) - just put a 10 user system in on directory and a 2 or 5 user copy in the other (locking will definitely fail if you use a single user version in either directory). Either the developer can handle changing the runtime count (or RTI used to do so for a small fee).
Using such a setup to bypass the passwords is more problematic and possibly violates the companies security policies (and federal law if the company is unaware you are doing so).
[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=2C4096250E17765A852571290066F12B|View this thread on the forum...]]