Date   

Re: Connect Retries...

roger g6ckr <radio@...>
 

Just a note re your second mail and relates to the emailing of the
spaces not the generating of them.
This is a reply using the first mail.
Spaces arrived here OK.

Since the lines are now quoted they should be preserved still with the
spaces. So it looks like the problem may be at the receive end not in
the system.
Roger
G6CKR

On Fri, 2008-02-15 at 21:14 +0000, Jeffrey P. Nast wrote:
Using flarq 3.0 and VBdigi 1.2.0...

I have noticed that the retry count fluctuates. With my laptop not
connected to anything (listening through the speaker), I will try
to "connect" to a number of different stations. Of course each one
will fail. But the number of retries for some attempts varies.

In the example below, for each "Connect" attempt I used a different
call sign. Notice also that an extraneous space character is
intermittantly inserted at the begining of some lines.

Questions:
* Does the "Retries" count in the flarq config also pertain to the
number of "Connect" attempts?
* Why does the number of connect attempts vary?
* Where does the intermittant extraneous space character in column 1
come from?

00cKC0MKS:1025 KC0TIU:24 0 741E9
00cKC0MKS:1025 KC0TIU:24 0 741E9
00cKC0MKS:1025 KC0TIU:24 0 741E9
00cKC0MKS:1025 KC0TIU:24 0 741E9
00cKC0MKS:1025 KC0WDQ:24 0 72D40
00cKC0MKS:1025 KC0WDQ:24 0 72D40
00cKC0MKS:1025 KC0WDQ:24 0 72D40
00cKC0MKS:1025 KC0WDQ:24 0 72D40
00cKC0MKS:1025 KC0MKU:24 0 79B21
00cKC0MKS:1025 KC0MKU:24 0 79B21
00cKC0MKS:1025 KC0MKU:24 0 79B21
00cKC0MKS:1025 KC0MKT:24 0 757E0
00cKC0MKS:1025 KC0MKT:24 0 757E0
00cKC0MKS:1025 KC0MKT:24 0 757E0
00cKC0MKS:1025 KC0RTX:24 0 7975D
00cKC0MKS:1025 KC0RTX:24 0 7975D
00cKC0MKS:1025 KC0RTX:24 0 7975D
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 N0MR:24 0 7B03A
00cKC0MKS:1025 N0MR:24 0 7B03A
00cKC0MKS:1025 N0MR:24 0 7B03A
00cKC0MKS:1025 N0IM:24 0 73C49
00cKC0MKS:1025 KC0FTN:24 0 7F19C
00cKC0MKS:1025 KC0FTN:24 0 7F19C
00cKC0MKS:1025 KC0FTN:24 0 7F19C
00cKC0MKS:1025 KC0FTN:24 0 7F19C
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 W0KTX:24 0 73853
00cKC0MKS:1025 KC0TST:24 0 7ED9B
00cKC0MKS:1025 KC0TST:24 0 7ED9B
00cKC0MKS:1025 W4LX:24 0 7D68C
00cKC0MKS:1025 W4LX:24 0 7D68C
00cKC0MKS:1025 W4LX:24 0 7D68C
00cKC0MKS:1025 W4LX:24 0 7D68C
00cKC0MKS:1025 W4LX:24 0 7D68C
00cKC0MKS:1025 VP6DX:24 0 7EB0E
00cKC0MKS:1025 VP6DX:24 0 7EB0E
00cKC0MKS:1025 VP6DX:24 0 7EB0E
00cKC0MKS:1025 VP6DX:24 0 7EB0E
00cKC0MKS:1025 KC0RCV:24 0 7EB37
00cKC0MKS:1025 KC0RCV:24 0 7EB37
00cKC0MKS:1025 KC0RCV:24 0 7EB37
00cKC0MKS:1025 KC0RCV:24 0 7EB37
00cKC0MKS:1025 KC0RCV:24 0 7EB37
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 W0RO:24 0 7490C
00cKC0MKS:1025 W0RO:24 0 7490C
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KI0DB:24 0 7F739
00cKC0MKS:1025 AA0AW:24 0 7ECF5
00cKC0MKS:1025 AA0AW:24 0 7ECF5
00cKC0MKS:1025 AA0AW:24 0 7ECF5
00cKC0MKS:1025 AA0AW:24 0 7ECF5
00cKC0MKS:1025 AA0AW:24 0 7ECF5
00cKC0MKS:1025 AA0AW:24 0 7ECF5
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0ZZL:24 0 7E290
00cKC0MKS:1025 KC0ZZL:24 0 7E290
00cKC0MKS:1025 KC0ZZL:24 0 7E290
00cKC0MKS:1025 KC0ZZL:24 0 7E290
00cKC0MKS:1025 KC0ZZL:24 0 7E290
00cKC0MKS:1025 KC0SJB:24 0 7810C
00cKC0MKS:1025 KC0SJB:24 0 7810C
00cKC0MKS:1025 KC0SJB:24 0 7810C
00cKC0MKS:1025 KC0SJB:24 0 7810C
00cKC0MKS:1025 KC0SJB:24 0 7810C
00cKC0MKS:1025 K0JJR:24 0 7CDD2
00cKC0MKS:1025 K0JJR:24 0 7CDD2
00cKC0MKS:1025 K0JJR:24 0 7CDD2
00cKC0MKS:1025 K0JJR:24 0 7CDD2
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 KC0MKS:24 0 7B1A1

