I was talking with someone yesterday who was using it with LOGic 9 without problems. He really liked it too BTW.

What does the error message say? As usual, we can expect a lot of problems with USB=>RS232 drivers, particularly non-FTDI stuff. I don't know if FTDI will work on Win 10 or not, but if they don't it's just a matter of time.

Windows 10 works pretty much perfectly with every app I throw at it EXCEPT Logic. I have had it working a couple of times but then various errors crop up; mostly the infamous OLE errors. There have also been NET errors and the latest a Fox Pro version error.

I have used and really liked LOgic for several years but this is about to get the best of me. I have experimented with several other loggers with absolutely no problems. I prefer LOgic but Windows 10 will soon be the OS of choice and necessity. At this point LOgic is just not compatible with Windows 10.

If I am missing something I would love to be educated. Meanwhile I will have to continue to explore other options.
73,
Gene K3GC

Preliminary tests done by one of our business clients using VFP is that VFP itself works flawlessly, and runs even faster to boot.

The errors reported here and from other LOGic users seem to be related to USB=RS232 adapters. (These errors are occurring in Windows, being passed to LOGic, and yes, would occur whether the rig is connected or not).

Apparently USB=>RS232 drivers are a still problem.
http://www.usconverters....0-USB-to-Serial-Adapter

(An aside, be sure to read the link "Why most serial adapters will not work on Win 7 or 8." It says that most non-FTDI adapters support about only 60% of the RS-232 standard.)

http://answers.microsoft...-4c06-b4fb-89b45d005ca0

Another issue is LOGic being tied to internet explorer, and with that being discontinued and replaced with something else, it is possible that LOGic may not control whatever browser is the default in Win 10. Fortunately it looks like we will be able to support FireFox and/or Chrome.

Anyway, when FTDI comes out with a driver for Win 10, I will start testing! Not time to panic yet.

Tnx & 73,

Dennis WN4AZY

Ok, your rig basically has a built-in USB=>RS232 adapter. You CAN change the driver. It is just another Windows driver. Hopefully Yaesu or their chip vendor will update the driver.

If other programs are working with the current FTDX3000 driver but LOGic is not, you could try using OmniRig. It may or may not work with Win 10.

Another possible issue with Win 10 and LOGic is that Win 10 may not have the .Net framework 2.0 installed. It is easy enough to add. If there is an option to add .Net 3.5 in Add/Remove windows features, that will work. We will be going to 4.5 soon anyway.

Tnx & 73,

Dennis WN4AZY

OK, I have pretty much gone as far as I can with Logic and Windows 10 build 10041.
Logic seems to perform quite well so long as you don't try to change com port settings. If you attempt to go to Tools, setup, misc ham setup the errors crop up and logic is done.
The same is true of attempting to invoke tools, advanced, serial port status except that Logic doesn't shut down you just end up with a blank status screen. Clearly this is a com port issue. I do not believe it is an issue with com port drivers. I have experimented with DXSuite and Log4OM fairly extensively and they have no problem with any com ports that I use. My com hardware is as follows. PCIe add-on card has two ports and an on-board port. I also have two (not in service presently) USB>rs232 adapters with the FTDI chipsets. When I use them they perform identically to the board mounted ones.
I hope this is of some help. Of all the choices out there I prefer Logic.
73,
Gene K3GC

Thanks Dennis,
I hope you are right. The only comment I would add is that I do not use the USB>RS232 adapter. I use only the PCIe and integral com only,
73,
Gene K3GC