comming soon...

Speaking of Windows OS (NT versions) ...

comming soon...

It's no brainer that "fast search" that microsoft provides with Winblows Vista and "7" sucks

and anyone that ever was curious enough to find out how it works knows it sucks donkey dick...

 

Dare I say this shit technology dates back to (as far as I know) Word '97 days, and I think it was even then named "fast search", tho can't be assed now to check it out again...

 

MS used Indexing service which runs on startup of Windows and quietly indexes... whatever...

Well this shit hapens in Vista and "7" too, although more sophisticated, but so stupid and slow that

its beyond me why they even rely on such technology...

 

Indexing service simply "scans" file(s) list on your Hard Drive/Disk and makes a list of what it indexed

and then the "Fast Search" that is in your Start Menu simply scans through the list and shows the results...

(this is shortly said...)

 

This process is slow and ineffective since:

1. some folders (most of them) don't get indexed at all

2. user has to manually set which folders or Drives/Partitions to index

3. Indexer scans (indexes) on the fly which causes unnecessary Hard Disk slowdown (not SSD)

4. It writes and reads from a FILE !!!

5. It is so damn slow...

 

Now why do I "trash talk" of this approach ?

Well 1st I hate slow search, fast search is nowdays like doing left mouse click, it must be fast and effective

and 2nd, the MFT (no I will not explain what it is), already contains full list of existing files and their paths

so why not directly use it ?

 

A perfect example of maximum efficiency is program called UltraSearch -> click

This nice small (and Portable and Free), app simply reads directly from MFT, there is no indexing, no writing or reading from a file or database at all !

 

---

 

Another alternative, which I personaly use for reasons I'll write later, is another Portable small and Free

app called Everything -> click

 

Unlike UltraSearch, this app unfortunately reads and writes from a database file, but unlike that MS's shit

it indexes and writes blazing fast and if left to run in background to index stuff, you won't even notice its indexing (as opposed if you run it every time anew)

 

---

 

Comparison of the two:

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

 

- Everything runs blazing fast on slower older machines but uses indexer and database file

 

- UltraSearch runs faster on DualCore CPU's than on SingleCore ones but doesn't use indexer or any file writing/reading at all, it reads directly from MFT

 

 

 

in any case they both kick the the living shit out of crap search MS is providing

and they are both free and portable

 

 

 

??/??/2011

I bet most of people already know this picture:

 

 

 

well I don't know about you but I am sick of Assbook and Dildder and every FUCKING IDIOT that puts those stupid ass links to them and showing off how they can "be in contact"

 

I've got 5 words for you assclowns:

 

FUCK YOU !

 

and Hosts File:

 

Hosts file is usualy located in %WINDIR%\System32\Drivers\etc folder.

As it is just file with no extension, by default OS doesn't provide any program to open it with...

so choose notepad (or any other text editor).

 

This file was used to map hostnames to IP addresses but is often used for other purposes, most popular one is to block Adverts or websites, greatness of this is that no 3rd party app is needed to block unwanted web content nor does this file present any high (if any) resource usage.

 

How does it work:

 

anything behind this number: 127.0.0.1

is re-linked to local domain (which is IP 127.0.0.1), thus nothing

so any website entered behind that number, and later accessed via web browser is linked to local nothing...

in short - it is blocked

 

*do have in mind, that if you edit this file while your browser is running, then the changes will NOT
come in effect until you close the browser and re-open it.

 

therefore to all you Assbook and Dildder morons:

 

 

 

 

 

??/??/2011

Unfortunately this article deserved its own page for its big image content

as it shows why so called Windows "7" sucks so much

 

clicky click

 

 

 

??/??/2011

When m$ deployed security update 908531 for Windows 2000, XP and 2003, the "update" installed infamous verclsid.exe process

 

Quoted M$:

"Security update 908531 (MS06-015) installs a new program, Verclsid.exe.

The Verclsid.exe program validates shell extensions before they are instantiated by the Windows shell or by Windows Explorer."

 

