Благодаря за предложението, принципно и Raze ми беше предложил същото - да направя тест на повърхността на диска, но честно казано, макар и да знам че би трябвало да е само един безобиден тест, предполагам че на програмата Hard Disk Sentinel не случайно е написано най-долу на прозореца предшестващ началото му с удебелен шрифт:

Разработчикът не дава гаранция за запазване на данните на никои дискове!

Още повече че силно се съмнявам да е повреден диска, но поне пък логовете са лесни, ето 700 + лога:

 

Winampp.evtx : https://dox.abv.bg/download?id=74f689602a#

Winamp.xml - https://dox.abv.bg/download?id=bbed500525#

От няколко от тях гледам че е указан път към някои плъгини, та може и да е от тях.

 

Не съм сигурен в .xml файла който е някакви си байтове какво точно експортирах, но в .evtx трябва да присъстват всичките.

Под логове имах предвид от папка C:\Windows\System32\winevt\Logs файловете system.evtx и application.evtx,  а под проверка -
echo y|chkdsk "c:" /f
echo y|chkdsk "d:" /f

System.evtx: https://dox.abv.bg/download?id=87512ca359#

Application.evtx: https://dox.abv.bg/download?id=e36c7f8049#

Spoiler

 

C:\WINDOWS\system32>echo y|chkdsk "c:" /f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process.  Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
This volume will be checked the next time the system restarts.

C:\WINDOWS\system32>echo y|chkdsk "d:" /f
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Volume dismounted.  All opened handles to this volume are now invalid.
Volume label is Локален диск.

Stage 1: Examining basic file system structure ...
  480256 file records processed.
File verification completed.
  124 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  3172 reparse records processed.
  497950 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  3172 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  8848 data files processed.
CHKDSK is verifying Usn Journal...
  35612424 USN bytes processed.
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.

Windows has made corrections to the file system.
No further action is required.

 871183356 KB total disk space.
 436569460 KB in 255555 files.
     78080 KB in 8849 indexes.
         0 KB in bad sectors.
    608200 KB in use by the system.
     65536 KB occupied by the log file.
 433927616 KB available on disk.

      4096 bytes in each allocation unit.
 217795839 total allocation units on disk.
 108481904 allocation units available on disk.

 

Ще рестартирам да направи и на C:/ , но къде да търся записа после ако има нужда ?

Цитат

CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.

Windows has made corrections to the file system.

На D  е направен ремонт

chkdsk boot log:
Стартирай Powershell и в него постави:
 

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

На десктопа ще се появи фаил CHKDSKResults.txt - копирай съдържанието му и го сподели.

Отвори C:\WINDOWS\system32\config
и започни да отваряш последователно папките:
\systemprofile
\AppData
\Local
В тази папка създай нова папка и я преименувай на TileDataLayer

Преинсталирай BB FlashBack Pro 5

 

Редактирано 21 май 20206 г. от DarkEdge (преглед на промените)

Spoiler

TimeCreated : 21.5.2020 г. 21:26:06
Message     : 
              
              Checking file system on 😄
              The type of the file system is NTFS.
              Volume label is Windows 10 Pro 1809.
              
              
              A disk check has been scheduled.
              Windows will now check the disk.                         
              
              Stage 1: Examining basic file system structure ...
                479232 file records processed.                                                        
              
              File verification completed.
                11951 large file records processed.                                   
              
                0 bad file records processed.                                     
              
              
              Stage 2: Examining file name linkage ...
                46979 reparse records processed.                                      
              
                610162 index entries processed.                                                       
              
              Index verification completed.
                0 unindexed files scanned.                                        
              
                0 unindexed files recovered to lost and found.                    
              
                46979 reparse records processed.                                      
              
              
              Stage 3: Examining security descriptors ...
              Cleaning up 2411 unused index entries from index $SII of file 0x9.
              Cleaning up 2411 unused index entries from index $SDH of file 0x9.
              Cleaning up 2411 unused security descriptors.
              Security descriptor verification completed.
                65466 data files processed.                                           
              
              CHKDSK is verifying Usn Journal...
                37370136 USN bytes processed.                                                           
              
              Usn Journal verification completed.
              
              Windows has scanned the file system and found no problems.
              No further action is required.
              
               104529498 KB total disk space.
                63550188 KB in 297642 files.
                  194032 KB in 65467 indexes.
                       0 KB in bad sectors.
                  595534 KB in use by the system.
                   65536 KB occupied by the log file.
                40189744 KB available on disk.
              
                    4096 bytes in each allocation unit.
                26132374 total allocation units on disk.
                10047436 allocation units available on disk.
              
              Internal Info:
              00 50 07 00 70 8a 05 00 36 26 0a 00 00 00 00 00  .P..p...6&......
              f9 01 00 00 8a b5 00 00 00 00 00 00 00 00 00 00  ................
              
              Windows has finished checking your disk.
              Please wait while your computer restarts.
              

 

 

