Tag: microsoft

Copy To… и Move To… в Windows 7

Copy To… и Move To… в Windows 7

Прочетох за това в Tech Republic Dojo. Малък и бърз хак, който дава следните две полезни менюта в десния бутон на Windows Explorer:

CopyTo_MoveTo_WinExpl

На времето имаше специален power tool, който правеше това. Сега това става лесно с един хак на Windows Registry:

  1. Идете в Windows Registry върху следния ключ: HKEY_CLASSES_ROOT\AllFilesystemObjects\shellex\ContextMenuHandlers
  2. Вътре в него направете два ключа със следното съдържание:
    1. За “Copy To Folder…” името на ключа трябва да е “{C2FBB630-2971-11D1-A18C-00C04FD75D13}
    2. За “Move To Folder…” името на ключа трябва да е “{C2FBB631-2971-11D1-A18C-00C04FD75D13}

Не знам дали изисква рестарт, май не, но не съм 100% сигурен.

И не забравяйте: всяко бърникане из Windows Registry може да ви скапе тотално и невъзвратимо компютъра. Ако не знаете какво правите и не сте готови сами да поемете този риск, недейте след това обвинява автора на този блог Smile.

Панорама от с.Проглед

Панорама от с.Проглед

За Гергьовден с Веси минахме към Проглед. Всъщност, аз минах от там, Веси се присъедини по-късно, защото тя беше на работа (при тях българските празници са важни, ама датските са по-важни).

Албумче от Проглед още не съм качил, не съм сигурен дали ще го направя. Качих обаче тази панорамка (ако използвате RSS-четец, най-вероятно няма да видите нищо, отворете страницата от сайта!):

Панорамата е “съшита” от 9 изображения, които нащраках почти като на шега. Исках да пробвам Microsoft ICE (още известен като HDView). Това е един продукт на Microsoft Research, с който много лесно може да се създаде панорамно изображение от множество снимки, снимани с презастъпване. Оригиналните снимки, от които създадох панорамата, заедно с JPG от самата панорама може да свалите от тук (62МБ архив!).

Изображенията са малко “мъгливи”, но това е защото никак не се старах, като снимах. Не е от продукта, а си е класическият мой “motion blur” – моето фотографско проклятие. Веси снима много по-чисто от мен, защото ръчичките ѝ са много по-стабилни от моите, въпреки тежкия апарат.

Също “избистрянето” на изображенията е малко бавно, изглежда от хостинга ми. Като правите Zoom, просто изчакайте малко (освен ако не правите най-дълбокия Zoom, там си е гореспоменатия motion blur).

С HD View (Microsoft Image Composite Editor, или още Microsoft ICE) се работи потресаващо лесно. Снимате, имайки впредвид това, че ще правите панорама, след това сваляте снимките от апарата. След като имате снимките, инсталирате Microsoft ICE (той е безплатен!), слде което просто завлачвате и пускате снимките и го оставяте на “шие”. Накрая за вас оставя да прегледате какво е съшил и да го запазите на диска си – или като JPG, или директно като DeepZoom panorama.

Допълнително може да изберете да качите на PhotoSynth вашето произведение. Аз имам качен там един Synth от Барса, но него го направих, използвайки PhotoSynth, а не HD View. А и той е от повече от 200 изображения, така че…

Най-яка е функцията “разпознаване на дълбочина”. Не съм я пробвал още, но ако се съди по PhotoSynth, тя трябва да разпознае кои снимки са част от детайла, и да ви предложи още по-дълбока перспектива там. Засега съм използвал HDView само за общи (“линейни”) панорами, някой ден обаче ще си поиграя да нащракам някое пано с 200+ снимки и ще пробвам и дълбочинно как ще са нещата.

Разбира се, продуктът е произведение на Microsoft и като такъв генерира интерактивните панорами в Silverlight. Това обаче, предвид тенденциите и проблемите, които други подобни технологии показват напоследък, е само плюс. С нетърпение чакам кога ще може това да го направят в HTML5. Някой ден, някой ден…