Great software! Thank you!

-Jeff Nast
KC0MKS




Yahoo! Groups Links



Re: Connect Retries...

w1hkj <w1hkj@...>
 

You need to enable the visibilty of control codes, "Configure/Show Ctl Codes" on the vbdigi menu system.

The extra space is probably just system noise.

Dave


Re: Connect Retries...

"Jeffrey P. Nast" <kc0mks@...>
 

Noticed that the Yahoo editor removed the spaces in column 1. Here it
is again, only I put an "x" wherever there was a space...

00cKC0MKS:1025 KC0TIU:24 0 741E9
00cKC0MKS:1025 KC0TIU:24 0 741E9
00cKC0MKS:1025 KC0TIU:24 0 741E9
00cKC0MKS:1025 KC0TIU:24 0 741E9
00cKC0MKS:1025 KC0WDQ:24 0 72D40
00cKC0MKS:1025 KC0WDQ:24 0 72D40
00cKC0MKS:1025 KC0WDQ:24 0 72D40
00cKC0MKS:1025 KC0WDQ:24 0 72D40
00cKC0MKS:1025 KC0MKU:24 0 79B21
00cKC0MKS:1025 KC0MKU:24 0 79B21
00cKC0MKS:1025 KC0MKU:24 0 79B21
00cKC0MKS:1025 KC0MKT:24 0 757E0
00cKC0MKS:1025 KC0MKT:24 0 757E0
00cKC0MKS:1025 KC0MKT:24 0 757E0
00cKC0MKS:1025 KC0RTX:24 0 7975D
x00cKC0MKS:1025 KC0RTX:24 0 7975D
x00cKC0MKS:1025 KC0RTX:24 0 7975D
x00cKC0MKS:1025 KC0MKS:24 0 7B1A1
x00cKC0MKS:1025 KC0MKS:24 0 7B1A1
x00cKC0MKS:1025 KC0MKS:24 0 7B1A1
x00cKC0MKS:1025 KC0MKS:24 0 7B1A1
x00cKC0MKS:1025 N0MR:24 0 7B03A
00cKC0MKS:1025 N0MR:24 0 7B03A
00cKC0MKS:1025 N0MR:24 0 7B03A
00cKC0MKS:1025 N0IM:24 0 73C49
00cKC0MKS:1025 KC0FTN:24 0 7F19C
x00cKC0MKS:1025 KC0FTN:24 0 7F19C
x00cKC0MKS:1025 KC0FTN:24 0 7F19C
x00cKC0MKS:1025 KC0FTN:24 0 7F19C
x00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 W0KTX:24 0 73853
00cKC0MKS:1025 KC0TST:24 0 7ED9B
00cKC0MKS:1025 KC0TST:24 0 7ED9B
00cKC0MKS:1025 W4LX:24 0 7D68C
x00cKC0MKS:1025 W4LX:24 0 7D68C
x00cKC0MKS:1025 W4LX:24 0 7D68C
x00cKC0MKS:1025 W4LX:24 0 7D68C
x00cKC0MKS:1025 W4LX:24 0 7D68C
x00cKC0MKS:1025 VP6DX:24 0 7EB0E
00cKC0MKS:1025 VP6DX:24 0 7EB0E
00cKC0MKS:1025 VP6DX:24 0 7EB0E
00cKC0MKS:1025 VP6DX:24 0 7EB0E
00cKC0MKS:1025 KC0RCV:24 0 7EB37
x00cKC0MKS:1025 KC0RCV:24 0 7EB37
x00cKC0MKS:1025 KC0RCV:24 0 7EB37
x00cKC0MKS:1025 KC0RCV:24 0 7EB37
x00cKC0MKS:1025 KC0RCV:24 0 7EB37
x00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 W0RO:24 0 7490C
00cKC0MKS:1025 W0RO:24 0 7490C
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KI0DB:24 0 7F739
00cKC0MKS:1025 AA0AW:24 0 7ECF5
x00cKC0MKS:1025 AA0AW:24 0 7ECF5
x00cKC0MKS:1025 AA0AW:24 0 7ECF5
x00cKC0MKS:1025 AA0AW:24 0 7ECF5
x00cKC0MKS:1025 AA0AW:24 0 7ECF5
x00cKC0MKS:1025 AA0AW:24 0 7ECF5
x00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0ZZL:24 0 7E290
x00cKC0MKS:1025 KC0ZZL:24 0 7E290
x00cKC0MKS:1025 KC0ZZL:24 0 7E290
x00cKC0MKS:1025 KC0ZZL:24 0 7E290
x00cKC0MKS:1025 KC0ZZL:24 0 7E290
x00cKC0MKS:1025 KC0SJB:24 0 7810C
x00cKC0MKS:1025 KC0SJB:24 0 7810C
x00cKC0MKS:1025 KC0SJB:24 0 7810C
x00cKC0MKS:1025 KC0SJB:24 0 7810C
x00cKC0MKS:1025 KC0SJB:24 0 7810C
x00cKC0MKS:1025 K0JJR:24 0 7CDD2
00cKC0MKS:1025 K0JJR:24 0 7CDD2
00cKC0MKS:1025 K0JJR:24 0 7CDD2
00cKC0MKS:1025 K0JJR:24 0 7CDD2
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
x00cKC0MKS:1025 KC0MKS:24 0 7B1A1
x00cKC0MKS:1025 KC0MKS:24 0 7B1A1
x00cKC0MKS:1025 KC0MKS:24 0 7B1A1

