Hello everybody!

I have Golded+ install on a Linux machine. The window that Golded opens
up in is set to 80x24 currently. Which seems to please Golded just fine.

But... I currently have a 45 inch monitor in use and would like to use
more than the current 25% of the screen that the Golded window occupies.

Is this both a Linux and Golded thing? If I try to increase the window
size using Linux then Golded gets all "Squirlly". Especially when I try to scroll.

In time I will figure out the problem AND solution. <g> But I thought
some wise soul might have a quicker solution. The max resolution via
HDMI is 1280x720 (16:9) with this particular plasma monitor (TV).

I am suspecting that Golded might have some display limitations. In the
past I have only used Golded using a 17 monitor on a Win32 machine.



Jeff




--- GoldED+/LNX 1.1.5-b20161221
* Origin: The OuijaBoard Too - Anoka. MN (1:282/1032)

Hi Jeff!

23 Jan 2017 00:18, from Jeff Smith -> All:

I am suspecting that Golded might have some display limitations.
In the past I have only used Golded using a 17 monitor on a
Win32 machine.

I did not see any issues.
When you change the terminal size, you need to restart godled.
Then it will use the complete available space.

CU, Ricsi

--- GoldED+/LNX
* Origin: Good day for flying but bad day for landing ... (2:310/31)

Hello Richard!

23 Jan 17 10:49, you wrote to me:

Hi Jeff!

23 Jan 2017 00:18, from Jeff Smith -> All:

I am suspecting that Golded might have some display limitations.
In the past I have only used Golded using a 17 monitor on a
Win32 machine.

I did not see any issues.
When you change the terminal size, you need to restart godled.
Then it will use the complete available space.

Telling Linux to enlarge that window and restarting Golded causes Golded to
use the same portion of a larger window. Telling both Linux and Golded to
use the same size terminal window allows Golded to "Fill Out" the window that it is running in. I have edited the window profile to maintain the settings
for when Golded is loaded in the future.

As a sidenote. I have tried to use an edited version of the "Advanced.cfg" file
for
Golded but something in the "Advanced" version causes Golded to fail to open at
all.
Golded opens fine using the basic config. As a result I am slowly adding keywords and
parameters from the advanced version as I see the need. So far Golded hasn't quit
loading. <g>

Jeff


--- GoldED+/LNX 1.1.5-b20161221
* Origin: The OuijaBoard Too - Anoka. MN (1:282/1032)

Hello Jeff!

23 Jan 17, Jeff Smith wrote to All:

But... I currently have a 45 inch monitor in use and would like to use more than the current 25% of the screen that the Golded window
occupies.

That's simple. Just open other programms, place their windows on your desktop and all screen space is occupied. ;)

Is this both a Linux and Golded thing?

Yes.

If I try to increase the window size using Linux then Golded gets all "Squirlly". Especially when I try to scroll.

I have the same issue if i change the size of the ssh terminal. But golded does
a correct screen redraw after a restart in that big window. The problem is, 1k
mails still fill only the upper area of a big screen.

I am suspecting that Golded might have some display limitations.

There is a DISPMARGIN keyword that limits the width. But the default is 0 and ueses the full screen width. Search the docs for width if you want to know if there are other limitations.

To fill the TV screen try to increase the font size of the terminal (window).

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/1351.7)

On 2017 Jan 23 00:18:00, you wrote to All:

Is this both a Linux and Golded thing?

no... it is a golded thing... linux doesn't care about the height or width AFAIK...

If I try to increase the window size using Linux then Golded gets all "Squirlly". Especially when I try to scroll.

my terminal screens are 197x62... someone recently reported a problem with wider screens... i suspect there's a problem in that golded is probably using a
byte counter for the width... a byte counter has a max of 255 columns and anything wider than that will roll back to zero and start over...

In time I will figure out the problem AND solution. <g> But I thought
some wise soul might have a quicker solution. The max resolution via
HDMI is 1280x720 (16:9) with this particular plasma monitor (TV).

I am suspecting that Golded might have some display limitations. In
the past I have only used Golded using a 17 monitor on a Win32
machine.

