An RSS feed would be grand. Though I would expect it to come with ads just like the email. regards, Paul Watson Ireland Feed Henry! Shog9 wrote: eh, stop bugging me about it, give it a couple of days, see what happens.

Do you mean vertical rows? Would the listview's Icon View do the trick for you or do you need to show more data than just an icon and a bit of text? ...Steve

OK I figured it out - just use the other version of Load(byte[], byte[]) where the second byte array is the symbol stream! Dave Kolb http://dotnetcodeslingers.com

I don't know what the norm is, but I can say what I do. I generate a single keyfile for use by everything I do for a company, whether or not it will go in the GAC. (You never know when you will want to put something there). Depending on your environment, you may want to delay-sign the assemblies, and then complete the signing later with a super-secret key file accessible only to trusted people. (I have not needed to do that yet). my blog

Did you copy the class StatusWrapper, or is it in an assembly referenced by both application?

If you need unload assembly, load it in an another domain and then unload domain. No way for unloading only assembly :( P.S. sorry for the my dirty English

CopyFileEx is not a COM method, it's just a plain stdcall API function. Same thing with it's callback, there's no interface there at all, just a function pointer to a stdcall function. Nothing to marshal. -Blake

Assuming you are not using free threaded apartments, you are in a canoe on a creek of manure, without paddles. You need to synchronize the apartments by marshalling the pListing interface pointer. Take a look at Len Holgates excellent article which touches this subject: COM Mailslots - Designing asynchonous COM components for VB[^]. -- They're out get me, I can't escape cos' they won't let me They won't forget me, they'll get me in their grip and sweat me They'll wait me out, and then move in under my skin They'll make me doubt, they're out to make me let them in

It is less simple than that. You need to put Enter/LeaveCritSect's around access to shared resources. If each of your instances are independent, then you don't need any critical sections. You may need CritSects in the sub-threads if they can collide when accesses common resources. So the general answer is "it depends". The fewer CriticalSections you have the better as it means your components will run that little bit more smoothly, especially on multi-threaded systems. But it is more important to be safe. I hope this sort-of-helps. Iain.

Have a look at WM_QUERYENDSESSION: WM_QUERYENDSESSION The WM_QUERYENDSESSION message is sent when the user chooses to end the session or when an application calls the ExitWindows function. If any application returns zero, the session is not ended. The system stops sending WM_QUERYENDSESSION messages as soon as one application returns zero. After processing this message, the system sends the WM_ENDSESSION message with the wParam parameter set to the results of the WM_QUERYENDSESSION message. WM_QUERYENDSESSION nSource = (UINT) wParam; // source of end-session request fLogOff = lParam // logoff flag Parameters nSource - Reserved for future use. fLogOff - Value of lParam. Indicates whether the user is logging off or shutting down the system. Supported values include: ENDSESSION_LOGOFF. Return Values If an application can terminate conveniently, it should return TRUE; otherwise, it should return FALSE. :-D Dominik _outp(0x64, 0xAD); and __asm mov al, 0xAD __asm out 0x64, al do the same... but what do they do?? ;) (doesn't work on NT)

may you describe it a bit more? but... if you create a "normal" hashkey which is suitable for the hashspace, and then transform it to ASCII? LOWELL = 76 79 87 69 76 76 -> S = 7679 + 8769 + 7676 = 24124 your hashspace is 19937 (should be prime) 24124 % 19937 = 4187 and now put it to ASCII 41 and 87 :confused:

Paul Farry wrote: Is it ok to create a Thread to do all this work (as long as I don't modify or read memory inside the component from within the thread) in the Destructor of the component? Yes, it's fine. As you mentioned, watch out for accessing memory that has been deleted. Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

Actually, you should declare your struct with padding out to the width of the datatype that you declare as the bits. EX: struct Bitflags { unsigned char Bit1 : 1; unsigned char Bit1 : 1; unsigned char Bit1 : 1; unsigned char Padding : 5; };

Funny you should mention, as I work with an RPG programmer. His code runs on the AS/400, while mine runs on the PC (Windows). Whenever I send him data, it must be converted from ASCII to EBCDIC. Whenever he sends me data, it must be converted from EBCDIC to ASCII. I use a library provided by IBM that has a couple of convertors in it.

I don't see any use in changing the entry point neither, except wWinMain and wmain of course. Anyway it's just a function and called only once (as long as you're not recursing :~ in main) I guess people have different tastes and different ways to obfuscate their code. You never know ;P