|  themike
 -Interested User-
 Posts: 3
 Joined: Jul 10, 2010
 
 
 
 | 
			
			Posted: Jul 11, 2010 12:08 AM
			  
			    
			  
			
			  
			Msg. 1 of 4
		I have a DTN dish/receiver that is used for DTN Meteorlogix. Previously the host PC was rented from DTN (it was an 8-9 year old Dell optiplex/Win2k). The decision was made to purchase a new PC in leiu continuing to rent. Unfortunately, the new PC has Windows 7 64bit edition loaded on it.
 Per instructions from tech support I downloaded AviationSentry from ftp.meteorlogix.com/pub/temp/AVS5.01.050610/
 
 The issue is that I cannot get the USB device driver for the receiver (Velocity/DtnRcUsb.sys) to load. Is this device even supported on Windows 7?
 
 I am not sure of the receiver model is at the moment, but I know that it in addition to USB, it also has an Ethernet and a serial (8P8C) connector on the back.
 
 I have also been unable to find any information on how to use the Ethernet connection. I assume that a certain IP/netmask will need to be statically assigned on the host PC.
 
 I apologize if this is not the proper forum to ask these questions. Any information or links on how to complete the setup would be most appreciated.
 | 
	|  themike
 -Interested User-
 Posts: 3
 Joined: Jul 10, 2010
 
 
 
 | 
			
			Posted: Jul 11, 2010 04:17 PM
			  
			    
			  
			
			  
			Msg. 2 of 4
		I checked and it is a DVB-SR1 receiver. | 
	|  DTN_CurtisT
 -DTN Technical Support-
 Posts: 323
 Joined: Jun 14, 2007
 
   
 
 | 
			
			Posted: Jul 12, 2010 07:31 AM
			  
			    
			  
			
			  
			Msg. 3 of 4
		Hello themike, what you will want to do is contact our Weather Customer Service dept at 800/655-8111 and they will be able to help you further. 
 Thanks.
 
 Curtis Thompson
 curtis.thompson@dtn.com
 Trading Markets Customer Service
 1-800-397-7000 x3614
 | 
	|  themike
 -Interested User-
 Posts: 3
 Joined: Jul 10, 2010
 
 
 
 | 
			
			Posted: Jul 18, 2010 06:14 PM
			  
			    
			  
			
			  
			Msg. 4 of 4
		Thanks to everyone at DTN for helping with this issue. The fix was to reload the machine with a 32-bit edition of Window 7. Apparently this is a common problem with lots of older hardware devices that lack new drivers for a 64-bit OS. |