Really, in this case, Google is you friend...not eHam.

Found in 10 seconds:

http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=10&PFid=15&Level=4&Conn=3&ProdID=23&DownTypeID=3&GetDown=false&Downloads=true#221

The drivers can be downloaded from here.  Just scroll down to the appropriate section and download the Windows drivers.


73

Dave
K3DCW

The Feld Hell Club runs a 40m Feld Hell net at 0100-0300 UTC on Thursday (Wednesday evening local time in US/Canada) around 7073 kHz.

After the net, there is usually a small flurry of activity around this frequency as various net participants spread out and work Feld Hell for an hour or so.

------------

Here's the announcement from last week's net:   

Title:         40 meter Net
 
Date:         Thursday 3 November 2011
Time:         1:00 - 3:00
Repeats:         This event repeats every week.
Location:         7.073 MHz ---- transmission frequency
Notes:         Net time is in UTC.

QNI will begin at approximately 0045 hours.

All participants welcome.

------------

73,

Dave
K3DCW

This is an easy fix.  The problem is with the USB-Serial adapter.  HRD does NOT work well with Prolific chip sets.  It may work with everything else, but HRD will choke and often give the Blue Screen of Death when using a Prolific chip set.

The solution is simple, and is 100% effective.  Switch to a FTDI-based chip set.  This solution is well documented here, on QRZ, and on the HRD mailing list. 

73

Dave
K3DCW

MacLoggerDX is just one choice....there is competition and choices on OS X; however, most don't get past MLDX to try the others.

My personal choice on OS X is RUMlog.  There is also Aether, YeaLogger, jLog, and likely a couple more.  For contest logging, both RUMped and Skookum Logger are outstanding. Finally, Fldigi has a built-in logbook program as well.

And don't forget, as Dave (AA6YQ) will likely remind us, DX Lab software runs just fine in Parallels as does most other Windows logging software. 

I, for one, would love to see HRD ported over to OS X (and Linux!). 

73,

Dave
K3DCW

WxWindows (now WxWidgets, btw) is a good tool.  Audacity uses it too good effect, for example.  And it supports a lot of the host system's window management capability and design.

Another possibility for cross-platform coding is the Fast-Light Toolkit (FLTK), used by the Fldigi/Flwkey/Fllog/Flrig programs, among others.  The biggest negative is that it uses its own interface design instead of the host system.  On the other hand, it would allow you to develop an unique "HRD" look that would hold cross-platform and it is designed to be Fast and Light, and thus high-performance even on systems with less horsepower.

73

Dave
K3DCW

As I said, Dave, the DXLab suite is a great package of programs. 

My only point being that if you want to run Windows, run Windows. If you want to run OS X, there are comparable packages on OS X as well.  And, while Parallels is great, if you really want to run Windows programs, BootCamp is probably a better choice to start with (from a performance standpoint) although it does take you out of the OS X environment.   

Ideally, all software would be written to be platform-agnostic, much like Fldigi which runs on Windows, Linux, OS X, and BSD. However, that isn't the case, so we have to deal with various ways to run various software packages.  The beautiful thing is that it can be done, in most cases; and at least we do have a choice in software.

73,

Dave
K3DCW

As pointed out, it does run in Parallels.  However, why do that when there is some great OS X native software out there.

MacLoggerDX, RUMlog (my personal favorite, and FREE!!!), Aether all do logging, telnet to the DX clusters, award tracking, and much more.

Spot for dedicated DX cluster support

Fldigi/cocoaModem for digital modes (Fldigi can't be beat on any platform!!!)

Flwkey for WinKey USB support on any platform

Flrig for rig control on any platform

MultiScan for SSTV

Fllog for multi-op log access

RUMped and SkookumLogger for contest logging

Combine Flrig/Flwkey/Fldigi and, if necessary, Fllog and you have a cross-platform, open-source HRD/DXLab type of integrated suite running natively on OS X.

...and there is a lot more that I didn't mention.

Not to take anything away from DXLab...it is a great suite.  My point being that there is a LOT of great ham radio software that is native to the Mac.

73

Dave
K3DCW
www.k3dcw.net

That should be K3DCW's web site, I presume.  That being said, I'm glad you found it to be of use.  That is why it is there.

73

Dave
K3DCW

Glad to hear you got it working.  Keyspan with the Mac is undoubtedly the best way to go.

73

Dave
K3DCW

How are you connecting the USB-Serial cable to the FT-897D?  Are you using the CT-62 cable?

There is no serial connection on the FT-897D, so something is missing in your description.


Also, I'm not sure about the IOgear adapter, but the best adapter I've seen for the Mac is the Keyspan adapter.  A bit expensive, but it is worth it.

Dave
K3DCW

Some really good options are available on the Mac.

Besides CocoaModem, look at Fldigi for digital modes.  It does a lot more than CocoaModem, although in a cross-platform interface rather than the beautiful Cocoa interface of CM.  Fldigi is my primary digital program.  It supports RSID, a LOT more modes, interfacing with online databases/PSKreporter, and can be connected to RUMlog for auto import into RUMlog's database.  You can even use RUMlog to handle the tuning of the rig and just use Fldigi as the digital component.

The MKII is NOT supported by OS X directly, and there are no drivers for it.  This is because the MKII has a variety of low level functions that need to be addressed directly.  uH Router does provide access to most of these functions, and does work with MLDX and CocoaModem. RUMlog also has its own version (RUMrouter) that does the same thing. 

I found that the US Navigator Interface is a GREAT tool for OS X, with built-in RS-232, Soundcard, FSK, and WINkeyer support along with support of OS X directly.

Other programs to check out would be things like Flwkey, Flrig, MultiScan SSTV.  Both RUMped and Skookum Logger are good for contest loggers. JT65-HF runs on OS X in Crossover for Mac.  WSJT can be compiled and run on OS X as well, if you're comfortable working at the command line. 

The software I have in everyday use on my Mac is as follows: RUMlog, Fldigi, JT65-HF, and Flwkey.  RUMped and Skookum Logger are both used; I haven't used one or the other enough to determine a favorite yet.

Dave
K3DCW

No, not likely. 

There is no requirement for 3 kHz separation, just like there is no requirement for 3 kHz of bandwidth in a SSB transmission.  Many hams run a lot smaller bandwidth.  You are just used to the greater dynamic range offered by the 3 kHz bandwidth.

Using 3kHz and 100w, you are putting out a slightly weaker signal than someone running 2.4kHz and the same 100w due to spreading that energy across a greater bandwidth.  Many contesters use 2.4kHz or even as small as 1.8kHz to get their signal out just that much better.  True, it isn't the best dynamic range, but it get's the job done and allows for more congestion on the bands. 

That being said, there is no excuse for jumping into someone's passband and calling away, interrupting an ongoing QSO.  That's just bad manners.

73

Dave

I think that as NN4RH so accurately indicates through his actions, the lookup count counts for nothing and is indicative of nothing, so why worry about it.

73,

Dave
K3DCW

The problem is the Prolific driver.

The solution is easy....get an adapter with the FTDI chipset. 

HRD and Prolific, especially on Vista/Win7 and even more so with 64-bit Vista/Win7, don't get along well.  A quick check of the HRD Yahoo group will show dozens and dozens of people with the same problem, all solved by switching to an adapter with the FTDI chipset.

Dave
K3DCW