Hi All

(Not sure if DoveNET is (a) alive and (b) sending from my BBS, but here we gooo)

I am currently setting up an instance of Synchronet BBS under windows, and looking to setup various FTN connections - however I'm hitting a roadblock. Whenever going through the intial Fido setup (and same with any of the FTN setups), it gets to a point where it wants to write to sbbsecho.ini - but fails as follows:

Save changes to FidoNet configuration file: sbbsecho.ini (Y/n)?
!Error 13 opening sbbsecho.ini
Using JavaScript exit_code: 1
C:\sbbs\exec\init-fidonet.js executed in 68.36 seconds
!Module (init-fidonet.js) set exit_code: 1

JavaScript: Destroying context
JavaScript: Destroying runtime

The file exists and has content in it - not sure why the error is coming up though.

Any suggestions?

Thanks
Blinx

---
þ Synchronet þ retroverse - bbs.retroverse.au - Dedicated to Retro Computing & Retro Gaming!
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Blinx to All on Mon Aug 28 2023 04:49 pm

Hi All

(Not sure if DoveNET is (a) alive and (b) sending from my BBS, but here we gooo)

Appears it is.

I am currently setting up an instance of Synchronet BBS under windows, and looking to setup various FTN connections - however I'm hitting a roadblock. Whenever going through the intial Fido setup (and same with any of the FTN setups), it gets to a point where it wants to write to sbbsecho.ini - but fails as follows:

Save changes to FidoNet configuration file: sbbsecho.ini (Y/n)?
!Error 13 opening sbbsecho.ini
Using JavaScript exit_code: 1
C:\sbbs\exec\init-fidonet.js executed in 68.36 seconds
!Module (init-fidonet.js) set exit_code: 1

JavaScript: Destroying context
JavaScript: Destroying runtime

The file exists and has content in it - not sure why the error is coming up though.

Any suggestions?

1. Run the jsexec command-line as the same user that you installed Synchronet as. The error is a permissions error, so it appears your running the command prompt (and jsexec) as a different user than the owner of your c:\sbbs directory tree.

2. You can alternatively, run this same script *from* the BBS under External Programs->Operator->FidoNet Setup (something like that).
--
digital man (rob)

Sling Blade quote #13:
Karl: He lives inside of his own heart. That's an awful big place to live in. Norco, CA WX: 95.9øF, 24.0% humidity, 4 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Digital Man to Blinx on Mon Aug 28 2023 11:53 am

Appears it is.

Indeed! Some confusion when all the areas were listed with zero messages (fresh install). Dug up the details for setup (and looking for support) and here we are :)

1. Run the jsexec command-line as the same user that you installed Synchronet as. The error is a permissions error, so it appears your running the command prompt (and jsexec) as a different user than the owner of your c:\sbbs directory tree.

This is what is curious - run as the same user that installed synchro. Also tried running from an elevated cmd prompt - still no joy. Definately looks perms based, but struggle to understand why. Same user, completely fresh install. Was happening on 3.20 as well - so complete wipe, fresh windows, install required software, install sbbs, sufficient config to get it up and running and then running the fido setup. Same error.

2. You can alternatively, run this same script *from* the BBS under External Programs->Operator->FidoNet Setup (something like that).

Tried this as well with no joy.

I did also give the current user (who installed) full rights on the file as well, no luck. The only other thought it is locked for some reason (when sbbs is running). Doubt it though as others would have had a similar issue.

Can always switch to a linux build but thats a pretty agressive work around :)

---
þ Synchronet þ retroverse - bbs.retroverse.au - Dedicated to Retro Computing & Retro Gaming!
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Blinx to Digital Man on Tue Aug 29 2023 08:20 am

Re: FTN Setup - Error
By: Digital Man to Blinx on Mon Aug 28 2023 11:53 am

Appears it is.

Indeed! Some confusion when all the areas were listed with zero messages (fresh install). Dug up the details for setup (and looking for support) and here we are :)

1. Run the jsexec command-line as the same user that you installed Synchronet as. The error is a permissions error, so it appears your running the command prompt (and jsexec) as a different user than the owner of your c:\sbbs directory tree.

This is what is curious - run as the same user that installed synchro.

What are the attributes on the file in the error message? Perhaps it's marked read-only?

Also
tried running from an elevated cmd prompt - still no joy. Definately looks perms based, but struggle to understand why. Same user, completely fresh install. Was happening on 3.20 as well - so complete wipe, fresh windows, install required software, install sbbs, sufficient config to get it up and running and then running the fido setup. Same error.