Папката е създадена с указаното име.

преди 24 минути, DarkEdge написа:

Преинсталирай BB FlashBack Pro 5

 

Тази редакция я видях току-що.

Той ли ми прави номера ? Нещо е повреден или съм със стара версия (5.4.0) ? Може би и двете...

И дял С е ремонтиран.
Обнови драйвъра на мрежовия адаптер на VirtualBox като укажеш папка:
C:\Program Files\Sun\VirtualBox за търсене на драйвъра

Ако това не помогне, реинсталирай VirtualBox.

Остава да тестваш резултата от ремонтите.

Редактирано 21 май 20206 г. от DarkEdge (преглед на промените)

Добре, но нито имам такава папка, имам C:\Program Files\Oracle\VirtualBox - тя ще да е, но пък прерових всички категории на диспечера на устройства и не намерих въпросния адаптер.

 

 

Като цъкна покажи скритите устройства изглежда че пак го няма, под Мрежови карти излиза само някаква Bluetooth Personal Area Network.

Тогава са някакви остатъци от VirtualBox:
 

Цитат

The description for Event ID 12 from source VBoxNetLwf cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

\Device\VBoxNetLwf

The message resource is present but the message was not found in the message table

 

Сега работи ли Winamp?

преди 6 минути, Freem@n написа:

нито имам такава папка, имам C:\Program Files\Oracle\VirtualBox - тя ще да е

тя ще да е, но пък нямаш мрежов адаптер. Значи ако ползваш програата, я преинсталирай.

преди 1 час, Freem@n написа:

беше предложил същото

Това въобще не е същото

Преди малко пак имаше един срив и случайност или не - това се случи малко след като отворих BB FlashBack само да проверя версията му коя е. (Когато крашна Winamp го бях вече затворил BB-то.)

 

Значи, по мои наблюдения крашва най-вече когато възпроизвежда музика от компютъра, файлове... когато е на някое радио сякаш по-не се товари и не прави толкова проблеми.

 

VBox поне засега не я ползвам, инсталирах я само да тествам един Linux.

преди 3 минути, Freem@n написа:

Преди малко пак имаше един срив и случайност или не - това се случи малко след като отворих BB FlashBack само да проверя версията му коя е. (Когато крашна Winamp го бях вече затворил BB-то.)

Не, че разбрах нещо...

Честитоооо!

Актуализация на Windows 10 от май 2020 г.

преди 12 часа, П.Петров написа:

Честитоооо!

Актуализация на Windows 10 от май 2020 г.

Е кажи какво ти е дал де, на мен не ми казва какво ще се свали като ISO посещавайки им сайта с Линукса.

Известни проблеми в Windows 10 версия 2004

Known issues

This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

 

TABLE 4

