Category: tehnice

To boot past Windows 8’s Start screen and go directly to Windows 8 desktop, you need to make a simple registry tweak. Do the following:
While in Windows 8 (desktop or Start screen, it doesn’t matter), open regedit. If you don’t know how to run regedit, read dotTech’s How to run Register Editor in Windows 8 guide.
When you have regedit open, navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon:

At the Winlogon registry folder, look for the registry entry named Shell, right-click it, and hit modify:

Once you right-click Shell and hit modify, a dialog box will pop open. In that box, there will be a Value data field which will say explorer.exe. Change explorer.exe to “explorer.exe /select,explorer.exe” (without the quotes) and hit OK:

Close Registry Editor.
Done! Restart your computer (click here to learn how to restart Windows 8, if you don’t know how) and upon boot you should see Start screen appear for a split second after which you are taken to Windows 8 desktop automatically:

 

 

 

 

v1:

If you are using win xp pro and outlook 2003 and can’t open Tif files in outlook.

Here is what you can do:

This problem known by Microsoft

In safe mode go to:
C:\Documents and Settings\username\Local Settings\Temporary internet Files\olk xxx

then delete this library contents.

if you cant see this library – open the hidden files and folder in the folder option

Now restart the computer to normal mode, open the outlook
and open the tif files

 

v2:

When opening an attachment directly from within Outlook you could get an error message saying that it can’t create the file and to that you need check the permissions on the folder you want to save it in. In most cases the permissions on the folder isn’t the issue but the fact that the folder is “full”. When you open an attachment directly from within Outlook it will first save a copy to a subfolder of the Temporary Internet Files folder. Cleaning out the folder will solve the issue.
Outlook Secure Temp folder

Unfortunately this is easier said than done. The subfolder name Outlook creates (on installation of Outlook) in the Temporary Internet Files folder is quite random. In Outlook 2003 and previous, the name starts with OLK and is followed by up to 4 random numbers or letters. In Outlook 2007 and Outlook 2010, this folder is called Content.Outlook and then has a subfolder which is named with with 8 random numbers and letters. In addition, by default, you cannot simply browse to the folder to clean it out. Getting to the Temporary Outlook Folder can still be accomplished in 2 easy steps though.

Step 1: Locate the folder
The folder location is stored in the registry in the following key;Outlook 97 HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\Outlook\Security
Outlook 98 HKEY_CURRENT_USER\Software\Microsoft\Office\8.5\Outlook\Security
Outlook 2000 HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Outlook\Security
Outlook 2002/XP HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security
Outlook 2003 HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security
Outlook 2007 HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Security
Outlook 2010 HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Security

Step 2: Get to the folder
Open the OutlookSecureTempFolder registry key from the location provided in Step 1.
Copy the path from the key.
Open Explorer
Paste the address in the Address Bar and press Enter

 

 

If you have found this page, it is likely that you encountered the following error when you tried to restore a differential backup using Microsoft SQL Server 2005. Restore failed for Server ”. (Microsoft.SqlServer.Smo) Additional Information: System.Data.SqlClient.SqlError: The log or differential backup cannot be restored because no files are ready to rollforward. (Microsoft.SqlServer.Smo) What this error is telling you is that there is no database that was left in non-operational mode, and thus has not been cleaned up such that uncommitted transactions have not been rolled back. The easy way to reproduce this error is to backup your database using full recover model, and do full and differential backups. Once you have your full and differential backup files you, if you want to restore your database all you have to do is restore the full backup first, and then one of the differential files (differential backups have all the changes since the last full backup) that brings you up to the point you want to restore to. You will get the above error when you try to restore the differential backup (after you just restored the full backup). Unfortunately, you forgot one critical detail (just like I did at first). You MUST restore all but the last (in this case the full backup) with NORECOVERY option. In the Microsoft SQL Server Management Studio there are three options on the Option “page” when you restore a database. Option 1 (the default): Leave the database ready to use by rolling back uncommitted transactions. Additional transaction logs cannot be restored.(RESTORE WITH RECOVERY) Option 2: Leave the database non-operational, and do not roll back uncommitted transactions. Additional transaction logs can be restored.(RESTORE WITH NORECOVERY) To properly restore a database that is backup up using full recovery mode with full and differential backups, here are the steps you need to follow to not get the above error. Restore Full backup

1. Open the Restore Database window in Microsoft SQL Server Management Studio
2. Ensure the To database field is filled in with the name you want.
3. Choose From device as the Source for restore.
4. Choose the full backup file you want to restore. In most cases this is the most recent full backup file.
5. Click the Options page on the left navigation.
6. Choose Leave the database non-operational, and do not roll back uncommitted transactions. Additional transaction logs can be restored.(RESTORE WITH NORECOVERY). This is the most important step!!!

