Error lookup tool

Error Lookup
для Windows

Version: 2.4.2

Author:

First release: 26 February 2011

Last updated: 10 November 2021

License: GPL v3

Language: C

Platform architecture: 32-bit/64-bit/arm64

Supported OS: Windows XP (SP 3), Vista, 7, 8, 8.1, 10, 11

Donation

Development is powered by your donations!

Description

Portable open source tool which can help by translating error codes into a more meaningful text description. The interface is simple — just a box to type your code, and another which displays the details — so there doesn’t seem much to learn.

The program also supports a wide range of codes: regular Windows errors, DirectX, NTSTATUS errors, Windows Internet errors, STOP codes, And we think it can probably be configured to read more (Settings > System modules), although there’s no documentation to confirm that and we didn’t test it.

The lightweight application is less than a megabyte, and it is compatible with Windows XP SP3 and higher operating systems. You can download either the installer or portable version.

Portable mode

To activate portable mode, create errorlookup.ini in application folder, or move it from %APPDATA%Henry++Error Lookup.

Download

• errorlookup-2.4.2-bin.zip
• errorlookup-2.4.2-setup.exe
• errorlookup-2.4.2-setup.exe.sig
• errorlookup-2.4.2.sha256

Latest stable release is always here

GPG Signature

Binaries have GPG signature errorlookup.exe.sig in application folder.

• Public key: pubkey.asc (pgpkeys.eu)
• Key ID: 0x5635B5FD
• Fingerprint: D985 2361 1524 AB29 BE73 30AC 2881 20A7 5635 B5FD

Languages

Put errorlookup.lng file into application directory and restart the program.

• Download language
• Read instruction to create your own localization

Links

• GitHub
• Changelog
• License agreement

Support

• Report issue
• Pull requests

Сами по себе коды ошибок Windows не предоставляют никакой практической информации, которая могла бы пригодиться в деле их устранения, запомнить же все коды просто невозможно, разве что вам постоянно приходится иметь с ними дело. Тем, кто является системным администратором или увлекается темой системного администрирования, в таких случаях может пригодиться тулза Error Lookup, буквально «Поиск ошибок».

Эта небольшая программка является, по сути, справочником по кодам ошибок в Windows 10.

Запустив утилиту, введите код ошибки или выберите его в выпадающем списке. При этом в поле модули станет выводиться свой список — список модулей, под которыми следует понимать сценарии, в которых появляется ошибка.

Такая классификация необходима, поскольку один и тот же код ошибки в разных сценариях будет иметь разные значения. Например, ошибка с кодом 0x00000003 в сценарии Windows (User Mode) станет указывать на невозможность системы найти указанный путь, а в сценарии BSOD — на попытку установить несовместимое оборудование.

Доступны модули с кодами ошибок DirectX, NTSTATUS, модули сетевых ошибок и так далее. Жаль вот только, что не для всех кодов Error Lookup выводит подробное описание, часто она ограничивается лишь названием ошибки, что тоже мало о чём говорит.

Стоп-ошибка 0x00000003 имеет имя INVALID_AFFINITY_SET, но что такое INVALID_AFFINITY_SET не указывается. Пришлось выяснять это в интернете. Но, поскольку Error Lookup активно развивается, есть надежда, что разработчик добавит подробные описания ошибок или даже общие рекомендации по их устранению.

Инструмент доступен на сайте разработчика github.com/henrypp/errorlookup, имеется портативная версия. Утилитой поддерживается русский язык, в настройках можно отключить часть модулей (всего их 109), которые по умолчанию все включены.

The Microsoft Error Lookup Tool

The Microsoft Error Lookup Tool displays the message text that is associated with a hexadecimal status code (or other code). This text is defined in various Microsoft source-code header files, such as Winerror.h, Setupapi.h, and so on.

The tool is digitally signed by Microsoft. The following is the SHA256 information for the file download:

Business environments may restrict which files can run and from where. Before you download and run this tool, check the following details:

