Building c:\sbbs\exec\Copy of default.bin
Compiling default.src...
error 2 opening default.src for read
Do you actually have a default.src file? It looks like you may have something called "Copy of default" but not a "default".
Nightfox
Building c:\sbbs\exec\Copy of default.bin
Compiling default.src...
error 2 opening default.src for read
Do you actually have a default.src file? It looks like you may have something called "Copy of default" but not a "default".
Nightfox
I have gone into my exec directory and removed all of the default.src's out of there that I had as copies. I then tried running jsexec update.js and I still get the same error. ERROR 2 OPENING DEFAULT.SRC FOR READ
I thought maybe after you had said something about ti that maybe that was causing a problem but it still does the same thing even after deleting them out of there.
I would take a good look at the permissions on that file, who is that file assigned to?? what permissions?? are you running the bbs as a different user? if so then default.src needs to be owned by that userrunning jsexec update.js and I still get the same error. ERROR 2
OPENING DEFAULT.SRC FOR READ
I would take a good look at the permissions on that file, who is that file assigned to?? what permissions?? are you running the bbs as a different user? if so then default.src needs to be owned by that user
Michael
I am having trouble with the * & /* commands from the main menu they do not work. I have not made and changes to any of the commands so I do not know why this would have stopped working. If someone has any idea on this matter it would be greatly appreciated.
Please the describe with more details:Synchronet Classic
1. What command shell are you using?
2. What happens when you type '*' at the menu prompt?The screen just blinks real fast and returns to the main menu waiting for my next choice.
3. Do you have any terminal/screen captures you can share?No, I do not have any screen captures of this.
4. Does the 'J'ump to area command work?Yes, the Jump to command works just fine.
Re: Menu Commands
By: Digital Man to Mojo on Sun Jul 15 2018 09:55 pm
Please the describe with more details:Synchronet Classic
1. What command shell are you using?
2. What happens when you type '*' at the menu prompt?The screen just blinks real fast and returns to the main menu waiting for my next choice.
3. Do you have any terminal/screen captures you can share?No, I do not have any screen captures of this.
4. Does the 'J'ump to area command work?Yes, the Jump to command works just fine.
What if you disable "Expert Menu Mode" ('X' from the defaults menu)?
If you view your scrollback (e.g. Alt-B in SyncTERM) what do you see?
Re: Menu Commands
By: Digital Man to Mojo on Mon Jul 16 2018 08:35 pm
What if you disable "Expert Menu Mode" ('X' from the defaults menu)?
Expert mode is disabled.
If you view your scrollback (e.g. Alt-B in SyncTERM) what do you see?
When I view the scrollback it just gives me a blank screen even after trying the * command before I view the scrollback.
Double-check your ctrl/text.dat file. It sounds like it may have been corrupted?
Re: Menu Commands
By: Digital Man to Mojo on Tue Jul 17 2018 03:34 pm
Double-check your ctrl/text.dat file. It sounds like it may have been corrupted?
I have a test bbs running on a different machine that everything works as it should on it. So I took the text.dat from there and put it on my rpoduction bbs to see if it would work and I still have the same problem /* does not work.
Are they both running the same build of sbbs?
Do you have any changes in your default.src/bin file from the stock ones?
Does '/*' work from the file transfer menu?
Re: Menu Commands
By: Digital Man to Mojo on Tue Jul 17 2018 09:07 pm
Are they both running the same build of sbbs?
Yes, they both are the same. When I do updates I do it to both of them. I do the test one first after a backup is made and then I do the production one after a backup is made.
Do you have any changes in your default.src/bin file from the stock ones?
As best as I can remember I have not made any changes to either default.src/bin as I am not sure what can be doen with it and do not want to mess them up.
Does '/*' work from the file transfer menu?
I go to the transfer menu and both * & /* work just fine.
What I would do is add some "print" lines to the default.src, recompile with Baja (which requires logging out/back-in if you're already logged in to the board) and make sure it's actually executing this portion of the command shell code:
cmdkey /*
msg_show_groups
end_cmd
Or you could try the Renegade or WWIV clone shells: they both use this same Baja function (it's "/A" for Renegade). If it works in those shells and doesn't for default, then it sounds like a problem with the default.bin file. If it doesn't work for any of them, then it sounds like a text.dat file issue. If the 'J'ump command works, then that means your configuration is okay and the BBS certainly know you have message groups, so it's something else.
Re: Menu Commands
By: Digital Man to Mojo on Wed Jul 18 2018 03:34 pm
What I would do is add some "print" lines to the default.src, recompile with Baja (which requires logging out/back-in if you're already logged in to the board) and make sure it's actually executing this portion of the command shell code:
cmdkey /*
msg_show_groups
end_cmd
I put a print line in there (not sure I am doing the print line correctly) and it did not make any difference. But I may have done it worng.
Or you could try the Renegade or WWIV clone shells: they both use this same Baja function (it's "/A" for Renegade). If it works in those shells and doesn't for default, then it sounds like a problem with the default.bin file. If it doesn't work for any of them, then it sounds like a text.dat file issue. If the 'J'ump command works, then that means your configuration is okay and the BBS certainly know you have message groups, so it's something else.
I also tried both Renegade & WWIV clone shells and the /* or * did not work in either of those shells. So this is where I am at with it at this point.
Okay, so earlier you said the '*' command wasn't work in the default shell and then you said it was. And now you're saying the '*' command doesn't work in the Renegade and WWIV shells. Definitely sounds like a text.dat issue. If you rename your ctrl/text.dat file to something else (like text.save) and then just create a 0-byte text.dat file, all the default strings built into sbbs.dll will be used. Try that.
Re: Menu Commands
By: Digital Man to Mojo on Wed Jul 18 2018 10:59 pm
Okay, so earlier you said the '*' command wasn't work in the default shell and then you said it was. And now you're saying the '*' command doesn't work in the Renegade and WWIV shells. Definitely sounds like a text.dat issue. If you rename your ctrl/text.dat file to something else (like text.save) and then just create a 0-byte text.dat file, all the default strings built into sbbs.dll will be used. Try that.
I did this as you said to renamed the text.dat to text.save. Then I made a new 0 byte file called text.dat. Now the * command works with some of the message areas and there are some it will not work with. As for /* it still does not work at all. I do not know what happened but something has really gotten messed up in here some where that is for sure.
Is it possible you created a text/menu/grps.asc file and maybe some text/menu/subs*.asc files? If so, these files would be displayed in place of the internally generated group and sub-board listings.
Re: Menu Commands
By: Digital Man to Mojo on Thu Jul 19 2018 02:04 pm
Is it possible you created a text/menu/grps.asc file and maybe some text/menu/subs*.asc files? If so, these files would be displayed in place of the internally generated group and sub-board listings.
Yes, i had created grps.asc and subs*.asc files. I never thought these would be a problem. But I went in and removed them all to see what would happen if they were all gone. After removing them I tried those commands and everything worked just fine. So I guess it does not like to work with custom menus in place. So Iguess there never was or at least I think there never was a problem it just did not like having to use the menus I had created when using * & /* command from the main menu. I guess I will have to leave those menu's out of there in order for this to work correctly.
The menu should've been displayed in place of the built in group/sub-board listings. What did you have in the menu files?
Re: Menu Commands
By: Digital Man to Mojo on Thu Jul 19 2018 10:39 pm
The menu should've been displayed in place of the built in group/sub-board listings. What did you have in the menu files?
I saved the as subs1.asc subs2.asc and so on. Is this correct or should they have been saved in some other way?
The filenames are correct. I was asking about the *content*. How those files subs*.asc files (and grps.asc) files work, is if they exist, there contents will be displayed to the user when they request a list of groups (grps.asc) and sub-boards within a group (subs#.asc).
I just tested it here and it seems to work as designed (the contents of the files are sent to the user).
Re: Menu Commands
By: Digital Man to Mojo on Fri Jul 20 2018 02:39 pm
The filenames are correct. I was asking about the *content*. How those files subs*.asc files (and grps.asc) files work, is if they exist, there contents will be displayed to the user when they request a list of groups (grps.asc) and sub-boards within a group (subs#.asc).
I did have the files in the menu folder, but I removed them because things were not working as they should.
Once I took them out the commands worked
just fine. So must be I did something worng with the files and that is what has cause this problem. I thought it should work but for some reason they were not working as they did for you.
I just tested it here and it seems to work as designed (the contents of the files are sent to the user).
Well it works for you and this is good now to figure out why it does not do the same here for me.
Maybe we have a different definition of "working". When you have those files present, their contents (the text you put in the file) will be shown to the user instead of the normal group or sub-board listing.
I'll ask again: what did you put in the files?
Was the content shown to
the terminal user when the '/*' command (grps.asc) or '*' (subs*.asc) command was used?
Re: Menu Commands
By: Digital Man to Mojo on Mon Jul 23 2018 12:53 am
Maybe we have a different definition of "working". When you have those files present, their contents (the text you put in the file) will be shown to the user instead of the normal group or sub-board listing.
I understand that this is whqat is suppose to happen, but for some reason here on my end when I have the menu grps.asc in place and I type /* the screen flashes quick and nothing is displayed. But with the grps.asc in place and I do J it displays the grps.asc file like it should. This is the same thing that happens when I have the subs files in place also I get nothing on the screen when I do * for it to list the current sub I am in.
I'll ask again: what did you put in the files?
A listing for that sub and I went right down the line and made one for each sub.
Was the content shown to
the terminal user when the '/*' command (grps.asc) or '*' (subs*.asc) command was used?
No, there was nothing displayed when either command was used while the menu files I created were in place. I remove the menu files I created and then try ti and the information is displayed as it should
So in all cases, the contents of the .asc files were displayed to me. Is it possible you're using weird attribute codes or something in your files? Perhaps you can try again with a simple plain-text .asc file?
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495949:35:01 |
| Calls: | 82 |
| Files: | 1,070 |
| Messages: | 287,256 |