RE: Rel 1.00 online
"Georges Berenger" <[email protected]> Fri, 24 Jun 2005 17:07:21 -0700
| Newsgroups | gmane.network.vnc.ultravnc.general |
|---|---|
| Message-ID | <76261096A156DE42AA68E538D3B401B6FE8F20@DALY-MSG.global.avidww.com> |
Thanks for the quick answer with details. About the driver: were the changes "important"?... I read that strings were missing. Was it serious in any way? thanks again, -georges _____ From: [email protected] [mailto:[email protected]] On Behalf Of De Vos Rudi Sent: Friday, June 24, 2005 5:23 PM To: [email protected] Subject: Re: [Ultravnc-list] Rel 1.00 online There where just some minor changes after Jun13... Viewer: -Fix 95 OSR1 (file transfer: function unknown in 95) -Let the user close the deamon without that the viewer close (viewer listener mode) (some people run a batch that cont start the server, if they can close the deamon they don't get a new viewer every x minutes) Server -Error in resource. Radio buttons where grouped wrong, (oder in resource file) -Important: check if the driver dll version also allow 1.019 (was fixed 13 of 14 June) New driver dll version was updated to 19. But winvnc does a dll check and only allow 18. Changed to allow 18 and 19 Georges Berenger schreef: For feature requests and bug reports RC15 RC16. Please use the forum at http://forum.ultravnc.net/ Contratulations! Two questions: - I found that a lot was checked in June 13 brings quite a few changes, just after I took the last update before our code freeze. Those include a new driver and a number of changes related to fast user switching. I was wondering if anyone could comment on how critical those changes were. At this point of our project, I can't take changes anymore without any major reason... - I've noticed that the you guys had followed my past advise, and grouped version info declaration in a header file included by the different resource files. However, the implementation did not include the advised separate rc2 file for the version part, to make the scheme compatible with Dev Studio's resource editor. Bottom line, Visual Studio removed the declarations from the resource file (I guess that's what happened, as it happened to me a few times...), and you are now back in the previous situation with all strings burned into every .rc file. If you wish to have again version info centralized & use VisualStudio to edit non-version info resources, you must create a second resource file .rc2 that you include in the regular .rc file. To repeat the info I gave in the original suggestion email: The versioninfo.h file that lives at the top of the source tree contains all the info needed. The resource files then need to include that file and use the definitions made in it. If you have problems with a resource editor (Visual Studio will replace the defines by their value if you open the resources with a non-text editor), you can place the version resource in an other file included in the original .rc file. For instance: Winvnc.rc: #include "winvnc.rc2" ... (remove the version info and leave the file otherwise unchanged) Winvnc.rc2: (to be edited with a text editor only) #include "versioninfo.h" // adjust the path as necessary... #ifndef _MAC //////////////////////////////////////////////////////////////////////// ///// // // Version // VS_VERSION_INFO VERSIONINFO FILEVERSION INT_VERSION PRODUCTVERSION INT_VERSION FILEFLAGSMASK 0x3fL #ifdef _DEBUG FILEFLAGS 0x1L #else FILEFLAGS 0x0L #endif FILEOS 0x40004L FILETYPE 0x2L FILESUBTYPE 0x0L BEGIN BLOCK "StringFileInfo" BEGIN BLOCK "080904b0" BEGIN VALUE "Comments", "\0" VALUE "CompanyName", STR_COMPANYNAME VALUE "FileDescription", "VNC server for Win32\0" VALUE "FileVersion", STR_FILEVERSION VALUE "InternalName", "WinVNC\0" VALUE "LegalCopyright", STR_COPYRIGHT VALUE "LegalTrademarks", "VNC\0" VALUE "OriginalFilename", "WinVNC.exe\0" VALUE "ProductName", "Ultr@VNC\0" VALUE "ProductVersion", STR_PRODUCTVERSION END END BLOCK "VarFileInfo" BEGIN VALUE "Translation", 0x809, 1200 END END #endif // !_MAC Cheers & congrats again! -georges ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&opÌk