Summary	Originating update	Status	Last updated
Difficulty connecting to more than one Bluetooth device Windows 10 devices with certain Realtek drivers might be unable to connect to more than one Bluetooth device. See details >	N/A	Investigating	May 27, 2020 12:22 AM PT
Errors or issues during or after updating devices with Conexant ISST audio drivers Devices with affected Conexant ISST audio drivers might receive an error or have issues with Windows 10, version 2004. See details >	N/A	Investigating	May 27, 2020 12:22 AM PT
Errors or issues during or after updating devices with certain Conexant audio drivers Devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen. See details >	N/A	Investigating	May 27, 2020 12:20 AM PT
Issues using ImeMode property to control IME mode for individual text entry fields Some IMEs for certain langauges might have issues using the ImeMode property with certain apps. See details >	N/A	Investigating	May 27, 2020 12:18 AM PT
Variable refresh rate not working as expected on devices with Intel iGPU Enabling VRR on affected devices will not enable the VRR for most games, especially games using Direct X 9. See details >	N/A	Investigating	May 27, 2020 12:13 AM PT
Stop error when plugging or unplugging a Thunderbolt dock Devices using Thunderbolt docks may receive a stop error when plugging in or unplugging the dock See details >	N/A	Investigating	May 27, 2020 12:18 AM PT
Errors or unexpected restarts for some devices using Always On, Always Connected Devices with more than one Always On, Always Connected capable network adapter might have issues. See details >	N/A	Investigating	May 27, 2020 12:11 AM PT
No mouse input with apps and games using GameInput Redistributable Affected apps and games using both GameInput Redistributable and Windows 10, version 2004 might lose mouse input. See details >	N/A	Investigating	May 27, 2020 12:11 AM PT
Issues updating or starting up devices when aksfridge.sys or aksdf.sys is present Devices with apps or drivers using certain versions of aksfridge.sys or aksdf.sys might have issues updating or starting See details >	N/A	Investigating	May 27, 2020 12:09 AM PT
Issue with older drivers for Nvidia display adapters (GPU) You might have issues if you are using an Nvidia display adapter (GPU) and drivers with a version below 358.00. See details >

преди 15 часа, П.Петров написа:

Честитоооо!

Актуализация на Windows 10 от май 2020 г.

Известни проблеми за тази актуализация:

Details    Originating update    Status    History
Difficulty connecting to more than one Bluetooth device
Realtek and Microsoft have found incompatibility issues with certain versions of drivers for Realtek Bluetooth radios and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Realtek Bluetooth radio drivers might be unable to connect or pair with more than one Bluetooth device at a time after updating.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Realtek Bluetooth radio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated.

Affected platforms:
Client: Windows 10, version 2004
Server: Windows Server, version 2004
Next steps: Microsoft and Realtek are working on a resolution and will provide an update in an upcoming release.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top    N/A

Investigating
Last updated:
May 27, 2020
12:22 AM PT

Opened:
May 27, 2020
12:22 AM PT
Errors or issues during or after updating devices with Conexant ISST audio drivers
Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant ISST audio driver and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant ISST audio driver might receive an error or experience issues while installing the update or after the device has updated. The affected driver will be named Conexant ISST Audio or Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have file name uci64a96.dll through uci64a231.dll and a file version lower than 7.231.3.0.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated.

Affected platforms:
Client: Windows 10, version 2004
Server: Windows Server, version 2004
Workaround: To mitigate this issue, you will need to check with your device manufacturer (OEM) to see if an updated driver is available and install it.

Next steps: Microsoft and Synaptics are working on a resolution and will provide an update in an upcoming release.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top    N/A

Investigating
Last updated:
May 27, 2020
12:22 AM PT

Opened:
May 27, 2020
12:22 AM PT
Errors or issues during or after updating devices with certain Conexant audio drivers
Synaptics and Microsoft have found incompatibility issues with certain versions of drivers for Conexant or Synaptics audio devices and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Conexant or Synaptics audio drivers might receive a stop error with a blue screen during or after updating to Windows 10, version 2004. The affected driver will be named Conexant HDAudio Driver under Sound, video and game controllers in Device Manager and have versions 8.65.47.53, 8.65.56.51, or 8.66.0.0 through 8.66.89.00 for chdrt64.sys or chdrt32.sys.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Conexant or Synaptics audio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated.

Affected platforms:
Client: Windows 10, version 2004
Server: Windows Server, version 2004
Next steps: Microsoft and Synaptics are working on a resolution and will provide an update in an upcoming release.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top    N/A

Investigating
Last updated:
May 27, 2020
12:20 AM PT

Opened:
May 27, 2020
12:20 AM PT
Issues using ImeMode property to control IME mode for individual text entry fields
Some apps utilize the ImeMode property to control the IME (Input Method Editor) mode for individual text entry fields to increase typing efficiency. Some IMEs in Windows 10, version 2004 (the May 2020 Update) might have issues using the ImeMode property with certain apps. For example, the input mode will not switch automatically to Kanji or Hiragana.

Affected platforms:
Client: Windows 10, version 2004
Server: Windows Server, version 2004
Next steps: For more information and workaround steps, please see KB4564002.

Back to top    N/A

