Boas,
Eu preferencialmente prefiro clean install.
Já experimentei o upgrade e o clean install e o upgrade como é óbvio nao permite ver grandes melhorias.
instalei no meu Tecra M1 um clean de windows 7 PRo e noto muito melhor performance do que no windows vista Business.
Segue informaçao sobre upgrade do windows existente para o novo windows 7:
1. Windows XP para Windows 7 :
a melhor forma é guardar os documentos ( atraves de user profile transfer e fazer clean install do windows 7
"Information here is still a bit murky because Microsoft has not specified which XP editions will be eligible.
The good news is that the company has confirmed that users currently running Windows XP will be able to buy the cheaper upgrade option of Windows 7. However, they will only be able to perform a clean install.
The hassle of backing up applications and user data will fall on the user; the upgrade process will not backup anything.
That may come as a shock to some, but Microsoft typically lets users purchase the cheaper upgrade option by owners of the last two releases of Windows (in this case XP and Vista) but the older of the two operating systems usually require a clean install.
From Windows Vista to Windows 7
Microsoft will only allow the following upgrade paths to Vista users.
For example, users who purchase an upgrade copy of Windows 7 Professional and have Vista Home Premium will only be able to perform a clean install.
Here's the migration list:
Windows Vista Home Premium to Windows 7 Home Premium
Windows Vista Business to Windows 7 Professional
Windows Vista Ultimate to Windows 7 Ultimate
If you are performing an upgrade installation from Windows Vista, the base language must match the target Windows 7 language, you must have about 9GB of free space for the installation, and the installation can only occur on the same partition that holds Windows Vista. Existing applications and user data will be automatically migrated to the new Windows 7 installation.
Clean installs will require about 16GB for the installation process. Unless the user chooses to repartition or format the current partition, Vista's files from C:\WINDOWS will be preserved under C:\WINDOWS.OLD, just as when upgrading from XP to Vista. Clean installs will also have to be performed when upgrading from a 32-bit version to a 64-bit version.
Windows Anytime Upgrade (WAU)
Once you have some edition of Windows 7 on your system, whether you purchased it via an OEM or just upgraded from Windows XP or Windows Vista, you will be able to upgrade to a "more premium" version of Windows 7 by purchasing an upgrade key to unlock additional features, just as in with Vista.
For example, you could start off with Windows Vista Home Premium, upgrade to Windows 7 Home Premium, and then later choose to upgrade to Windows 7 Professional.
As with Vista, the same DVD includes the various editions. Unlike with Vista, every edition of Windows 7 is a superset of the previous edition, so you will not lose any features when upgrading.
quarta-feira, 4 de novembro de 2009
segunda-feira, 2 de novembro de 2009
STOP ERROR 0X000000FC HP NC6400
On boot Hp nc6400 gives an error 0x0000007C.
I remove the battery and flush the bios for 30 seconds and now it seems to be working.
gives a message after boot that is error loading c:\windows\system32\otpbqymf.dll
seems to be ok now.
I remove the battery and flush the bios for 30 seconds and now it seems to be working.
gives a message after boot that is error loading c:\windows\system32\otpbqymf.dll
seems to be ok now.
segunda-feira, 19 de outubro de 2009
SYMANTEC UNINSTALL PASSWORD
In the cases where Symantec AntiVirus server has been taken down and no longer exist, or the client computer has no access to company network, or the default client uninstall password does not work, the following hack will enable you to remove Symantec Antivirus without using a password:
Open Registry Editor (regedit).
Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LANDesk\VirusProtect6\CurrentVersion\Administrator Only\Security\
Change the value for useVPuninstallpassword key from 1 to 0.
Exit Registry Editor and now you can uninstall Symantec AntiVirus Client.
The trick should work on most version of Symantec AntiVirus client or Norton AntiVirus Client, including version 7, 8, 9 or 10.
Open Registry Editor (regedit).
Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LANDesk\VirusProtect6\CurrentVersion\Administrator Only\Security\
Change the value for useVPuninstallpassword key from 1 to 0.
Exit Registry Editor and now you can uninstall Symantec AntiVirus Client.
The trick should work on most version of Symantec AntiVirus client or Norton AntiVirus Client, including version 7, 8, 9 or 10.
sexta-feira, 24 de julho de 2009
UNMOUNTABLE_BOOT_VOLUME HP nc6400
HP notebooks that use Microsoft Windows XP without XP Service Pack 2 installed may start with the following error:
STOP 0x000000ED (0xaaaaaaaa,0xbbbbbbbb,0xcccccccc,0xdddddddd) UNMOUNTABLE_BOOT_VOLUME
This error is related to the way Windows XP interacts with the hard drive during an unexpected shutdown. Sometimes the contents of the cache are not written to the drive properly causing the error to appear when the notebook restarts.
This document provides instructions to repair your notebook PC and prevent this error from reoccurring. Once you have repaired your notebook PC, be sure to follow the steps to prevent the error from occurring again.
View the knowledge base article from Microsoft, Stop 0x000000ED Error Message When Volume on IDE Drive with Caching Enabled Is Mounted (in English) and the Microsoft Help and Support article, Unmountable Boot Volume (in English).
Repairing the notebook PC when the error occurs
The following repair options require the HP Operating System disc that was included with the HP Notebook PC. If you have misplaced or lost your disc please view HP Notebook PCs - Obtaining a Recovery CD or DVD set to order a new disc. For customers in Europe, Middle East, and Africa please refer to the HP support document Europe, Middle East, and Africa - Statement on the Availability of the Recovery Software on CD . For other countries/regions, contact your local HP support center for information about obtaining recovery CDs.
Option 1:
Use CHKDSK from the Recovery Console
Start the computer with the HP Operating System disc in the CD or DVD drive.
Press any key when prompted to boot from the CD or DVD.
A blue screen will appear and several files will load. This process takes about 30 seconds to complete. You should not have to select anything from the keyboard.
At the blue setup menu, press R to Repair a Windows XP installation.
At the C: prompt, type chkdsk /r . This repair process may take 30 - 60 minutes depending on the size of the hard drive and repairs needed.
After the chkdsk completes, type Exit at the C: prompt.
Windows will restart. Eject the CD or DVD and it should continue normally.
STOP 0x000000ED (0xaaaaaaaa,0xbbbbbbbb,0xcccccccc,0xdddddddd) UNMOUNTABLE_BOOT_VOLUME
This error is related to the way Windows XP interacts with the hard drive during an unexpected shutdown. Sometimes the contents of the cache are not written to the drive properly causing the error to appear when the notebook restarts.
This document provides instructions to repair your notebook PC and prevent this error from reoccurring. Once you have repaired your notebook PC, be sure to follow the steps to prevent the error from occurring again.
View the knowledge base article from Microsoft, Stop 0x000000ED Error Message When Volume on IDE Drive with Caching Enabled Is Mounted (in English) and the Microsoft Help and Support article, Unmountable Boot Volume (in English).
Repairing the notebook PC when the error occurs
The following repair options require the HP Operating System disc that was included with the HP Notebook PC. If you have misplaced or lost your disc please view HP Notebook PCs - Obtaining a Recovery CD or DVD set to order a new disc. For customers in Europe, Middle East, and Africa please refer to the HP support document Europe, Middle East, and Africa - Statement on the Availability of the Recovery Software on CD . For other countries/regions, contact your local HP support center for information about obtaining recovery CDs.
Option 1:
Use CHKDSK from the Recovery Console
Start the computer with the HP Operating System disc in the CD or DVD drive.
Press any key when prompted to boot from the CD or DVD.
A blue screen will appear and several files will load. This process takes about 30 seconds to complete. You should not have to select anything from the keyboard.
At the blue setup menu, press R to Repair a Windows XP installation.
At the C: prompt, type chkdsk /r . This repair process may take 30 - 60 minutes depending on the size of the hard drive and repairs needed.
After the chkdsk completes, type Exit at the C: prompt.
Windows will restart. Eject the CD or DVD and it should continue normally.
segunda-feira, 27 de abril de 2009
sexta-feira, 3 de abril de 2009
erros ARcServe E5110 The database is no longer available." "E4101 Unable to login to db engine" "E3530 Failed to login to database EC=-2005
This has been based on CA support KB - Reference is TEC 426805
Title: "E5110 The database is no longer available." "E4101 Unable to login to db engine" "E3530 Failed to login to database EC=-2005"
Description:
The errors listed above may appear if there is a problem with the ARCserve standard database (VLDB) which can in turn place the ARCserve Database Engine in a shutdown state.
Solution:
Resolving the Problem
If the database engine will not stay in a running state this could be an indication of a problem with the contents within the database. As a first step perform the following:
Run CSTOP.BAT from the ARCserve install directory.
Remove the following files from X:\Program Files\CA\BrightStor ARCserve Backup\Database:
rdm.chi, rdm.chk and rAAAA*.chg
Remove the *.tmp files from the X:\Program Files\CA\BrightStor ARCserve Backup\temp directory.
Edit VELOCIS.INI in X:\Program Files\CA\BrightStor ARCserve Backup\Database modifying the following entries to the values listed:
Archiving =0
AsyncRead =0
AsyncWrite=0
Run CSTART.BAT from the ARCserve install directory.
If this does not help than this may be an indication that detail table data in the database have inconsistencies. An initialization of this table can be done to zero out the detail specific data while retaining specific information relating to jobs, tapes, media pools, etc. in tact. It should be noted that this operation will remove all detail record information for given backups, and specific restore data will need to be merged back into the database for restore by Tree, Session, and Query operations.
Close all ARCserve applications.
Start > Programs > ARCserve > ARCserve Server Admin.
Select the Database Engine tab.
Select Operation > Initialize Database...
Select "The database to be initialized" and then highlight astpsdat.
Click the initialize button.
If the initialization of the ASTPSDAT database does not resolve the problem please contact CA Technical Support.
Title: "E5110 The database is no longer available." "E4101 Unable to login to db engine" "E3530 Failed to login to database EC=-2005"
Description:
The errors listed above may appear if there is a problem with the ARCserve standard database (VLDB) which can in turn place the ARCserve Database Engine in a shutdown state.
Solution:
Resolving the Problem
If the database engine will not stay in a running state this could be an indication of a problem with the contents within the database. As a first step perform the following:
Run CSTOP.BAT from the ARCserve install directory.
Remove the following files from X:\Program Files\CA\BrightStor ARCserve Backup\Database:
rdm.chi, rdm.chk and rAAAA*.chg
Remove the *.tmp files from the X:\Program Files\CA\BrightStor ARCserve Backup\temp directory.
Edit VELOCIS.INI in X:\Program Files\CA\BrightStor ARCserve Backup\Database modifying the following entries to the values listed:
Archiving =0
AsyncRead =0
AsyncWrite=0
Run CSTART.BAT from the ARCserve install directory.
If this does not help than this may be an indication that detail table data in the database have inconsistencies. An initialization of this table can be done to zero out the detail specific data while retaining specific information relating to jobs, tapes, media pools, etc. in tact. It should be noted that this operation will remove all detail record information for given backups, and specific restore data will need to be merged back into the database for restore by Tree, Session, and Query operations.
Close all ARCserve applications.
Start > Programs > ARCserve > ARCserve Server Admin.
Select the Database Engine tab.
Select Operation > Initialize Database...
Select "The database to be initialized" and then highlight astpsdat.
Click the initialize button.
If the initialization of the ASTPSDAT database does not resolve the problem please contact CA Technical Support.
segunda-feira, 9 de fevereiro de 2009
reset sessao Terminal Server por CMD
Fortunately there is an easy solution. Windows 2000+ (includes Windows XP and 2003) have two command-line tools called qwinsta and rwinsta that can query and reset a remote session.
For example, let's say that I can't gain access to a server using Terminal Services because both sessions are used up. I can use another server to check the status of the first one. As long as the logged in user has administrative rights on the non-accessible machine I would run this:
qwinsta /server:12.12.12.12
Where 12.12.12.12 is the IP address or name of the non-accessible machine.
This will display something like this:
> qwinsta /server:12.12.12.12
SESSIONNAME USERNAME ID STATE TYPE DEVICE console 0 Conn wdcon rdp-tcp 65536 Listen rdpwd rdp-tcp#470 Bob 1 Active rdpwd rdp-tcp#471 Jane 3 Active rdpwd
Now I know that Bob and Jane are the two that are logged in. Since Jane left the office 20 minutes ago I know that she forgot to log off. I don't know where Bob is but I only need one session so I'll ignore him for now.
To disconnect Jane's session I would type this:
rwinsta /server:12.12.12.12 3
Notice the 3 which is the session ID I found from using qwinsta above.
Yet another option with W2K3 is a new feature that lets you connect to the desktop directly and gain a 3rd session.
If you're like me, you probably noticed that rwinsta and qwinsta seems like strange names. This came from the Citrix Metaframe days which Terminal Services has descended from. It stands for:
qwinsta = Query WINdows STAtionrwinsta = Reset WINdows STAtion
One final comment. Microsoft has replaced these two tools with Query but since qwinsta and rwinsta is fully compatible with W2K WinXP and W2K3 I choose to use it instead.
For example, let's say that I can't gain access to a server using Terminal Services because both sessions are used up. I can use another server to check the status of the first one. As long as the logged in user has administrative rights on the non-accessible machine I would run this:
qwinsta /server:12.12.12.12
Where 12.12.12.12 is the IP address or name of the non-accessible machine.
This will display something like this:
> qwinsta /server:12.12.12.12
SESSIONNAME USERNAME ID STATE TYPE DEVICE console 0 Conn wdcon rdp-tcp 65536 Listen rdpwd rdp-tcp#470 Bob 1 Active rdpwd rdp-tcp#471 Jane 3 Active rdpwd
Now I know that Bob and Jane are the two that are logged in. Since Jane left the office 20 minutes ago I know that she forgot to log off. I don't know where Bob is but I only need one session so I'll ignore him for now.
To disconnect Jane's session I would type this:
rwinsta /server:12.12.12.12 3
Notice the 3 which is the session ID I found from using qwinsta above.
Yet another option with W2K3 is a new feature that lets you connect to the desktop directly and gain a 3rd session.
If you're like me, you probably noticed that rwinsta and qwinsta seems like strange names. This came from the Citrix Metaframe days which Terminal Services has descended from. It stands for:
qwinsta = Query WINdows STAtionrwinsta = Reset WINdows STAtion
One final comment. Microsoft has replaced these two tools with Query but since qwinsta and rwinsta is fully compatible with W2K WinXP and W2K3 I choose to use it instead.
Subscrever:
Mensagens (Atom)