Wiki edit of http://wiki.synchro.net/install:win by ecbbs:
Added link and text re: Windows installer that pulls from CVS & nightly builds.
Wiki edit of http://wiki.synchro.net/install:win by deuce:
[Installation] Move CVS/latest installer to after the official one.
Re: [wiki.synchro.net] page changed: install:win
By: wiki.synchro.net to All on Tue Feb 04 2014 21:07:25
Wiki edit of http://wiki.synchro.net/install:win by ecbbs:
Added link and text re: Windows installer that pulls from CVS &
nightly builds.
A note to the curious:
Cyan and I put this installer together today. It pulls the latest ctrl, exec, node1-4, text, web and xtrn directories from CVS, then downloads the latest nightly build and unpacks it into the exec directory. It may need some work yet, but should produce a fresh installation that's quite up-to-date. (We've tested it and found it to work on Windows XP, 7, and 2008 so far, and it will probably work on others.)
The SBBSCTRL environment variable gets set appropriately, and sbbs.dll is copied to the system directory (I can't remember if this is necessary, or
if we could just add the 'exec' directory to the PATH.) If anyone can
think of any new-installation/upgrade pitfalls that we may need to address, let me know.
Hopefully this makes things easier for newcomers (and others) doing fresh installs. The existing upgrade process is a bit confusing for those who fail to read the documentation that comes with each upgrade archive. :D
echicken wrote to wiki.synchro.net <=-
Wiki edit of http://wiki.synchro.net/install:win by ecbbs:
Added link and text re: Windows installer that pulls from CVS & nightly builds.
A note to the curious:
Cyan and I put this installer together today. It pulls the latest
ctrl, exec, node1-4, text, web and xtrn directories from CVS, then downloads the latest nightly build and unpacks it into the exec
directory. It may need some work yet, but should produce a fresh installation that's quite up-to-date. (We've tested it and found it to work on Windows XP, 7, and 2008 so far, and it will probably work on others.)
The SBBSCTRL environment variable gets set appropriately, and sbbs.dll
is copied to the system directory (I can't remember if this is
necessary, or if we could just add the 'exec' directory to the PATH.)
If anyone can think of any new-installation/upgrade pitfalls that we
may need to address, let me know.
Hopefully this makes things easier for newcomers (and others) doing
fresh installs. The existing upgrade process is a bit confusing for
those who fail to read the documentation that comes with each upgrade archive. :D
The SBBSCTRL environment variable gets set appropriately, and sbbs.dll is copied to the system directory (I can't remember if this is necessary, or
Quick question.... I have certain .js files modified in the exec folder. Being that's the case, sometime in the future, if you're ever thinking about doing it, can there be a cfg file that will allow us to block certain files from being updated?
The contents of CVS do not a working Windows install make. Please don't
do this as your testing environments and knowledge pre-requisites are insufficient.
echicken wrote to Bill McGarrity <=-
Quick question.... I have certain .js files modified in the exec folder. Being that's the case, sometime in the future, if you're ever thinking about doing it, can there be a cfg file that will allow us to block certain files from being updated?
This wasn't an updater, but an installer.
FWIW, if you modify JS files, etc., they should go into the mods
directory (that's what it's for.) That's the way to 'block' them from being overwritten.
Quick question.... I have certain .js files modified in the exec folder. Being that's the case, sometime in the future, if you're ever thinking
about doing it, can there be a cfg file that will allow us to block certain files from being updated?
Re: [wiki.synchro.net] page changed: install:win
By: Digital Man to echicken on Tue Feb 04 2014 22:53:52
The contents of CVS do not a working Windows install make. Please
don't do this as your testing environments and knowledge
pre-requisites are insufficient.
While I know that the contents of CVS aren't always going to be "working", I'd be curious to know what might be missing. It seemed like, coupled with a nightly build, the ctrl, exec, text, web and xtrn directories from CVS ought to do it. I accept that this is not the case, but am curious as to why.
Deuce wrote to Bill McGarrity <=-
Quick question.... I have certain .js files modified in the exec folder. Being that's the case, sometime in the future, if you're ever thinking
about doing it, can there be a cfg file that will allow us to block certain files from being updated?
Modified/new files belong in the mods directory. The mods directory
isn't modified and is searched first when looking for JS and BIN files.
An exercise of installing the BBS, creating user accounts, posting messages, uploading and downloading files (of different types), joining
a QWK network, joining an FTN network, etc. (basically using all the features of the BBS) would eventually highlight all the issues. But that takes hours of work and a good idea of what "working" actually looks
like.
I guess instead (or in addition) you could take a working Synchronet-Windows installer, install it on a virgin system, and then compare all the directory contents and registry contents and see what's different to get a clue where to look for the deficiencies. I also do a lot of tweaking of the .cnf files through-out the process of creating
and debugging a Windows-Install package, so those file contents would
need a close inspection to find out what's lacking.
| Sysop: | Ragnarok |
|---|---|
| Location: | Dock Sud, Bs As, Argentina |
| Users: | 136 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 63:31:07 |
| Calls: | 15,176 |
| Calls today: | 3 |
| Files: | 19,862 |
| D/L today: |
92 files (16,850K bytes) |
| Messages: | 1,693,954 |