Live witSoft License

Yes, it's live

Manual Asus WL-330gE

Untuk yang mempunyai Asus Portable Wireless Access Point, berikut ini link manualnya

Asus WL-330gE user's manual in English

Prolific USB To Serial Driver Fix!

Windows 32 and 64-bit Operating Systems - Prolific PL-2303 Driver Fix (VID_067B&PID_2303)

For Windows XP, Windows 7, Windows 8, Windows 8.1 and Windows 10!

"This Device cannot start (Code 10)"

"No driver installed for this device"

"Device driver was not successfully installed"

The Internet is full of web pages discussing this problem, but no one really seems to understand what causes it. Even the companies selling these USB to Serial adapters appear to be either dumbfounded or have selective amnesia. After all, it's absolutely great for business. There are many "backyard" fixes out there, but none of them are done properly and if they work it's just a temporary "Band-Aid" to the problem. It will come back to haunt you.

What has happened is that there have been counterfeit "Prolific" chips coming from China. The counterfeit chips use the same Vendor ID (VID_067B) and Product ID (PID_2303) as the authentic Prolific chips. So, Prolific made changes to their newest drivers to render the adapters using counterfeit chips unusable. Unfortunately, it renders all earlier adapters inoperative and so you have to go out and buy new ones. Planned obsolescence? Getting a working driver installed by the average user is almost impossible.

If one of these Prolific 64-bit drivers gets installed to your computer then your legacy device will no longer work and will issue the generic "Code 10" error. 
Driver Versions:

3.3.5.122, 3.3.11.152, 3.3.17.203, 3.4.25.218, 3.4.31.231, 3.4.36.247
3.4.48.272, 3.4.62.293, 3.4.67.325, 3.4.67.333, 3.6.78.350, 3.6.81.357 

Or, you may get no error at all, but your device will not work. If your adapter was working prior to going to Windows Update, you may be able to "roll back" to the previous installed driver and all will be well once again. However, if you didn't have a previous driver installed that worked, you'll have to go through the process of removing any PL-2303 driver installation programs,the actual driver files, and the information (.INF) file BEFORE you are able to successfully install the correct driver. What aggravates the issue is that there are many "Prolific Driver Removal Tools" that do not work properly as well! And Windows 8, 8.1, and Window 10 are set by default to automatically update your drivers without your permission or even notifying you of the update. So, no matter how many times you remove the driver files and reboot, the next time you insert the USB-To-Serial adapter, Windows installs the newest non-working version again. Yes, it's frustrating as hell.

The only 64-bit driver I have ever found that works with all the "Prolific" adapters is Version 3.3.2.102. The below installer program will remove all of the incompatible drivers, make a change so that Windows can never update the driver without your okay, and install the Version 3.3.2.102 compatible drivers.

Windows 64-bit Fix for:
- All Windows 64-bit operating systems including Windows 10
.Prolific USB to Serial Adapter OR other device.
.Device using PL-2303 H, HX, HXA, HXD, X, XA, EA, RA, SA, TA, TD version chips
.Driver Version: 3.3.2.102
.Driver Date: 09/29/08
.Supported device ID and product strings: . VID_067B&PID_2303 for "Prolific USB-to-Serial Comm Port"

1. Download and Save the "PL2303_64bit_ Installer.exe" at the link below:

http://www.ifamilysoftware.com/Drivers/PL2303_64bit_Installer.exe

You can just Save it to your Desktop to make it easier. Norton's 360 won't like it, so to save all the grief of dealing with that beast you might want to disable your anti-virus before running the installer.

2. Unplug all USB-To-Serial adapters and Double click on the installer "PL2303_64bit_Installer.exe"

3. When it prompts you, plug in one (1) of your USB-To-Serial adapters and click "Continue".

4. Reboot your computer.

5. Unplug the adapter and plug back in again. That's it!

Trouble Shooting: You must follow ever step in the process precisely. If you still receive an error after running the PL-2303_64bit_Installer.exe and your device is plugged in, go to the Windows Device Manager. Scroll down to Ports (Com & LPT) and Double-Click on "Prolific USB-to-Serial Comm Port (COM#)". In the Properties Window, Click on "Driver". The "Driver Version" must say "3.3.2.102" dated 09/24/08. If not, then the correct driver is not installed. Unplug the USB-To-Serial adapter and run the "PL2303_64bit_Installer.exe" again, following the directions precisely until you get it right.