try a test... set your terminal width to 255 and see if golded works... then try 256 and see if it craps... 256 should be the same as zero if my suspicion above is right...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... A thing is not proved just because no one has ever questioned it.
---
* Origin: (1:3634/12.73)

Hello mark!

If I try to increase the window size using Linux then Golded gets
all "Squirlly". Especially when I try to scroll.

my terminal screens are 197x62... someone recently reported a problem
with wider screens... i suspect there's a problem in that golded is probably using a byte counter for the width... a byte counter has a
max of 255 columns and anything wider than that will roll back to zero
and start over...

In testing I have found that if I increase the terminal screen beyound
132x39 then Golded starts to have problems. If I go beyond 132 then the terminal window extends beyond the edge of the screen on the right.

I will do some more testing with screen size and display font in both
Linux and Golded to achieve a balance between what I thinks looks good
and what both Linux and Golded can deal with.

I am suspecting that Golded might have some display limitations.
In the past I have only used Golded using a 17 monitor on a Win32
machine.

try a test... set your terminal width to 255 and see if golded
works... then try 256 and see if it craps... 256 should be the same as zero if my suspicion above is right...

Will do and advise. Typing this with it set to 132 and Golded is displaying everything in it's proper and expected location on the screen. And the terminal window fills the desktop display area.

That all having been said I still catch myself ending my lines manually at 80 charactors. <g> Which also looks to be the average limit on the messages that I
read.

For S-N-G's the above two lines (Well one anyway) are 129 charactors long. <g>


Jeff


--- GoldED+/LNX 1.1.5-b20161221
* Origin: The OuijaBoard Too - Anoka. MN (1:282/1032)

23 Jan 17 00:18, you wrote to all:

I have Golded+ install on a Linux machine. The window that Golded
opens up in is set to 80x24 currently. Which seems to please Golded
just fine.

But... I currently have a 45 inch monitor in use and would like to use more than the current 25% of the screen that the Golded window
occupies.

I am too impatient to enlarge, start Golded, rinse, repeat to find the limit where things break...

BUT

On my 26-50" screens full screen terminals will break golded starting, period,

THere is a patch: https://fidonet.ozzmosis.com/echomail.php/golded/37e10bdf0c33c539.html

The patch below fixes a bug where a very wide terminal causes GoldED to crash:

---------- Fri 21 Nov 14, GoldED+/BSD 1.1.5-b20130910 (Nov 16 2014 22:19:02)
! 23:02:48 Memory error at [gemlst.cpp,365].
! 23:02:48 gsprintf(buffer,256,%-5.5s%s%-*.*s %-*.*s%s%-*.*s %s,...):
buffer overflow (need 381 bytes).


Index: gemlst.cpp ===================================================================
RCS file: /cvsroot/golded-plus/golded+/golded3/gemlst.cpp,v
retrieving revision 1.67
diff -u -r1.67 gemlst.cpp
-+- gemlst.cpp 19 Oct 2011 23:31:31 -0000 1.67
+++ gemlst.cpp 22 Nov 2014 16:50:45 -0000
{at}{at} -333,7 +333,7 {at}{at}
mattr_ = hattr;
}

- char buf[256];
+ char buf[2560];