• Do you have to have permission or a security exception in order to download or run the tool?
• Can you store and run this tool on your computer (for example, in your Documents folder)? Or do you have to store and run the tool on a specialized computer, such as a central file server?

Usage

Download the tool by selecting this link.

If you didn’t specify a location in step 1, go to your download folder, and copy or move the downloaded file (Err_6.4.5.exe) to folder in which you will store the tool. You do not have to expand or install the file.

If you copy or move the file to a folder that is listed in your operating system’s Path environment variable, it will work at any command prompt.

Open a Command Prompt window. If necessary, change the directory to the location of the Error Lookup Tool.

Run the following command:

In this command, represents the hexadecimal code that you want to look up.

Examples

More information

Keep in mind that this is a «point-in-time» tool. The Microsoft Error Lookup Tool decodes most Microsoft error codes as of the date on which the tool was compiled. As new releases of Windows add new event and error codes, you may have to download a new version of the Error Lookup Tool. Check the Microsoft Download Center for a new version, or see Error Codes.

Источник

Error Lookup для Windows

Error Lookup — небольшая утилита для получения информации о системных ошибках Windows, DirectX, NTSTATUS, WinInet, STOP. Вводите код ошибки — получаете текст. Поддерживаются следующие коды ошибок:

• Windows — коды возвращаемые функцией GetLastError();
• DirectX — коды возвращаемые функциями DirectX;
• NTSTATUS — коды возвращаемые функциями API режима ядра;
• WinInet — коды возвращаемые функциями библиотеки WinInet;
• Диспетчер устройств — коды которые сообщает диспетчер устройств;
• STOP — коды выдаваемые на синем экране смерти.

Распространяемый компонент Microsoft Visual C++ для Visual Studio 2015, 2017 и 2019, поскольку в VS 2015 и более.

Windows 7 USB/DVD Download Tool — отличный инструмент от компании Microsoft, с помощью которого можно легко.

Приложение для персонализированной настройки периферийных устройств от компании HyperX.

Бесплатная и простая в использовании утилита, с помощью которой можно буквально за пару.

MapKeyboard — небольшая бесплатная утилита с помощью которой можно легко переназначить или.

Process Lasso — Небольшая утилита для операционных систем Windows, которая позволяет вручную или.

Отзывы о программе Error Lookup

Admin

Отзывов о программе Error Lookup 2.4.2 пока нет, можете добавить.

Источник

Средство поиска ошибок (Майкрософт)

Средство поиска ошибок (Майкрософт) отображает текст сообщения, связанный с шестнадцатеричным кодом состояния (или другим кодом). Этот текст определяется в различных файлах заголовков исходного кода Майкрософт, таких как Winerror.h, Setupapi.h и т. д.

Средство цифровой подписывается корпорацией Майкрософт. Ниже приведены сведения о SHA256 для скачивания файла:

Бизнес-среды могут ограничивать, какие файлы могут запускаться и откуда. Перед скачиванием и запуском этого средства проверьте следующие сведения:

• У вас есть разрешение или исключение безопасности, чтобы скачать или запустить средство?
• Можно ли хранить и запускать это средство на компьютере (например, в папке «Документы»)? Или вам нужно сохранить и запустить средство на специализированном компьютере, например на центральном файловом сервере?

Использование

Скачайте средство, щелкнув эту ссылку.

Если вы не указали расположение на шаге 1, перейдите в папку загрузки и скопируйте или переместите скачанный файл (Err_6.4.5.exe) в папку, в которой будет храниться средство. Вам не нужно развертывать или устанавливать файл.

При копировании или перемещении файла в папку, указанную в переменной среды path операционной системы, она будет работать в любой командной строке.

Откройте окно командной строки и При необходимости измените каталог на расположение средства поиска ошибок.

Выполните следующую команду:

В этой команде ошибки представляет шестнадцатеричный код, который требуется найти.

Примеры

Дополнительные сведения

