• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

XP Pro x64

DasFox

Diamond Member
I just noticed in XP Pro x64 whenever I run MS paint I get a bug file:

wiadebug.txt:

====================Start 'mspaint.exe' Debug - Time: 2006/03/04 23:52:32:375====================
Could not revoke the client's pIWiaEventCallback from the Global Interface Table
Could not revoke the client's pIWiaEventCallback from the Global Interface Table


Anyone have a fix for this MS Paint bug in XP Pro x64?

THANKS
 
I've been running Windows 20 years, I'd say I know what I'm doing, yes I'd make a good beta tester. This bug happens on a fresh install of x64 with Paint, also when installing some applcations it reports back a bug as well, so the next time I see one of those on a install, I'll report that one back here, as well.

Anyone who has been around Windows for any length of time, knows that x64 has some issues with drivers, and 32 bit applications, since 32 bit will be a large amount of the software running and that the system has some issues, bugs, still that need working out, that's all there is to it.

ALOHA
 
I'm running Windows XP Pro 64bit and I have not gotten that error with my MS paint. Sorry I can't help you with that, try googling it. Last resort, try emailing Microsoft and see what they say...Just some suggestions.
 
This reminds me of the first AT-clone, that I bought in 1987. It was a 12.5MHz 80286 with 1MB of RAM. It was a clone, in the days when PC clones were still a risk.

Anyway, everything seemed to work great, except for MS Paint (the DOS version, of course). Paint had some weird bug with this system.

That made me nervous (having been living with Apple clones for years, with problems). So I asked the seller to fix the problem. He substituted his older 10MHz 80286 motherboard, which worked perfectly.

Of course, by doing this, I was taking a 25% performance hit. But it was worth it for a board that ran without errors.

I guess history repeats itself, huh?
 
Originally posted by: EuR Fr3nCh T3rRoR
I'm running Windows XP Pro 64bit and I have not gotten that error with my MS paint. Sorry I can't help you with that, try googling it. Last resort, try emailing Microsoft and see what they say...Just some suggestions.


Aye Aye El Cap e Tahn 😉

http://support.microsoft.com/gp/contactbug

By the way I'm getting some other bug when doing some installations, with installervise, so I'll post one of those the next time I see it and call MS over it too.

THANKS
 
Report a bug to microsoft and get a update put out by them that opens up 4 other bugs that the OS code had waiting to be released to the public. Just joking around, but suprisingly I have not had any issues with Windows XP Pro 64bit on both of my rigs.

<--Knocks on wood...
 
Are you certain it's not related to:

1. A particular driver you have installed.
2. Faulty hardware.
3. An unusual operating system configuration (you mentioned in another post that you disabled several system services).
 
Originally posted by: MrChad
Are you certain it's not related to:

1. A particular driver you have installed.
2. Faulty hardware.
3. An unusual operating system configuration (you mentioned in another post that you disabled several system services).

I think your number 1 and 3 choice is possible, but I don't think faulty hardware would cause an error message within MS Paint only, maybe it would, but I wouldn't think so...I think more then likely it's a certain driver he has installed, since I have not been having any issues really with XP 64, but I could just be lucky too though.
 
DasFox, why don't you try doing a ChkDsk? Run the Windows disc and do a ChkDsk, and see if it fixes it. You might just have a corrupted Windows file laying around somewhere, or even a corrupted Registry file. I had a power outage not that long ago and I had to reformat my second rig, because it corrupted some data that had to do with Windows and I was getting errors, but reformating fixed it for me.

Just trying to help mate.
 
Back
Top