Прототип на моя бъдещ е-четец

Прототип на моя бъдещ е-четец

Днес го видях в kaldata.com:

Няма да замени e-book reader-а ми, но устройството е брилянтно като замисъл. Ще мине известно време, докато стане масово, ясно е, но само помислете за удобството и переспективите!

ASUS EEE 1000H от Laptop.bg

ASUS EEE 1000H от Laptop.bg

Днес се оплаках, че имам грижи с изборът на Netbook. Точно се бях спрял на един, и не  успявах да се свържа с магазинът. Малко след оплакването обаче веднага се намериха приятели, и ето че на скайпът влязохме във връзка.

Големият проблем, който исках да изясня беше дали Windows 7 RC ще се инсталира и ще  работи на хардуера на мъничето. Не ме притесняваше толкова скоростта (Windows 7 е предвиден да работи на нетбук), а съвместимостта на ниво драйвери. Знае се, че 7-цата е с нов драйверен модел.  А и най-сериозния проблем ми се яви това, че Сашо отрече съвместимостта, а след като специалист от негов ранг не може да се справи, значи работата може да се окаже неприятна.

За мое голямо удовлетворение момчетата и момичетата от Laptop.bg се оказаха изключително отзивчиви. Само след някакви 15тина минути разговор вече имах уговорена среща надвечер в офиса на фирмата. От мен – инсталационното DVD на Windows 7 RC, а от тях – чисто новичък ASUS EEE 1000H с 1GB RAM и 160GB твърд диск. SSD не беше задължително, още повече че то не е и фактор при инсталацията и използването на 7цата – ако тръгне с твърд диск, ще работи и с SSD след време.

В уговорения час бях там. Всичко беше готово, така че седнах и се захванах за работа. Очаквах проблеми. Затова не мога да ви опиша с какво удоволствие след по-малко от час имах работеща операционна система Windows 7 RC с всички драйвери (без ACPIто, което доинсталирах вкъщи). Мъничкото нетбуче се държеше перфектно, изкара 2.0 performance index с единия си гигабайт памет. Инсталираната 7-ца беше заела около 470MB, оставяйки половината памет свободна.

След като експериментът беше много по-успешен от очакваното, с голям кеф си взех този нетбук и 2ГБ рам. Сега дописвам този материал с малката клавиатура. Малко имам зор с нея, но трябва да свиквам.

Накрая искам да кажа няколко неща за хората от laptop.bg. Да им благодаря за толерантността и търпението, нехарактерни (за жалост) по нашите ширини. Да им пожелая много успех, който обаче да не ги кара да си променят отношениието към клиентите. Laptop.bg, благодаря ви!

Visual Studio Debug Error: Unable to Start Debugging

Visual Studio Debug Error: Unable to Start Debugging

These days I was striking with very annoying issue. Each time when I try to start debugging any Windows solution, my Visual Studio 2008 Professional was giving me the annoying error “Error while trying to run project: Unable to start debugging. The system cannot find the file specified”:

Visual Studio Debugging Error

To my impression, this started happening after installing and reviewing (and then uninstalling) one of the internal Technical Previews of Visual Studio 2010 (and .NET framework 4.0). After that, even reinstalling the frameword and Visual Studio 2008 did not help – the error was (and still is) showing each time after I do Debug. The application was running fine when started with Run.

Web searches showed nothing.

I was almost ready to give up (and reinstall completely my Windows 7 RC!) when a good friend of mine (and brilliant developer himself) advised me to try researching the issue with Process Monitor.

The Process Monitor showed me that VS is trying to create a lot of stuff in places, where it should not (like Program files, for example). Weird, because it’s with last current SP, it should respect that. Obviously something screwed up the logic and now it was doing the wrong things again.

At that point I “remembered” that maybe “Run as administrator” might help. It was helping a lot before releasing of the SP, which made VS compatible with Vista.

I tried “Run as administrator” and… suddenly all went fine. I was able to debug.

Since this workaround resolves my current problem (and I’m almost sure the whole thing is because of screw up from beta version), I will not research more. I wrote this note in case someone strikes with similar issue and (the same as me) forgets to try the “Run as administrator” magic 🙂 .