Removal: There is no "Uninstaller" for this file. The installer itself is just an executable ".EXE" file that can be deleted when you are done. Any additional files that it uses are temporary only and are stored in the "C:\Windows\Temp" folder.

Windows 32-bit Fix for:
- All Windows 32-bit operating systems from XP up
.Prolific USB to Serial Adapter .
.Device using PL-2303 H/HXA/HX/X version chips
.Driver Version: 2.0.2.8
.Driver Date: 11/20/07
.Supported device ID and product strings: . VID_067B&PID_2303 for "Prolific USB-to-Serial Comm Port"

1. Download and Save the "PL-2303_Driver_ Installer.exe" program at the link below:

http://www.ifamilysoftware.com/Drivers/PL-2303_Driver_Installer.exe
You can just Save it to your Desktop to make things easy.

2. Run the installer program. If it offers a choice to remove the driver, then select to remove the current "bad" driver. Then run the installer again to install the correct driver.

Trouble Shooting: If you still receive an error after running the PL-2303_Driver_Installer.exe and your device is plugged in, go to the Windows Device Manager. Scroll down to Ports (Com & LPT) and Double-Click on "Prolific USB-to-Serial Comm Port (COM#)". In the Properties Window, Click on "Driver". The "Driver Version" must say "2.0.2.8" dated 11/20/07. If not, then the correct driver is not installed. Unplug the USB-To-Serial adapter and run the "PL2303_Driver_Installer.exe" again, following the directions precisely until the correct driver appears in the Device Manager.

Removal: The Prolific 32-bit PL-2303_Driver_Installer is a "Program" file and therefore installed to your computer and must stay. If you want to delete it, use the Windows "Uninstall a Program" or "Add or Remove Program" feature, however this will also uninstall the driver itself.

Windows 32-bit Files Direct Install:
For XP, Vista, and Windows 7 users that cannot get the driver files installed using the PL-2303_Driver_Installer above, you can also try having Windows install the files directly. Download and run the file "PL2303Win32.exe" installer program from the link below:

http://www.ifamilysoftware.com/Drivers/PL-2303_Win32.exe

This will install the driver files in a directory on your hard drive named, "C:\PL2303Win32". Plug in your Prolific USB to Serial adapter, go into Device Manger, and then Scroll down to Ports (Com & LPT) and Double-Click on "Prolific USB-to-Serial Comm Port (COM#)", or in some cases, "Other Device". Click on "Update Driver' and then choose to locate the driver on your computer. Click on "Browse" and direct Windows to the folder "C:\PL2303Win32" where the files are located and click OK. Windows will copy the files directly into the Driver Store for the system to use. Next, unplug your Prolific adapter and plug it in again and the driver will be installed from the Driver Store to Windows/System32/Drivers and your device should be working properly.

This article is from www.ifamilysoftware.com

Installing Visual Basic/Studio 6 on Windows 10

As I’ve worked my way through the various oddities of Windows 10, I’ve found that most applications work great. For the most part, anything that worked on Windows 7 works on Windows 10. Visual Basic 6 (VB6) has been one of the few exceptions, so far.

Why install Visual Basic 6? It’s a long-dead program, after all. Well, like many companies out there, mine has a few proprietary programs that were written, long ago, in VB6. The apps work great, so it just hasn’t made sense to spend the time and/or money it would take to upgrade them to VB.Net. Yet, we still need to be able to make minor changes to the programs now and then.

We could keep an old XP machine around just for VB6, or set up a virtual instance of XP, or go for either of those options with Windows 7 (VB6 installed on Win7, though not perfectly). Instead of going those routes, though, I decided to look into getting VB6 properly installed on Windows 10. These notes should work for the Pro and Enterprise editions of both Visual Basic 6 and Visual Studio 6.

Note that this tutorial is really geared toward getting Visual Basic 6 up and running. I do not know whether any of the other Visual Studio applications will work after the steps below have been followed.

Also note that this process will not allow you to install the Data Access components. They just don’t work with Windows 10.