problem starts, atleast it is most noticable if you open a folder with bunch of pictures (over 200) that are HQ or HD and view is set to thumbnails (you can notice this also if you go in system32 folder and scroll up/down but lag is not so huge since not much data is to "get")

 

the OS invokes verclsid.exe that does god knows what... and hogs down PC with huge lag, making any work impossible until this process stops doing whatever it does...

(depends how many files you have)

 

now one would hope that when checking/caching is complete, it would not repeat...
well it does over and over again, and killing it via taskmanager/cmd taskkill only starts it again...

and i got sick of it yesterday (actualy 1 year ago i formated disk in hope this was a bug)

 

so asking about this on another forum I got nice reply from someone saying to replace original verclsid.exe with "dummy" file, a Dud (click)

 

so I did... on Win XP SP3 and all problems are gone... OS still calls verclsid.exe (which is actualy dummy file renamed) but since file does nothing and has instant unload, in my case the image thumbnails are NOT reloaded again and I can freely browse any folder with huge amount of files or images and no lag is present.

 

If you're wondering WHY was this verclsid.exe deployed with hotfix in first place if it is so devastating...
well it was part of security patch, and both XP SP2 and SP3 have it, Server 2003 would have it in SP2
(by the year of deployement which was in 2006)

 

anyway... if XP RTM and SP1 worked just fine without it, then I guess SP2 and SP3 will countinue to work fine without it too...

 

 

 

01/12/2009

So lets whine a bit about Windows DLL hell...
Since its existance in 16bit world, Microslop Winblows had problem with DLL hell...

 

What is it ?
Some programmer makes an App in specific language environment, lets say in Visual Basic 6, and normaly App doesn't include any additional libraries with it nor does Windows Update, so you run an App and you get Error that bunch of DLL's is missing

 

in other words for each stupid environment update you have to download new runtimes because older wont apply for specific App written in never version

 

same goes for common windows controls - oh fuck everyone experienced this or it wasn't correct version, or it was missing or it wasn't registered with regsvr at all

 

so who the fuck can keep track with bunch of fucking updated versions?
when i was on Win98/ME I always made a CD compilation with bunch of runtimes from most known versions...
it just sucked...

 

XP had dllcache in i386 folder, which was basicaly a backup of system dll's and that is all there is...

 

but with VISTA it all changed, people came across with infamous WinSxS also known as Side by Side, sure XP had this too but it wasn't used correctly (if you can call it correctly)

 

WinSxS is basicaly a folder with huge amount of dll's, some stupid assemblies and whatnot...
and with many different versions of the same so in theory there was no need for installing new runtimes as OS already had them...

 

but instead to solve DLL hell it made it into more than just hell, the stupidity of m$ programers led to backup of any installed app and their runtimes and even if user was to uninstall an app or bunch of app's, the backups stayed so suddenly the SxS folder started to get bigger and bigger, instead being ~500 MB big it went to space eating like Pac-man on New-Years party -_- ... fucking folder starts to eat up to 25 GB of space...

 

when people started to complain, you got 2 answers...

 

1. they (backup files) are not realy all there, they are just virtual hard-links to original files

    so increased space report is only illusion (yea right)

2. hard drives are cheap now

 

and best is, Windows 7 has this bullshit too and I doubt Win 8 will be shipped with better thing

 

-

 

heres one funny cut from one forum that made me laugh (last comment)

 

 

 

 

 

09/11/09

I'm not gonna cover all here since theres already planned special section for Longhorn, as you see theres a planned link on the page menu...

 

Anyways if you browse the forums or some IT blogs you may quite often come across with something called Microsoft Longhorn or just Longhorn...

 

is it some secret Microsoft project ?
is it an OS ?

 

 

close...

Microsoft Windows "Codename Longhorn", was an OS, to be more specific it was an Alpha stage OS of what we know today as Vista, but unlike any other MS OS in its Development stage, Longhorn had almost NOTHING to do with what Vista is now...

 

Longhorn introduced following notable features altho many of them were locked/hidden and had to be accesed by hacking:

 

- New type of taskbar (different button layout, combinable with sidebar)