Thanks again!
-Jeff


--- In NBEMSham@..., "Jeffrey P. Nast" <kc0mks@...> wrote:

Using flarq 3.0 and VBdigi 1.2.0...

I have noticed that the retry count fluctuates. With my laptop not
connected to anything (listening through the speaker), I will try
to "connect" to a number of different stations. Of course each one
will fail. But the number of retries for some attempts varies.

In the example below, for each "Connect" attempt I used a different
call sign. Notice also that an extraneous space character is
intermittantly inserted at the begining of some lines.

Questions:
* Does the "Retries" count in the flarq config also pertain to the
number of "Connect" attempts?
* Why does the number of connect attempts vary?
* Where does the intermittant extraneous space character in column
1
come from?

00cKC0MKS:1025 KC0TIU:24 0 741E9
:
:
00cKC0MKS:1025 KC0MKS:24 0 7B1A1

Great software! Thank you!

-Jeff Nast
KC0MKS


Connect Retries...

"Jeffrey P. Nast" <kc0mks@...>
 

Using flarq 3.0 and VBdigi 1.2.0...

I have noticed that the retry count fluctuates. With my laptop not
connected to anything (listening through the speaker), I will try
to "connect" to a number of different stations. Of course each one
will fail. But the number of retries for some attempts varies.

In the example below, for each "Connect" attempt I used a different
call sign. Notice also that an extraneous space character is
intermittantly inserted at the begining of some lines.

Questions:
* Does the "Retries" count in the flarq config also pertain to the
number of "Connect" attempts?
* Why does the number of connect attempts vary?
* Where does the intermittant extraneous space character in column 1
come from?

