Martin Zugec

Same like Zxian, however I am using control command... For common stuff I am using shortcuts (like winkey + Break etc...)

Absolutely agree Two years ago I changed my mind and began (however slowly) to buy software I am using... However I am using pirated versions if I want just to try something. If I find it useful, I will buy it

Hmmm, I must say I am FOR piracy... I would never use pirated products for commercial use, but it is something different for home use. Someone on conference spoke about creating new kind of competition for companies. Piracy created competition for company, so they must keep their prizes low, if they want to get customers. In fact you can see this on New Zealand - it is country with lowest piracy rating, but highest prizes for software... Another example is eastern europeans regions, asia or india, where is high rating of piracy - you can see that companies give them low prizes. So what I wanted to say is "invisible hand of market" is acting here, too. You MUST have piracy for software to evolve and spread.

I am proudly serving my masters BTW If you are intrested in batches, sometimes you can find something useful in my blog.

I use it like For /f "usebackq delims==. tokens=1-3" %%i IN (`set strArrayName`) DO Echo Array field number %%j have value %%k

For me personally, if I need to tweak something, I run RegMon/FileMon from Sysinternals or InstallRite, change settings and see where that change applied...

echo %strArrayName.1% will show first entry in array... Variable %strArrayNumber% shows total number of array entries

I am not big fan of games, this this one is great http://www.etc.cmu.edu/projects/experiment...ooUnlimited.exe

Mine is similar Set strArrayNumber=0 For /f "usebackq" %%i IN (`type test.txt`) DO ( Set strArrayValue=%%i call:functionArray ) Goto :EOF :functionArray set /a strArrayNumber=%strArrayNumber% + 1 set strArrayName.%strArrayNumber%=%strArrayValue% Goto :EOF

2bledd: Yes, they work like this. Every beta project is with documentation, product forums. About blogs - in my opinion MS have best implemented blog for their employees/developers. Once I subscribed to developers bloglist and I received unmanageable amount of posts every day. Now I use RSS only for my favourite guys, like Michael Howards, Valery Pryamikov and few others.

For streaming purposes it is good to "tweak" NTFS - disable LastAccess stamp, Indexing etc...

2Jamey: I must say I am glad you posted is with comment "This is not a solution to your problem but an alternative suggestion.". Quite unusual these days 2notquiteanewbie: MS is based on objects, that is why I dont like removing system components - you wont be able to find out where is the problem later. I would recommend you two steps: 1.) run sfc /scannow - it should restore system components. 2.) run repair in Outlook - it will restore KeyPath objects from installation. If any OE object is set as keypath with newer version, it will restore him. You can find restore in Help - Detect and repair

You can create something called "Junction points" aka "symbolic links". The problem is there are three limitations: a.) these two folders must be on same partition b.) it is NTFS feature c.) it works only on directories, not files. So your folder B will be subdirectory in A folder For more informations: http://en.wikipedia.org/wiki/NTFS_junction_point For utilities: http://www.sysinternals.com, utility called Junction

For this purposes I use WBAT - it will boot to menu, where one of options is Standart (it will be fully automatic, taking configuration from network), the second is Special, where you will see settings on one screen and you can change what you want... So you use values like **REPLACE_USER** in winnt.sif and then search&replace this value

Use Windows Memory Diagnostic from Online Crash Analysis centre - http://oca.microsoft.com/en/mtinst.exe

This is because you got Automatically restart in Control Panel - System - Advanced - Run and recovery (something like this). Please attach your dmp file for analysis, I will post to you what is your problem.

This behavior is typical in few scenarios - - user profiles with same name in domain and local machine. - user profiles with damaged profiles. The usual workaround is modifying ProfileList in registry

You mean junction points?

Yep, cabarc from Microsoft

The best combination is: XP SP2 (VERY important) MS AntiSpyware/Sunbelt CounterSpy Automatic Updates (Shell.Applications etc.) Least privilege - http://martinzugec.blogdrive.com/archive/26.html

Well, "Send" from other Office applications is acting differently because of MAPI. Could you post your win.ini file content? There should be MAPI location... For example [Mail] MAPI=1 CMC=1 CMCDLLNAME32=mapi32.dll CMCDLLNAME=mapi.dll MAPIX=1 MAPIXVER=1.0.0.1 OLEMessaging=1

Well, talking about beta... MS is planning to have much "wider" beta programs, so there will also be public betas available (similar to MS Antispyware or VS Express today). If you go to windows update, you may find in your option ability to include betas (default in unchecked)

From Microsoft: Q. Why are 2 more revisions released? A. On 5/17, Windows Installer 3.1 package was released to "Windows Update V5" as a Critical Update. All updates released to "Windows Update V5" are automatically published to WSUS RC environment. This resulted in revision 102 of "Microsoft Windows Installer 3.1" ( b166a6a9-398b-4c81-b8db-2043cf0672a1 ) update. On WSUS RC, this update needs to be marked as WSUS update (or mandatory update) and hence revision 103 was published to make it WSUS update. These re-release could not be avoided as WSUS RC is still not a final released product. Once the product is released, such re-releases will not happen. Hence update b166a6a9-398b-4c81-b8db-2043cf0672a1, revision 103 is the latest release of the update. This is the only revision that needs to be approved. Q. After the re-release, will the clients which already have the update install it again? A. No. The Windows Installer binaries did not change across these revisions. If a client had installed one revision of the update, then the new revision will not be installed. File version of msi.dll installed by the update is 3.1.4000.2435. If the client machine with applicable OS/service pack has msi.dll < 3.1.4000.2435, then this update will be offered, otherwise it will not be offered. Q. What are the applicable platforms for this update A. Windows 2000 SP3, SP4 Windows XP SP1, SP2 Windows Server 2003 Gold (only x86 platforms) Q. Are any more re-releases of "Windows Installer 3.1" expected? A. As of now, there are no more re-releases expected to WSUS RC. But please be aware that WSUS is still not a released product and hence there may be some more changes expected based on the issues being reported. We will make efforts to communicate any re-releases in future.

It is, second revision of 3.1 fixes some problems, but the most interesting point is that every new version of WI brings new functionality. WI 3 brings a LOT of stuff for patching/updating, so it looks like many companies will use it.

Hmmm, there was ability to use Virtual registry emulation in ACT... But I dont remember how did it work (e.g. redirection of 9x keys, or creating whole registry hive...). Just an idea where to look for.