Restore Differential backup

1. Open the Restore Database window in Microsoft SQL Server Management Studio
2. Ensure the To database field is filled in with the name you want. The same that you specified in step 2 for the Restore Full backup
3. Choose From device as the Source for restore.
4. Choose the differential backup file you want to restore. In most cases this is the most recent differential backup file.
5. Click the Options page on the left navigation.
6. Choose the default: Leave the database ready to use by rolling back uncommitted transactions. Additional transaction logs cannot be restored.(RESTORE WITH RECOVERY) Make sure to choose this if you want to use your database after the restore.

That is it, no more error. If you are lucky 🙂

CAUSE

This issue may occur if the TCP/IP protocol has become unbound from the dial-up adapter, or if a conflict is created when a second WAN Miniport IP device driver loads.

Back to the top Back to the top

RESOLUTION

To resolve this issue, uninstall the TCP/IP protocol, remove the second WAN Miniport IP device, and then reinstall the TCP/IP protocol. To do so, follow these steps:

1. Uninstall the TCP/IP protocol. To do so:

a. In Control Panel, double-click Network and Dial-up Connections, right-click Local Area Connection, and then click Properties.

b. Under Components checked are used by this connection, click Internet Protocol (TCP/IP), and then click Uninstall.

c. Follow the on-screen instructions to uninstall TCP/IP.

d. Restart the computer when prompted, but click No if you are prompted to allow Windows to enable a protocol.

2. Right-click My Computer, and then click Properties.

3. Click the Hardware tab, and then click Device Manager.

4. On the View menu, click Show hidden devices.

5. Under Network adapters, there should be no WAN Miniport IP devices. If a WAN Miniport IP device is listed, continue to the following step. If no WAN Miniport IP device is listed, go directly to step 16.

6. Click Start, click Run, type regedit in the Open box, and then click OK.

 

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

7. Locate the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}

8. On the Registry menu, click Export Registry File, type backup-key in the File name box, and then click Save.

 

Note You can restore the changes that you make to this registry key. To do so, double-click the backup-key.reg file that you saved.

9. Click each of the registry subkeys under this key, and then view the Data column of the DriverDesc value to determine which of the subkeys corresponds to WAN Miniport (IP). For example, the 0005 subkey.

10. Right-click the subkey whose DriverDesc value data is WAN Miniport (IP) (for example, right-click 0005), and then click Delete. Click Yes to confirm that you want to delete the key.

11. Quit Registry Editor.

12. Right-click My Computer, and then click Properties.

13. Click the Hardware tab, and then click Device Manager.

14. On the View menu, click Show hidden devices.

15. Under Network adapters, right-click WAN Miniport (IP) and then click Uninstall. Click OK to confirm that you want to remove this device.

16. Reinstall the TCP/IP protocol. To do so:

a. In Control Panel, double-click Network and Dial-up Connections, right-click Local Area Connection, and then click Properties.

b. Click Install.

c. In the Select Network Component Type dialog box, click Protocol, and then click Add.

d. Under Network Protocol, click Internet Protocol (TCP/IP), and then click OK.

e. When the protocol is installed, click Close.

17. Reset the modem by turning the power off and then on, or for an internal modem, restart the computer.

18. Test your Internet connectivity.

Turn off any firewalls for debugging. If the firewall is the problem, you’ll have to configure it to allow access to “trusted zone” addresses. Note that some firewalls must be completely uninstalled to stop them from affecting your networking.

PING each computer by IP address, and if successful, PING by name. You can obtain the IP address of a computer by opening a command prompt (DOS window) and typing IPCONFIG. This should work for any Windows version. A failure here needs to be corrected before you go any farther.

Check your Services are Started on all PCs: Workstation, DHCP Client, DNS Client, Server, TCP/IP Netbios helper, Computer Browser.

All computers should be in the same workgroup for computer browsing to function properly. File & Print Sharing has to be enabled on any computer you wish to share files or printers from. You also need to actually share the resource in question from My Computer, right click on the drive/printer/folder, and select sharing.

If you encounter difficulties accessing computers that are visible in Network Neighborhood, make sure the computer being accessed has an account with the same name/password as the system connecting to it uses to login.

While the default NetBIOS setting is correct for normal network configurations, it’s possible for it to be altered, and it costs nothing to make sure it’s correct. NETBIOS over TCP/IP must be enabled for normal network browsing.

Please note to use these licenses only for educational and testing use.

1. SERVER Start > Control Panel > Add or Remove Programs > Add or Remove Windows Components’. Add “Terminal Server” & Terminal Server Licensing” Default licensing mode is per device as we will need to for actiivation.