00cKC0MKS:1025 KC0TIU:24 0 741E9
00cKC0MKS:1025 KC0TIU:24 0 741E9
00cKC0MKS:1025 KC0TIU:24 0 741E9
00cKC0MKS:1025 KC0TIU:24 0 741E9
00cKC0MKS:1025 KC0WDQ:24 0 72D40
00cKC0MKS:1025 KC0WDQ:24 0 72D40
00cKC0MKS:1025 KC0WDQ:24 0 72D40
00cKC0MKS:1025 KC0WDQ:24 0 72D40
00cKC0MKS:1025 KC0MKU:24 0 79B21
00cKC0MKS:1025 KC0MKU:24 0 79B21
00cKC0MKS:1025 KC0MKU:24 0 79B21
00cKC0MKS:1025 KC0MKT:24 0 757E0
00cKC0MKS:1025 KC0MKT:24 0 757E0
00cKC0MKS:1025 KC0MKT:24 0 757E0
00cKC0MKS:1025 KC0RTX:24 0 7975D
00cKC0MKS:1025 KC0RTX:24 0 7975D
00cKC0MKS:1025 KC0RTX:24 0 7975D
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 N0MR:24 0 7B03A
00cKC0MKS:1025 N0MR:24 0 7B03A
00cKC0MKS:1025 N0MR:24 0 7B03A
00cKC0MKS:1025 N0IM:24 0 73C49
00cKC0MKS:1025 KC0FTN:24 0 7F19C
00cKC0MKS:1025 KC0FTN:24 0 7F19C
00cKC0MKS:1025 KC0FTN:24 0 7F19C
00cKC0MKS:1025 KC0FTN:24 0 7F19C
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 KC0PHK:24 0 78425
00cKC0MKS:1025 W0KTX:24 0 73853
00cKC0MKS:1025 KC0TST:24 0 7ED9B
00cKC0MKS:1025 KC0TST:24 0 7ED9B
00cKC0MKS:1025 W4LX:24 0 7D68C
00cKC0MKS:1025 W4LX:24 0 7D68C
00cKC0MKS:1025 W4LX:24 0 7D68C
00cKC0MKS:1025 W4LX:24 0 7D68C
00cKC0MKS:1025 W4LX:24 0 7D68C
00cKC0MKS:1025 VP6DX:24 0 7EB0E
00cKC0MKS:1025 VP6DX:24 0 7EB0E
00cKC0MKS:1025 VP6DX:24 0 7EB0E
00cKC0MKS:1025 VP6DX:24 0 7EB0E
00cKC0MKS:1025 KC0RCV:24 0 7EB37
00cKC0MKS:1025 KC0RCV:24 0 7EB37
00cKC0MKS:1025 KC0RCV:24 0 7EB37
00cKC0MKS:1025 KC0RCV:24 0 7EB37
00cKC0MKS:1025 KC0RCV:24 0 7EB37
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 KC0MKQ:24 0 76820
00cKC0MKS:1025 W0RO:24 0 7490C
00cKC0MKS:1025 W0RO:24 0 7490C
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KB0ROB:24 0 7D79F
00cKC0MKS:1025 KI0DB:24 0 7F739
00cKC0MKS:1025 AA0AW:24 0 7ECF5
00cKC0MKS:1025 AA0AW:24 0 7ECF5
00cKC0MKS:1025 AA0AW:24 0 7ECF5
00cKC0MKS:1025 AA0AW:24 0 7ECF5
00cKC0MKS:1025 AA0AW:24 0 7ECF5
00cKC0MKS:1025 AA0AW:24 0 7ECF5
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0NFB:24 0 7EEC9
00cKC0MKS:1025 KC0ZZL:24 0 7E290
00cKC0MKS:1025 KC0ZZL:24 0 7E290
00cKC0MKS:1025 KC0ZZL:24 0 7E290
00cKC0MKS:1025 KC0ZZL:24 0 7E290
00cKC0MKS:1025 KC0ZZL:24 0 7E290
00cKC0MKS:1025 KC0SJB:24 0 7810C
00cKC0MKS:1025 KC0SJB:24 0 7810C
00cKC0MKS:1025 KC0SJB:24 0 7810C
00cKC0MKS:1025 KC0SJB:24 0 7810C
00cKC0MKS:1025 KC0SJB:24 0 7810C
00cKC0MKS:1025 K0JJR:24 0 7CDD2
00cKC0MKS:1025 K0JJR:24 0 7CDD2
00cKC0MKS:1025 K0JJR:24 0 7CDD2
00cKC0MKS:1025 K0JJR:24 0 7CDD2
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 KC0MKS:24 0 7B1A1
00cKC0MKS:1025 KC0MKS:24 0 7B1A1