IE8 RTM

IE8 RTM

IE8 logo Интересен ден е днес. Internet Explorer 8 е готов. Всеки може да го свали веднага от неговата официална страница.

Като казах всеки… излъгах. Ако сте с Windows 7 Beta, ще трябва да почакате. Версия за Windows 7 beta обещават да има, но по-късно и доставена през Windows Update.

Подхождам със смесени чувства засега. IE8 определено е качествен скок. Според мен разликите са повече дори отколкото бяха между 7ма и 6та версия. Но тепърва хората ще кажат успех ли ще бъде ИЕ8 или не.

Редица проучвания сочат IE8 наравно с Firefox 3 откъм средна производителност. Някои фаворизират IE, други – FF. Но едно е ясно, IE8 определено е скок в производителността, а предвид колко много бизнес приложения разчитат на IE, като цяло тази версия ще подобри значително опитът на хората, ползващи IE.

Яд ме е, че не мога да инвестирам достатъчно време в разучаването на IE8 add-on модела. Казват, че бих читав. Но като няма време – няма.

Засега оставам да чакам с нетърпение обещания update към IE8 RTM за потребителите на Windows 7. След това – ще видим, ще пишем и т.н.

Infonotary електронни подписи и под Windows 7

Infonotary електронни подписи и под Windows 7

Едно от последните изпитания, които новата операционна система трябваше да мине, за да мога да бъда 100% “както преди”, беше инсталацията на драйверите и софтуерът, който обслужва е-подписите на InfoNotary.

За целта използвах собствения ми архив с драйвери и софтуер, вместо публичните такива. Направих това, понеже след комуникация с InfoNotary навремето получих не-поддържана версия на драйвера, която обаче “виртуализира” наличието на смарт-карта, което прави осъществимо “hot-plug” на четецът и смарт-картата.

Инсталацията мина изключително безболезнено. За да подкарам подписът, инсталирах следните компоненти и драйвери:

  1. Поставяне на четецът и картата и оставяне на Windows 7 да си открие и инсталира драйверите, които идват готови
  2. Инсталиране на Драйвер CardMan3x21_V1_1_2_4.exe
  3. Инсталиране на Hot Plug Enabler for CardMan 6121 V1_0_3_0. Както посочват по-долу в коментарите, това чудо по някаква причина не работи след Win7 beta
  4. Инсталиране на Siemens CardOS (x32) драйверите

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

Благодаря много на Zdravko Totkov, който изясни проблем с материала след Windows 7 beta.

Windows 7 SQM Issue During Visual Studio 2008 Setup

Windows 7 SQM Issue During Visual Studio 2008 Setup

It came time for another Windows 7 posting. It was very close to be a negative posting, sharing some Installer 5 pains. However, with the help of Windows 7 Core teams, that got resolved, so I’d like to share with you my experience and solution, since it could be of someone else’s help.

It all started when I tried to install Visual Studio 2008 Professional. After Setup starts and passes the privilege elevation prompt, it did some verification, and during the parse of Installer data (as it seems to me), it came with this very nasty error message: “A problem has been encountered while leading the setup components. Cancelling setup".

clip_image002