if(AA->Msglistwidesubj()) {
resiz += tosiz + 1;


Which does let wide terminals work... I've done it to all the ones of recent...
and works.

BUT

ONLY FOR READING

If you reply the internal editor barfs and seg faults... for probably similar reasons... but I just don't have time to dig through to find its buffer to enlarge it.


Rick


... Ding Dong the Witch is DEAD! I Made America Great Again! President Trump! --- GoldED+/LNX 1.1.5-b20161221
* Origin: Vina's Talos Moon Base Alpha (1:135/377)

On 2017 Jan 26 13:03:06, you wrote to me:

If I try to increase the window size using Linux then Golded gets
all "Squirlly". Especially when I try to scroll.

my terminal screens are 197x62... someone recently reported a problem
with wider screens... i suspect there's a problem in that golded is
probably using a byte counter for the width... a byte counter has a
max of 255 columns and anything wider than that will roll back to
zero and start over...

In testing I have found that if I increase the terminal screen beyound 132x39 then Golded starts to have problems. If I go beyond 132 then
the terminal window extends beyond the edge of the screen on the
right.

i forgot to mention that my GUI dimensions are 1600x1200 at this time... this is one reason why i can have such TUI widths... are you running your golded in an xterm in a GUI or are you running it bare in a TUI??

I will do some more testing with screen size and display font in both Linux and Golded to achieve a balance between what I thinks looks good
and what both Linux and Golded can deal with.

I am suspecting that Golded might have some display limitations. In
the past I have only used Golded using a 17 monitor on a Win32
machine.

try a test... set your terminal width to 255 and see if golded
works... then try 256 and see if it craps... 256 should be the same
as zero if my suspicion above is right...

Will do and advise. Typing this with it set to 132 and Golded is displaying everything in it's proper and expected location on the
screen. And the terminal window fills the desktop display area.

That all having been said I still catch myself ending my lines
manually at 80 charactors. <g> Which also looks to be the average
limit on the messages that I read.

yeah, don't do that... let the readers' terminals wrap the lines to their widths... only charts and tables are traditionally forced widths less than 79 characters...

For S-N-G's the above two lines (Well one anyway) are 129 charactors
long. <g>

Jeff

--- GoldED+/LNX 1.1.5-b20161221

FWIW: look at my PID... your version is newer than mine... i'm not sure what the differences are between them, though...

* Origin: The OuijaBoard Too - Anoka. MN (1:282/1032)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Age doesn't show here, but immaturity sure does.
---
* Origin: (1:3634/12.73)

Hi Jeff!

23 Jan 2017 04:45, from Jeff Smith -> Richard Menedetter:

I did not see any issues.
When you change the terminal size, you need to restart godled.

Telling Linux to enlarge that window and restarting Golded causes
Golded to use the same portion of a larger window. Telling both Linux
and Golded to use the same size terminal window allows Golded to "Fill Out" the window that it is running in. I have edited the window
profile to maintain the settings for when Golded is loaded in the
future.

I do not really understand what you mean by tellinf Linux and Golded.

I have a terminal window.
If I make it bigger and restart Ged+ it will use the space.
Like this:
https://vserv.ricsi.priv.at/ged.png

As a sidenote. I have tried to use an edited version of the
"Advanced.cfg" file for Golded but something in the "Advanced" version causes Golded to fail to open at all.

What error do you get?

CU, Ricsi

--- GoldED+/LNX
* Origin: Nobody notices when things go right (2:310/31)

Hello Richard,

Telling Linux to enlarge that window and restarting Golded causes
Golded to use the same portion of a larger window. Telling both Linux
and Golded to use the same size terminal window allows Golded to "Fill
Out" the window that it is running in. I have edited the window
profile to maintain the settings for when Golded is loaded in the
future.

I do not really understand what you mean by tellinf Linux and Golded.
I have a terminal window.

If I make it bigger and restart Ged+ it will use the space.

Here, if I use a a terminal window larger than what Golded seems to like Golded (After a restart) will use a portion of that window. If I make the window larger than the display (The window extends off the screen) then the Golded display is pretty much unreadable. And things like message date and time
are not displayed. And scrolling causes the Golded display to be garbled and pretty much unreadable. I have found a terminal display setting that both Golded and Linux seem to be happy with.

Like this:
https://vserv.ricsi.priv.at/ged.png

That is pretty much what I see now with the terminal set to 132x39. Any larger than that and Golded is unhappy.

As a sidenote. I have tried to use an edited version of the
"Advanced.cfg" file for Golded but something in the "Advanced" version
causes Golded to fail to open at all.

What error do you get?

No error at all. I am simply returned to the terminal command prompt. If I use the simple CFG file then Golded opens up fine. I am slowly adding necessary keywords to see if and when Golded fails to load. I suspect that there is a keyword that is causing the problem.

Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: The OuijaBoard - Anoka, MN (1:282/1031)

Hi Jeff!

29 Jan 2017 06:42, from Jeff Smith -> Richard Menedetter:

Like this:
https://vserv.ricsi.priv.at/ged.png

That is pretty much what I see now with the terminal set to 132x39.
Any larger than that and Golded is unhappy.

Ah OK ... I set my fonts to biiiig and my laptop resolution is not that high. So I simply do not see that behavior.
That explains.

As a sidenote. I have tried to use an edited version of the
"Advanced.cfg" file for Golded but something in the "Advanced"
version causes Golded to fail to open at all.

What error do you get?

No error at all. I am simply returned to the terminal command prompt.

Try gedlnx |less

That is a negative remnant from the DOS legacy on linux.

CU, Ricsi

--- GoldED+/LNX
* Origin: Happiness is having ALL Star Trek shows on videotape! (2:310/31)

On 2017 Jan 27 11:08:12, Rick Christian wrote to Jeff Smith:

yes, i know this is old and i'm top posting... sorry...

i've spent the last day hunting down this patch because my golded+ was crashing
with "stack smashing detected"... yeah, i was running my terminal window at max
screen size which is now 271x70... if i drop to 256x70, i can read but, as noted below, the internal editor craps the sheets... dropping back to 255x70 allows both to work... i am NOT using the patch... it didn't seem to do any good either way and i was still limited in max COLSxROWS... i even added a second zero to make the buf larger and that didn't help, either... the problem is the same with my old golded using the code from cvs and this new one using the latest code from github... it is really starting to look like there's a byte size counter somewhere that is the real problem... i hate that my C/C++ skills are non-existant these days :(

I am too impatient to enlarge, start Golded, rinse, repeat to find the limit where things break...

BUT

On my 26-50" screens full screen terminals will break golded starting, period,

THere is a patch: https://fidonet.ozzmosis.com/echomail.php/golded/37e10bdf0c33c539.html

The patch below fixes a bug where a very wide terminal causes GoldED to crash:

---------- Fri 21 Nov 14, GoldED+/BSD 1.1.5-b20130910 (Nov 16 2014 22:19:02) ! 23:02:48 Memory error at [gemlst.cpp,365]. ! 23:02:48 gsprintf(buffer,256,%-5.5s%s%-*.*s %-*.*s%s%-*.*s %s,...): buffer overflow (need 381 bytes).

Index: gemlst.cpp ===================================================================
RCS file: /cvsroot/golded-plus/golded+/golded3/gemlst.cpp,v
retrieving revision 1.67
diff -u -r1.67 gemlst.cpp
-+- gemlst.cpp 19 Oct 2011 23:31:31 -0000 1.67
+++ gemlst.cpp 22 Nov 2014 16:50:45 -0000
{at}{at} -333,7 +333,7 {at}{at}
mattr_ = hattr;
}