Great software! Thank you!

-Jeff Nast
KC0MKS


Re: NBEMS bug or question

"Allison Parent" <kb1gmx@...>
 

Well, I downloaded and tried the Puppy Linux live CD version and
that impressed me greatly. It loaded on everything I tried it on
even an older P166/mmx with 128mb and ran very well. The FLdigi
did everything I asked of it. Runs on IBM t21 laptop very well
and I plan to try it on a slower machine to see its tolerence.


Allison

--- In NBEMSham@..., w1hkj <w1hkj@...> wrote:

The vbdigi application is resizeable to a minimum size that fits on an
800x600 screen as several other users have indicated.

Resize mouse cursors should appear when the cursor in on any edge or
corner of the main dialog. It's been a long long time since I
looked at
W98, but you should also be able to open a windows menu by clicking in
the upper left hand corner icon. One of those menu items should be
Size
as well as Move.

73, Dave W1HKJ


Re: NBEMS Testing

"wy7usa" <wy7usa@...>
 

I could be available this weekend if you like.

My QTH is in north west Wyoming.

73

Eric / WY7USA

--- In NBEMSham@..., John Bradley <jbradley@...> wrote:

so where is anyone doing any tests on NBEMS? 30m works well daytime
from up
here in western Canada.



Have successfully transferred mail using MFSK, since that day had a
lot of
Doppler or "flutter" on my signal, a problem living at this latitude.



John

VE5MU


Disconnects

"wy7usa" <wy7usa@...>
 

Tried the program today for few hours with a fellow ham a few miles
away on 2m ssb. It worked quite well.

We did experience a few disconnects where one station disconnects
(probably times out somehow) while the other one is still showing a
connection. There doesn't appear to any way short of terminating flArq
to force the remaining station to also disconnect so a reconnect will
be possible.