Remove Any Remnants of VB6/VS6

If you’re like me, you probably tried to install Visual Basic 6 on your computer the old fashioned way. When the install failed, you were then left with bits and pieces of VB laying around, and no uninstaller. Luckily, Microsoft wrote up an article about removing Visual Studio manually (How To Manually Uninstall Visual Studio with MSDN Library). I do not believe searching your hard drive for some of the files, as they mention, is necessary. Here are the most important steps to follow:

• Delete the installation folders for any Visual Studio products. Note that the following are the default locations; the actual locations may be different on your system if you did a custom installation or if you are on a 64-Bit computer:
  • \Program Files\Microsoft Visual Studio
  • \Program Files\Common Files\Microsoft Shared\MSDesigners98
  • \Program Files\Common Files\Microsoft Shared\MSDN
  • \Program Files\Common Files\Microsoft Shared\VS98
  • \Program Files\Common Files\Microsoft Shared\Wizards98

• Delete the installation folders for any MSDN Libraries (the previous step may have deleted these if they were installed to the default location). The default folders are as follows:
  • Program Files\Microsoft Visual Studio\MSDN98 (for the MSDN Library for Visual Studio 6.0)
  • Program Files\Microsoft Visual Studio\MSDN (for the MSDN Quarterly Library releases)

• Use Regedit.exe to delete the following Registry keys if they exist:
  • HKEY_LOCAL_MACHINE\Software\Microsoft\DevStudio
  • HKEY_LOCAL_MACHINE\Software\Microsoft\MSVSDG
  • HKEY_LOCAL_MACHINE\Software\Microsoft\HTML Help Collections
  • HKEY_LOCAL_MACHINE\Software\Microsoft\Visual Basic\6.0
  • HKEY_LOCAL_MACHINE\Software\Microsoft\Visual Component Manager
  • HKEY_LOCAL_MACHINE\Software\Microsoft\Visual Modeler
  • HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\6.0
  • HKEY_CURRENT_USER\Software\Microsoft\DevStudio
  • HKEY_CURRENT_USER\Software\Microsoft\MSVSDG
  • HKEY_CURRENT_USER\Software\Microsoft\Visual Basic\6.0
  • HKEY_CURRENT_USER\Software\Microsoft\Visual Modeler
  • HKEY_CURRENT_USER\Software\Microsoft\VisualFoxPro
  • HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\6.0

• If you’re on a 64-Bit system, check here, as well:
  • HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\DevStudio
  • HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\MSVSDG
  • HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\HTML Help Collections
  • HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Visual Basic\6.0
  • HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Visual Component Manager
  • HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Visual Modeler
  • HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\VisualStudio\6.0

• Use Regedit.exe to delete any instance of the key for Visual Studio or MSDN Library under the following keys. Since you don’t have an uninstaller, you probably won’t find anything here. It’s worth looking through the keys, anyway, to see if you find any mentions of Visual Studio or MSDN. WARNING: Do not delete the “Uninstall” key; only delete MSDN or Visual Studio keys listed within it.
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
  • 64-Bit systems only: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

Prepare Your Files

Now, we need to get all of our files in place. The tool we’re going to use for the installation can actually read off the CDs, but I find it much quicker to have already copied the necessary files to my hard drive. In my case, I setup everything in C:\Visual Studio 6\.