- Sidebar
- Doubledeck taskbar (read #1)

- Phodeo:

      3D file view (any type of file was put in 3D space, some even rendered to 3D look)

      Carousel file view

      Panorama (timeline) file view

- Pivot: folders that agregated file types (music, pictures...) from ALL partitions - something like shortcuts to such file types in 1 folder which saves you from searching all over the disks, later only seen in Beta 1 of Vista (bld 5112) as Virtual folders and later removed until Windows 7 (yep Vista didn't have this among many Longhorn features)

- Windows Future Storage aka WinFS (database type of file storage)

- Desktop Composition Engine (DCE) now known as Desktop Window Manager aka DWM

- various visual effects (Spining windows, Transparent window borders, Half transparent windows, objects in 3D space known as Aero Stars or Squares , Aurora animated Panels)

- improved security over 2000 and XP SP1 (later ported to XP SP2)

- more flexible and usable UI

 

and as oposed to Vista, it had different "vision"...

but it failed and project had to be restarted and built from anew Server 2003 SP1 (5.2 kernel)

 

why it failed ?
main reason above all others, is because MS developed Longhorn and in same time they developed .NET framework from which Longhorn was mainly made of (shell was)...
(+ most of the team was put back to work on XP SP2 security due to Blaster and Sasser which led to more delays of Longhorn development...)

 

so code was very unstable, explorer had huge memory leaks, half of features did not work well, OS crashed every now and then, they had so many builds and every some build had something different/new inside...

 

it was just a mess...

Even Jim Allchin in confidential internal memo that was sent to Steve Ballmer and Bill Gates admited Longhorn was a pig and that he favours OSX

-

I do have in plan to make Longhorn seperate page content so people can see some things, since picture worth thousand words :)

 

 

Happy Halloween !

 

now get the hell out of here !

 

 

 

01/11/09

In my Windows 7 nagging I wrote I am going to write why Superfetch sux...
So lets start:

 

Idea behind Prefetch (originaly made for Longhorn but ported to XP SP2) was to boot OS faster, to load most used apps faster and to install hotfixes without reboot (lol they realy improved this - NOT -)...

 

But as always there is difference between theory and practice, Prefetch works in a way that it stores in specific hidden system folder a list of most used apps by user and then it "loads the apps in RAM" thus "making the execution/use faster". All this is bullshit, in reality it works like this: user uses some apps, prefetcher stores (makes)

the list of app names and their location on hard disk/partition and then they should be faster executed/accessable, but they are NOT ! Why ?

Because:

1. MFT already stores location of any file (not just apps)
2. Hard Disk has to: SEEK --> MFT --> SEEK FOR PREFETCH LIST --> SEEK APPS
    in other words, seeking for those apps is twice longer
3. If your hard disk/partition is fragmented or improperly defragmented
    prefetching takes long ass time

4. Prefetch takes some time to "learn" what you use most (read few weeks)

 

 

Biggest fail of this is if your Task Scheduler service is disabled (and mine always is since some stupid programs always force in daily or weekly update or maintaince or whatever) the Prefetcher itself wont work properly if at all... lol

 

That was about Application Prefetch, the Boot prefetch indeed works and makes your OS boot up 5-10 secs faster (*g* what an improvement).

 

As for Windows 7 and its glorious 30% RAM Prefetching usage...
What a load of crap... I can't stand to read some bunch of stupid kids pretending they are IT professionals and talking how this is good thing, how FINALY using your FULL potential of RAM is great and is no more unused...

Well for your information YOU STUPID BUNCH OF MORONS, ask yourself:
if OS isn't so BLOATED why does it need a damn pre-load of anything ?

 

Got you there !

 

Face it, XP SP3 consumes 800-900 MB Hard Disk space (without crap of .NET)

Windows 7 consumes from 6 and over 7 GB Hard Disk space (Home - Enterprise/Ultimate) and that is pure OS,
so now add in bunch of Apps user installed and if dumbass uses only 1 partition for everything including multimedia with programs/games

 

two words: IT SUCKS

 

naturaly, with SSD drives this isn't an issue anymore.... (speed and fragmentation wise) then again they are still not cheap for home use...

 

 

 

28/10/09