Initially I thought this comes from my setup files, which somehow got corrupted. I retried from our products’ web (where the stuff is verified frequently), but the result was the same. Then I tried my own Visual Studio 2008 Professional installation DVD, and the result was the same. Then I tried evaluations of Visual Studio (C# Express), and the result was the same.

I almost given up. I have already found a similar issue in the Internet, without any encouraging advice.

My last resort was our internal resources. I sent a mail to a principal product manager, who already helped a couple of times, then I crossed my fingers and waited. I knew these guys are very busy, so getting an answer from them was only on their own good will and helpfulness.

Fortunately for me, Steve was extremely helpful again and forwarded my question to the right person. Just few hours later I had the answer in my inbox:

Please try renaming the following registry key:
HKLM\Software\Microsoft\SQMClient\Windows\DisabledSessions

Thanks, Peres! Once I did that, the issue disappeared.

From the registry I’m getting the impression this is an issue with the “Software Quality Management” module. But you can never be sure, of course. That’s why it’s beta software, ain’t it? I’m having the feeling that the error is not connected with Visual Studio setup, but may also be seen with other products’ setup. Also, I heard that in x64 it might not be resolved that easy.

Finally I’d like to share two very interesting links, which I found these days:

Happy hacking!

Windows 7 on Thinkpad T61p

Windows 7 on Thinkpad T61p

After installing Windows 7 beta on one of my home machines, I decided to go on and put it on my company T61p.

Since I had Bitlocker enabled, I decided to do clean install there too. I won’t go through details again, but in short: all went smooth and nice and about 30 min after I started I had working Windows 7.

I’d like to share here some tricks, which I had with my notebook. Win 7 is still a beta and I already encountered the first glitch I had. It was connected with my Thinkpad’s sound.

The issue was very annoying: I had my audio drivers installed and Windows was reporting them working OK. However, no sound was coming out from my speakers and/or headphones. You know the small green bar, which shows the level of the sound, right? That bar was also moving, indicating that sound should come out, but alas… silence!

I did some mad searches and nothing. Tried to replace the drivers (no need, by the way, out of the box drivers work just fine), and still nothing.

I phoned a colleague, who shared that he was experiencing the same issue, but “the sound magically came out after some time”. Good to hear, but still not an option.

So I stared to dig in the issue. After like 1h I already had it resolved.

The issue was simple (once you resolved it), and quite dumb 🙂 . The main problem comes from the fact that:

  • Thinkpad has additional volume buttons on the keyboard
  • We’re very used to them and we expect they work seamlessly every time
  • However, in Windows 7 beta regarding this issue the things are still.. beta!

As I already said, the issue was stupid. If you mute your audio with audio mute button, the audio gets muted, but Windows does not catch that event. So the icon remains visible as “non-muted” and Windows (software) does not care to “unmute” the audio, if you move the slider. No matter what do you. Restart does not help.

The only thing, which will help you in this case, is to press “volume up” or “volume down” buttons, the ones just right the “volume mute” button. Once you do that, the Thinkpad enables the sound back, and  then you’re just fine.

I’m sure that will be fixed for the RTM (I already reported the issue, and I’m sure it’s not only me). However, that was the first “struggle” with Win 7. I’m sure there will be more (it’s beta after all!), but that’s the risk of installing and using beta software 🙂 .

Happy hacking!

Windows 7 beta on Toshiba Qosmio F20

Windows 7 beta on Toshiba Qosmio F20

Today I finally obtained Windows 7 32 bit Beta bootable ISO (build 7000). Last night I tried to install the non-bootable bits, but it seems something went wrong when we were downloading them from the internal mirror, so I had to wait for today. Today I grabbed the ISO from a colleague and burned it. I was ready for the evening.

My plan was to install tonight  Windows 7 beta 32 bits on my old Toshiba Qosmio F20 notebook. We used this notebook in Denmark, it was Vessi’s primary work machine before she got her MacBook, and it also was my primary gaming machine after that 🙂 . Since the notebook is quite old-fashion, I wanted to see how the process would go.

I decided to go on clean install, wiping out the old (and very crap-full) setup.

The basic install went trouble-free and after 25 minutes I had working machine with Windows 7. On first look, I was missing these drivers:

  • Mass Storage Controller (WTF?)
  • Audio
  • Video
  • Network (Wireless). My wired network was correctly recognized and setup

I started looking for drivers. Simple search led me to the page at Drivers Collection, containing Toshiba Qosmio F20 Windows XP drivers.

First, of course, I needed the wireless driver. I had to use USB stick to transfer it (phew, no worries with the drivers for the stick, though). The wireless driver, of course, did not work “directly”. When I ran it, the setup asked for authorization, and after that just ended 🙂 . Hmmm, let’s try the compatibility wizard? The wizard asked me a couple of questions, I told him that it worked before on Windows XP, Next, Next and then it started and completed successfully. The driver, however, did not fire immediately, so I had to restart. After the restart, of course, it did not work as well :).

