Kā paātrinās Windows XP ielādi?

[Guest]

Jautājums:

Atbilde:

 

BootVis.exe Tool for System Manufacturers

Updated: September 19, 2003

 

About Bootvis.exe

Bootvis.exe is a performance tracing and visualization tool that Microsoft designed to help PC system designers and software developers identify performance issues for boot/resume timing while developing new PC products or supporting software.

 

Please note that Bootvis.exe is not a tool that will improve boot/resume performance for end users. Contrary to some published reports, Bootvis.exe cannot reduce or alter a system's boot or resume performance. The boot optimization routines invoked by Bootvis.exe are built into Windows XP. These routines run automatically at pre-determined times as part of the normal operation of the operating system.

 

If you are an end-user seeking to resolve issues for boot/resume performance on your PC, we recommend that you contact the vendor from whom you purchased the PC. For information from Microsoft on specific issues, you can search Knowledge Base for Windows XP product issues related to "resume time." Knowledge Base is a free information service available at: ;kbhowto"]http://support.microsoft.com/?scid=fh;[ln];kbhowto

 

You can also post questions to the Microsoft Windows XP Newsgroups at: http://support.microsoft.com/newsgroups/?p...p&Product=winxp

 

If you are a software developer or system designer seeking assistance for using Bootvis.exe in your development efforts, please work with your usual Microsoft Product Support Services (PSS) contacts for developer support. To get developer support if you do not already have a contact, please see: http://msdn.microsoft.com/support/

 

The Bootvis.exe tool is no longer available from this site.

[gigis]

Ar šito vajag uzmanīgi!

Man pēc Bootvis lietošanas sāka veidoties liels "C:WINDOWSSystem32LogFilesWMItrace.log" fails, kas dažās stundās piepildīja cieto, pārstartējot izdzēsās un atkal strauji palielinājās par pāris MB sekundē. Pārinstalēju windows, vēlāk gan atradu, kā ar šo problēmu cīnīties:

Inflated TRACE.LOG problem, how to fix.

 

After running the MS Bootvis utility, the file C:WINDOWSSystem32LogFilesWMItrace.log becomes hugely inflated.

 

The file shrinks on reboting but may rapidly grow to a few gig's in size, to cure the problem run BootVis again and click Trace-->Stop Tracing, the file will now stop growing and may be safely deleted.

 

Bootvis tomēr nedaudz paātrina sistēmas ielādes ātrumu, tāpēc ir vērts pamēģināt.

[Guest]

Ar šito vajag uzmanīgi!

Man pēc Bootvis lietošanas sāka veidoties liels "C:WINDOWSSystem32LogFilesWMItrace.log" fails' date=' kas dažās stundās piepildīja cieto, pārstartējot izdzēsās un atkal strauji palielinājās par pāris MB sekundē. Pārinstalēju windows, vēlāk gan atradu, kā ar šo problēmu cīnīties:

Inflated TRACE.LOG problem, how to fix.

 

After running the MS Bootvis utility, the file C:WINDOWSSystem32LogFilesWMItrace.log becomes hugely inflated.

 

The file shrinks on reboting but may rapidly grow to a few gig's in size, to cure the problem run BootVis again and click Trace-->Stop Tracing, the file will now stop growing and may be safely deleted.

 

Bootvis tomēr nedaudz paātrina sistēmas ielādes ātrumu, tāpēc ir vērts pamēģināt.

 

tad mosh padalies savaas zinaashanaas kaa tiikt galaa ar sho probu

[clickhere]

vot shitaadus izsmeljoshos topikus kur ir pilniibaa 100% viss pateikts dereetu likt kaut kaadaa jau gatavaa saitaa vai citaa nodaljaa.. citiem un pashiem buus vieglaak peeec tam atrast

[gigis]

tad mosh padalies savaas zinaashanaas kaa tiikt galaa ar sho probu

 

Googlē atradu divus risinājumus problēmai:

1)

if you notice excessive disk activity after using bootvis' date='go to the registry and find HKLM,system,current control set,control,WMI,globallogger. look at the value for START, if it is set to 1 change it to 0. after a reboot,you can delete Windowssystem32logfilesWMItrace.log[/quote']

2)

to cure the problem run BootVis again and click Trace-->Stop Tracing, the file will now stop growing and may be safely deleted

 

pats šīs metodes neesmu pārbaudījis, jo neizdevās problēmu atkārtoti izraisīt

 

Problēma var rasties, ja lieto trace->next boot vai citu trace funkciju, bet nekādām problēmām nevajadzētu būt, ja lieto tikai Trace->Optimize system (kas arī ir vienīgais, ko parastam lietotājam no šīs progas vajag)

 

Optimizācijas būtība ir tas, ka faili, kas tiek lietoti sistēmas boot laikā tiek defragmentēti un salikti optimālā izkārtojumā uz diska. Diemžēl optimizācija izraisa pārējo failu fragmentāciju, tāpēc, ja pēc optimizācijas lieto citu defragmenteru, visa optimizācija atkal tiek izjaukta