- char buf[256];
+ char buf[2560];

if(AA->Msglistwidesubj()) {
resiz += tosiz + 1;

Which does let wide terminals work... I've done it to all the ones of recent... and works.

BUT

ONLY FOR READING

If you reply the internal editor barfs and seg faults... for probably similar reasons... but I just don't have time to dig through to find its buffer to enlarge it.

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... When I spilled my cottage cheese, I lost my whey.
---
* Origin: (1:3634/12.73)

On 2018 Dec 29 09:03:38, I wrote to all:

On 2017 Jan 27 11:08:12, Rick Christian wrote to Jeff Smith:

yes, i know this is old and i'm top posting... sorry...

i've spent the last day hunting down this patch because my golded+ was crashing with "stack smashing detected"...

i forgot to post that...


----- snip -----

Pick New Area: +-G-Description----------------------------------------EchoID--------------------------New---Msgs------------------------------------------------------------------------------------------------------------------------------------------------------------- ----------------+

|---Netmail areas--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ----|
| NetMailArea NetMailArea
0 1071 *** stack smashing detected ***: /home/wkitty42/fido/bin/gedlnx terminated |
| Aborted (core dumped) |
----- snip -----


it always gets the netmail area, as above, and then dies... 255x70 works, 256x70 does not...


)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... URA True Northerner if sittin on yer deck shootin ravens is fun.
---
* Origin: (1:3634/12.73)

29 Dec 18 09:03, you wrote to all:

