Windows API

Apparently that is a known issue. Responding to MCN_GETDAYSTATE should work they say. But that are what I'm already doing and it works very well on XP but not Vista. I have not seen any application that using bold days in SysMonthCal32 to work at all on Vista. not even MS own Windows Calendar. Guess I have to turn off Windows Theme for that application. Then the Old version of SysMonthCal32 is used and then it works. But it is so ugly. But that is our workaround until the bug is fixed. And it must be a bug since I can't see it work in any application on any Vista machine I test. I haven't been able to find a list of known bug of Vista. Guess MS does not publish that. So I have spent 2 days at work trying to fix something that are unfixable. - Mathias S.

It doesn't matter if you're logged in as admin, by default you don't have permission to modify parts of the registry like HKCU (where COM registration is kept). You can register it manually with regsvr32, or run the IDE elevated. --Mike-- Visual C++ MVP :cool: LINKS~! CP SearchBar v3.0 | C++ Forum FAQ Dunder-Mifflin, this is Pam.

There was a "microsoft.com" key at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\EscDomains in the registry I assumed that means "Escape Domains" or sth like that, however deleting it (+reboot) didn't help. Greetings - Gajatko Portable.NET is part of DotGNU, a project to build a complete Free Software replacement for .NET - a system that truly belongs to the developers.

You have a space in your security descriptor text string. That's not allowed according to the MSDN documentation. Vista is most likely stricter at interpreting the string. As a style point I would prefer using the alias "WD" for 'Everyone', rather than the SID S-1-1-0. DoEvents: Generating unexpected recursion since 1991

Here are a few links for you. Windows Vista User Experience Guidelines[^] Developing with Windows Vista[^] Windows Vista Application Compatibility[^] The Windows Vista Developer Story: Application Compatibility Cookbook[^] As for programming issues, UAC is probably the one to watch out for, just learn how to write a manifest file and you should be ok. regards, Jonathan Wilkes Darka[Xanya.net]

I am sorry the xml file for ipApplication.exe.manifest is <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="1.0.0.0" processorArchitecture="X86" name="ipApplication" type="win32"/> <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3"> <security> <requestedPrivileges> <requestedExecutionLevel level="requireAdministrator"/> </requestedPrivileges> </security> </trustInfo> </assembly>

You asked this in HW with no response. Take it to the Vista forum. Morality is indistinguishable from social proscription

In some cases, it is the processor. For example, the old Motorola 68000 used the high bit of the addressing registers as a flag bit, thereby cutting the maximum memory size to 2G. Sometimes, the addressing bus only allows for 31 bits and the high bit line is used for signalling. I don't think Intel does such a thing with their processors. But, I also heard that using memory above 2GB, programs slow down. Maybe, the processor or the OS is doing something special to access this memory. Also, the operating system, system BIOS, and many of the IO addresses are directly memory mapped. (The operating system should load into memory.) Therfore, some of the memory addressing space is used for ROM access and other memory addressing is to the IO channels.

I haven't programmed in Vista for about 9 months. But if you want to store your data in the registry, if you place it into HKEY_LOCAL_MACHINE, vista will not allow that. It creates a copy in the current user's node only. Try using HKEY_ROOT instead. If you want to place the data on disk, Vista has a folder called Program Data, similar to Program Files. Place your data there instead of program files.

I believe so, the rest of the information on the property page for an image in Vista is the EXIF info, the tag itself will also be stored in the photo and is more metadata than EXIF but is definately stored in the photo itself which is why you can only tag certain file types. One problem with editing these tags is that it might break the ability of other applications to read the original file's metadata (EXIF) due to the fact that each graphics package / camera manufacture seems to use these tags sightly differently. regards, Jonathan Wilkes Darka[Xanya.net]

You can do this easily by clicking on the "START" button, then right click on "Computer" and select "Properties" and look at the System Type. Or in C++; bool Is64BitOS() { SYSTEM_INFO sysInfo; GetSystemInfo(&sysInfo); if((sysInfo.wProcessorArchitecture == PROCESSOR_ARCHITECTURE_AMD64) // x64 (AMD or Intel) || (sysInfo.wProcessorArchitecture == PROCESSOR_ARCHITECTURE_AMD64)) // Intel Itanium Processor return true; return false; } regards, Jonathan Wilkes Darka[Xanya.net]

Right-click the drive, go into Properties, Security tab, click Advanced, add the Everyone group and allow it Full Control. Check the box to Replace Permission Entries On All Child Objects With Entries Shown Here That Apply To Child Objects. That'll rewrite all the ACLs on the drive. If you want slightly more security than that, add the local Users group instead. NTFS-formatted disks have never been portable between systems - the Security Identifiers (SIDs) are based on the machine's SID which is randomly generated by setup. When Explorer in Vista gets the inevitable Access Denied error it throws up a UAC prompt to confirm that you'd like to use your admin powers to take ownership of the object and then to edit the ACL, but it only does so for that one object and the one permission that was required. You can of course use FAT32 which has no security at all, but it has a 4GB limit on the size of a file. DoEvents: Generating unexpected recursion since 1991

You can obtain OEM Windows Vista through the System Builder program. Rules are at http://oem.microsoft.com/script/contentpage.aspx?pageid=561815[^]. The basic differences are: - OEM Windows is not transferrable, it must stay with the original machine it was first installed on. Retail Windows can be transferred to different machines. - OEM Windows support is through the OEM that sold it. There is no recourse to Microsoft. In effect that makes you the support department. Retail Windows includes two free support incidents. DoEvents: Generating unexpected recursion since 1991