Can someone point me at some instructions on how to use GoldED+ as an editor in Synchronet?
Re: using GoldED+ as editor
By: Michael Trip to All on Sat May 09 2015 19:58:44
Can someone point me at some instructions on how to use GoldED+ as
an editor in Synchronet?
I dont think you can use Golded as an internal editor, however, you CAN use it to readthe message base externally
I added the following two lines the area where the AREAFILE section is.
AREAFILE Synchronet \\bbs\c\SBBS\ctrl\msgs.cnf
AREAFILE Synchronet \\bbs\c\SBBS\ctrl\areas.bbs
Since I am reading it over my local network I had to use the \\ and full path to the computer Synchronet is located.
Hello,
Can someone point me at some instructions on how to use GoldED+ as an editor in Synchronet?
i read all realted to golded to be use , i found this msg
I did it's work but can the screen be longger 80x60 with golded+
Does the GoldEd+ documentation mention Synchronet? I would expect it to have the instructions.
Re: using GoldED+ as editor
By: Digital Man to Michael Trip on Sun May 10 2015 18:37:28
Does the GoldEd+ documentation mention Synchronet? I would expect it to have the instructions.
Nope. I found out from somebody else several years ago, how to make it read Synchronet Message base. Simple matter really, but I don't think it can be used as an internal editor.
Hello,
Can someone point me at some instructions on how to use GoldED+ as an editor in Synchronet?
Does the GoldEd+ documentation mention Synchronet? I would expect it to
have the instructions.
Nope. I found out from somebody else several years ago, how to make it
read Synchronet Message base. Simple matter really, but I don't think it can be used as an internal editor.
Does the GoldEd+ documentation mention Synchronet? I would expect
it to have the instructions.
Nope. I found out from somebody else several years ago, how to make
it read Synchronet Message base. Simple matter really, but I don't
think it can be used as an internal editor.
Right, I didn't mean to imply that it could be used as a message reader for the
BBS user.
it read Synchronet Message base. Simple matter really, but I don't
think it can be used as an internal editor.
you might be able to rig something with doorway.
you might be able to rig something with doorway.
Perhaps. There however we run into the 32 bit limitation. I doubt it will work on a 54 bit OS, as Doorway is 16 bit, if I remember correctly
Re: using GoldED+ as editor
By: Mro to Joe Delahaye on Mon May 11 2015 16:41:59
it read Synchronet Message base. Simple matter really, but I don't
think it can be used as an internal editor.
you might be able to rig something with doorway.
Perhaps. There however we run into the 32 bit limitation. I doubt it will work on a 54 bit OS, as Doorway is 16 bit, if I remember correctly
Perhaps. There however we run into the 32 bit limitation. I doubt it
will work on a 54 bit OS, as Doorway is 16 bit, if I remember
correctly
i dont run my bbs on a 64bit os. makes it sort of hard for the doorgames and other 16bit utils.
i dont run my bbs on a 64bit os. makes it sort of hard for the
doorgames and other 16bit utils.
Agreed. My system sits on a 32 bit Vista. There are however people out there on a 64 bit system these days, since preloaded computers come that way. Thus while your suggestion might work on my system, not so much on others.
Running a BBS is fairly niche thing these days. I think installing a 32-bit OS to run DOS doors is par for the course. It's similar to getting into any other hobby, like R/C cars or model planes - There are some things you're going to just have to know about in order to get it working. That said, I've heard of people running DOS doors in 64-bit Linux distributions - I believe Dosemu would work for that. I've wondered if there's a way to rig Dosemu in 64-bit editions of Windows to get DOS doors to work.
Nightfox wrote to Joe Delahaye <=-
Running a BBS is fairly niche thing these days. I think installing a 32-bit OS to run DOS doors is par for the course. It's similar to
getting into any other hobby, like R/C cars or model planes - There are some things you're going to just have to know about in order to get it working.
Perhaps. There however we run into the 32 bit limitation. I doubt it
will work on a 54 bit OS, as Doorway is 16 bit, if I remember
correctly
Deuce's cioxtrn is a native 32-bit alternative to Doorway, if that's what you're looking for.
distributions - I believe Dosemu would work for that. I've wondered if there's a way to rig Dosemu in 64-bit editions of Windows to get DOS doors to work.Not sure about dosemu, but I have a setup I've been meaning to try that uses dosbox to that effect.
aRunning a BBS is fairly niche thing these days. I think installing
are32-bit OS to run DOS doors is par for the course. It's similar to getting into any other hobby, like R/C cars or model planes - There
itsome things you're going to just have to know about in order to get
working.
Personally, with my BBS system facing the internet, I prefer to have
some separation from my home systems -- either a physical box separate
from my home system or a VM that I can isolate from the rest of my
data.
Running a 32 bit OS just for the OS doesn't limit my home desktop that
way.
Running a BBS is fairly niche thing these days. I think installing a 32-bit OS to run DOS doors is par for the course. It's similar to getting into any other hobby, like R/C cars or model planes - There are some things you're going to just have to know about in order to get it working. That said, I've heard of people running DOS doors in 64-bit Linux distributions - I believe Dosemu would work for that. I've wondered if there's a way to rig Dosemu in 64-bit editions of Windows to get DOS doors to work.
Agreed. My system sits on a 32 bit Vista. There are however people out there on a 64 bit system these days, since preloaded computers come that way. Thus while your suggestion might work on my system, not so much on others.
64-bit Linux distributions - I believe Dosemu would work for that.
I've wondered if there's a way to rig Dosemu in 64-bit editions of
Windows to get DOS doors to work.
I've also h eard of people fighting withe Dosemu to get doors to work <G>
I've wondered if there's a way to rig Dosemu in 64-bit editions of
Windows to get DOS doors to work.
for Linux, I've heard that Synchronet has
some amount of support for Dosemu built in, so it's not terribly difficult to get it running for DOS doors.
for Linux, I've heard that Synchronet has
some amount of support for Dosemu built in, so it's not terribly difficult to get it running for DOS doors.
there is a bit more tinkering and configuration than on a windows 32bit system
I don't know about Windows, but for Linux, I've heard that Synchronet has some amount of support for Dosemu built in, so it's not terribly difficult to get it running for DOS doors.
I dont think you can use Golded as an internal editor, however, you CAN use it to readthe message base externally
I added the following two lines the area where the AREAFILE section is.
AREAFILE Synchronet \\bbs\c\SBBS\ctrl\msgs.cnf
AREAFILE Synchronet \\bbs\c\SBBS\ctrl\areas.bbs
AREAFILE Synchronet \\bbs\c\SBBS\ctrl\msgs.cnf
AREAFILE Synchronet \\bbs\c\SBBS\ctrl\areas.bbs
Out of curiousity I downloaded GoldEd+ and tried to set it up to read messages on my BBS. I've specified my areafile configuration as you've pointed out above. When I try to open a message area in GoldEd+ though, I'm getting an error that looks like GoldEd+ is trying to use something called SMBOpen and it can't find SMBOpen. For example:
I did a file search on my BBS machine, hoping that SMBOpen might be a command-line executable included with Synchronet or other software, but I don't have any files called SMBOpen. Have you (or anyone else) encountered that error before?
AREAFILE Synchronet \\bbs\c\SBBS\ctrl\msgs.cnf
AREAFILE Synchronet \\bbs\c\SBBS\ctrl\areas.bbs
I did a file search on my BBS machine, hoping that SMBOpen might be
a command-line executable included with Synchronet or other
software, but I don't have any files called SMBOpen. Have you (or
anyone else) encountered that error before?
Not that I remember. Did you add both lines in the same place where the rest of the AREAFILE lines are? Perhaps there is a change in the later versions of Golded+ Mine is Gedwin.exe date 2011-03-21
Yes, I put both of those lines in there. The version I downloaded is dated 2013-02-10, so I tried downloading the one you have but it displays the same error.
I did a file search on my BBS machine, hoping that SMBOpen might be a command-line executable included with Synchronet or other software, but I don't have any files called SMBOpen. Have you (or anyone else) encountered that error before?
I did a file search on my BBS machine, hoping that SMBOpen might
be a command-line executable included with Synchronet or other
software, but I don't have any files called SMBOpen. Have you (or
anyone else) encountered that error before?
I tried to find that on both this Windows 8.1 64 bit machine, and
the 32 bit Vista BBS machine. Golded+ works on both and I too
cannot find that file SMBOpen
I tried to find that on both this Windows 8.1 64 bit machine, and
the 32 bit Vista BBS machine. Golded+ works on both and I too
cannot find that file SMBOpen
it is probably a function in a dll or other shared object file...
On Mon, 18 May 2015, Joe Delahaye wrote to Nightfox:
I did a file search on my BBS machine, hoping that SMBOpen might
be a command-line executable included with Synchronet or other software, but I don't have any files called SMBOpen. Have you (or anyone else) encountered that error before?
I tried to find that on both this Windows 8.1 64 bit machine, and
the 32 bit Vista BBS machine. Golded+ works on both and I too
cannot find that file SMBOpen
it is probably a function in a dll or other shared object file...
Re: using GoldED+ as editor
By: Joe Delahaye to Michael Trip on Sat May 09 2015 20:27:43
I dont think you can use Golded as an internal editor, however, you CAN use it to readthe message base externally
I added the following two lines the area where the AREAFILE section is.
AREAFILE Synchronet \\bbs\c\SBBS\ctrl\msgs.cnf
AREAFILE Synchronet \\bbs\c\SBBS\ctrl\areas.bbs
Out of curiousity I downloaded GoldEd+ and tried to set it up to read messages on my BBS. I've specified my areafile configuration as you've pointed out above. When I try to open a message area in GoldEd+ though, I'm getting an error that looks like GoldEd+ is trying to use something called SMBOpen and it can't find SMBOpen. For example:
! 09:47:43 Open error exit at [gmosmb1.cpp,114].
! 09:47:43 Synchronet message base could not be opened (2 opening ..\data\sub : 09:47:43 ..\data\subs\DOVE-Net\dove-sys
: 09:47:43 WinNT 5.1.2600-SP3 iF6M10 reports error 2: No such file or directo ! 09:47:43 Function track dump follows:
- 09:47:43 00039937 SMBOpen
I did a file search on my BBS machine, hoping that SMBOpen might be a command-line executable included with Synchronet or other software, but I don't have any files called SMBOpen. Have you (or anyone else) encountered that error before?
I was thinking it is probably a function call, if not a file. If so, though, I'm not sure why GoldEd+ doesn't come with everything it needs in order to run. Unless Synchronet support is not a standard feature and there's an additional component I need to download somewhere.
it is probably a function in a dll or other shared object file...
I was thinking it is probably a function call, if not a file. If
so, though, I'm not sure why GoldEd+ doesn't come with everything
it needs in order to run. Unless Synchronet support is not a
standard feature and there's an additional component I need to
download somewhere.
! 09:47:43 Open error exit at [gmosmb1.cpp,114].
! 09:47:43 Synchronet message base could not be opened (2 opening
..\data\sub : 09:47:43 ..\data\subs\DOVE-Net\dove-sys
: 09:47:43 WinNT 5.1.2600-SP3 iF6M10 reports error 2: No such file or
directo ! 09:47:43 Function track dump follows:
- 09:47:43 00039937 SMBOpen
"SMBOpen" appears to be the name of the *function* that was executed and produced the error, not the name of the file. It could be that the relative path "..\data\subs\DOVE-Net\dove-sys" was not correct for the process executing GoldEd+ or perhaps it needs ".shd" appended to "dove-sys". I really have no experience with GoldEd+, but I'm pretty sure SMBOpen is not the filename it's trying to open.
I was thinking it is probably a function call, if not a file. If so,
though, I'm not sure why GoldEd+ doesn't come with everything it needs
in order to run. Unless Synchronet support is not a standard feature
and there's an additional component I need to download somewhere.
i used it to read my fidonet email. it always worked fine. i never did anything weird with golded though
i think it is something that has been added in recent times (last year or three)... but i don't use golded... this is only what i remember seeing discussed and subsequent reports of others that are using it with sbbs... you might want to inquire in the golded support echo on fidonet, though ;)
! 09:47:43 Open error exit at [gmosmb1.cpp,114].
! 09:47:43 Synchronet message base could not be opened (2 opening
..\data\sub : 09:47:43 ..\data\subs\DOVE-Net\dove-sys
: 09:47:43 WinNT 5.1.2600-SP3 iF6M10 reports error 2: No such file or
directo ! 09:47:43 Function track dump follows:
- 09:47:43 00039937 SMBOpen
"SMBOpen" appears to be the name of the *function* that was executed and produced the error, not the name of the file. It could be that the relative path "..\data\subs\DOVE-Net\dove-sys" was not correct for the process executing GoldEd+ or perhaps it needs ".shd" appended to "dove-sys". I really have no experience with GoldEd+, but I'm pretty sure SMBOpen is not the filename it's trying to open.
! 09:47:43 Open error exit at [gmosmb1.cpp,114].
! 09:47:43 Synchronet message base could not be opened (2 opening
..\data\sub : 09:47:43 ..\data\subs\DOVE-Net\dove-sys
: 09:47:43 WinNT 5.1.2600-SP3 iF6M10 reports error 2: No such file or
directo ! 09:47:43 Function track dump follows:
- 09:47:43 00039937 SMBOpen
"SMBOpen" appears to be the name of the *function* that was
executed and produced the error, not the name of the file. It
could be that the relative path "..\data\subs\DOVE-Net\dove-sys"
was not correct for the process executing GoldEd+ or perhaps it
needs ".shd" appended to "dove-sys". I really have no experience
with GoldEd+, but I'm pretty sure SMBOpen is not the filename it's
trying to open.
Yeah, I thought I'd try doing a file search in case it was
referring to a file. I imagine it probably is the name of a
function.
based on the log and DM's response, where is your golded's starting directory?? perhaps you need to have it starting in the sbbs\ctrl directory or similar so that '..' does back up to your sbbs home directory and 'data\subs' will work properly from there...
Yeah, I ended up moving it to sbbs\GoldEd (previously I had it in a different directory), and that helped. Now it doesn't complain when it opens a message area - but now it's saying there are no messages in the area, even when I know there are messages there..
Yeah, I ended up moving it to sbbs\GoldEd (previously I had it in
a different directory), and that helped. Now it doesn't complain
when it opens a message area - but now it's saying there are no
messages in the area, even when I know there are messages there..
I have Golded in its own directory. Not as a subdirectory of
anything else. C:\Golded
Going from the suggestion that "..\data\subs\DOVE-Net\dove-sys" was
not the correct relative path from my GoldEd directory, I moved GoldEd into a directory sbbs\GoldEd on my system, and now I'm no longer
getting that error about SMBOpen. Now though, when I open a message
area, GoldEd shows there are no messages in the area.
Yeah, I'm not sure yet why it's not working for me. I'm not trying to do anything weird with it either; I only configured it as Joe Delahye suggested and tried reading a sub-board.
Yeah, I ended up moving it to sbbs\GoldEd (previously I had it in a
different directory), and that helped. Now it doesn't complain when
it opens a message area - but now it's saying there are no messages
in the area, even when I know there are messages there..
I have Golded in its own directory. Not as a subdirectory of anything else. C:\Golded
Going from the suggestion that "..\data\subs\DOVE-Net\dove-sys" was
not the correct relative path from my GoldEd directory, I moved
GoldEd into a directory sbbs\GoldEd on my system, and now I'm no
longer getting that error about SMBOpen. Now though, when I open a
message area, GoldEd shows there are no messages in the area.
At the area list screen, try hitting ALT-S to do a message scan before you go into those areas to read messages.
Going from the suggestion that "..\data\subs\DOVE-Net\dove-sys" was
not the correct relative path from my GoldEd directory, I moved
GoldEd into a directory sbbs\GoldEd on my system, and now I'm no
longer getting that error about SMBOpen. Now though, when I open a
message area, GoldEd shows there are no messages in the area.
At the area list screen, try hitting ALT-S to do a message scan
before you go into those areas to read messages.
That didn't seem to help. Now when I try to open any area, it says the area is locked, and it still shows 0 messages. It says I need to totally exit out, and then it crashes when I do so.
I have Golded in its own directory. Not as a subdirectory of
anything else. C:\Golded
right but you are using a complete path to your message areas instead of a relative path that starts without a '\' ;)
At the area list screen, try hitting ALT-S to do a message scan
before you go into those areas to read messages.
That didn't seem to help. Now when I try to open any area, it
says the area is locked, and it still shows 0 messages. It says I
need to totally exit out, and then it crashes when I do so.
I think I see (at least part of) what's going on. I have unique
internal code prefixes configured for all of my message groups in SCFG
to help ensure that there are no name conflicts (in case sub-boards in different message groups would happen to have the same internal code). That setting is the "Internal Code Prefix" setting in SCFG for each message group. GoldEd+ seems to be ignoring that - GoldEd+ created messagebase files for all my areas, without the group prefixes, and
they were all empty. So unless GoldEd+ can be configured to use the
group internal code prefixes, GoldEd+ might not work with my setup..
Do you know if GoldEd+ can be set up to use Synchronet's group
prefixes?
not work with my setup.. Do you know if GoldEd+ can be set up to use
Synchronet's group prefixes?
That's a possibility. Though if those directory locations are stored in msgs.cnf, it shouldn't be a problem. You'd probably have to grab the source of Golded and see how it parses msgs.cnf or something. Maybe noone has ever reported that as an issue since most people don't separate their groups like that.
Re: Re: using GoldED+ as editor
By: Accession to Nightfox on Thu May 21 2015 16:39:34
not work with my setup.. Do you know if GoldEd+ can be set up to use
Synchronet's group prefixes?
That's a possibility. Though if those directory locations are stored in msgs.cnf, it shouldn't be a problem. You'd probably have to grab the source of Golded and see how it parses msgs.cnf or something. Maybe noone has ever reported that as an issue since most people don't separate their groups like that.
I wasn't referring to the directories; I was referring to the internal code prefixes that Synchronet lets you configure in the message group settings. For instance, I've set up my DOVE-Net group to have the internal code prefix DOVE_, so for instance, the SYNCBAJA sub-board becomes DOVE_SYNCBAJA. What GoldEd+ was doing was making empty messagebase files without the prefix - so, using my same example, GoldEd+ was creating files named SYNCBAJA (instead of DOVE_SYNCBAJA), and they were empty.
I do have my message groups separated into different subdirectories too, but GoldEd+ actually seemed to recognize that. GoldEd+ placed its new files in the subdirectories that I have set up for my message groups.
really? that was one of the dances Max went through several times
before settling on her method... it sucked the first time she ran a
full %rescan on all message areas i carry on this system... the second time we were a little more prepared for the 50+Meg of traffic bundles
and made arrangements for plenty of room as well as enlarging the max
size of bundles and pkts for that transfer...
Unfortunately, I have a feeling whoever added in the support for
Synchronet is probably long gone, too.
i thought this was a recent addition to golded? recent as in the last
3 or 4 years...
I wasn't referring to the directories; I was referring to the internal code prefixes that Synchronet lets you configure in the message group settings. For instance, I've set up my DOVE-Net group to have the internal code prefix DOVE_, so for instance, the SYNCBAJA sub-board becomes DOVE_SYNCBAJA. What GoldEd+ was doing was making empty messagebase files without the prefix - so, using my same example,
GoldEd+ was creating files named SYNCBAJA (instead of DOVE_SYNCBAJA),
and they were empty.
I do have my message groups separated into different subdirectories
too, but GoldEd+ actually seemed to recognize that. GoldEd+ placed
its new files in the subdirectories that I have set up for my message groups.
I think you've likely identified the exact problem. The internal code prefixes were added in 2003 (SBBS v3.11), so I suspect GoldEd+ was enhanced to support Synchronet message bases before that time/version
and was never updated. Maybe there's someone to submit a bug report
to?
I wasn't referring to the directories; I was referring to the internal
code prefixes that Synchronet lets you configure in the message group
settings. For instance, I've set up my DOVE-Net group to have the
internal code prefix DOVE_, so for instance, the SYNCBAJA sub-board
becomes DOVE_SYNCBAJA. What GoldEd+ was doing was making empty
messagebase files without the prefix - so, using my same example,
GoldEd+ was creating files named SYNCBAJA (instead of DOVE_SYNCBAJA),
and they were empty.
I think you've likely identified the exact problem. The internal code prefixes were added in 2003 (SBBS v3.11), so I suspect GoldEd+ was enhanced to support Synchronet message bases before that time/version and was never updated. Maybe there's someone to submit a bug report to?
If you know C++ you could grab the sources and check into it. I believe I can still get in touch with a couple people that have access to update the code (Kai, the one that responded to you in GOLDED, may be one of them). Otherwise there hasn't been any updates for awhile now and the current maintainer doesn't say much in echos based in the USA (I think he's in Russia or Ukraine).
BUT, if you are to do anything, please make an update to the documentation as well to include that stuff so the 1-2 people that ask about it every year have something to go by. :)
Otherwise, if you're not interested, another option would be to setup another node (a separate mailer/tosser for use only with Golded. That's what I've done here since I like my Synchronet message bases packed to 5000 messages max. When Synchronet does that Golded has no idea about it, and when you scan for messages it will show every message in any area that was packed as new (it loses newscan pointers due to the pack/renumbering - which is obviously normal for Golded to not understand what happened).
Unfortunately, I have a feeling whoever added in the support for
Synchronet is probably long gone, too.
i thought this was a recent addition to golded? recent as in the last 3 or 4 years...
| Sysop: | MCMLXXIX |
|---|---|
| Location: | Prospect, CT |
| Users: | 325 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 09:36:18 |
| Calls: | 510 |
| Messages: | 220574 |