2. You can alternatively, run this same script *from* the BBS under External Programs->Operator->FidoNet Setup (something like that).

Tried this as well with no joy.

Can you elaborate?

I did also give the current user (who installed) full rights on the file as well, no luck. The only other thought it is locked for some reason (when sbbs is running). Doubt it though as others would have had a similar issue.

Can always switch to a linux build but thats a pretty agressive work around :)

I'd rather we figure out what the issue so I can help any future sysop that has the same issue with a Windows install.
--
digital man (rob)

This Is Spinal Tap quote #11:
Nigel Tufnel: No. no. That's it, you've seen enough of that one.
Norco, CA WX: 96.1øF, 29.0% humidity, 14 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Digital Man to Blinx on Mon Aug 28 2023 05:35 pm

2. You can alternatively, run this same script *from* the BBS under External Programs->Operator->FidoNet Setup (something like that).

Tried this as well with no joy.

When running the command form the elevated cmd prompt, the same error 13 occured. No other information is provided.

Can you elaborate?
I'd rather we figure out what the issue so I can help any future sysop that has the same issue with a Windows install.

No stress. I spun up a linux instance and have a syncro bbs running on it (not tried anything fido related yet). I'll spin up a new Windows instance from scratch and run through the process again and provide feedback.

---
þ Synchronet þ Retroverse BBS - bbs.retroverse.au - Dedicated to Retro Computing & Gaming!
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Blinx to Digital Man on Tue Aug 29 2023 08:20 am

The following has been tried (all resulting in error 13):

- Fresh windows install with base requirements for running sbbs, running under the user that was created at time of windows install (thus an administrator)
- Running jsexec init-fidonet.js from a command prompt which is eithe normal or "Run as Administrator"
- started the same process fomr the File -> Run -> Initial Fido Setup menu item - Added Everyone with full access to the sbbsecho.ini file

I have recived my detaield for setting up AmigaNet, so could also use the process to setup the AmigaNet connection and areas with real information. The same issue occured, hwoever it is probably important to note that all the na files saved correctly to the folder as well as the saving of the .cnf files as well (so perms might not be the issue?)

The following is the steps to show the workflow taken to setup AmigaNet (not certain informaiton has been removed):

Which or [Q]uit: 39
Network name is 'AmigaNet' (Y/n)?
Network name: AmigaNet
Network zone: 39
Network info: https://amiganet.vlzn.nl/
Network domain: amiganet
Network coordinator: Wilfred van Velzen <amiganet.z39c@gmail.com> 2:280/464 EchoList: AmigaNetEchomailAreas.na
Reading Message Area configuration file: msgs.cnf
Your hub's address is 39:39/0 (Y/n)? n
Your hub's address (zone:net/node): 39:nnn/nnn
Your hub's address is 39:nnn/nnn (Y/n)? y
Your hub's sysop's name: xxxxxxxxxxxxx
Your hub's sysop's name is 'xxxxxxxxxxxxx' (Y/n)? y
Your hub's hostname or IP address is fido.vlzn.nl (Y/n)? n
Your hub's hostname or IP address: xxxxxxxxxxxxx
Your hub's hostname or IP address is xxxxxxxxxxxxx (Y/n)? y
Your hub's BinkP/TCP port number is 24554 (Y/n)?
Your node address is 39:901/9999 (Y/n)? n
Your zone number (e.g. 39): nn
Your network number (e.g. 901): nn
Your node number (e.g. 9999 for temporary node): nnnn
Your node address is 39:nnn/nnn (Y/n)? y
Your name is 'Matt Ianson' (Y/n)? y
Your AreaFix (a.k.a. Area Manager) Password (case in-sensitive): .......... Your AreaFix Password is '..........' (Y/n)? y
Your BinkP Session Password (case sensitive): ..........
Your BinkP Session Password is '..........' (Y/n)? y
Your TIC File Password (case sensitive) (optional): ..........
Your TIC File Password is '..........' (Y/n)? y
Add node address 39:nnn/nnn to your configuration (Y/n)? y
Your origin line is 'Retroverse - retroverse.au' (Y/n)? y
Create AmigaNet message group in SCFG->Message Areas (Y/n)? y
Adding Message Group: AmigaNet
Save Changes to Message Area configuration file: msgs.cnf (Y/n)? y
msgs.cnf updated successfully.
Download AmigaNet EchoList: AmigaNetEchomailAreas.na (Y/n)? y
Download from: http://www.vlzn.nl/AmigaNet/AmigaNetEchomailAreas.na (Y/n)? y Downloaded http://www.vlzn.nl/AmigaNet/AmigaNetEchomailAreas.na to d:\sbbs\ctrl\AmigaNetEchomailAreas.na
Removing AmigaNet: Title Prefixes from d:\sbbs\ctrl\AmigaNetEchomailAreas.na Import EchoList (d:\sbbs\ctrl\AmigaNetEchomailAreas.na) into Message Group: AmigaNet (Y/n)? y
Importing d:\sbbs\ctrl\AmigaNetEchomailAreas.na

