Problems getting TH8800 Thermotron drivers to work with windows 7

[Crushed]

I am having problems getting my Thermotron TH8800 drivers to work with Windows 7 64-Bit pro. They work in XP mode but I noticed while searching the forums to get communication between my PC and the chamber to work that using a virtual machine might actually be my problem. Now though I'm forced back to fixing the problem that forced me into the VM originally. The dll files for my drivers are not being read by win. 7. Can anyone help me with this issue?

Thanks in advanced!

I have also attached a picture of theerror message I keep getting. As well as the drivers I am using.

[Crushed]

The question still stands. I have been working on it off and on all day, still without success.

 I think I forgot to mention that I am using LabVIEW 2009 SP1 64-Bit version. Everything works fine on my XP machine, but my company is trying to make the jump to Win 7 and I am the test subject. That means I can't just let this bug lie and go back to XP where everything works.

 Once again. Thanks in advanced!

[RavensFan]

Can a 64 bit LabVIEW environment work with 32 bit drivers in a 64 bit Win7 OS?

I'm thinking you are going to need 64 bit drivers from Thermotron for this to be able to work.

[Crushed]

Problem is they don't have 32-bit drivers. Well at least I couldn't find any if they do.

This brings up a good idea though, if I were to use the 32-bit version of LabVIEW on my 64-bit pc, would this possibly fix the problem?

I did recompile the drivers using the 64-bit version of LabVIEW in hopes that that would change things, but I guess it didn't. I'll check this out tomorrow and report back.

[RavensFan]

???

You said their drivers are using .dll's.  Which I am assuming they are 32 bit .dll's since you said it works with WinXP.

I don't know how you are able to recompile their drivers.  You may be able to recompile their LabVIEW files, but you aren't going to be able to recompile their .dll's to be 64-bit.

[Crushed]

K, well then, I recompiled the LabVIEW files just like the readme that came with the drivers told me to do.

I went to tools -> advanced -> mass compile.

I'm rather unfimiliar with dll files, are they reliant on the bit type of the OS to run or the program that is trying to run them?

[RavensFan]

---

@Crushed wrote:

K, well then, I recompiled the LabVIEW files just like the readme that came with the drivers told me to do.

I went to tools -> advanced -> mass compile.

I'm rather unfimiliar with dll files, are they reliant on the bit type of the OS to run or the program that is trying to run them?

---

Yes.  DLL stands for dynamic linked library.  They are precompiled routines and are compiled for running on either a 32 bit or 64 bit processor.  It is one of the issues why you can't drivers for some kinds of hardware to run natively on a Win7 64 bit OS.  Fortunately, most things still work because Win7 has a 32-bit environment it can run things in.  That is why there is still a system32 driver directory and 32 bit programs can run, but are installed in the Program Files (x86) directory.

If you've been reading the forums, you'll see that NI itself hasn't created all the drivers needed for LabVIEW 64 and why certain toolkits won't work with it.

[Crushed]

Yes, I did see that. I was hoping though that there might be away around that problem. But from the looks of things I'm going to have to try a clean install with a 32-bit version.

I did try running it with the 32-bit Version of LabVIEW. Unfortunately it didn't work. But I feel as if that was to be expected.

So would moving to a 32-bit Version of Windows 7 fix this issue?

[RavensFan]

I would have expected 32 bit LabVIEW with 32 bit dll's on Win7 64 bit, but was executing in it's 32-bit environment would have worked.

If it's not, I'd suggest you try contacting Thermotron.

[Crushed]

Called Thermotron support. They couldn't help. As far as they new I shouldn't be having any problems with using the drivers.

I'm going to try and use the drivers on another system with Win 7 pro 64-bit and see what happens. If they work there then it's just something up with my machine and getting a different version of windows may not help.

Once again thanks for the help and suggestions.