i've spent the last day hunting down this patch because my golded+ was crashing with "stack smashing detected"... yeah, i was running my
terminal window at max screen size which is now 271x70... if i drop to 256x70, i can read but, as noted below, the internal editor craps the sheets... dropping back to 255x70 allows both to work... i am NOT using the patch... it didn't seem to do any good either way and i was still limited in max COLSxROWS... i even added a second zero to make the buf larger and that didn't help, either... the problem is the same with my
old golded using the code from cvs and this new one using the latest
code from github... it is really starting to look like there's a byte
size counter somewhere that is the real problem... i hate that my C/C++ skills are non-existant these days :(

I wrote the first patch for that back in 2014 but it was never accepted upstream.

Consequently the current version of GoldED still has that bug.

I never tested >255 char wide screens with the editor, partly because my fix wasn't accepted upstream, so I forgot about submitting any more patches, but mainly because I never use terminals that large and I didn't expect anyone else
to.

See the next series of messages for my fixes to the bugs I know about. Be warned I haven't tested them extensively with very large terminals so you're likely to encounter more crashes.

--- GoldED+/BSD 1.1.5-b20180707
* Origin: Blizzard of Ozz, Melbourne, Victoria, Australia (3:633/267)

On 2018 Dec 31 06:29:42, you wrote to me:

I wrote the first patch for that back in 2014 but it was never
accepted upstream.

yeah, i know/remember... they were the first to show up in my local searches...
i was actually looking for a simple golded compilation script that i thought someone had posted but i wasn't able to find what i thought i remembered... not
even after spending a few hours digging back through ozzmosis...

Consequently the current version of GoldED still has that bug.

yep... funny thing is, once i remembered how to compile golded and got the latest code, i was still seeing the "stack smashing" crash... it wasn't until is suddenly dawned on me that i had rebooted the system and this new wide screen monitor was now better recognized that i got my first clue about the terminal width being the problem... so i went looking for the "[2560]" patch to
be sure where to put it... it didn't help and i still had the same problem... so i took that patch back out and built again... then i tried dropping my terminal width and loading golded... that's how i figured out the 255 width limit... heighth didn't seem to matter... the real thing that initially threw me off was the error message changed to the "stack smashing" one... that almost
lead me down the wrong rabbit hole at first...

I never tested >255 char wide screens with the editor, partly because
my fix wasn't accepted upstream, so I forgot about submitting any more patches, but mainly because I never use terminals that large and I
didn't expect anyone else to.

hehehe... yeah, i spend almost all of my time in one of over a dozen terminal windows i have open at any one time... the majority of them are opened max (fullscreen?)... on this new monitor, that's 271x70 with my current configuration...

See the next series of messages for my fixes to the bugs I know about.
Be warned I haven't tested them extensively with very large terminals
so you're likely to encounter more crashes.

i will look...

i am happy to say that something certainly has been corrected since my last code update and build... i wasn't able to do any nodelist lookups but now that seems to work... i think i have a little more work to do to get the nodelist stuff working properly (ie: name lookups) but i'll get to that at some point...
if anyone has any pointers, they'd be appreciated... right now my nodelist is being compiled into three goldnode.gx[aln] files...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Give up, you'll only live till you die.
---
* Origin: (1:3634/12.73)

On 2018 Dec 30 16:21:38, I wrote to you:

See the next series of messages for my fixes to the bugs I know
about. Be warned I haven't tested them extensively with very large
terminals so you're likely to encounter more crashes.

i will look...

NOTE: the 3rd time is the charm? my previous attempts crashed when i hit CTRL-Z
to bring up the menu to save and exit... luckily i was able to find the below text of my original post in golded.tmp and rescue it before trying again... i'm
doing this in the known working 255x70 terminal... i'll try 256 in a minute and
if that works, then larger until it crashes but i think we know what'll happen... i'll also try to remember to grab that crash message this time... might still have the last ones in the terminal scroll back buffer ;)


i've applied those fixes and am now reading and writing this reply in a maximized terminal window of 217x70... so far, this initial test seems to be ok... let's see what happens when i save this reply and move on to another area... if you get this message, then i guess everything is working as needed ;)

i guess i should probably update my version number somehow to show that this is
a custom build of the code i have with your patches applied...


)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Happy Holidays and a Wonderful 2011 to you and yours!
---
* Origin: (1:3634/12.73)

On 2018 Dec 30 16:54:54, I wrote to you:

