Windows 7, Windows Server 2008 R2 and Exchange Server 2010 | Microsoft

Default password for all TMNet Streamyx supported modem.

1. ZTE modem
* IP Address: 192.168.1.1
* Username: ADSL
Password: expert03
* Username: ZXDSL
Password: ZXDSL
* Username: admin
Password: telekomst
2. KASDA modem:
* IP Address: 192.168.1.1
* Username: admin
Password: telekomst
3. ArtNet modem:
* IP Address: 192.168.1.1
* Username: admin
Password: telekomst
* Username: admin
Password: admin
* Username: admin
Password: password
4. Triz modem:
* IP Address: 192.168.1.1
* Username: admin
Password: aaaaaaaa
5. Aztech modem:
* IP Address: 10.0.0.2 OR 192.168.1.1
* Username: admin
Password: blank
* Username: admin
Password: password
* Username: admin
Password: admin
6. Billion modem:
* IP Address: 192.168.1.254
* Username: admin
Password: password
7. Huawei modem:
* IP Address: 192.168.1.1
* Username: admin
Password: admin
8. Hyundai HSE-220 Modem:
* IP Address: 192.168.1.1
* Username: ADSL
Password: ADSL
* Username: admin
Password: ADSL
* Username: root
Password: root
9. Riger DB102:
* IP Address: 192.168.1.1
* Username: tmadmin
Password: tmadmin
10. TP-LINK MODEM / ADSL2 / ROUTER:
* IP Address: 192.168.1.1
* Username: admin
Password: admin

Create a shared variable for passing data from subreport to main report

Since CR not allowed to sum (formula), e,g, sum({@mainformula), I
calcualte the grand total from subreport. detailed steps are:

1. In subreport, create formula called subformula, the shared valiable = grand total

WhilePrintingRecords;
Shared CurrencyVar myTotal :=Sum ({Command.SUM(AB.FEEAMOUNT)})

2. In main report, created a formula called mainformula

WhilePrintingRecords;
Shared CurrencyVar myTotal;
myTotal

3. Then put this mainformula on the main report underneath of subreport. Here what you want for the result.

Removable USB/thumb drives use the Autorun feature to load files when the drives are plugged into the USB port. Malware exploits the Autorun feature to spread from thumb drive to PC. Disable the autorun feature to prevent malware from spreading.
Difficulty: Easy
Time Required: 2 minutes
Here's How:

1. The easiest and most effective means to truly disable autorun can be done via this simple autorun registry hack:

REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\Autorun.inf]
@="@SYS:DoesNotExist"
2.

To use this method, Open Notepad and copy/paste the following into a text file:

REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\Autorun.inf]
@="@SYS:DoesNotExist"