• First, copy the contents of all Visual Basic/Studio 6 and MSDN CDs to the folder you’ve chosen.
• Next, download and extract the Visual Studio SP6 patch (https://www.microsoft.com/en-us/download/details.aspx?id=9183). Place the extracted contents in a folder named VS6SP6.
• You should end up with a set of directories that look like those shown below. The names aren’t important, as long as you know what’s what.

We’re going to use a handy tool put together by Giorgio Brausi to complete our installation. It takes care of some of the trickier parts of getting Visual Basic/Studio 6 installed on a Windows 10 computer.

• Download Giorgio’s installation program from his website, nuke.vbcorner.net (http://nuke.vbcorner.net/Articles/VB60/VisualStudio6Installer/tabid/93/language/en-US/Default.aspx or https://drive.google.com/open?id=0B7xuK3ceEW-1QXh3SjRJQ1ZMajQ).
• The program does not need to be installed. Simply extract the contents of the zip file and run vs6installer.exe.
• The first thing we need to do is setup the program’s working folder. This is where the installer program will copy it’s working fileset to. I suggest using a folder you know the program will have permission to access. Something in your Documents folder should work.
• Click the “Set Root folder” button.
  
• Browse to where you want to create the root folder, then click Make New Folder. Using the tool to make the folder will ensure that it has the necessary permissions. Click “Yes” to confirm that it is the correct location.
• If you want to install the various graphic files included with VS6, then make sure that option is checked.
• Make sure the “Disable Data Access” option is chosen. It should already be selected, by default, on Windows 10 systems.
• Select the edition you will be installing. In my case, I chose Visual Studio 6 Professional Edition. You should choose whatever matches the CDs you are using for the installation. Your options should look similar to this:
  
• Click the “Step 1” button. The program will now have you select the source location for Visual Basic/Studio’s files. The files can be on CDs, or on your hard drive (as I previously recommended). Select the set of files referenced at the top of the selection window, confirm that the copy procedure is correct, then wait as the necessary files are copied to the new root location.
  
  
• Click “Step 2” and select the MSDN files. Technically, you don’t need to install MSDN, but it doesn’t hurt. You will need to select both CDs for this step. After CD1 has finished copying, you will be prompted to select CD2.
  
• On to “Step 3”. This will prepare the Service Pack 6 files. Browse to and select the files you previously extracted to the VS6SP6 directory.
  
• You may run into an issue here if you are installing the Professional Edition of VB6/VS6. The Service Pack 6 files that are still available on the Net are actually for the Enterprise Edition. I have, so far, been unable to source a Pro version of SP6. If you get an error about missing files (see below), then simply move on with the installation. We’ll manually install SP6, later.
  

Install Visual Basic/Studio

Now that our files are in place, it’s time to begin installing the program.

• Click the first Install button.
  
• Click “Yes” to confirm you wish to continue with the installation.
• The standard installer will now launch. Make your way through it, entering your Serial Number as necessary.
• Make sure to choose the standard Install option, NOT the Server Applications option.
• Keep clicking Next, Continue, OK, etc., until you get to this screen. Click the Custom button.
  
• The installer tool will have already made the appropriate selections based upon what you chose before launching the installer, so there should be no need to make any changes here. I believe you can install the options besides Visual Basic 6, but they were unnecessary for me. Some of the items under “Data Access” are incompatible with Windows 10. They should already be disabled if you left the “Disable Data Access” option checked in the installer tool.
• If your version of Visual Studio/Basic has a SourceSafe option, then it is probably wise to uncheck that option.
• Here’s how my installation options looked:
  
• Click Continue and the program will install.
• Click OK when you get the Success message.
• You may need to Restart your system at this point. If so, wait for the restart to finish, then pick up where you left off.
• The MSDN installer will now launch. Make sure to UNCHECK the “Install MSDN” option, then click Next.
  
• Click “Yes” to the message warning you about not installing MSDN, click Next to skip any additional installers, then UNCHECK “Register Now” and click Finish.
• If you were to check Programs and Features now, you would see that you now have a proper Visual Basic/Studio 6 uninstaller.

Install the MSDN Library

Time to install the MSDN Library. This step is optional, but I recommend it as Visual Basic 6 Help files are only going to get harder to find on the Net as time goes by.

• Click the second Install button.
  
• Click “Yes” to confirm you want to install MSDN, then make your way through the various screens.
• When you get to the screen below, go ahead and click the “Full” option. You could click the “Custom” button and pick and choose what files to install, but considering the size of modern HDDs, it really isn’t necessary.
  
• Click OK when installation has finished, and make your way back to the installer tool.

Install Service Pack 6

There are two ways to install Service Pack 6. If you have the proper service pack files for your installation, then you will be able to use the installer tool to launch the installation. If not, then you’ll need to launch the installer manually.

Note that Service Pack 6 only contains updates for Visual Studio, Visual C++, and Visual Basic, and Visual SourceSafe. If you installed any other programs (FoxPro or InterDev), then you should first install Service Pack 5. I find it hard to justify installing those programs, so won’t go over that scenario here.

• If you were able to find the right version of SP6 for your installation, then you can click the third Install button.
  
• Click “Yes” to confirm you want to install SP6.
• If you were unable to find the correct version of SP6, then find the folder you previously extracted the SP6 files to (during this step), right click on the setupsp6.exe file, and choose “Run as administrator”.
• From here on, the installation of SP6 will be the same for both scenarios.
• Click “Continue”, then click “I Agree”.
• If you get an option to click a “Complete” button, then do so.
• Click “OK” once installation has finished.

A Few More Steps

Just a few more steps until we’re done. These steps will take care of a few errors/annoyances you may encounter.

• Go to the Options tab in the Visual Studio 6 Installer program and click “Create Desktop shortcut”.
  
• Run the newly created shortcut from your Desktop.
• If you get an “Automation error”, then close VB6, return to the installer tool, and click the “Run As Administrator” option.
  
• Relaunch VB6, and the error should be gone.
• You can now return to the installer tool and click the “Run As Administrator” option again to turn off that setting. It is not needed after the necessary registrations have been completed.
• We have just one more setting to change. VB6, when run on Windows 10, will experience a delay whenever you draw, move, or resize objects on a Form in the VB IDE. To correct this issue, click the “Set Vista SP2 compatible” button.
  
• If the “Set Vista SP2 compatible” button does not work, then you may need to set that option manually. To do so, navigate to where VB6 is installed (most likely C:\Program Files (x86)\Microsoft Visual Studio\VB98\).
• Right click on VB6.exe and choose “Properties”.
• Go to the Compatibility tab, check the “Run this program in compatibility mode for” option, and choose “Windows Vista (Service Pack 2)”.
  
• Click OK, then try running the program again. You should now find that controls can be manipulated without issue.

And you’re done! Visual Basic 6 should now run just as well as it ever did. Now then, time to get back to work on converting those VB6 apps to VB.Net 

This article is from blog.danbrust.net

How to Disable Driver Signature Enforcement in Windows 10/8/7 64-Bit

In 64-bit operating systems starting with Windows Vista, Windows will load a kernel-mode driver only if the driver is signed. It was designed to prevent unsigned device drivers (or kernel modules in general) from being loaded and executed. After installing an unsigned device driver, it will always result in a blue screen of death during the startup process.

The problem is that many devices ship with unsigned drivers. Today, we’ll show you 2 methods to disable Driver Signature Enforcement in Windows 10, 8, 7 (64-bit) so you can then install / load unsigned drivers without problems.

Option 1: Disable Driver Signature Enforcement Completely

1. Open a Command Prompt with admin privileges. In Windows 10 or 8, just press the Windows key + X and then select “Command Prompt (Admin)”.
2. Type in the following command and press Enter.
   bcdedit /set testsigning on
   You should receive “The operation completed successfully” message.
3. Close the Command Prompt and restart your computer. From now on, you will be able to install or run any unsigned driver without problems.
   If you need to enable the Driver Signature Enforcement again, run this command instead:
   bcdedit /set testsigning off

Option 2: Disable Driver Signature Enforcement Once

If you don’t want to use the method above to permanently disable Driver Signature Enforcement, here is a solution for you to temporary turn off Driver Signature Enforcement to install unsigned driver:

1. Press the Windows key + R to bring up the Run box. Type shutdown /r /o and hit Enter.
2. Windows informs you that you are about to be signed off. Click Close.
3. Once your Computer has rebooted you will need to choose the Troubleshoot option.
   
4. Then head into Advanced options.
   
5. In the Advanced Options window, choose Startup Settings.
   
6. Click the Restart button on the Startup Settings screen to reboot your computer again.
   
7. After restart in Startup Settings windows, press the F7 key on your keyboard to select “Disable driver signature enforcement“.
   
8. Your PC will then reboot. Proceed to install your unsigned drivers. During the installation procedure, Windows will inform you that can’t verify the publisher of this driver software. Just ignore the warning message and choose “Install this driver software anyway” to complete the installation.

Keep in mind that after the next restart, Driver Signature Enforcement will be automatically enabled again to prevent new drivers from being installed, but Windows will keep using any unsigned drivers you’ve already installed.

This article is from www.top-password.com