Synchronet Configuration Utility (Win32) v3.19b Copyright 2022 Rob Swindell

Compiled master/a2a9dc027 Jan 2 2022 16:02:33 with MSC 1928
Reading main.cnf ...
Reading msgs.cnf ...
Importing Areas from d:\sbbs\ctrl\AmigaNetEchomailAreas.na ...
Imported 20 areas (20 added) from d:\sbbs\ctrl\AmigaNetEchomailAreas.na
Saving configuration (46 message areas) ... done.
Save changes to FidoNet configuration file: sbbsecho.ini (Y/n)? y
!Error 13 opening sbbsecho.ini
Using JavaScript exit_code: 1
d:\sbbs\exec\init-fidonet.js executed in 186.94 seconds
!Module (init-fidonet.js) set exit_code: 1

JavaScript: Destroying context
JavaScript: Destroying runtime

Hit enter to continue...

---
þ Synchronet þ retroverse - bbs.retroverse.au - Dedicated to Retro Computing & Retro Gaming!
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Blinx to Digital Man on Tue Aug 29 2023 05:35 pm

The following has been tried (all resulting in error 13):

Okay, so some way forwrd potentially. I archived the sbbsecho.ini file that was there and created a zero file size sbbsecho.ini. I imagine that the js script builds out/appends to that ini file as part of the process.

This worked (well, got through to the next steps rather than a failure).

Also found that the inbound/outbound/nonsecure folders did not exist in ../fido either (checked that from the fidonet video from a few years ago).

So this is probably a win at the moment. I've setup my AmigaNet feed, and tried pushing a netmail to the hub I'm connected to. Next issue (and I have seen this also when trying to get things runnign with AmiBinkD) is a no such host error:

f280.n901.z39.binkp.net:24554 failed (Error: No such host is known)

Obviously DNS is happy on this system...

Blinx..

---
þ Synchronet þ Retroverse BBS - bbs.retroverse.au:23023
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Blinx wrote to Digital Man <=-

Compiled master/a2a9dc027 Jan 2 2022 16:02:33 with MSC 1928
Reading main.cnf ...
Reading msgs.cnf ...
Importing Areas from d:\sbbs\ctrl\AmigaNetEchomailAreas.na ...
Imported 20 areas (20 added) from
d:\sbbs\ctrl\AmigaNetEchomailAreas.na Saving configuration (46
message areas) ... done. Save changes to FidoNet configuration
file: sbbsecho.ini (Y/n)? y !Error 13 opening sbbsecho.ini
Using JavaScript exit_code: 1
d:\sbbs\exec\init-fidonet.js executed in 186.94 seconds
!Module (init-fidonet.js) set exit_code: 1

The \sbbs\ctrl location is not where echomail ".na" files would normally
be kept. Do you have the "SBBSCTRL" environment variable set?



... Internal Error: The system has been taken over by sheep at line 19960
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Blinx to Digital Man on Tue Aug 29 2023 12:20 pm

Re: FTN Setup - Error
By: Digital Man to Blinx on Mon Aug 28 2023 05:35 pm

2. You can alternatively, run this same script *from* the BBS under External Programs->Operator->FidoNet Setup (something like that).

Tried this as well with no joy.

When running the command form the elevated cmd prompt, the same error 13 occured. No other information is provided.

I was suggesting that you login to the BBS and use the FidoNet setup from the External Programs->Operator menu. I wasn't talking about running the jsexec command from a command prompt (evelated or otherwise).
--
digital man (rob)

Breaking Bad quote #37:
only the very best... with just a right amount of dirty. - Saul
Norco, CA WX: 92.3øF, 29.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Blinx to Digital Man on Tue Aug 29 2023 05:35 pm

Re: FTN Setup - Error
By: Blinx to Digital Man on Tue Aug 29 2023 08:20 am

The following has been tried (all resulting in error 13):

