DirWinOpen=F6 Doesn't Seem To Work In V10,B031
- Thread starter BitPusher
- Start date
- Jun
- 608
- 6
Alias Load Failure with Version 10
Now that I switched to global aliases, my version-9 alias file loads
without problem. (Under version 9, I had no problem loading the file
with local aliases.)
I must say that the uncontrolled failure in version 10 is disappointing.
There is no warning message -- just a complete crash. It would be
gracious if the alias loader would check for enough space and fail with
an error message rather than leaving the alias storage messed up so that
the system later crashes (the crash did not always occur at the time the
aliases were loaded -- only the first time a command was issued.)
-- Jay
Now that I switched to global aliases, my version-9 alias file loads
without problem. (Under version 9, I had no problem loading the file
with local aliases.)
I must say that the uncontrolled failure in version 10 is disappointing.
There is no warning message -- just a complete crash. It would be
gracious if the alias loader would check for enough space and fail with
an error message rather than leaving the alias storage messed up so that
the system later crashes (the crash did not always occur at the time the
aliases were loaded -- only the first time a command was issued.)
-- Jay
- May
- 3,515
- 5
Alias Load Failure with Version 10
rconn wrote:
| vefatica wrote:
|
|
| ---Quote---
|| I use global lists. MEMORY reports
||
|| 262,144 characters total alias
|| 261,466 characters free
||
|| 131,072 characters total function
|| 131,019 characters free
||
|| These are both twice the values mentioned in limitations.htm and
|| alias.htm.
||
|| Do we have any control over the size of global alias and function
|| lists?
| ---End Quote---
| You cannot specify the initial size, and you cannot resize global
| lists.
Why?
I seem to recall that global list allocations are nominal, as they use their
total allocated sizes in virtual address space, but those pages which are
completely free never actually use physical storage, so in Vince's above
case aliases and functions would each have only 1 page of physical memory.
Is this correct?
BTW, my own global tables are substantially bigger (see below), but I'd
never had storage allocation problems.
262,144 characters total alias
212,622 characters free
131,072 characters total function
124,956 characters free
--
Steve
rconn wrote:
| vefatica wrote:
|
|
| ---Quote---
|| I use global lists. MEMORY reports
||
|| 262,144 characters total alias
|| 261,466 characters free
||
|| 131,072 characters total function
|| 131,019 characters free
||
|| These are both twice the values mentioned in limitations.htm and
|| alias.htm.
||
|| Do we have any control over the size of global alias and function
|| lists?
| ---End Quote---
| You cannot specify the initial size, and you cannot resize global
| lists.
Why?
I seem to recall that global list allocations are nominal, as they use their
total allocated sizes in virtual address space, but those pages which are
completely free never actually use physical storage, so in Vince's above
case aliases and functions would each have only 1 page of physical memory.
Is this correct?
BTW, my own global tables are substantially bigger (see below), but I'd
never had storage allocation problems.
262,144 characters total alias
212,622 characters free
131,072 characters total function
124,956 characters free
--
Steve
- Jun
- 608
- 6
Alias Load Failure with Version 10
> It's a bug in the memory allocator; it's been fixed
> in build 38.
Excellent!
Now it would be nice if you could figure out (and fix) why F6 does not
bring up the directory history under WinXP. Or did one of the many
messages I missed have a solution to that problem?
-- Jay
> It's a bug in the memory allocator; it's been fixed
> in build 38.
Excellent!
Now it would be nice if you could figure out (and fix) why F6 does not
bring up the directory history under WinXP. Or did one of the many
messages I missed have a solution to that problem?
-- Jay
- May
- 13,418
- 190
Alias Load Failure with Version 10
On Sun, 18 Jan 2009 18:48:17 -0600, Steve Fábián <> wrote:
I think so (we'll see what Rex says). The global lists are views of memory
mapped files backed up by the page file. I suppose that TCC doesn't try to
access anything beyond my few aliases (their end marked with a double NUL) and
that consequently Windows doesn't commit more pages that it needs to.
On Sun, 18 Jan 2009 18:48:17 -0600, Steve Fábián <> wrote:
I think so (we'll see what Rex says). The global lists are views of memory
mapped files backed up by the page file. I suppose that TCC doesn't try to
access anything beyond my few aliases (their end marked with a double NUL) and
that consequently Windows doesn't commit more pages that it needs to.
- Jun
- 608
- 6
Alias Load Failure with Version 10
Rex,
Do you plan to do anything about the memory assigned for local aliases
and functions? I'm running build 38, and with the local aliases option
checked, TCC bombs.
The help file on limitations gives figures for global values but says
nothing about local values. I would certainly like to see more than 16K.
-- Jay
Rex,
Do you plan to do anything about the memory assigned for local aliases
and functions? I'm running build 38, and with the local aliases option
checked, TCC bombs.
The help file on limitations gives figures for global values but says
nothing about local values. I would certainly like to see more than 16K.
-- Jay