2) But, i see several ERROR 2 (no such file) from qwktomsg.cpp, this are incorrect. These file are exist and have access (sbbs run as root)
The value of access=4294967191 and info= blaffes me
Here i paste the relevant log lines:
11/29 21:43:22 evnt ERROR 2 (No such file or directory) in qwktomsg.cpp
line 484 writing "/sbbs/data/subs/docksudh/dsoldantropol"
access=4294967191 info=
Re: importing OLD qwk files
By: Ragnarok to DOVE-Net.Synchronet_Discussion on Tue Nov 29 2016 09:58 pm
2) But, i see several ERROR 2 (no such file) from qwktomsg.cpp, this are incorrect. These file are exist and have access (sbbs run as root)
That just happens to be the current value of 'errno' at the time of the failure. You can probably ignore that.
The value of access=4294967191 and info= blaffes me
That looks like a negative number sign extended to an unsigned value.
Here i paste the relevant log lines:
11/29 21:43:22 evnt ERROR 2 (No such file or directory) in qwktomsg.cpp line 484 writing "/sbbs/data/subs/docksudh/dsoldantropol" access=4294967191 info=
Get the latest code from CVS, rebuild, and reproduce the error and there should
be a lot more detail in the error messages which should help to identify the cause of the problem. Also, just to be sure, run chksmb on your "dsoldantropol"
msgbase and make sure it's not corrupt. If it is, just delete the dsoldantropol.* files and re-import the QWK packet.
digital man
Re: importing OLD qwk files
By: Ragnarok to DOVE-Net.Synchronet_Discussion on Tue Nov 29 2016 09:58 pm
2) But, i see several ERROR 2 (no such file) from qwktomsg.cpp, this are incorrect. These file are exist and have access (sbbs run as root)
That just happens to be the current value of 'errno' at the time of the failure. You can probably ignore that.
The value of access=4294967191 and info= blaffes me
That looks like a negative number sign extended to an unsigned value.
Here i paste the relevant log lines:
11/29 21:43:22 evnt ERROR 2 (No such file or directory) in qwktomsg.cpp line 484 writing "/sbbs/data/subs/docksudh/dsoldantropol" access=4294967191 info=
Get the latest code from CVS, rebuild, and reproduce the error and there should
be a lot more detail in the error messages which should help to identify the cause of the problem. Also, just to be sure, run chksmb on your "dsoldantropol"
msgbase and make sure it's not corrupt. If it is, just delete the dsoldantropol.* files and re-import the QWK packet.
digital man
Synchronet/BBS Terminology Definition #10:
CVS = Concurrent Versioning System
Norco, CA WX: 58.8F, 23.0% humidity, 7 mph W wind, 0.00 inches rain/24hrs ---
Synchronet Vertrauen Home of Synchronet telnet://vert.synchro.net
Get the latest code from CVS, rebuild, and reproduce the error and there should
be a lot more detail in the error messages which should help to identify the cause of the problem. Also, just to be sure, run chksmb on your "dsoldantropol"
msgbase and make sure it's not corrupt. If it is, just delete the dsoldantropol.* files and re-import the QWK packet.
Hello!
I test now, and get notice the new error thanks!:
info=smb_addmsg subject field missing
I can confirm that messages with empy subject raise the error.
Can you fix to support message whitout subject or maybe put "(no
subject)" if occur ?
Also, I would greatly appreciate if you can help to solve the enconding problem from usernames (maybe for other fields) see the example capture https://ibin.co/33pOQjd2VBV2.png
for example the username "Yabrn" was imported as "Yabr n"
I committed a change to CVS that will we allow (again) messages with no subjects.
yes is strange but do not have the issue in the body:Also, I would greatly appreciate if you can help to solve the enconding problem from usernames (maybe for other fields) see the example capture https://ibin.co/33pOQjd2VBV2.png
for example the username "Yabrn" was imported as "Yabr n"
That is strange. From the hex dump of the messages.dat in DOCK_SUD.001, I see that the ex-ASCII charcter in that name is 0xA0 (160), which should appear as an 'a' with an accent mark if viewed with the CP437 character set. Like this:
I can find no code in the QWK import or SMB stuff that would convert this to another character value. If you send me the resulting message base files, I can
confirm what is or is not happening to this character during import from QWK.
Is it possible it's just a terminal/viewing issue and the character is actually
stored in the message base exactly the same as in the QWK packet? You can use a
tool like smbutil to verify this as well.
for example the username "Yabrn" was imported as "Yabr n"
That is strange. From the hex dump of the messages.dat in
DOCK_SUD.001, I see that the ex-ASCII charcter in that name is 0xA0
(160), which should appear as an 'a' with an accent mark if viewed
with the CP437 character set. Like this:
I can find no code in the QWK import or SMB stuff that would convert
this to another character value. If you send me the resulting message
base files, I can confirm what is or is not happening to this
character during import from QWK.
El 01/12/16 a las 07:44, Digital Man escribi:
I committed a change to CVS that will we allow (again) messages with no subjects.
yeah!! all messages was imported!
Also, I would greatly appreciate if you can help to solve the enconding problem from usernames (maybe for other fields) see the example capture https://ibin.co/33pOQjd2VBV2.png
for example the username "Yabrn" was imported as "Yabr n"
That is strange. From the hex dump of the messages.dat in DOCK_SUD.001, I see that the ex-ASCII charcter in that name is 0xA0 (160), which should appear as an 'a' with an accent mark if viewed with the CP437 character set. Like this:
I can find no code in the QWK import or SMB stuff that would convert this to another character value. If you send me the resulting message base files, I can
confirm what is or is not happening to this character during import from QWK.
Is it possible it's just a terminal/viewing issue and the character is actually
stored in the message base exactly the same as in the QWK packet? You can use a
tool like smbutil to verify this as well.
yes is strange but do not have the issue in the body:
http://bbs.docksud.com.ar/msgs/msg.ssjs?msg_sub=dsoldantropol&message=59
anyway. im very happy to get all messages imported. this issue in the from/to field do not seriuos
Hello Digital,
On 01 Dec 16 02:44, Digital Man wrote to Ragnarok:
for example the username "Yabrn" was imported as "Yabr n"
That is strange. From the hex dump of the messages.dat in
DOCK_SUD.001, I see that the ex-ASCII charcter in that name is 0xA0 (160), which should appear as an 'a' with an accent mark if viewed
with the CP437 character set. Like this:
For the record, your 'a' with an accent mark was not in your message after "Like this:".
I can find no code in the QWK import or SMB stuff that would convert this to another character value. If you send me the resulting message base files, I can confirm what is or is not happening to this
character during import from QWK.
I'm using Putty here and don't see the character as typed by you either. However the line I quoted of Ragnarok's I do indeed see the accented 'a'.
When this gets back to you, though.. it will be in UTF-8.. so it probably won't
display correctly for you. :)
yes is strange but do not have the issue in the body:
http://bbs.docksud.com.ar/msgs/msg.ssjs?msg_sub=dsoldantropol&message=59
How does it look in the Terminal server (or smbutil) though? That could just be
an issue with how the message is displayed in the web UI.
anyway. im very happy to get all messages imported. this issue in the from/to field do not seriuos
Okay. I am curious about that missing character though. If you want, you could
just zip up the resulting message base files and I could take a look.
digital man
Re: importing OLD qwk files
By: Accession to Digital Man on Thu Dec 01 2016 08:01 am
Hello Digital,
On 01 Dec 16 02:44, Digital Man wrote to Ragnarok:
for example the username "Yabrсn" was imported as "Yabr n"
That is strange. From the hex dump of the messages.dat in DOCK_SUD.001, I see that the ex-ASCII charcter in that name is 0xA0 (160), which should appear as an 'a' with an accent mark if viewed with the CP437 character set. Like this: а
For the record, your 'a' with an accent mark was not in your message after "Like this:".
Let me try again: а
No?
I can find no code in the QWK import or SMB stuff that would convert this to another character value. If you send me the resulting message base files, I can confirm what is or is not happening to this character during import from QWK.
I'm using Putty here and don't see the character as typed by you either. However the line I quoted of Ragnarok's I do indeed see the accented 'a'.
Ha, in Ragnarok's message the character looks like a Beta B (225 in CP437): с
When this gets back to you, though.. it will be in UTF-8.. so it probably won't
display correctly for you. :)
Most BBS stuff assumes CP437. Try using that encoding/translation instead of UTF-8.
I'm using Putty here and don't see the character as typed by you either. However the line I quoted of Ragnarok's I do indeed see the accented 'a'.
When this gets back to you, though.. it will be in UTF-8.. so it probably won't
display correctly for you. :)
That is strange. From the hex dump of the messages.dat in
DOCK_SUD.001, I see that the ex-ASCII charcter in that name is 0xA0
(160), which should appear as an 'a' with an accent mark if viewed
with the CP437 character set. Like this:
For the record, your 'a' with an accent mark was not in your message
after "Like this:".
Let me try again:
El 01/12/16 a las 16:48, Digital Man escribi:
yes is strange but do not have the issue in the body:
http://bbs.docksud.com.ar/msgs/msg.ssjs?msg_sub=dsoldantropol&message=5 9
How does it look in the Terminal server (or smbutil) though? That could just be
an issue with how the message is displayed in the web UI.
smbutil also show issue
https://ibin.co/33v5LbGEA8Bm.png
anyway. im very happy to get all messages imported. this issue in the from/to field do not seriuos
Okay. I am curious about that missing character though. If you want, you could
just zip up the resulting message base files and I could take a look.
here is the message base files: http://bbs.docksud.com.ar/tmp/dsoldantropol.zip
El 01/12/16 a las 11:01, Accession escribi:
I'm using Putty here and don't see the character as typed by you either. However the line I quoted of Ragnarok's I do indeed see the accented 'a'.
When this gets back to you, though.. it will be in UTF-8.. so it probably won't
display correctly for you. :)
i read from thunderbird via nntp and also i can not see the character
from DM,
but if i use syncterm is show fine.
I'm using Putty here and don't see the character as typed by you
either. However the line I quoted of Ragnarok's I do indeed see the
accented 'a'.
When this gets back to you, though.. it will be in UTF-8.. so it
probably won't display correctly for you. :)
i read from thunderbird via nntp and also i can not see the character
from DM, but if i use syncterm is show fine.
| Sysop: | Ragnarok |
|---|---|
| Location: | Dock Sud, Bs As, Argentina |
| Users: | 137 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 115:20:33 |
| Calls: | 15,363 |
| Calls today: | 1 |
| Files: | 20,059 |
| D/L today: |
1 files (42K bytes) |
| Messages: | 1,798,732 |
