Computer information using COMate

Share your advanced PureBasic knowledge/code with the community.
akj
Enthusiast
Enthusiast
Posts: 668
Joined: Mon Jun 09, 2003 10:08 pm
Location: Nottingham

Post by akj »

But if I include Droopy's lib it then starts getting complicated as I get messages relating to duplicated labels such as IID_Unknown:
Is there an easy way to supress such error messages?

EDIT:
I am now using the compiled version of Droopy's lib rather than the source and all is now OK.
Anthony Jordan
Micko
Enthusiast
Enthusiast
Posts: 244
Joined: Thu May 24, 2007 7:36 pm
Location: Senegal
Contact:

Post by Micko »

very big work
thanks
SFSxOI
Addict
Addict
Posts: 2970
Joined: Sat Dec 31, 2005 5:24 pm
Location: Where ya would never look.....

Post by SFSxOI »

Just a quick informational thing for the 'QFE_Info()' procedure. According to the MSDN, for the Win32_QuickFixEngineering WMI class;

For Windows Vista: Starting with Windows Vista, this class returns only the updates supplied by Component Based Servicing (CBS). These updates are not listed in the registry. Updates supplied by Microsoft Windows Installer (MSI) or the Windows update site (http://update.microsoft.com) are not returned by the Win32_QuickFixEngineering class that i used in the 'QFE_Info()' procedure.

For Windows XP: instances of this class represent updates found in two places in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix

and....

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates
nicolaus
Enthusiast
Enthusiast
Posts: 456
Joined: Tue Aug 05, 2003 11:30 pm
Contact:

Post by nicolaus »

Well it is a very nice code and super work.
But if i use it with Win XP SP3 every time it stops with a error messagerequester at the procedure "MB_Info". If i click ok than it shows a lote of more error messages.

With Vista it works very fine!
SFSxOI
Addict
Addict
Posts: 2970
Joined: Sat Dec 31, 2005 5:24 pm
Location: Where ya would never look.....

Post by SFSxOI »

@nicolaus;

I'll take a look and see whats causing the MB_Info problem for ya on XP SP3. I might have included something that doesn't work on XP in that area. I'll have to find an XP machine to check it on and i'll get back with something a little later.

EDIT:

Well, everything seems to be working here OK. In the MB-Info procedure, put this debug line above the message requester and let me know what it says:

Code: Select all

Else
Debug COMate_GetLastErrorDescription()  ; <<<< put this
MessageRequester("Error", "MBInfo")

and add this too above the sysMB\Release() after the Wend

Wend
      MB\Release() ; <<<<<<< add this above the sysMB\Release() and see if the problem goes away 
      sysMB\Release() 
      
 
make sure your using the latest version of COMate also.
User avatar
GeoTrail
Addict
Addict
Posts: 2794
Joined: Fri Feb 13, 2004 12:45 am
Location: Bergen, Norway
Contact:

Post by GeoTrail »

Nice work m8.
To save people from some time, I've added all the code parts into files, included all the needed pbi files and the Droopy libs.

Can be downloaded here:
http://robert.geotrail.no/Computer_info ... COMate.rar

Forgot to write that the Droop exe file copies both the x86 og 64 versions of the lib to your PB folder. You can't have BOTH there so delete the one you don't need.
I Stepped On A Cornflake!!! Now I'm A Cereal Killer!
User avatar
singo
User
User
Posts: 35
Joined: Mon Apr 23, 2007 4:50 am
Location: Nabiac NSW Australia

Re: Computer information using COMate

Post by singo »

Tried this with ComatePLUS, latest Droopy and PB4.51X86 on Win XPSP3 and gettting error :-

POLINK Error : Unresolved external symbol "VerLanguageNameA" and a similar error if compiled with unicode.

Any ideas on how to fix this error ?
Singo
Win10, Win7, Debian x86 & OSX ~ PB 5.70 LTS
Minimbah NSW Australia
Post Reply