Lepenye Tamás előadásai

Lepi a múlt héten tartott az Inetpub tagoknak előadást és éles rendszeren bemutatót a clusterekről. Egy bosszantó software hiba miatt – Lepi szerint “Úgy látom, hogy a szoftver kissé bugos.” – kevésbé finom lélek – pl. én – a Gödöllei féle nagyszótárból, vagy a Magyar Tengerész Káromkodások c. kiadványokból ordítottam volna idézeteket.

Lepi 3 elődásának ppt formátumú vázlatai a http://www.box.net/public/0ykdcma1vb#main helyen láthatóak.

Mindenki sajnálhatja, hogy nincs hang. Mi – jelenlévők – előadását lenyűgözve hallgattuk. Köztudott belepofázásunkat és vitázó hajlamunkat nem a mikrofon jelenléte, hanem az előadás magas színvonala tartotta kordában.

I’m rocking out to Alabama Song by The Doors from the album Westbury Music Fair,NY 04-1968

Internet Explorer 7 Release Candidate 1 in standalone mode

Jon Galloway írta IE7 Standalone Launcher updated for RC1 tárgyú bejegyzésében, hogy a http://tredosoft.com/IE7_standalone oldalon részletesen leírja Junfeng Zhang, hogyan is működik e dolog:

Why run Internet Explorer 7 Release Candidate 1 in standalone mode?

Maybe you are a web developer who wants to test his/her designs on IE7 but want to keep Internet Explorer 6 until Microsoft releases the final version. It’s basically a way of running IE7 and IE6 at the same time without having to overwrite the previous version.

What does the program do?

“IE7s.exe” will create a .exe.local file (if you’re interested, read Junfeng Zhang’s blog post for more information about the .local file). After that it will add values to more than a thousand registry keys in your Windows Registry. Internet Explorer 7 should start then. 10 seconds later the program will perform a cleanup, remove all the registry keys and close itself. It is OK to run multiple instances at once.

A dolog lényege Junfeng Zhang’s blog post-jában van:

DotLocal (.local) Dll Redirection

If you are developing software on Microsoft Windows platform, you probably have heard of the term “Dll Hell”.

“Dll Hell” happens when two applications install two incompatible versions of a shared dll. Since there is no versioning control for dll in Windows, the second copy may overwrite the first copy. As a result, the first application will not function any more.

Since LoadLibrary will search the application directory first, among other things, a workaround for the “Dll Hell” is to carry the “shared” dll with the application, which effectively makes the “shared” dll private.

But there is another kind of “Dll Hell” which can not be easily worked around. And this is COM.

If two incompatible versions of a COM server is installed and registered, even the two COM servers may reside physically in different location, there is only one place to register the COM server. Hence only the latest registered COM server will be activated. This is essentially another manifest of the “Dll Hell” problem.

To workaround this problem, a “Dll redirection” mechanism is introduced in Windows 2000.

For an application foo.exe, if there is a file foo.exe.local exists, Windows will first look at foo.exe’s application directory, before start the regular dll search. To mitigate the COM problem, the redirection applies both to full path dll loading, as well as partial name loading.

In Windows XP and Windows Server 2003, the behavior of DotLocal(.local) is altered a little bit. If foo.exe.local is a file, Windows will keep the same behavior as Windows 2000. But if foo.exe.local is a directory, Windows will search foo.exe.local directory for the dll, instead of the application directory.

In Windows XP and above, Windows (via fusion team) introduced a new side by side programming model for application isolation. This model essentially is the same model introduced in .Net framework (with no surprise, as both models are designed by the same team, with small variances based on the need of the specific product). In Windows the metadata is stored in a XML file (typically called a manifest file), as opposite to the assembly binary in .Net framework.

Since the side by side isolation model is a logic evolution of the DotLocal(.local) dll redirect, in Windows XP and Windows Server 2003, when there is an application manifest (foo.exe.manifest, or a Win32 resource of ID RT_MANIFEST, Type 1), the DotLocal dll redirection is disabled.

It turns out the DotLocal(.local) dll redirection has a huge value in private testing. When developing a new version of the COM server, you don’t really want to mess up with the one in system. If you can redirect the dll to a private version for a set of specified applications, and let other applications use the system one, it will be the best of all the world. And DotLocal(.local) provides exactly that, with the exception that if the application has a manifest, DotLocal(.local) dll redirect is disabled.

Így megoldódott a végleges IE6 és az IE7 RC1 egymás mellett futásának korrekt lehetősége. Nincs “Dll Hell”.

A fejlesztők örülhetnek.

(Már aki nem tudta magának ezt megcsinálni.

Lásd:”After that it will add values to more than a thousand registry keys in your Windows Registry.”

Nos ezek vannak döntő többségben.)

I’m rocking out to Hello, I Love You by The Doors from the album Waiting For The Sun

Currently listening Plugin for WLW

Currently Listening ver 1.5 out now.

Yep, updating again today. I just felt like adding Winamp support, so it’s been added. There are some caveats to this though. I basically use the same technique that everyone (I’m assuming) else uses to try and get the Winamp information. Unfortunately that means no Album name data. I know it sucks but really you should upgrade your media player anyway, Winamp is so 1990’s.

Download the fresh basket of goodness.

Az eredmény:

I’m rocking out to God Was Never On Your Side by Motörhead from the album Kiss Of Death

Security Engineering Book in Digital Form

