|
Greetings! With the very latest ACS Service pack that was delivered a
few weeks ago, we shipped a new 'windows script' that handles the File
associations for you. Once you down load the latest version from ESS or
the FTP site if you look in the directory Windows_Application there are
2 new scripts install_acs_32.js & install_acs_64.js . These scripts will
create the file associations and put a shortcut to the main page and
session manager on your desktop. Basically it will emulate a windows
install process. This script will have to be run for every user, and
should simplify the initial set up for each user. There is also a
QuickStart guide in that directory.
If you have thoughts on making this process better, PLEASE let me know.
Thanks! Tim
Tim Rowe, timmr@xxxxxxxxxx
Business Architect Application Development & Systems Management for IBM i
IBM i Development Lab, Rochester, MN
(507) 253-6191 (Tie) 553-6191
http://www-03.ibm.com/systems/power/software/i/are/index.html
------------------------------
message: 2
date: Thu, 6 Aug 2015 10:09:37 -0500
from: Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>
subject: Re: new acs install process
thanks Justin.
Is there a way to NOT have to do the associate back to the
acslaunch-win-32.exe on every user?
I tried to make shortcuts in my folder where my default .hod and
acsbundle.jar exist, but even when I copy the shortcuts to the user
desktop, it asks for a association...
I presume in windows that file associations are profile based?
is there a way to make the association stick with the shortcut????
On Wed, Aug 5, 2015 at 3:13 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
wrote:
I keep mine on our NetServer with the AcsConfig.properties set to onlyand
allow 5250 (only component my end users need). I have default 5250.HOD
IBMi.kmp files in that same folder that I copy down to the user's PC.the
Right-click the local 5250.HOD and do an "Open with" to point back to
acslaunch-win-32.exe file on the NetServer.list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
------------------------------
------------------------------
End of MIDRANGE-L Digest, Vol 14, Issue 1112
********************************************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.