Getting The DLP-RFID1 Reader to work 0n Windows 7 build 7000(64-bit)
Well I was just sent a private message by a friend @MS who saw that I got the DLP RFID Reader/Writer to work with Vista 64 bit with a small hack. Well, the hack is not needed any more because the makers of the device driver FTDI have updated support for 64 bit. You can find the drivers here: http://www.ftdichip.com/FTDrivers.htm.
From this site I found the CDM 2.04.16.exe file that contains the updated version of the drivers.
Steps to install:
1. First plug in the DLP RFID Reader into the USB port.
2. The prompt will tell you that the driver can not be installed.
3. Next run the executable which installs the lastest drivers.
4. Open the Device Mgr, find the troubled DLP device and right-click and update its driver.
5. Choose to browse computer, and then select to install the driver from a list of installed drivers.
6. Select the FTDI as the manufacturer, then select the first option.
7. Unplug the device and plug it back in, Windows 7 should recognize it.
8. Test the device with the RFIDSample.exe application that can be found on the FTDI web site.
Hope this helps.
Friday, April 17, 2009
Wednesday, April 15, 2009
Getting SQL Dev/SQL Express DBs to talk to each other inside of VPC images
This is just a note to myself, and maybe someone else can use this tip as well...
Most of the MS MOC VPC images by default can't talk to each other, as in the case of the Sharepoint course 5060/5061 and 50064 etc.
You can make changes to the images to have them talk to each other.
1. Using VPC Console, change the network adapter to use the current Network card on the physical system.
2. Inside the VPC images configure the network card to use a dummy IP address such as 192.268.10.1, use the default Subnet Mask of 255.255.255.0 and set the DNS server address to itself such as 127.0.0.1
3. At this point verify that the Server VPC Images can browse and see each other using Windows explorer, such as if the first Server image is named "Server1", and the Second is named "Server2", then within the Win Explorer of "Server1" try to connecto to file://%20server2/ and within the "Server2" image try to connect to \\ server1 in their respective windows.
4. If all is good here, On the image that contains SQL 2005+, open the SQL Suraface Area configuration application, and select the Surface Area Configuration for Services and Connections -> Select the SQLExpress->Database Engine-> Remote Connections and select Local and Remote connections, choosing any of the available choices. (For example Using both TCP/IP and named pipes)
5. Next open Active Computers and Users/ or the Computer Management snapin, and add the account you plan to use to connect to SQL to a Windows/AD Group that you will add to the Sysadmin role in SQL/SQLExpress.
6. Next open up SQL/SQLExpress, goto the security->Role folder, and Add this Windows /AD Group to the SysAdmin sql role.
7. Next Open the Services control applet from the control panel, and restart the SQL/SQL Express service.
8. Lastly, Start the SQL Browsing service if it's not already started.
---Happy coding
This is just a note to myself, and maybe someone else can use this tip as well...
Most of the MS MOC VPC images by default can't talk to each other, as in the case of the Sharepoint course 5060/5061 and 50064 etc.
You can make changes to the images to have them talk to each other.
1. Using VPC Console, change the network adapter to use the current Network card on the physical system.
2. Inside the VPC images configure the network card to use a dummy IP address such as 192.268.10.1, use the default Subnet Mask of 255.255.255.0 and set the DNS server address to itself such as 127.0.0.1
3. At this point verify that the Server VPC Images can browse and see each other using Windows explorer, such as if the first Server image is named "Server1", and the Second is named "Server2", then within the Win Explorer of "Server1" try to connecto to file://%20server2/ and within the "Server2" image try to connect to \\ server1 in their respective windows.
4. If all is good here, On the image that contains SQL 2005+, open the SQL Suraface Area configuration application, and select the Surface Area Configuration for Services and Connections -> Select the SQLExpress->Database Engine-> Remote Connections and select Local and Remote connections, choosing any of the available choices. (For example Using both TCP/IP and named pipes)
5. Next open Active Computers and Users/ or the Computer Management snapin, and add the account you plan to use to connect to SQL to a Windows/AD Group that you will add to the Sysadmin role in SQL/SQLExpress.
6. Next open up SQL/SQLExpress, goto the security->Role folder, and Add this Windows /AD Group to the SysAdmin sql role.
7. Next Open the Services control applet from the control panel, and restart the SQL/SQL Express service.
8. Lastly, Start the SQL Browsing service if it's not already started.
---Happy coding
Subscribe to:
Posts (Atom)