Re: IBM i Access windows don't save size

Joe, are you talking about when you select 80 column or 132 and then save
it or are you talking where you can mouse over to the edge, then resize
it?? In both cases do you go back and then save(as) on the the either all
ready created .WS or create a new one?? The .WS, do you have rights to save
changes to it, I am sure that you do.


On Thu, Jan 20, 2011 at 9:06 AM, Vern Hamberg <vhamberg@xxxxxxxxxxx>wrote:

That changed a number of releases ago, I believe. It allows at least for
individual settings, because there is also the option to put them under
your own Documents and Settings area.

Vern

On 1/20/2011 7:13 AM, Joe Pluta wrote:

As a followup, things have gotten even weirder, or at least more
confusing. For example, it seems that IBM moved where things are
stored. Everything used to be in this directory:

C:\Program Files\IBM\Client Access\Emulator\Private

This included workstation layouts (.ws), macros (.mac), keyboard maps
(.kmp) and so on. Now at least some of that stuff has been moved to:

C:\Documents and Settings\All Users\Application Data\IBM\Client
Access\Emulator\private

It's an option on the PC5250 tab of the IBM i Access Properties dialog.
It got set when I tried to check the box to store window information in
the session file.

Joe

Nope. Still get the original size. I was going to try copying the
LastExit data from pcswin.ini to the individual .ws files to see if

that

worked, but it got backburnered.

Joe

Joe

Did you ever figure out how to retain the window sizes? I have a user
that has the same issue.

Thanks

Bob Cagle
IT Manager
Lynk, Inc.

-----Original Message-----
From: Joe Pluta

I just upgraded to V6.0 of iSeries Access and I am having problems

with

my emulator windows not keeping their size. I want them to be at
808x526, and every morning they switch back to 808x476. I have to

drag

the bottom of the window down 40 or 50 pixels and they resize

perfectly,

but it's a bit of an inconvenience.

I've tried saving using the File / Save, but that doesn't seem to fix
the problem. Has anyone run into something like this?

Joe

--
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.