Имейте в виду, что это инструмент «на определенный момент времени». Средство поиска ошибок (Майкрософт) декодирует большинство кодов ошибок Майкрософт по дате компиляции средства. По мере добавления новых выпусков Windows новых кодов событий и ошибок может потребоваться скачать новую версию средства поиска ошибок. Проверьте центр загрузки Майкрософт для новой версии или просмотрите коды ошибок.

Источник

Windows Error Lookup Tool

View Windows Error Code and Define Descriptions

Simple enough, windows will display a value in either Decimal or Hex for Win32, HRESULT, NTSTATUS and STOP error codes (For the Developer, this can be the return value of an API call or from GetLastError). Type in an error code and WELT will display the Facility, Status, Code, Define, and Description for the error. You also have the option to create a note for an error (so you can keep track of what you have done to create the error) I have removed the notes for now, if you request it, I will add it back.

Although geared towards the developer, the average user should find this program useful.

Unsure of the value of a define? Enter it into WELT and it will show you the value.
Total defines supported:

• Win32: 2,527
• NTSTATUS: 1,730
• HRESULT: 1,767
• STOP: 318

Defines are from various header files and [MS-EERR].pdf — v20120328 released Wednesday, March 28, 2012
Am I missing a define (I know I am) Send me the define, value, and where it is from.

To use:
Enter either a define or error code and hit enter (you can also paste and WELT will automatically search)
Valid numbers are:

• Decimal — signed or unsigned
• Hexadecimal — 0x########

WELT will detect the error type from the code entered and if it is found, the type will become «enabled» under the edit control. You can click on one to get the error information.

To Install/Uninstall
Select a download from the right Create a directory and unzip files. To uninstall, delete directory

For the curious
The skin is called Anion from WindowBlinds

Источник

Windows Error Code & Message Lookup Tools

Ever been stumped with an error code your Windows installation threw up and did know where to look it up? There are a few tools that can help you identify the Error Code and Message which Windows may throw up. Let us have a look at a few of such free tools that can help you find out the meanings of such Windows error codes and messages.

Windows Error Code & Message Lookup Tools

Windows Error Lookup Tool, Error Messages, ErrMsg, Error Goblin for Windows are some free error code lookup tools that can help you identify what Windows error codes means. This post also lists useful links to download and web pages that can help you identify the error codes and check up on error messages

1] Error Messages for Windows

Error Messages for Windows will allow you to look up Microsoft Windows error code numbers and display a descriptive message explaining what the numeric code actually means. It also lets you display and print all of the error codes and messages defined for your version of Windows. Error Messages for Windows have now been updated for Windows 10 and you can download it from http://www.gregorybraun.com/MSWinErr.html.

2] Windows Error Lookup Tool

Windows Error Lookup Tool is another tool, like Error Goblin or ErrMsg, that can help you look up Windows error codes. If you have software programs that produce numeric error codes, you can find out what they mean using these tools.

3] Microsoft Error Code Lookup Tool

The Microsoft Error Code Lookup Tool, may say it’s for Exchange, but it covers Exchange, Windows and a number of other Microsoft products too. This command-line tool can help determine error values from decimal and hexadecimal error codes in Microsoft Windows operating systems.

The syntax for running this tool is:

Here represents the hexadecimal code that you want to look up.

For instance, if you gave system error code 0x7, you have to run the following command:

4] Windows Error Code Lookup

The Windows Error Codes document lists the common usage details for those Win32 error codes, HRESULT values, and NTSTATUS values. The Events and Errors Message Center lets you search for and find detailed message explanations, recommended user actions, and offers links to additional support and resources. This post on Windows Errors, System Error Messages and Codes will give you the complete list and meaning of the errors.

5] Error Lookup Tool

Error Lookup Tool offers a straightforward UI that is easy to understand. You just need to go ahead and put in your error code and all the details will be flashed in the lower part. You can see the details like the error description and their related system module.

How do I check for errors in Windows 11/10?