2. SERVER Start Terminal Server Licensing (Start > Control Panel > Administrative Tools > Services >Terminal Server Licensing) if it is not started

3. SERVER Go to the Terminal Server Licensing, Right-click on Terminal Server > Properties > Installation Method:

Select Installation Method “Web Browser”

4. SERVER Go to next tab “Required Information”. Fill all 4 fields with some none important information. Write somewhere TS ID on the bottom of that window

5. SERVER Right-click on Terminal Server and select Activate Server. Terminal Server License Server Activation Wizard will start. Read > press next

6. SERVER Select activation method “Web Browser” press next

7. WEB BROWSER Go to https://activate.microsoft.com/ to get license server ID

8. WEB BROWSER Select “Activate a license server” press next

9. WEB BROWSER Fill out required fields with some information that makes sense. Choose country USA. Use Product ID use from step 6, press next on the bottom

10.WEB BROWSER Press next one more time on the bottom

11.WEB BROWSER If you did every thing right then you gonna get license server ID key (enter this information in your terminal server activation window), but do not close window we will need this for client access licenses (CALs). If everything is OK you will now have Terminal Server License Server Activated.

12.WEB BROWSER Next in the “Do you wish to install license tokens at this time?” select “Yes”

13.WEB BROWSER Fill out the required fields on the Microsoft web page . License Server ID get from Terminal Server CAL Installation Wizard. Important is to set License Program to “Other agreement“.

14.WEB BROWSER Choose Product Type Windows 2003 Terminal server Per Device CAL, Fill quantity (I put around 100) and Agreement Number 6565792

15.WEB BROWSER Press next once more on the bottom

16.WEB BROWSER you are gonna get your license key pack ID what you need to insert to Terminal Server CAL Installation Wizard > close window do not press finish, but first write down license key pack ID

17.SERVER Insert license key pack ID into your server and finish wizard

 

preluat de pe http://www.harmhoekstra.nl/kb/entry/30/ 

Here you find information about writing inner joins with the comma operator. It’s the most basic way to combine (join) two tables. There is an alternative syntax that can be used, because in MySQL you can write inner joins in two different ways. Another popular way is it to use the INNER JOIN command or synonymous keywords like CROSS JOIN and JOIN. Please make sure to read our dedicated documentation for more information when you understand the comma operator syntax.

The following examples are equivalent to the INNER JOIN examples, to make it easy to compare them. The first example builds the Cartesian product of two tables: Every row in the left table is combined with every row in the right table. In ANSI SQL, this is called a cross join. MySQL however doesn’t distinguish between inner joins and cross joins.

— inner join without a condition: a cross join
SELECT *
FROM <firstTable> a, <anotherTable> b

— inner join with WHERE-clause
SELECT *
FROM <firstTable> a, <anotherTable> b
WHERE a.<columnName> = b.<columnName>

When you write inner joins using the comma operator, there is only one way to specify the join condition: with a WHERE-clause.

Basics

An inner join combines all matching rows from two related tables. Two rows match if they are related, for example because they share a common column. When you write an inner join with the comma operator, the join condition which reflects a relationship between tables is added as a WHERE clause. You can use inner joins to SELECT, UPDATE or DELETE data that is stored within MySQL tables. Here are two more examples which are equivalent to the INNER JOIN examples:

SELECT *
FROM tableA a, tableB b
WHERE a.someColumn = b.otherColumn

SELECT *
FROM tableA a, tableB b
WHERE a.columnName = b.columnName

Further information

You have seen how to write inner joins with the comma operator. From our point of view, it’s “OK” to use this feature. However, using the alternative syntax makes it easier to read your joins. It’s considered as a good behavior to write statements where you can directly see if it’s an INNER JOIN or a CROSS JOIN (the Cartesian product of two tables).

error occurs usualy when insert a new cartdrige

the easy solution is to press “stop” more than 5 seconds

 

Recently fixed this problem after much effort and failed attempts. System restore and safe mode were inaccessible reinstalling windows `over the top` of itself was not an option either as the windows partition was not being recognised which meant only a clean windows install as a last resort. However I eventually tried the following couple of fixes with the final one doing the trick for me.

1) on grub-boot prompt.
press “e” to enter edit mode

2) then press downarrow to reach the line that starts with “kernel “
press “e” again

3) at the end of this line type in “init=/bin/sh” or “/bin/bash”

4) then press enter to make that change and press “b” to boot

in a few seconds you will be on your “#” prompt

5) only one step left
“mount -o remount rw /”

this step is necessary coz in this case root file system is mounted as read only.

6) finally type “passwd” and you get the screen to change the password

and then type in “init 6? or “reboot”