Investigating
Last updated:
May 27, 2020
12:18 AM PT

Opened:
May 27, 2020
12:18 AM PT
Variable refresh rate not working as expected on devices with Intel iGPU
Intel and Microsoft have found incompatibility issues when using a monitor with Variable refresh rate (VRR) plugged into an Intel integrated graphics processing unit (iGPU) display adapter and Windows 10, version 2004 (the Windows 10 May 2020 Update). Enabling VRR on affected devices will not enable the VRR for most games, especially games using Direct X 9.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers or firmware from being offered Windows 10, version 2004.

Affected platforms:
Client: Windows 10, version 2004
Next steps: Microsoft and Intel are working on a resolution and will provide an update in an upcoming release.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top    N/A

Investigating
Last updated:
May 27, 2020
12:13 AM PT

Opened:
May 27, 2020
12:13 AM PT
Stop error when plugging or unplugging a Thunderbolt dock
Intel and Microsoft have found incompatibility issues when Windows 10, version 2004 (the Windows 10 May 2020 Update) is used with certain settings and a Thunderbolt dock. On affected devices, you might receive a stop error with a blue screen when plugging or unplugging a Thunderbolt dock. Affected Windows 10 devices will have at least one Thunderbolt port, have Kernel DMA Protection enabled and Windows Hypervisor Platform disabled. To verify your Kernel DMA Protection settings, please see How to check if Kernel DMA Protection is enabled. To verify your Windows Hypervisor Platform settings, select Start, type turn windows features on or off and select it. When the Windows Features dialog opens, find the setting for Windows Hypervisor Platform. If it is note checked, then Windows Hypervisor Platform is disabled.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers or firmware from being offered Windows 10, version 2004.

Affected platforms:
Client: Windows 10, version 2004
Next steps: Microsoft and Intel are working on a resolution and will provide an update in an upcoming release.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top    N/A

Investigating
Last updated:
May 27, 2020
12:18 AM PT

Opened:
May 27, 2020
12:18 AM PT
Errors or unexpected restarts for some devices using Always On, Always Connected
Some devices using the Always On, Always Connected feature might have compatibility issues with Windows 10, version 2004 (the Windows 10 May 2020 Update). Affected devices will have more than one Always On, Always Connected capable network adapter, such as the Microsoft Surface Pro 7 and Microsoft Surface Laptop 3, and might receive errors or unexpected shutdown or restart.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected drivers or firmware from being offered Windows 10, version 2004.

Affected platforms:
Client: Windows 10, version 2004
Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top    N/A

Investigating
Last updated:
May 27, 2020
12:11 AM PT

Opened:
May 27, 2020
12:11 AM PT
No mouse input with apps and games using GameInput Redistributable
An incompatibility issue was found with some apps and games using GameInput Redistributable and Windows 10, version 2004 (the Windows 10 May 2020 Update). Affected apps or games might lose mouse input. Note GameInput Redistributable might be bundle with apps and games and might be silently installed during the installation of that app or game.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with GameInput Redistributable from being offered Windows 10, version 2004.

Affected platforms:
Client: Windows 10, version 2004
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top    N/A

Investigating
Last updated:
May 27, 2020
12:11 AM PT

Opened:
May 27, 2020
12:11 AM PT
Issues updating or starting up devices when aksfridge.sys or aksdf.sys is present
An incompatibility issue was found with apps or drivers using certain versions of aksfridge.sys or aksdf.sys and Windows 10, version 2004 (the Windows 10 May 2020 Update). When an affected version of aksfridge.sys or aksdf.sys is present, Windows 10, version 2004 might fail to install or might fail to start after updating. Affected file versions are up to 1.8.0.* for aksfridge.sys or up to 1.51.* for aksdf.sys.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with an affected version of aksfridge.sys from being offered Windows 10, version 2004 or Windows Server, version 2004.

Affected platforms:
Client: Windows 10, version 2004
Server: Windows Server, version 2004
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top    N/A

Investigating
Last updated:
May 27, 2020
12:09 AM PT

Opened:
May 27, 2020
12:09 AM PT
Issue with older drivers for Nvidia display adapters (GPU)
Nvidia and Microsoft have found incompatibility issues with certain versions of Nvidia display adapter drivers and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Nvidia display driver versions might receive a stop error with a blue screen or other issues during or after installing the update to Windows 10, version 2004. The affected drivers are any version lower than 358.00.

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Nvidia display drivers drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated.