There are multiple ways to check for errors in Windows 11 and Windows 10 computers. However, Windows Error Lookup Tool is one of the best tools to find details about the errors that appear on Windows PC. It displays the kind of error based on the error code you entered in the app.

How do I find Windows errors?

You can use the Windows Error Lookup Tool to find Windows errors on your computer. It is a neat and clean app that you can use to find details about the error. Whether it is a Windows Update error, activation error, or something else, you can find all the information about the error code.

I hope this post helps you.

Date: April 9, 2020 Tags: Errors, Freeware

Источник

The Microsoft Error Lookup Tool displays the message text that is associated with a hexadecimal status code (or other code). This text is defined in various Microsoft source-code header files, such as Winerror.h, Setupapi.h, and so on.

The tool is digitally signed by Microsoft. The following is the SHA256 information for the file download:

Business environments may restrict which files can run and from where. Before you download and run this tool, check the following details:

• Do you have to have permission or a security exception in order to download or run the tool?
• Can you store and run this tool on your computer (for example, in your Documents folder)? Or do you have to store and run the tool on a specialized computer, such as a central file server?

Usage

Download the tool by selecting this link.

If you didn’t specify a location in step 1, go to your download folder, and copy or move the downloaded file (Err_6.4.5.exe) to folder in which you will store the tool. You do not have to expand or install the file.

If you copy or move the file to a folder that is listed in your operating system’s Path environment variable, it will work at any command prompt.

Open a Command Prompt window. If necessary, change the directory to the location of the Error Lookup Tool.

Run the following command:

In this command, represents the hexadecimal code that you want to look up.

Examples

More information

Keep in mind that this is a «point-in-time» tool. The Microsoft Error Lookup Tool decodes most Microsoft error codes as of the date on which the tool was compiled. As new releases of Windows add new event and error codes, you may have to download a new version of the Error Lookup Tool. Check the Microsoft Download Center for a new version, or see Error Codes.

Источник

Ever been stumped with an error code your Windows installation threw up and did know where to look it up? There are a few tools that can help you identify the Error Code and Message which Windows may throw up. Let us have a look at a few of such free tools that can help you find out the meanings of such Windows error codes and messages.

Windows Error Lookup Tool, Error Messages, ErrMsg, Error Goblin for Windows are some free error code lookup tools that can help you identify what Windows error codes means. This post also lists useful links to download and web pages that can help you identify the error codes and check up on error messages

1] Error Messages for Windows

Error Messages for Windows will allow you to look up Microsoft Windows error code numbers and display a descriptive message explaining what the numeric code actually means. It also lets you display and print all of the error codes and messages defined for your version of Windows. Error Messages for Windows have now been updated for Windows 10 and you can download it from http://www.gregorybraun.com/MSWinErr.html.

2] Windows Error Lookup Tool

Windows Error Lookup Tool is another tool, like Error Goblin or ErrMsg, that can help you look up Windows error codes. If you have software programs that produce numeric error codes, you can find out what they mean using these tools.

3] Microsoft Error Code Lookup Tool

The Microsoft Error Code Lookup Tool, may say it’s for Exchange, but it covers Exchange, Windows and a number of other Microsoft products too. This command-line tool can help determine error values from decimal and hexadecimal error codes in Microsoft Windows operating systems.

The syntax for running this tool is:

Here represents the hexadecimal code that you want to look up.

For instance, if you gave system error code 0x7, you have to run the following command:

4] Windows Error Code Lookup

The Windows Error Codes document lists the common usage details for those Win32 error codes, HRESULT values, and NTSTATUS values. The Events and Errors Message Center lets you search for and find detailed message explanations, recommended user actions, and offers links to additional support and resources. This post on Windows Errors, System Error Messages and Codes will give you the complete list and meaning of the errors.

5] Error Lookup Tool

Error Lookup Tool offers a straightforward UI that is easy to understand. You just need to go ahead and put in your error code and all the details will be flashed in the lower part. You can see the details like the error description and their related system module.