Richard Bejtlich ajánlása:

I just read at Light Blue Touchpaper that one of my top ten books of the past ten years is now available online. Now you have no excuse not to read this incredible book (reviewed here).
It seems funny that the blog commenters asking about making a single .pdf have not heard of Pdftk.
Thanks to jimmythegeek for getting this news to me faster than my Bloglines feed.


http://taosecurity.blogspot.com/2006/08/security-engineering-book-in-digital.html

FW: ALERT! Centrino users must update or get owned!

ALL PCs with the Centrino logo or any computer using an Intel Wireless Ethernet adapter must update their PROSet software and drivers found here. An update was released earlier this month but that version was found to leak memory and cause PC slowdown. It is absolutely critical for IT departments and individual users to update their PROSet software and drivers. Get tips and links for the update here!


http://blogs.zdnet.com/Ou/?p=306

Server Virtualisation

Ron Oglesby írt egy érdekes cikket Brian Madden oldalán.

Ebben szó esik a hardware virtualizációról, de nem történik említés az Intel által kidolgozott EFI szabványról.

Erről írtam korábban:

More Power to Firmware, majd
FW: Linux beats Windows to Intel iMac,
Intel Macs May Boot Windows XP After All,

:-(( UEFI – Microsoft Shuts Windows on New PC Firmware


A legutóbbi hivatkozásomban írt cikkből egy most is fontosnak tartott dolgot szeretnék kiemelni:

UEFI, ironically, supports the Microsoft plan. The firmware was designed to work with both 32-bit and 64-bit operating systems and to be backward-compatible with OSes designed to work with BIOS—on the desktop, the bulk of the OSes which will be used are 32-bits—using a special Software Compatibility Module to emulate BIOS functions.

PointerToo many versions of Vista? Read more here.

Thus, UEFI Forum members, which include Microsoft, Intel, Advanced Micro Devices, Dell, Hewlett-Packard and BIOS makers American Megatrends, Insyde Technologies and Phoenix Technologies, agreed to focus on delivering 64-bit UEFI implementations in PCs, using compatibility modules as a bridge to non-EFI OSes, a person familiar with the matter said.

Véleményem szerint nem új fogalmakat kéne bevezetni, hanem a már elfogadott szabványok szerint kell dolgozni. A virtualizáció és sok egyéb dolog könnyebben mehetne.

Load Windows Live Writer

A WLW gyors elérése fontos, ezért soulposition [at_sign] msn dizzot com kitalálta a  Live Writer System Tray kisalkalmazást. Nos ez nem gyors elérés.

Helyette javaslom az RBTray használatát. A leírásból:

You can download RBTray 3.2 from this link

RBTray 3.2
GNUware
(Distributed under terms of GNU General Public License – see below)
Copyright (C) 1999-2006 by Nikolay Redko
Allows you to minimize windows in the tray area on taskbar by clicking right mouse button on the window’s minimize/close box or from system menu or from window’s system menu (+). Allows to set any window in “Always on top” state from window’s system menu.

Más kérdés, hogy a WLW betöltése is lehetne eleve gyorsabb.

Az RBTray általánosan alkalmazható.

Kiegészítés (2006.08.28, 13:19):

LiveWriter OnScreen jobb, mint a Live Writer System Tray, de a betöltés sebességén nem javít(hat).

LiveWriter OnScreen is free. Free as in free beer, not as in freedom.

Its free today, free tomorrow and free forever.

You need to install LiveWriter before you install LiveWriter OnScreen.

see the help for details.

218660434_c2c1e93a87

 Néhány elem nem installálódik,

LiveWriterOnscreen1LiveWriterOnscreen2

ergo nem is megy a My Feeds-ből a WLW-be insert. A képeket meg mindig új post-ba akarja illeszteni. A Spot viszont jó, ha nincs Screen Capture 2 .

Egy jó elképzelés, módosítani és aktualizálni kéne az IE7 RC1-re is.

Windows Vista Pre-RC1 (5536) Guide

Az MSTechToday weblogjában láttam ezt a hivatkozást egy tweak guide-ra, innen:

Windows Vista Pre-RC1 (5536) Guide

Written by Chris Holmes, Dena Reiter and Kristan Kenney

http://www.longhornblogs.com

Introduction And Overview

Windows Vista Build 5536 has been released to beta testers. This is the first build that truly shows what Windows Vista is capable of, and shows a great deal of improvement over previous builds. It is also “Pre-RC 1”, meaning that it is a preview of what we can expect in Windows Vista Release Candidate 1 (RC1).

This build introduces a lot of performance fixes and offers greater stability overall. The installation process is much quicker on most machines, and some people have even gotten the much desired 15-minute installation times.

As this build is a preview of Release Candidate 1, it is stable and usable on a day-to-day basis for most people. However, there are some things that you may find negatively impacts your experience with Windows Vista, and this guide outlines some of these things as well as how to remedy these issues.

Egyes javaslatok (disable UAC), nyilván akkor hasznosak, ha végleges verzióról van szó és power user-ek vagyunk. Esetleg, ha mást akarunk kipróbálni.

Nyilván nem azért lát az ITember (nem tudom, hogy az előember-ember-utóember sorban hol a helye?) egy beharangozottan biztonságosabb, stabilabb oprendszer használatához, hogy ezen előnyöket hirtelen negligálja.

Ettől függetlenül hasznos útmutató.