|
| Archive |
| March, 2011 (2) |
| February, 2011 (2) |
| January, 2011 (2) |
| December, 2010 (1) |
| May, 2010 (1) |
| April, 2010 (4) |
| March, 2010 (2) |
| February, 2010 (8) |
| January, 2010 (2) |
| December, 2009 (3) |
| November, 2009 (2) |
| October, 2009 (4) |
| September, 2009 (4) |
| August, 2009 (1) |
| July, 2009 (9) |
| June, 2009 (8) |
| May, 2009 (6) |
| February, 2009 (1) |
| January, 2009 (1) |
| December, 2008 (1) |
| November, 2008 (1) |
| October, 2008 (1) |
| August, 2008 (3) |
| July, 2008 (6) |
|
|
|
|
Monday, April 26, 2010 |
|
|
Here is a great chart I found that clearly lays out which versions will support in-place upgrades on 7. All OS's including Vista and XP included.

|
|
|
|
|
Friday, April 09, 2010 |
|
|
I had a problem with a Windows XP PRO Remote Desktop host. No one could connect to the machine either locally or remotely. There was no error on the client - it would try to connect and then just go back to blank or return to the connect screen.
On the host, I found an error that RDPDD.dll failed to load in the event logs.
The problem seems to be with the video driver.
This registry key that increases the size of the session image space solved the problem for me:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
"SessionImageSize"=dword:00000020
Further research says that replacing/updating removing/reinstalling the video driver may help too. |
Friday, April 09, 2010 5:12:27 PM (Central Standard Time, UTC-06:00) | | Windows XP
|
|
|
|
Wednesday, April 07, 2010 |
|
|
You may receive the message in a Window titled "Setup Error" that says Error "Setup.rul 380" has occurred and Setup cannot continue.
The error “Setup.rul “380″” Is caused by not having .NET 2.0 or higher installed. This is because the Software that controls the card is trying to be installed with the driver also. Installing only the driver will work as well.
In order to fix this issue without installing .NET 2.0 or higher please follow these directions. Also remember what the folder name is associated with the Wireless driver you downloaded. It will be RXXXXX. In the case of a Vostro 1520 with Dell Wireless card 1397, the directory is R219313.
This is easily fixed by installing just the driver. Right click “My Computer” then click on “Manage” Then click on “Device Manager” Then right click on your wireless network card. You will then need to click on “Update Driver”. A box will pop up. Click on “No, not this time”. Now click “Next”. Now click on “Install from a list or specific location (Advanced)”. Now click on “Don’t search. I will choose the driver to install.” In the list select “Network Adapter” and click next. Now click on “Have Disk”. Now click on “Browse”. On the left side click on “My Computer”. Now go to “C:\Dell\Drivers\RXXXXX\” NOTE: You may see that it has a lot of folders. Select the folder that’s best for your install of Windows. Then when you do this you will be left with one file to select. Select that file and click ok.
The system will then only install that driver. You won’t get the Dell Wireless software installed with it, so you should use the Microsoft interface to configure your wireless networks. To enable the Dell Wireless software, install .NET 2.0 or higher and re-run the driver setup. |
|
|
|
|
Tuesday, April 06, 2010 |
|
|
If you forget the admin password for Symantec Endpoint Protection, You can reset the account and password back to the defaults by reviewing the reset_pass.pdf file (steps below) located at \Symantec Endpoint Protection Manager\Tools (usually under c:\program files)
To use Resetpass.bat:
1. Open Windows Explorer on the computer where you run Symantec Endpoint Protection Manager. 2. Change directory to the <Drive>:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tools folder. 3. Double-click the Resetpass.bat executable file. The password is reset to the default password. 4. Be sure to change the password immediately.
This will change the username and password to "admin" |
|
|
|
|
|
|