How do I check for errors in Windows 11/10?

There are multiple ways to check for errors in Windows 11 and Windows 10 computers. However, Windows Error Lookup Tool is one of the best tools to find details about the errors that appear on Windows PC. It displays the kind of error based on the error code you entered in the app.

How do I find Windows errors?

You can use the Windows Error Lookup Tool to find Windows errors on your computer. It is a neat and clean app that you can use to find details about the error. Whether it is a Windows Update error, activation error, or something else, you can find all the information about the error code.

I hope this post helps you.

Date: April 9, 2020 Tags: Errors, Freeware

Источник

1. _com_error is just a wrapper around FormatMessage.

2. Higher versions of MS VS contain buggy implementation of _com_error.

See here for details. Sign In· View Thread

conversion error when compiling

ehaerim

23-Dec-07 22:44

In an ATL COM project, if (FAILED(hr)) < ::MessageBox(NULL, _com_error(hr).ErrorMessage, _T(«FinalConstruct»), MB_ICONSTOP); > cause the following error message and I couldn’t make it compile OK. error C2664: ‘MessageBoxA’ : cannot convert parameter 2 from ‘const char *(void) const’ to ‘const char *’ There is no context in which this conversion is possible How to fix this? HaeRim
Sign In· View Thread

Can we use this with WSAGetLastError () for reporting WinSock errors?

Siva Ranganeni

24-May-06 5:17

