Hi Dave,

There are several settings needed to make it all work.


I attach my info hoping it will be clear enough to get going. If not, let me know. I also use Win7 and your FLdigi version is fully functional.


Good luck!


73s SWL Tobias
.-.-.

I recently upgraded to V. 4.2.06 from an earlier version.听 On the earlier version, the RxID function was working properly, but since the upgrade it is not.听 I have both RxID and TxID enabled.听 I am running the program on Windows 7 Pro.听 No changes that I know of other than the version upgrade to 4.2.06.听 Is anyone else having this issue?听 Assuming not, any suggestions?听 I use Fldigi on a net where we often switch between MT63 and Olivia depending on propagation, and the TxID/RxID functionality is much appreciated.

听

73,

听

Dave, W9PFD

听 听

听

听

Goes to British sundial...

--

73, Lem W1LEM

Bob

Thanks for suggestions. Turning squelch off and changing the Tx speeds seems to have done the trick. Now copying both Rx code and and my sending - which is what I was really after. Wanted to improve sending technique

听

听

73 Paul w2eck

So there is no way just to move them around I take it, not the answer I was hoping for but it is what it is.

Thanks for the info guys! I set it up and now I have alerts that I can hear from across the room.

73

Hi Dave,

Using Windows11, Fldigi v.4.2.06 and Flrig v.2.0.05 I'm trying to configure these softwares with a QRP-Labs QDX, mainly for use of RTTY mode.

I succeeded in configuring both "Rig control" and "Soundcard - Devices" and everything works nicely.

BUT, even after clicked on "Configure" then "Save config" on top of Fldigi screen the configuration is not properly saved since next time I restart Fldigi I need to open the Configuration again and click on Portaudio in Soundcard-Devices: Portaudio does not remain checked.

Any idea to help solve this inconvenience?

73 - Pierre - FK8IH

In听 receiving CW - in my v4.2.06,07- the cw is being properly decoded on the ARRL broadcast in the signal browser window -but not showing up in the yellow decode window- any ideas on how to fix?

Second problem, when I am trying to decode my own sending - I can see the code TX breaks in the waterfall in Fldigi but again it's not being decoded in the yellow decode window. Again , any ideas on how to get this working.

Am sure both are just settings I have incorrect.

83 Paul w2eck

Hello Paul,

In addition to David's reply (he's faster than me ;-), here are my thoughts and suggestions.


I've also been struggling with C: getting full quite a bit over the years, on different PCs.


But honestly, I would not generally recommend moving functional installed program files elsewhere unless there's a REAL need to do so. because these are files Windows governs quite rigorously. As David has pointed out, for FLdigi, there's a good way to do so, as I explain below.


On the other hand, it usually is the DATA that grows somewhat excessively over time, rather than the programs themselves.


If I may first suggest a different approach (just as an alternative - or simply as a logic check upfront):


Download and install the TREESIZE FREE software from https://www.jam-software.de/treesize_free/.

It is about 8 MB, install it (at least temporarily) where ever it makes most sense to you.

Then take the time, open it, select Drive C: and let it analyze and show you, which files and folders actually take up how much space on your hard disk.

It's very simple and intuitive, IMHO, and quickly gives you a good idea, where the storage really gets absorbed, both visually (the size of the graphical elements is proportional to the space needed on the HDD) and in a folder view, giving the numerical statistics per folder / subfolder etc.


One general word of caution, since this is a common source of confusion: some (even huge) files used by Windows may APPEAR to exist twice or more often in different locations, looking like obsolete multiple copies. In reality, there's a (usually hidden) way of creating so-called 'hard links' between files. Or rather, these make a SINGLE file appear in different places, as if it were physically there separate times. But in fact, deleting one of them, if they are in fact hard linked, will remove all others of the same name, too. So don't try and remove unknown Windows 'stuff' that might fall in this category, because it may do more harm than good!

On the other hand, it is usually safe to remove any files in temporary 'Temp' folders, because those files still being used will deny being deleted anyway.

Finally, depending on the kind of data filling up your hard disk, compressing the respective folders and the files contained therein (Right Click on the folder, Properties, Advanced => Compress...) may be effective. But it will not help in a relevant manner in all cases, where the data consists of already packed or other binary data, such as audio, video, image, office files.


well, if your Treesize (or personal) analysis result is, that it's really the program installations that you need to move for space reasons, well, go ahead and do so. But in most cases, this will probably require an uninstall / re-install of the respective software packages. With possible side effects, because Windows may be picky or restrictive in certain cases. You have been warned ;-)


- - - - - -


As David pointed out, there is a functional and useful procedure in the FLdigi Manual, which may help for your 'relocating' project (the following is basically copied from the Help file):


Installing fldigi on a thumb drive

Installing fldigi (and any of the other NBEMS flxxxx applications) on a thumb drive is very simple. Create a folder on the thumb drive named 'FL_APPS'. Then copy the fldigi executable to that folder. Note that folder FL_APPS may reside on any hard drive, or removable drive (including a rewritable CD/DVD) on your system. Copy the executable for flarq, flrig, flmsg, flamp, etc to that same folder if you want to have a complete NBEMS installation on that device:
fldigi.exe
flarq.exe
flmsg.exe
flamp.exe
flrig.exe

The key to using the applications thus installed is to execute the program from that folder.
This is best accomplished by opening the FL_APPS folder using the system files explorer. Then start the application by double clicking on it's icon.
You will be guided through the new install wizard the first time you do this and fldigi will place all of it's configuration folders in the same folder from which it was started. For example, if the [thumb] drive were device "D:"
D:\FL_APPS\fldigi.exe
D:\FL_APPS\fldigi.files
D:\FL_APPS\fldigi.files\fldigi_def.xml
etc ...


- - - - - -


Now if you first run FLdigi from the new D:\...\FL_APPS\... folder, check whether it actually reads the config etc. from the new location, a sub-folder under D:\...\FL_APPS\...., by opening the Menu - File - Folders - Fldigi Config... => verify that the opening drive and folders are the ones you wish to use, and do the same for the other folders and Macros to be sure.

If the OLD data has not been transferred correctly while installing FLdigi in the D:\...\FL_APPS\... folder, you can shut FLdigi down, copy all your existing data (overwriting any existing newer files on D:) with your original 'OLD' user files from Drive C:

COPY FROM ... C:\users\Paul\fldigi.files\*.* [or where ever your data location currently is - and keep it as a backup for the time being]
COPY -TO- ... D:\...\FL_APPS\fldigi.files\*.* [the new FLdigi data location]

RUN FLdigi from the new location again.

Now at last, the (copied) original data should be properly read from the new D: location, giving you the 'usual' look and feel from the old installation.

Once all is OK and after you have verified (confirmed!) all your user settings, macros, logbook etc. to be OK, you can remove your OLD installation and data files from the C: drive. Yet, I'd still keep a copy somewhere for a while, just in case, instead of deleting the files for good.


I cannot give a guarantee that this works in your case, but I've tried it here in a similar manner, and it appears to work just fine.

So in case you find anything going wrong or not being properly described above, please let us know, to the benefit of any future requests of this kind. Thank you.


Good Luck!



Best regards
Tobias
.-.-.

See