I saw that there’s another version of this driver, this time for Intel-based wireless adapters. I downloaded it, and retried the procedure. However, this time there was no setup, just selected “Update driver”, pointed to it and then it started doing “stuff” for about 5+ minutes. Then it timed out.

I retried the process. Same thing. After that I noticed there’s an installation file there (IMDinst) and decided to start it. The first run complained that it’s not supported on this operating system. But I was very pushy and selected after that “Use recommended settings”. Then it started and… timed out after the same amount of time as before, but did not show any error. The last resort was rebooting and retrying.

Suddenly, I noticed that… my wireless switch (the hardware one), is set to… OFF! Damn! DAMN! How stupid is that?

Turned on the wireless switch, and retried. The same thing!

Last resort: restart and retry! And nothing.

My next step was to find the “Intel ® PRO/Wireless network driver” on the net. That hit on the Intel site, which ended up to a 188MB (!!) zip file, containing all drivers (or so they claimed). I just had to download the whole thing (impressive 1221KB/sec speed, thanks Megalan!), and then move it with the same USB stick I was using before. Now I had the VISTA version of the driver as well, so I was a bit more hopeful.

This time I decided to restart and run the package on a clean system. Then I tried the standard setup. And it failed. Now I started to get a bit angry, because I was close to my very last resort: manual install.

This huge, 200MB structure, had 4 set of drivers: 32 bit, 64 bit for both Vista and XP. Since I had 32 bit OS, my choice was only for these. I tried with VISTA driver first and I got a failure! Almost desperate, I tried the XP driver and… oh miracle! It worked.

So, in short, if you want to install the Wireless drivers for this Toshiba Quosmio F20:

  1. Download the drivers from Intel, nothing else.
  2. Unpack the driver, you have to see a structure like X:\FV 12.2.0.0_Gen_SW_155293\XP\x32. There are the drivers.
  3. Manually update the driver. In Device Manager, right click the unknown network driver, and manually point to this directory. Otherwise it will chose the wrong driver and it won’t work.
  4. And, FFS, turn off your wireless adapter before that!

Now, since my wireless card was already working, it was time for the rest.

The first thing you should know after installing a new Windows setup is: Windows Update! Windows Update helps both for fixing critical security glitches and also it installs the latest drivers’ versions, even some which are not included on the distribution image.

However, before running Windows Update, I decided to install AVG Antivirus. This is great antivirus for personal use, since it’s free for home user and it provides excellent protection and features in the free package. The download and installation took me only like 2 minutes. No restart was necessary, so I was ready to continue with Windows Update.

Windows update showed 4 important updates, all of them were drivers, which I needed in order to get all yellow exclamation marks away from my Device Manager:

  • TV Tuner Driver
  • Video controller driver
  • Audio controller driver
  • (Optional) LAN controller driver (not the wireless), which was already working but obviously there was update available

All 4 drivers were successfully installed and after the restart I got it all working and in excellent shape.

Windows 7 boots up in about 25 seconds (from right after BIOS until the login prompt). This is pretty quick, but of course the system is not yet loaded with stuff. We’ll see how it will go after a couple of months usage.

Then I saw that I still have one yellow (!) in the Device manager. This was Mass Storage Device, most probably my card reader. I downloaded the CardBus driver from DriversCollection and tried it. It worked like a charm, but again with manual (Update Driver from Device Manager) installation, I even did not try the standard setup.

My conclusion is that Windows 7 Setup was the best Windows setup I’ve ever experienced in years. Yes, it had its challenges, but none of them were unavoidable. And considering this is the most modern Windows operating system on an old hardware, and considering that all hardware at the end is working as it should, I account this as a definitive success.

I’d encourage every one, who is computer geek, to give Windows 7 beta a try. It will be available soon on the main Windows 7 site. I do not remember when was the official release date for it, but it should be really soon.

Happy hacking!

Theme: Overlay by Kaira Extra Text