Hi, This is a great article and very helpful. Can we use the same with WSAGetLastError()? Will the following code give Winsock error message()? _com_error( HRESULT_FROM_WIN32(WSAGetLastError() ).ErrorMessage() Thanks in Advance. Siva
Sign In· View Thread

Re: Can we use this with WSAGetLastError () for reporting WinSock errors?

jwpfish

16-Jul-07 18:16

You can do that, e.g.: puts(_com_error(WSAENOTSOCK).ErrorMessage());
Sign In· View Thread

That is great! Thank you!

Ferne Li

8-May-06 16:32

That is great! Thank you!
Sign In· View Thread

Excellent.

kimjim

20-Mar-06 18:11

Excellent article. I implemented this in my project. Thank you. A few words about passing GetLastError() as an argument. As far as I know all the function’s arguments are evaluated before the actual function call is made. Let us take a case where some other win32 or other functions are called in the constructor of the _com_error or like class object. But we are passing the GetLastError as a parameter. So before even the constructor which is afterall a function, starts its execution. So I dont think this will be a problem. If at all the problem comes just make a workover. Create a function alike: and put all your _com_error calls in that(using the ‘hr’ above). Pass GetLastError as a parameter to CallComErrMsgBox(). This should solve the problem. Again excellent article. This kind of articles teaches again and again the time that can be saved by stopping «reinventing the wheel» Thanks, Jim

Sign In· View Thread

Very good

Sam NG

20-Feb-06 17:02

Thank you I am not aware of the _com_error class. I do the error handling by my own macro, not a bad solution, but I think if the compiler already have it, better not «reinventing» the wheel. Besides, I agree with ARB70 that display the «system» error message may not be the most difficult part, providing a more meaningful message specific to your application and your target user group is a even more challenging task. And I am always confused about what should be display in case of error «Error initialize the program» seem good enough for general users but it won’t help in finding the reason why the program won’t start. Sam

Sign In· View Thread

Re: Very good

Brian C Hart

21-Feb-06 9:13

«Error initialize the program» seem good enough for general users but it won’t help in finding the reason why the program won’t start. Perhaps. but all these strings are mapped to specific E_ or other constant values in code. and can be looked up in the docs. That’s the beauty of it. So just append, to the _com_error.ErrorMessage() output a string saying «nnEmail Tech support with the exact wording of this error string, and what you were doing when this happened.» Then you can work backwards from there as to what SDK calls you were making at that point, and from the error string you can work back to which error code the SDK call returned, and then you can look the SDK call up in the docs and work backward to figure out when said call returns that specific code. Sincerely Yours, Brian Hart Department of Physics and Astronomy University of California, Irvine

Sign In· View Thread

One problem this article does not solve.

ARB70

3-Jan-06 12:43

The fact that both Win32 and COM error messages are frequently cryptic and unhelpful. I have used _com_error a lot in the past for dealing with HRESULTS. If you import a COM type library in C++ and call methods on the generated smart pointers they always throw _com_error when something goes wrong, so having a catch handler that deals with them is nearly always mandatory. I was not aware that you could also use them for dealing with Win32 calls and that is very helpful and useful. Thanks. However both Win32 and COM produce extremely «techie», unhelpful error messages and I nearly always find that they require massaging if they are going to be of any help to a «normal» user. In you example «The system cannot find the file specified» is not terribly helpful. 100 different files may have been specified! «Class not registered» is even more cryptic! So unlike some other posters I won’t be changing all my code to use a one liner approach but will continue using support classes and other code to provide more meaningful error messages. Maybe this is not such a problem if all of your users are «propellor heads». ARB70

Sign In· View Thread

Re: One problem this article does not solve.

Brian C Hart

3-Jan-06 13:12

So unlike some other posters I won’t be changing all my code to use a one liner approach but will continue using support classes and other code to provide more meaningful error messages. Maybe this is not such a problem if all of your users are «propellor heads». Conceded. You have to do what you think is best for your particular application, and the user base you will be serving. Sincerely Yours, Brian Hart Department of Physics and Astronomy University of California, Irvine

Sign In· View Thread

Re: One problem this article does not solve.

Paul Sanders (the other one)

20-Oct-07 8:45

Nearly two years after the event is perhaps a little late to comment on this, but you never know, someone may read it. I think that reporting ‘bare metal’ WIN32 errors is extremely important when something happens to your program that you did not anticipate when you wrote it. I do accept, though, that it is no substitute for handling error conditions that you know, when you are writing the program, might reasonably arise (such as ‘file not found’, to take a trivial example). I guess what I am trying to say is that unexpected things ALWAYS happen to your software, and the more helpful *to the developer* the error message is in such circumstances, the more likely he/she is to be able to get to the bottom of it (and hence fix it in the next release). «The operation could not be completed» just doesn’t cut it. Encourage your users to copy cryptic error messages to the clipboard (provide a button that does it) and email them to you, perhaps. Of course, the ultimate error message is ‘assert failed’

Sign In· View Thread

Re: One problem this article does not solve.

Brian C Hart

21-Oct-07 16:38

Common Gotcha’s with GetLastError()

Doug Schmidt

3-Jan-06 6:07

The article above is good, but readers should be cautioned not to embed a call to GetLastError() as an argument to another function. Resist the temptation to do everything in one line. The only 100% reliable way of calling GetLastError() is on a line by itself, immediately after the WIN32 API call. The reasoning is that GetLastError() retrieves the last error encountered by the last Win32 API call on each thread. Some C++ class contructors (like _bstr_t ) will make WIN32 API calls to allocate resources, and if the arguments to the error formatting function use these objects, GetLastError() may actually return 0 (SUCCESS). So if your app formats every error with «ERROR DETECTED: %s», then you run the risk of displaying the embarassing «ERROR DETECTED: No error detected.», since «No error detected» is the message string for SUCCESS. The rather large I am working on has hit this problem many times, and usually it is because a temporary string was construtcted in between the Win32 API call and the call to GetLastError() . So you should prefer: over this more terse equivalent of Cheers, Doug

Sign In· View Thread

Re: Common Gotcha’s with GetLastError()

Brian C Hart

3-Jan-06 8:48

The above article is good, but readers should be cautioned not to embed a call to GetLastError() as an argument to another function. Resist the temptation to do everything in one line. The only 100% reliable way of calling GetLastError() is on a line by itself, immediately after the WIN32 API call. I concur that one should be careful; however, I have used this approach in multithreaded programs, with the _com_error class only, and have not had any problems. I assume that _com_error is somewhat thread-safe since it is designed to also be thrown as an exception type. Sincerely Yours, Brian Hart Department of Physics and Astronomy University of California, Irvine

Sign In· View Thread

Re: Common Gotcha’s with GetLastError()

Karim AM

16-Jan-06 16:05

I disagree with Doug Schmidt on this one — I’d expect you to be fine passing GetLastError() on its own into a function call or constructor, as the first thing that will happen is that GetLastError()’s return result will be assigned (and therefore fixed) into the function/constructor parameter. I would however be careful with macros, or fns/c’tors that have multiple parameters, where AFAIK it’s undefined in what order the parameters will be evaluated. Karim

Sign In· View Thread

Nice article. However.

W. Kleinschmit

1-Jan-06 22:40

Quote: . to determine if it is anything other than the ‘success value,’ which is S_OK. . Sorry, but this is wrong. By definition every negative HRESULT is an error. So the FAILED(. ) macro only tests for bit 31 of the HRESULT set. There are other possible return values (S_FALSE for example), that are sometimes used to indicate special situations but are not considered an error. FAILED(S_FALSE) returns FALSE. Anyway. Your article is one of the more usefull ones I have seen on CodeProject lately. Hang on.

Sign In· View Thread

Re: Nice article. However.

Brian C Hart

2-Jan-06 9:23

Sorry, but this is wrong. By definition every negative HRESULT is an error. So the FAILED(. ) macro only tests for bit 31 of the HRESULT set. There are other possible return values (S_FALSE for example), that are sometimes used to indicate special situations but are not considered an error. FAILED(S_FALSE) returns FALSE. I stand corrected. Sincerely Yours, Brian Hart Department of Physics and Astronomy University of California, Irvine

Sign In· View Thread

How do you correct this

AlexEvans

2-Jan-06 15:33

Nice work Brian Do intend to post a fix? Or maybe a way to fix this issue? Thanks for sharing Alex
Sign In· View Thread

Re: How do you correct this

Brian C Hart

2-Jan-06 15:39

As you can see, I have revised the article. This invites readers to look up FAILED and SUCCEEDED macros in the docs. The way you check for whether your COM calls have succeeded or fails really depends on your particular application. Sincerely Yours, Brian Hart Department of Physics and Astronomy University of California, Irvine
Sign In· View Thread

Immediate usage

Randor

1-Jan-06 16:23

There are some articles I read here on codeproject that have an immediate effect on my active projects, and motivate me to update older projects. This article is one of them. Many thanks.
Sign In· View Thread

Re: Immediate usage

Brian C Hart

1-Jan-06 18:23

I am humbled by your compliment. Thank you. Sincerely Yours, Brian Hart Department of Physics and Astronomy University of California, Irvine
Sign In· View Thread

Re: Immediate usage

JPaulson

3-Jan-06 8:39

I agree. I immediately went through and updated the project I was working on as well. This is why I subscribe to the CodeProject newsletter.
Sign In· View Thread

Two words for you

Rob Manderson

1-Jan-06 10:33

Bloody brilliant! And exactly what I needed for a COM object I’m writing. You got my 5. I’m working on a version for Visual Lisp++ My blog http://blogs.wdevs.com/ultramaroon/[^]
Sign In· View Thread

Re: Two words for you

Brian C Hart

1-Jan-06 19:50

And exactly what I needed for a COM object I’m writing. You got my 5. Such a pleasure to receive such kind words. Thank you. Happy New Year! Sincerely Yours, Brian Hart Department of Physics and Astronomy University of California, Irvine
Sign In· View Thread

General News Suggestion Question Bug Answer Joke Praise Rant Admin

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Источник

Автор: Baguvix от 13-01-2021, 10:54, Посмотрело: 990, Обсуждения: 0

Категория: Системные утилиты / Другое