- Fresh windows install with base requirements for running sbbs, running under the user that was created at time of windows install (thus an administrator)
- Running jsexec init-fidonet.js from a command prompt which is eithe normal or "Run as Administrator"
- started the same process fomr the File -> Run -> Initial Fido Setup menu item - Added Everyone with full access to the sbbsecho.ini file

What about using the external progarm option (while logged into the BBS)?

What are the attributes on the sbbsecho.ini file (e.g. read-only)?
--
digital man (rob)

Rush quote #39:
Sounds that build high like a mountain or notes that fall, gently, like rain Norco, CA WX: 92.3øF, 29.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Blinx to Digital Man on Tue Aug 29 2023 07:49 pm

Re: FTN Setup - Error
By: Blinx to Digital Man on Tue Aug 29 2023 05:35 pm

The following has been tried (all resulting in error 13):

Okay, so some way forwrd potentially. I archived the sbbsecho.ini file that was there and created a zero file size sbbsecho.ini. I imagine that the js script builds out/appends to that ini file as part of the process.

What were the attributes of the sbbsecho.ini file that you "archived"?

This worked (well, got through to the next steps rather than a failure).

Also found that the inbound/outbound/nonsecure folders did not exist in ../fido either (checked that from the fidonet video from a few years ago).

SBBSecho will create the outbound directory automatically before placing files in it. BinkIT will created the inbound and nonsecure-inbound directories when it receives file for them.

So this is probably a win at the moment. I've setup my AmigaNet feed, and tried pushing a netmail to the hub I'm connected to. Next issue (and I have seen this also when trying to get things runnign with AmiBinkD) is a no such host error:

f280.n901.z39.binkp.net:24554 failed (Error: No such host is known)

Obviously DNS is happy on this system...

binkp.net only works for FidoNet zones (1-4), so that would not be expected to work. You'll need to specify a BinkP host address for that FTN address (39:901/280) in your EchoCfg->Linked Nodes - you can't use DNS to auto look it up.
--
digital man (rob)

This Is Spinal Tap quote #18:
Sustain, listen to it. Don't hear anything. You would though were it playing. Norco, CA WX: 92.3øF, 29.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: FTN Setup - Error
By: Gamgee to Blinx on Tue Aug 29 2023 07:25 am

The \sbbs\ctrl location is not where echomail ".na" files would normally
be kept. Do you have the "SBBSCTRL" environment variable set?

This is a clean/default install of SBBS and following the installtion instructions from the wiki. There was no reference there about needing to set a variable. Looks like the installer does it as there is an SBBSCTRL variable set, which goes to the correct directory (for me, d:\sbbs\ctrl)

Is there something I'm missing here?

---
þ Synchronet þ Retroverse BBS - bbs.retroverse.au:23023
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: a
By: Digital Man to Blinx on Tue Aug 29 2023 10:57 am

What were the attributes of the sbbsecho.ini file that you "archived"?

Normal attributes (not read only). Authenticated users had modify rights, Administrators had full rights and users had read & execute. Nothing out of the ordinary there.

SBBSecho will create the outbound directory automatically before placing files in it. BinkIT will created the inbound and nonsecure-inbound directories when it receives file for them.

No worries - created them manually anyway.

binkp.net only works for FidoNet zones (1-4), so that would not be expected

Good to know. I'm working on my connection to Fido at the moment. With AmigaNet, loosk to be OK, as it fails the DNS then says it is connecting at the domain:24554 address provided by the hub.

---
þ Synchronet þ Retroverse BBS - bbs.retroverse.au:23023
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Digital Man to Blinx on Tue Aug 29 2023 10:49 am

I was suggesting that you login to the BBS and use the FidoNet setup from the External Programs->Operator menu. I wasn't talking about running the

Sorry, forgot to mention I had also run this way as well. Same issue occured (however the error was in red and flashed quickly and the screen cleared)

---
þ Synchronet þ Retroverse BBS - bbs.retroverse.au:23023
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Blinx wrote to Gamgee <=-

Re: Re: FTN Setup - Error
By: Gamgee to Blinx on Tue Aug 29 2023 07:25 am

The \sbbs\ctrl location is not where echomail ".na" files would normally
be kept. Do you have the "SBBSCTRL" environment variable set?

This is a clean/default install of SBBS and following the
installtion instructions from the wiki. There was no reference
there about needing to set a variable. Looks like the installer
does it as there is an SBBSCTRL variable set, which goes to the
correct directory (for me, d:\sbbs\ctrl)