trying again... i'm doing this in the known working 255x70 terminal... i'll try 256 in a minute and if that works, then larger until it
crashes but i think we know what'll happen... i'll also try to
remember to grab that crash message this time... might still have the
last ones in the terminal scroll back buffer ;)

well, dammit... i've just written a test message, a G reply to that message and
a Q reply to /that/ message... all at 271x70 and everything works... they're over in FIDOTEST, FWIW...

i wasn't able to catch those last crash codes... i'll do that the next time it happens...

how would i run golded in gdb so it can find the proper source code lines? that
might be complicated by me running golded via the cp437 tool that converts cp437 characters to the proper ones for display on the screen... hummm...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... All of my voices listen to different radio stations.
---
* Origin: (1:3634/12.73)

On 2018 Dec 30 17:07:28, I wrote to you:

i wasn't able to catch those last crash codes... i'll do that the next

time

it happens...

got it! looks to maybe be related to having long lines covering the full screen
width... if i keep the lines short, no problem... this one is maybe 3/4s of my screen width...
whatever it is, it seems to happen when i CTRL-Z to save the message... maybe it has something to do with processing golded.tmp and getting the message body from there?

sooo, on the crash, some information scrolls off the screen and i can't get to it... but i did get a screen shot... it ain't pretty...

http://sestar.synchro.net/temp/20181230-golded-widescreen-crash-event.jpg

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Today's mood: cranky with a touch of psycho
---
* Origin: (1:3634/12.73)

Hi! mark,

On 30 Dec 18 16:21, you wrote to andrew clarke:

i am happy to say that something certainly has been corrected since my last code update and build... i wasn't able to do any nodelist lookups
but now that seems to work... i think i have a little more work to do
to get the nodelist stuff working properly (ie: name lookups) but i'll
get to that at some point... if anyone has any pointers, they'd be appreciated... right now my nodelist is being compiled into three goldnode.gx[aln] files...

Those three files are created here as well. I have these entries in my GoldEd.cfg (they are the only nodelist related statements, BTW):

--- 8< ---
; The path to your nodelists.
; NOTE: This keyword MUST be in GOLDED.CFG!!!
NODEPATH /opt/ftn/fido/nodelist/

; Filenames of your nodelists.
; If extention is ".*" or ".999", the newest is used automatically.
; NOTE: This keyword MUST be in GOLDED.CFG!!!
; xxx use daily lists from 22 August 2018...
; xxxx NODELIST nodelist.999
NODELIST z3daily.999

; Uncomment this to use Version 7 nodelist indexes.
;xxxxNODEPATHV7 /opt/ftn/fido/nodelist/

; Uncomment this to use a raw FIDOUSER.LST file.
;xxxxFIDOUSERLIST fidouser.lst

; Where to allow nodelist lookup when entering messages.
LOOKUPNET YES
LOOKUPECHO NO
LOOKUPLOCAL NO
--- >8 ---

When the daily nodelist is unpacked, the following code updates the index files:

--- 8< ---
cd /opt/ftn/fido/exteditor
./gnlnx -force
--- >8 ---

But you probably already knew that bit. Oops. :)

Cheers,
Paul.

... Dark Shadows - https://www.youtube.com/watch?v=KwleloRuaEw
--- GoldED+/LNX 1.1.5-b20130515
* Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)

On 2018 Dec 31 10:16:42, you wrote to me:

to get the nodelist stuff working properly (ie: name lookups) but i'll
get to that at some point... if anyone has any pointers, they'd be
appreciated... right now my nodelist is being compiled into three
goldnode.gx[aln] files...

Those three files are created here as well. I have these entries in my GoldEd.cfg (they are the only nodelist related statements, BTW):

i have the same and the same ones commented out, too...

When the daily nodelist is unpacked, the following code updates the
index files:

i'll try to remember that... mine were generated automatically earlier... i guess when GE started or maybe i keyed something that did it from inside GE? i dunno... i'll remember that command, though...

But you probably already knew that bit. Oops. :)

i hadn't quite got that far yet :lol: -=B-b

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Let your life dance lightly on the edges of time like the dew on a leaf. ---
* Origin: (1:3634/12.73)