Affected platforms:
Client: Windows 10, version 2004
Server: Windows Server, version 2004
Workaround: To mitigate this issue, you will need to check with your device manufacturer (OEM) to see if an updated driver is available and install it.

Next steps: Microsoft and Nvidia are working on a resolution and will provide an update in an upcoming release.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Редактирано 28 май 20206 г. от DarkEdge (преглед на промените)

Колеги, със сигурност сте го коментирали назад в темата, ама вече станиците са над 400. Как да забраня ъпдейтите завинаги? 

преди 1 минута, criminall написа:

Колеги, със сигурност сте го коментирали назад в темата, ама вече станиците са над 400. Как да забраня ъпдейтите завинаги? 

На Windows 10 май не може.

https://www.sordum.org/9470/windows-update-blocker-v1-5/

 

преди 2 минути, Валсо написа:

май не може

И през май, и през юни пак може.

преди 1 минута, DarkEdge написа:

https://www.sordum.org/9470/windows-update-blocker-v1-5/

Леле, до какво отчаяние са ви докарали тия от Майкрософт, та да трябва някой да прави отделен инструмент за спиране на ъпдейтите!
И понеже виждам реакцията ти на предишния ми пост, казах "май не може", като имах предвид, че вътрешно/нейтив не може - не и както можеше в 7-цата, примерно. Освен това преди време четох новини, че щели да връщат тази опция да се спират ъпдейтите, пък после решили да не я връщат, после пак решили да я връщат и въобще все такива непостоянни решения като настроенията на бременна жена.  

преди 5 минути, Валсо написа:

имах предвид, че вътрешно/нейтив не може - не и както можеше в 7-цата, примерно.

Забележка: Това не се отнася за Home версиите по подразбиране - липсва им gpedit.

Но, пък, си е мн. по-удобно с едно тулче с размер 800kB като wub да цъкнеш един бутон и да се свърши работата.

Редактирано 28 май 20206 г. от DarkEdge (преглед на промените)

преди 46 минути, Валсо написа:

..., казах "май не може", като имах предвид, че вътрешно/нейтив не може - не и както можеше в 7-цата, примерно. 

Може и в Home 10 от сервизите съм ги спрял, както ме научи тука един на тази тема.

И сега какво, да не я ли сваляме за сега тази нова версия ?
Колко да изчакаме да я ремонтират ?

преди 6 часа, Белгиеца написа:

Може и в Home 10 от сервизите съм ги спрял, както ме научи тука един на тази тема.

И сега какво, да не я ли сваляме за сега тази нова версия ?
Колко да изчакаме да я ремонтират ?

На виртуалка на пръв поглед си бачка дабре. Пак зависи за какво ще я използваш. Ако я слагаш на клиент е криво, ако е за теб - тествай. Аз мисля че скоро ще я пачнат/фикснат през ъпдейтите.

преди 12 часа, DarkEdge написа:

https://www.sordum.org/9470/windows-update-blocker-v1-5/

От днес това нещо има и български превод. По-точно отпреди 2 чàса.

Твърде левашко изпълнение на превода!

преди 12 часа, Белгиеца написа:

както ме научи тука един на тази тема.

Левак!@ Да беше проявил някакво уважение към човека и да го споменеш с ника му. Еб@си пренебрежението - един. Отдалече си личи, че си от Левуново.

преди 29 минути, DarkEdge написа:

Твърде левашко изпълнение на превода!

Левак!@ Да беше проявил някакво уважение към човека и да го споменеш с ника му. Еб@си пренебрежението - един. Отдалече си личи, че си от Левуново.

И ти си същият неблагодарник като Бангиеца. Като си такъв тарикат, направи го ти.

преди 2 минути, Валсо написа:

Като си такъв тарикат, направи го ти.

Умнико, ползвам си го на английски. Ти да не би някъде да каза благодаря за информацията? Не съм счел за необходимо да го напиша, не съм го направил!

преди 25 минути, DarkEdge написа:

Умнико, ползвам си го на английски. Ти да не би някъде да каза благодаря за информацията? Не съм счел за необходимо да го напиша, не съм го направил!

А тези, които не знаят английски? Типичният егоист, като всяка winsheep...