tag:blogger.com,1999:blog-8643966532123751496.comments2022-11-30T11:41:51.074+01:00I work without regaining consciousnessUnknownnoreply@blogger.comBlogger33125tag:blogger.com,1999:blog-8643966532123751496.post-67813759978785388862016-10-13T19:33:02.198+02:002016-10-13T19:33:02.198+02:00Thank you very much!
This worked for me on Windows...Thank you very much!<br />This worked for me on Windows 10 64 bit. :)Anonymoushttps://www.blogger.com/profile/13745195020822443713noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-89085769620884747722016-07-07T11:10:34.665+02:002016-07-07T11:10:34.665+02:00This worked on Windows 10 also. Thanks for the Po...This worked on Windows 10 also. Thanks for the Post!Danhttps://www.blogger.com/profile/06169894579231442018noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-1626904108083608592016-07-07T11:09:56.119+02:002016-07-07T11:09:56.119+02:00Works on Windows 10 also. Thanks for the post!Works on Windows 10 also. Thanks for the post!Danhttps://www.blogger.com/profile/06169894579231442018noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-28758376974040178432016-02-08T17:55:10.207+01:002016-02-08T17:55:10.207+01:00Fantastic Post, thankyou!
These instructions combi...Fantastic Post, thankyou!<br />These instructions combined with "Microsoft .NET Framework 1.1 Service Pack 1 Update for using SendKeys" sorted out my issues with an old piece of .net software :)Richard Dabellhttps://www.blogger.com/profile/09183110612438045269noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-25888940860525661432015-10-19T15:35:46.283+02:002015-10-19T15:35:46.283+02:00Did you use x32 or x64 command promt? Or there is ...Did you use x32 or x64 command promt? Or there is no difference?GunSmokerhttps://www.blogger.com/profile/15611696588191431330noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-42674693709971856752015-07-10T09:42:09.623+02:002015-07-10T09:42:09.623+02:00This comment has been removed by a blog administrator.Anonymoushttps://www.blogger.com/profile/06163775987491718328noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-26131146954907003212014-10-31T16:48:28.550+01:002014-10-31T16:48:28.550+01:00Thank you very much! Fixed my issue with ease. Muc...Thank you very much! Fixed my issue with ease. Much appreciated.Laurahttps://www.blogger.com/profile/13354083347156572544noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-20856323840313339662014-05-16T16:23:30.504+02:002014-05-16T16:23:30.504+02:00You saved my bacon! Running custom barcode scanner...You saved my bacon! Running custom barcode scanner software and it's dependent on 1.1. Many customers are upgrading to Win 8 and it's wreaking havoc on our systems. Thanks for posting that info, it worked like a charm.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-78314128275179487062014-05-16T04:10:10.871+02:002014-05-16T04:10:10.871+02:00These instructions are way more complicated than t...These instructions are way more complicated than they need to be. This is much simpler. http://support.encore.com/technicalsupport/kb.aspx?kb_id=731&product_id=2644Vengeancehttps://www.blogger.com/profile/04974982229990855832noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-17223835146152453792014-04-02T21:43:43.907+02:002014-04-02T21:43:43.907+02:00Thank you very very much! Worked like a charm on W...Thank you very very much! Worked like a charm on Windows 8.1 x64. Just a NOTE to anyone else trying it:<br /><br />It seemed like some of the installers ran throughout the described process were displaying some panels from Windows. In there you should click the option saying something like "Run this program anyway" (or without compatibility support or something). This will allow the installation to continue.<br /><br />Thank you again for this awesome article!:)SkullDemonhttps://www.blogger.com/profile/13576808462369517211noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-84834516853128536672014-02-12T08:59:30.421+01:002014-02-12T08:59:30.421+01:00This code doesn't work under Windows XP and Wi...This code doesn't work under Windows XP and Windows Server 2003 (http://msdn2.microsoft.com/en-us/library/ms684175.aspx). Please use TlsAlloc/TlsSetValue/TlsGetValue instead of __declspec(thread)!<br />Anonymoushttps://www.blogger.com/profile/08559056369876557207noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-87933291629247104672014-01-24T21:49:43.437+01:002014-01-24T21:49:43.437+01:00VS2012 breaks this decision! Constructor std::stri...VS2012 breaks this decision! Constructor std::string() always allocates memory...Anonymoushttps://www.blogger.com/profile/08559056369876557207noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-67736835419229479772013-01-28T21:26:23.076+01:002013-01-28T21:26:23.076+01:00Do you mean process GUIDs to detect different proj...Do you mean process GUIDs to detect different project types?Anonymoushttps://www.blogger.com/profile/08559056369876557207noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-75926461705736407702013-01-27T22:42:23.438+01:002013-01-27T22:42:23.438+01:00Is there a way to pro grammatically get this infor...Is there a way to pro grammatically get this information?<br /><br />TarunTarunhttps://www.blogger.com/profile/13637216175024699097noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-85779205524108182072012-10-31T19:28:56.073+01:002012-10-31T19:28:56.073+01:00This comment has been removed by the author.cadudehttps://www.blogger.com/profile/05384729591444689363noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-23597996648052382972012-10-31T09:43:42.930+01:002012-10-31T09:43:42.930+01:00This comment has been removed by the author.cadudehttps://www.blogger.com/profile/05384729591444689363noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-41256636377464125402012-10-28T11:35:39.497+01:002012-10-28T11:35:39.497+01:00I mean that new RIP/RSP values point to the valid ...I mean that new RIP/RSP values point to the valid memory. RSP is aligned in the right way and in valid range.Anonymoushttps://www.blogger.com/profile/08559056369876557207noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-15097562977981258002012-10-28T08:20:47.694+01:002012-10-28T08:20:47.694+01:00This comment has been removed by the author.cadudehttps://www.blogger.com/profile/05384729591444689363noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-44782405754283312192012-10-26T17:16:44.378+02:002012-10-26T17:16:44.378+02:00I don't use the loader critical section. I use...I don't use the loader critical section. I use the dynamic function table critical section.Anonymoushttps://www.blogger.com/profile/08559056369876557207noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-890683372071320002012-10-26T17:11:38.958+02:002012-10-26T17:11:38.958+02:00regarding checking critical secion
i found this, ...regarding checking critical secion<br /><br />i found this, is this doable, what are you using ?<br /><br />http://www.tech-archive.net/Archive/Development/microsoft.public.win32.programmer.kernel/2009-11/msg00020.htmlcadudehttps://www.blogger.com/profile/05384729591444689363noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-57678135621167572772012-10-26T09:36:20.683+02:002012-10-26T09:36:20.683+02:00Remove RtlZeroMemory() and NvContext. You should u...Remove <i>RtlZeroMemory()</i> and <i>NvContext</i>. You should use context in <i>RtlVirtualUnwind()</i>. Please add strong RSP and RIP check after unwinding.<br /><br />You should stop walking after <i>DoStackSnapshot()</i> call anyway.<br /><br />P.S. You need to fix CLR before or use CLR v2.0 x64 for debug.Anonymoushttps://www.blogger.com/profile/08559056369876557207noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-15708873545595998612012-10-26T09:19:31.770+02:002012-10-26T09:19:31.770+02:00This is the known issue of CLR v4.0 x64. It calls ...This is the known issue of CLR v4.0 x64. It calls <i>clr!EEGetThreadContext()</i> with <i>CONTEXT_EXCEPTION_REQUEST</i> by itself and checks that there the <i>CONTEXT_SERVICE_ACTIVE</i> or/and <i>CONTEXT_EXCEPTION_ACTIVE</i> in ContextFlags of <i>CONTEXT</i>.<br /><br />There is the only one way to fix it: the patch.Anonymoushttps://www.blogger.com/profile/08559056369876557207noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-33709105504966057872012-10-26T02:28:46.781+02:002012-10-26T02:28:46.781+02:00This comment has been removed by the author.cadudehttps://www.blogger.com/profile/05384729591444689363noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-1520663720010330212012-10-25T23:19:27.866+02:002012-10-25T23:19:27.866+02:00I tried to use StackWalk64(), but I really had som...I tried to use <i>StackWalk64()</i>, but I really had some trouble with it. It worked strange when I don't have PDB.<br /><br />Base is <a href="http://blogs.msdn.com/b/davbr/archive/2005/10/06/profiler-stack-walking-basics-and-beyond.aspx" rel="nofollow">here</a>, but I have some improvements:<br />0. suspend thread<br />1. check dynamic function table critical section to ability to enter<br />2. get <i>CONTEXT</i> for suspended thread<br />3. call <i>GetFunctionFromIP()</i>, goto #7 if it's success and returns non-zero FunctionID<br />4. call <i>RtlLookupFunctionEntry()</i><br />5. call <i>RtlVirtualUnwind()</i> if #4 returns non NULL or pop RIP from stack if NULL<br />6. check and update RSP + RIP in <i>CONTEXT</i>, goto #3<br />7. call <i>DoStackSnapshot()</i><br /><br />There are some critical bugs in CLR v2.0 x64 and CLR v4.0 x64 described <a href="http://workblog.pilin.name/2012/04/stack-walker-clr-x64.html" rel="nofollow">here</a>. However, the article in Russian now. I'm going to translate it when I will have time for it. Now, you can use Google Translate...Anonymoushttps://www.blogger.com/profile/08559056369876557207noreply@blogger.comtag:blogger.com,1999:blog-8643966532123751496.post-76697127787643898902012-10-25T18:42:13.312+02:002012-10-25T18:42:13.312+02:00This comment has been removed by the author.cadudehttps://www.blogger.com/profile/05384729591444689363noreply@blogger.com