Save the file as something.reg. (You have to be sure to change the "Save File as Type" to "All Files" before saving, or Windows will try to save it as a .txt even if you typed in .reg.
3.

Locate the file you just saved and double-click the file to run it. You will receive a prompt asking if you want to add the data to the registry. Click yes to allow the modification.
4.

The above method nulls any request for autorun.inf and works on XP Home or Pro, as well as Windows Vista. Credit for this tip goes to Nick Brown.

If you opt to disable autorun using any other method, you will first need to install an autorun patch from Microsoft that allegedly resolves issues that cause autorun to run even after it's been disabled (using methods other than the above recommended method).
5. XP Pro users who have installed the appropriate Microsoft patch for your system and wish to disable autorun using a method other than described above, follow steps 3 through 8 only. XP Home users begin at step 9. Vista users, see How to Disable Autorun in Windows Vista.
6. Windows XP Pro users: Click Start and then click Run. Type gpedit.msc and click OK. The Group Policy window will open. In the left pane, double-click Administrative Templates
7. In the right pane, double-click System, scroll down the list and double-click Turn Off Autoplay
8. In the Turn Off Autoplay Properties window, select Enabled. From the dropdown next to Turn Off Autoplay on, select All drives and then click OK. Exit Group Policy by selecting File, then choosing Exit from the menu.
9. XP Home users will need to make the changes by editing the registry directly. To begin, click Start and then click Run
10. Type regedit and click OK. The Registry Editor window will open.
11. In the left pane, navigate to:
HKEY_CURRENT_USER
Software
Microsoft
Windows
CurrentVersion
Policies
Explorer.
(Note: For help navigating the registry, see the Windows Basics System Registry tutorial).
12. With Explorer highlighted, in the right-pane right click the value NoDriveTypeAutoRun and select Modify from the drop down menu. The base value will be set to Hexadecimal. If not, select Hexadecimal.
13. Type 95 and click OK.
Note that this will stop Autorun on removable/USB drives, but still allow it on CD ROM drives. If you want to disable autorun on both, substitute b5 for the 95. (Thanks to Ian L. of Manitoba for the tip).
14. Exit Registry Editor by selecting File, then choosing Exit from the menu.
15. You will now need to reboot your computer for the changes to take effect.

When you having this kind of error message prompt out when you are using ado components. Means this is cause by the field lenght was not compatible, please check you form input lenght and the database table field lenght. Please make sure it is same.

You may have faced the issue of losing the SQL Server SA password. Perhaps you followed the security best-practice of removing the builtin\Administrators from the sysadmin server role, and no one you can find is in the sysadmin role. At this point you may think that your only options are to reinstall SQL Server and attach the databases, or to directly access the master database files, which may potentially damage the data.

SQL Server 2005 provides a better disaster recovery option for this scenario that is non-intrusive for master DB and that will help you preserve any objects and data stored in master DB (such as logins, certificates, Service Master Key, etc.) intact. Members of the Windows Administrators group now have access to SQL Server when SQL Server is in started in single-user mode, also known as “maintenance mode “.

Using the single-user mode, SQL Server 2005 prevents a Windows Administrator to abuse this privilege to act on behalf of the sysadmin without being noticed. This allows Windows Administrator accounts to perform certain maintenance tasks, such as installing patches.

In order to start SQL Server in single-user mode, you can add the parameter “-m” at the command line. You can also use the SQL Server Configuration Manager tool, which provides proper controls for the file access and other privileges. To use the Configuration Manager tool to recover your system, use the following steps:

1. Open the Configuration Manager tool from the "SQL Server 2005| Configuration" menu
2. Stop the SQL Server Instance you need to recover
3. Navigate to the “Advanced” tab, and in the Properties text box add “;–m” to the end of the list in the “Startup parameters” option
4. Click the “OK” button and restart the SQL Server Instance

NOTE: make sure there is no space between “;” and “-m”, the registry parameter parser is sensitive to such typos. You should see an entry in the SQL Server ERRORLOG file that says “SQL Server started in single-user mode.”

5. After the SQL Server Instance starts in single-user mode, the Windows Administrator account is able to connect to SQL Server using the sqlcmd utility using Windows authentication. You can use Transact-SQL commands such as "sp_addsrvrolemember" to add an existing login (or a newly created one) to the sysadmin server role.

The following example adds the account "Buck" in the "CONTOSO" domain to the SQL Server "sysadmin" role:

EXEC sp_addsrvrolemember 'CONTOSO\Buck', 'sysadmin';

GO

6. Once the sysadmin access has been recovered, remove the “;-m” from the startup parameters using the Configuration Manager and restart the SQL Server Instance

Important Security Notes:

This process should only be used for disaster recovery when no other method to access the system with a privileged (i.e. sysadmin or equivalent) is available.

This process allows a Windows Administrator account to override their privileges within SQL Server. It requires explicit and intrusive actions that can be monitored and detected, including:

· Stop SQL Server and restart it in single use mode

· Connecting to SQL Server using Windows credentials


Special thanks to Buck Woody (http://blogs.msdn.com/buckwoody/) for his help in writing this article.

The VersionInfo library basically just wraps the Win32 GetFileVersionInfo (and related) API functions. The library makes it very easy to read values from the Version Info resource of Windows executables and DLLs.
Features

* Reads all integer version info values:
File version, product version, File flags, OS, file type, file sub-type and file date.
* Reads any named version info string value such as:
Product Name, Product Version, Company, Copyright, etc.
* Supports languages, character sets and translations.
* Optionally extends the TApplication class with a version info property.

The TApplicationVersion class

The TApplicationVersion class contains the core functionality of the library. The following is the public interface of the class:

TApplicationVersion = class
public
constructor Create(const Filename: string);
destructor Destroy; override;
class function VersionToString(Version: int64): string;
class function StringToVersion(const Value: string): int64;
function GetString(const Key: string; LanguageID: integer; CharsetID: integer): string; overload;
function GetString(const Key, TranslationID: string): string; overload;
function GetString(const Key: string; Index: integer = 0): string; overload;
property Valid: boolean;
property Strings[const Key: string]: string; default;
property FileVersion: int64;
property ProductVersion: int64;
property FileFlags: DWORD;
property OS: DWORD;
property FileType: DWORD;
property FileSubType: DWORD;
property FileDate: int64;
property LanguageID[Index: integer]: WORD;
property CharsetID[Index: integer]: WORD;
property LanguageNames[Index: integer]: string;
property TranslationCount: integer;
end;

The TApplicationVersionHelper class

As a bonus there’s also a class helper that extends TApplication with a version info property:

TApplicationVersionHelper = class helper for TApplication
public
property Version: TApplicationVersion;
end;

To enable the class helper you just include the ApplicationVersionHelper unit in your uses clause.
Examples
Example 1

Read the version number from a file and display it in a message box

uses
VersionInfo;
...
const
Filename = 'foobar.exe';
var
FVersionInfo: TVersionInfo;
Version: string;
begin
FVersionInfo := TVersionInfo.Create(Filename);
try
Version := TVersionInfo.VersionToString(FVersionInfo.FileVersion);
finally
FVersionInfo.Free;
end;
ShowMessage(Format('The file %s has version %s', [Filename, Version]));
end;

Example 2

Set the application title to the description value specified in the version resource

uses
Forms,
VersionInfo,
ApplicationVersionHelper; // Enable the class helper
...
begin
Application.Title := Application.Version['FileDescription'];
end;

-------------------------------------------------------------------------------------

Source Code Sample --> Download