| View previous topic :: View next topic |
| Author |
Message |
sieber
Newbie
Joined: 01 Jul 2003
Posts: 13
Location: Germany
|
 Posted: Wed Jul 23, 2003 2:24 pm Post subject: |
 |
|
Hy,
I have found the problem. but not a solution.
The copyright character makes the problem. If I remove the ® (hex 0xAE) or © (hex 0xA9) character from the Version info and recompile the EXE, it works.
Also the VDS add-on programs are not working (e.g. TipOfDay.EXE; Infos Manager.exe; DialogDesigner.EXE)
Any Idea ?
Jochen |
|
| Back to top |
|
 |
FreezingFire
Admin Team
Joined: 23 Jun 2002
Posts: 3508
|
| Posted: Wed Jul 23, 2003 2:40 pm Post subject: |
|
|
They are probably not working because of the copyright character in the
version information, like you said. 
_________________
FreezingFire
VDSWORLD.com
Site Admin Team |
|
| Back to top |
|
|
PGWARE
Web Host
Joined: 29 Dec 2001
Posts: 1566
|
| Posted: Wed Jul 23, 2003 2:53 pm Post subject: |
|
|
It may be that there are missing portions within the VERSIONINFO resource. After checking many exe's with version info and the ones in vds exe's here is what I found missing in the vds exe's:
| Quote: |
PRODUCTVERSION
FILEFLAGSMASK VS_FFI_FILEFLAGSMASK
FILEOS VOS__WINDOWS32
FILETYPE VFT_APP
|
The bold sections are the parts missing within the resource section for versioninfo. Actually FILEOS VOS_NT_WINDOWS32 is listed within the vds exe's, in other dll's/exe's I've found this to actually be FILEOS VOS__WINDOWS32.
The copyright character within the versioninfo structure is completely standard. I checked all other portions of the versioninfo and everything matches up fine except for those two lines mentioned above. |
|
| Back to top |
|
|
jules
Professional Member
Joined: 14 Sep 2001
Posts: 1043
Location: Cumbria, UK
|
| Posted: Wed Jul 23, 2003 2:58 pm Post subject: |
|
|
I don't think that's relevant. I have a pretty good idea what the cause might be now, but because it is connected with the techniques used to protect EXEs against decompilation and modification I can say no more about it. I didn't write the code concerned, which appears to originate in VDS 4 anyway, but I am passing my thoughts on to the appropriate people. I'm pretty sure it will be possible to fix this, but it's going to require both an IDE and a run-time update.
_________________
The Tech Pro
www.tech-pro.net |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
@vdsworld