| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Any ideas? |
Hi Neil,
Good to see this echo isn't dead... ;-)
Tue 2002-12-03 15:09, Neil Heller (1:106/2000) wrote to All:
> I recently wrote a Windows program using MFC as a shared resource.
Using which compiler? I have a Win2K box, and a WinXP box (a measly P133
with 64 Mb & 10 Gb HDD RAM, would you believe), as well as several
compilers, including Visual C++ 6.0...
> I thought it would run in Windows XP without change IF XP also used MFC
> as a shared resource.
You would hope so. ;-)
> However, upon launching the program XP showed an error message that a
> system problem had occurred (no detail at all) and stated that I should
> report it to Microsoft.
Strange. Can you post a short program demonstrating the problem? And any
appropriate compiler/linker arguments (unless you're using the IDE of your
compiler...)
> My first thought was that at least one entry point into a DLL had been
> changed resulting in a linkage problem. Does anybody have any other
> ideas about what the problem may have been?
You may be calling an MFC function with the wrong arguments. I'm not at
all familiar with it though.
> [An interesting note}
> In the error message that I received (above) the OS was stated to have
> been NT 5.1 (build two thousand something). Interesting, no?
Not really. ;-)
Windows 2000 is NT 5.0, Windows XP is NT 5.1. Presumably the next will be 5.2...
7:34 voodoo [c:\]ver /r
4NT 3.01A Windows NT 5.00
4NT Revision A (119) Windows NT Build 2195 Service Pack 3
7:35 digital [c:\]ver /r
4NT 3.01A Windows NT 5.01
4NT Revision A (119) Windows NT Build 2600
-- mail{at}ozzmosis.com
--- Msged/NT 6.1.1
* Origin: Blizzard of Ozz, Mt Eliza, Victoria, Australia (3:633/267.1)SEEN-BY: 633/267 270 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.