A way to ungracefully terminate a connection could be useful. It felt
like the connections are not very robust and that a single missed
keep-alive packet could cause a connection loss. (Not sure about the
last one, as I haven't studied the protocol in detail yet).

73

Eric / WY7USA


Re: Tx Offset usage

"wy7usa" <wy7usa@...>
 

I believe the txOffset is for calibration of differences in the TX and
RX clocks. See the help file of the MMVARI programm on how to
calibrate this with the help of an external loopback cable.

73

Eric / WY7USA


--- In NBEMSham@..., w1hkj <w1hkj@...> wrote:

The current /Tx Offset/ control will allow you to enter values beyond
the allowable limits of the MMVARI encoder/decoder. The /Tx Offset/
control will change to a combo box pick list for the next version. In
the meantime do not enter values larger than +/- 20 Hz. This
control is
used to compensate for *small* differences between Rx and Tx
frequencies. The difference is the combined error of your sound card
codec and your transceiver. Start with a 0 Hz offset. If you find
that
your Tx signal is 10 Hz higher than your Rx point then enter 10 Hz into
the control and vbdigi will subtract 10 Hz from the transmitted audio
waveform.

If you want to a large frequency differential between Rx and Tx then
you
should use the /Split/ control for that purpose.

Remember that there is on-line help for vbdigi:
http://w1hkj.com/vbdigi-help/vbdigi.html

73, Dave, W1HKJ


Re: NBEMS bug or question

w1hkj <w1hkj@...>
 

The vbdigi application is resizeable to a minimum size that fits on an 800x600 screen as several other users have indicated.

Resize mouse cursors should appear when the cursor in on any edge or corner of the main dialog. It's been a long long time since I looked at W98, but you should also be able to open a windows menu by clicking in the upper left hand corner icon. One of those menu items should be Size as well as Move.

73, Dave W1HKJ


Re: NBEMS bug or question

"Allison Parent" <kb1gmx@...>
 

--- In NBEMSham@..., roger g6ckr <radio@...> wrote:


On Tue, 2008-02-12 at 16:39 -0600, w1hkj wrote:
You just might be pushing the limits of antiquity Allison. What
size is
your screen? The software was designed to run on W98 through
Vista, but
you are the first to report trying this with a W95 hybrid. VB6
handles
all screen dimensions in Twips. The minimum width for the
application
is 7500 Twips. That will correspond to a different number of pixels
depending on your screen width in pixels. It has been run
successfully
on screen sizes of 1024x768 and up. Are you using something smaller
than that?

Dave, W1HKJ
Hi.
I just tested on a 500Mhz win98 laptop.
with bit of fiddling I can get what looks like a usable screen with
800x600 and the even lower screen size of 640x480.
by dragging the window about to get to the edges I manged to size it to
fit.
I then tried maximising it and that also made it fit.
I hope that is useful.
73 Roger G6CKR
Sorry no.

Minimized is 99% full screen and no resize. Maximized fills teh screen
but I expect that as normal.

What I can't do is grab a corner and shorten or make the screen
narrower at all. This is a problem as if there something on the
desktop I need I have to minimize to taskbar rather than have it at
and edge where I can pick it up.

Allison


Re: NBEMS bug or question

"Rich Newsom" <richwa4sxz@...>
 

I just fired up the old reliable Win98se test bed and set a 640x480
and had no problem resizing the window to lsee than half of the
screen. This on a P1-200mmx processor w 132M of SDram. Video is old
Matrox Mystique with 4M of ram. I still have a Win95 box with a 1
gig scsi drive to hook up but the dust storm when I start it may
drive me out of the shack.

Try selecting a different font, see what happens. I have a large font
selected so I can monitor while across the room. I've left this
setup running NBEMS & Rigcat for 3 days continuous without ever
missing a thing.

Rich
WA4SXZ

--- In NBEMSham@..., "Allison Parent" <kb1gmx@...> wrote:

I added the software V1.2 to my system and found an annoying bug.

The digi software does not resize to less than a full screen with
overhang. Makes using the buttons and sliders along the edges
hard to use.

Any thoughts?

System is W98se hybrid (no IE/OE and W95 gui). This is a fully
tested system with a larger group of Digi modes.

Allison
KB1GMX


Re: NBEMS bug or question

roger g6ckr <radio@...>
 

On Tue, 2008-02-12 at 16:39 -0600, w1hkj wrote:
You just might be pushing the limits of antiquity Allison. What size is
your screen? The software was designed to run on W98 through Vista, but
you are the first to report trying this with a W95 hybrid. VB6 handles
all screen dimensions in Twips. The minimum width for the application
is 7500 Twips. That will correspond to a different number of pixels
depending on your screen width in pixels. It has been run successfully
on screen sizes of 1024x768 and up. Are you using something smaller
than that?

Dave, W1HKJ
Hi.
I just tested on a 500Mhz win98 laptop.
with bit of fiddling I can get what looks like a usable screen with
800x600 and the even lower screen size of 640x480.
by dragging the window about to get to the edges I manged to size it to
fit.
I then tried maximising it and that also made it fit.
I hope that is useful.
73 Roger G6CKR


Re: NBEMS bug or question

"Allison Parent" <kb1gmx@...>
 

--- In NBEMSham@..., w1hkj <w1hkj@...> wrote:

You just might be pushing the limits of antiquity Allison. What
size is
your screen? The software was designed to run on W98 through Vista,
but
you are the first to report trying this with a W95 hybrid. VB6 handles
all screen dimensions in Twips. The minimum width for the application
is 7500 Twips. That will correspond to a different number of pixels
depending on your screen width in pixels. It has been run successfully
on screen sizes of 1024x768 and up. Are you using something smaller
than that?

Dave, W1HKJ
The screen in use is a CRT that will go pop if I ask the card to do
more than 800x600. If I switch to the flat panel it sill looks poor
at 1280x1024 and doesn't resize. The system in use (98hybrid) has
a good and very flexible video card in it. The program runs fine
otherwise and the CPU isn't even working hard.

When tried on the WIn2k box and the XP box the problem was the screen
has two sizes large and way too large with no resize. That was viewed
on a screen that was 1600x1200. I expect windows apps to resize
when I grab a side or corner and the copy I have does not do this.

That size issue made it unusable on the laptop that was also limited
to 800x600.

Hope that helps with the explanation.


Re: NBEMS bug or question

w1hkj <w1hkj@...>
 

You just might be pushing the limits of antiquity Allison. What size is your screen? The software was designed to run on W98 through Vista, but you are the first to report trying this with a W95 hybrid. VB6 handles all screen dimensions in Twips. The minimum width for the application is 7500 Twips. That will correspond to a different number of pixels depending on your screen width in pixels. It has been run successfully on screen sizes of 1024x768 and up. Are you using something smaller than that?

Dave, W1HKJ


NBEMS bug or question

"Allison Parent" <kb1gmx@...>
 

I added the software V1.2 to my system and found an annoying bug.

The digi software does not resize to less than a full screen with
overhang. Makes using the buttons and sliders along the edges
hard to use.

Any thoughts?

System is W98se hybrid (no IE/OE and W95 gui). This is a fully
tested system with a larger group of Digi modes.

Allison
KB1GMX


Tx Offset usage

w1hkj <w1hkj@...>
 

The current Tx Offset control will allow you to enter values beyond the allowable limits of the MMVARI encoder/decoder.  The Tx Offset control will change to a combo box pick list for the next version.  In the meantime do not enter values larger than +/- 20 Hz.  This control is used to compensate for small differences between Rx and Tx frequencies.  The difference is the combined error of your sound card codec and your transceiver.  Start with a 0 Hz offset.  If you find that your Tx signal is 10 Hz higher than your Rx point then enter 10 Hz into the control and vbdigi will subtract 10 Hz from the transmitted audio waveform.

If you want to a large frequency differential between Rx and Tx then you should use the Split control for that purpose.

Remember that there is on-line help for vbdigi: http://w1hkj.com/vbdigi-help/vbdigi.html

73, Dave, W1HKJ


Re: Ver 1.2 Slow transmit?

"wy7usa" <wy7usa@...>
 

The computer is a HP Pavilion AMD Athlon 64 X2 Dual Core 4200+
The internal soundcard driver is a Realtek AC'97
The radiointerface is a SignalinkUSB (External Soundcard USB Audio device)

I only have one version of MMVARI.ocx installed, ver. 1.0.0.6, the
same version that came with NBEMS.

I do have the MMVARI programm installed. It works fine.

In the files section, you will find a recording of RTTY and PSK31
sending the text "CQ CQ de WY7USA".

Well, I'll do anything to help (I also am a programmer, btw.), but am
out of ideas.

73

Eric / WY7USA

--- In NBEMSham@..., w1hkj <w1hkj@...> wrote:

Good morning Eric,

Your's is the first report of a "slow" sound card interface.

Would you be so kind as to provide some additional information; Make
and
model of computer, Sound card being used.

Is any other program concurrently sharing the sound card with vbdigi?

Thanks, Dave, W1HKJ


New file uploaded to NBEMSham

NBEMSham@...
 

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the NBEMSham
group.

File : /slowaudio.mp3
Uploaded by : wy7usa <wy7usa@...>
Description : Slow Audio in ver. 1.2

You can access this file at the URL:
http://groups.yahoo.com/group/NBEMSham/files/slowaudio.mp3

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/l/us/yahoo/groups/original/members/web/index.htmlfiles

Regards,

wy7usa <wy7usa@...>


Re: Ver 1.2 Slow transmit?

w1hkj <w1hkj@...>
 

Eric,

I see from an earlier posting that you are using the SignaLinkUSB. That is the same setup as here and I have not experienced any such slow down on the audio.

One other thought. Do you have an MMVARI.ocx control installed from some other program that uses the control? If so it might be a incompatible ocx control problem. All of the audio i/o is integral to that control.

73, Dave, W1HKJ


Re: Ver 1.2 Slow transmit?

w1hkj <w1hkj@...>
 

Good morning Eric,

Your's is the first report of a "slow" sound card interface.

Would you be so kind as to provide some additional information; Make and model of computer, Sound card being used.

Is any other program concurrently sharing the sound card with vbdigi?

Thanks, Dave, W1HKJ