Is anybody running this combo ?
I just upgraded to '10' and my
DATS comes up but is dysfunctional
I just upgraded to '10' and my
DATS comes up but is dysfunctional
That's one of many reasons I gave up on Win 10, many of the programs I run either became flakey or just wouldn't run at all.
Have you tried to contact them? tech@parts-express.com or 800-338-0531 x1.
Or you could try this: http://www.parts-express.com/dayton-audio-dats-v2-computer-based-audio-component-test-system--390-806#lblProductQ&A
Another thought, I don't know if Win 10 works the this way but you could try right clicking the DATS icon and selecting "Properties" and the "Compatibility" tab and "Run this program under compatibility mode for" Win 7 or Win XP mode.
Mike
Last edited:
> Have you tried to contact them?
No ........ Just manifested ............
caveat :
my 2nd goround w/10
actually DATS runs best
in WINE ........... 🙂
No ........ Just manifested ............
caveat :
my 2nd goround w/10
actually DATS runs best
in WINE ........... 🙂
Last edited:
I also am having trouble getting a DATS 2 to run under Windows 10. Parts Express thinks it's a hardware problem and asked me return it. Personally, I suspect Windows 10....
Sorry guys super old topic I know
Dtas V2 in win 11 just opens then crashes,
I installed via DL from Dayton site since new pc doesn't have a rom drive.
Do I need to just buy the new V3?
Dtas V2 in win 11 just opens then crashes,
I installed via DL from Dayton site since new pc doesn't have a rom drive.
Do I need to just buy the new V3?
It’s one of these external Windows things; upgrade to fix one bug (or dozens), it breaks something else.
I’m running Windows 10, WT3 with DATS V3 software.
It works fine. Occassionally when it does something funny I reboot my computer and recalibrate the leads and impedance with the 1K resister and off it goes, working again.
I’m running Windows 10, WT3 with DATS V3 software.
It works fine. Occassionally when it does something funny I reboot my computer and recalibrate the leads and impedance with the 1K resister and off it goes, working again.
I remember trying to see if I could use the DATS program with my WT3 a few years ago. Running W10, the program would open and then close after a few seconds, so it might be some other problem that isn't specific to W11.
While typing this reply I just tried DATS V2 again on my W10 machine and it does the same thing. Still had the v2.1.1 setup file I tried before, but also downloaded v2.1.2. No luck.
EDIT: Tried it on a W10 laptop I rarely use and it works fine. Weird.
While typing this reply I just tried DATS V2 again on my W10 machine and it does the same thing. Still had the v2.1.1 setup file I tried before, but also downloaded v2.1.2. No luck.
EDIT: Tried it on a W10 laptop I rarely use and it works fine. Weird.
Last edited:
Ill try on a win 10 pc and see if that makes any difference.
Thanks for the input
Thanks for the help.
I have a Dell pc with 10 on it I will try, and it has a dvd drive too in case the rom version makes a difference!
Yeah, I don't know why it runs on one install but not the other. The laptop is an old Intel i5 Toughbook from 2010 that I mainly use for vehicle diagnostics a few times a year, so the W10 install is pretty clean. My main PC is an AMD Ryzen build, but the windows install is around 4 years old and has seen heavy use. Probably time for me to do a clean install, but I don't even want to think about it right now.
I am mining on all but one pc, and they are all 2021 PCs except for the Dell that is like 6 years old with an I5 also.
I might do a clean install on the Dell if it doesnt work right away.
It has Games on it mainly. I was gaming on there with an RTX3060 till I burned out the MB with too much draw through the slot.
I replaced the MB and it has sat since.
The Dell pc with win 10 worked. I didnt check what build it has though.
guys Im facing a different challenge in here. Im able to get test lead calibration and 1k resistor calibration as predicted but when I measure Fs seems fine but the Qts values are above 0.15 to 0.25 more than the specified value by the seas or other drivers tested many drivers but the offset is there. Running Windows 10 with mic permissions allowed and volume at 100. Is the hardware gone? or is it the OS which is creating the problem?