Thanks for any suggestions,
Got a program somewhat working in Windows 7 Pro but it just stares at me in Windows XP Pro on Wiffies computer.
Any ideas?
Thinking about transferring the whole masm folder to Wiffies computer and trying again.
I have little hope that that will make any difference as I did just that not to long ago.
hiya Jack
without seeing the code - hard to say
my guess is that you are using a newer function or (more likely) a newer functionality of an old one :P
Hi Dave,
Still using the SDK from the late 90s.
With the old visual studio from the same time.
It really ought to work on XP and not on 7 one would think.
You may can fix i by running it as administrator...
Yes it did work in safe mode Qword.
I copied the entire masm32 folder to wiffies XP Pro computer.
Compiled the program there and it stared at me.
Can't delete the executable module as it gives an access denied message.
Had to go into safe mode to delete it. This shouldn't be necessary.
Since I am using the old SDK I shouldn't have anything in the program not compatible
with XP. :(
WinXP is more temperamental than Win7, If you forget to save esi, edi, ebx, ebp, esp where you use them, the program will have problems, were Win7 seem to disregard them at times (From what I have seen) Mis aligned stack maybe? Hard to tell without seeing code.
One day I have create one code to win XP, and worked fine. But when I enable the visual effects, it don't worked. Then I corrected it, and when I tryed in Vista, don't worked again.
The fault is that I do not have fully filled some structures.
Try it.
Quote from: shankle on June 18, 2011, 01:30:47 AM
Can't delete the executable module as it gives an access denied message.
Had to go into safe mode to delete it.
You have tried to kill the process? (Taskmanager)
If this wont work, it could be a problem with ruining AV, that keeps an open handle to the image. (I've seen this when using the famous Norton AV :bg)
You may show us your code?
No I have not tried killing the process but I will.
I am using ESET SS for my virus program.
Will keep on digging. Maybe using another approach.
Nothing out of the ordinary with the APIs.
Problem is solved. Now working in Windows XP Pro and Windows 7.
Problem caused by the intricacies of CreateWindowsEX.
Thanks for your help.
Quote from: shankle on June 19, 2011, 07:35:43 PM
Problem caused by the intricacies of CreateWindowsEX.
C'mon, sharing is loving - details please :thumbu
Ok will try.
One of the "addr" was not capitalized. Not sure if that is a problem.
I had the dwExStyle parameters mixed up with the Windows Style parameters.
Since I am going to have to have more than one "CreateWindowsEx" in my
program the hWndParent doesn't seem to want to work when changed to
something other than "NULL".
Quote from: shankle on June 19, 2011, 10:51:42 PM
Ok will try.
One of the "addr" was not capitalized. Not sure if that is a problem.
I had the dwExStyle parameters mixed up with the Windows Style parameters.
Since I am going to have to have more than one "CreateWindowsEx" in my
program the hWndParent doesn't seem to want to work when changed to
something other than "NULL".
The addr thing doesn't matter. Mixing up the Extended Styles with the reg window styles will matter. The first (Main window) you create, the parent is NULL, everything else (all children) and other windows, need a valid parent handle, or they don't get created correctly.