Okay, I guess perhaps the Windows version of the installer sets that automatically. Not familiar with the Windows setup.

Is there something I'm missing here?

Not sure how an echomail network *.na file would end up in the CTRL
directory unless you put it there, but maybe that's automated somehow
too. I haven't used the auto-Fido-setup stuff either, have always done
it manually. Hopefully somebody more familiar with the Windows details
will chime in with more info.



... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: FTN Error 13
By: Blinx to Digital Man on Wed Aug 30 2023 08:58 am

Re: a
By: Digital Man to Blinx on Tue Aug 29 2023 10:57 am

What were the attributes of the sbbsecho.ini file that you "archived"?

Normal attributes (not read only). Authenticated users had modify rights, Administrators had full rights and users had read & execute. Nothing out of the ordinary there.

There is something out of the ordinary with the file if you can just archive and then recreate it and all is fine.

binkp.net only works for FidoNet zones (1-4), so that would not be expected

Good to know. I'm working on my connection to Fido at the moment. With AmigaNet, loosk to be OK, as it fails the DNS then says it is connecting at the domain:24554 address provided by the hub.

Is the port number correct?
--
digital man (rob)

This Is Spinal Tap quote #33:
Nigel Tufnel: Well, so what? What's wrong with bein' sexy?
Norco, CA WX: 98.0øF, 25.0% humidity, 9 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Blinx to Digital Man on Wed Aug 30 2023 08:59 am

Re: FTN Setup - Error
By: Digital Man to Blinx on Tue Aug 29 2023 10:49 am

I was suggesting that you login to the BBS and use the FidoNet setup from the External Programs->Operator menu. I wasn't talking about running the

Sorry, forgot to mention I had also run this way as well. Same issue occured (however the error was in red and flashed quickly and the screen cleared)

Okay, thanks. Sounds like something out of the normal with that file on your system.
--
digital man (rob)

This Is Spinal Tap quote #37:
David St. Hubbins: We are Spinal Tap from the UK - you must be the USA!
Norco, CA WX: 98.0øF, 25.0% humidity, 9 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: FTN Setup - Error
By: Gamgee to Blinx on Tue Aug 29 2023 05:49 pm

Not sure how an echomail network *.na file would end up in the CTRL directory unless you put it there, but maybe that's automated somehow
too. I haven't used the auto-Fido-setup stuff either, have always done
it manually. Hopefully somebody more familiar with the Windows details
will chime in with more info.

The auto-fido-setup stuff downloads echolists (or extracts them) to the CTRL directory for no particular reason. This is not Windows-specific.
--
digital man (rob)

Synchronet "Real Fact" #101:
Avatars were added to Synchronet (backward compatible w/v3.16) in January 2018 Norco, CA WX: 98.0øF, 25.0% humidity, 9 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Digital Man wrote to Gamgee <=-

Re: Re: FTN Setup - Error
By: Gamgee to Blinx on Tue Aug 29 2023 05:49 pm

Not sure how an echomail network *.na file would end up in the CTRL directory unless you put it there, but maybe that's automated somehow
too. I haven't used the auto-Fido-setup stuff either, have always done
it manually. Hopefully somebody more familiar with the Windows details
will chime in with more info.

The auto-fido-setup stuff downloads echolists (or extracts them)
to the CTRL directory for no particular reason. This is not Windows-specific.

Ahhh, OK, well that explains that part then. I guess I would have
expected to find them in ../data, with areas.bbs and friends. Thanks for
the clarification.



... I'm as confused as a baby in a topless bar.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Blinx to Digital Man on Tue Aug 29 2023 05:35 pm

Save changes to FidoNet configuration file: sbbsecho.ini (Y/n)? y
!Error 13 opening sbbsecho.ini

This problem should now be fixed (bug in a couple of the .js scripts).
--
digital man (rob)

Sling Blade quote #20:
Doyle: Hey is this the kind of retard that drools and rubs shit in his hair? Norco, CA WX: 73.5øF, 61.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FTN Setup - Error
By: Digital Man to Blinx on Fri Sep 22 2023 12:06 pm

!Error 13 opening sbbsecho.ini

This problem should now be fixed (bug in a couple of the .js scripts).

Oh awesome, thanks! I did have a workaround in place where I'd backup the file, create a blank .ini then run the process - then combine the files again.

However have also since worked with Deon @ Clrghouz and worked out setting things up manually now anyway :)

---
þ Synchronet þ Retroverse - retroverse.au
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)